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

Privacy Policy

Last updated: 2026-11-17

This policy was prepared by Vimatech Ltd. It describes how the service actually handles data at the date above. It does not constitute legal, tax or accounting advice. Regulatory content verified on 7 October 2026, on 19 October 2026 for AI qualification (sections 3.6, 6 and 10), and on 17 November 2026 for the emails we send to businesses that are not yet customers (section 3.9).

1. Introduction

Rendevo (“we”, “us”, “our”) is operated by Vimatech Ltd, a company registered in England & Wales (No. 17001986). This Privacy Policy explains how we collect, use, and protect your personal data when you visit rendevo.com or use the Rendevo platform at app.rendevo.com.

2. Data Controller

Vimatech Ltd
Company No. 17001986
Registered in England & Wales
Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom
Registered with the UK Information Commissioner’s Office as a data controller, reference ZC155985
Email: privacy@rendevo.com

3. Data We Collect

3.1 Information You Provide

  • Account data: name, email address, company name
  • Billing data: payment method details (processed by Paddle)
  • Content data: qualification funnels, templates, and settings you create
  • Images you publish: the logo and the cover image you upload for your workspace, which anyone can see on your public booking pages. Only PNG and JPEG files are accepted. Before we store one, we remove the metadata a camera or an editing tool may have left in it (EXIF, XMP, IPTC and comments in a JPEG, text, EXIF and time chunks in a PNG), and we drop anything appended after the end of the image. When you replace or remove an image, we delete the previous file; if that deletion fails, the failure is logged rather than ignored. You can remove either image at any time, on any plan. A logo can be a photo of a person, so upload only an image you are entitled to publish. The service cannot delete a whole workspace yet, so nothing removes these images automatically when a workspace closes: remove them yourself before you leave, or ask us at privacy@rendevo.com and we remove them
  • Communication data: messages sent via contact forms or support

3.2 Information Collected Automatically

  • Usage data: pages visited, features used, actions taken
  • Device data: browser type, operating system, screen resolution
  • Log data: IP address, access times, referring URLs
  • Export records: when you download a CSV export, our security log records that you did, for which workspace, which kind of export, with which filters and how many rows. It never records the content of the file

3.3 Cookies and audience measurement

What is set without asking you. rendevo.com and the app at app.rendevo.com set cookies that make them work, keep them secure or remember a choice you made in them. None of them is used to measure your visit or to follow you, so none of them asks for your consent:

Cookie Set by What it is for How long it lasts
auth_token Rendevo, on app.rendevo.com Keeps you signed in to the app. Scripts on the page cannot read it 7 days, or until you sign out
rendevo_logged_in Rendevo, shared with rendevo.com Tells rendevo.com that you are signed in, so that it offers to open the app rather than to sign in. It holds the value 1 and nothing else 7 days, or until you sign out
rendevo_plan Rendevo, shared with rendevo.com Tells rendevo.com which plan the workspace you have open in the app is on, so that the pricing page never sends you to pay for that plan or a lower one: it marks that plan as your current plan, offers checkout only for a higher one and links the others to the page where you manage your plan. It holds the plan’s name and nothing else: free, pro, team or agency (our internal name for the Business plan) 7 days from its last update, or until you sign out
two_factor_challenge Rendevo, on app.rendevo.com Holds a sign-in in progress while you enter your second factor 5 minutes
sidebar_state Rendevo, on app.rendevo.com Remembers whether you left the app’s side menu open or closed 7 days
rendevo_consent Rendevo, shared between rendevo.com and app.rendevo.com so that one answer covers both Remembers whether you accepted or refused audience measurement, so that we do not ask you again on every page. It holds your choice and the date you made it, nothing else 6 months
cf_clearance Cloudflare, which serves both addresses (section 6) Security. Cloudflare checks, with a small script of its own, that a visit comes from a person and not from an automated bot, and this cookie remembers that your browser passed the check so that it is not repeated on every page. It is placed on rendevo.com and every address under it, booking pages included. It is not used to measure your visit or to follow you About one year: the expiry Cloudflare gave it when we checked on 7 October 2026

What the app keeps in your browser’s own storage. The app also writes a few values to your browser’s local storage and session storage, which are not cookies. They stay on your device, are used only by the app itself, and are not used to measure your visit or to follow you: your light or dark display preference; the workspace you last opened; the two figures you enter yourself in the estimate of turned-away requests on your dashboard; and, until it has been used, the page to return to after you confirm your email address or connect a calendar or a Stripe account. On a booking page that takes a payment, the booking being paid for is kept in session storage, for that browser tab only, so that the payment step can pick up where it was after Stripe’s form. You can clear them from your browser’s settings at any time, and the app then simply forgets those settings.

What runs without a cookie: Cloudflare’s count of page views. Cloudflare, which serves both addresses (section 6), adds a small script of its own, loaded from static.cloudflareinsights.com, to the pages of rendevo.com and of the app, booking pages included. We use it for one thing: counting how often each page is viewed and seeing how fast pages load, so that we can improve the site and the app. It sets no cookie and does not read or write anything in your browser’s storage. When a page loads, it sends Cloudflare the address of that page, the address of the page you came from, the timings of how the page loaded and was displayed, how much memory the page used where your browser reports it, and an identifier generated for that one page load. Like any request your browser makes, it also carries your IP address and your browser’s standard technical information, from which Cloudflare’s reports show the browser, operating system, type of device and country. Cloudflare’s documentation, which we read on 7 October 2026, states that it discards the IP address at the data centre that receives the request and does not store it, that it does not fingerprint visitors, and that it does not track individual visitors across the websites it serves. What we see is totals, by page and by those categories, never a record of an individual visitor. We rely on our legitimate interest in knowing which pages are used and whether they load well (section 5).

This count is separate from Google Analytics below: refusing Google Analytics does not switch it off, and accepting it does not change it. You can object to it. Because the count does not single out any visitor, we cannot switch it off for you alone from our side: the way to stop it is to block static.cloudflareinsights.com in your browser or with a content blocker. The site and the app work exactly the same without it.

What is set only if you accept: Google Analytics. The first time you visit, a banner asks whether you accept audience measurement. Accept and Refuse are the same size and sit side by side, and the site and the app work the same whichever you choose. Until you accept, the Google Analytics script is not loaded at all and nothing is sent to Google. If you refuse, or ignore the banner, that remains the case.

If you accept, we load Google Analytics on rendevo.com and app.rendevo.com, and we use it for one purpose: counting visits and seeing which pages and steps lead people to create an account and to subscribe. Not for advertising. Google Analytics then sets two cookies, _ga and _ga_<ID>, on the address you are visiting only (not on the whole rendevo.com domain), for 13 months from the moment they are first set. Their lifetime is not extended when you come back.

What we send to Google when you have accepted:

What Detail
Pages viewed On rendevo.com, the address of the page without anything after the ?, except the five campaign parameters utm_source, utm_medium, utm_campaign, utm_content and utm_term. In the app, the kind of screen (for example “event editor” or “lead detail”), never its real address and never its title, because those can carry a prospect’s name, an email address or a security token.
Buttons Which “sign up” or “sign in” button you clicked, where it sits on the page, and which plan it was for.
Account milestones, sent by our server That an account was created, how (email or Google) and whether through an invitation; that a workspace was created and what kind of business it describes; that a workspace published its first event, received its first qualified request and its first booking; that a subscription started, with the plan name. Never an amount, never a name, never an email address, never anything a prospect typed.
A random identifier for your account A random code generated for this purpose only, so that visits on rendevo.com and in the app can be connected to the same account. It is not your account number and not your email address.
Technical data Google collects itself The browser, device type and approximate location derived from your IP address. Google states that for users in the UK, the EU and Switzerland it uses the IP address only to derive that approximate location and then discards it, and does not log or store it. We read that statement on Google’s own help page on 7 October 2026.

The account milestones are sent from our server rather than from your browser. We send them only if you accepted measurement and that choice is recorded on your account, and we stop the moment you withdraw it.

We switched off the Google Analytics settings that would go further than this: Google signals, the collection of user-provided data, precise location and device data, and the use of this data for personalised advertising. Google keeps the event data for 14 months, the period we set in Google Analytics. Section 6 says who Google is in this arrangement, and section 10 how the data leaves the United Kingdom and the EEA.

Changing your mind. A “Cookie settings” link reopens the same choice. On rendevo.com it sits at the bottom of every page. In the app, it sits at the bottom of the sign-in and sign-up pages and, once you are signed in, in the menu under your name at the bottom of the left-hand sidebar and on your Account page. If you withdraw, we stop loading Google Analytics, delete the Google Analytics cookies we are able to delete, and our server stops sending milestones for your account. What Google already received before you withdrew stays with Google for the period above; you can ask us to request its deletion (section 8).

Booking pages never carry Google Analytics. The pages your prospects open to book a meeting with a Rendevo customer, wherever they are served from, including addresses under app.rendevo.com/book, never load our Google Analytics and never send anything to Google on our behalf. The choice you make on rendevo.com is not read there. Cloudflare’s count of page views, described above, does run on the booking pages served at app.rendevo.com, as on every other page Cloudflare serves there.

Stripe on booking pages that take a payment. When a customer asks its prospects to pay at booking, the payment form is Stripe’s, loaded from Stripe at the payment step and not before, and Stripe may set its own cookies there for fraud prevention. That form belongs to the customer’s own Stripe account (section 6).

What is still not used. Apart from Google Analytics, if you accept it, and Cloudflare’s count of page views, we run no advertising pixel, no remarketing tag and no other third-party measurement tool on either surface. If that changes, we will ask you first, and this section will say what changed.

3.4 Product events, measured by us and shared with nobody

When you use certain features in the app, we write a product event to our own database: what happened, in which workspace, under which account, on which plan at that moment, and a few properties describing the action. Opening an upgrade prompt, creating a webhook endpoint and customising your branding are examples.

Three things about it, because the word “analytics” usually implies the opposite of each. It is attached to your account, which is what makes it useful to us and what gives you the rights in section 8 over it. It is shared with nobody: no third-party analytics provider receives it, Google Analytics included, and it never leaves our own database. The account milestones described in section 3.3 are a separate, much shorter list, sent to Google only if you accepted measurement; a product event record is never one of them. And it does not rest on your consent: we rely on our legitimate interest in knowing which parts of the product are used and where people get stuck, under Article 6(1)(f). You can object at any time, at privacy@rendevo.com, and we stop.

We keep each record for 365 days, then a scheduled job deletes it. That is the same period as our security log: keeping a record of what you clicked for longer than the trace we would need to investigate an incident would not survive the data minimisation test.

3.5 Figures about you that your workspace’s owners and admins can see

On the Team plan, the owners and admins of a workspace can read reports about the people who host meetings in it: the share of your bookable hours taken by Rendevo bookings, week by week; the meetings already booked with you over the next one or two weeks; the prospects routed to you; and the recorded outcome of your past meetings.

For those reports, the customer who runs the workspace is the controller, because the purpose is theirs (managing their own team), and we process the figures on their behalf under our Data Processing Agreement. What we guarantee regardless of who runs the workspace:

  • if you are a member, you see your own figures only, and the application tells you that owners and admins can see your booking load and meeting outcomes by week;
  • figures are weekly at the finest, with no ranking, no score, no individual alert, and nothing about what you do in the application;
  • the booking load counts only meetings booked through Rendevo against the hours you have opened for booking. It is not a measure of your working time or your performance;
  • if you leave a workspace, you stay named in its reports for 12 months, then your figures are grouped under “Former members”. The record of your departure holds when you joined, when you left, your role and who removed you, with no reason and no comment. The meetings you held stay in the workspace, because they are the customer’s records.

These reports are built and switched off at the date above. If you are an employee, your employer is the one who must tell you how it uses them.

3.6 If you filled in a booking page

This part is for the people who answer a Rendevo booking page, rather than for our customers.

The business whose page you filled in decides what happens to your answers and is responsible for them; the page says so, and names that business, on the step where you enter your contact details. We run the page and store your answers on that business’s behalf, as its processor. So the business, not Rendevo, is the one to ask about what it keeps and for how long. That business’s own privacy notice tells you the rest: how to contact it, why it uses your answers and how long it keeps them.

What is stored, so that you are not surprised by it:

  • Your answers are saved as you go, before you submit. From your first answer or your contact details, the page saves your progress a moment after each step, so the business can see a request that was started and not finished. If you leave halfway, what you had entered by then stays with the business, marked as unfinished.
  • With your answers, we record your IP address, your browser’s user agent, and when you started and finished. The service can also record the campaign parameters of the link you followed (utm_source, utm_medium, utm_campaign, utm_content, utm_term) and the domain of the page that sent you, never its full address, where the business leaves that setting on. At the date above, booking pages do not send these values yet, so none are recorded.
  • If your email address is at a company domain rather than at a public provider such as Gmail or Outlook, the business may see that domain’s icon next to your request. To show it, our server asks the website of that domain for its icon. The request carries nothing you entered and names no one, and no other company is involved.
  • If the business switched on AI qualification, your answers are also assessed by a language model, to help the business decide whether your request fits. Your name, email address and telephone number, your IP address, your browser details and the address of the page that sent you are never sent for this. Your answers are, after we automatically mask email addresses, telephone numbers, web addresses and your name in what you typed; masking can miss something, so what you write may still identify you. The request goes through OpenRouter, Inc., in the United States, to Claude, a model made by Anthropic and run by Amazon Web Services in Ireland; Anthropic itself receives nothing (section 6). The result, a score, a recommendation and for each of the business’s criteria a short reason, is stored with your request and deleted with it. The result cannot turn your request down: at most it asks a person at the business to look at it, and you can still book. If the business’s own rules decline a request, the page that says so carries a link to ask the business for a person to review it; we record that you asked, with your request, and show it to the business in its account; the business is also told by email, for up to 20 requests a day, beyond which a request is shown in its account without an email.
  • If you book a meeting, its details go into the host’s connected calendar, and Google or Microsoft may email you an invitation from that calendar. If the meeting is later moved or cancelled, whether by you or by the business, they may also email you an update or a cancellation notice from that calendar (section 6).
  • Up to two reminders if you do not pick a time. A business can choose to email people whose request it has accepted but who have not booked a meeting yet, at most twice, between an hour and three days after it accepted the request. If the business whose page you filled in has switched this on, the step where you enter your contact details says so and lets you refuse them there, before anything is sent, unless the business has told us that it writes only to companies or that you have already agreed to its emails. Each email names the business, carries a link that takes you straight to its calendar without filling in the form again, and carries a link to unsubscribe. You receive at most two for a request, and none at all, or no second one, if you book, if you refused them, if you unsubscribe, or if the business changes its decision about your request.
  • One email if a meeting you booked did not take place. A business can choose, event by event, to email you once when it marks a meeting you booked as a no-show, shortly after it does so, to offer you another time. The step where you enter your contact details tells you that the business may email you once after the meeting and lets you refuse it there, before anything is sent, unless the business has told us that it writes only to companies or that you have already agreed to its emails. The email is sent in the business’s name, says the meeting did not take place as planned without saying who missed it, carries a link to pick another time and a link to unsubscribe. The link to pick another time is specific to your booking and does not contain your name or email address; it lets you book without filling in the form again, shows none of your answers and cannot change them, and it stops working once you book again, if your request is deleted, or 14 days after the email is sent. You receive at most one email from the business after a meeting, and none at all if you refused it, if you unsubscribed, if you already have another meeting coming up with that business, if the business sets the meeting back to held before it is sent, or more than 7 days after the meeting.
  • If you unsubscribe, from that email, from the button your mail app shows, or by refusing on the booking page, that business stops sending you reminder and follow-up emails through Rendevo. It does not cancel a meeting, and if you book one you still receive its confirmation and its reminders. To make that last, the business’s list of people who unsubscribed keeps your email address, the date and how you unsubscribed, and nothing else. That entry stays for as long as the business uses Rendevo, even after your answers are deleted and even if you ask the business to delete your data: without it, you would start receiving its emails again.
  • If the page takes a payment, you pay the business through its own Stripe account (section 6). Stripe sends us a record of that payment, which carries your name, your email address, your billing address and the last four digits of your card; we erase that content 30 days after we receive it and keep only the reference that stops the same payment being counted twice.

How long your answers are kept is set by the business. Unless it has chosen otherwise, an unfinished request is deleted 30 days, and a finished one 24 months, after its last activity. A request linked to an upcoming meeting is not deleted, and one linked to a payment is kept until 120 days after the payment’s last update, or longer while the payment is pending or disputed.

To access, correct or delete what you entered, write to the business. If you write to us instead, we pass your request to it and tell you that we have. We do not confirm to anyone whether their data is in the service, or with which business, because that would disclose the business’s data.

3.7 Where you came from when you created your account

When you create an account, we record how you reached the sign-up page, so that we know which of our channels bring people who actually use Rendevo. We keep:

  • the five campaign parameters of the link you followed to sign up, if it had any (utm_source, utm_medium, utm_campaign, utm_content, utm_term), each shortened to a fixed length;
  • the domain of the page that sent you, never its full address;
  • the plan you were looking at when you clicked “sign up”, if any.

We never keep an advertising click identifier (such as gclid or fbclid), and we record this whether or not you accept Google Analytics, because it is written to our own database and sent to nobody. It rests on our legitimate interest in knowing which channels work, under Article 6(1)(f), and you can object at privacy@rendevo.com. We keep it for 365 days after your account is created, then a scheduled job deletes it.

3.8 Set-up emails to the owner of a workspace

If you own a workspace, we may send you up to two short emails to help you finish setting it up. Nobody else in the workspace receives them: not the members you invite, not the admins.

Email When it is sent When it is not sent
A reminder to publish your first event At least 24 hours after you create your account, if no event is published in your workspace by then If an event is published before it goes out
A reminder about sharing your booking link At least 3 days after your first event is published, if no prospect has completed one of your booking pages by then If a prospect completes one before it goes out

Each of them is sent at most once, and never again after that: the first once for your account, the second once for each workspace you own. They go out at 10:00 in your workspace’s time zone, Monday to Friday only, so the first one arrives on the first weekday morning after the 24 hours have passed, and the second on the first weekday morning after the 3 days. Just before sending, we check again, and if you have already done what the email is about, it is not sent.

They are about using the Rendevo account you already have. They carry no price, no plan, no offer and nothing about any other product.

Stopping them. Each set-up email has a “Stop set-up emails” link at the bottom. One click stops both, without signing in. Your email app may also show its own unsubscribe button for these emails, which does the same thing. Stopping them changes nothing else: you keep receiving the emails the service needs in order to work, such as sign-in and security messages, booking confirmations and reminders, and messages about your subscription.

What they use. Your name, your email address, your workspace’s time zone, whether an event is published, and whether a prospect has completed one of your booking pages. We read this from our own database, never from Google Analytics, so whether you accepted audience measurement (section 3.3) makes no difference. We record that each email was sent, so that it is never sent twice, and whether you stopped them; we keep both while your account exists.

We rely on our legitimate interest in helping the people who sign up actually get the service working, under Article 6(1)(f). Not on our contract with you: the service works without these emails, so sending them is not necessary to perform it. You can object at any time, with the link in the email or at privacy@rendevo.com, and we stop.

3.9 If we contacted you about Rendevo before you had an account

This part is for people who received an email or a LinkedIn message from us about Rendevo without having signed up.

What we hold. Your name, your work email address, your job title, the business you work for and its website, where we found those details, the dates we wrote to you, and your replies. Nothing else: no home address, no personal phone number, nothing about your private life.

Where it comes from. From public professional sources: your business’s own website, your public LinkedIn profile, read by a person, and public professional directories. We do not buy contact lists and we do not collect profiles with automated tools. If you ask, we tell you exactly where we found your details.

Why, and on what basis. To offer Rendevo to businesses it may be useful to, under our legitimate interest in making our product known to them, Article 6(1)(f). We weighed that interest against yours before writing: we only write to a work address about your work, we write a few times at most, and stopping us takes one reply. In the United Kingdom we only send such an email unasked to an address at a company or another corporate body. We do not send one to a sole trader or to a partnership that is not a limited liability partnership, unless they asked us to.

Stopping it. Reply “unsubscribe”, or anything that says no, or write to privacy@rendevo.com. We stop writing to you, and we keep your email address on a list of people not to contact, with the date you asked, so that we never write again. That list holds nothing else and is the one thing we keep after you object, because without it we could not keep the promise.

How long. If you do not answer, we delete your details 6 months after our last message. If you answer, 6 months after our last exchange, unless you open an account, in which case the rest of this policy applies. The do-not-contact list is kept for as long as we send such emails.

Who handles it. The emails are written and sent by a person, one at a time, from our own mailbox, hosted by Google Workspace (section 6). They come from an address at rendevo.com or at getrendevo.com, a domain Vimatech Ltd holds for these emails only, so that they never affect the delivery of the emails our customers rely on. Each one names Vimatech Ltd and gives our postal address. We do not share these details with anyone else.

4. How We Use Your Data

We process your data for:

  • Providing and maintaining the Service
  • Processing payments and managing subscriptions
  • Sending transactional emails (confirmations, reminders)
  • Sending the owner of a new workspace up to two set-up emails, which can be stopped in one click (section 3.8)
  • Writing to people at businesses that are not yet customers, to offer them Rendevo, and keeping a list of those who asked us to stop (section 3.9)
  • Sending each owner and admin of a workspace a weekly summary of its results by email, on Monday morning in the workspace’s time zone. It gives the workspace’s totals for the previous week, each compared with the week before: leads submitted, qualified and disqualified, meetings held and no-shows, and, where there is any, the call time the workspace’s rules filtered out. It carries totals only, never a prospect’s name, email address or answers, and no offer. It is on unless you turn it off, and it is not sent when the workspace’s email notifications are off or when nothing happened that week. You can turn it off in your account settings, or with the one-click link at the bottom of the email, which stops this email only. It is sent through Resend (section 6)
  • Improving the Service based on usage patterns
  • Measuring the audience of rendevo.com and of the app with Google Analytics, only if you accept it (section 3.3)
  • Counting page views of rendevo.com and of the app with Cloudflare Web Analytics, which sets no cookie (section 3.3)
  • Knowing which channels bring new accounts (section 3.7)
  • Responding to support requests
  • Protecting accounts, which includes telling you and the owners and admins of your Workspaces when someone asks for the second factor on your account to be removed, and when an authenticator is added to it or taken off it (section 6)
  • Complying with legal obligations
Purpose Legal Basis
Service delivery Contract performance
Weekly summary of a workspace’s results to its owners and admins (section 4) Contract performance
Billing Contract performance
Product usage measurement Legitimate interest
Counting page views with Cloudflare Web Analytics (section 3.3) Legitimate interest
Audience measurement with Google Analytics, including the account milestones our server sends (section 3.3) Consent, which you can withdraw at any time from “Cookie settings”
Recording where a new account came from (section 3.7) Legitimate interest
Account security notifications, including the disclosure in section 6 Legitimate interest
Set-up emails to the owner of a workspace (section 3.8) Legitimate interest
Emails and messages to businesses that are not yet customers (section 3.9) Legitimate interest
Keeping the list of people who asked us not to contact them (section 3.9) Legal obligation and legitimate interest
Marketing emails from us to you, as a Rendevo account holder Consent
Legal compliance Legal obligation

6. Data Sharing

We do not sell your personal data. Apart from the disclosure described at the end of this section, which goes to people rather than to suppliers, we share data only with:

  • Amazon Web Services: hosts the application’s API, its database and the images you upload, in its London region (eu-west-2), in the United Kingdom. Our contracting party is Amazon Web Services EMEA SARL, of Luxembourg. Section 10 gives the terms and the date we read them.

  • Paddle.com Market Limited: payment processing, invoicing and tax collection (acts as Merchant of Record and independent data controller for transaction data). See Paddle’s Privacy Notice for how they handle your payment information.

  • Cloudflare, Inc.: serves the public website at rendevo.com and the pages of the Rendevo application at app.rendevo.com, including the public booking pages your prospects open. Every request to either address passes through Cloudflare, so it handles your IP address, your browser headers and the content of each request on its way to our servers, including what you type into the application and what a prospect enters on a booking page. It also runs the page-view count described in section 3.3 (Cloudflare Web Analytics), which sets no cookie and sends Cloudflare the address of each page viewed, the page you came from and loading timings. We do not use Cloudflare to store your account, funnel or prospect data: that is kept in our database on Amazon Web Services in London (section 10). Because Cloudflare, Inc. is established in the United States, that data leaves the United Kingdom and the EEA under the standard contractual clauses in Cloudflare’s own data processing addendum, with the UK Addendum for the United Kingdom part. Section 10 gives the clause references and the date we read them.

  • Plus Five Five, Inc., trading as Resend (United States): sends our email: the confirmations and the reminders about your meetings, the emails about your account, the set-up emails described in section 3.8, and, for a business that switches them on, the reminders, two at most, that business writes to a person who has not booked yet, and the one email offering another time after a meeting it marks as a no-show (section 3.6). Subscribed on 16 September 2026, sending since 6 October 2026. Because it is established in the United States, that data leaves the United Kingdom and the EEA under the standard contractual clauses in Resend’s own data processing terms, with the UK Addendum for the United Kingdom part. Resend’s own published list of sub-processors includes two entities whose stated purpose is artificial intelligence. Its documents do not say which data reaches them; its data processing terms limit its processing, and that of its sub-processors, to providing its service to us.

  • OpenRouter, Inc. (United States) and Amazon Web Services, through Amazon Bedrock (Ireland), only for the people who fill in the booking page of a business that switched AI qualification on (section 3.6). OpenRouter routes each request to Claude Haiku 4.5, a language model made by Anthropic and run by Amazon Bedrock, which returns a score and a recommendation. Amazon states that model makers have no access to prompts and completions on Amazon Bedrock, so Anthropic receives nothing. They never receive a name, an email address, a telephone number, an IP address or browser details. Every request is limited to services that do not keep its content once the answer is returned. They act for us, and we act for the business whose page was filled in. Transfers: section 10.

  • Google Ireland Limited, for Google Analytics, only if you accept audience measurement (section 3.3). It receives the pages, buttons and account milestones listed there, and acts as our processor under the Google Ads Data Processing Terms, which the Google Analytics Terms of Service incorporate. Google may pass the data to Google LLC and its other sub-processors, including in the United States (section 10). We switched off the settings that would let Google use this data for its own products or for advertising.

Five more receive something narrower, and they are listed because a list that omits the small ones is not a list.

  • Google, for Google Workspace, which hosts our own mailbox. It holds the emails we send to and receive from businesses that are not yet customers (section 3.9), and anything you write to us at a rendevo.com address. It acts as our processor under Google’s Cloud Data Processing Addendum, which applies to Google Workspace (section 10).

  • Google LLC, where you choose to sign in with Google or to connect a Google calendar. The sign-in tells Google that you are signing in to Rendevo. Connecting a calendar lets us read your busy times and write the meetings you accept. When a prospect books a meeting on that calendar, Google sends them an invitation from your calendar. If the meeting is later moved or cancelled, Google also sends them an update or a cancellation notice, whoever makes the change: your team, or the prospect through the links in the emails about their meeting. Where a move is made by cancelling the event and creating a new one, the prospect receives a cancellation notice followed by a new invitation. The prospect receives all of these messages from Google in your calendar’s name. From Google we receive only your name, your email address and your Google account identifier when you sign in, and only your busy times when you connect a calendar: we do not read the titles or content of your events.

    Rendevo’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. In practice: we use that information only to sign you in and to provide the calendar features you connected; we do not transfer it to anyone except as needed to provide those features, to comply with the law, or as part of a merger or acquisition; we never use it for advertising and never sell it; and no person at Vimatech reads it unless you ask us to, it is needed for security or to investigate abuse, or the law requires it.

  • Microsoft Corporation, the same, where you connect an Outlook calendar instead, including the Microsoft Teams link added to the meeting. As with Google, we read only your busy times. Implemented and reachable, but no credentials are provisioned at the date above, so nothing flows through it today.

  • Stripe, where you connect your own Stripe account to take payments on a booking page. You contract with Stripe directly, your prospects pay into your account, and we take no commission and never hold the funds. We keep your Stripe account identifier and its status, and receive the payment records described in section 3.6. Stripe is your provider, under your own agreement with it, and not ours.

  • Have I Been Pwned, when you choose a password. We send the first five characters of a hash of it and never the password, never your email address and nothing that identifies you. That is the whole of the exchange, and it is what lets us tell you that a password has appeared in a known breach without telling anybody which password is yours.

This list was built by reading our own source code and our own infrastructure, not a list of suppliers we assume we use. The fuller version, which also covers the providers that touch the data of people who book meetings with our customers, is on how we handle your data, and the contractual list is in section 9.4 of our Data Processing Agreement. Where a provider processes data on our behalf, section 10 names the data processing terms that bind our account with it and the date we read them.

The people in your Workspaces

One disclosure in this policy is not to a supplier, and you are the one who triggers it.

If you lose every authenticator and every recovery code, the only route back into your account is a recovery request, described on how we handle your data. Starting one sends an email to your account address and to every owner and admin of every Workspace you belong to. That email carries your name and your email address, tells them a request to remove the second factor on your account exists, and gives each of them a link that cancels it. Two further emails go to the same people, on day one and on day six.

That disclosure is the point of the mechanism rather than a side effect: a request of this kind is announced to everyone it could affect, and the person who starts it cannot suppress the announcement. There is no setting, no preference and no role that turns it off. If you do not want your name and address reaching the owners and admins of a Workspace, do not start a recovery request.

Adding or removing an authenticator on your account emails the same people. That message names you and says what changed, for the same reason: an authenticator appearing on an account is what a takeover looks like from outside, and the people who would lose something by it are the ones who should hear about it.

Those copies are not the same email, and the difference is deliberate. Yours carries a link that locks the account down: using it signs every session out and invalidates your password, so whoever added that authenticator loses the account. The copies sent to the owners and admins of your Workspaces carry no link at all, neither that one nor any other. They are told what happened, and they cannot act on your account from the message. We separated the two copies on 21 September 2026, before any of these emails had reached anybody, since the application was not deployed and the provider that would send them had not sent a message yet.

The link that cancels a recovery request is the exception, and it reaches every recipient of that email. Cancelling only puts the account back where it was, so it can take nothing away from you. That is the rule we apply to every security email we send: a link that undoes something goes to everyone who is told, and a link that destroys something goes to you alone.

We rely on legitimate interests, ours and those of the people we tell, under Article 6(1)(f): keeping accounts from being taken over, and letting the owners and admins who would carry the consequences stop a request that should not have been made. Recital 49 treats processing that is strictly necessary and proportionate for ensuring network and information security as a legitimate interest, and that is the interest at work here.

We do not rely on contract performance. A recovery mechanism that told only you would still deliver the service you signed up for, so telling other people is not necessary to perform our contract with you. Saying it was would be the easier answer rather than the correct one.

Two consequences of that choice, written down rather than left implicit. Because the basis is legitimate interests, you have the right to object under Article 21(1). If you object, we will not stop this notification while you keep an account that can start a recovery request: preventing a takeover, and protecting people who are not you, are the compelling grounds that article contemplates. What you keep is the control that actually matters, since nothing is sent unless you start the request yourself. And the notification reaches every Workspace you belong to, including one where you are only a member and the owners work at a different company, because any Workspace your account can reach is a Workspace your account can be used against. We consider that scope proportionate for that reason.

Paddle as Data Controller

When you make a payment, Paddle collects and processes your payment details (card number, billing address, etc.) as an independent data controller. Rendevo does not store or have access to your full payment card details. We only receive confirmation of subscription status, customer ID, and transaction references from Paddle.

7. Data Retention

  • Account data: retained while your account is active, and deleted within 30 days of a deletion request. Deletion is handled by hand for now (section 8)
  • Billing records (subscription status, the Paddle customer identifier and transaction references; Paddle keeps the payment details themselves, section 6): retained for as long as UK company and tax law requires Vimatech Ltd to keep its accounting records, then deleted. The period is the one set by those texts in force, and we do not restate a number of years here
  • Application error logs, which can contain an email address or an IP address: deleted after 30 days
  • Content of a payment record received from Stripe (section 3.6): erased 30 days after we receive it
  • Product event records: deleted 365 days after the event, by a scheduled job that runs every day
  • Where a new account came from (section 3.7): deleted 365 days after the account is created
  • Your audience measurement choice (section 3.3): the rendevo_consent cookie lasts 6 months, after which we ask again; the record of that choice on your account is kept while the account exists
  • Google Analytics cookies: 13 months from when they are set. Google Analytics event data: kept by Google for 14 months
  • Set-up emails (section 3.8): the record that each one was sent, and whether you stopped them, kept while your account exists
  • Contact form data: retained for 90 days or until processed
  • Details of a business we wrote to before it had an account (section 3.9): deleted 6 months after our last message if there was no answer, or 6 months after our last exchange. The do-not-contact list, which holds an email address and the date of the request only, is kept for as long as we send such emails
  • The record of a business hiding the opt-out box on one of its booking pages (which owner or admin, by name and email, when, on which statement and which version of its text, and when it was switched off): kept while the workspace exists, then for 6 years after its deletion, as evidence of the business’s statement, even if that person’s account is deleted
  • The record of AI qualification being switched on or off in a workspace (which owner or admin, when, which version of the screen and of the list of providers): kept while the workspace exists, then for 6 years after its deletion, as evidence of the business’s authorisation
  • Weekly summary (section 4): the record that it was sent to you for a workspace and a week, so that it is never sent twice, and the date you turned it off, if you did. Both are kept while your account exists, and the first is deleted with the workspace

8. Your Rights

Under the UK GDPR, and under the EU GDPR where it applies to you, you have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Erase your data (“right to be forgotten”)
  • Restrict processing
  • Data portability: export your data
  • Object to processing based on legitimate interest
  • Withdraw consent at any time. For Google Analytics, open “Cookie settings” (described in section 3.3) and choose Refuse.

To exercise these rights, email privacy@rendevo.com.

Withdrawing your consent to Google Analytics is something you do yourself. Every other request, including deleting your account, is handled by hand by our team, and we answer within one month, the period set by Article 12(3). That includes objecting to the product event records described in section 3.4, which we stop writing and delete for your account on request.

You can also complain to a regulator. If you think we have handled your data unlawfully, you have the right to lodge a complaint with the UK Information Commissioner’s Office, at ico.org.uk. If you are in the European Economic Area, you can complain to the data protection authority of the country where you live or work, or where the problem happened. You do not have to contact us first, although we would like the chance to put it right.

9. Security

These are the measures we can point at in our own code today:

  • Encryption in transit (TLS) on connections to rendevo.com and to app.rendevo.com
  • Encryption of stored credentials: connected calendar access and refresh tokens, webhook signing secrets and custom header values, and two-factor authentication secrets are encrypted at the application layer before they are written to the database
  • Encryption at rest of the database’s storage and of its automated backups, kept for 7 days, by Amazon Web Services, and of the images you upload, checked on the live configuration on 5 October 2026
  • Authentication on every route that touches your data, and a check of your chosen password against known breaches
  • A second factor on password accounts, using an authenticator app. Up to three authenticators can be registered on one account, and ten single-use recovery codes are issued when it is switched on. Those codes are salted and hashed with bcrypt, the same scheme as passwords, are shown on one screen only, and are never sent by email
  • One route back for an account that has lost every authenticator and every recovery code: a recovery request that you start yourself once your password has been accepted, that is announced by email to you and to the owners and admins of your Workspaces, that nobody here can shorten, and that takes effect seven days later. No support route and no administrative command can turn a second factor off, and none can shorten those seven days. Section 6 says who is told. Because that route exists, the real strength of an account is a first factor plus seven days of notice rather than two factors, and how we handle your data says in full what that costs and why we accept it
  • Scheduled deletion that runs without anyone deciding to run it, for the records described in section 7
  • Outbound requests to an address you configure are checked before they are made, so the service cannot be turned into a way of reaching machines it should not reach

Our second factor is available on every account that has a password. An account created by signing in with Google 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.

10. International Transfers

Requests to the public website at rendevo.com and to the application at app.rendevo.com are served by Cloudflare’s global network, so the data described in section 6 may be handled by a Cloudflare node outside the United Kingdom and the EEA. Cloudflare, Inc. is established in the United States.

That transfer travels on the standard contractual clauses in Cloudflare’s own contract. Cloudflare’s self-serve subscription agreement, which carries a last update of 12 September 2025, provides at its section 6.1 that Cloudflare’s Data Processing Addendum “is hereby incorporated by reference into this Agreement”. The addendum therefore binds our account without a separate signature. That addendum, version 6.4, effective 3 April 2026, applies the EU standard contractual clauses at its clause 6.2(a), Module Two for a customer acting as controller, which is our position here; and at clause 6.2(b) it applies those same clauses as amended by the UK Addendum, which it treats as executed between the parties. We read both documents on 18 September 2026. For the data of people who book meetings with our customers, which we handle as our customers’ processor, the same clause 6.2(a)(i) applies Module Three; we read it on 18 October 2026.

Cloudflare also states, at clause 6.4 of the same addendum, that it complies with the EU-U.S. Data Privacy Framework. We have not verified that certification on the Framework’s own list and we do not rely on it, for the same reason we do not rely on the equivalent statement made by our email provider.

The application’s API and its database run on Amazon Web Services, in its London region, which the provider names eu-west-2. That was decided on 15 September 2026, and the infrastructure was created there on 2 October 2026. The application has been in service since 6 October 2026. Its pages, and the requests they send to that API, pass through Cloudflare, as described above.

eu-west-2 is a region name, not a location in the European Union. London is in the United Kingdom, which is a third country under the EU GDPR. If you are in the EEA, your personal data is therefore processed outside the Union, in the United Kingdom, and that transfer relies on the European Commission’s adequacy decision for the United Kingdom for as long as it remains in force.

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, whose Article 2 replaces its Article 4 with: “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.” We read that in the decision itself on 17 September 2026. The Commission states in the same decision that it should start the procedure to extend it at the latest six months before it ceases to apply, if the finding still holds. An extension is not a certainty, and we do not present it as one.

Our account is located in the United Kingdom. For such an account, the AWS Customer Agreement (last updated 14 August 2026) names Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg, as the contracting party. The AWS Service Terms provide at section 1.14.1 that they incorporate the AWS Data Processing Addendum when AWS services are used to process customer data, so that addendum binds our account without a separate signature. We read both on 5 October 2026.

Transactional email is the exception to the paragraphs above. The provider that sends our email, including the confirmations and reminders about your meetings and the set-up emails in section 3.8, is established in the United States, so that data leaves both the United Kingdom and the EEA. It does not travel on an adequacy decision. It travels on the standard contractual clauses in that provider’s own data processing terms, Module Two, completed by the UK Addendum for the United Kingdom part of the transfer. It has been sending since 6 October 2026.

AI qualification is a further exception, and it applies only to the answers of people who fill in the booking page of a business that switched it on. Those answers, without name, email address, telephone number, IP address or browser details, go to OpenRouter, Inc. in the United States, which passes them to Amazon Web Services in Ireland. OpenRouter is not on the Data Privacy Framework List (we checked on 19 October 2026), so the UK’s data bridge with the United States does not cover it. The transfer from the United Kingdom relies on the International Data Transfer Addendum issued under section 119A of the Data Protection Act 2018, which OpenRouter’s Data Processing Agreement of 26 August 2026 applies at its section 13.3, and from the EEA on the European Commission’s standard contractual clauses in the same agreement. The onward leg to Ireland goes to a country of the European Economic Area, which UK law treats as approved for transfers. Section 9.4 and section 12.4 of our Data Processing Agreement give the details.

Google Analytics is a further exception, and it applies only if you accept audience measurement. The Google Analytics Terms of Service published for the United Kingdom (last modified 11 January 2024) name Google Ireland Limited as the contracting party, and incorporate the Google Ads Data Processing Terms (version 8.0, 30 May 2024), under which Google acts as our processor and may process the data in any country where Google or its sub-processors have facilities, the United States included. For transfers out of the EEA and the United Kingdom, those terms rely first on any “alternative transfer solution” Google has adopted, and otherwise on the standard contractual clauses they set out. Google states that it relies on the EU-U.S. Data Privacy Framework for transfers from the EEA to the United States, and in certain circumstances on the UK Extension to that framework for transfers from the United Kingdom, with the standard contractual clauses as the fallback. Google also states that data from devices in the UK, the EU and Switzerland is first collected on servers in those regions before being forwarded for processing. We read these documents on Google’s own sites on 7 October 2026. We have not verified Google LLC’s certification on the Data Privacy Framework list ourselves, so we report what Google states and do not present it as our own finding.

Our own mailbox is a further exception. It is hosted by Google Workspace, and Google’s Cloud Data Processing Addendum, which applies to Google Workspace, provides at its section 4.1 that where data leaves the United Kingdom for a country without adequacy regulations, the transfer relies on an alternative transfer solution Google has adopted, or otherwise on the standard contractual clauses it sets out. We read that addendum on Google’s own site on 17 November 2026.

11. Children

The Service is not directed to individuals under 16. We do not knowingly collect data from children.

12. Changes

We may update this Privacy Policy periodically. Material changes will be communicated via email. The “Last updated” date reflects the most recent revision.

13. Contact

For privacy-related inquiries: