Privacy draft
This launch draft describes the current product architecture. Final publisher identity and public support details will be added before broad marketplace submission.
Depending on the features you use, ME.me may store account and membership identifiers, owner instructions, goals, business or project context, customer or project notes you provide, configured resources, tasks, decisions, outcomes, approvals, workflow state, connector metadata, and similar product records.
The current application uses an external authentication provider for registration, sign-in, and session handling. The ME.me application links authenticated user identifiers to product memberships and roles. The ME.me data model is not designed to store your account password.
Authorized MCP or connector clients may request ME.me tools on your behalf. Content intentionally written through those tools can be stored as product context or history. ME.me does not represent that every connected AI provider follows the same retention or training practices.
The current system records operational and audit information needed to run and troubleshoot the service, such as request metadata, timing, status, change events, and connector audit information. Sensitive credential headers are intended to be redacted from ordinary request logging.
Retention varies by data type and operational need. The current launch build does not yet provide a universal self-service export or complete account and company erasure workflow. We will not publish a fixed deletion promise until the product can reliably honor it.
Customer billing is not enabled in the current launch build, so this policy does not claim that ME.me currently processes customer payment-card information.
