Mimic privacy policy

Beta privacy policy · Effective 29 October 2026

Information processed

Mimic may process a verified email address and identity identifier, display name and pending access-request status; approved workspace membership and server-assigned roles; user-provided profile details; rails, jobs, work, messages, requests, decisions, corrections, source citations, and audit metadata.

Where enabled, it also processes uploaded files, source text, skill documents and references, and the information returned by authorized retrieval calls.

Do not provide passwords, authentication phrases, one-time codes, government identifiers, payment-card data, unrelated sensitive personal information, full private transcripts, or hidden chain-of-thought reasoning.

Purposes

We use this information to authenticate users, enforce workspace permissions, preserve authorized work context, retrieve relevant material, coordinate work and decisions, inspect source citations, correct records, secure the service, and investigate failures.

Who receives information

Workspace information is returned only through tools authorized for the connected account and its permitted workspace scope. Installing or connecting the plugin does not automatically grant access to a workspace. Beta access requires approval.

Infrastructure and authentication providers, including AWS and Google/Cognito, may process information needed to host and authenticate the service under their applicable terms. When you use Mimic through OpenAI or another connected AI service, the material intentionally submitted or retrieved through that connection is also processed by that service under its applicable terms and account settings.

We do not sell workspace information.

Retention and deletion

The beta keeps workspace records for operational continuity until an authorized owner requests export or deletion or the service is closed. Export and deletion requests are handled through support. Some security and audit records may be retained where reasonably necessary to prevent abuse, resolve disputes, or meet legal obligations.

Disconnecting or revoking a connection does not by itself delete workspace records or information already returned to an AI service. Requests affecting shared records, sealed archives, or backups require review of the applicable access, integrity, and retention requirements. This policy does not promise immediate erasure of every copy.

Your choices

Contact support to request access, correction, export, or deletion of workspace information; correct a role; revoke access; or ask a privacy question. We may need to verify your identity and authority over the material before acting.