Read how Grey Mirror restricts access to your uploads and reports, handles security issues and protects private conversation data. Report a concern here.
Your conversation is private. This page explains how we restrict access to uploads and reports, check account ownership and handle security issues. It also tells you how to report a concern.
Authored policy source: July 16, 2026
Factual revision updated:
OAuth 2.1
MCP account linking uses PKCE-capable OAuth flow.
Deny first
Full report, metrics, and comparison tools verify ownership and entitlement.
No raw logs
Tokens, secrets, raw uploads, and message bodies are redacted or omitted from MCP logs.
Authentication and account linking
Browser sessions use JustLayMe authentication. ChatGPT connector access uses the MCP OAuth flow, bearer access tokens, scoped permissions, expiration, refresh, and revocation.
Private bearer mode exists only for controlled development and must not be used for public Apps Directory traffic.
Authorization boundaries
Every MCP report, status, metrics, checkout, participant, and comparison tool verifies the JustLayMe user and job ownership before returning data.
Full report and full metrics output require existing JustLayMe entitlement. A ChatGPT identity alone never unlocks a report.
Upload and raw content protection
Grey Mirror uploads are handled through JustLayMe's authenticated upload system, never through open public static paths.
MCP v1 avoids returning raw intimate message text by default. Preview outputs are limited to summaries, scores, safe metrics, evidence density, limitations, payment state, and deep links.
External model boundary
Report writing uses derived report facts rather than complete raw transcripts by default. DeepSeek can also receive limited excerpts and file names during upload to help read an unfamiliar export. When JEV features are enabled, its configured providers can receive limited excerpts or compact conversation windows for participant attribution and claim checks, as described in the Privacy Policy. These separate processing purposes should not be mistaken for an entirely on-device analysis.
This boundary is enforced on the server. Provider keys remain on the server and are never bundled into browser JavaScript.
Monitoring and incident response
The MCP stack records structured audit events for auth failures, ownership failures, entitlement failures, checkout link generation, summary access, metrics access, comparison access, and participant mapping.
Security issues can be reported through the public security contact route. Confirmed incidents are triaged by impact, containment, remediation, notification obligations, and prevention work.
Certifications and limits
Do not treat this page as a SOC 2, ISO 27001, HIPAA, or PCI attestation unless a completed attestation is separately published.
Payment card data is handled by payment processors. JustLayMe should not receive raw card numbers through the app or MCP connector.
Frequently Asked Questions
Does the MCP connector expose raw messages?
No by default. It returns structured, entitlement-gated report data and deep links back to JustLayMe.
Can a guessed job ID expose another report?
No. MCP tools verify ownership before job, report, metrics, comparison, participant, or checkout operations.
Read how account-scoped uploads and report access are handled in the published security and privacy information.
02
Processing
Check the current processor and retention terms for the information you upload.
03
Removal
Know the deletion route before supplying a conversation you may later want removed.
Conceptual reading guide. This diagram explains what to inspect; it is not a customer report, diagnostic test or measured relationship score.Use this guide on the question you came with
A polished interface is not a security guarantee. Review the published controls and contact support about a specific concern before uploading.