Myte.ai

Terms for the public chat and API lane.

Myte is an evolving inference service. The public anonymous chat is designed to stay anonymous at the application layer, while the authenticated API surface keeps the account, key, and usage metadata needed to run the service.

Anonymous public chat

Ask Myte can be used without creating an account.
Anonymous public chat is designed around no durable prompt or response retention at the application layer.
Myte does not use anonymous public chat to create a durable public-chat account, named profile, or normal per-person usage ledger.
If you choose supported local files, Myte uses them as text-extraction-only context for the current loaded visit. Unsupported, executable, macro-bearing, embedded-binary, encrypted, or suspicious files can be rejected.
Spark mode may continue a long reply across multiple live runtime cycles for the same request, but it remains inside the same anonymous retention boundary.
Rate limits, queueing, and related service-protection controls may still apply to anonymous use.

Output verification

Model outputs can be inaccurate, incomplete, outdated, or misleading.
Verify important outputs before relying on them.
Do not use outputs as the sole basis for legal, medical, financial, safety, security, employment, compliance, or other high-stakes decisions.
You remain responsible for reviewing outputs before acting on them.

Service protection

Myte may apply rate limits, queueing, admission control, and concurrency shaping.
Accounts or API keys may be temporarily suspended or revoked to protect the service and other users.
Availability, latency, supported request sizes, and concurrency policy may change as the system evolves.

Your responsibilities

You are responsible for the content you submit and for ensuring you have rights to any data you send.
If you upload files, you are responsible for ensuring they are lawful to process and free of prohibited malicious content.
You may not use the service to violate law, abuse the service, attempt unauthorized access, distribute malware, or infringe third-party rights.
API keys are for programmatic access and should be kept secure.