Privacy policy

This is a machine translation. Ridian is operated by a German company, and this document was written in German under German law. Only the German version is legally binding; this translation is provided for convenience. Where the two differ, the German text applies.

This policy describes what is processed when using Ridian. It also states the points that cannot be presented as an advantage — for instance that technical support based in the United States can access the operating environment.

1. Controller

PPJ Venture Labs UG (haftungsbeschränkt), Hohenzollernstraße 30, 80801 Munich, Germany, represented by Paul Koch. [email protected] ·full details (German)

If you use Ridian for professional or business purposes or for an organisation, the customer — you or your organisation — is the controller for the connected provider data; we then process it on the customer's behalf under the data processing agreement. If you use Ridian purely privately, we are the controller for that data ourselves.

2. If you only visit this website

When these pages are requested, our delivery provider processes technically necessary connection data: IP address, time, requested address, volume transferred, browser and operating system identifiers. A page cannot be delivered without them.

Legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure operation).

Your privacy choices. We use self-hosted c15t to remember your choice in this browser across getridian.com, Docs, Help and Console. Necessary cookies and local storage keep that choice for up to 180 days; the consent history is kept for twelve months. Fonts are hosted locally. Optional usage analytics stays off until you explicitly consent. You can change or withdraw your choice at any time using “Privacy settings”. Support and sign-in do not require analytics consent.

Optional usage analytics

With your consent, we may record views and interactions across the website, Docs, Help and Console: fixed events such as page views, documentation search, opening the assistant and accepted support requests, a page category, language, timestamp and technical browser identifier. Search terms, chat text, email addresses and calendar contents are excluded from these web events. Public-surface reporting in the admin is aggregated and does not link these events to contacts. The technical browser identifier is nevertheless pseudonymous, not anonymous.

The basis for optional analytics is Art. 6(1)(a) GDPR and, where information is stored on or read from your device, section 25(1) TDDDG. Necessary storage of your choice implements and documents it. Web events are deleted after 90 days. Withdrawal stops further optional collection and does not affect the lawfulness of prior processing. Shared analytics is currently disabled.

Web analytics with PostHog

On this website we use PostHog with your consent (PostHog Inc., processed in the EU cloud). We record page views, clicks on interface elements, browser and device type, and a pseudonymous identifier that recognises returning visits. No session recordings (“session replays”), no form input and no calendar content. Your IP address is not stored. The legal basis is Art. 6(1)(a) GDPR, and § 25(1) TDDDG for storage on your device.

Retention. The events are stored at PostHog. A shorter retention period cannot be configured on the plan we use, so we deliberately do not state a fixed period we could not enforce. Independently of this, we delete the data relating to you without undue delay when you withdraw your consent or ask us to erase it. You can withdraw at any time viaPrivacy settings in the footer; for an erasure request, a message to the address in section 1 is enough.

Optional product analytics

During registration and in your personal privacy settings, you can separately allow us to analyse registration, setup, successful product usage and paid orders you initiated with PostHog in the EU. Events use a shared technical product identifier. Names, email addresses and calendar, chat and email content are not transmitted. A payment is attributed only to the person who initiated the relevant checkout; workspace payments are not attributed to all members.

If you allow this analysis during registration and have also allowed website analytics, the pseudonymous browser identifier can associate the immediately preceding website visit. We consider at most the 30 minutes before registration. Website and product profiles are not permanently merged. If multiple registrations use the same browser identifier, this analysis excludes that association. Existing consents are not extended without this additional choice. You can disable product analytics at any time in your personal privacy settings; email consents remain independent.

Advertising: Meta pixel

On this website we use the Meta pixel with your consent (Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, Ireland). It lets us measure whether our ads lead to an enquiry and build audiences for further ads. What is transmitted: the page view, the fact that an enquiry was submitted successfully together with its type (demo or developer pilot), and your IP address and browser details. We do not transmit form contents such as your name, email address, company or message through the Meta pixel. Separate server-side reporting with a hashed email address is described below.

The Meta pixel runs on this website only. It is not loaded in the signed-in application (console.getridian.com) or in Docs and Help — not even if you consented here. The pixel does not collect usage data there. The consent-dependent server-side reports of confirmed sign-ups and contracts described below are separate.

For the collection and transmission to Meta we are joint controllers with Meta (Art. 26 GDPR); for its own subsequent processing Meta is the sole controller. Meta provides the joint controller arrangement at facebook.com/legal/controller_addendum. This also transfers data to the USA, based on the European Commission’s adequacy decision for the EU-US Data Privacy Framework, under which Meta is certified, supplemented by standard contractual clauses. A level of protection equivalent to the European one cannot be guaranteed in every case, particularly regarding access by US authorities. The legal basis is Art. 6(1)(a) GDPR, and § 25(1) TDDDG for storage on your device. Meta describes its processing in its privacy policy.

Campaign source of enquiries and sign-ups

If you reach us through a link with campaign details, we use them to attribute enquiries and sign-ups to the advertising campaign they came from. Always, including without consent, these are: the link’s UTM values (source, medium, campaign, term, content), a predefined channel label, the path of the landing page without parameters, and the name of the referring website without its full address. Without consent we do not store them in your browser; they stay in the memory of the open page and are passed on through our links.

Only with your consent to the “Advertising” purpose, the ad’s click identifiers are added (Meta: fbclid, _fbc, _fbp). We then also store the source in our own cookie ridian_attr for 90 days: the first touch and the latest touch with campaign details.

When you submit an enquiry or sign up, we store this source with the enquiry or on your user account. It is visible to the people responsible for sales and customer care in our internal management system (see section 3). The legal basis for campaign details without click identifiers is Art. 6(1)(f) GDPR (our legitimate interest in measuring the effectiveness of our advertising); for click identifiers and the cookie it is Art. 6(1)(a) GDPR and § 25(1) TDDDG. You may object under Art. 21 GDPR.

Reporting back to Meta

Only if you have consented to the “Advertising” purpose and came to us through a Meta ad, our server reports a successful enquiry, a sign-up after your email address has been confirmed and a later contract back to Meta (Conversions API). What is transmitted: the click identifier, the type and time of the event, a random event identifier, the value for a contract, and your email address solely as a SHA-256 hash. Name, company and message are not transmitted. Meta may match the hash against its own data. As with the Meta pixel, we are jointly responsible with Meta for this transmission; Meta alone is responsible for its subsequent processing. The legal basis is Art. 6(1)(a) GDPR. Withdrawal stops future reports; events already transmitted are not affected.

Cookies used by these optional services

These cookies are set only after your consent to the respective purpose and are deleted when you withdraw it. Strictly necessary storage for sign-in and for remembering your privacy choice is not listed here.

You can change your choice at any time via Privacy settingsin the footer. Withdrawal takes effect for the future; the lawfulness of processing carried out until then remains unaffected.

Emails from Ridian

You can subscribe to emails about getting started, usage tips, product news, and offers and invitations. All four topics are optional and individually selectable. We use Customer.io (Peaberry Software Inc., USA) as our processor, with an EU workspace and EU endpoints configured. It processes your email address, a technical identifier, language and topic choices. Setup tips also use your chosen goal and coarse setup milestones; we do not transfer calendar, chat or email contents for this purpose. Open and click tracking are disabled. The legal basis for these emails and their personalisation is Article 6(1)(a) GDPR.

For new registrations, we help you finish setup with up to five emails within 14 days. You can decline this series during registration and unsubscribe at any time, free of charge, in your settings or through the link in each email. It ends earlier after your first meaningful use; personal support pauses it. Existing accounts are not enrolled automatically, and earlier three-email subscriptions are not extended. For these messages closely related to the setup you started, we rely on the existing-customer exception in section 7(3) of the German Act Against Unfair Competition and our legitimate interest in helping you get started under Article 6(1)(f) GDPR. The series is separate from optional topic subscriptions.

For this purpose we process the registration notice and any refusal, registration time, an account-bound checksum of the original address, language, coarse setup progress, first meaningful use, and pause/unsubscribe status. Customer.io receives only the status attributes needed for the relevant step. Replies go to our shared support inbox and are recorded as support cases. An authenticated support message or an appointment recorded by our team pauses the series; clicking a link is not treated as a booking. We remove setup attributes from Customer.io when the series ends. We retain the local evidence and final status until account deletion to prevent automatic re-enrolment.

For necessary account, contractual, security and operational messages, we maintain a Customer.io profile containing your verified email address, technical identifier, language and account status even without an optional subscription. Affected users may receive these messages independently of their topic choices. Where processing is necessary to perform our contract with you, it is based on Article 6(1)(b) GDPR; statutory information obligations are based on Article 6(1)(c) GDPR; otherwise, processing is based on Article 6(1)(f) GDPR. Our legitimate interest is reliable communication about secure operation and use of the service, including with contacts at our business customers. These messages contain no advertising.

You can change or withdraw your choices at any time in your personal Ridian settings or through the link in an email. Subscribing again requires your deliberate selection. Security, account and contractual emails are independent of these subscriptions.

We retain the necessary data while a subscription is in use. Setup attributes are removed when you achieve your setup goal or the journey of up to seven days ends. After complete withdrawal, we stop optional emails. A minimal customer profile for necessary account, contractual, security and operational messages remains for the duration of your Ridian account; this does not create a marketing subscription. On account deletion, we delete and suppress the technical provider identifier against recreation. Your topic choices remain in Ridian until you delete your account.

In Ridian, we keep separate records for each topic to demonstrate consent and withdrawal: the necessary link to your verified email address, time, source, language and consent wording version. These records are separate from sending and generally remain until the end of the third calendar year following the end of reliance on the respective consent, including after withdrawal or account deletion. They are then deleted automatically. The legal bases are Article 6(1)(c) in conjunction with Articles 5(2) and 7(1) GDPR, and Article 6(1)(f) GDPR for necessary legal evidence.

Access from third countries, particularly the United States, can occur despite the EU configuration. Our data processing agreement with Customer.io incorporates the EU Standard Contractual Clauses as safeguards for these transfers. You can request a copy of the relevant safeguards from us.

Customer.io also maintains its own history of subscription changes. This survives deletion of the sending profile and is not covered by the automatic expiry of our Ridian records. The data processing agreement generally provides for provider retention for the duration of the agreement and deletion on our instruction at its end. Statutory rights to erasure and restriction remain unaffected; please address these requests to us.

Public documentation assistant

When you submit a question, Ridian sends it, up to three earlier questions in the same chat and relevant public documentation excerpts to OpenRouter for processing by the configured Mistral provider in the EU. This assistant cannot access your Ridian account or calendars. The integration uses the EU endpoint and a fixed provider without global fallback; model-training data collection and prompt caching are disabled in the request. This is not a guarantee about all technical connection and billing data processed by the providers.

Ridian does not persist the chat. It stays in the browser tab and is cleared on reload. Cloudflare processes the IP address for abuse-prevention rate limits. Processing requested assistance is based on Art. 6(1)(b) GDPR; general product questions and abuse prevention rely on Art. 6(1)(f) GDPR (answering your request and secure operation). You can instead search the documentation without AI or contact our team. Do not enter passwords, tokens or private calendar contents.

Support requests and human assistance

The Help form collects your name, email address, topic and message. When handing over from the assistant, you review and confirm the message and your contact details first. The entire chat is not automatically sent to support. Requests and later replies are processed in Ridian's support system at Convex and are available to the team responsible for handling them. Lettermint sends acknowledgements and replies; open and click tracking are disabled for these emails.

The basis is Art. 6(1)(b) GDPR for contractual assistance and pre-contractual requests, otherwise Art. 6(1)(f) GDPR for answering your enquiry. Retention depends on handling the case, necessary evidence and legal retention duties. Support does not require analytics or marketing consent.

Cancellation and withdrawal without signing in

Using “Cancel contracts here” and “Withdraw from contract” in Help, you can cancel or withdraw from a contract without signing in. For this we collect your name, email address, optionally the email address of your Ridian account, the contract concerned, the requested date, an optional reason and the date and time of receipt. The notice is processed like a support request in Ridian's support system at Convex; Lettermint sends the acknowledgement. We match the notice to your contract and carry it out.

The basis is Art. 6(1)(c) GDPR in conjunction with sections 312k and 356a of the German Civil Code (duty to accept and confirm) and Art. 6(1)(b) GDPR (performance of the contract). We keep the details as long as we need them as evidence, usually until the end of the regular three-year limitation period; tax retention duties remain unaffected.

3. If you send an access request

The access form collects your name, work email address, company, optional role and the information you provide about your intended use. We use these details only to assess and answer your request. Our demo forms on advertising landing pages also require a phone number including its country code, so that we can call you personally about your request. Lettermint B.V. in the Netherlands delivers the request to us by email.

To process an accepted enquiry even if email delivery temporarily fails, we also store its details in our Convex database in the Ireland EU region. This includes a technical enquiry reference, handling and delivery status, your optional measurement decision and the version of the notice shown with that decision. Access is limited to people responsible for handling enquiries and operating the service. To limit abuse, we check on submission how many enquiries arrived in the last few minutes. For that we process your IP address solely as a keyed checksum that cannot be turned back into your address and is deleted shortly after.

The legal basis is Art. 6(1)(b) GDPR for steps requested before entering into a contract and, for general business enquiries, Art. 6(1)(f) GDPR (our legitimate interest in responding); for abuse limitation it is Art. 6(1)(f) GDPR (secure operation). We retain an enquiry until it has been resolved and thereafter for no longer than twelve months, so that we can respond if you come back to us. After that we delete it unless a statutory retention duty or an ongoing contract preparation applies. The technical checksums used for abuse limitation are removed within an hour. You can object to this storage and request deletion at any time.

With every enquiry we store its campaign source as described in section 2 (click identifiers only with your consent). So that our team can handle and follow up enquiries, we create a copy of your enquiry — name, email address, company, role, message, language, type of enquiry and source — as a contact with company, deal and callback task in our internal customer management system (Ridian Admin, operated at Convex in the EU region Ireland). Only people responsible for sales and customer care have access. The copy is subject to the same legal basis and retention period as the enquiry itself. If you ask us to delete your enquiry, we also delete or anonymise this copy together with its source and related tasks; statutory retention duties remain unaffected.

Enquiries through Meta Instant Forms

If you submit a contact form in one of our Facebook or Instagram ads, Meta receives your details directly. Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, Ireland, sends us the data you entered or confirmed: your name, work email address, phone number and, depending on the form, details such as team size, company and intended use. This also includes the submission time and technical identifiers for the enquiry, form, page, ad and campaign, where available.

We use these details to call you personally about your enquiry, discuss your needs and arrange a requested Ridian trial. Your phone number is a required field in our Meta contact forms for this callback. We transfer the enquiry to our internal customer management system at Convex (EU region Ireland); the responsible team members receive email notifications through Lettermint and handle correspondence through Google Workspace. Campaign identifiers help us attribute the source of the enquiry. The legal basis is Art. 6(1)(b) GDPR for pre-contractual steps you request, and Art. 6(1)(f) GDPR for general business enquiries and source attribution (answering enquiries and measuring the effectiveness of our advertising). The same retention and erasure rules apply as for the other enquiries in this section.

Submitting such a form does not subscribe you to a newsletter or automated onboarding emails and does not replace separate consent to optional advertising or analytics at Ridian. Meta’s own processing, including possible transfers to third countries, is governed by Meta’s privacy policy. To exercise your rights towards us, use the contact address in section 1.

4. If you create an account

Registration source and setup

When you register, we store a coarse source channel once on your user account, such as Claude, ChatGPT, a landing page or the platform named in an advertising link, together with the campaign source from the registration link as described in section 2: UTM values always, click identifiers only with your consent to the “Advertising” purpose. We do not take over full referrer URLs. Later sign-ins do not overwrite this source. A missing channel remains unknown. Claude and ChatGPT entries do not distinguish directory listings from custom connectors.

To diagnose setup, we record server-confirmed steps with their time and a technical user or flow identifier: registration, assistant setup starting or expiring, a provider connection starting, an account being connected, setup completion, approval, token exchange and the first successful substantive assistant tool call. These records contain no calendar content, tool inputs or outputs, tokens, IP addresses or browser identifiers. The source is retained until account deletion and setup steps for 90 days; expired steps are cleared hourly. These data remain in our operational database and this feature does not send them to advertising or analytics services. The exception is reporting a sign-up to Meta with your consent as described in section 2. It creates no additional analytics cookies or browser identifiers.

The purpose is to understand entry channels and identify technical setup failures, not personalised advertising. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in working setup and effectiveness measurement limited to coarse channels. You may object under Article 21 GDPR by contacting us at the address above.

To return to an assistant request after email verification in a new tab, we temporarily retain the verified authorisation request on your new user account. Only after signing in and verifying your email can you resume it within 30 minutes. It does not itself grant assistant access. We remove it after completed setup, otherwise after 24 hours plus the hourly cleanup interval. The basis is Article 6(1)(b) GDPR.

5. If you connect calendars or other provider features

You grant us access to the calendars and provider features that you select via Google, Microsoft or CalDAV. Calendar, task, contact, mail and room access are enabled separately. We store the credentialsencrypted (AES-256-GCM with a versioned key).

What we store, and why

For every event in a source calendar — a calendar you have set up as the source of a synchronisation — we store a reconciliation state. It contains the event data in normalised form: title, description, location, times, status, recurrence rules, reminders and, where the provider supplies them, the attendees.

This state is required to detect changes. Without it, the entire calendar would have to be rewritten on every run. The synchronisation engine does not read calendars you do not use as a source. If you use the API or an authorised assistant, Ridian reads another connected calendar only for the action you requested and does not add those event bodies to the reconciliation state.

What is written into a target calendar is determined solely by the policy you set. It ranges from “show as busy only” to full details. Actual attendee entries are never copied into target calendars — that would trigger invitation emails to those people.

Purposes of processing

We process the event data of your source calendars in order to

1. carry out the synchronisation you have set up, and
2. give you and applications you have expressly authorised access to your calendar data — for example through our interface or an AI assistant you have connected.

There is no processing for our own purposes: calendar content is not evaluated, not used for statistics about user groups and not used to train models. Operational figures such as the number of runs or error rates contain no event content.

Legal basis. For purely private use, it is Art. 6(1)(b) GDPR (performance of the contract of use). For professional use we process on the customer's behalf, and the controller determines the legal basis. Connecting a calendar is voluntary, but without it Ridian cannot provide synchronisation. No automated decision-making within the meaning of Art. 22 GDPR takes place.

Events may contain special categories of personal data under Art. 9 GDPR, for instance indications of health or beliefs. We do not evaluate them; which details a target calendar receives is determined by your policy.

Tasks, contacts, mail and organisation rooms

When you enable one of these features for a connected account, Ridian processes the following data only to carry out the action you request in the application, API or an assistant you have expressly authorised:

Task, contact, mail and room content is passed directly between the provider and the authorised client and is not retained as application content in Ridian. For safe retries, Ridian keeps hashes and encrypted provider identifiers for up to seven days; these records contain no task title, contact fields, recipient, subject, message body or room address. Audit records contain the actor, provider, action, outcome and a hashed target identifier, but no provider content.

If you connect an assistant, the provider data needed for your requested action is returned to that assistant under the Ridian permissions you approved. Ridian does not use Google user data for advertising, user profiling or training general-purpose AI models.

On the Basic and Professional plans we keep an access log for connected assistants: per call the time, the assistant, the function used and the result, without calendar contents, event titles or inputs. It lets you trace what your assistants did (Art. 6(1)(b) GDPR), and only you see your own entries. On the Free plan nothing is recorded.

In-app assistant

The in-app assistant is optional and is used only after you activate it. For each answer, Ridian sends your request, reviewed earlier messages and the approved calendar, task, contact and account information and, where granted, mailbox content needed for it via OpenRouter to a configured model provider that processes the request in the EU. The connection uses the EU endpoint without a fallback route outside the EU; only providers that do not store requests (zero data retention) are permitted, and use for model training is excluded. The assistant makes changes within the access rights you grant. In approval mode, you approve each prepared action; in automatic mode, which you enable, it can carry out your requests without an additional individual approval. The legal basis is the same as for calendar data above.

Alvin through WhatsApp

The following additional information applies when you link your Ridian account to WhatsApp. We process your WhatsApp identifier, your phone number where available, messages, technical sending and receiving information, and the link to your Ridian account and workspace. Replies may contain information needed for your request from sources authorised for this channel. Processing by Alvin's model providers is described in the preceding assistant section.

Messages are exchanged through the WhatsApp Business Platform and the Cloud API provided by Meta Platforms Ireland Limited. Local Storage Germany is enabled for our WhatsApp number. This setting covers the message content defined by Meta at rest; before that, content may be processed and stored worldwide for up to 60 minutes. It does not restrict all account, usage, connection or Meta contact-book data to Germany. WhatsApp's own privacy information also applies to your use of WhatsApp.

For personal use, handling your requests relies on Article 6(1)(b) GDPR; for business use, your controller determines the legal basis. Linking the channel is independent of advertising consent. You can disconnect WhatsApp from Ridian or stop further messages by sending “stop”. This does not remove copies already delivered to recipients' devices. You can continue using Ridian in the app.

Agent Mailbox

An Agent Mailbox gives your assistant its own email address on ridianmail.com. For this, Ridian processes incoming and outgoing email and saved drafts with sender and recipient addresses, subject, content and attachments; this includes data of the people you correspond with. Lettermint B.V. in the Netherlands receives and sends the email, and it is stored with Convex in the EU region Ireland. Open and click tracking are disabled. Assistants access the mailbox only within the permissions you grant; attachments are analysed only at your request, as described for the assistant above. Email remains stored until you delete it permanently or the mailbox or your account is deleted. The legal basis is the same as for calendar data above.

When the test-mailbox page is visible, a private mailbox is automatically created or recovered without sign-in. The inbox view is embedded from the separate address mailbox.getridian.com. Only there do we save a random access credential in local browser storage (IndexedDB) before creating the mailbox; other getridian.com pages cannot read it. This necessary storage lets you reopen the same mailbox and is independent of your analytics consent. An access backup you download contains the same secret access. Clearing browser data loses browser access without a backup or prior claim; it does not delete the mailbox or its contents, and the mailbox does not automatically expire. Claiming associates the mailbox with your verified account and selected workspace. The test-mailbox page loads no advertising or autocapture scripts. With your usage-analytics consent, we record only fixed events for successful mailbox access and displayed incoming mail, plus page category and language; email addresses, message content and access credentials are excluded.

Ridian's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

6. Retention

The security log is retained in anonymised form: the link to your person is removed, while the record that an event occurred remains.

7. Recipients

Providers that operate Ridian

The providers that process calendar and account data in operating Ridian are listed, with purpose and processing location, at sub-processors. The list is maintained there and forms part of the data processing agreement; it applies equally where we are controller for private use.

The load-bearing services are Convex, Inc. for the application and database in the EU region Ireland, Cloudflare, Inc. for delivery over a global network, and Lettermint B.V. in the Netherlands for system and contact email and the Agent Mailbox.

Providers for our own purposes

These providers process on our behalf under Art. 28 GDPR, but only for our own purposes and not with calendar data from your connections. Processing by Meta for advertising purposes (pixel and reporting back) is described in section 2. Our team's AI assistant may process content from support requests and our customer records, such as name, email address and the history of a request; it has no access to your calendars.

Stripe as an independent controller

The payment itself is processed by Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Dublin 2, Ireland, as an independent controller. Stripe collects the payment method, billing address, VAT ID where applicable, and device and transaction data, and also processes them for its own purposes, in particular fraud prevention and compliance with legal obligations such as anti-money-laundering rules. The basis for the transfer to Stripe is Art. 6(1)(b) GDPR. Details are in Stripe's privacy policy. We do not receive full payment method details from Stripe.

Recipients you initiate

When you connect a provider account, we communicate with that provider on your behalf — Google Ireland Limited, Microsoft Ireland Operations Limited or the CalDAV service you specify. These providers are not our processors; you established the connection yourself. A message you ask Ridian to send is also disclosed by the provider to the recipients you specify.

8. Transfers to third countries

We state this point explicitly because it can be decisive for organisations with strict requirements.

The application is operated by Convex in the EU region Ireland. Application data stored there, backups and failover systems remain within the European Union. The different processing locations described in section 5 apply to messages exchanged through WhatsApp.

For operational monitoring, technical metadata is transferred to service providers in the United States. Convex's technical support is based in the United States and may access the operating environment when handling reported incidents. Convex does not currently offer a variant without this access.

This website is delivered via Cloudflare. Calendar content is not transmitted in the process — the application communicates directly with the EU region.

These transfers, and possible access from the United States by the providers named in section 7, are covered by the European Commission's Standard Contractual Clauses, which form part of the data processing agreements, and for certified providers additionally by the EU-US Data Privacy Framework; for customers in the United Kingdom, supplemented by the UK Addendum.

9. Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interests (Art. 21).

Deleting your account is possible within the application itself. It also removes the copies we created in your target calendars — provided the credentials for them are still valid. Where this fails for individual calendars, we tell you which ones are affected.

You may lodge a complaint with a supervisory authority. The authority responsible for us is the Bavarian Data Protection Authority (Bayerisches Landesamt für Datenschutzaufsicht), Promenade 18, 91522 Ansbach, Germany.

10. Changes

We update this policy when the processing changes. Existing contract customers are informed separately and in advance about new sub-processors.