Skip to main content
Rendevo is live. Prospects answer your questions before they book. Get started free

Data protection

How we handle your data

Where your data is kept, which providers handle it, how long we keep it, and how it is protected. The list of providers comes from reading our own code, and each protection described is in place today, so you can use this page when you review us as a supplier.

Position verified on 18 October 2026. Prepared by Vimatech Ltd. This page describes facts about the service. It does not constitute legal advice.

Your prospects' data is under your control

For the answers and bookings your prospects submit, you decide what happens to them, and we only process them on your instructions, as your processor. We decide, and answer for, one thing only: the data about your own account, workspace and billing. The privacy policy covers that part. For your prospects' data, our data processing agreement is in force from 19 October 2026 as part of the terms, and this page summarises what it commits us to.

What you can check

This page names every provider that handles your data and where, and says which protections exist in our code today. If your review needs something that is not here, ask us. Vimatech Ltd is registered with the UK Information Commissioner's Office as a data controller, under reference ZC155985.

Location

Where the data is kept

The Rendevo application has been in service since 6 October 2026, on infrastructure created in London on 2 October 2026.

What Provider Where Status
The application's API and its database: everything the service stores Amazon Web Services Region eu-west-2, London, United Kingdom In service since 6 October 2026. The database is encrypted at rest and its automated backups are kept for 7 days.
The application's pages (app.rendevo.com), including your public booking pages Cloudflare, Inc. Global network, including nodes outside the United Kingdom and the EEA In service since 6 October 2026. Requests pass through it on their way to the API; it is not where your data is stored.
The public website (rendevo.com), the pages you are reading Cloudflare, Inc. Global network, including nodes outside the United Kingdom and the EEA In service. It holds no account, funnel or prospect data.
Email (confirmations, reminders, and the reminder to book and the no-show email you can switch on) Resend, the trading name of Plus Five Five, Inc. United States Sending since 6 October 2026.

If you are established in the EEA: what the adequacy decision covers, and what it does not

Region eu-west-2 is in London, so the database, its backups and the images you upload are stored in the United Kingdom. Transfers to the United Kingdom are covered by the European Commission's adequacy decision, which stands on its own: for the data that comes to us here, there are no clauses for you to put in place with us, for as long as that decision remains in force. Some of the providers in the table below are established outside the United Kingdom and the EEA, and the last paragraph of this box deals with them.

A transfer is involved all the same, and the vocabulary hides it. The "eu" in an AWS region name is a label, not a location. Region eu-west-2 is in the United Kingdom, which has been a third country under Regulation (EU) 2016/679 since it left the Union, so using Rendevo means personal data leaves the Union. The adequacy decision is what makes that lawful without further safeguards.

That decision was adopted on 28 June 2021 as Implementing Decision (EU) 2021/1772 and amended on 19 December 2025 by Implementing Decision (EU) 2025/2574. It expires on 27 December 2031, unless the Commission extends it. That date is not a summary: Article 2 of the 2025 decision replaces Article 4 of the 2021 one with the sentence "This Decision shall expire on 27 December 2031, unless extended in accordance with the procedure referred to in Article 93(2) of Regulation (EU) 2016/679", and we read it in the decision itself on 17 September 2026.

The same decision says the Commission should start the procedure to extend it at the latest six months before that date, if the United Kingdom still meets the standard. That is an intention and not a guarantee, and the decision can also be suspended or repealed earlier. Our data processing agreement provides standard contractual clauses that take effect on their own for any transfer that stops being covered, so nothing has to be signed if the decision lapses.

Several providers are established in the United States. Cloudflare, which carries requests to the application's pages, and Resend, which sends messages about your meetings, handle data on its way through rather than storing your records, but that data still leaves both the Union and the United Kingdom. It does not travel on an adequacy decision: it travels on standard contractual clauses in each provider's own data processing terms, which bind our account with them. For Cloudflare, the traffic we carry on your behalf travels on Module Three of those clauses. Google and Microsoft are involved only if you connect their calendars, under your own account with them, and Stripe only under your own contract with it. OpenRouter is involved only if an owner of your workspace switches AI qualification on, and then receives your prospects' answers without their name, email address, telephone number, IP address or browser details; it is not on the Data Privacy Framework List, so that transfer travels on the UK Addendum in its own data processing agreement, and the model runs on Amazon Bedrock in Ireland. Google Analytics is involved only if you accept audience measurement on this website or in the app, and never on your booking pages: Google states that it relies on the EU-U.S. Data Privacy Framework and its UK Extension for that transfer, with standard contractual clauses as the fallback. The table below gives the details.

Sub-processors

Who else touches the data

Every provider below was found by reading our own code, not copied from a vendor list. Each transfer basis was read in the provider's own terms, on the date given.

Provider What it touches Where Transfer basis
Amazon Web Services The application's API, its database and the images you upload: everything the service stores eu-west-2, London, United Kingdom No transfer out of the United Kingdom for storage. Our contracting party is Amazon Web Services EMEA SARL, Luxembourg, named for an account located in the United Kingdom by the AWS Customer Agreement (last updated 14 August 2026). The AWS Data Processing Addendum binds our account through section 1.14.1 of the AWS Service Terms. Read on AWS's own documents on 5 October 2026.
Cloudflare, Inc. Delivery of this website, and of the application's pages and the requests they send, public booking pages included, and a count of page views on both that sets no cookie (Cloudflare Web Analytics, described in the privacy policy). It handles IP addresses, browser headers and the content of those requests on their way to the API, including what a prospect submits. It is not where your data is stored. United States company, global network Standard contractual clauses, Module Two, at clause 6.2(a) of the Cloudflare data processing addendum, version 6.4 effective 3 April 2026, with the UK Addendum at clause 6.2(b) for the United Kingdom part. Section 6.1 of Cloudflare's subscription agreement incorporates that addendum into our account by reference, so no separate signature is needed. Read on Cloudflare's own documents on 18 September 2026. That module covers our own account data. For the application traffic we handle on your behalf, clause 6.2(a)(i) of the same addendum applies Module Three, read on 18 October 2026. Cloudflare also states it complies with the EU-U.S. Data Privacy Framework; we have not verified that and do not rely on it.
Paddle.com Market Ltd Your subscription: payment, invoicing and tax. Independent controller for transaction data. We never see your card details. Set by Paddle as an independent controller, in its own privacy notice Not a transfer by us: Paddle collects payment data directly, as seller, under its own terms
Plus Five Five, Inc., trading as Resend Email to your prospects: confirmations, reminders and notifications, including the notice a prospect receives when your team cancels their meeting, carrying a name, an email address and the details of a meeting; and, if you switch it on for an event, the reminders, two at most, you write to a qualified prospect who has not booked, with a link to your calendar; and, if you switch it on for an event, the one email offering another time to a prospect whose meeting you mark as a no-show. Sending since 6 October 2026. United States. Its own terms say its primary processing happens there, and its published list names 22 further sub-processors, all in the United States. Standard contractual clauses, Module Two, in the provider's own data processing terms, with the UK Addendum for the United Kingdom part. Those terms bind our account without a separate signature: the addendum says it becomes binding when the agreement is entered into, and that the clauses are deemed signed with it. Read on the provider's documents on 17 September 2026. The provider's own sub-processor list includes two entities whose stated purpose is artificial intelligence; its documents do not say which data reaches them, and its data processing terms limit its sub-processors to providing its service to us.
OpenRouter, Inc., and Amazon Web Services through Amazon Bedrock (AI qualification) Only in a workspace where an owner has switched AI qualification on: the funnel's questions, your prospect's answers after automatic masking of email addresses, phone numbers, web addresses and the prospect's name, and the criteria and any instructions you wrote for the model, which are sent as written: keep a prospect's details out of them. Never the prospect's name, email or phone fields, IP address or browser details. OpenRouter routes each request, with no fallback, to Claude Haiku 4.5, a model made by Anthropic and run by Amazon Bedrock; Amazon states that model makers have no access to prompts and completions there, so Anthropic receives nothing. Every request is limited to services that do not keep its content once the answer is returned. Masking can miss something, so the answers remain personal data. OpenRouter: United States, where it processes each request. The model: AWS region eu-west-1, Ireland. OpenRouter's Data Processing Agreement, last updated 26 August 2026, part of its terms of service: the UK Addendum at section 13.3, appended to standard contractual clauses entered on Module Two. OpenRouter is not on the Data Privacy Framework List, checked on 19 October 2026, so we do not rely on that framework. The leg to Ireland is OpenRouter's onward transfer to its own sub-processor, to a country of the EEA. Details in sections 9.4 and 12.4 of the data processing agreement.
Google (Calendar API, including Meet) Where you sign in with Google: your name, email address and Google account identifier. Where you connect a Google calendar: your busy times only, never the content of your events, and events naming the prospect as guest, with their name, email address, telephone number, any booking notes, the times and the link. Google also emails the prospect itself, from your calendar: an invitation when the meeting is booked, and an update or a cancellation notice when it is moved or cancelled, whether by your team or by the prospect. Set by your own Google account Your calendar is held by Google under your own account, not as our sub-processor (data processing agreement, section 9.5)
Microsoft (Graph, Outlook calendar) The same, where an Outlook calendar is connected, including the Microsoft Teams link added to the meeting. Implemented and reachable, but no credentials are provisioned, so no data flows today. Set by your own Microsoft account Not in use: no data flows today
Stripe (your own account) Only if you connect your own Stripe account to take payments on a booking page. Your prospect pays into your account, under your contract with Stripe; we take no commission and never hold the funds. Stripe sends us a record of each payment, with the payer's name, email, billing address and the last four digits of the card, and we erase that content after 30 days. Stripe is your provider, not our sub-processor. Set by your contract with Stripe Set by your contract with Stripe
Google Ireland Limited (Google Analytics) Only for visitors of rendevo.com and users of the app who accept audience measurement: the pages they view (in the app, the kind of screen and never its real address or title), the sign-up buttons they click, account milestones sent by our server without any amount, and a random identifier made for this purpose. Never on your public booking pages, wherever they are served from, and never anything a prospect typed. Google signals, user-provided data collection and advertising personalisation are switched off. Google keeps the data for 14 months. Google Ireland Limited is the contracting party under the Google Analytics Terms of Service for the United Kingdom (last modified 11 January 2024). Google may process the data in any country where it or its sub-processors have facilities, the United States included, and states that data from devices in the UK, the EU and Switzerland is first collected on servers in those regions. Google Ads Data Processing Terms, version 8.0 of 30 May 2024, incorporated by the Google Analytics Terms of Service, with Google as processor. For transfers to the United States, Google states that it relies on the EU-U.S. Data Privacy Framework and, for the United Kingdom, on its UK Extension, with the standard contractual clauses of those terms as the fallback. Read on Google's own sites on 7 October 2026. We have not checked Google LLC's certification on the Framework's list ourselves, and we do not present it as our own finding.
Have I Been Pwned When you choose a password: the first five characters of a hash of it, and nothing else. Never the password, never your email address, nothing that identifies you. Not applicable: what is sent does not identify you Not applicable

Measures

How your account and data are protected

What is built into the service today.

Encrypted in transit, credentials encrypted at rest

TLS on every connection to this website and to the application. Connected calendar tokens, webhook signing secrets and two-factor secrets are encrypted at the application layer before they are stored. The database's storage and the uploaded images are encrypted at rest, which we checked on the live configuration on 5 October 2026.

Two-factor authentication that nobody here can switch off for you

If you sign in with a password, you can turn on a second factor with an authenticator app. Every sign-in asks for a code from it, with no option to remember a device and skip the code. You can register up to three authenticators on one account, and registering a second one is what keeps a lost phone from locking you out. You also get ten recovery codes, each usable once, shown on one screen and stored salted and hashed with bcrypt, the scheme we use for passwords, so we cannot read them back to you afterwards.

Our second factor is available on every account that has a password. An account created with Google sign-in can set one through the forgot-password email and then switch our second factor on; until it does, any second factor on it is the one set on its Google account.

Every change to this needs your password, re-entered in the app and good for ten minutes afterwards, and every change sends you an email that cannot be turned off. Some changes need more than the password. Switching the second factor off, or replacing your recovery codes, needs a code from an authenticator already on the account. Switching it on, or adding another authenticator, needs a code from the device being registered, which proves you hold that device and says nothing about the ones already there. Removing an authenticator needs the password and no code; the last one cannot be removed while the second factor is on.

Adding or removing an authenticator also alerts every owner and admin of your Workspaces. They receive the alert and nothing they can act on: the link that locks an account down, which signs every session out and invalidates the password, goes to you and to nobody else. The one link every recipient gets is the one that cancels a recovery request, described below, because cancelling gives the account back rather than taking anything from it.

Nobody at Rendevo can turn your second factor off. There is no support route, no administrative command, and no identity check we would accept instead, because anything we could ask you about the account is something a person reading your email already knows. Two automated tests hold this in place: one fails the build if a third place in our code can clear a second factor, the other fails if a second place can set the date a recovery wait ends, or if a scheduled task gains an option that could move it.

If you lose every authenticator and every recovery code, there is one way back, and it is slow on purpose. Once your password has been accepted on the sign-in screen, you can start a recovery request. It emails your account address and every owner and admin of every Workspace you belong to, including a Workspace you are only a member of, and nobody can suppress that email: no setting, preference or role turns it off. It then waits seven full days, and nobody here can shorten them. Nothing about the account changes while it waits, so if you still have a session you keep working. A red banner appears on every screen of the app while you are signed in; if you are locked out, the emails are the only notice you get. Two more go out, on day one and on day six. Signing in with an authenticator code or a recovery code cancels the request, and so does the link in each of those emails, for every recipient. That cuts both ways: any owner or admin who is told can stop it in one click, which protects you when somebody else started it and blocks you when they would rather you stayed out. A cancelled request can be started again immediately.

On the seventh day, the second factor is removed, every authenticator and recovery code is destroyed, every session is signed out, your password is invalidated so you get back in by resetting it by email, and connected calendars are deactivated so nobody silently inherits access to them. One request runs at a time, starting another does not restart the seven days, and one request may complete every 30 days. Only completions count, so a cancelled request does not use up that allowance.

What this means for you, plainly. Because this route exists, your account is protected by its password plus seven days of notice, not by two factors. A password can be reset by email, so whoever takes over your mailbox can start a request and wait a week. What stops them is the notice, and it only works if somebody other than you receives it. If your Workspace has other owners or admins, any one of them can stop the request in a click. If you are the only owner of your only Workspace, every warning lands in the mailbox that was taken, and the banner is on a screen you are not signed in to. We accept that, because in practice the alternative to a slow, announced route is an exception made by hand under pressure, and exceptions become the rule. Two practical steps follow: protect the mailbox on your Rendevo account at least as well as the account itself, and add a second owner to your Workspace. The screen that gives you your recovery codes explains the seven days and asks you to confirm you have understood them before it closes.

No card details stored

Paddle.com Market Ltd is the Merchant of Record for your subscription and collects payment as an independent controller. We receive the subscription status, a customer identifier and transaction references, and never the card details themselves.

Old records deleted automatically

The security event log, our internal record of product usage, the record of where a new account came from and the record of each webhook delivery are all deleted after 365 days. The content of a failed webhook delivery is erased after 30 days, and the content of a successful one is never stored at all, because you already have it and a second copy of your prospects' data would earn us nothing. The content of a payment record received from Stripe is erased after 30 days, and application error logs are deleted after 30 days. Your prospects' submissions follow the retention setting of your workspace, which you choose: unless you change it, an unfinished submission is deleted 30 days and a finished one 24 months after its last activity, counted from 19 October 2026 at the earliest, and you can also choose to keep everything (data processing agreement, section 8.1). Scheduled jobs enforce those limits every day without anyone having to decide to run them.

Deletion and exports on request

To have your data deleted, write to [email protected] and we handle it by hand. A CSV export of a workspace's submissions and bookings is built for owners and admins; while it is switched off, we send the same records by hand. The same applies if you object to our internal record of product usage.

Your rights

Your rights over your account data

You have these rights whatever we build. Today you use them by email, and we handle each request by hand.

  • Access: ask for a copy of your personal data
  • Rectification: have inaccurate data corrected
  • Erasure: ask for your personal data to be deleted
  • Portability: receive your data in a portable format

How to exercise them

Write to [email protected]. We handle each request by hand, and we answer within one month, the period the law sets (Article 12(3) of the UK GDPR and of the EU GDPR). If you think we got it wrong, you can complain to the UK Information Commissioner's Office, at ico.org.uk, or, in the EEA, to the data protection authority of your country.

If you reached us because you filled in a booking page, the business you were booking with decides what happens to your answers, not Rendevo. Those answers are saved as you go, before you submit, so the business can see a request you started and did not finish. We pass your request to them and tell you that we have. We do not confirm to anyone whether their data exists in the service, or with which customer, because confirming it would disclose that customer's data.

Something missing here?

If a detail you need is not on this page, ask and we will tell you what we know, including when the answer is that we do not know yet.