Privacy Notice · reviewed 1 October 2026
Your public-service data and your choices.
The public Laboratory calculates in your browser. The website receives ordinary technical request information, and an enquiry is sent only when you submit it. This notice describes the public website, Laboratory, Lens and enquiry route. Macrovision is planned and is not accepting paid engagements or institutional financial records.
Information by activity
The information received depends on the feature you choose.
Calculation inputs are different from website connection information and contact correspondence. An ordinary page download does not upload your Laboratory assumptions.
| Activity | Information and purpose | Where the information goes |
|---|---|---|
| Website delivery and security | Connection and request metadata, which can include IP address, route, time and response information, to deliver the service and investigate reliability or abuse. | Hosting and operational systems. These records are distinct from calculation inputs. |
| Laboratory calculation | The editable assumptions and result needed for your chosen experiment. | The calculation Worker in your browser. The public calculation does not submit those values to YieldGuard or an AI provider. |
| Optional walkthrough handover | The calculation request, receipt and model information you deliberately choose to copy. | Same-tab browser session storage for up to 30 minutes. No financial values are placed in the page URL, an enquiry, email or analytics. You can clear the copy from the walkthrough. |
| Public Lens | A public market-context snapshot and ordinary request metadata. | Same-origin public reads. Browser Lens contact intake and click telemetry remain disabled; the separate intake API can record a deliberately submitted consented contact request. |
| Enquiry submission | Organisation, work email and a brief problem, with your handling acknowledgement, random reference, creation/expiry times, notice version and a request-integrity hash. | A private server queue for review and response. Submission does not create a subscription or paid engagement. No attachments or Laboratory inputs are collected by this form. |
| Email and privacy correspondence | Details you send, necessary reply history and proportionate information needed to handle a request or complaint. | The company's correspondence process. Email is an alternative channel and has a separate retention purpose from the enquiry queue. |
Enquiry rate limiting uses temporary in-memory network identifiers for up to 20 minutes. The enquiry record does not persist an IP address, browser header or page URL. Please describe the business problem without sending credentials, private keys, full cash positions or personal records.
Strategy builder and experiment histories.
The public strategy preview calculates and retains results in this browser page. It does not send financial inputs or results to the strategy database. An optional Laboratory continuation uses a same-tab local copy that expires after 30 minutes. Reset clears the preview and that copy; a download remains under your control.
Purchased workspace access is planned and closed. Its implemented service is disabled for customer operations. Before activation, its processing notice and agreement must explain automatic result recording, the strategy-building purpose, who can access records, retention and backup periods, export and deletion. Purchased workspace runs are intended to preserve exact inputs, calculated outputs, model versions and receipts; they are not used to train an AI model or execute transactions.
Privacy, access and deletion requests use contact@yieldguard.io.
Purposes and lawful bases
Public-service information is used for delivery, security and the request you make.
YieldGuard relies on legitimate interests to operate and protect the public service and to respond to a business enquiry. Processing is limited to information needed for those purposes. Privacy rights and legal obligations are handled under the applicable legal requirement. Where contractual steps apply to a request by the prospective individual contracting party, that basis can also apply.
The enquiry acknowledgement confirms that you understand the stated handling; it is not marketing consent. The public form does not subscribe you to marketing, send the content to an AI service or send an automatic outgoing email. The public site does not activate advertising or optional analytics trackers. YieldGuard does not sell enquiry records or use them for advertising.
Local Laboratory calculation values are not collected for hosted model training. Institutional AI extraction, change explanations and document preparation remain planned. Provider terms, permitted data flows and review controls must be agreed and evidenced before institutional AI receives customer content.
Retention and deletion
Enquiries expire from the active queue after 30 days.
The enquiry service removes expired queue records on startup, before access and through maintenance every minute while running. The queue is separate from the public static site and its release archives. A queue reference is an acceptance record, not a delivery receipt for an email.
Email correspondence and privacy-request records have separate purposes. Such records are kept while needed to answer and resolve the matter or meet an applicable legal, dispute or security obligation. Operational logs are retained for service and security needs; no fixed log-retention period is promised by this notice. Ask the privacy contact about the record or period relevant to your request.
Deleting an active queue record does not establish immediate erasure from hosting-provider snapshots or existing email correspondence. A provider snapshot retention/deletion configuration has not been independently qualified for this public enquiry service. The website therefore makes no blanket promise of immediate deletion from every recovery copy.
The optional local walkthrough copy expires after 30 minutes and is rejected and removed on later access after expiry. Closing the tab ordinarily ends its session storage; you can remove the copy earlier using the walkthrough's clear control or browser storage settings. The Laboratory's service worker caches public application assets, not your calculation inputs.
Providers, security and transfers
Current public hosting and planned customer processing have separate boundaries.
The public site and private enquiry queue use a Hetzner-hosted server in Falkenstein, Germany, checked on 1 October 2026. Website transport uses HTTPS. Queue file permissions restrict ordinary access to the service and authorised operators; no independent storage-encryption or assurance guarantee is made.
Correspondence uses a business-email provider. Public mail-routing records point to Zoho EU; those records alone do not establish every processing location or the mailbox's retention settings. Hosting, communications and authorised operational access can receive information needed for their service. No AI provider receives a public enquiry or Laboratory calculation through these flows.
A full institutional subprocessor and transfer register is not established. Before institutional records are accepted, the actual contracts, hosting/support locations, recipients and applicable UK/EEA transfer mechanism and assessment must be documented. The public website does not claim that EU routing or a server location alone establishes those safeguards. External websites linked from YieldGuard apply their own notices.
Rights and concerns
You can ask YieldGuard about your information or make a privacy complaint.
Email contact@yieldguard.io or write to the registered office. Include the contact address or enquiry reference and the matter you want reviewed. A form, account or paid engagement is not required. YieldGuard may seek proportionate identity information when necessary; do not send identity documents unless a justified verification method has been agreed.
UK data-protection law, including the UK GDPR and Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025, applies to relevant processing. EU GDPR can also apply where its territorial conditions are met. A draft institutional standard or an unavailable product does not remove existing statutory rights or obligations.
Changes to processing
A new data flow needs a clear notice before information is submitted.
A hosted save, customer import, AI provider or integration would change the present public boundary. YieldGuard must explain the new purpose, recipients, authority and handling before that feature receives information. The product-status register identifies current availability, and the Cookie Policy describes the browser storage used by the public experiences.