Mistrum
Data Processing Agreement
Version 3 · effective 20 November 2026
Translation of the Czech original; in case of any discrepancy the Czech version prevails.
The agreement on the processing of personal data under art. 28 of the General Data Protection Regulation (GDPR) is an integral part of the Terms of Service of the Mistrum service.
1. Parties
Controller: the user of the Service who prepares estimates and offers for their clients in it (a tradesperson or company), identified by the data of their account.
Processor: Sergej Děďuchin, ID No. 09827064, Kurzova 2222/16, 155 00 Praha 5, a natural person registered in the trade register (Municipal District Office Prague 13) (the “Provider”).
2. Subject matter and duration
2.1 The Provider processes for the Controller the personal data that the Controller enters into the Service (clients, jobs, photos of interiors, offers), data that the Controller’s clients enter on the link of their offer, and in Stavba data about the company’s people and sites (art. 3), solely for the purpose of providing the Service.
2.2 The processing lasts for as long as the Service is used. If the Controller deletes a job, a client or the whole account, the data is deleted at once (art. 9).
3. Nature, purpose and categories
- Purpose: preparing estimates and offers, recognising rooms and works from photos and text with AI, calculating the price, PDF and Excel offers, sending the offer to the client by e-mail and link, the client’s acceptance, rejection and requests regarding the offer, handing the offer over to the Controller’s Dokkio account on their instruction.
- Categories of data subjects: the Controller’s clients and their contact persons; persons who happen to appear in photos of interiors; in Stavba the Controller’s employees and collaborators (company members) and persons named in the diary, protocols and documents of the site (site manager, technical supervision, investor, suppliers).
- Categories of data: name, company, company ID, VAT ID, address, e-mail, phone; address and description of the job; photos of interiors and exteriors (location and camera data are removed on upload); areas, items and prices; time of the first view of the offer; on acceptance of the offer name, time and a hash of the IP address, possibly an image of the on-site signature; reason for rejection; text of a change request or question and the contact the client gives; delivery status of the e-mail with the offer.
- Stavba, categories of data: name, e-mail and role of a company member, their cost rate; attendance (arrival and departure time, break, absence, correction requests); only when the Controller switches it on the location of the phone at the moment of arrival and departure and a photo on arrival; construction diary entries (names of people on site, drawn signatures, weather); photos of the site; documents, receipts and suppliers’ invoices; orders; handover protocols with the names and signatures of both parties; device token for notifications.
- Special categories of data (art. 9 GDPR) are not processed by the Service on purpose. The Controller does not photograph people or documents and does not put health data and the like into the job description. The photo on arrival is not evaluated and is not used to uniquely identify a person, so the Provider does not process it as biometric data.
4. Controller’s instructions
4.1 The Provider processes data only on the Controller’s documented instructions. The instructions are given by the settings and use of the Service and by this agreement; other instructions are sent by the Controller to [email protected].
4.2 If the Provider considers an instruction to be contrary to the GDPR, it informs the Controller without delay.
4.3 The Provider does not process the Controller’s data for its own purposes. It uses prices from the Controller’s offers to refine estimates only if the Controller switches on “Share anonymous prices” in Settings, and always without names, addresses and photos.
4.4 Employee data (Stavba). The Controller is responsible for having a legal basis for the attendance, location and photo of their people, for informing them under art. 13 GDPR and Section 316(3) of the Labour Code about the extent and manner of monitoring, and for the settings of the Service matching their rules. For this the Service offers the text “Information for employees”: the app shows it before the first arrival (if location or photo is on) and the Controller prints it in Stavba (Information for employees, a PDF with a line for a signature). The text is not legal service.
4.5 Location and photo on arrival are off by default. If the Controller switches them on, the Provider determines the location of the phone only once at Arrival and Departure (never continuously or in the background), stores it with the attendance record and stores the photo in private storage; it does not use them for its own purposes.
4.6 AI proposal of a diary entry. On the user’s instruction (the button Propose entry) the photos of the day marked for the diary (at most 10, reduced), the user’s dictation or text and the names of the people who had attendance that day are sent to the AI, so that the proposal knows who worked. This is OpenRouter through zero-data-retention endpoints; data is not used to train models. The result is only a preview: nothing is written to the diary without the user’s confirmation and the proposal has the button “Report AI output”.
5. Confidentiality
Persons authorised to process data (the Provider and any collaborators) are bound by confidentiality.
6. Security (art. 32 GDPR)
- Confidentiality: encryption in transit (HTTPS) and at rest; separation of users’ data by row-level database policies; files in private storage reached only by time-limited links; service keys only on the server; the server accepts traffic only through Cloudflare.
- Offer link: a random, unguessable token; the client does not see purchase prices or the Controller’s margin on it; actions on the link have a limited number of attempts.
- AI: models receive only the data needed for the task, through zero-data-retention endpoints and with a daily cap on calls.
- Availability and recovery: daily encrypted backups of the database and files (14 daily and 8 weekly), restore checks, monitoring of operation every 5 minutes.
- Clean-up: anonymous accounts without activity for 30 days are deleted together with files; unfinished photo uploads after 7 days.
7. Sub-processors
7.1 The Controller grants general authorisation to engage these sub-processors:
| Processor | Purpose | Location and basis of transfer |
|---|---|---|
| Supabase, Inc. (project in the EU region – Frankfurt) | database, sign-in, storage of photos, signatures and PDFs | EU; transfers to Singapore and the USA (standard contractual clauses) |
| IONOS SE (server in Germany) | running the application, backups, background processing | EU (Germany) |
| Cloudflare, Inc. | DNS, reverse proxy and traffic protection (all traffic passes encrypted through Cloudflare), form protection (Turnstile), availability monitoring | EU/USA (DPF, standard contractual clauses as a fallback) |
| OpenRouter, Inc. and the model providers Anthropic, PBC and Google LLC | AI: recognising rooms and work from photos and text, follow-up questions, turning dictation into edits; for problem reports, turning the voice into text and translating it (in the shared Dokkio inbox) | USA (adequacy decision – DPF, or standard contractual clauses); zero-data-retention endpoints only (for Google models at most temporary retention for abuse monitoring), data is not used to train models |
| Resend, Inc. | sending e-mails (offers to clients, sign-in codes, estimates) and their delivery status | USA (DPF and standard contractual clauses) |
| Sendinblue SAS (Brevo, France) | backup sending of the same e-mails when Resend is down | EU |
| Google LLC (Firebase Crashlytics and Cloud Messaging; Sign in with Google) | crash diagnostics of the mobile app (technical crash data, no name or e-mail); notifications to Android phones (device token and notification text); sign-in, if you choose it | EU/USA (DPF) |
| Apple Inc. (Apple Push Notification service) | notifications to iPhone (device token and notification text); Sign in with Apple, if you choose it | USA (standard contractual clauses) |
| OpenMeteo GmbH (Switzerland) | weather for the construction diary: our server sends the municipality of the project and the date, no data about people | Switzerland (adequacy decision) |
7.2 The Provider announces a change of sub-processors at least 30 days in advance by e-mail or in the app; the Controller may object before the change takes effect and stop using the Service. The Provider imposes on sub-processors obligations equivalent to this agreement and is responsible for their performance.
7.3 Transfers outside the EU take place only on the basis of an adequacy decision (EU–US Data Privacy Framework, “DPF”) or standard contractual clauses.
7.4 Dokkio is not a sub-processor: the Provider hands the offer over to the Controller’s Dokkio account only when the Controller connects it and starts the handover themselves. Processing in Dokkio is governed by the Controller’s contract with Dokkio.
8. Assistance
8.1 The Provider helps the Controller to fulfil obligations towards data subjects (access, rectification, erasure, portability), mainly through the functions of the Service: editing and deleting a client, job and offer, Data export and Delete account in Settings.
8.2 The Provider helps with impact assessments and consultations with the supervisory authority within the scope of the information it has.
8.3 The Provider reports a security breach to the Controller without undue delay, at the latest within 48 hours of discovery, with a description of its nature, the categories concerned, the likely consequences and the measures taken.
9. Termination
If the Controller deletes the account in Settings, the data is deleted at once with the files; it disappears from backups in the normal rotation cycle within 8 weeks at the latest. The Controller downloads the export beforehand (Settings → Data export). Data is not kept longer unless EU or Czech law requires it.
10. Audit
On request the Provider provides the Controller with the information needed to demonstrate compliance with the obligations under art. 28 GDPR and allows an audit by the Controller or an appointed auditor at most once every 12 months, after 30 days’ notice and without disrupting operation; the cost of the audit is borne by the Controller.
11. Final provisions
The liability of the parties is governed by art. 82 GDPR and the Terms of Service. The agreement takes effect when the Controller first uses the Service; no separate consent is needed. Governing law: Czech Republic.