Privacy Policy

Data we collect

This policy covers the JustLayMe website and the Grey Mirror Apple app, including web content opened inside the app. We collect the messages and other content you submit, generated reports, email address, account identifier, purchase history, and optional product-interaction data. Account uploads, saved reports, identifiers, and purchase entitlements are linked to your account to provide the service.

We collect account data such as email address, authentication state, subscription state, billing identifiers, support messages, and security logs.

Our servers log every request they receive: the time, the page or API route (without query strings), the response status and timing, the IP address and approximate country reported by Cloudflare, the browser or app type and version, and your account ID when you are signed in. These request logs are kept for up to 30 days to operate, secure, debug, and improve the service, including understanding where people get stuck. The operator receives email alerts for sign-ins, new accounts, and Grey Mirror runs, plus periodic summaries of these request logs. Request logs never contain uploaded messages, files, or report content.

When you use Grey Mirror or related tools, we process files, screenshots, pasted text, job metadata, derived metrics, report outputs, participant choices, and operational events needed to run the analysis.

How we use data

We do not link your data with third-party data for targeted advertising or share it with data brokers. Optional analytics is used to understand product interactions, not for advertising tracking. Stripe processes payment-card details; we retain purchase and entitlement records to keep paid reports available.

We use data to authenticate you, process uploads, run Grey Mirror analysis, deliver reports, enforce pay-per-report access, support checkout, resolve participant mapping, debug failures, secure the service, and answer support or privacy requests.

On public, non-sensitive pages, first-party analytics are reduced into coarse daily aggregate counts for up to 90 days. Allowlisted event names: public_page_view, public_cta, public_web_vital_cls, public_web_vital_fcp, public_web_vital_inp, public_web_vital_lcp, public_web_vital_ttfb, public_scroll_50, public_scroll_90, public_grey_mirror_start, public_upload_wizard_start, public_upload_file_selected, public_analysis_started, public_sample_report_opened, public_report_paywall_viewed, public_report_unlock_clicked, public_app_store_click, public_mac_download_clicked, public_unlock_offer_viewed, public_unlock_steps_opened, public_unlock_preview_continued, public_unlock_report_granted. Fixed dimensions: page (home, grey_mirror_landing, authority, blog, trust, pricing, other_public); source (direct, search, assistant, referral, campaign_present); viewport (mobile, tablet, desktop); outcome (none, engaged, good, needs_improvement, poor). These first-party aggregates contain no user, session, device, job, report, upload, or transaction identifiers and no raw relationship content. Google Analytics and Microsoft Clarity are separate optional analytics services, enabled by default on eligible public pages and controlled through your analytics preferences. Product-interaction data may be linked to your account where needed for analytics; it is not used for advertising tracking. Google receives manual page views and allowlisted events with queries and referrers removed. Clarity receives globally masked interaction and layout data on eligible public pages, including campaign and in-page-anchor URLs. Both providers stop on private, account, report, upload, and excluded paste-tool routes. Neither provider receives uploads, messages, reports, account data, or custom user identifiers from this integration.

Grey Mirror uploads and reports

Uploads are processed for the report or tool you requested. Sensitive uploads are not served from public static paths. Derived outputs may include summaries, metrics, confidence notes, evidence density, payment state, unlock state, and job status.

Preview and full report data are not the same. The MCP connector and the web app must verify entitlement before returning full report, full metrics, heavy analyzer output, or comparison detail.

Retention

Original uploads, stored messages, and reports stay in your account until you delete the report or your account. They are not subject to the old 24-hour original-upload or 7-day job cleanup schedule. You can request authenticated deletion through /api/privacy/delete-my-data or use the account deletion controls. Temporary working copies and archived transport chunks can expire separately from the retained original upload. Temporary export-download files expire after 30 minutes.

Deletion requests target active application records and known generated artifacts. The exact encrypted-backup expiry schedule is not publicly committed; backup rotation and mandatory security or billing records may outlast active-system deletion.

Hosting and processors

The primary application and analysis systems are privately operated in the United States behind Cloudflare; street-level origin details are withheld for security. Cloudflare handles edge transport and security, Stripe handles billing, Brevo handles transactional email, Google supports optional account sign-in and privacy-limited Google Analytics, and Microsoft provides fully masked Clarity; analytics preferences control these optional services on eligible public pages. The analytics integrations do not receive uploaded relationship content or report data.

DeepSeek has two roles. It writes report prose from derived report facts by default, and during upload it can receive limited excerpts and file names to help Grey Mirror read an unfamiliar export. Upload text is not sent to any other language-model provider for that purpose.

When JEV features are enabled, Vercel AI Gateway and TypeSafe AI can receive limited excerpts for participant attribution, or derived report facts and masked statements for claim checks. The new episode feature, currently under evaluation, sends compact conversation windows with stable participant labels, known names and common contact details masked, and source references preserved. Context can still identify people. JEV does not receive the complete history for these checks and does not write report prose.

Uploaded conversations are not sold for advertising, and report inference does not update active model weights.

Your controls

First-party aggregate analytics are enabled by default on eligible public pages. You can turn both providers off in Settings or at /privacy#analytics-choices, and control first-party aggregate analytics separately. Global Privacy Control (GPC), Do Not Track (DNT), a saved opt-out, an account opt-out, or unavailable preference storage disables optional analytics. Revoking third-party consent tells both providers to stop collecting. Google and Microsoft may set analytics cookies while analytics are enabled; an opt-out withdraws provider consent.

You can request export, deletion, correction, or privacy support at privacy@justlay.me. Necessary operational, security, authentication, fraud, billing, and availability records remain separate from aggregate analytics and follow their own purposes and retention rules.

Frequently Asked Questions