Privacy Policy
This policy explains what Never Manual (“we”) collects when you use Slate: the site nmslate.com, the app at app.nmslate.com, the account at accounts.nevermanual.cloud you sign in with, and our API and MCP server as far as you use them for Slate. 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 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
- Your account: name, email address and photo, from the sign-up form, or from Google if you sign in with it.
- Your workspace: what you and your team put in: social accounts and their details, including passwords and 2FA codes you store, media, posts and schedules, presets, phones and their runs, keys for the services you connect.
- Runs on phones: frames of the screen, the text on it, what the AI agent typed and what it decided, step by step.
- Technical data: IP address, browser and device details, and logs of requests and errors, kept for security and to fix problems.
- Support: what you write to us by email, to our Telegram bot or in the Support chat in Slate. With a message from the chat we also see your name, email address, workspace and the page you wrote from.
- Payments: for each bill you pay, the amount, the method and the payment's reference. For crypto, also the network, the address and the transaction's ID; a transaction on a public blockchain can be seen by anyone, and we do not publish which transaction was yours.
- Site visits: our sites count visits with Cloudflare Web Analytics and with Umami, which runs on our own server: which pages were opened, where the visit came from, the country and device, how long it lasted and how far the page was scrolled. Neither sets cookies or identifies you.
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 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. The text of a preset is checked by OpenAI's moderation before it runs; that check keeps none of it.
During a run or a showing on a 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
| Who | What for | What data | How long they keep it |
|---|---|---|---|
| Clerk (US) | Accounts and sign-in | Name, email, photo, sessions, workspace roles | While 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 real phones | IP address, requests, content in transit, including a real phone's live screen | As long as it needs to serve the request |
| Hostinger (US) | Our servers | What our apps store: databases, files in progress, logs | Until 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 database | Files, run films, delivery logs | Until we delete them; run films 30 days |
| Sightengine (France; processing in the EU, Canada or the US) | Checking images and video frames for nudity | Images and video frames | Deleted after the check |
| OpenAI (US) | Checking the text of presets | The text of a preset | Not kept for this check |
| OpenRouter (US) | Routing AI requests: the AI agent on phones, captions, names and tags for files, finding a sign-in code in letters, the Pilot | Frames and text of a phone's screen, what the agent types, presets and their fields, images and text | Request 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 models | The same, while the request runs | None 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 phones, captions and names for files | Frames and text of a phone's screen, what the agent types, images and text | Files 14 days, logs 2 months |
| Google Cloud (Netherlands, US) | Cloud phones | Everything on a cloud phone: accounts, files, screen | Until the phone leaves your workspace; Google then deletes it within 180 days |
| Upload-Post (Spain) | Posting through the API, when you connect it | Account tokens, posts, media | Tokens until the account is disconnected there or another account takes its place; logs 90 days; analytics 26 months |
| Keepz | Card and crypto payments | What you enter when you pay, and the payment itself | Under its own policy |
| Resend (US) | Support email, notices and receipts | Email address, text, attachments | 30 days |
| Telegram | Support: our bot, and the chat where we read and answer messages from it, from support email and from the Support chat in our apps | Messages, files, your Telegram name; from the Support chat, your name, email address, workspace and the page you wrote from | Until deleted from the chat |
| Google (Gmail, US) | A copy of every email sent to our addresses | Email address, text, attachments | Until we delete it |
| Public blockchain nodes such as TronGrid and PublicNode | Showing a payment's confirmations | A transaction's ID | Under their own policies |
Crypto payments go through BTCPay Server, which we run on our own servers. Real 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.
- Sign-in cookies (Clerk) and security cookies (Cloudflare).
- nm_product: which product site you visited last, 6 months.
- nm_rail: whether the side menu is open, 1 year.
- nm_tz: your time zone, so that times show in it, 1 year.
- nm_restofme_connect: while you connect restof.me, 15 minutes.
- nm_share: a guest's access to a shared phone, 8 hours.
- farm_stream: access to a phone's live screen, 1 hour.
How long we keep it
- Account and workspace data: while the account or workspace exists.
- A run's frames, film, requests and logs: 30 days. The run's date and result stay in your history.
- The recording of a showing: until you accept it into a preset or cancel it.
- Logs: 90 days.
- Backups: daily ones 14 days, three monthly copies of the phones database, and our host's weekly server backups, the last two.
- Support conversations: 24 months after the last message.
- A cloud phone: until it leaves your workspace. A real one is reset to factory settings within 7 days after it leaves.
- Payment records: as long as tax law requires. Records of blocked accounts: 3 years after the account closes, to stop abuse and answer disputes. Records of a report to the authorities: as long as the law requires or the case is open.
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. Before you delete, you can ask us for a copy of your data.
What you already posted stays on the platform you posted it to.
Our access
The person who runs the service has technical access to our servers and to the real 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 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 the archive.