Skip to content
Availies
Developers

Data processing agreement

Version: 2026-10-25.

Between the customer that holds an Availies account ("the controller") and MT Consult, a sole proprietorship registered in Denmark, Ingrid Marievej 49, st. mf, 2500 Valby, Denmark, CVR 45319504 ("the processor"). It is part of the terms of service and is accepted with them when the account is created. Words used here mean what the GDPR (Regulation (EU) 2016/679) gives them.

1. What is processed, and why (Article 28(3), opening words)

Point Content
Subject matter and purpose Providing the scheduling service: showing free times, taking bookings, writing them to hosts' calendars, sending the emails around a booking, routing visitors with forms, and sending booking events to the controller's own systems when the controller connects them
Nature Storage, retrieval, transmission by email and by webhook, matching against the controller's lookups, and deletion; automated, in a hosted service shared by many controllers with each controller's data bound to its own account
Duration While the controller has an account, plus the grace period and the purge described in section 11
Whose data The controller's visitors (people who book or answer a routing form), the guests they add, the controller's hosts, and the controller's members as far as their membership, role, invitations and actions inside the account are concerned (a member's sign-in identity, sessions and the account's billing are the processor's own, as its privacy notice says)
What data Names, email addresses, phone numbers where asked, time zones, answers to the controller's booking and routing questions, booking times and statuses, meeting addresses and video links, cancellation reasons, hosts' working hours and calendar identifiers, records of changes
Special categories None intended. The controller does not ask for them in booking or routing questions unless agreed with the processor in writing (terms, section 4)

2. Instructions (Article 28(3)(a))

The processor processes the personal data only on the controller's documented instructions. The terms of service, this agreement and the controller's settings and actions in the service are those instructions; the controller may give further written instructions by email to privacy@availies.com. If the service cannot carry an instruction out, the processor says so without delay and the parties agree how it is met; failing that, the controller may end the agreement. The processor does not process the data for its own purposes. This covers transfers to a third country or an international organisation: they happen only through the sub-processors in section 6, as the controller instructs by using the service, or to the systems the controller itself connects (its webhook endpoints, its lookup systems and its hosts' calendars), which are the controller's own instructions and the controller's responsibility, also where those systems are outside the EU. If a law of the Union or of Denmark requires the processor to process the data otherwise, the processor tells the controller before processing, unless that law forbids it on important grounds of public interest. If the processor believes an instruction infringes the GDPR or other data protection law, it tells the controller at once.

3. Confidentiality (Article 28(3)(b))

The processor lets only people bound to confidentiality handle the data. Today that is the owner of the processor. A look into a controller's account by the processor's operator is time-limited, read-only, and shown on every screen of that account while it lasts.

4. Security (Article 28(3)(c), Article 32)

The processor keeps technical and organisational measures that fit the risk. Today these include:

  • every statement that reads or changes a controller's rows names the controller's account in that same statement, and a check in the build fails on a statement that does not;
  • stored credentials for other services (calendar tokens) are encrypted at rest with a key kept outside the database; secrets are kept outside the code and never written to logs;
  • the service's own stores are in the European Union (section 7); the email provider keeps its delivery records in the United States, as the sub-processor list states;
  • personal data is kept out of logs and metrics; error reports are scrubbed before they leave of every email address, network address, credential and token the scrubber recognises, and keep the request's address without its query string, the account's id and internal ids;
  • links in emails are signed for one account and one action and expire; manage links for a booking are secrets of the visitor;
  • sign-in is by one-time code or by Google with a confirmed address; sessions end after 24 hours without use and at most 30 days after sign-in; a human check guards booking, sign-in and sign-up against scripts;
  • changes to settings are recorded with who made them; the records are kept 365 days, and for each setting the newest older record is kept as a baseline;
  • availability and resilience: the hosting provider runs the service in many data centres; the database keeps a point-in-time recovery history of 30 days on the plan the service runs on, so it can be restored to a moment before a fault;
  • deletions survive a database restore: a ledger of what was purged or erased is replayed before the service serves again;
  • testing: every change runs the whole test suite, the account-isolation check and the identity scan before it is pushed, and reaches a staging environment before production; the processor reviews these measures when a change touches them and at least once a year.

The processor may change these measures as long as the level of protection does not fall. This section is the description of the technical and organisational measures that Article 28(3)(c) and Article 32 call for; it covers confidentiality, integrity, availability and resilience, the ability to restore, and regular testing.

5. Helping with people's rights (Article 28(3)(e))

The processor helps the controller answer requests from people about their data (access, correction, deletion, restriction, objection, portability), taking into account the nature of the processing. Through the service itself, the controller can find everything the account holds about one email address, download it and erase it from the account's settings (a pending booking or one whose meeting has not happened is listed for the controller to cancel first). Where a request needs more than the service offers, the controller writes to privacy@availies.com and the processor helps without undue delay, within the time the controller has to answer. A request a person sends to the processor directly is passed to the controller without delay. The processor does not answer such a request on the controller's behalf unless the controller asks it to.

6. Other processors (Article 28(2) and (4), Article 28(3)(d))

The controller gives general written authorisation to the processor to use the companies in the sub-processor list, each for the task named there. Before adding or replacing a sub-processor, the processor tells the controller by email to the account's owners at least 30 days before the new sub-processor starts processing, naming it, where it keeps the data and what it does. The controller may object within that period on reasonable data protection grounds; if the parties find no solution, the controller may end the agreement before the change takes effect, with the refund the terms give for leaving over an announced change. The processor puts on each sub-processor, by contract, the same data protection duties as this agreement puts on the processor, and stays fully liable to the controller for the sub-processor's performance. The sub-processors' own terms are the standard terms each offers (the list names them); where such terms give the processor less than 30 days' notice of that company's own changes (the email provider gives 14), the processor tells the controller as soon as it learns of the change, and the controller's right to object stands.

7. Where the data is, and transfers outside the EU (Article 28(3)(a), Chapter V)

The service stores the data in its hosting provider's European Union jurisdiction. The processor is established in Denmark. Data leaves the EU only through the sub-processors in the list, for the tasks named there; for those transfers the processor is the exporter. Each transfer to the United States goes to a company certified under the EU-U.S. Data Privacy Framework and rests on the Commission's adequacy decision for it (Commission Implementing Decision (EU) 2023/1795); the Standard Contractual Clauses of Commission Implementing Decision (EU) 2021/914, which each of those companies' terms incorporate, apply if the certification or the decision lapses. If a transfer comes to rest on the clauses, the processor assesses whether they give the data adequate protection there, tells the controller, and stops that transfer if they do not. The protections of US law that the adequacy decision relies on apply to every transfer to the United States, whatever its mechanism. Where the hosting provider handles a request in a data centre outside the EU and the United States (the sub-processor list says when), that is the hosting provider's onward transfer under the clauses in its terms. The processor keeps the list current, checks each certification when it updates the list, and gives the controller, on request, a copy of or a link to each sub-processor's terms. Transfers to systems the controller connects are the controller's own (section 2).

8. Helping with security duties, breach notices and impact assessments (Article 28(3)(f))

The processor helps the controller meet Articles 32 to 36 with the information the processor has: the measures in section 4, the breach information in section 9, a description of the processing (section 1 and the data model the service publishes in its documentation) for an impact assessment, and, on request to privacy@availies.com, further information and help with an impact assessment, a prior consultation or a notification, as far as the nature of the processing and the information available to the processor allow.

9. Breaches (Article 33(2))

The processor tells the controller, by email to the account's owners, without undue delay and at the latest 48 hours after becoming aware of a breach of the controller's personal data, with what is known: the nature of the breach, the categories and approximate number of people and records concerned, the likely consequences, what is being done about it and whom to contact; information not yet known follows as it becomes known. This supports the controller's own duty to notify under Article 33(1). The processor does not notify the supervisory authority or the people concerned on the controller's behalf unless the controller asks.

10. Records and audits (Article 28(3)(h))

The processor gives the controller the information needed to show that these duties are met: this agreement, the sub-processor list, the measures of section 4, and on request the records of processing the processor keeps and written answers to the controller's reasonable questions about them. The controller, or an auditor it appoints who is bound to confidentiality and is not a competitor of the processor, may audit the processor's compliance, including by inspection, at most once every 12 months, with 30 days' written notice, during business hours, in a way that does not expose other controllers' data or weaken the service's security, and at the controller's cost, including the processor's reasonable time. The controller first says what it wants to verify, so that the processor can answer as much as possible in writing and the audit covers the rest.

Outside that yearly audit, and with reasonable notice, the controller may also audit:

  • after a breach of the controller's personal data, at the processor's cost;
  • when a supervisory authority requires an audit, at the processor's cost;
  • when the controller has documented, reasonable grounds to believe that the processor does not comply with this agreement or with Article 28 of the GDPR, and the processor's written answers, given within 30 days of the request, have not settled them, at the controller's cost. Where a supervisory authority or an urgent risk to the data requires it, the audit is not delayed by the written stage.

11. Deletion and return (Article 28(3)(g))

  • While the account is active, the controller can download the account's data at any time (one file, from the account's settings): every table of the account except its working queues, sync positions, held time, page reports and sealed credentials, and never a secret.
  • The controller ends the processing by deleting the account (terms, section 10); the request is accepted once no booking is pending or waiting to happen. The account then closes at once. For 14 days (the grace period) an owner of the account can undo the deletion and the account reopens as it was; there is no download during the grace period, so the controller downloads first.
  • If the processor ends the agreement with notice, the download stays available until the account closes. If the processor ends the agreement at once (terms, section 10), it suspends the account and deletes nothing at that moment; the controller may ask within 14 days of the processor's notice for a copy of its data, which the processor provides in a common machine-readable form within 30 days of the request. The account stays suspended until those 14 days have passed and any copy asked for has been provided; ordinary retention continues meanwhile; then the account is deleted as this section describes, from the grace period on. With the download, this gives the controller the choice between return and deletion that Article 28(3)(g) requires.
  • When the grace period ends, the purge starts as soon as every email, cancellation notice and calendar cleanup already under way has finished (so that people are still told what the controller did before deleting), and it deletes every row of the account, the stored calendar tokens (asking the calendar provider to revoke them where no other account shares the grant), the account's reservations and limits, and any stored files, in that order. If work under way does not settle within 7 days after the grace period, the processor's operator is alerted and sees it through. The processor completes the purge within 30 days after the grace period ends.
  • Deleted data stays in the database's recovery history for up to 30 days after deletion, reachable only by restoring the whole database, and is then gone. If the processor restores the database, the deletions are applied again from a ledger before the service serves again.
  • The processor keeps what Union or Danish law requires it to keep (bookkeeping records of payments, held by the payment provider) and nothing else.
  • Copies in sub-processors' own records (the email provider's delivery records and error reports) are deleted on those companies' schedules under their terms, as the sub-processor list states; the purge does not reach them. On request, the processor confirms to the controller in writing when the purge is complete.
  • The processor deletes nothing the controller's own systems received by webhook or lookup, and nothing in hosts' calendars; those are the controller's.

12. Liability

The liability provisions of the terms of service (section 11) apply to claims between the parties under this agreement. They do not limit either party's liability to a person whose data is processed (GDPR Article 82).

13. Order of documents, law and term

If this agreement and the terms of service disagree about personal data, this agreement wins. Danish law applies and the Copenhagen City Court is the agreed court, as in the terms. This agreement lasts as long as the processor holds personal data for the controller. Changes to it follow section 8 of the terms (30 days' notice by email).

Annex: processing in one table

Question Answer
Controller The account holder
Processor MT Consult, Denmark
Sub-processors sub-processors.md
Storage location European Union (hosting provider's EU jurisdiction)
Retention set by the controller Visitor data: 90 days after the meeting by default, 30 to 730 days; routing answers without a booking: the same from submission; event payloads: 30 days; email records: 90 days; history and audit: 365 days (defaults the controller may change where the service allows)
Retention fixed by the processor Prefilled links: 7 days after expiry; invitations: 30 days after acceptance, withdrawal or expiry; sign-in sessions: 24 hours without use, at most 30 days; grace period 14 days; purge completed within 30 days after it; recovery history up to 30 days
Breach notice Within 48 hours of the processor becoming aware
Sub-processor changes 30 days' notice by email to the account's owners; a change in a sub-processor's own sub-processors is passed on as soon as the processor learns of it (section 6)
Audits Once every 12 months, 30 days' notice, at the controller's cost; also after a breach or on an authority's demand (at the processor's cost), and on documented grounds to suspect non-compliance (at the controller's cost)
Privacy notice Terms of service Data processing agreement Sub-processors

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