Data Processing Agreement
This Data Processing Agreement (“DPA”) is between the business that owns a Never Manual workspace (“you”) and Never Manual (“we”), the individual entrepreneur identified in our Legal Notice. It is for a business in the EU, the EEA, the UK or Switzerland: it applies to its workspace once we have agreed terms with it and one of its admins has accepted it in the workspace's settings on behalf of that business. We record who accepted it, which version and when. It forms part of our Terms of Service.
What it covers
The personal data we process for you in Slate, including Media, phones, the AI agent, presets, schedules and posting.
Who decides
You are the controller of what you put in your workspace and of what your presets and runs touch, including anything that appears on a phone's screen. We process it for you, on your instructions. You are responsible for the legal basis and for telling the people concerned, including people whose data appears in the apps and websites you automate. If you are yourself a processor for a client of yours, we are your sub-processor, and you pass your client's instructions on to us.
We are the controller only of your account, payments, security logs and what we need to stop abuse; the Privacy Policy covers that. Roles follow what actually happens: if you plan to use the service in a way this DPA does not describe, tell us first.
Your instructions
Your instructions are our Terms and this DPA, your settings, your presets and schedules, and what you ask us in writing. We process your data only on them, unless a law we are subject to requires otherwise; then we tell you first, unless that law forbids it. If we think an instruction breaks data protection law, we tell you.
What the AI agent sees
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.
For your workspace, AI features run through OpenRouter, only on routes that keep no prompts or outputs and only on the hosts in Annex 3. That rests on what those hosts state to OpenRouter. We do not train AI models on your data.
Confidentiality and our access
The service is run by one person, the individual entrepreneur in our Legal Notice, who keeps your data confidential. Anyone we later give access to your data is bound to confidentiality first.
That person has technical access to our servers and to the physical phones, and uses 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. Passwords in the vault are encrypted, and the key is on our server, so this is not end-to-end encryption.
Security
We keep at least the measures in Annex 2. We may change them, but not to ones that protect your data less. We hold no security certifications.
Sub-processors
You allow us to use the sub-processors in Annex 3. Each has a contract with us that protects your data in substance as this DPA does. We email the workspace owner at least 10 days before we add or replace one. If you object on reasonable grounds and we cannot resolve it, you can leave and get the unused part of your plan and packs back. If one has to be replaced at once to keep the service running or safe, we tell you right after. Services you connect with your own key, such as your mail provider, are yours, not our sub-processors.
Requests from people and help we give
If someone asks us about their data in your workspace, we pass the request to you and do not answer it ourselves unless you ask us to. We help you answer such requests, assess risks and consult authorities, as far as we reasonably can with what we hold. This help is included, unless it takes a lot of work; then we agree a fee with you first.
Breaches
We tell you of a personal data breach affecting your data without undue delay and no later than 72 hours after we learn of it, with what we know at the time, and send the rest as we learn it. We tell the workspace owner by email.
Audits
You can ask for documents and written answers about how we protect your data at any time. You can also audit once a year on 30 days' notice, at your cost, or more often after a breach or when an authority requires it.
When it ends
When you delete the workspace, or ask us to, we erase your data from our systems within 30 days. Before that you can ask us for a copy at [email protected]. Backups age out: daily ones within 14 days, monthly copies of the phones database within 3 months, our host's weekly server backups within 2 weeks. Copies at sub-processors go on the schedules in Annex 3. We keep what the law requires us to keep, such as payment records.
Liability
We answer for our sub-processors as we do for ourselves, within the limit of liability in our Terms. That limit does not apply to the Standard Contractual Clauses, to claims by the people the data is about, or to anything the law does not let us limit. You answer for what you choose to show the agent and for the decision to run a preset on it.
Transfers
We are established in Georgia, which the European Commission has not found to protect personal data adequately, and our sub-processors are where Annex 3 says. Where you transfer personal data to us from the European Economic Area, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914 form part of this DPA: Module Two where you are a controller, Module Three where you are a processor. You are the data exporter and we are the data importer. Clause 7 applies. In Clause 9, Option 2 applies, with the notice in this DPA. The optional wording in Clause 11 does not apply. In Clause 13, the competent authority is the one where you are established, or, if you are not established in the EU, the one where your representative is or, without one, where the people concerned are. In Clauses 17 and 18, the law and the courts of the Netherlands apply. Annexes I to III of the Clauses are filled in by the parties above and by Annexes 1 to 3 below.
For data from Switzerland, the same Clauses apply with these changes: the Swiss Federal Act on Data Protection takes the place of the GDPR, the Federal Data Protection and Information Commissioner is the competent authority, and “Member State” includes Switzerland, so that people there can bring claims where they live. For data from the United Kingdom, the International Data Transfer Addendum to the EU Standard Contractual Clauses issued by the Information Commissioner applies; its Tables 1 to 3 are filled in by this DPA, and either party may end it as its Table 4 allows.
We pass data on to our sub-processors only under a transfer tool the law allows. If any of these tools is replaced or found invalid, we offer its successor.
United States
Where US state privacy laws apply, we act as your service provider or processor: we do not sell or share your personal data and use it only to provide the service to you.
Order and changes
If the Standard Contractual Clauses, this DPA and our Terms disagree on personal data, the Clauses win, then this DPA. We may change this DPA for good reason, such as a new law, a new sub-processor or a new feature. We email workspace owners at least 14 days before an important change, and a change does not lower the protection of your data unless the law requires it. Past versions stay at nmslate.com/terms/archive. Questions: [email protected].
Annex 1: the processing
- People concerned: your team; the people whose social and app accounts you manage on phones; people whose data appears in your media and posts or in the apps and websites your presets use, such as followers, commenters and people shown in photos and videos; senders of the letters searched for a sign-in code when you connect your mail.
- Data: sign-in details you store for accounts (logins, and encrypted passwords and 2FA seeds); frames and text of a phone's screen and what the agent typed during runs and showings; preset text, field values and Answers; media files, their names and captions; posts and schedules; run history; contact details and messages that appear on a phone.
- Special categories: we do not look for them, but a screen or a file can show them, for example health or a person's sex life. If yours include them, you are responsible for having a valid basis.
- What we do with it: store it, show it to your team, operate apps on phones with an AI agent, write captions and names with AI, check files for nudity, and post to the platforms you choose.
- Purpose: to provide the service as you set it up.
- How long: while the workspace exists, then as in “When it ends”; run records 30 days.
- How often: continuously.
Annex 2: security measures
- Our sites and apps are served over HTTPS only, and our servers and the phones reach each other through encrypted tunnels.
- Passwords, 2FA seeds and vault notes are encrypted one by one with AES-256-GCM. An account's login and vault are shown only to the account's executor, managers and owners.
- Sign-in goes through Clerk. Each workspace has roles, and its data is kept apart by workspace in our databases and storage. Files are served by signed links that expire.
- During runs, password fields are masked and Password and 2FA fields are filled in by our engine, as described above. AI features use zero-retention routes only; the text of presets is checked by OpenAI's moderation, which keeps none of it for that check.
- Real phones are on our premises in Georgia, each used by one workspace at a time, and reset to factory settings before another workspace gets one. Cloud phones run on separate machines that reach only the internet, not each other or our network.
- Run records are deleted after 30 days and logs after 90 days. Backups of the phones database are encrypted before they leave the server.
- Our tools record each time we open a phone that is in your workspace.
Annex 3: sub-processors
| Who | What for | What data | How long they keep it |
|---|---|---|---|
| Hostinger (servers in the US) | Our servers | What our apps store about your workspace | Until we delete it; its weekly backups of the whole server, the last two |
| Cloudflare (US) | Network, security, the tunnel to our physical phones | Requests and content in transit, including a real phone's live screen | As long as it needs to serve the request |
| Clerk (US) | Sign-in and workspace membership | Names, email addresses and roles of your team | While the account exists |
| Bunny.net (Slovenia; storage in Germany, delivery worldwide) | Storing and delivering media and run films; encrypted backups of the phones database | Media files, run films, backups | Until we delete them; run films 30 days; monthly backups 3 months |
| Google Cloud (the Netherlands, US) | Cloud phones | Everything on a cloud phone | Until the phone leaves your workspace; Google then deletes it within 180 days |
| OpenRouter (US) | Routing AI requests | Frames and text of a phone's screen, what the agent types, presets, fields and Answers, images and text for captions and names, letters searched for a sign-in code | Prompts and outputs not kept; request metadata kept |
| Microsoft Azure, Google Cloud Vertex AI, xAI, Fireworks AI, DeepInfra, Together AI (US), through OpenRouter | Running the AI models | The same, while the request runs | Not kept, on their zero-retention routes |
| 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 for content that is not allowed | The text of a preset | Not kept for this check |
| Upload-Post (Spain; storage in Germany) | 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 |