Privacy policy

Who is responsible

OPALITH SAS is the controller of the personal data described in this policy, for the website at rdv.dev and for the app at app.rdv.dev. Its registered office is at 254 rue Vendôme, 69003 Lyon, France (RCS Lyon 991 600 156).

We have not appointed a data protection officer. Questions about this policy and requests about your data go to hello@rdv.dev. The publisher and host details are in the legal notice.

One case works differently. When a business uses rdv.dev to take bookings, that business decides why and how it uses its guests' data, and we process that data on its behalf. If you booked a meeting with one of our customers, read If you booked a meeting through rdv.dev first.

What this policy covers

• The website at rdv.dev: its pages, the contact form, and the links into the app.
• The app at app.rdv.dev: accounts, workspaces, calendar connections, event types, availability, bookings, branding, text reminders, and the public API, MCP server and webhooks.
• Public booking pages, at addresses such as rdv.dev/{workspace}/{event}, for the part of the processing we decide ourselves: delivering the page, keeping it secure, and running the service.

rdv.dev is a service for businesses. It is not meant for children, and we do not knowingly collect data from anyone under 16.

On the website

Contact form. When you write to us from the contact page, we receive what you type: your name, your email address, your company if you give it, and your message. We use them to answer you and to follow up on that conversation. We do not add you to a mailing list.

Audience measurement. We use Vercel Web Analytics and Vercel Speed Insights to count page views and to measure how fast pages load. They set no cookie, store nothing on your device and keep no identifier for you. We only see aggregated figures: pages viewed, referring sites, countries, browsers and devices, and load times.

Language and theme. The NEXT_LOCALE cookie remembers the language you chose, so the next page you open is in the same language. Your light or dark theme choice is kept in your browser's local storage. Both are strictly necessary for what you asked for and need no consent.

Server logs. Our host processes the technical data every web request carries (IP address, browser, page requested, time) to deliver the page and to protect the service against abuse.

Links into the app. The "Start free" links pass on the referral code (ref) and the campaign parameters (utm_*) that were in the address you arrived with, so the app knows how you found us. The website itself does not store them.

In the app

Account. Your first and last name, email address, and password if you choose one (we store only a hash of it). Your job title, phone number and LinkedIn profile address if you add them. Your time zone, language and profile picture. The version of the terms and of this policy you accepted, and when.

Sign in with Google or Microsoft. We receive your name, email address and account identifier, your profile picture from Google, and the domain of your organisation for a Google Workspace account. We use them to create your account, sign you in, and offer to join your company's workspace. See Google user data and Microsoft user data.

Workspaces and membership. The workspaces you create or join, your role in each, how you joined (invitation, code, company domain or request), the invitations you send and the email addresses they go to, join requests, and the company domains a workspace claims.

Security. For each signed-in session, the IP address and browser (user agent) it was opened from, and when. You can see your sessions and sign them out in Settings → Security. We also count requests per account and per hashed IP address to limit abuse.

Files. Profile pictures, workspace logos and brand fonts are stored in a public file store (Vercel Blob), after we re-encode them. Anyone who has a file's address can open it: that is how a logo appears on a booking page or in an email. They are deleted with the account or workspace they belong to.

Scheduling. Your event types, weekly hours and booking rules, and the bookings made with you: date and time, location or video link, status, the guest's details (see If you booked a meeting through rdv.dev), and who made the booking, a person or an agent.

Calendars. Only if you connect one, and only as described in Google user data and Microsoft user data.

Branding from your website. When an owner or admin asks rdv.dev to read the workspace's website, our servers fetch the address they give and the pages, style sheets, logos and fonts it points to, then suggest logos, colours and fonts. Nothing is applied until someone reviews and ticks it. When this option is enabled, Firecrawl (United States) is asked for a second reading of sites we cannot read ourselves; it receives the website address and reads its public pages. An analysis and the logos it staged are deleted 30 days after it ends, or 7 days after if it failed or was cancelled. What you apply becomes part of your brand.

Referral. If you sign up through a link that carries a referral code, we record that code with your account to know who referred you.

Agents, API and webhooks. The API keys and OAuth clients your workspace creates (keys are stored only as a hash), the webhook endpoints it registers and the deliveries sent to them, and a record of the requests made with them.

Text reminders. Sent to a guest only when the guest gives a mobile number and ticks the box that asks for reminders. See If you booked a meeting through rdv.dev.

Payments. When a workspace subscribes to a paid plan, Stripe collects the card details; we never see the full card number. We keep the billing contact, billing address, VAT number, the card's brand and last four digits, and the invoices.

Emails we send. Address confirmations, password resets, invitations, booking confirmations and alerts about a calendar that stopped working. They are sent by Mailtrap.

Why we use it, and on what legal basis

Google user data

rdv.dev uses Google in two separate ways. Each asks for its own permission, and signing in with Google never gives access to your calendar.

Sign in with Google

We ask only for the basic scopes: openid, email and profile. We receive your name, email address, profile picture, Google account identifier and, for a Google Workspace account, your organisation's domain. We use them to create your account, sign you in, and offer to join your company's workspace. This permission gives no access to your calendar, email or files.

Google Calendar

You connect a calendar separately, in Settings → Connected accounts, through a connection window run by Nango. rdv.dev asks for two permissions:

• calendar.events.freebusy, to see when you are busy on the calendars you connect;
• calendar.events.owned, to create, update and delete the events rdv.dev books for you.

What we do with them:

• Free/busy. We read the start and end times of your busy periods to work out which times can be booked. We read them live, when slots are shown or a booking is made, and do not store them.
• Events. When a meeting is booked, moved or cancelled, we create, update or delete the matching event in your calendar, with its title, time, guest, location or video link and description. We keep the event's identifier so we can update or delete it later.
• Nothing else. We do not store the titles, descriptions, attendees or any other content of your calendar events in our database.
• Tokens. Your OAuth tokens are held by Nango, our processor for calendar connections (United States). They never reach our database or our code. Our requests to Google, and Google's responses, pass through Nango.

Who sees it:

• We share your availability, meaning when you are free and never what your events contain, only with the people who book you through your booking pages, and with the API clients, MCP clients and webhooks that you or your workspace authorise.
• Nango, our host and our database provider process it as our processors, under contract, only to provide the service (see Who receives personal data).

What we never do:

• We do not use Google user data for advertising, and we do not sell it.
• We do not use it to develop, improve or train generalized artificial intelligence or machine learning models.
• No one at OPALITH SAS reads it, unless you give us permission for specific data (for example in a support request), it is needed for security (for example to investigate abuse), or the law requires it.
• We transfer it to no one, except to provide the features you use, to comply with the law, or as part of a merger, acquisition or sale of assets, after telling you.

Revoking access and deleting data:

• Disconnect the calendar in Settings → Connected accounts. We revoke the Google grant, delete the connection at Nango and on our side, and stop reading or writing that calendar.
• You can also remove rdv.dev from your Google Account's permissions page at any time.
• Deleting your account disconnects every calendar the same way. Events already created stay in your calendar: they are yours.

rdv.dev's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Microsoft user data

Microsoft works the same way, with two separate permissions.

Sign in with Microsoft

We ask for openid, email, profile, offline_access and User.Read, the basic permissions to read your name, email address and account identifier. We do not import your Microsoft profile photo. Because the organisation running a Microsoft account sets its email address, we always confirm that address by email before it is trusted.

Outlook calendars (Microsoft Graph)

You connect an Outlook or Microsoft 365 calendar separately, through Nango. rdv.dev asks for Calendars.ReadWrite, which Microsoft requires both to read when you are busy and to write the events rdv.dev books.

• Busy times. When we read your calendar (calendarView), we request only four fields per event: start, end, free/busy status and whether it is cancelled (start, end, showAs, isCancelled). Never the subject, body, attendees or location. We read them live and do not store them.
• Events. We create, update and delete the events rdv.dev books, with a Microsoft Teams link when the event type uses one, and keep each event's identifier.
• The other rules are the same as for Google: tokens held by Nango, no event content in our database, availability shared only with the people booking you and the integrations you authorise, no advertising, no sale, no training of AI or machine learning models, and no human access except with your permission, for security or when the law requires it.

To revoke access, disconnect the calendar in Settings → Connected accounts, or remove rdv.dev from the apps page of your Microsoft account. For a work or school account, your administrator can also remove it.

If you booked a meeting through rdv.dev

When you book through a booking page at rdv.dev/{workspace}, the business that runs that workspace is the controller of your data: it decides why it takes bookings and what it does with them. OPALITH SAS processes your data on its behalf, as its processor, under our data processing agreement. That business's own privacy policy applies.

What we keep on its behalf:

• your name, email address, time zone and language;
• the notes or answers you add when you book;
• the meeting: date, time, duration, location or video link, status, and any reschedule or cancellation;
• your mobile number and your consent to text reminders, only if you asked for reminders;
• a hash of the token behind your manage link. The link itself is only in your email.

Who receives it:

• the host or hosts of the meeting, in rdv.dev and in their calendar. The event we create there lists you as a guest, so Google or Microsoft may send you an invitation too;
• Mailtrap, which delivers your confirmation and any change or cancellation;
• ClickSend (Australia), which delivers text reminders, only if you asked for them.

Text reminders. Only if you give a mobile number and tick the box. A text a day before the meeting, or an hour before when it was booked at short notice, and a text if the host cancels. To stop them, write to the business you booked with, or to us at hello@rdv.dev, and we stop the texts for that booking.

Changing or cancelling. Use the manage link in your confirmation email.

Your rights. Send requests about your booking to the business you booked with. If a request reaches us, we forward it to that business and help it answer.

How long. As long as the business keeps its workspace, unless it deletes your booking sooner. Deleting the workspace deletes its bookings. Records of text reminders are deleted 30 days after they are sent.

Who receives personal data

We do not sell personal data, and we do not share it for advertising. The companies below process it for a specific job, and receive only what that job needs.

We also disclose data to authorities when the law requires it, and only what it requires.

Transfers outside the European Union

The app's database is in Frankfurt (Germany) and its functions run there. Several of the providers above are companies based in the United States or Australia, so data can be processed outside the European Union. Each of those transfers relies on the EU-US Data Privacy Framework where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses (decision 2021/914), with additional measures: encryption in transit and at rest, and keeping as little data as possible with each provider. Calendar tokens, for example, never reach our database, and free/busy reads are never stored.

You can ask us for a copy of these safeguards at hello@rdv.dev. The data processing agreement describes what we do if a government outside the EU asks for data.

How long we keep it

• Account. For as long as the account exists. Deleting your account (Settings → Security) deletes your profile, sessions, calendar connections and files at once. Upcoming meetings you host are cancelled, and their guests are told.
• Sessions. A session expires 30 days after it was last used; expired sessions, with their IP address and browser, are deleted every day.
• Workspace data. Event types, hours, brand, logos and bookings are kept for as long as the workspace exists. Deleting the workspace deletes all of it, files included.
• Invitations and join requests. Invitations are deleted 30 days after they expire or are revoked; join requests 90 days after they are decided.
• Website analyses for branding. 30 days after the analysis ends, or 7 days if it failed or was cancelled, with the logos it staged.
• Text reminder records. 30 days after the text is sent.
• Contact messages. As long as the conversation is open, then up to 3 years after our last exchange.
• Invoices and accounting records. 10 years, as French commercial law requires.
• Server logs. At most 30 days, unless an incident requires them for longer.
• Backups. Deleted data can remain in our database provider's restore history for a short period, at most 30 days, before it ages out.

How we protect it

• Encryption in transit (HTTPS) everywhere, and encryption at rest by our database and file storage providers.
• Passwords stored only as a hash. Manage links, API keys and invitation secrets stored only as a hash, or not at all.
• Calendar tokens held by Nango, never in our database or our code.
• Every action in the app checks who is asking and what their role allows, on the server.
• Access to production systems limited to the people who run the service.

If a breach is likely to put your rights at risk, we tell the CNIL within 72 hours and, when the law requires it, we tell you.

Your rights

Under the GDPR and French law, you can ask us to:

• access the personal data we hold about you, and get a copy;
• correct it if it is wrong or incomplete;
• erase it;
• restrict how we use it while a question is settled;
• export it in a common, machine-readable format (portability);
• object to processing based on our legitimate interest;
• withdraw your consent at any time, where we rely on it, without affecting what was done before;
• record instructions for what happens to your data after your death, as French law allows.

Much of this you can do yourself in the app: edit your profile, disconnect a calendar, delete your account. For anything else, including a copy or an export of your data, write to hello@rdv.dev. We answer within one month; if a request is complex, we may extend this by two months and tell you why. We may ask you to prove who you are when there is a reasonable doubt.

If you booked a meeting with one of our customers, send requests to that customer first (see If you booked a meeting through rdv.dev).

You can also complain to the CNIL (Commission nationale de l'informatique et des libertés), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, cnil.fr, or to the supervisory authority of the EU country where you live or work.

Cookies and storage

Neither the website nor the app uses advertising or tracking cookies, so neither shows a cookie banner. Everything below is strictly necessary for a service you asked for, or keeps a preference you set.

Vercel Web Analytics and Speed Insights use no cookie and no browser storage. When you connect a calendar, the connection window is served by Nango, and the sign-in screens by Google or Microsoft; their own cookies and policies apply there.

Changes to this policy

The date at the top of this page is the version in force. If a change affects how we use your data, we tell account holders by email or in the app before it applies and, when the law requires it, ask you to accept the new version. Earlier versions are available on request.

Contact

OPALITH SAS, 254 rue Vendôme, 69003 Lyon, France. Email hello@rdv.dev. We answer in English or French.