Reference

Security and privacy

Your agency's records are encrypted on your own devices, with keys that never reach us. This page explains what that means, and the few things our relay does see.

On this page

End-to-end encryption

Your agency is stored on your Mac, iPhone and iPad in an encrypted database (SQLCipher). Its key is kept in that device’s Keychain and never leaves it.

When sync is on, every change is encrypted on your device before it leaves (AES-256-GCM), with the key it belongs to: each client and each project has its own key, and there are a sales key and a billing key. Keys are passed from device to device sealed to that device’s own public key (X25519), and every device signs its requests (Ed25519). In a team, a person receives only the keys their role needs. Roles.

Neurova can’t read your clients, contacts, requests, projects, tasks, time, notes, files, quotes, invoices, partners, figures, the companies in your client finder, or your team’s names and emails.

The agency ledger

Who belongs to your agency is not decided by our relay. Your devices keep a ledger: statements such as “this device was added” or “this person is a developer”, each signed by the device that made it and chained to the one before. Every device checks the ledger and takes keys and roles only from it. The relay stores the ledger in order but can’t write to it.

When you add a device, the safety number ties the new device to the one that made the code. Compare it every time. Add a device.

What our relay can read

The relay runs on Cloudflare, at studio-api.neurova-ai.com and studio.neurova-ai.com. Each agency has its own storage, created in the EU jurisdiction; pairing codes and the addresses of booking, portal and pay pages are in a database in the EU. To work, the relay needs a few things in the clear:

What Why
Your devices’ public keys and when they were added or removed Devices sign every request
Team members’ roles and public keys, and which keys each person holds (never the keys themselves) So each device gets only what its person may read
Order, sizes and times of the encrypted changes To keep sync in order
Pairing codes, valid ten minutes To add a device
Your sign-in settings, if you use Google Workspace sign-in, and a hash of each person’s Google account ID To check sign-ins
Your booking page and free start times (times only) For the booking page
Your portal page, and your portal contacts’ email addresses and first names For the client portal and its emails. The portal
For quote answers and sign-offs: the time, internet address and browser of the answer, until your device picks it up As evidence of the answer
For pay and retainer links: the invoice number, amount, currency and payment status, and your Stripe account ID To take the payment through Stripe
Hashes of addresses that used an unsubscribe link For your do-not-contact list
Invoice numbering counters, and the day’s count of emails sent from the web app So two devices never issue the same number, and for the daily limit

Everything else (bookings, portal requests and replies, quotes, the names typed on quotes) is sealed in the visitor’s browser or on your devices, and the relay stores it only as ciphertext. The relay doesn’t log request bodies. Cloudflare keeps technical request logs (such as times, paths and errors) for a short time, to find faults.

Studio’s mail

Two kinds of email go through the relay and Cloudflare’s email service, from noreply@studio.neurova-ai.com:

  • Client portal emails: invitations, sign-in links and “something new” notices to your portal contacts.
  • Email from the web app: invoices, quote and retainer links and reminders you send from the browser. Recipient, subject, text and attachments pass through on their way out; the relay keeps nothing of them except a count of the day’s emails.

Email sent from the Mac (outreach, invoices, reminders) goes from your own Google Workspace or Microsoft 365 mailbox and doesn’t pass through us.

What your devices do directly

These go straight from your device to the service, with your agency’s own account, under your agency’s own agreement with it. Neurova sees none of it:

  • Claude (Anthropic): research, web search, fit scores and market briefs, with your API key.
  • Google Places, OpenStreetMap, and the websites of companies you add.
  • Google Workspace or Microsoft 365: sending email, busy times and calendar events. The only thing that reaches the relay is the list of free start times for your booking page.
  • Google Analytics, Search Console and Metricool, read-only, from an owner’s Mac.
  • Slack and Microsoft Teams: the generic chat notes, from an owner’s Mac.
  • GitHub, GitLab, Cloudflare, Vercel and Supabase, read-only.
  • VIES and the European Central Bank for VAT checks and exchange rates. From the web app these pass through the relay, because those services don’t accept requests from a web page; the relay keeps nothing of them.

Tokens and keys for all of these stay in the Keychain of the Mac that connected them, and never reach the browser.

Stripe handles your clients’ payments on your agency’s own Stripe account, under your agreement with Stripe. The relay creates the payment page and receives Stripe’s payment updates; your clients’ card or bank details go only to Stripe.

Meeting recordings

Meetings are recorded and transcribed on your Mac by macOS’s own speech recognition, only after you confirm everyone agreed. The audio is deleted after transcription unless you choose to keep it. Meeting notes.

The web app

The web app is a device of your agency like the others. Its keys are made in the browser and kept there as locked keys, which the page can use but not read out. Its copy of your agency is kept encrypted in the browser’s storage. The page loads no third-party scripts.

In Safari, the browser’s own storage can’t hold one kind of key locked, so the web app keeps that key encrypted under a locked key instead. The signing key stays locked in every browser.

Safari deletes a site’s data after seven days without a visit, unless the web app is added to the Dock or Home Screen. The browser then needs pairing again; nothing is lost.

Notifications

Notices are made on your devices after a sync. No push service is used, so nothing readable passes Apple’s servers. The Watch gets its information from your iPhone.

Where data is stored

  • On your devices, encrypted.
  • In encrypted form on Studio’s relay: Cloudflare, with storage in the EU jurisdiction.
  • Stripe, Google, Microsoft, Anthropic and the other services you connect hold what you give them under your own agreement with them.

Privacy documents

  • The Neurova Studio privacy policy covers the apps, the relay, the portal and Studio’s mail.
  • Your agency is the controller of its clients’ and contacts’ data; Neurova is a processor for the relay, the mail and the portal. A data processing agreement is being prepared; email support@neurova-ai.com for it.

Last updated 19 November 2026

Can't find it here? See Support and FAQ or email support@neurova-ai.com. We reply by email, usually within two working days.