Data processing agreement under Article 28 GDPR

Version 2 of 20 November 2026

An organization that accepted Version 1 of 17 November 2026 keeps it until it accepts this version (§ 12(3)). We send Version 1 on request.

between the "controller", which is either the customer of an organization under the terms of service, that is the person who creates the organization or takes over its billing, or the body they act for in doing so, or the body for which a person accepts this agreement in their own account for professional use, for example a school or a company,

and Jonathan Ilk, JMilk Software, Olgastr. 49, 70182 Stuttgart, Germany (the "processor", "we").

For an organization, the agreement is concluded when the person who creates the organization accepts it for the controller. When a person takes over billing, they conclude this agreement in the same way for the new controller; it applies from the start of their subscription, and the previous agreement ends with the previous subscription. When we set up an organization, the person who manages billing accepts it before anyone can join or create a quiz. For an account, the agreement is concluded when the account holder accepts it in their account for the body they use the account for. The person who accepts confirms that they may act for the controller. We keep when and in which version this happened, for an organization also by which account. On request we send the controller this agreement as a PDF signed by us, with the name and address it gives us for this.

§ 1 Subject matter and duration

(1) For an organization, we provide the controller with the organization in Rondilo under the terms of service. For an account, we provide its holder with Rondilo under the terms of service, and this agreement covers that account's quizzes, pictures, sounds, parties and their History. Below, "the workspace" means the organization or these parts of the account. In both cases we process personal data in the workspace on the controller's behalf. Annex 1 describes the nature, purpose, kinds of data and data subjects.

(2) The agreement applies as long as the organization or the account exists, and after that until the workspace's data is deleted under § 9.

(3) Not covered are processing operations for which we are the controller ourselves: accounts and sign-in, plans, subscriptions and payments, cancellations and withdrawals, our emails about subscriptions and about this agreement, publications in Discover with their ratings, reports and moderation, solo plays and Versus, the hosting minutes an account counts for fair use, abuse prevention and logs. When a quiz of the workspace is published to Discover, the controller hands that version, and for an organization its public name, to us, and we are the controller for it. The controller also permits us to derive counts from the workspace's parties and people, and we are the controller of them: daily figures on parties, players, questions and errors and the number of people for billing, which name no person, and the party totals of the account that hosted, which are kept with that account and count only its parties, their players and the questions played. These counts hold no player names, answers, player identifiers or content.

§ 2 Instructions

(1) We process the data only on documented instructions from the controller, including for transfers to a third country, unless Union or German law requires us to. In that case we tell the controller beforehand, unless the law forbids it.

(2) The instructions are this agreement, the terms of service and the settings and actions that the people in the organization make within their roles or, for an account, that the account holder makes. The controller gives further instructions in text form to contact@rondilo.com. We send our messages under this agreement by email from contact@rondilo.com, for an organization to the person who manages billing, for an account to the account's email address.

(3) If we consider an instruction unlawful, we tell the controller at once and may suspend it until the controller confirms or changes it.

§ 3 Duties of the controller

(1) The controller is responsible for the processing being lawful and for informing data subjects under Articles 13 and 14 GDPR. For an organization, it decides who gets the invite link and which roles it gives. For an account, it is responsible for what the account holder does in it on its behalf.

(2) By using the organization, the controller chooses a standard offering: every History entry is fully visible to and downloadable by everyone in the organization and is kept as long as Annex 1 says. Every History entry holds the names and scores of the top three and the names of up to three award winners. Whether it also keeps every player's name, answers, points and answer times, the controller decides with the setting "Detailed History in organization parties", which starts off. The controller checks from the start that it may keep the names and scores of the top three and the names of the award winners and show them to everyone in the organization, and checks the same for the rest of this data before turning the setting on. In every party of an organization quiz, we tell players when they join, before they enter their name, that the organization keeps the names and scores of the top three and the names of the award winners and that everyone in it sees them, and, while the setting is on, instead that it keeps their name, answers and scores and that everyone in it sees them. If that changes after a player joined, we show it to them again in the waiting room. The controller gives its players any further information itself.

(3) For an account, every History entry is visible to and downloadable by the account holder only and is kept as long as Annex 1 says. Every History entry holds the names and scores of the top three and the names of up to three award winners. Whether it also keeps every player's name, answers, points and answer times, the account holder decides for each party with Detailed History, which needs Pro, starts off and then follows the account holder's last choice. The controller checks from the start that it may keep the names and scores of the top three and the names of the award winners, and checks the same for the rest of this data before Detailed History is turned on. In every party, we tell players when they join, before they enter their name, what the host keeps, and tell them again in the waiting room if that changes. The controller gives its players any further information itself.

(4) Where children or pupils play, the controller does not base the processing on the consent of children under 16 and, for an organization, checks whether everyone in it may see their results, for example under the school law that applies to it. It makes sure players enter no more about themselves than needed, for example a first name, and checks whether it needs a data protection impact assessment.

(5) Where the controller uses the workspace for employees, it obtains the agreement of its works council or staff council where required, for example under section 87(1) no. 6 of the German Works Constitution Act, and relies on its own legal basis. Every History shows the names and scores of the top three and the names of the award winners and, with Detailed History, each player's answers and points; an organization also shows who created and edited quizzes and hosted parties.

§ 4 Confidentiality

We bind everyone with access to the data to confidentiality, unless they are under a statutory duty of confidentiality. Today only Jonathan Ilk has access. We keep a record of our processing as a processor under Article 30(2) GDPR.

§ 5 Security

We take the technical and organizational measures under Article 32 GDPR described in Annex 2. We may develop them further as long as the level of protection does not fall.

§ 6 Sub-processors

(1) The controller approves the sub-processors in Annex 3.

(2) We announce a new or replaced sub-processor at least 14 days in advance by email, for an organization to the person who manages billing, for an account to the account's email address, and note it on this agreement's page. Within those 14 days the controller may object for an important data protection reason; without an objection, the sub-processor counts as approved. While an objection is unresolved, we do not use the new or replaced sub-processor for the workspace's data where we can keep that data from it with reasonable effort; where we cannot, the controller may stop the affected processing by not using the functions concerned. If we find no solution within 30 days of the objection, the controller may cancel the organization's subscription for the end of the current paid month or, for an account, end this agreement with immediate effect; § 9(4) then applies.

(3) Every sub-processor is bound by a contract under Article 28(4) GDPR that imposes on it substantially the same data protection obligations this agreement imposes on us, including sufficient guarantees under Article 32 GDPR. We are liable for it as for ourselves. On request we name the terms we agreed with it.

§ 7 Third countries

Transfers to a country outside the EEA take place only through the sub-processors in Annex 3. For the USA they rely on the adequacy decision on the EU-US Data Privacy Framework where the company is certified, and otherwise on the Commission's standard contractual clauses in the company's terms. There is no adequacy decision for Singapore; there the transfer relies on the safeguards in Fly.io's terms. Which safeguards these are, and how we assess the transfer, is set out in the assessment of the transfer to Singapore, which the controller receives on request. If an authority of a third country asks us for the workspace's data, we inform the controller as far as we may.

§ 8 Assistance

(1) We help the controller answer requests from data subjects under Chapter III GDPR. In an organization, Admins and the person who manages billing can remove people, view, download and delete History entries and export quizzes; in an account, its holder can view, download and delete History entries and export quizzes. What they cannot do themselves, we do on request. Players are known only by the name they entered. On instruction we remove a single player from a History entry. If a request concerning the workspace reaches us, we pass it on to the controller and do not answer it ourselves, unless the controller instructs us to.

(2) We assist the controller with its duties under Articles 32 to 36 GDPR with the information we have.

(3) We report a personal data breach affecting the workspace's data by email without undue delay after becoming aware of it, for an organization to the person who manages billing, for an account to the account's email address, with the information under Article 33(3) GDPR as far as we have it. Where we cannot give all of it at once, we give it in stages without further undue delay.

§ 9 Deletion and return

(1) Until the deletion, Admins and the person who manages billing can export all of the organization's quizzes as a file and download each History entry as a spreadsheet, also while the organization is read only. On request we hand the controller its pictures, sounds, logo and list of people as files. For an account, its holder can export its quizzes and download each History entry in the same way, and on request we hand over its pictures and sounds as files.

(2) The person who manages billing deletes the organization. Its Pro then runs to the end of the paid month; without a paid month it ends with the deletion. 30 days after its Pro ends, or 30 days after the deletion if its Pro had already ended, and otherwise 6 months after its Pro ended, we delete all of the organization's data: quizzes, pictures, sounds, logo, History, people, settings and the organization itself. Pictures and sounds are already deleted 30 days after its Pro ends. Backups of Firestore are enabled in the Google Cloud project. Deleted data can remain in them until those backups expire; we do not restore it from them into use. Google removes deleted data from its systems under its own terms within at most 180 days. Lettermint deletes its copy of an email 28 days after it was sent, and from its backups no later than 14 days after that.

(3) For an account, its holder deletes single quizzes, pictures, sounds and History entries or the whole account. History is deleted as Annex 1 says. Pictures and sounds are deleted 30 days after the account's last paid plan ends, and everything with the account. What (2) says about backups and about the copies at Google and Lettermint applies in the same way.

(4) When the processing on the controller's behalf ends, the controller chooses whether we delete the workspace's data or first return it. It gets the data back by exporting and downloading it as in (1) or by asking us in text form for the files we hand over. If it has not chosen return by the time a deletion under (2) or (3) is due, we delete the data then; after a return we delete it as well.

(5) What the law requires us to keep, we keep only as long as required and process no further.

§ 10 Evidence and audits

(1) On request we give the controller all information needed to show compliance with this agreement, first through our documentation, the annexes of this agreement and a self-assessment we fill in, and through the reports and certificates of our sub-processors.

(2) Where these do not suffice, the controller, or an auditor it appoints who is bound to confidentiality and is not our competitor, may carry out inspections by appointment, with reasonable notice and without disproportionately disturbing our operations. Inspections take place at most once a year, except after a breach under § 8(3), on concrete indications that we do not comply with this agreement, or where a supervisory authority requires it of the controller.

(3) The controller bears its own costs. For an exceptional effort on our part beyond the information under (1), it reimburses our reasonable costs, which we state to it beforehand.

(4) For sub-processors, their reports and certificates serve as evidence. Where a question the controller needs answered remains open after them, we obtain the further information from the sub-processor.

§ 11 Liability

Towards data subjects the parties are liable under Article 82 GDPR. Their recourse against each other follows Article 82(5) GDPR. Otherwise the liability rules of the terms of service apply to claims under this agreement.

§ 12 Final provisions

(1) Where they conflict on the protection of personal data, this agreement takes precedence over the terms of service.

(2) German law applies. If the controller is a merchant (Kaufmann) and makes the contract for its trade, or is a legal person under public law or a special fund under public law, the exclusive place of jurisdiction is Stuttgart.

(3) We offer changes to this agreement as a new version. We announce it by email, for an organization to the person who manages billing, where their account has an email address, for an account to the account's email address, and offer it in Rondilo, on the organization's Billing tab or in the account, where it is accepted. Until then the previous version applies. If a change in the law requires a new version and the controller refuses it, either party may cancel the organization's subscription for the end of the current paid month or end this agreement for an account; § 9(4) then applies.

Annex 1: Description of the processing

Nature and purpose. Storing, showing, editing, downloading and deleting the workspace's content and, for an organization, its people; hosting parties of its quizzes on a live server, which for that holds the quiz, the data of the players and their connections and, for an organization, its id, name and logo link in memory only; storing, showing and downloading their History; for an organization also checking the invite link and the allowed email domains against an account's confirmed email address, sending the invite link by email to the addresses its Admins and the person who manages billing enter, showing its logo and name in its parties and notifying its people about roles, removal, joins refused because the organization is full, trials, payments, the coming deletion and reports.

Data subjects. The players in parties of the workspace's quizzes; people who appear in its content (texts, pictures, sounds); for an organization also the people in it and the people whose email address is entered for an invite email.

Kinds of data.

  • People, for an organization: account id, role, joined date. Name and email address are read from the account when people of the organization view them, and are not kept with the organization. Account ids of those who created or last edited a quiz or hosted a party. Who is editing a quiz right now (account, quiz, until one minute after the last sign of activity). Email addresses entered for an invite email, kept with the open invite (when it was sent and when it expires) until it is used or cancelled, and otherwise deleted within a day after its link ends, 14 days after it was sent. Who sent an invite is not stored.
  • Content: quizzes with texts, answers, settings and language; pictures (two WebP versions and a record with owner, time, size, width and height); sounds (one file and a record with owner, time, size and duration); for an organization its logo and default theme; up to 10 color pairs with an optional name; folders with name and time.
  • Parties: during the party, in the live server's memory, the whole quiz (texts, answers, settings and signed links to pictures and sounds), the host's account id, the players' names, answers (including typed text, poll votes and word cloud entries), points and answer times, and the IP addresses of the players' and the host's connections, which the live server uses, apart from the connection itself, only to fend off too many connections and join attempts. In History: the quiz title, the text and answers of each played question, figures for each question, poll votes, the most common words of each word cloud, all final scores without names, the names and scores of the top three, the names of up to three award winners, the host's account id. While Detailed History is on (in an organization through the setting "Detailed History in organization parties", in an account through the host's choice for the party), also each player's name, final score and rank and, for each question, their answer (including typed text, poll votes and word cloud entries), whether it was right, their points and their answer time. For an organization, its party totals (totals only).
  • Settings of an organization: its name, invite link on or off, its number, up to 10 allowed email domains, whether quizzes may be shared, whether Detailed History is on in its parties, public name.
  • Notifications about the organization to its people: the organization's id, for a role change the new role, for a report the quiz's link.

The workspace is not meant for special categories of personal data (Article 9 GDPR). The controller asks no questions whose answers would contain such data while Detailed History is on.

Duration. As in § 1(2) and § 9. History is kept until seven days after the quiz ends or until 30 days after the organization's Pro ends, for an account until 30 days after the end of a paid plan its holder held then or got since, whichever is later, unless deleted sooner. The data in the live server's memory ends with the party. Counters against too many connections, starts and join attempts, which hold account ids and IP addresses, count for one minute each and are gone at the latest when the live server stops. Editing markers and notifications are deleted automatically after they expire, usually within a day.

Annex 2: Technical and organizational measures

Data centers. We run no servers of our own. The data is in data centers of Google, Cloudflare and Fly.io, whose physical security the companies evidence.

Sign-in and administration. People sign in only through Firebase Authentication (with Google, with an email sign-in link or with email and password). Rondilo's admin area opens only after a server-side check against the administrator list. Production is deployed only from the operator's computer with the operator's own Google account. The development environment deploys automatically through Google Workload Identity Federation, with no Google key stored. The key that opens our sealed secrets is held by the operator and, for that deployment, as a secret at GitHub. Access to the live servers uses a key valid for that one app at Fly.io only.

Data access. The browser has no direct access to the database or storage. The Firestore and Cloud Storage rules refuse every such access, and the storage for pictures and sounds at Cloudflare has no public access. Every access to the workspace goes through our server code, which checks on each request whether the person is in the organization and which role they have, or whether it is the account holder, and which refuses all editing and hosting while an organization is read only. Pictures, sounds and the logo reach the browser only through signed links valid for at most 7 days. The operator can technically reach all data through the Google, Cloudflare and Fly.io consoles. The operator opens the workspace's content or History only on the controller's instruction or where the law requires it.

Separation. Each organization's and each account's data sits logically separated under its own key, in the same database as all others. Other accounts, people of other organizations and outsiders are refused, except for a quiz shared through its link or published to Discover, and the content players see in a party. Signed links to pictures, sounds and the logo stay valid for up to 7 days, also after a person has left the organization.

Encryption and transfer. Connections from browsers and devices to our services are encrypted with TLS. For the live servers, including calls from our server functions, TLS ends at the Fly.io edge server the connection runs through. There it is decrypted, and Fly.io carries it on to the live server over its own network, encrypted with WireGuard. Google encrypts the database and its storage at rest. Cloudflare encrypts the storage for pictures and sounds at rest. Server functions and live servers call each other only over HTTPS and identify each other with credentials issued by Google and signed requests. The invite link is not stored but checked with a secret key. It sits in the fragment of the address and so reaches no log. Secret keys are kept encrypted with AES-256-GCM and inserted at deployment.

Input and logs. Each organization quiz records who created it and who last edited it. Our application logs contain no names, answers, scores, content, organization ids, email addresses, links or IP addresses, and are kept for 30 days at Google and seven days at Fly.io. We exclude the request logs of our server functions from storage. Google keeps IP data of page delivery for a few months and of sign-in for a few weeks, and audit logs of administrative actions on the project for 400 days. Google sets these periods.

Availability. The database runs as a regional Google offering in europe-west1 with Google's redundancy. Pictures and sounds are stored at Cloudflare in its EU jurisdiction, with Cloudflare's redundancy. Backups of Firestore are enabled in the Google Cloud project. Deleted data can remain in them until those backups expire; we do not restore it from them into use. Deleted pictures and sounds cannot be restored. Alerts tell us when a live server runs twice, the paid live servers are fully in use, a message arrives through the contact form, a deletion run for pictures and sounds is overdue or costs reach a threshold.

Testing the measures. Automated tests in our code check that the Firestore rules and the Cloud Storage rules refuse every access from the browser, that pictures and sounds are handed out only through time-limited links our server functions issue, and that our logs contain no names, email addresses, answers, scores, content, links, IP addresses or organization ids. We review these measures at least once a year.

Data minimization and deletion. Names and email addresses of the people in an organization are not kept with it. The address of an invite email is kept only with its open invite. Its link works for 14 days, and the address is deleted once the invite is used or cancelled, otherwise within a day after the link ends. Deletion runs for pictures and sounds run daily. Editing markers and notifications expire by themselves. A party's state lives only in the memory of a single live server and ends with it. Our server functions' abuse counters hold only values derived with a secret key, from which the IP address or account id cannot be recovered, and expire within a day. The live servers' counters against too many connections, starts and join attempts hold IP addresses and account ids, in memory only, for one minute each. The country of a visit is worked out from the address with a table on our own servers, and the address is dropped at once.

Organization. Rondilo is run by one person, who is bound to confidentiality. Security incidents are reported under § 8(3).

Annex 3: Sub-processors

CompanyWhat it doesPlace of processing
Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, with Google LLC (USA)Database (Firestore), server functions, scheduled jobs, under the Cloud Data Processing AddendumBelgium (europe-west1)
Google Ireland Limited, with Google LLC (USA)Sign-in and accounts (Firebase Authentication), including sign-in emails; page delivery (Firebase Hosting); logs (Cloud Logging, 30 days; audit logs 400 days), under the Firebase Data Processing and Security TermsUSA (sign-in); worldwide (page delivery, logs)
Fly.io, Inc., USALive servers for parties: the quiz, players' names, answers, scores and answer times, the IP addresses of the players' and the host's connections, the host's account id, for an organization its id, name and logo link, in memory only and for as long as Annex 1 says; logs without these data seven daysFrankfurt (Germany), Ashburn, Virginia (USA), Singapore; the region usually follows the time zone of the device the party is started on, some starts always run in Frankfurt. TLS ends at the Fly.io edge server the connection runs through, which can be in another country
Lettermint B.V., Willemsvaart 16 B, 8019 AB Zwolle, the NetherlandsAutomatic sending of the organization's invite emails to the addresses its Admins and the person who manages billing enter, and of the emails about the organization's subscription to the person who manages billing: confirmations of conclusion, cancellation and withdrawal, notices of changes and a cancellation by us; a copy of each email for 28 days, deleted from backups no later than 14 days after thatEU (the Netherlands, backups in Germany)
STRATO GmbH, GermanyMailbox for contact@rondilo.com: instructions, requests and reports about the workspace, our replies to them and our other messages under this agreement, including notices of new sub-processors and of new versions of this agreement and breach notices, which we send by handGermany
Cloudflare, Inc., USAStorage for the pictures and sounds of the workspace and an organization's logo, under Cloudflare's data processing agreement with standard contractual clausesEU (Cloudflare's EU jurisdiction for R2 storage)

For the workspace, Lettermint sends only an organization's invite emails under this agreement. The automatic emails about an organization's subscription or an account's plan are our own processing (§ 1(3)); we name Lettermint here because these emails reach the person who manages billing. Lettermint sends no messages under this agreement.

These companies name their own sub-processors at cloud.google.com/terms/subprocessors, cloudflare.com/gdpr/subprocessors, fly.io/legal/sub-processors and lettermint.co/subprocessors.

Not sub-processors under this agreement: Link (Sold through Link, LLC) and Stripe, and in the apps Apple and Google Play, which act for payments as independent controllers; GitHub, which stores our code and deploys the development environment, holds the key to our secrets for that and receives no data of the workspace. When a quiz of the workspace is published to Discover, that is our own processing (§ 1(3)). We then have that version and, for an organization, the public name checked automatically by OpenRouter, Inc., New York (USA), with TypeSafe's model, with nothing stored there.