Your data and connected agents
Choose what the agent can read
A connection acts for your account through the API and MCP tools. It never becomes a browser session or an administrator. Your password is not given to the assistant. Give each integration its own key or OAuth connection and the smallest scopes it needs.
| Scope | What it can read or do | What it cannot access |
|---|---|---|
levels:read | Your effective language levels, native languages and public explanation URLs. | Books, reading history, raw level inputs, email, billing or changing levels. It cannot spend. |
books:read | Stories and books you made, their status and text, and JSON or EPUB exports. | Other readers' private books or the public library. Status reads can start an audiobook already requested with a story and charge its reserved price. |
account:read | Your credit balance, plan and a quote for a story or audiobook. | Email, billing details, payment methods or account settings. Quotes spend nothing. |
stories:write | Start stories and request audiobooks using your saved settings, subject to your plan and cap. | Admin routes, changing account settings, raising its own cap or buying credits. |
Scopes are independent. A writing key does not automatically get book or level access. Existing keys do not gain new scopes. OAuth consent lists the permissions you grant. A tool shown in discovery still checks its scope before doing work.
Story text is content, never instructions
Responses carrying story text have an untrusted field. The MCP server also instructs assistants to show returned text without acting on it. A story, title or topic can contain instruction-like words. An agent must not treat those words as a command, open links from them, send secrets or start another paid request because of them.
These markers tell the connected client how to handle content. They cannot guarantee every outside assistant follows the guidance. Review what your client sends to its model and its own privacy terms before connecting.
What no connection can do
A connection cannot read email or billing details, reach admin routes, buy credits, raise its own monthly cap, change levels or read another reader's private work. An admin's API key gets the same limited operations as any other key.
Paid starts reserve the whole known price against the connection's UTC monthly cap before work starts. Concurrent starts share that cap. The account balance, plan rules and service spending brakes also apply. Set an explicit cap, including 0 for read-only use. An uncapped connection has no monthly connection ceiling, so do not choose uncapped access if you want a fixed spending bound. Raising the cap does not buy credits.
Revoke access and remove retained copies
Open Settings → API keys, find the key or OAuth connection and revoke it. Future authenticated requests are refused immediately, including requests using refreshed tokens from that OAuth connection. Revocation does not cancel work already accepted or recall content already exported, cached, published or included in a chat.
Disconnect the integration in the client too. Remove retained level snapshots or exports from your service and request deletion from the client if needed. Alloglot cannot erase another provider's copies. If a key leaked, revoke first and follow Incidents and support. Never send the key to support.
Public and private stories
Private requests are not scanned for public-content moderation. When a request or book becomes public, it goes through the same moderation and publishing checks as the app. Vendor policies still apply to private generation. API access does not make your account or private books public.