Privacy
What personal data ClimaToolkit keeps, why, where and for how long, and what rights you and your customers have.
Draft of 20 November 2026
Who runs ClimaToolkit
Two kinds of data, two roles
Your own data as an account holder: your email, your technician details, your units’ records and your settings. For these, we are the controller. Your customers’ data that you type on a unit: name, installation address, phone and email. For these, you are the controller and we are your processor: we keep them only for you, as the data processing agreement in our terms sets out (GDPR Art. 28). Google (Firebase) stores and processes both kinds for us as our sub-processor (see “Where the data is kept”).
Your own data: what, why, how long
Email and sign-in: your email address, the sign-in links we send, your password if you set one (we never see it) and when you signed in. To give you an account. Legal basis: the contract with you (GDPR Art. 6(1)(b)). Your technician details: your company, its F-gas certificate number, your name, your personal certificate number and its type. To print them on your F-gas records and PDFs, as the F-gas Regulation asks (EU 2024/573 Art. 7(1)(e)). Legal basis: the contract. Your units and their records: technical data, history, leak checks, commissioning records, the yearly F-gas report. This is the service itself. Legal basis: the contract. Your plan (free or Pro). To be filled in: Payments: what Paddle (web) and Apple (iOS) pass to us. Step 10, not built yet. Technical logs: Google keeps the IP addresses of requests for a limited time, to keep the service secure and detect abuse (Authentication a few weeks, Hosting a few months, by Google’s own account). Legal basis: our legitimate interest in a secure service (Art. 6(1)(f)).
Your customers’ data on units
Who sees them: you, signed in to your account. We do not look at them; we access them only to fix a problem you report to us, or when the law requires it. Where they show: in your unit list (to search and sort), on the unit’s page, and on the PDFs you make from it (the service report, the commissioning protocol). How long: until you change or clear them, delete the unit or delete your account. Deleting a unit deletes its customer details and its whole history (our daily backups keep them 7 days more). When Pro ends: your units stay read-only. You can open them, download their PDFs and delete them, but not add or change anything. Nothing is deleted because Pro ended.
Where the data is kept
Cloud Firestore, the database (your profile, units, your customers’ details, history and records), and Cloud Functions: Google Cloud region europe-west3, Frankfurt, Germany. Firebase Authentication (your email and sign-in): Google runs it only in data centres in the USA. Firebase Hosting (the website and the app’s files): served worldwide through Google’s network and the Fastly content delivery network.
In your browser or app; no tracking
your language, calculator settings and reading preferences; that you are signed in, and during a sign-in by email link, your email and the page to come back to; a copy of your units and records (Firestore’s offline cache), so they work without signal. It is deleted from this browser when you sign out; changes not yet sent would be lost with it, so the app warns you first; the Pro knowledge, for use without signal for about 30 days; it is deleted when you sign out.
Security in short
Everything travels encrypted (HTTPS). The database refuses everything by default: each account can read and change only its own data. These rules are tested on Google’s emulator. Your customers’ details can be stored only on a unit; the database refuses them anywhere else. Signing in by email link proves the email address; a password is optional, Google keeps it and we never see it. Only the operator can manage the Firebase project. To be filled in: Confirm: two-step verification on that Google account, and that nobody else has access. A copy of the database is made every day and kept 7 days, in Frankfurt, to put things right after a mistake.
If something goes wrong
Your own data: we report it to the Slovak data protection authority within 72 hours of finding out, unless it is unlikely to put anyone at risk (GDPR Art. 33(1)), and tell you without undue delay if the risk to you is high (Art. 34). Your customers’ data: we tell you without undue delay (Art. 33(2)), with what we know, so that you can meet your own duties as their controller (72 hours, Art. 33(1)).
Your rights
When your customer asks about their data
show them what you keep: open the unit, or give them its PDF; correct it: edit the unit’s Customer part; delete it: clear the Customer fields (the unit’s technical and F-gas record stays), or delete the whole unit.