Legal
Privacy Policy
Last updated: 30 September 2026
1. Who we are
Vonzl is a product of Cromozo Innovations Limited ("Cromozo", "we", "us"), a company registered in England and Wales (company number 15668893), registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. For the purposes of UK GDPR and the Data Protection Act 2018, Cromozo Innovations Limited is the data controller for the account, firm, and usage data described in this policy.
Questions about this policy or your data can be sent to privacy@vonzl.com.
2. What we collect
Account and profile data. Your email address (required); a password (if you don't sign in with Google) stored only as a salted hash, never in plain text; and, if you choose to fill them in, your name, title, role at your firm, company name, country, and city. If you sign in with Google, we receive your email, Google account ID, and profile picture URL from Google — nothing else.
Firm and billing data. Your firm's name, which plan it's on, seat count, and subscription status. Payment details themselves are collected and held by Paddle, our payment provider — we never see or store your card details (see Section 5). The country on your profile is also used to show plan prices in your local currency.
Marketing consent. Whether you've agreed to receive product update emails, and when you last changed that preference — tracked separately from account/service emails (like email verification), which aren't marketing and aren't gated on this consent.
Usage telemetry. A closed, fixed set of structural events — for example, that a generation was requested, a folder was added, or a dictation session completed — each carrying only short, whitelisted fields like a word count, a playbook name, or which app you were dictating into. This is enforced technically, not just by policy: the system rejects any event type or field it doesn't already recognise, so it cannot be made to store a document snippet, a query, or any other free text, even by mistake or misuse.
What we deliberately don't collect here. The documents you index for Q&A, what you dictate, and what you type into Ask are not sent to or stored by our account/billing service at all — see Section 4 for exactly where that content does and doesn't go depending on your plan.
3. Why we process it, and our legal basis
We process account and firm data to provide the service you've signed up for and to fulfil our contract with you (UK GDPR Article 6(1)(b)) — creating your account, running your subscription, and keeping the app working. We process usage telemetry on the basis of our legitimate interest (Article 6(1)(f)) in understanding how the product is used and keeping it reliable — this processing is kept proportionate by the telemetry being deliberately content-free, as described in Section 2. Marketing emails are sent only with your consent (Article 6(1)(a)), which you can withdraw at any time from Settings or by emailing us — this won't affect transactional emails like billing receipts or the messages the app needs to send you to work (e.g. email verification).
4. How Vonzl processes your content
This section covers the documents, dictated audio, and questions you actually work with inside the app — distinct from the account data in Section 2, and processed differently depending on your plan:
- Document indexing for Q&A happens entirely on your device. The files you point Vonzl at are read, chunked, and embedded locally, and stored in a local database — we never receive them.
- AI drafting, summarising, and Q&A sends your prompt, and any document excerpts retrieved locally to answer it, to whichever engine is active for your plan: our cloud AI provider (AWS Bedrock) for Cloud plans, or hardware you run yourself for Local Appliance plans, which we have no access to. We access Bedrock through our AWS account in London (eu-west-2), but the specific AWS server that actually handles a given request may be elsewhere — the AI model we currently use is only available to us via AWS's cross-region routing, not a UK-only option (see Section 6). We don't log this prompt/excerpt content by default; a firm can opt in to logging it for support/debugging purposes, and only then is it retained.
- Dictation audio is transcribed on-device by default (nothing leaves your machine). If you choose a cloud speech-to-text engine, audio is streamed to AWS Transcribe in London (eu-west-2) — a single-region service, not cross-region like Bedrock above — for that session only, and isn't retained by us afterwards. Local Appliance plans transcribe on your own hardware.
- Text-to-speech playback uses AWS Polly in London (eu-west-2, also single-region) on Cloud plans, or your own hardware on Local Appliance plans.
- On-screen context (email-aware replies, content commands) is read locally, using the accessibility permission you grant the app. It is only sent anywhere as part of a generation request you explicitly trigger — to the same engine as above for your plan — and the app shows you what's about to be sent before it goes. We don't store it.
- Voice commands are transcribed like dictation (on-device by default) and matched against your command list locally; the matched command runs on your machine. The heard phrase isn't stored by our services — usage telemetry records only that a command ran (see Section 2).
5. Who we share it with
We don't sell personal data. The processors below each handle a specific, limited slice of it:
- Amazon Web Services — cloud speech-to-text and text-to-speech, always processed in AWS's London (eu-west-2) region; AI generation, accessed via our AWS account in London but potentially processed on AWS servers elsewhere via cross-region routing (see Section 6). See Section 4 for exactly what's sent and when.
- Paddle (our payment provider and merchant of record) — receives your billing/payment details directly; we never handle your card number ourselves.
- Loops (lifecycle and marketing email) — receives your email address and, where relevant, a short, fixed set of structural signals like "hasn't used a playbook yet" or "day 3 since signup" — never document content or free text.
- Google — only if you choose to sign in with Google, to authenticate you and provide your profile picture.
- Google Analytics — only on this website, and only if you accept the cookie banner: receives standard analytics data (pages viewed, how you arrived, approximate location from your IP, device/browser type, and interactions like button clicks). It never receives anything from the desktop app. See Section 9.
We may also disclose data where required by law.
6. International transfers
Cromozo Innovations Limited is based in the UK. Where a processor we use is based outside the UK or transfers data outside it, we only rely on a basis recognised as providing adequate protection under UK GDPR — such as an adequacy decision, or the UK International Data Transfer Agreement / Standard Contractual Clauses. This applies in particular to AI generation requests on Cloud plans (Section 4): we submit them through our AWS account in London, but AWS's own cross-region routing for the AI model we currently use may process the request on AWS infrastructure outside the UK — this transfer is covered under AWS's standard data processing terms, which incorporate the UK's Standard Contractual Clauses. Cloud speech-to-text and text-to-speech don't have this cross-region behaviour and stay within the UK. Website analytics data (Section 9), where you've consented to it, is processed by Google, which may transfer it outside the UK under Google's data-processing terms incorporating the UK's recognised transfer safeguards.
7. How long we keep it
If you delete your account or your firm's account from the app, it enters a 30-day grace period during which you can cancel the deletion, after which your account and personal data are permanently removed. If your firm has billing history — a plan was ever actually chosen — a minimal, anonymised billing record is kept afterwards rather than fully erased, as UK tax law requires invoice records to be retained for 6 years. We otherwise keep account and usage data for as long as your account is active.
8. Your rights
Under UK GDPR you have the right to:
- ask us what personal data we hold about you, and get a copy of it (right of access) — available self-service in the app, including your account details and full usage/audit history;
- ask us to correct inaccurate data (right to rectification) — most profile fields are editable directly in the app;
- ask us to delete your data (right to erasure) — self-service, with the 30-day grace period described in Section 7;
- ask us to restrict how we use your data (right to restriction);
- receive your data in a portable format (right to data portability);
- object to our processing (right to object); and
- withdraw consent at any time, where consent is our legal basis (e.g. marketing emails).
To exercise any of these, use the relevant control in the app or email privacy@vonzl.com. If you're unhappy with how we've handled your data, you also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO).
10. Security
Passwords are never stored in plain text — only as a salted hash. Session and email-verification tokens are stored hashed, not as the raw value a link or client actually holds. If you pair with a Local Appliance, the desktop app pins that appliance's certificate on first connection so it can detect if it's later talking to a different device.
11. Children
Vonzl is a productivity product for individuals, teams, and businesses. It is not directed at, and we do not knowingly collect data from, anyone under 18.
12. Changes to this policy
We may update this policy as the product and our data practices develop. We'll update the "Last updated" date above when we do, and for material changes, the app will ask you to accept the new version the next time you sign in.
13. Contact us
Cromozo Innovations Limited — privacy@vonzl.com. See also our Terms of Service.