Privacy Policy
This policy explains what Never Manual (“we”) collects when you use Studio: the site nmstudio.app, the app at studio.nevermanual.cloud, the account at accounts.nevermanual.cloud you sign in with, and our API and MCP server as far as you use them for Studio. 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 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: media, workflows and their results, keys for the services you connect.
- 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 Studio and on the Billing page. With a message from the chat we also see your name, email address, workspace and the page you wrote from.
- Payments: for each top-up, 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 in Studio
Studio's API nodes run through kie.ai, and its prompt writer through OpenRouter, on 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. Prompts are checked by OpenAI's moderation before a task runs; that check keeps none of it.
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 | IP address, requests, content in transit | 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 | Files, delivery logs | Until we delete them |
| A cloud provider of GPU machines | Running Studio tasks | A task's inputs, results and workflow | While 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 nudity | Images and video frames | Deleted after the check |
| OpenAI (US) | Checking Studio prompts | The text of a prompt | Not kept for this check |
| OpenRouter (US) | Routing AI requests: Studio's prompt writer | The text and images you give it | 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 |
| kie.ai (US) | API nodes in Studio | Images, text and prompts a node sends | Files 14 days, logs 2 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 |
| Hugging Face and Civitai | Fetching the models your workflows use | Our IP address and your workspace's key when a model needs one; never your files | Under their own policies |
| 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. Services you connect with your own key, such as Hugging Face or Civitai, 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.
How long we keep it
- Account and workspace data: while the account or workspace exists.
- A task and its settings until you delete it, files you upload for 7 days unless you pin them, results until Media takes them.
- Logs: 90 days.
- Backups: daily ones 14 days, and our host's weekly server backups, the last two.
- Support conversations: 24 months after the last message.
- 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.
Our access
The person who runs the service has technical access to our servers. We use it only to fix something you asked us to fix, to keep the service running and secure, or to review a breach of our terms. Our tools record each time we act in your workspace with our service key.
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.