The version Never Manual shared between Slate and Studio, no longer in force since November 12, 2026, when each product got its own documents: nmslate.com/terms for Slate, nmstudio.app/terms for Studio.

Privacy Policy

Last updated: November 8, 2026

This policy explains what Never Manual (“we”) collects when you use nevermanual.cloud, the product sites nmslate.com and nmstudio.app, accounts.nevermanual.cloud, the apps Slate and Studio, and our API and MCP server, and what we do with it. Never Manual is a trading name of the individual entrepreneur identified in our Legal Notice, who is the controller of the personal data we decide how to use: your account, payments, security logs and what we need to stop abuse. Contact: [email protected].

What a workspace holds, and what its presets and runs touch, is decided by the workspace's owner, and we process it for them. For a business in the EU, the EEA, the UK or Switzerland this is set out in our Data Processing Agreement. If your data is in someone else's workspace, for example on a Cloud Phone's screen or in a post, ask that workspace's owner; if you ask us, we pass your request on to them.

What we collect

How we use it

To run the service, sign you in, keep it secure, stop abuse, reply to you and improve it. We do not sell your data and do not use it for advertising. We do not train AI models on your data.

AI and Cloud Phones

AI features run through kie.ai and OpenRouter. On OpenRouter we use only hosts that do not train on your data; which of them answers is OpenRouter's choice, and some keep requests for a while under their own terms, such as OpenAI for up to 30 days. For a business workspace under our Data Processing Agreement, AI features run only through OpenRouter, on routes that keep no prompts or outputs and only on the hosts that agreement names. Studio's API nodes run through kie.ai.

During a run or a showing on a Cloud Phone, what the phone shows and what the AI agent types go to the AI provider: frames of the screen, the text on it and in its fields, and the preset's text, fields and the account's Answers. They also stay in that run's history for 30 days. That includes a sign-in if your preset goes through one, and a code that appears on the screen.

When the phone marks a field as a password, its text is replaced with dots before it reaches the model or the run's history, what the agent typed into it is not repeated, and that screen is left out of the run's film and the final check. An app that does not mark its password field is not covered by this. A Password or 2FA field in a preset is filled in by our engine from the account's vault, and the model sees only a placeholder; the screen can still show the value if the app shows it.

Do not put passwords or codes in a preset's text, its fields or an account's Answers: they go to the model on every step of a run. While you use the live screen yourself and no run or showing is active, nothing on it goes to an AI model.

When you connect your own mail, we read the three newest letters to an account's address to find a sign-in code. If a simple rule finds no code, the letters go to OpenRouter.

Who else handles it

WhoWhat forWhat dataHow long they keep it
Clerk (US)Accounts and sign-inName, email, photo, sessions, workspace rolesWhile the account exists; up to 90 days after our contract with them ends
Cloudflare (US)Network, security, site analytics, email to our addresses, the tunnel to our physical phonesIP address, requests, content in transit, including a physical Cloud Phone's live screenAs long as it needs to serve the request
Hostinger (US)Our serversWhat our apps store: databases, files in progress, logsUntil we delete it; its weekly backups of the whole server, the last two
Bunny.net (Slovenia; storage in Germany)Storing and delivering media and run films; encrypted backups of the phones databaseFiles, run films, delivery logsUntil we delete them; run films 30 days
A cloud provider of GPU machinesRunning Studio tasksA task's inputs, results and workflowWhile the machine works for us; the provider's backup of a deleted machine up to 7 days
Sightengine (France; processing in the EU, Canada or the US)Checking images and video frames for nudityImages and video framesDeleted after the check
OpenAI (US)Checking Studio promptsThe text of a promptNot kept for this check
OpenRouter (US)Routing AI requests: the AI agent on Cloud Phones, captions, names and tags for files, finding a sign-in code in letters, the Pilot, Studio's prompt writerFrames and text of a Cloud Phone's screen, what the agent types, presets and their fields, images and textRequest metadata; prompts and outputs only where the host that answered keeps them
The hosts OpenRouter chooses, among them OpenAI, Microsoft Azure, Amazon Bedrock, Google, xAI, DeepInfra, Fireworks AI and Together AI (US)Running the AI modelsThe same, while the request runsNone of them trains on it; some keep requests for up to 30 days under their own terms. For a workspace under our Data Processing Agreement, only zero-retention routes, kept by none
kie.ai (US)AI features for workspaces not under our Data Processing Agreement: the AI agent on Cloud Phones, captions and names for files; API nodes in StudioFrames and text of a Cloud Phone's screen, what the agent types, images, text and promptsFiles 14 days, logs 2 months
Google Cloud (Netherlands, US)Virtual Cloud PhonesEverything on a virtual Cloud Phone: accounts, files, screenUntil the phone leaves your workspace; Google then deletes it within 180 days
Upload-Post (Spain)Posting through the API, when you connect itAccount tokens, posts, mediaTokens until the account is disconnected there or another account takes its place; logs 90 days; analytics 26 months
KeepzCard and crypto paymentsWhat you enter when you pay, and the payment itselfUnder its own policy
Resend (US)Support email and noticesEmail address, text, attachments30 days
TelegramSupport: our bot, and the chat where we read and answer messages from it, from support email and from the Support chat in our appsMessages, files, your Telegram name; from the Support chat, your name, email address, workspace and the page you wrote fromUntil deleted from the chat
Google (Gmail, US)A copy of every email sent to our addressesEmail address, text, attachmentsUntil we delete it
Hugging Face and CivitaiFetching the models your workflows useOur IP address and your workspace's key when a model needs one; never your filesUnder their own policies
Public blockchain nodes such as TronGrid and PublicNodeShowing a payment's confirmationsA transaction's IDUnder their own policies

Crypto payments go through BTCPay Server, which we run on our own servers. Physical Cloud Phones and the records of their runs are on our premises in Georgia. When you post, the content goes to the platform you chose, under its own policy. Services you connect with your own key, such as your mail provider, handle your data under your contract with them.

We report apparent child sexual abuse material to NCMEC and to the authorities, and give them the account, payment and log details they need. We answer other requests for your data when a court or a prosecutor orders it.

Outside your country

Your data is processed outside your country: in Georgia, where we are, in the United States and in the EU, by the providers listed above.

Cookies

We set only the cookies the service needs. There are no advertising or tracking cookies, so there is no cookie banner.

How long we keep it

When you delete

When you delete a workspace or your account, or ask us to, we erase its data from our systems within 30 days. Backups, support conversations and copies at our providers go on the schedules above. We keep payment records and records of breaches for as long as the law requires. What you already posted stays on the platform you posted it to. Before you delete, you can ask us for a copy of your data.

Our access

The person who runs the service has technical access to our servers and to the physical phones. We use it only to fix something you asked us to fix, to clean a device after it leaves your workspace, to keep the service running and secure, or to review a breach of our terms. Our tools record each time we open a Cloud Phone that is in your workspace or act in your workspace with our service key. Passwords in the vault are encrypted, and the key is on our server, so this is not end-to-end encryption.

Your rights

You can ask to see, correct or delete your data, get a copy of it, or object to how we use it: write to [email protected]. You can complain to the State Audit Office of Georgia or to the data protection authority where you live.

Changes

We post changes here, update the date above and keep past versions at nevermanual.cloud/terms/archive.