Back
PrivacyTerms
Myte.ai

What the public chat stores, and what it does not.

What you write to Myte, and what Myte writes back, are not written by the Myte app to MongoDB or durable application storage on the DGX Spark. The active thread stays only in page memory for the current loaded visit, while the live request is processed transiently in memory so Myte can answer. If you choose supported local files, Myte extracts text for the current loaded visit and sends only that extracted text transiently with the live request.

Anonymous chat

  • Anonymous public-chat inputs, outputs, and reconstructed transcript history are not written by the Myte app to MongoDB or durable application storage.
  • The active thread lives only in page memory for the current loaded visit.
  • During a live request, the exchange exists transiently in memory and inference buffers so Myte can answer.
  • You can clear the thread at any time with Clear chat.
  • 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.
  • Raw attached files are not stored by the Myte app as durable anonymous-chat records. Only extracted text is sent transiently with the live request.
  • Myte does not use anonymous public chat to create a durable public-chat account, named profile, or normal per-person usage ledger.
  • Because Myte controls inference at the hardware layer, the exchange does not need to pass through a third-party inference provider.
  • Spark mode can continue a long reply across multiple live runtime cycles for the current request, but it does not change the anonymous retention boundary.
  • If you explicitly send feedback, Myte stores an encrypted record containing the room-shape telemetry already used to run the service, plus the thumbs signal and optional note you choose to send.
  • 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 usage totals, route health telemetry, and hashed throttling identifiers.

Account and API surface

  • Email, display name, 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.
  • Usage counts, token totals, latency, and route rollups are stored for operations and reporting.
  • Prompt 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 minimal service-protection and usage metadata to operate the lane, but it is not intended to become a durable registry of anonymous chat users.

TermsDocs