Neurova Studio privacy policy

Your agency's records are encrypted on your own devices. Our relay stores and forwards ciphertext and cannot read them.

Last updated 19 November 2026

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

Neurova AI is a sole proprietorship (eenmanszaak) registered in the Netherlands:

What stays on your devices

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 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:

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:

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

People who use your booking or unsubscribe page

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

We don't sell data, show ads, or use your data to train any AI model.

How long we keep it

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.