In force from 19 October 2026. This agreement forms part of the Rendevo Terms of Service and applies to every workspace from that date. It sets out our obligations to you as your processor. It does not constitute legal, tax or accounting advice about your own obligations as a controller.
Regulatory content verified on 7 October 2026, and on 19 October 2026 for the transfers made by AI qualification (sections 9.4 and 12.4). Each provider’s terms carry, in section 9.4, the date on which we read them.
0. How to read this document
Two different sets of personal data pass through Rendevo, and they are not governed by the same thing.
| Whose data | Who decides what happens to it | Which document governs it |
|---|---|---|
| Yours: your account, your workspace, your billing | Vimatech Ltd, as controller | The Privacy Policy |
| Your prospects’: the people who fill in your funnels and book meetings with you | You, as controller | This agreement, under which Vimatech Ltd is your processor |
This agreement covers the second row only. Where it says “you”, it means the Rendevo customer, called the Operator below. Where it says “we”, it means Vimatech Ltd.
1. Parties, subject matter and duration
The Operator is the party that has accepted the Rendevo Terms of Service. The Operator is the controller.
The Processor is:
Vimatech Ltd Private Limited Company, registered in England & Wales Company No. 17001986 Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom Registered with the UK Information Commissioner’s Office, reference ZC155985 Contact for this agreement: [email protected]
Subject matter. The processing of personal data relating to the Operator’s prospects, which Vimatech Ltd carries out on the Operator’s behalf in the course of providing the Rendevo service.
Duration. This agreement takes effect when the Operator accepts the Terms of Service, and on 19 October 2026 for an Operator that accepted them before that date. It continues for as long as Vimatech Ltd processes personal data on the Operator’s behalf. Sections 10 (end of processing), 12 (transfers) and 14 (liability and survival) survive its termination.
Applicable law of data protection. Vimatech Ltd is established in the United Kingdom and is subject to the UK GDPR and the Data Protection Act 2018. Where the Operator is established in the European Economic Area, or where the Operator’s processing falls within the territorial scope of Regulation (EU) 2016/679, that Regulation applies to the Operator’s processing and this agreement is to be read as giving effect to Article 28 of both instruments. References to article numbers below are identical in the two texts.
2. How this agreement is entered into
This agreement is incorporated by reference into the Rendevo Terms of Service. Accepting the Terms of Service means accepting this agreement. No separate signature is required, and no signature is needed for it to bind both parties.
We chose this mechanism because every sign-up creates a controller-to-processor relationship, and a contract that depended on a separate signature for each account would leave most accounts without one, which is the outcome Article 28(3) exists to prevent. Article 28(9) allows the contract to be in electronic form.
Two consequences follow, and they are stated rather than hidden.
Version changes. Where we change this agreement in a way that materially affects the Operator’s rights or our obligations, we notify the Operator by email at least 30 days before the change takes effect. An Operator who does not accept the change may terminate its subscription before the effective date. Changes required by a change in the law, or by a supervisory authority, may take effect sooner where the law leaves us no choice; we say so when we notify.
Operators that need a signed document. Some Operators, particularly larger organisations and public bodies, have internal or regulatory requirements that a data processing agreement be executed as a signed instrument, and some need negotiated terms such as a named audit window or a specific breach notification period. We will execute a signed counterpart of this agreement on request, at [email protected]. The signed counterpart carries the text published here: we do not negotiate variations of this agreement on any plan.
3. Roles, and the two places where ours changes
3.1 The Operator is the controller
The Operator determines the purposes of the processing, which is the qualification of its own prospects, and it determines the essential means: which questions its funnels ask, and therefore which personal data is collected; what the qualification rules do with the answers; who is contacted and how; and how long the resulting records are kept. Vimatech Ltd determines only non-essential technical means, such as the database schema, the hosting arrangement and the security measures.
3.2 Where Vimatech Ltd is a controller in its own right
On the same records, for two purposes of our own, Vimatech Ltd is a controller and not a processor. This is stated rather than glossed over: a processor that uses data for its own purpose becomes a controller for that purpose, whether or not the contract admits it.
| Purpose | Our role | Legal basis |
|---|---|---|
| Storing the Operator’s submissions and returning them to the Operator | Processor | The Operator’s instructions, Article 28 |
| Abuse prevention, anti-spam and rate limiting on public funnels, using the IP address and user agent recorded with a submission | Controller | Legitimate interests, Article 6(1)(f), recital 49 |
| Platform security and security event logging | Controller | Legitimate interests, and Article 32 |
3.3 What we will not do, in any role
We do not use the content of the Operator’s submissions, bookings or prospect records for product analytics, for benchmarking, for training machine-learning models, or for improving the service. There is no purpose for which we would be entitled to do so, and doing it would be processing outside the Operator’s instructions under Article 28(10).
How far down the chain this reaches. The paragraph above is an undertaking by Vimatech Ltd, and we keep it. Each sub-processor listed in section 9.4 is bound by its own data processing terms, which limit it to processing on our instructions; the undertaking above is not copied into those terms word for word. For one of them, the transactional email provider, its published sub-processor list includes two entities whose stated purposes are artificial intelligence and self-hosted large language models, and its standard terms do not say which data reaches them. Section 9.4 sets out what its documents say and what they do not.
Artificial intelligence, only where an owner switches it on. One feature of the service sends prospect data to a language model: AI qualification, which is off in every workspace until an owner of that workspace switches it on (section 9.6). The providers it uses are named in section 9.4, and the undertaking above applies to what they receive: we use none of it for any purpose of our own. No other feature of the service sends prospect data to an artificial-intelligence or machine-learning provider.
We do not place any measurement, analytics or advertising tag of our own on an Operator’s public funnel pages. That rule follows the page, not its address: it applies to every public booking page, whether it is served from its own domain or from a path of the application, such as app.rendevo.com/book. One script does reach the pages served at app.rendevo.com without being part of our code: Cloudflare, which serves that address, adds its Web Analytics script to the pages it serves there, booking pages included. It sets no cookie and stores nothing on the prospect’s device; it sends Cloudflare the address of the page, the page the prospect came from and loading timings, and we see the result only as totals per page. It serves our own purpose of knowing which pages are used and whether they load well, not the Operator’s, and section 3.3 of our Privacy Policy describes it. At the date above the service also offers no way for an Operator to add one: there is no tag or pixel setting in the product. If one is added, this section will say so before it is offered.
Our own audience measurement, and why it does not reach prospect data. Vimatech Ltd measures the audience of rendevo.com and of the signed-in application with Google Analytics, for visitors and users who accept it. That measurement concerns the Operator’s own users, for our own purpose, and is governed by the Privacy Policy, not by this agreement. Google Analytics never runs on a public booking page, and in the signed-in application it never sends what an Operator’s user sees about a prospect: screens are reported by their kind (for example “lead detail”), never by their real address or title, both of which can carry a prospect’s name or email address. The account milestones our server sends to Google count events, such as a first booking, without any content from the record that produced them. If that guarantee failed, prospect data would reach Google for a purpose of ours, which the first paragraph of this section forbids.
That sentence is about tags, and it should not be read as saying that nothing about a visit is recorded. One thing is: where the Operator leaves source capture switched on, a submission keeps the campaign parameters of the link the prospect followed and the origin of the page that sent them. Section 4.3 describes exactly what is kept, and section 5 treats the setting as the Operator’s instruction. None of it is sent to anyone else, and none of it is used for any purpose of ours.
4. The processing, described
4.1 Nature and purpose
We host and operate the Rendevo service. On the Operator’s behalf, that means: presenting the Operator’s qualification funnel to a prospect and recording the answers, progressively as the prospect enters them and before any submission, so that a funnel started and not finished is kept as an unfinished submission; evaluating the Operator’s own decision rules against those answers and recording the outcome; scheduling, rescheduling and cancelling meetings between the prospect and the Operator; writing those meetings into a calendar the Operator has connected; sending transactional email about them; where the Operator switches it on for an event, sending up to two reminder emails, which the Operator writes, to a prospect it has qualified who has not booked (section 4.5); where the Operator switches it on for an event, sending one email, whose text is ours, to a prospect whose meeting the Operator marks as a no-show, offering another time (section 4.7); delivering event notifications to endpoints the Operator has configured; computing the reports the Operator reads about its funnels, its bookings and, on the Team plan, the booking load of its own members (section 4.4); showing, next to a lead whose email address is at a domain other than a public email provider, the icon that domain publishes for itself (section 4.6); and producing the CSV exports the Operator downloads.
4.2 Categories of data subjects
- Prospects: individuals who open, fill in or submit an Operator’s public funnel.
- Individuals who book, reschedule or cancel a meeting with the Operator through Rendevo.
- Any third party whose personal data a prospect volunteers in a free-text answer. The Operator controls which questions are asked and is therefore responsible for whether such answers are invited at all.
- The Operator’s own members, meaning its employees or contractors who host meetings in its workspace, for the per-member reports described in section 4.4 only. For their accounts themselves, Vimatech Ltd is the controller and the Privacy Policy applies.
4.3 Categories of personal data
Taken from what the service actually stores, not from a generic list.
| Category | What it is | Where it lives |
|---|---|---|
| Identity and contact details | Prospect name, email address, telephone number and the country selected alongside it | funnel_submissions, bookings |
| Funnel answers | The prospect’s answers to the Operator’s questions, stored as free-form structured data. The Operator determines the content of this field entirely. Answers and contact details are saved as the prospect goes, from the first answer or contact detail entered, so a prospect who abandons the funnel leaves an unfinished submission (status partial) holding what was entered until then |
funnel_submissions.answers |
| Qualification outcome | The calculated score, the accept or reject decision, the rule that produced it, and the metadata of that decision | funnel_submissions |
| Meeting records | Start and end time, timezone, duration, the assigned host, meeting status, meeting link, notes, cancellation reason | bookings |
| Technical data collected on submission | IP address, user agent, start and completion timestamps | funnel_submissions |
| Source of the submission | Where the Operator leaves source capture switched on: the five standard campaign parameters of the link the prospect followed (utm_source, utm_medium, utm_campaign, utm_content, utm_term), each cut to 150 characters, and the origin of the referring page, meaning its scheme and domain (and a port, if it is not the standard one), never its path or its query string. No advertising click identifier is kept, such as gclid or fbclid. Capture is on unless the Operator switches it off for the workspace. Built on the server side and not yet in service at the date above: the public funnel pages do not yet send these values. A campaign parameter can carry whatever the Operator put in its own link, including an identifier or an address that points to one recipient; the Operator should not put personal data in its links |
funnel_submissions (utm_source, utm_medium, utm_campaign, utm_content, utm_term, referrer_origin) |
| Payment records | Where the Operator takes payment through its own Stripe account: the amount, currency and status of each payment, and the Stripe event as delivered to us, which carries the payer’s name, email address, billing address and the last four digits of the card. The content of that event is erased after 30 days (section 8.2) | prospect_payments, prospect_payment_events |
| Reminder sent | Whether and when each of the two reminders of section 4.5 was sent for a submission, so that neither is sent twice | funnel_submissions |
| No-show email | For an event: whether the email of section 4.7 is switched on and since when. For a booking: when that email was sent, and a fingerprint of the link it carries with the link’s expiry, never the link itself | no_show_follow_up_settings, bookings |
| Opt-out box hidden | For an event, who in the Operator’s team (name and email) declared that its prospects are companies only or have already agreed to these emails, which of the two, which emails it covers, when, and the version of the declaration, and when and by whom it was switched off; kept while the workspace exists and for 6 years after its deletion, as evidence of the Operator’s declaration, even if that person’s account is deleted; and, on each submission made while the box was hidden, that it was and under which declaration | prospect_opt_out_waivers, funnel_submissions |
| Unsubscribe list | For each workspace, the email addresses that have unsubscribed from its reminder and follow-up emails: the address in lower case, when, and how (the link in an email, the button of the mail app, the refusal on the booking page, or an entry added by the Operator). Nothing else, and no link to any submission, booking or funnel | A list per workspace, kept apart from submissions and bookings |
| Event delivery content | Where the Operator has configured a webhook endpoint and a delivery to it fails, the content of the attempted delivery and the endpoint’s response. Successful deliveries do not store this content. | webhook_deliveries |
| Company icon | The domain of a lead’s email address, when it is not a public email provider, and the icon that domain publishes, as described in section 4.6 | lead_favicons, one record per domain |
4.4 Reports about the Operator’s own members
On the Team plan, the Operator can read four reports about the people who host meetings in its workspace: the share of each member’s bookable hours taken by Rendevo bookings over the last 4, 8 or 12 complete weeks; the bookings already scheduled for each member over the next 7 or 14 days; the prospects routed to each member; and the recorded outcome of each member’s past meetings (completed, no show, not recorded). They are computed from the bookings and the availability schedules the service already holds, when the report is opened, and are not stored.
The Operator is the controller of these reports, and we are its processor. The purpose is the Operator’s: managing the workload of its own team. The legal basis is the Operator’s to establish; for an employer that will generally be its legitimate interest, since an employee’s consent to their employer is not a reliable basis.
What the reports are built to show, and what they are not. These limits are in the service, and the Operator cannot remove them:
- Owners and admins see every member. A member sees their own figures only, never a colleague’s and never a team median.
- Figures are shown by week at the finest. There is no ranking, no score and no individual alert, and nothing about a member’s activity in the application is used.
- The booking load counts only meetings booked through Rendevo against the hours the member has opened for booking. It is not a measure of working time or performance, and the report says so. Past weeks are measured against the member’s current availability schedule.
- A no show is the prospect’s behaviour, not the member’s, and it is presented that way.
- A member who leaves stays named in these reports for 12 months after leaving, then is grouped under “Former members”. When a member is removed, we record the workspace, the person, their role, when they joined, when they left and who removed them, with no reason and no free text. A member who still hosts upcoming meetings cannot be removed until those meetings are reassigned or cancelled. The bookings themselves stay in the workspace and follow the Operator’s own retention (section 8.1).
- Each member sees, in the application, a notice that the owners and admins of the workspace can see their booking load and meeting outcomes by week.
What remains the Operator’s. Informing its members before the reports are used, consulting employee representatives where its law requires it, and carrying out any impact assessment are the Operator’s obligations as employer and controller. Those obligations differ from one country to another and we do not describe them here. No per-member figure is included in an export, and there is no email digest of these reports. A bookings export does name the host of each booking, because that is part of the booking record.
Status at the date above: built, and switched off in the service. Before it is switched on, we tell Operators by email, and the date it was switched on will be written here.
4.5 The reminders to a qualified prospect who has not booked
What it is. For each event, the Operator can switch on up to two emails to a prospect whose submission is qualified (by the Operator’s rules or by hand) and who has not booked a meeting. Each is sent after a delay the Operator chooses, counted from the moment the submission last became qualified: one hour, four hours, one day, two days or three days, the second always later than the first when both are on (by default, one hour and one day). Each has its own switch, either can be on without the other, and the Operator writes the subject and text of each. Switching it on is the Operator’s instruction to send it (section 5). Each is sent at most once per submission, so a submission never receives more than two, and no address receives more than two from the same workspace in any 30 days. Neither is sent to a submission waiting for review, disqualified or pending, to a submission qualified before the Operator switched that reminder on, or more than 7 days after it was due. Everything is checked again at the moment of sending: no email leaves if the prospect has booked, even if that meeting was later cancelled, if the submission is no longer qualified, if the Operator has switched that reminder off, if the submission has been deleted, or if the address is on the workspace’s unsubscribe list.
How we treat it. We do not read what the Operator writes, so we treat every reminder as direct marketing, whatever its content. That decides what Rendevo adds and the Operator cannot remove: a closing section that says why the prospect receives the email, a link to unsubscribe, the List-Unsubscribe and List-Unsubscribe-Post headers that let a mail app unsubscribe in one action, and the name, contact email and postal address the Operator gives when switching the reminder on. If any of those three is missing, the reminder is not sent. We do not check them; they are the Operator’s statement of who it is. No open or click tracking is added to the reminder.
What the Operator answers for. The Operator is the controller of the reminder and of the list of who unsubscribed. It is responsible for having a lawful basis for the reminder and, for individuals, a lawful route under the electronic marketing rules where they are; for the content it writes; and for the information it gives its prospects. Its booking page shows, on the step where contact details are entered, that the business may send this reminder, with a way to refuse it there, unless the Operator has hidden that box for the event by the declaration described in section 4.1 of the Terms of Service; we record that declaration and do not check it; the Operator’s own privacy notice remains its responsibility. The rules the Operator accepts for this email are in section 4.1 of the Terms of Service.
The link in the reminder. It takes the prospect to the calendar of the event, to pick a time, without filling in the form again. It is specific to one submission, opaque, and does not contain the prospect’s name or email address. It shows neither the answers nor the qualification, and it cannot change them. It stops working once the prospect has booked, once the submission is no longer qualified or has been deleted, and 7 days after the reminder that carries it is sent.
Unsubscribing. An unsubscribe applies to the whole workspace, not to one event, and stops every reminder and follow-up email from that workspace to that address. It does not stop the confirmation and reminders of a meeting the prospect books. The unsubscribe page names the Operator as the business responsible for the prospect’s data and gives its contact email. The Operator sees its list and can add an address to it; it cannot remove one, and we refuse to send to an address on the list even on the Operator’s instruction (section 5, unlawful instructions).
Special category data. Rendevo is not designed to process the special categories of personal data described in Article 9, nor data relating to criminal convictions under Article 10. The free-text answer field makes it technically possible for an Operator to ask a question that elicits such data. An Operator that does so is responsible for identifying an Article 9 condition and for the additional measures that follow, and should tell us before doing so, because the measures in section 7 were not designed on that assumption.
Children. Rendevo is not directed at children. An Operator whose funnels may be completed by children is responsible for the age verification and consent requirements that apply, and we have built nothing to support that case.
4.6 The company icon shown next to a lead
What it is. In the Operator’s lead list, a lead whose email address is at a domain other than a public email provider, such as Gmail, Outlook, iCloud, Proton or Yahoo, is shown with the small icon that domain publishes for itself. When a member of the workspace who can see that lead displays it, and the icon is not already held, our server in the United Kingdom requests the file /favicon.ico from that domain, then from its www address if the first gives nothing. The request carries the domain name and nothing else from the lead: no name, no email address, no answer and no cookie, and it identifies itself as Rendevo. We use no third-party icon or logo service, so the list of the Operator’s prospect domains is given to no one.
What the domain’s own server learns. As with any request to a website, the server that holds the domain, and any provider that server uses, learns that a Rendevo server asked for its icon at that time. It does not learn which Operator, which person or why. Where the domain belongs to one individual, for example a domain in their own name, that is the only information about them that leaves the service, and it goes to the server they chose for their own domain.
What we keep. The icon and the domain it came from, for 7 days, or the fact that the domain gave no usable icon, for 24 hours (section 8.2). The icon is held once per domain rather than once per workspace, so that the same domain is not requested again for each Operator, and it is shown only to members of a workspace that has a lead at that domain and may see that lead. On a personal domain, the icon may show its owner.
4.7 The email after a meeting marked as a no-show
What it is. For each event, the owner of the workspace can switch on one email to the prospect when the Operator marks a meeting as a no-show. Switching it on is the Operator’s instruction to send it (section 5), and marking a meeting as a no-show is what sends it. The text is Rendevo’s, and the Operator cannot edit it: it says the meeting did not take place as planned, without saying who missed it, and offers a link to pick another time. It is sent shortly after the meeting is marked, once the delay to undo the mark has passed, and not at all if the meeting is set back to held before then.
When it is not sent. Everything is checked again at the moment of sending. No email leaves if the Operator has switched it off for the event; if the meeting was marked before it was switched on; if the meeting ended more than 7 days earlier; if the booking was cancelled or its prospect data deleted; if the booking is not linked to a submission, or that submission has been deleted; if the prospect has another upcoming meeting with the workspace; if the address is on the workspace’s unsubscribe list; if the Operator’s name, contact email or postal address is missing; or if another email has already been sent to the prospect after that meeting. A booking receives at most one email after the meeting.
Who can receive it. Only a prospect whose submission was made on a contact step that said the business may email them once after the meeting and offered a way to refuse it, or on a contact step where the Operator had hidden that box for the event by the declaration described in section 4.1 of the Terms of Service, which we record and do not check.
How we treat it. As direct marketing, like the reminders of section 4.5, because it invites the prospect to resume a sales conversation with the Operator. The sender name is the Operator’s name and replies go to the Operator’s contact email. Rendevo adds the same closing section, which the Operator cannot remove: why the prospect receives the email, a link to unsubscribe, the List-Unsubscribe and List-Unsubscribe-Post headers, and the Operator’s name, contact email and postal address. No open or click tracking is added to it.
The link in the email. It lets the prospect pick another time for the same event without filling in the form again. It is specific to one booking, opaque, and does not contain the prospect’s name or email address; we keep only a fingerprint of it and its expiry. It shows neither the answers nor the qualification, and it cannot change them. It stops working once the prospect has booked again, once the meeting is no longer marked as a no-show, once the submission has been deleted, and 14 days after the email is sent.
What the Operator answers for. The same as for the reminders in section 4.5: the lawful basis, the lawful route under the electronic marketing rules for individuals, and the information it gives its prospects, together with the accuracy of the no-show mark that sends the email. The rules the Operator accepts for this email are in section 4.1 of the Terms of Service. An unsubscribe from a reminder stops this email too, and the reverse.
5. Documented instructions
We process the personal data covered by this agreement only on the Operator’s documented instructions, including as to transfers, unless we are required to do otherwise by law. Where the law requires it and does not prohibit us from saying so, we inform the Operator before processing.
The Operator’s instructions are, and are limited to:
- This agreement and the Terms of Service.
- The configuration the Operator makes in the service: its funnels and questions, its decision rules, its scheduling settings, its connected calendar, its email templates, its webhook endpoints, its connected Stripe account, its source capture setting, its retention setting for prospect records (section 8.1), and whether AI qualification is on, with the criteria and the instructions it writes for it (section 9.6).
- The actions the Operator takes in the service, including deleting a funnel and downloading an export, and its requests to us to delete records, a workspace or an account, which we carry out by hand (section 8.3).
- Any further written instruction the Operator sends to [email protected], to the extent it concerns processing we are technically able to perform. An instruction that would require us to build something, or that falls outside the scope of the service, is not binding on us unless we accept it in writing.
Unlawful instructions. We inform the Operator if, in our opinion, an instruction infringes the UK GDPR, the EU GDPR or other applicable data protection law. We may suspend the processing concerned until the instruction is withdrawn or amended. We are not obliged to make our own legal assessment of an Operator’s instructions, and the absence of an objection from us is not an endorsement of an instruction’s lawfulness.
Instruction in relation to payment. Where an Operator connects its own Stripe account and enables payment on a funnel, that enablement constitutes the Operator’s instruction to transmit the relevant prospect data to that Stripe account. Stripe then acts as the Operator’s own provider under the Operator’s direct contract with Stripe, not as our sub-processor. Stripe’s processing of that data falls outside this agreement. See section 9.
Instruction in relation to exports. When an owner or admin downloads a CSV export, that download is the Operator’s instruction to hand it a copy of the records it covers. Once the file is on the Operator’s device it has left our systems: its storage, its sharing and its deletion are the Operator’s responsibility, and nothing in section 7 applies to it any longer.
Optional tags. The service offers no advertising or measurement tag on funnel pages at the date above (section 3.3), so there is no instruction of this kind to give.
6. Confidentiality
We ensure that every person authorised to process personal data under this agreement is bound by an appropriate obligation of confidentiality, whether a contractual one or a statutory one, and that the obligation survives the end of their engagement.
Who has access, at the date above. Vimatech Ltd is a very small company. Access to production personal data is limited to its director. No employee, contractor or support provider has that access. Before anyone else is given it, they will be bound by a written confidentiality obligation that survives the end of their engagement.
We grant access to personal data only to those who need it to perform our obligations under this agreement, and only to the extent needed.
7. Security
We implement appropriate technical and organisational measures under Article 32, taking into account the state of the art, the cost of implementation, the nature, scope, context and purposes of the processing, and the risk to individuals.
7.1 Measures in place today
Each of these was checked against our source code, and where stated against the live configuration, on the date given.
| Measure | What it is |
|---|---|
| Encryption in transit | TLS on all connections to the service and on all outbound event deliveries. Event delivery endpoints are restricted to the standard web ports, and delivery to a private, loopback or link-local address is refused. |
| Encryption of stored credentials | Connected calendar access and refresh tokens, and webhook signing secrets and custom header values, are encrypted at the application layer before being written to the database. |
| Password protection | Passwords are stored hashed with bcrypt at cost factor 12. New and changed passwords are checked against the Have I Been Pwned breach corpus using the range API, which sends only the first five characters of a hash and never the password, the full hash or the email address. |
| Access control | Every prospect record is scoped to a workspace. Access is governed by workspace membership and by roles (owner, admin, member). |
| Event signing | Outbound event deliveries are signed with a per-endpoint secret that the Operator can rotate. |
| Two-factor authentication | Available on password accounts, using an authenticator app. Up to three authenticators may be registered per account. Ten single-use recovery codes are issued at set-up, shown once, and stored salted and hashed with bcrypt, the same scheme as passwords above. |
| No administrative reset of a second factor | No support route or administrative command can turn off an account’s second factor, and none can shorten the deferred unlock below. Two automated tests hold that shut: one permits exactly two places in our code to clear a second factor and fails the build if a third appears, the other permits exactly one place to set the date the deferred unlock ends and fails if either scheduled task grows an option that could move it. |
| Deferred unlock of a second factor | The only route back for an account holder who has lost every authenticator and every recovery code. Initiated by the account holder from the sign-in screen, and only after the password has been accepted. Initiation emails the account address and every owner and admin of every Workspace the account belongs to; that notification cannot be suppressed by any setting, preference or role. The period is seven full days, is fixed, and is not shortenable by any interface, administrative access or maintenance command. During it the account is unchanged and existing sessions continue, a persistent banner is shown throughout the application, and reminder emails are sent on day one and on day six. Any sign-in with an authenticator code or a recovery code cancels the request, as does a cancellation link carried by each of those emails to each of those recipients, which means any notified owner or admin can end it in one click, whether or not the account holder wants it ended. On completion the second factor is removed, all authenticators and all recovery codes are destroyed, all sessions are revoked, the password is invalidated so that re-entry requires an email reset, and connected calendars are deactivated. One request is in flight at a time, a new request does not restart the period, and one request may complete every 30 days; only completions count against that allowance, so a cancelled request does not consume it and may be started again immediately. Stated plainly: with this measure in place the strength of an account is a first factor plus seven days of notice rather than two factors, a trade accepted deliberately in place of ad hoc exceptions granted by hand. |
| Exports of prospect records | Only an owner or admin can download an export, and only after re-entering their password recently. The file is written as it is downloaded and is not kept on our side. It contains no IP address and no user agent. Any cell that begins with a character a spreadsheet would read as the start of a formula (=, +, -, @, a tab or a carriage return) is prefixed with an apostrophe, free-text answers included. Each export is recorded in the security event log: who, which workspace, which kind of export, which filters and how many rows, never the content. Built and switched off in the service at the date above. |
| Encryption at rest of stored records | The database’s storage is encrypted at rest by the hosting provider, and so are its automated backups and the uploaded images. Checked on the live configuration on 5 October 2026. |
| Security event logging | Security-relevant events are recorded in a dedicated log, retained for 365 days and purged automatically thereafter. |
| Automatic retention enforcement | Scheduled daily jobs enforce the retention limits in section 8 without human discretion. |
7.2 Personal data breaches
We notify the Operator without undue delay after becoming aware of a personal data breach affecting personal data processed under this agreement, and in any event in time for the Operator to meet its own obligation under Article 33(1). Our notification describes, to the extent known: the nature of the breach and the categories and approximate number of data subjects and records concerned; the likely consequences; and the measures taken or proposed. Where we cannot provide all of it at once, we provide it in phases without further undue delay.
We do not notify a supervisory authority or a data subject on the Operator’s behalf. That obligation is the controller’s, and exercising it for the Operator would require a judgement about the Operator’s context that we are not in a position to make.
We do not commit to a fixed number of hours. Our commitment is the one above: without undue delay, and in time for the Operator to meet its own deadline under Article 33(1).
8. Retention
8.1 Prospect records: the Operator sets the period, the service applies it
How long the Operator keeps its prospects’ data is a decision for the Operator as controller, taken under Article 5(1)(e). The service gives each workspace a setting to record that decision and applies it automatically. The setting is part of the Operator’s documented instructions (section 5).
What the setting offers. It treats two kinds of submission separately: a finished submission, which the prospect completed, whatever its status afterwards, and a partial submission, which the prospect started and left before the end. Each workspace chooses one of three modes.
| Mode | Finished submissions | Partial submissions |
|---|---|---|
| Suggested | Deleted 24 months after their last activity | Deleted 30 days after their last activity |
| Keep | Never deleted automatically | Never deleted automatically |
| Custom | Deleted after the period the Operator sets, from 1 day to 3,600 days or from 1 to 120 months, or never | Deleted after the period the Operator sets, from 1 to 365 days, or never |
A workspace that has made no choice is in Suggested mode. The suggested periods are a starting point offered by the product. They are not a statement of what the law requires of the Operator, and choosing them does not relieve the Operator of choosing a period suited to its own purposes.
The suggested periods apply from 19 October 2026. That date is the starting point for workspaces in Suggested mode: no submission is deleted under a suggested period before that period has run in full from that date, so the first deletions of partial submissions can occur from 18 November 2026 and the first deletions of finished submissions from 19 October 2028. A workspace that has chosen Keep or Custom is not affected by that date: its own choice applies from the moment it is made, subject to the delay below.
Last activity is the latest of: the creation of the submission, the moment the prospect started it and the moment they finished it, the last change of its status, and the creation and the start time of any booking linked to it. A submission linked to an upcoming booking is therefore never deleted.
Nothing is counted retroactively. Time that elapsed before automatic deletion was introduced in the service does not count towards any period.
Who can change the setting. Only an owner of the workspace, after confirming their password again. Each change is recorded with its author, its time and the setting before and after it, and every owner of the workspace receives an email describing it. A shorter period takes effect only 7 days after the change, and until then the longer of the two periods applies, so that an owner who did not make the change has time to reverse it. A longer period takes effect immediately.
What deletion does. A scheduled job runs every day. It deletes each expired submission with its answers, the results of AI qualification and the reasons given for them (section 9.6), any request by the prospect for a review by a person, the records of AI qualification requests about it (section 8.2), its qualification decisions and its status history. On the bookings linked to that submission which have already ended, it erases the prospect’s personal data: name, email address, telephone number, notes, cancellation reason, location details, time zone and booking metadata. The booking itself remains, with its date and time, its event type, its status and the team member who held it, so that the Operator’s statistics stay accurate. A booking that has not yet taken place is never touched. The workspace’s unsubscribe list (section 4.5) is never touched either.
Payments hold deletion back. Where a payment taken through the Operator’s Stripe account is linked to the submission or to one of its bookings, neither the submission nor the booking’s prospect data is deleted:
- while the payment is pending, still processing, or disputed, until that is resolved;
- once the payment has succeeded, has been refunded in full or in part, or a dispute about it has been lost, until 120 days have passed since the last update of the payment. This is a period we chose so that the Operator can still answer a dispute; it is not a statement of the card networks’ own deadlines.
The payment record itself follows section 8.2.
What the setting does not reach. It applies to the records held in the service. It does not reach copies that have already left it: the event in a team member’s connected calendar, emails already sent, data already delivered to the Operator’s webhook endpoints or to its Stripe account, and files the Operator has exported (section 5). Bookings that are not linked to any submission are not covered either.
Deleting other records, on request. Bookings made without a funnel submission are kept until the Operator asks for their deletion. To have them deleted, or to have a single booking or submission deleted before its period ends, the Operator asks at [email protected], and we delete them by hand under section 11.
8.2 Periods we do set, and why
These periods apply to our own technical records. Where a scheduled job applies one, it runs once a day, so the record is deleted or erased within a day after its period ends. They are not settings, and an Operator cannot extend them: a controller cannot instruct us to keep a duplicate longer than the purpose that justifies it.
| Record | Period | What happens | Counted from |
|---|---|---|---|
| Content of a failed event delivery: the attempted payload and the endpoint’s response | 30 days | The content is erased; the delivery record itself survives | The delivery attempt |
| The delivery record itself: event name, status code, response time, attempt number, outcome, identifiers and timestamps | 365 days | The record is deleted | The delivery attempt |
| Security event log | 365 days | The record is deleted | The event |
| Content of a payment event received from Stripe | 30 days | The content is erased; the record survives as the reference that stops the same event being applied twice | Receipt of the event |
| The unsubscribe list of a workspace (section 4.5) | As long as the workspace exists | Deleted with the workspace (section 8.3). It is not reached by the Operator’s retention setting, by the deletion of a submission, a booking or a funnel, or by a prospect’s request to have their data erased, because deleting an entry would start sending to someone who refused | The unsubscribe |
| Application error logs, which can contain an email address or an IP address | 14 days on the application server, 30 days in the log service | The log is deleted | The entry |
| Raw response of the language model, before the results in section 9.6 are taken from it | 30 days | The response is erased; the results stay with the submission, under section 8.1 | Receipt of the response |
| Network address of the submission on the record of an AI qualification request: the IPv4 address, or the first half (/64) of an IPv6 address, used only to limit how many requests one network can trigger on a funnel in a day | 2 days | The address is erased from the record | The request |
| Record of each AI qualification request, without the answers or the response: model, provider that answered, version of our instructions, the Operator’s criteria at that time, a keyed fingerprint of what was sent that cannot be read back, time, outcome code, cost and response time | 365 days, or earlier when the submission is deleted under section 8.1 | The record is deleted | The request |
| Icon of the domain of a lead’s email address, with that domain (section 4.6) | 7 days; 24 hours where the domain gave no usable icon | The record is deleted | The request to the domain |
The content of a successful event delivery is never stored. Where a delivery succeeds, the Operator has received the content, and keeping a second copy of its prospects’ data would serve no purpose we could defend.
Each of these periods may be extended for an individual record where we are required to preserve it, for example because it is relevant to a legal claim, an investigation or a regulatory request. The extension is recorded on the record itself and applies to that record alone.
8.3 Deleting a workspace or an account
An Operator that wants a workspace or an account deleted asks at [email protected], and we handle the request by hand, subject to checking that it comes from an owner of the workspace concerned.
- Export first, if the Operator wants one. Before deleting, we open the export described in section 10, whatever the plan, or send the records by hand while the export is switched off.
- Collection stops when we act on the request. The Operator’s public funnels are taken down first, so that no further prospect data is collected for an Operator that has asked to leave.
- The data is deleted within 30 days of the request, the same period our Privacy Policy gives for account data, and we confirm it to the Operator when it is done.
This request is how a workspace or an account is deleted.
8.4 Backups
The database is backed up automatically by the hosting provider, in the same region, and those backups are kept for 7 days, checked on the live configuration on 5 October 2026. A record deleted from the database therefore disappears from the automated backups no later than 7 days after its deletion. At the date above, no manual snapshot of the database holds Rendevo data.
9. Sub-processors
9.1 General authorisation
The Operator gives a general written authorisation for us to engage sub-processors, subject to this section. Where we engage one, we impose on it by contract data protection obligations that are, in substance, those we owe under this agreement, and we remain fully liable to the Operator for its performance.
9.2 Changes, and the right to object
We maintain the current list at section 9.4.
Sub-processors that serve every workspace. We notify Operators by email of any intended addition or replacement of one of these sub-processors at least 30 days before it begins processing. An Operator may object on reasonable data-protection grounds within that period, in writing to [email protected]. If we cannot resolve the objection, the Operator may terminate its subscription for the affected part of the service without penalty, with a refund of any prepaid, unused fees. We do not treat an objection as a breach, and we do not require the Operator to justify it beyond stating its grounds.
Sub-processors of an optional feature. Some features are off in every workspace until an owner of that workspace switches them on, and send nothing to anyone while they are off. Section 9.4 lists their sub-processors separately, and the screen on which an owner switches the feature on names them again. Switching the feature on from that screen is the Operator’s specific written authorisation of those sub-processors for that workspace. We record which owner gave it, when, and which version of the screen and of the list they saw. While the feature is off in a workspace, no data from that workspace reaches those sub-processors, and no notice about them is owed to that workspace. Where the feature is on, we notify the owners of the workspace by email at least 30 days before any addition or replacement among those sub-processors takes effect, and an owner may object as above; we may instead show the new list on the same screen and keep the workspace on the previous list until an owner accepts the new one. In every case an owner or admin can switch the feature off at any time, which stops every transfer to those sub-processors from that moment and leaves the rest of the service unchanged.
Changes that are not additions. Removing a sub-processor is not an addition or a replacement. Nor is performing ourselves, on infrastructure already listed in section 9.4, a function that a sub-processor used to perform, where no provider receives data it did not receive before. In those cases we update the list and tell Operators by email when the change takes effect, without a notice period.
We send every notice under this section by email to the owners of the workspaces concerned, at the address of their Rendevo account, and we update section 9.4 on the same day.
9.3 Stripe is not a sub-processor of ours
Where an Operator enables payment, the Operator connects its own Stripe account and contracts directly with Stripe under Stripe’s own terms. Funds pass from the prospect to the Operator’s Stripe account. Vimatech Ltd never holds them, takes no commission, and is neither the seller, the merchant of record, nor a payment service provider for those transactions.
Stripe is therefore a recipient of prospect data on the Operator’s instruction, and the Operator’s own provider. It is not our sub-processor, its processing is outside this agreement, and the terms governing it are those between the Operator and Stripe. The Operator is responsible for naming Stripe in its own privacy notice to prospects.
9.4 Current sub-processors
This list covers sub-processors that touch prospect data, which is the data this agreement governs. Providers that only handle the Operator’s own account and billing data, such as Paddle, are not sub-processors under this agreement; they are described in the Privacy Policy, where Vimatech Ltd acts as controller. Calendar providers and Stripe, which receive prospect data under the Operator’s own account with them, are described in sections 9.3 and 9.5.
The list was established by reading the source code on the date at the top of this document, not from a list of vendors we believe we use. A service that is installed but never called is not listed.
| Sub-processor | What it does with prospect data | Where | Transfer mechanism |
|---|---|---|---|
| Cloudflare, Inc. (delivery of the application’s pages and of the requests they send) | Serves the pages of the application at app.rendevo.com, including the public funnel and booking pages, and carries every request those pages send to our API. It therefore handles the prospect’s IP address, browser headers and the content of each request in transit, including the answers and booking details the prospect submits. We do not use it to store prospect data. Its check against automated bots may also place a security cookie, cf_clearance, in the prospect’s browser on those pages, for about one year; it is not used to measure the visit (Privacy Policy, section 3.3). Its Web Analytics script also runs on those pages for our own count of page views, without a cookie (section 3.3 above). In service since 6 October 2026 |
United States company, global network, including nodes outside the United Kingdom and the EEA | Standard contractual clauses in Cloudflare’s data processing addendum, version 6.4 effective 3 April 2026, which section 6.1 of Cloudflare’s self-serve subscription agreement incorporates into our account by reference, with the UK Addendum for the United Kingdom part. Where we act as your processor, clause 6.2(a)(i) of that addendum applies Module Three (processor to processor); Module Two applies to our own account data, where we are controller. Read on Cloudflare’s own documents on 18 September 2026, and clause 6.2(a)(i) read again on 18 October 2026. Cloudflare’s statement that it complies with the EU-U.S. Data Privacy Framework is not verified and we do not rely on it |
| Amazon Web Services (the application’s API, the database and uploaded images) | Holds every record this agreement governs. Infrastructure created on 2 October 2026, in service since 6 October 2026 | Region eu-west-2, London, United Kingdom. Contracting party: Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 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, incorporated into our account by section 1.14.1 of the AWS Service Terms. Read on AWS’s own documents on 5 October 2026. Storage is in the United Kingdom, our own place of establishment, so storage is not an onward transfer out of the UK: see section 12.4. Under section 12.1 of the addendum, AWS does not move data out of the region we selected except as necessary to provide the services we use or to comply with the law or a binding order. For data subject to the EU GDPR that is nevertheless transferred to a third country, section 12.2.2 applies the processor-to-processor standard contractual clauses (Module Three) where we act as processor. The addendum names no separate instrument for the United Kingdom element of such a transfer. Addendum read on AWS’s own site on 18 October 2026 |
| Plus Five Five, Inc., trading as Resend (transactional email) | Sends the confirmations, reminders and notifications the service generates, including the notice a prospect receives when the Operator’s team cancels their meeting. These carry the prospect’s name, email address and the details of their meeting. Where the Operator switches them on, it also sends the reminders of section 4.5, whose text the Operator writes, and the email of section 4.7 after a meeting marked as a no-show. Subscribed on 16 September 2026, sending since 6 October 2026 | United States. The provider’s own data processing addendum states that its primary processing operations take place in the United States, and its published sub-processor list names twenty-two further sub-processors, all in the United States | Standard contractual clauses. The provider’s addendum applies the EU standard contractual clauses, Module Two, to transfers out of the EEA, and the same clauses as amended and completed by the UK Addendum to transfers out of the United Kingdom. Read on the provider’s own documents on 16 September 2026. The provider also asserts certification under the EU-U.S. Data Privacy Framework and its UK Extension; we could not verify that certification on the Framework’s own list, and we do not rely on it |
Sub-processors of AI qualification (section 9.6). These receive data only from a workspace in which an owner has switched AI qualification on, under section 9.2. Their terms were read on the providers’ own published documents on 18 and 19 October 2026.
| Sub-processor | What it does with prospect data | Where | Transfer mechanism |
|---|---|---|---|
| OpenRouter, Inc., 169 Madison Ave #2404, New York, NY 10016, United States (routing to the model) | Receives each AI qualification request from our service, which carries only what section 9.6 lists, and forwards it to the single endpoint we fix: Claude Haiku 4.5 run by Amazon Bedrock in the AWS region OpenRouter labels eu-west-1 (Ireland). Fallback to any other endpoint, provider or model is disabled, and every request is restricted to endpoints that OpenRouter lists as not retaining request content. Prompt logging and OpenRouter’s own use of inputs and outputs are switched off on our account. Its data processing agreement commits it to delete inputs and outputs promptly after the output is generated. It keeps metadata about each request without its content, such as tokens used and latency. OpenRouter decrypts and processes each request in the United States before passing it on |
United States. OpenRouter’s agreement, Schedule 2: hosting on Google Cloud Platform in US regions | OpenRouter’s Data Processing Agreement, last updated 26 August 2026, which forms part of its terms of service and binds our account without a separate signature. For transfers out of the United Kingdom, section 13.3 of that agreement applies the International Data Transfer Addendum issued under section 119A of the Data Protection Act 2018, appended to the EU standard contractual clauses that section 13.2 enters on the basis of Module Two (controller to processor), with us as exporter. For prospect data we act as your processor; the agreement does not offer Module Three. OpenRouter, Inc. is not on the Data Privacy Framework List, checked on the list maintained by the US Department of Commerce on 19 October 2026, so the UK Extension to that framework does not apply to it. Section 12.4 gives the position under UK law |
| Amazon Web Services, through Amazon Bedrock, engaged by OpenRouter | Runs Claude Haiku 4.5, a language model made by Anthropic, PBC, on the request OpenRouter forwards, and returns the result described in section 9.6. Amazon states that model providers have no access to the accounts in which Amazon Bedrock runs their models, nor to prompts and completions: Anthropic receives no prospect data. OpenRouter lists this endpoint as one that does not retain request content | Ireland, AWS region eu-west-1, as labelled by OpenRouter and confirmed as the serving region on 19 October 2026 |
Sub-processor of OpenRouter, which section 5.1 of its agreement requires to bind it by a written agreement no less protective than its own, and which remains liable for it under section 5.4. Ireland is in the European Economic Area: under UK law, a transfer to it is treated as approved by regulations (section 12.4) |
Third-party web fonts. The public funnel pages have served their fonts from our own origin since 20 September 2026, and the email templates load no remote font. Neither Google Fonts nor Bunny Fonts receives prospect data, so neither is listed.
Hosting and the database, decided on 15 September 2026, created on 2 October 2026. The provider that hosts the Rendevo API and its database is Amazon Web Services, region eu-west-2, London, United Kingdom. The infrastructure was created there on 2 October 2026. The pages of the application are served by Cloudflare, as the table above says, and every record this agreement governs is stored in the database, not at Cloudflare.
eu-west-2 is in the United Kingdom, not in the European Union. The eu- prefix is a region name chosen by the provider, not a statement of location, and the United Kingdom has been a third country for the purposes of Regulation (EU) 2016/679 since it left the Union. Nothing in this agreement, in the Privacy Policy or in any marketing page may describe the service as hosted in the Union or in the EEA. What this means for an Operator established in the EEA is in section 12.2, and it is the reason that section exists.
Transactional email, decided on 16 September 2026. The production email provider is Resend, the trading name of Plus Five Five, Inc., of 2261 Market Street #5039, San Francisco, CA 94114, United States. The account is subscribed and the sending domain mail.rendevo.com is configured.
In service since 6 October 2026. From that date, messages about meetings, including those sent to prospects, go out through this provider.
Two things follow from this provider being established in the United States, and neither of them applies to the hosting. First, it is a transfer to a third country at both ends: from us, established in the United Kingdom, and from an Operator established in the EEA whose prospects’ data passes through us. Second, it is, with Cloudflare and, where AI qualification is switched on, OpenRouter, one of the sub-processors in this agreement whose transfer mechanism is an actual set of clauses rather than an adequacy decision, so section 12.4 governs the United Kingdom element of it in practice and not only in principle.
Established on 17 September 2026: no separate signature is required. The provider’s data processing addendum is incorporated into our account by the agreement itself. Its preamble states that the addendum “shall become legally binding upon Customer entering into the Agreement or upon execution of this Addendum”, its signature blocks are “provided for reference purposes only”, and clause 6.3.9 provides that “[b]y entering into this DPA, the parties are deemed to have signed the EU SCCs incorporated herein, including their Annexes”. Read on the provider’s own published documents, which carry a last update of 27 August 2026. The transfer mechanism therefore exists in our contract and not only in a published template.
The provider’s sub-processor list, read on 17 September 2026. The list, last updated by the provider on 27 August 2026, names twenty-two sub-processors. Each entry carries a name, a country and a purpose, and nothing else, and every one of the twenty-two is located in the United States. Two of them bear on the undertaking in section 3.3: Anthropic, PBC, whose stated purpose is “Artificial Intelligence”, and RunPod, Inc., whose stated purpose is “Self-hosted LLMs”. Those quoted strings are the whole of each entry.
What the provider’s documents say about those two, and what they do not. They do not say which personal data reaches them. The list states no data categories. The addendum authorises sub-processors generally, on a “need to know” basis, across the scope described in its Annex I, which expressly includes message content. A commitment not to train artificial-intelligence or machine-learning models on customer content does exist in the provider’s Enterprise Terms, at their section 6.4, and it expressly excludes message bodies and recipient personal information from any training corpus. That document binds the provider only towards a customer under an Order Form that references it, and the words “train”, “machine learning” and “artificial intelligence” appear nowhere in the standard terms of service, the data processing addendum or the privacy policy that govern an ordinary account. We do not rely on that commitment and we do not pass it on to the Operator. What binds this provider towards us is its data processing addendum, which limits its processing, and that of its sub-processors, to the provision of its service on our instructions. Section 3.3 binds Vimatech Ltd; we do not represent that its wording binds this provider beyond what its addendum says. The provider has been sending the service’s email since 6 October 2026 on that basis.
Why Cloudflare is listed. The front end of app.rendevo.com, public funnel and booking pages included, is served by Cloudflare, and the requests those pages send to our API pass through it. A prospect’s answers therefore travel through Cloudflare on their way to the database, which makes Cloudflare a sub-processor, listed in the table above with its transfer mechanism.
9.5 Destinations the Operator chooses, which are not our sub-processors
Calendars. Where one of the Operator’s members connects a Google or Microsoft calendar, the service reads that member’s busy times, creates, moves and cancels events in that calendar, and asks the calendar to generate a meeting link (Google Meet or Microsoft Teams). Each event names the prospect as its guest, with their name and email address, and carries a title with the prospect’s name, a description with their email address, their telephone number and any booking notes, and the times. Since 27 September 2026, Google also emails the prospect an invitation from that calendar when the meeting is booked. When the meeting is moved or cancelled, Google emails the prospect an update or a cancellation notice, whether the change is made by the Operator’s team or by 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. Each of these messages carries the same details as the event. Connecting the calendar is the Operator’s instruction to write those events into it. The calendar, and everything written into it, is held by Google or Microsoft under the terms of the account the member connected, which is the Operator’s or its member’s account and not ours; the provider is therefore the Operator’s own provider for that data, in the same way as Stripe (section 9.3), and not our sub-processor. At the date above, no credentials for Microsoft calendars are provisioned in the service, so no Outlook calendar can be connected and no data reaches Microsoft.
Webhooks. Where the Operator configures a webhook endpoint, we send event data, which may contain prospect personal data, to the URL the Operator supplies. That destination is the Operator’s own system or its own provider. It is not our sub-processor, we have no contract with it, and the Operator is responsible for the lawfulness of that transfer and for any onward transfer it entails.
We apply security controls to that delivery regardless: the destination must use a public address and a standard web port, delivery to private, loopback and link-local addresses is refused, redirects are not followed, and each delivery is signed with a secret the Operator can rotate.
The same applies to Stripe, as described in section 9.3.
9.6 AI qualification, an optional feature
Off unless an owner switches it on. AI qualification is off in every workspace. Only an owner of the workspace can switch it on, on a screen that names the sub-processors it uses (section 9.4) and states what is sent to them. Switching it on is the Operator’s instruction under section 5 and its authorisation under section 9.2. We record which owner switched it on, when, and the version of the screen and of the sub-processor list, and we keep that record for as long as the workspace exists and for 6 years after its deletion, as evidence of the authorisation. Any owner or admin can switch it off at any time; from that moment no further request leaves our service for that workspace.
What is sent, and what never is.
| Sent to the sub-processors in section 9.4 | Never sent |
|---|---|
| The funnel’s questions and the prospect’s answers to them. Free-text answers are first passed through automatic masking of email addresses, telephone numbers, web addresses and the name the prospect entered | The prospect’s name, email address and telephone number fields |
| The qualification criteria the Operator wrote, and the instructions it writes for the model (up to 2,000 characters), both sent as written, without masking | The prospect’s IP address and user agent |
| The campaign parameters and the referring origin of the submission (section 4.3), the booking details and any payment record |
Nothing else from the submission or the workspace is sent. The identifier attached to each request designates the workspace, never the prospect.
The Operator’s criteria and instructions are sent as written. They are meant to describe what the Operator is looking for, not any one prospect, and the Operator does not put a prospect’s personal data in them. Personal data the Operator writes there anyway is sent on its own instruction and under its responsibility as controller, and this agreement applies to it.
Pseudonymised, and still personal data. Removing the contact fields and masking free text does not stop an answer from being personal data. A free-text answer can still identify the prospect, or another person, through what it describes, and automatic masking can miss a name or an address written in an unusual form. What is sent is personal data, and this agreement applies to it in full. In a funnel where AI qualification is on, the Operator should not ask a question that invites special category data (section 4.3) or details that identify a person by themselves. Uploaded documents, such as a CV or a PDF, are not sent; sending them would change this section, and would be shown on the activation screen for a new acceptance before any document is sent.
What comes back, and where it goes. For each submission the service receives a score, a recommendation (qualify, disqualify or review) and, for each of the Operator’s criteria, whether it is met, not met or unknown, with a reason of one short sentence, limited to 200 characters, together with the model’s overall confidence. These are stored with the submission as part of its qualification outcome (section 4.3), shown to the Operator, available to the Operator’s rules, and deleted with the submission under section 8.1. They are kept as long as the submission because they are what lets the Operator explain an outcome and reconsider it (section 9.7); only the raw response is erased earlier (section 8.2). The model is instructed to keep its reasons free of personal data, but a reason can restate what the prospect wrote, so it is treated as personal data like the answer it describes. They are estimates produced by a language model and can be wrong. The text sent to the model is not stored separately: it is built from the submission each time.
The Operator’s rules decide. The results decline nobody. A rule that uses them can only send the submission to review, where a member of the Operator’s team decides; it cannot decline a request. The assessment runs after the Operator’s other rules have let the request through, and a submission sent to review can still be booked.
What the providers may do with it. We do not use what is sent or returned for any purpose of our own (section 3.3). OpenRouter’s Data Processing Agreement makes it our processor and commits it to delete inputs and outputs promptly after generating the output, prompt logging being off on our account; before deletion it may classify them automatically, solely to detect misuse of its service. Its privacy policy, last updated 31 August 2026, states that it does not use inputs or outputs for model training. Section 6.5 of its terms of service, last updated 31 August 2026, also gives it a licence to categorise inputs for the usage statistics it publishes, without associating them with any user or organisation; its data processing agreement does not expressly exclude that use. Whether an endpoint retains request content is OpenRouter’s reading of the provider’s published policy, which its agreement says is not a guarantee of the provider’s compliance. That is why the paragraph on what is sent comes first: the protection that does not depend on anyone else’s terms is what never leaves our service.
Not for decisions about work, education, credit, insurance, housing or public services. The Operator may not use AI qualification to recruit or select people for employment or work, to assess candidates or workers, to decide on admission to education or training, or to assess a person’s eligibility for credit, insurance, housing or a public service. The feature is neither designed nor assessed for those uses, and it cannot be switched on in a workspace whose profile is “Recruiter”. An Operator that uses it for those purposes acts outside its instructions and outside the purpose for which we offer the feature.
9.7 Decisions taken without a person
A rule that declines a request without anyone reviewing it is a decision based solely on automated processing. A rule that uses the results of AI qualification cannot decline a request (section 9.6). Where such a decision is a significant decision for the prospect, meaning that it has a legal or similarly significant effect, Articles 22A to 22D of the UK GDPR, inserted by the Data (Use and Access) Act 2025 and in force since 5 February 2026, apply to the Operator as controller; for an Operator subject to the EU GDPR, Article 22 of that Regulation applies instead. Whether a declined request has that effect depends on the Operator’s business, and we cannot assess it for each Operator.
What remains the Operator’s. Establishing the legal basis for the decision; telling its prospects, in its own privacy notice, that it uses AI qualification and that their answers are sent to the providers listed in section 9.4; giving them information about decisions taken without a person, letting them make representations, obtain human intervention and contest them, as Article 22C of the UK GDPR requires; and carrying out any impact assessment required by Article 35.
What the service provides for it. AI qualification cannot be switched on in a workspace unless each of the following exists in the service:
- the review outcome, which sends a submission to a person instead of declining it;
- a way for the prospect to ask the Operator for review by a person, on the screen that declines a request. The request is always recorded with the submission and shown on it in the service. The owners and admins of the workspace also receive an email with a link to it, for up to 20 requests per workspace and per day, counted in the workspace’s time zone; requests beyond that are recorded and shown in the same way, without an email. A request changes nothing by itself: a member of the Operator’s team decides;
- the ability for the Operator to reverse a decline;
- for every outcome, a record of the rule and its version, the results used, the model, the version of our instructions to the model and the time, kept as long as the submission, so that the Operator can explain and reconsider it.
10. Return and deletion at the end of processing
At the Operator’s choice, we delete or return all personal data processed under this agreement when the provision of the service ends, and delete any existing copies, unless applicable law requires us to retain them.
The choice is the Operator’s, not ours. Article 28(3)(g) gives the controller two options, and a product that offered only deletion would remove one of them. Where an Operator asks us to delete its account or a workspace, it is offered an export of its prospect records before anything is deleted (section 8.3).
How the records are returned. An owner or admin downloads them as CSV files from the service: one for submissions, with the answers, and one for bookings. On Pro and Team the export is part of the plan. On any other plan, Free included, an Operator that is closing its account writes to [email protected], and we open the same export for that workspace for 30 days, so that it can take its records before they are deleted. Returning an Operator’s data does not depend on the plan it pays for. The export is built and switched off in the service at the date above; until it is switched on, the records are returned by hand on the same request.
Because deletion is by request (section 8.3), the offer of an export is made in our reply to that request, not by a screen in the service.
Where a workspace is transferred rather than deleted, the member accepting it is told, in the acceptance text, that they are taking on responsibility for third parties’ personal data and are becoming the controller of it. Accepting without being told that is not acceptance.
Retention required by law. Where we are required by UK or EU law to retain personal data after the end of the service, we retain it only to that extent, only for as long as required, and we continue to protect it under section 7. We inform the Operator of the requirement unless the law prohibits it.
11. Assistance to the Operator
11.1 Requests from data subjects
Prospects have no relationship with Vimatech Ltd and will generally write to whichever address they can find. Three rules apply.
- We never act on a prospect’s request ourselves. We forward it to the Operator concerned, and we tell the prospect that we act as a processor and that their request has been passed to the controller.
- We never confirm to a prospect whether their data exists in the service, or with which Operator. Confirming would disclose the Operator’s data and would open an enumeration channel: anyone could learn who had applied to, or requested a meeting with, whom.
- We assist the Operator, by appropriate technical and organisational measures and insofar as this is possible, in fulfilling its obligation to respond to requests under Chapter III: access, rectification, erasure, restriction, portability and objection.
How that assistance is given, at the date above. The Operator asks at [email protected], and we find, extract or delete that prospect’s records for it, by hand. The export of all submissions and bookings (section 10) also serves access and portability requests that cover the whole workspace.
11.2 Assistance with Articles 32 to 36
Taking into account the nature of the processing and the information available to us, we assist the Operator in ensuring compliance with:
- Article 32, security of processing, by maintaining and documenting the measures in section 7 and by making the information in this agreement available.
- Article 33, breach notification, as described in section 7.2.
- Article 34, communication to data subjects, by providing the information the Operator needs to make its own communication. We do not communicate with the Operator’s prospects on its behalf.
- Article 35, data protection impact assessments, by providing information about our processing that is not otherwise available to the Operator. We do not carry out the assessment, which is the controller’s.
- Article 36, prior consultation, by providing the information the Operator needs for a consultation with its supervisory authority.
Charges. We do not charge for assistance under this section where a request is proportionate to the service the Operator pays for. Where a request is manifestly excessive or repetitive, we may charge a reasonable fee based on our actual costs, having first told the Operator what it will be and given it the chance to withdraw or narrow the request. We do not make assistance conditional on payment of a fee we have not disclosed in advance.
12. International transfers
12.1 The position
Vimatech Ltd is established in the United Kingdom. Personal data processed under this agreement is therefore processed in the United Kingdom, and in the locations of the sub-processors listed in section 9.4. The hosting decided on 15 September 2026 keeps the API and the database in the United Kingdom as well, in the London region of Amazon Web Services. Requests to the application pass through Cloudflare’s global network on their way there, as section 9.4 records. That region is named eu-west-2 by the provider, which is a label and not a location: it places nothing in the European Union.
12.2 Operators in the European Economic Area
An Operator established in the EEA, or whose processing is subject to Regulation (EU) 2016/679, transfers personal data to a processor outside the Union when it uses Rendevo. That transfer is covered by the European Commission’s adequacy decision in respect of the United Kingdom, Implementing Decision (EU) 2021/1772 of 28 June 2021, as amended by Implementing Decision (EU) 2025/2574 of 19 December 2025, which permits transfers to the UK without further safeguards for as long as it remains in force.
The decision expires on 27 December 2031. Article 2 of Implementing Decision (EU) 2025/2574 replaces Article 4 of Implementing Decision (EU) 2021/1772 with the following: “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.” Read in the text of the decision itself, as published by the Commission, on 17 September 2026.
Two things qualify that date. The decision provides for periodic review at least every four years, and recital 132 states that the Commission should, at the latest six months before the decision ceases to apply, start the procedure to extend it by a further four years where the adequacy finding is still justified. An extension is a stated intention and not a certainty, and the decision can be suspended, repealed or amended before its term if the finding stops holding. That is the reason for the standby clause in section 12.3, which needs no further act by either party to take effect.
12.3 The standby clause, if adequacy lapses
Because adequacy decisions are periodically reviewed and can be amended, replaced or allowed to expire, this agreement incorporates the standard contractual clauses adopted by the European Commission in Implementing Decision (EU) 2021/914, Module Two (controller to processor), as a dormant term.
Those clauses take effect automatically, without any further act by either party, in respect of any transfer that ceases to be covered by an adequacy decision, from the moment that coverage ceases. Where they take effect:
- The Operator is the data exporter and Vimatech Ltd is the data importer.
- The optional docking clause applies; the option for a general authorisation of sub-processors under Clause 9 applies, with the 30-day notice period in section 9.2; the redress option under Clause 11(a) does not apply.
- The description of the transfer in Annex I is taken from sections 1 and 4 of this agreement, and the technical and organisational measures in Annex II are those in section 7.
- For Clause 17, those clauses are governed by the law of Ireland; for Clause 18, disputes arising from them are resolved by the courts of Ireland. Section 15 does not apply to them.
12.4 Operators in the United Kingdom, and onward transfers
Where the Operator is established in the United Kingdom, the processing takes place in the United Kingdom and no restricted transfer arises between the Operator and us.
Where personal data is transferred onward to a sub-processor outside the United Kingdom or the EEA, each such transfer relies on a mechanism recorded against that sub-processor in section 9.4. Where the mechanism is the standard contractual clauses, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, issued by the Information Commissioner under section 119A of the Data Protection Act 2018, applies to the UK element of that transfer.
We use that Addendum, and not the standalone International Data Transfer Agreement, because it is the instrument our sub-processors’ own data processing terms already incorporate. For Cloudflare and for the transactional email provider, the Addendum is completed and treated as executed in their own terms (section 9.4).
AI qualification, where an owner switches it on. Two transfers follow, and they do not rest on the same thing.
- United Kingdom to the United States, to OpenRouter. OpenRouter, Inc. is not on the Data Privacy Framework List, so the Data Protection (Adequacy) (United States of America) Regulations 2023, which cover only US organisations shown on that list as participating in its UK Extension, do not apply. The transfer is made subject to appropriate safeguards under Article 46 of the UK GDPR: the Addendum described above, which section 13.3 of OpenRouter’s agreement applies. As Article 46(1A) requires since 5 February 2026, we rely on it only having considered, reasonably and proportionately, that the protection of the data after the transfer is not materially lower than under UK law, taking into account that only the content listed in section 9.6 is sent and that it is not kept once the result is returned.
- United States to Ireland, to Amazon Web Services. This is OpenRouter’s onward transfer to its own sub-processor, under the clauses it entered with us. Ireland is a member of the European Economic Area, and under paragraphs 4 and 5 of Schedule 21 to the Data Protection Act 2018 a transfer to an EEA state is treated as approved by regulations made under Article 45A of the UK GDPR, read on legislation.gov.uk on 19 October 2026.
For an Operator subject to the EU GDPR, the transfer to OpenRouter relies on the EU standard contractual clauses that section 13.2 of its agreement enters.
12.5 Representative in the European Union
At the date above, Vimatech Ltd has not designated a representative in the Union under Article 27 of Regulation (EU) 2016/679, and none is named or implied here. If one is designated, this section will name it.
13. Audits and information
We make available to the Operator all information necessary to demonstrate compliance with Article 28, and we allow for and contribute to audits, including inspections, conducted by the Operator or by an auditor it mandates.
In practice, and in order of what will actually satisfy most Operators:
- Information first. On request to [email protected], we provide this agreement, the current sub-processor list, the description of our technical and organisational measures in section 7, and answers to a written security questionnaire. For the great majority of Operators this is sufficient, and it is the fastest route.
- Audit on request. Where information is not sufficient, the Operator may audit, on 30 days’ written notice, no more than once in any twelve-month period, during business hours, subject to confidentiality undertakings, and in a manner that does not disrupt the service or compromise the confidentiality of other Operators’ data. We do not grant access to the data of any other Operator, and no audit may require it.
- Without the notice or the frequency limit where the Operator is required to audit by a supervisory authority, or following a personal data breach affecting the Operator’s data.
Costs, and which plans. The audit right applies on every plan, Free included, because Article 28(3)(h) does not depend on what the Operator pays. Each party bears its own costs of an audit: the Operator pays for its auditor, and we do not charge for the time we spend supporting an audit that stays within the limits above.
14. Liability
The limitations and exclusions of liability in the Rendevo Terms of Service apply to this agreement and to any claim arising under it, as if set out here.
Where the standard contractual clauses have taken effect under section 12.3, Clause 12 of those clauses governs liability for the transfers they cover, and the limitations in the Terms of Service do not restrict it.
Nothing in this agreement limits either party’s liability to a data subject, or the rights of a data subject, or any liability that cannot lawfully be limited.
15. General
Order of precedence. Where this agreement conflicts with the Terms of Service on a matter of data protection, this agreement prevails. Where the standard contractual clauses have taken effect under section 12.3 and conflict with this agreement, those clauses prevail.
Governing law. This agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction, in each case subject to section 12.3 in respect of the standard contractual clauses, and subject to any mandatory rule of the Operator’s own jurisdiction that cannot be excluded.
Severability. If any provision is held invalid, the rest continues in effect.
Contact. [email protected] for anything under this agreement; [email protected] for a signed counterpart.