Legal
Subprocessors
Every third party that touches customer data, what it does, and what it sees. Four functions, no more than we need.
Last updated: 2026
This document is a draft for review. It has not been reviewed by qualified legal counsel and must be before RevVane accepts paying customers. Nothing on this page is legal advice. Bracketed values are placeholders and are not real details.
Vendor names are not yet published. We describe each subprocessor by function. A specific vendor appears here only once the data processing agreement with it is signed — naming a vendor we have not contracted with would be a claim we cannot support.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Speech-to-text provider [VENDOR — TBC] | Transcribing call recordings into text so calls can be labelled and searched. | Call audio fetched from your connected source, and the transcript produced from it. No account or billing data. | [REGION — TBC] |
| LLM routing provider [VENDOR — TBC] | Running the labelling pass: outcome, intent score, estimated job value, spam and voicemail flags, dispute recommendation. | Transcript text plus the minimum call metadata needed for context (duration, campaign, vertical). No recordings, no account credentials, no billing data. | [REGION — TBC] |
| Cloud hosting and infrastructure [VENDOR — TBC] | Running the application, database, object storage, queues and backups. Everything else sits on top of this. | All service data: account and workspace data, call metadata, transcripts, derived labels, encrypted source credentials, logs and backups. | [REGION — TBC] |
| Payment processor [VENDOR — TBC] | Subscription billing, invoices, tax handling and card processing. | Billing contact name and email, company details, plan and invoice history. Card details go to the processor directly and are never stored by us. No call data, no transcripts, no recordings. | [REGION — TBC] |
What is not on this list
- No analytics or advertising vendors. We run no third-party analytics, no ad pixels and no session replay. See the Cookie Policy.
- No data brokers, no resale. We do not sell customer data or share it for cross-context behavioural advertising.
- No transactional email provider yet. Invitations, password resets and digests will need one; it will be added to this table before it goes live, and it will receive email addresses and message content only — never call data.
- Connected sources are not subprocessors. Ringba, Google Search Console and any other source you connect are your vendors under your own agreements. We read from them on your instruction; we do not send them your RevVane data.
The no-training rule flows down
Customer call data is never used to train, fine-tune or evaluate models. That is not only our commitment — it is an instruction we pass to each AI subprocessor, and we select providers on the basis that they offer a no-training, zero-retention processing configuration. Where a provider's terms are recorded here, the specific contractual clause will be cited alongside the vendor name. Until then, treat the arrangement as not yet confirmed rather than assumed.
How each one is engaged
Before a subprocessor processes any customer data it must be under a written agreement with data protection terms no less protective than our Data Processing Addendum, including confidentiality, security measures, breach notification, deletion on termination and a valid transfer mechanism where data leaves the UK or EEA. We stay liable to you for what our subprocessors do.
How you will hear about changes
We give at least [NOTICE PERIOD — e.g. 30 DAYS] notice before adding or replacing a subprocessor. Notice goes to the notification address on your workspace and this page is updated with the change and its date. You can subscribe to change notices without holding an account through /contact.
How to object
You may object to a new subprocessor on reasonable data protection grounds within [OBJECTION WINDOW] of the notice, by writing to [PRIVACY CONTACT EMAIL] with your reasons. We will work with you in good faith on an alternative — for example, disabling the affected feature for your workspace. If there is no workable alternative, you may terminate the affected part of the service without penalty and receive a pro-rated refund of prepaid fees, per clause 8 of the DPA.
Questions
Ask before you sign up, not after: /contact or [PRIVACY CONTACT EMAIL]. Our security posture is described at /security — including what we do not have, such as a SOC 2 report.