Emailing your snapshot.
When enabled, you can ask us to email one report for your snapshot, which you can forward to your IT team. We store the address you enter encrypted for up to 180 days, and remove it earlier if its snapshot run is deleted. We use it to send that report and an internal notification to Meo through Resend, our email processor. We don’t add it to marketing lists; marketing updates need the separate opt-in. The emails themselves are subject to the receiving mailbox’s retention. SMS and automated calls are off. To ask for deletion, use the Meo contact route; do not send private report links or sensitive findings.
Information used for a request.
The instant service uses the submitted public business domain, confirmed scope, bounded public evidence, request/job state and the technical records needed to limit abuse and provide private access. Do not submit credentials, personal records, patient details, private links or confidential information.
Public evidence is summarized for the snapshot. It may contain errors or incomplete observations. Sensitive raw records should not be included in the displayed evidence.
The browser session controls access.
Private results are bound to a secure HttpOnly session cookie. A run identifier alone does not grant access. Access can expire or be revoked; opening a run in another browser session may not work.
Do not share the browser session. Do not put private report links, capability values or sensitive evidence into support messages, analytics or public posts. Search-engine exclusions and referrer protections supplement access controls; they are not authentication.
Deeper-review requests, when enabled.
The optional two-step form collects email, name, phone, company, public domain, an optional snapshot reference and your contact choices so a Meo advisor can handle your request. Contact fields in the stored request record are encrypted using AES-256-GCM; domain, request metadata and permissions are not encrypted. Stored requests are retained for 180 days, then removed by worker maintenance along with the notification queue.
An internal notification email containing those details is sent through Resend, our email processor, to Meo’s internal inbox for advisor follow-up. The notification is subject to the internal mailbox’s retention; the stored request record’s encryption and 180-day retention do not apply to that email. A recorded receipt does not prove notification delivery or authorize testing. Manual advisor calls and optional marketing are separate, unchecked choices. SMS and automated calls remain off. We do not sell request information. For deletion requests, use the existing Meo contact route; do not include private report links or sensitive findings.
When the feature is disabled, no contact form is shown. Third-party analytics and advertising scripts are not enabled.
Lifetime and deletion.
The service stores run evidence for a maximum of 14 days, with private session access limited to that period or less. Expired or revoked runs are denied immediately on a status read. The worker removes expired or revoked run records during maintenance; while it is running, it checks for purge work at least once per minute.
Do not treat a private snapshot as permanent storage. There is no public self-service deletion form. Operational maintenance and any future backup/subprocessor policy must not be confused with a guarantee that physical deletion occurs at the exact second access expires. The existing marketing audit’s longer retention periods do not apply to instant snapshots.
Provider and model boundaries.
Third-party passive providers and production model interpretation are disabled in the initial native release until their contracts, data use and limits are approved. No credential/breach-record searches or new scan submissions are part of the instant scope.
A synthetic sample is for layout explanation only and contains no customer record or live finding.