This policy covers the Neurova Studio apps for Mac, iPhone, iPad and Apple Watch, the relay they
work with at studio-api.neurova-ai.com, and the booking and unsubscribe pages that relay serves.
Our website has its own privacy statement.
In short: your agency's records are encrypted on your own devices with keys
only your agency holds. Our relay in the EU stores and forwards that ciphertext and cannot read
it. Your Google or Microsoft mailbox, your Claude key and your Google Places key are used straight
from your device and never pass through us. The apps have no analytics, ads or tracking.
Who is responsible for what
- Your agency's data (clients, contacts, requests, projects, tasks, time,
notes, files, agent runs, and the companies and people you find and contact with the client
finder): your agency is the controller under the GDPR. Neurova AI is a processor only for the
relay, which stores and forwards these data for you in encrypted form, and holds the sealed
bookings and unsubscribe records described below.
- The data we need to run the relay (which devices belong to your agency, team
roles, your sign-in settings): Neurova AI is the controller, as described below.
- Your own accounts at Google, Microsoft, Anthropic and the other services you
connect: the app talks to them directly from your device, under your agency's agreement with
each of them. Neurova AI is not a party to that.
Neurova AI is a sole proprietorship (eenmanszaak) registered in the Netherlands:
- Neurova AI, owner Andreas Chitos
- Heideveldstraat 6, Eindhoven, the Netherlands
- Chamber of Commerce (KvK): 94328900
- Email: support@neurova-ai.com
What stays on your devices
- All your records. Everything you keep in Neurova Studio is stored in an
encrypted database on your Mac, iPhone or iPad. Each record is encrypted (AES-256-GCM) with
the key of the client or project it belongs to, and keys are given only to the people in
your agency whose role needs them. A freelancer receives only the keys of their assigned
projects.
- Keys and secrets. Encryption keys, the sign-in tokens for your mailbox, and
the API keys and tokens you add (Claude, Google Places, GitHub, GitLab, Cloudflare, Vercel,
Supabase) are kept in the Keychain on your device. Project secrets in the workspace kit stay
in that Mac's Keychain and are never synced.
- Coding agents. Claude Code, Codex, Cursor, Copilot CLI and Gemini CLI report
their runs to the app over a connection on your own Mac (127.0.0.1), protected by a token.
Token usage is read from the agents' own files on your Mac. The app's MCP server also listens
only on your Mac.
- Notifications are made on your device after a sync. No push service is used,
so nothing readable passes Apple's servers. The Watch gets its information from your
iPhone.
What our relay holds
Your devices send every change to the relay already encrypted. The relay can read only what it
needs to do its work:
- the public keys of your agency's devices, and when they were added or removed;
- team members' roles and public keys, and which keys each person holds, in encrypted form
(never the keys themselves);
- sequence numbers, sizes and times of the encrypted changes, and short-lived pairing codes
(valid for ten minutes) for adding a device;
- if your agency uses Google Workspace sign-in: the settings you entered, and per person a
scrambled (SHA-256 hashed) form of their account ID at Google;
- if you use the client finder's email: the SHA-256 hashes of addresses that
used the unsubscribe link. The app computes the hash, so the relay never sees the address;
your devices pull the hashes into your do-not-contact list;
- if you publish a booking page: its address, title, introduction, meeting length, time zone
and public key, and your free start times (times only, no calendar details),
with which ones are taken;
- sealed booking requests: a booking is encrypted in the visitor's browser to
your agency's key. The relay keeps it only until your Mac picks it up, then deletes it. It
can see the time slot that was booked, not who booked it.
The relay runs on Cloudflare Workers. Each agency has its own Durable Object, created in the EU
jurisdiction, which holds its encrypted changes, files and the items above. Pairing codes and
booking page addresses are kept in a Cloudflare D1 database in the EU. The relay does not log
request bodies.
Google user data
When you connect a Google Workspace mailbox in Settings, Neurova Studio asks Google for these
permissions, and uses them only as described:
https://www.googleapis.com/auth/gmail.send: to send the emails you write or
schedule, from your own address. The app cannot read, search or delete your mail.
https://www.googleapis.com/auth/calendar.freebusy: to read when your calendar is
busy, so the app can work out the free times for your booking page. It sees busy periods,
not what the events are.
https://www.googleapis.com/auth/calendar.events: to add a booked meeting to your
calendar.
openid and email: to know which account you connected.
The sign-in happens in the system's own sign-in window. The tokens Google returns are kept in
your Mac's Keychain and sent only to Google. Google user data is not sent to Neurova's servers:
the only thing that leaves your Mac for the relay is the list of free start times your Mac works
out from the busy periods, so visitors to your booking page can choose one. We do not use Google
user data for advertising, we do not sell it, and we do not use it to train AI models, ours or
anyone else's. Nobody at Neurova AI can read it.
Neurova Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect the mailbox in Settings at any time, which deletes the tokens from your
Keychain, and remove the app's access in your Google Account under Security.
Microsoft data
When you connect a Microsoft 365 mailbox, Neurova Studio asks Microsoft for these permissions
through Microsoft Graph:
Mail.Send: to send the emails you write or schedule, from your own address. The
app does not read your mail.
Calendars.ReadWrite: to read the times of events in your calendar, so the app
can work out the free times for your booking page, and to add booked meetings. Only the
times and whether you are shown as busy are used.
offline_access: to stay connected without asking you to sign in again.
openid and email: to know which account you connected.
Microsoft data is handled exactly like Google data above: tokens stay in your Mac's Keychain
and go only to Microsoft, nothing is sent to Neurova's servers except the free start times for
your booking page, and the data is never used for advertising, sold or used to train AI models.
You can disconnect in Settings, and remove access in your Microsoft account.
Claude, Google Places and other sources
- Claude (Anthropic). Company search, research, fit scores and market briefs
use your agency's own Claude API key. The app calls Anthropic directly from your device; the
requests don't pass through us, and Anthropic handles them under your agency's own
agreement with Anthropic.
- Google Places. Searches use your agency's own Google Places key, directly
from your device. As Google's terms require, Neurova Studio stores only the Google place ID of
a result; names, phone numbers and websites are read live when you look at it.
- OpenStreetMap. Area searches go from your device to the public Nominatim and
Overpass services.
- Company websites. The app reads a company's own homepage and one contact
page for what it publishes, such as its name, phone numbers and business email addresses.
- Code and deploy services (GitHub, GitLab, Cloudflare, Vercel, Supabase): read
with your own tokens, directly from your device.
People who use your booking or unsubscribe page
- Booking page. A visitor chooses a time and enters their name and email
address, and if they like their company, phone number and a short note. Before anything is
sent, their browser encrypts these details to your agency's key, so our relay cannot read
them. Your Mac picks up the booking, decrypts it, files it in your client finder and adds the
meeting to your calendar. The agency that owns the page is responsible for these data.
- Anti-spam. The booking page uses Cloudflare Turnstile to check that a visitor
is not a bot. Turnstile receives technical data about the visit, such as the IP address and
browser, under Cloudflare's
Turnstile privacy policy. The pages use no other third-party scripts, and no cookies of
our own.
- Unsubscribe page. Every email sent through the client finder carries a link
to unsubscribe in one click. Using it stores only the hash described above, and the sender's
devices add the address to their do-not-contact list.
Contact rules
Before each call or email, the app checks the contact rules of the company's country, for all
27 EU countries, and blocks or warns. These rules are a safety net, not legal advice. The agency
decides whom it contacts and on what basis, and remains responsible for it.
Who else receives data
- Cloudflare hosts the relay, its storage and the Turnstile check, with storage
in the EU jurisdiction.
- Apple delivers the apps. The apps send it no data of yours beyond what the App
Store itself needs.
We don't sell data, show ads, or use your data to train any AI model.
How long we keep it
- Encrypted changes: until your devices replace them with newer ones and compact the change
log, or a record is deleted.
- Sealed bookings: until your Mac has picked them up.
- Pairing codes: ten minutes.
- Unsubscribe hashes: kept, so that the address stays on your do-not-contact list.
- The records on your own devices stay yours, and your agency decides how long to keep them.
Security
Records are encrypted on the devices, every device signs its requests to the relay, and
devices are added only by pairing with a device you already have, confirmed with a safety number
or QR code. A lost device can be removed from another one, and the keys are renewed.
Your rights
For the data we hold as controller, you can ask us for access, correction or deletion, or
object, at support@neurova-ai.com. If your details are
held by an agency that uses Neurova Studio, for example because you booked a meeting or received an
email from them, please contact that agency: we cannot read those data, and we help the agency
where we can. You can also complain to the Dutch Autoriteit Persoonsgegevens or the data
protection authority in your own country.
Last updated 19 November 2026.