Grey Mirror by JustLayMe

Relationship-message privacy must be explicit, not implied.

Grey Mirror handles sensitive relationship-message uploads. This page keeps the public guidance conservative and routes account-specific requests to the formal privacy, data-deletion, trust, and contact surfaces.

How should users think about privacy?

Users should treat relationship-message uploads as sensitive personal data. Grey Mirror public copy avoids unsupported security, compliance, retention, deletion, or training-data claims and links to current policy surfaces for account-specific requests.

What data may be involved?

A Grey Mirror run may involve raw uploads, normalized messages, participant labels, parser diagnostics, report artifacts, cached assets, account identifiers, and payment or unlock state depending on the flow.

Which details belong on the formal policy pages?

The public explainer should not turn operational details into promises unless the formal policy pages also say them. Use the linked pages for current account, deletion, access, and privacy-request language.

Raw upload and normalized-data retention windows belong on the current privacy and deletion pages.
Report retention, cache cleanup, backup expiry, and temporary export cleanup should match the implemented policy surface.
Deletion, export, and access-request workflows should route through the site’s account, privacy, deletion, trust, or contact paths.
Training-data and subprocessor language should stay conservative unless the current policy states a specific claim.
Region-specific rights language should appear in the formal policy pages, not in isolated product copy.

What should the product never claim without proof?

Trust copy is only useful if it is accurate. Grey Mirror should not claim certifications, encryption specifics, compliance status, region-specific rights handling, or subprocessor lists unless the underlying policy and implementation support it.

No fabricated SOC 2, HIPAA, GDPR, or ISO claims.
No unsupported encryption-at-rest or end-to-end encryption language.
No fake deletion SLA.
No unsupported training-data promise.

Where should users go next?

Users should read the formal privacy policy and contact support for account-specific requests. This page is a product-specific privacy explainer, not a replacement for approved legal policy.

Privacy policy

Formal site privacy terms.

Trust Center

Public trust and responsible-use surface.

Contact

Support and privacy request routes.

Frequently Asked Questions

Can I delete my uploaded conversation?

Use the data-deletion, privacy, trust, or contact routes for the current request path. Grey Mirror should not promise a deletion outcome in a guide page that the formal policy does not support.

Does Grey Mirror train on my messages?

This guide avoids unsupported training-data claims. Check the current privacy and trust pages for the live policy language.

Is Grey Mirror HIPAA or SOC 2 compliant?

No such claim is made here. Public copy should not state compliance certifications unless they are verified and approved.