Privacy policy
Last updated 13 September 2026
Aleida is the controller for the personal data collected on aleida.ai. Reach us at hello@aleida.ai.
Only what the demo booking form asks for: your name, your email address, your company if you fill it in, and the time you picked.
No cookies for advertising, no tracking pixels, no profiling.
To hold the meeting you booked and to send you a confirmation and a reminder. Nothing else. We do not sell it and we do not pass it to anyone for their own purposes.
Legitimate interest: you asked to meet us, and we need your details to make that happen. You can object at any time by mailing hello@aleida.ai.
Supabase stores the booking. Vercel runs the site. Resend sends the confirmation email. All three are processors under agreement, and none of them may use the data for their own purposes.
Until the meeting has happened and any follow-up is done, and then no longer than we need it for our accounting obligations. Mail us and we will delete it sooner.
You can ask what we hold about you, have it corrected, have it deleted, and object to the processing. Mail hello@aleida.ai and we answer within a month.
If you think we are handling your data wrongly you can complain to the Swedish Authority for Privacy Protection (IMY).
The Aleida app
This part applies to companies that use the Aleida recruitment app at app.aleida.ai and connect a Google account to it. It describes exactly what Aleida receives from Google, and what we do with it.
When someone at a company connects a Google account, Aleida asks Google for three things: the email address of that Google account, permission to create and edit events on the calendars that account owns (not calendars shared with it), and permission to see when its calendar is busy.
Aleida does not read the titles, descriptions, attendees or contents of any existing events in your calendar. The only events we handle are the interview meetings Aleida creates.
The email address is shown in the app's settings, so you can see which account is connected.
When a job candidate books one of the interview times a recruiter proposed, Aleida creates that single meeting in the connected calendar, with the candidate as a guest and a Google Meet link. Google sends the candidate the calendar invitation.
When a recruiter proposes interview times, Aleida asks the calendar whether those times are busy, so it can warn about a clash. We only learn whether a time is busy or free, never what is scheduled then.
We use Google user data for nothing else. We do not use it for advertising, we do not sell it, and we do not use it to develop, improve or train artificial intelligence or machine learning models. It is never sent to the AI models Aleida uses to assess interviews.
Aleida stores one thing from Google: a refresh token that lets the app create meetings when a candidate books, even when no recruiter is logged in. It is encrypted with AES-256-GCM before it is stored, in a database hosted in the EU (Ireland). Only Aleida's servers can read it; it is never sent to a browser.
For each meeting Aleida creates, we also store the meeting's ID and its Meet link alongside the booking in Aleida.
Nobody. Google user data is not shared with, transferred to or disclosed to any third party, except as needed to create the meeting in Google itself.
Until you disconnect. In the app's settings, "Disconnect" revokes Aleida's access at Google and deletes the stored token immediately. You can also revoke access at any time from your Google account at myaccount.google.com/permissions.
Meetings already created stay in your calendar, because they are yours. The meeting ID and Meet link stored on a booking are deleted together with the candidate's record.
Aleida'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.
Questions about Google user data: hello@aleida.ai.
Want to know more?
Leave your work email and we'll get in touch, usually the same day.