Subprocessors
The providers we send data to, and on what terms.
Last updated: November 9, 2026
Controller: Lightpost One Ltd (trading as Rool), Dublin, Ireland
Contact: contact@rool.dev
Rool is built on infrastructure and services we do not run ourselves. This page is the formal register of those providers: who they are, what they do for us, what data they receive, where they process it, and on what terms. Each provider does one job and receives only the data that job needs. Most act as our processors, handling data only on our instructions under a data processing agreement. Where a provider instead receives data under its own terms, its entry says so.
The privacy policy explains the same providers in plain language, and how data flows through Rool. This page is the reference version, and the one our data processing agreements point to.
We update this page and the change log at the bottom whenever we add, replace, or remove a provider.
Providers that run Rool
These providers are part of running Rool, so they are involved whenever you use it.
Hetzner (Finland)
Hosting of servers and storage, including the servers that deliver the app, receive connections and run sign-in
- Legal entity
- Hetzner Online GmbH, Germany
- Processing location
- Finland
- Data received
- All service data stored on those servers, and every connection and sign-in request as it is processed
- Role
- Processor, acting on our instructions
- Agreement
- Hetzner Data Processing Agreement (version 1.2), concluded in the customer account , in force since October 20, 2026
- Added
- September 29, 2026
Verda (Finland)
GPU hosting for Rool's own AI models
Planned. Not in use at the moment. Our own models currently run on ScanNet only. Verda stays listed so that we can move them back at short notice; a changelog entry will record when that happens.
- Legal entity
- DataCrunch Oy (trading as Verda), Finland
- Processing location
- Finland
- Data received
- Nothing is sent to Verda. When our models run on GPU servers it operates, your messages, attached images, and the text of files the AI reads pass through that hardware while our models process them.
- Role
- Processor, acting on our instructions
- Agreement
- Data Processing Terms in the Verda Terms and Conditions (section 10), accepted at account creation , in force since December 25, 2025
- Terms
- Infrastructure only. We deploy and run the models ourselves on isolated instances. Nothing is used for training.
- Added
- September 29, 2026
ScanNet (Denmark)
GPU hosting for Rool's own AI models
- Legal entity
- A/S ScanNet, Denmark
- Processing location
- Denmark
- Data received
- Nothing is sent to ScanNet. Our models run on GPU servers it operates, so your messages, attached images, and the text of files the AI reads pass through that hardware while our models process them.
- Role
- Processor, acting on our instructions
- Agreement
- Data processing agreement on the Danish Data Protection Agency standard terms (version 2.1), signed , in force since October 21, 2026
- Terms
- Infrastructure only. We deploy and run the models ourselves on isolated instances. Nothing is used for training.
- Added
- October 21, 2026
Google Cloud
Database and encrypted machine restore points
- Legal entity
- Google Cloud EMEA Limited, Ireland
- Processing location
- Finland (europe-north1)
- Data received
- Account data, sign-in records, and usage records in the database (Cloud SQL), and encrypted restore points of every machine (Cloud Storage).
- Role
- Processor, acting on our instructions
- Agreement
- Cloud Data Processing Addendum, incorporated into the Google Cloud Platform Terms of Service , in force since March 23, 2025
- Added
- September 29, 2026
Stripe
Payments
- Legal entity
- Stripe Payments Europe, Limited, Ireland
- Processing location
- EU and United States
- Data received
- Billing details when you buy a plan or credits
- Role
- Processor, acting on our instructions
- Agreement
- Stripe Data Processing Agreement, incorporated into the Stripe Services Agreement , in force since January 27, 2026
- Terms
- Acts as our processor for billing. For fraud prevention and anti-money-laundering checks it acts as an independent controller under its own privacy policy. Certified under the EU-US Data Privacy Framework.
- Added
- September 29, 2026
Apple
Sign in with Apple and iOS in-app purchases
- Legal entity
- Apple Distribution International Ltd., Ireland
- Processing location
- EU and United States
- Data received
- Sign-in identifiers and purchase records, when you use them
- Role
- Independent provider, under its own terms
- Terms
- Your Apple Account and App Store purchases are Apple's own services, handled under Apple's privacy policy. Apple is the merchant for purchases in the iOS app. We receive a sign-in identifier and a purchase confirmation, nothing more. The Apple Developer Program License Agreement contains no processor terms, so Apple is not our processor.
- Added
- September 29, 2026
Google (Google Account)
Sign-in with a Google Account
- Legal entity
- Google Ireland Limited, Ireland
- Processing location
- EU and United States
- Data received
- Sign-in identifiers, when you use it
- Role
- Independent provider, under its own terms
- Terms
- Your Google Account is Google's own service, handled under Google's privacy policy. We receive your name, email address, and an account identifier, nothing more. Google acts under its own terms here, not as our processor.
- Added
- November 8, 2026
Resend
Email sending and receiving
- Legal entity
- Plus Five Five, Inc., United States
- Processing location
- United States (email is sent from Ireland, stored in the United States)
- Data received
- Email Rool sends you, and email your machine sends and receives, including its content
- Role
- Processor, acting on our instructions
- Agreement
- Resend Data Processing Addendum (updated 31 December 2025), binding on acceptance of the Resend terms of service , in force since May 8, 2026
- Terms
- Stores email, including its content, under its own retention terms. Certified under the EU-US Data Privacy Framework.
- Added
- September 29, 2026
Speechmatics
Speech to text
- Legal entity
- Cantab Research Limited (trading as Speechmatics), United Kingdom
- Processing location
- EU (Speechmatics EU region)
- Data received
- Microphone audio, sent directly from your device
- Role
- Processor, acting on our instructions
- Agreement
- Data processing terms in the Speechmatics Terms of Service (section 7), accepted at account creation. Model training is not enabled , in force since August 24, 2026
- Added
- September 29, 2026
Matomo
Website visit measurement for rool.dev
- Legal entity
- InnoCraft Ltd (Matomo Cloud), New Zealand
- Processing location
- Germany, with backups in Ireland
- Data received
- Page views and technical data, without cookies
- Role
- Processor, acting on our instructions
- Agreement
- Matomo Cloud Data Processing Agreement (version 3.0), part of the Matomo Cloud Terms of Service , in force since February 19, 2026
- Added
- September 29, 2026
Google Workspace
Support email
- Legal entity
- Google Cloud EMEA Limited, Ireland
- Processing location
- EU (data at rest); processing may be outside the EU/EEA
- Data received
- Email you send to contact@rool.dev, and our replies
- Role
- Processor, acting on our instructions
- Agreement
- Cloud Data Processing Addendum to the Google Workspace Agreement, accepted in the Admin console , in force since October 20, 2026
- Added
- September 29, 2026
Optional providers
These providers each power a specific feature and are only involved when you use it. Requests are sent from Rool’s servers under Rool’s account, not yours. Each provider can be turned off for an account under Settings, Data and Privacy, and the setting covers every machine that account owns. Your own machines follow your settings. A machine owned by a team follows that team’s settings, chosen by its admins, for everyone who works in it, including people from other accounts. Content you put in a team machine can therefore reach providers you have turned off for yourself.
TensorX (Ireland)
Backup AI models when Rool's own are unavailable or busy, and some advanced or experimental models
- Legal entity
- TensorX Ltd., Ireland
- Processing location
- Ireland and Finland
- Data received
- Messages, conversation history including participant names, account details given to the AI such as plan and approximate location, attached images, and the text of files the AI reads
- Role
- Processor, acting on our instructions
- Agreement
- TensorX Data Processing Agreement, incorporated into the TensorX Terms of Service , in force since September 8, 2026
- Terms
- May not use your data to train AI models. Keeps nothing after answering.
- Added
- September 29, 2026
Google Cloud AI (Vertex AI)
Image generation and editing
- Legal entity
- Google Cloud EMEA Limited, Ireland
- Processing location
- EU
- Data received
- The description of the image you ask for, and the image you ask to edit
- Role
- Processor, acting on our instructions
- Agreement
- Cloud Data Processing Addendum, incorporated into the Google Cloud Platform Terms of Service , in force since March 23, 2025
- Terms
- May not use your data to train AI models.
- Added
- September 29, 2026
Brave Software (Brave Search)
Web, image, and video search
- Legal entity
- Brave Software, Inc., United States
- Processing location
- United States
- Data received
- The search query, written by you or by the AI on your behalf
- Role
- Independent provider, under its own terms
- Terms
- Keeps queries for up to 90 days. Brave's data processing addendum excludes search query data, so no agreement covers queries and Brave does not act as our processor for them. We send each query with no identifier, so in Brave's hands it cannot be linked to the person who sent it. On that basis we treat queries sent to Brave as not being a transfer of personal data.
- Added
- September 29, 2026
SerpApi
Google Scholar search
- Legal entity
- SerpApi, LLC, United States
- Processing location
- United States
- Data received
- The search query
- Role
- Processor, acting on our instructions
- Terms
- Keeps searches for 31 days. Offers Standard Contractual Clauses for transfers.
- Added
- September 29, 2026
Jina AI (Jina Reader)
Rendering web pages for the AI to read
- Legal entity
- Jina AI GmbH, Germany
- Processing location
- Not stated by Jina; requests pass through a global network and may be processed outside the EU/EEA
- Data received
- The address of the page
- Role
- Processor, acting on our instructions
- Agreement
- Elastic Customer Data Processing Addendum (v100623.0), applying to Jina AI services since the Elastic acquisition , in force since March 11, 2026
- Terms
- Does not train on requests. May keep the addresses it receives under its own terms. Owned by Elastic N.V. since October 2025; processing is governed by the Elastic Customer DPA.
- Added
- September 29, 2026
Transfers outside the EU/EEA
Your machines, files, conversations, and account data are stored in the European Union (Finland). Where a provider above processes or stores data outside the EU/EEA on our behalf, the transfer is covered by the European Commission's Standard Contractual Clauses in our agreement with that provider, or by the EU-US Data Privacy Framework where the provider is certified under it. Brave receives search queries under its own terms, not on our behalf, and no agreement covers them. We send each query with no identifier, so in Brave's hands it cannot be linked to the person who sent it, and on that basis we treat queries sent to Brave as not being a transfer of personal data. You can ask for a copy of the safeguards that apply to a particular provider at contact@rool.dev.
Change log
- November 9, 2026: The Rool app is now delivered from our own servers at Hetzner instead of Firebase Hosting. Google Cloud holds only the database and the encrypted machine restore points, all in Finland.
- November 8, 2026: Verda is not in use at the moment: our own models run on ScanNet only. The entry stays in the register, marked as planned, so that we can move them back at short notice, and it is left out of the privacy policy until then.
- November 8, 2026: Sign-in moved from Google Identity Platform to our own servers at Hetzner, with the records in our database in Finland, so Google Cloud no longer holds data outside the EU/EEA. Sign-in with a Google Account is now listed on its own, like Sign in with Apple.
- October 23, 2026: ScanNet started processing data: our own AI models now run on its GPU servers in Denmark.
- October 21, 2026: ScanNet (Denmark) listed ahead of use as a second GPU host for our own models, on the same terms as Verda. A further entry will record when it starts.
- September 29, 2026: Register published, listing the providers already named in the privacy policy.
Contact
Questions about this register: contact@rool.dev