Back
PrivacyTerms
Myte.ai

What Myte stores, and what it does not.

Myte is operated from Quebec, Canada. For chat, Myte does not retain durable records of what you send or what Myte answers. For accounts and API access, Myte stores the identity, access, and usage information needed to operate the service, including name, email, verification state, key metadata, request counts, and input and output size totals.

Anonymous chat

  • Anonymous chat inputs, outputs, and reconstructed transcript history are not retained as durable service records.
  • The active thread lives only in page memory for the current loaded visit.
  • During a live request, the exchange is processed only long enough for Myte to answer.
  • You can clear the thread at any time with Clear.
  • Public chat does not request device or folder access automatically. If you choose Attach, your browser opens a file picker only for the supported files you select.
  • Supported local file attachments are processed as text-extraction-only context for the current loaded visit. Unsupported, executable, macro-bearing, embedded-binary, encrypted, or suspicious files are rejected.
  • For supported attachments, text extraction happens for the current session and the extracted text can be sent transiently to Myte only to answer the live request.
  • Raw attached files and extracted attachment text are not retained as durable server-side anonymous-chat records after the request completes.
  • Myte does not use anonymous public chat to create a durable public-chat account, named profile, or normal per-person usage ledger.
  • Longer replies may continue across more than one live pass for the same request without changing that retention boundary.
  • If you explicitly send feedback, Myte stores the thumbs signal and optional note you choose to send, plus limited service metadata needed to process it.
  • That feedback record does not include your prompt body, Myte's reply body, or a user identity field.
  • Limited service and anti-abuse metadata can still be retained to operate and protect the service, including request counts, route and latency health, hashed throttling identifiers, and input and output size totals.

Account and API surface

  • Name, email, verification state, and session lifecycle metadata are stored to operate accounts.
  • Project names, key metadata, key prefixes, and one-way key verifiers are stored for API access.
  • Request counts, input and output size totals, latency, and route rollups are stored for operations and reporting.
  • Query bodies and response bodies are not retained as durable service records.
  • Passwords and full API-key secrets are not stored in plaintext.
Practical boundary

Anonymous public chat is designed to stay anonymous at the application layer. Myte keeps only the limited service, access, and usage metadata needed to run and protect the service, not a durable record of what anonymous users ask, what Myte answers, or the local files they attach.

TermsDocs