Skip to content
Availies
Developers

Privacy notice

Version: 2026-10-25.

Availies is a scheduling service: a person shares a booking link, and someone else picks a time. This notice says what personal data the service handles, why, where it is kept, how long, and what you can ask for.

Availies is run by MT Consult, a sole proprietorship registered in Denmark, Ingrid Marievej 49, st. mf, 2500 Valby, Denmark, business registration number (CVR) 45319504 ("we", "us"). Questions about personal data: privacy@availies.com. Other questions: support@availies.com. We have not appointed a data protection officer, because the law does not require one for a service like ours (GDPR Article 37(1)); privacy@availies.com reaches the person responsible for data protection.

Who this is about

You are We call you
Someone who books a meeting through a booking link, or answers a routing form A visitor
Someone a visitor adds to a booking by email address A guest
Someone whose calendar takes the bookings A host
Someone who signs in to set the service up for an account (a company or a team) A member
Someone a member has invited to join an account An invitee
Someone who reads our website or writes to us A website visitor

Whose rules apply to your data

If you are a visitor, a guest or a host, the account whose booking link you used (our customer) decides what is collected and why. It is the controller. We handle that data for the account, on its instructions, under a data processing agreement. We are the processor. We do not use that data for our own purposes. Ask the account first about your data. If you write to us, we pass your request to the account and tell you we did.

If you are a member or an invitee, we decide how your sign-in identity (your email address and name), your sessions and your account's billing are handled. We are the controller for those, and this notice is ours. Your role in an account, what you do there and the records of your changes belong to that account's setup, which the account decides; we process those for the account as we do its other data.

If you write to us (support or privacy mail), we are the controller for that correspondence.

What we handle, and why

When you book a meeting (visitor)

  • Your name and email address, and your phone number if the account's booking page asks for it.
  • Your answers to the questions the account put on its booking page or routing form.
  • The time you picked and your time zone, and the meeting address or video link if the meeting has one.
  • If you came through a link that already carried your details (a prefilled link), those details.
  • The email addresses and names of guests you add.
  • The reason you give if you cancel.
  • A keyed hash of your network address, used to limit how often one network can book or submit a form, kept for a short time by the rate limiter; the product's own records hold the hash, not the address. Our human check (Cloudflare Turnstile) receives your network address to tell people from scripts.

We use this to make the booking, put it in the host's calendar, send the confirmation, reminders and any change, and let you move or cancel the booking. The emails carry a link that lets whoever holds it move or cancel that one booking, so treat them as yours.

If the account has connected its own systems, the booking is also sent there (see "Where it goes" below).

When you are added as a guest

Your email address and name as the visitor typed them. You get the confirmation, a notice when the time changes and a notice if the meeting is cancelled. You cannot change the booking; the visitor can.

When your calendar takes bookings (host)

  • Your name, email address, phone number if given, working hours and time zone.
  • The email address of the calendar account you connected.
  • Access to your calendar, which you grant by signing in with your calendar provider (Google today). We ask Google for three permissions: to view your availability in your calendars, to see the list of calendars you are subscribed to, and to see, create, change and delete events on calendars you own. We use them like this: we only look at busy times and at the meetings Availies created. We do not store or use the content of your other calendar entries. For availability we ask only whether you are busy, never what you are doing. When a calendar changes, we ask Google only for the ids and statuses of the changed entries, match them against the meetings Availies created, and read only those. The access token is stored encrypted; we never see your Google password.
  • Which calendar receives the bookings and which calendars count as busy.

We use this to show free times, to write the booked meetings into your calendar, to move or remove them when a booking changes, and to notice when you move or delete such a meeting in your calendar.

Statement required by Google. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

When you sign in and use the service (member)

  • Your email address, which you must give to sign in, and your name, which Google gives us or you type; the accounts you belong to with your role in each. Without an email address there is no account.
  • How you sign in: a six-digit code sent to your email address, or your Google account (then Google tells us your email address, your name and whether the address is confirmed). When you ask for a code, the sign-in library counts requests per network address for a minute, in a row that holds the address.
  • A session, kept by a cookie on the app's own address. The session's record holds your network address and your browser's description, and is removed when the session ends: after 24 hours without use, and at most 30 days after sign-in. The cookie is not used for advertising or to follow you across sites.
  • A record of the changes you make to settings (configuration history) and of actions such as adding a member or making an API key (the audit log), each with who did it and a keyed hash of the network address, so that an account can see who changed what.
  • The version of the terms of service you accepted when you created the account, and when.
  • If a member invites you, the invitation holds your email address and the role offered. We got your address from the member who invited you, and you see this notice before you accept, on the sign-up page. The record is removed 30 days after the invitation was accepted, withdrawn or expired.

We use this to run your account, keep it secure and show your account who did what.

When your account pays (member)

Paid plans are bought through Stripe. On Stripe's payment page you give Stripe your name, billing address, email address, VAT number and card details. We never see the card. From Stripe we receive a reference to the customer and the subscription, its plan, its state and the number of paid seats, and we store those. Invoices and receipts are kept by Stripe and reachable through the billing page.

Stripe takes the payments for us, and is also a controller in its own right where it prevents fraud and meets its own legal duties. In Stripe's own suggested words: "We use Stripe for payments, analytics, and other business services. Stripe may collect personal data including via cookies and similar technologies. The personal data Stripe collects may include transactional data and identifying information about devices that connect to its services. Stripe uses this information to operate and improve the services it provides to us, including for fraud detection, loss prevention, authentication, and analytics related to the performance of its services. You can learn more about Stripe and read its privacy policy at https://stripe.com/privacy."

When you write to us

Mail to privacy@availies.com and support@availies.com is received by our mail provider (Google Workspace). Privacy mail stays in that mailbox. Support mail is forwarded on, through the mail forwarding of our other domain (run by Cloudflare), to the mailbox we read, which is run by Google Ireland Limited (Gmail), Gordon House, Barrow Street, Dublin 4, Ireland. We keep a conversation while the matter is open and delete it within 12 months of its closing, unless a legal claim or a bookkeeping duty needs it longer.

When you read our website

The public website sets no cookies and runs no analytics or tracking. The booking pages set no cookies either. Our hosting provider sees the ordinary request data a web server sees (address, browser, page), and in production we keep no request logs of our own.

Failures

When the service fails in a way we did not plan for, a report goes to our error-reporting provider (Sentry, EU region). A report says what broke and where: the kind of error and its message, the lines of our own code around the failure, the request's method and its address (host and path) without the query string, the request's id, the id of the account the request acted in, and for some failures other internal ids (for example of a lookup endpoint, an assistant connection or a background job). Before it leaves, the reporting library is told not to collect the person, cookies, headers, bodies or query strings, and a scrubber removes those again and replaces every email address, network address, credential and token it recognises, in any field. A path can still name an account's handle and booking link or the id of a record, and an error message can hold other words, so we treat reports as data that may relate to a person and keep them in the EU region.

What we do not do

  • We do not sell personal data.
  • We do not use it for advertising.
  • We do not use it to train machine learning or language models.
  • We do not read, store or use the content of calendar entries that were not booked through Availies.

Where it is kept, and where it goes

Everything the service stores (the database, the objects that hold reservations and limits, and the files) is created inside our hosting provider's European Union jurisdiction and stays there. Requests are answered from the provider's data centre nearest to you, which reads those stores from where it is; so the storage is in the EU, and the handling of a request can happen elsewhere.

Some data goes to other companies that help us run the service. The full list, with each company's legal name, what it receives, where it keeps it and on what basis data may leave the EU, is in sub-processors.md. In short:

  • Cloudflare hosts the service and stores its data (in its EU jurisdiction), checks that a visitor is a person, and forwards the mail of our other domain.
  • Resend delivers our emails. It sends them from its EU region; its own records of each email (recipient, subject, delivery status) are stored in the United States, under the EU Standard Contractual Clauses and the EU-U.S. Data Privacy Framework.
  • Google is the host's own calendar provider, and runs the mailbox that receives our support and privacy mail, which Google may keep in any country where it has data centres, the United States included (Google lists them at datacenters.google/locations, read 2026-10-23); Google is certified under the EU-U.S. Data Privacy Framework, and its data processing terms add the EU Standard Contractual Clauses.
  • Stripe takes payments.
  • Sentry receives error reports, in its EU region.

If you are a visitor or a host, the account may also have connected its own systems: a webhook endpoint it runs, or a lookup that asks its own system who you are. Bookings and changes are then sent to those systems too. Those systems are the account's, not ours; the account's own privacy notice covers them.

How long it is kept

Data Kept
A visitor's name, address, phone, answers, guests, meeting address, reason Until 90 days after the meeting ended, unless the account chose another period between 30 and 730 days. The booking's time, host and status stay without a name
Routing form answers that led to no booking The same period, counted from the submission
Prefilled links and their details Until 7 days after the link expired
Outgoing event payloads (what was sent to the account's systems) 30 days after the event was created, once every delivery of it has finished
Email records The recipient, subject and delivery status for 90 days. The message itself only while it waits to be sent; it is cleared when the send ends
Configuration history and the audit log 365 days. For each setting, the newest record older than that is kept as the baseline, so the current setup can be explained and restored
Invitations 30 days after the invitation was accepted, withdrawn or expired
Sign-in sessions (network address, browser description) Until the session ends: 24 hours without use, at most 30 days
Sign-in request counters (network address) One row per network address and sign-in step, reused by the sign-in library. The count resets after its one-minute window; the row with the address is deleted within 24 hours after that address's last sign-in attempt
A host's details and the calendar connection While the host exists and the calendar is connected. Disconnecting deletes the stored token
A member's sign-in identity (email address and name) While the person belongs to any account, and until the person asks us to delete it. Removing a member from an account does not delete the identity
Billing references and subscription state While the account exists. Invoices and payment records: five years from the end of the financial year they belong to (Danish Bookkeeping Act, § 12), in Stripe and in our bookkeeping
Error reports Deleted by Sentry when our plan's retention period ends: at most 90 days
Support and privacy mail While the matter is open, then deleted within 12 months of its closing (see "When you write to us")

The periods for the account's visitor data, payloads, logs and history are settings of each account; the numbers above are the defaults the service applies until an account changes them.

When an account is deleted. An owner asks for deletion in the account's settings. The account closes at once: its pages, members, keys and connected assistants stop working. For 14 days (the grace period) an owner can undo this. When the grace period ends, the purge starts as soon as every email, cancellation notice and calendar cleanup already under way has finished, and it removes every row of the account from the database, the stored calendar tokens (and asks Google to revoke them, where no other account shares the grant), the account's reservations and limits, and any stored logo (logos are not stored yet; when they are, they go here). The account's handle stays reserved and leads to a page that says the account no longer exists. Deleted data stays in the database's recovery history for up to 30 days after it was deleted, where it can only be reached by restoring the whole database; then it is gone. If we ever restore the database, deletions and erasures are applied again from a ledger before the service serves again. Sign-in identities are not deleted with an account (a person may belong to other accounts). Billing records stay with Stripe. Addresses on the email suppression list (a list of addresses that bounced or complained, held as hashes to protect everyone's delivery) are kept while the suppression is needed and removed on a verified request; the list is not in use yet.

The legal grounds (for members and website visitors)

  • To perform our agreement (GDPR Article 6(1)(b)): if you hold the account yourself, your account, sign-in and billing details, the terms version you accepted and the emails the service must send you.
  • Our legitimate interest (Article 6(1)(f)): if your employer or organisation holds the account, our interest in giving it the service it bought, which needs your sign-in identity and session; for everyone, our interest in keeping the service secure and able to show who did what (sessions, the audit log, the human check, rate limits, error reports, the suppression list), in answering the mail you send us, and in serving the website to the browser that asks for it.
  • A legal duty (Article 6(1)(c)): bookkeeping records of payments (invoices and the payment records behind them), which the Danish Bookkeeping Act (bogføringsloven, § 12) requires us to keep for five years from the end of the financial year they belong to, and answering a request about your rights (Articles 12 to 22).

Where we rely on our legitimate interest, we have weighed it against yours: we use only what the service needs to work and stay secure, keep it for the periods in the table above, and use none of it for advertising or profiling. You may object to that use at any time by writing to privacy@availies.com (GDPR Article 21), and we then stop unless we show compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend a legal claim.

For visitors, guests and hosts, the account whose booking link was used states its own grounds in its own notice.

What you can ask for

You can ask to see the data held about you, to have it corrected or deleted, to have its use limited, to object to its use, and to receive it in a form you can take elsewhere (GDPR Articles 15 to 21).

  • Visitors, guests and hosts: ask the account whose link you used. The account can find everything it holds about an email address, download it for you and erase it. A booking that is still pending, or whose meeting has not happened, is cancelled first and erased after; the account is told which ones. If you write to us instead, we pass your request to the account and tell you so.
  • Members: write to privacy@availies.com from the address you sign in with. An account owner can download everything the account holds and delete the account from its settings.

We answer within one month, as the law requires, and tell you if a complex request needs longer.

You can complain to the data protection authority where you live or work. Ours is the Danish Data Protection Agency (Datatilsynet), Carl Jacobsens Vej 35, 2500 Valby, Denmark, www.datatilsynet.dk (the site has the complaint form and the agency's contact addresses).

Automated decisions

The service makes no decision about you with legal or similarly significant effect. A routing form sends you to a booking page by your own answers; a duplicate check may decline to take a second booking online and send the explanation by email. As the service works, neither has a legal effect on you or affects you in a similarly significant way, so neither is a decision of the kind GDPR Article 22 covers. An account that uses a routing form or the duplicate check to decide something weightier for you (for example access to a job or to health care) is responsible for assessing that use and for letting a person review the result.

Security

Every account's rows are bound to that account in every database statement, and a check in the build fails on a statement that is not. Stored credentials are encrypted. Links in emails are signed for one account and one action and expire. Personal data is kept out of logs and metrics, and error reports are scrubbed before they leave, as "Failures" above describes. Access to the service's administration is limited to the operator, and a look into an account by the operator is time-limited and shown on every screen of that account.

If a breach affects data we process for an account (its visitors, guests, hosts and members' records inside it), we tell that account within 48 hours of learning of it, and the account tells its people and its authority as the law requires it to. If a breach affects data we control (your sign-in identity, sessions or billing), we tell the Danish Data Protection Agency within 72 hours where the law requires it, and we tell you directly when the breach is likely to put you at high risk (GDPR Articles 33 and 34).

Children

The service is for businesses and the people they meet. We do not knowingly collect data from children under 15, and an account may not point a booking page at them (terms, section 4). Fifteen is the age from which Danish law lets a child consent on its own to the processing of its personal data by online services offered directly to children (databeskyttelsesloven § 6, stk. 2). The restriction is our product rule; we do not rely on a child's consent for anything.

Changes

When this notice changes, the version date at the top changes. Members are told by email, 30 days before a change that matters to them takes effect. (Contractual notices to a customer go to its account's owners, as the terms say; this is a notice to you as a person.)

This notice is in English, and English is the binding version.

Privacy notice Terms of service Data processing agreement Sub-processors

Availies is being built. It is not open for sign-up yet.