Privacy Policy
Prüfprotokoll (store name "Prüfprotokoll – Prüf-App"), for Android and iOS, published by Steinwerk Labs.
Package / bundle identifier: io.kirolabs.prf.protokoll
Last updated: 6 October 2026
Deutsche Fassung: siehe „Datenschutzerklärung“ weiter unten auf dieser Seite.
1. The short version
• There is no account. No sign-up, no login, no password. Prüfprotokoll has no server of its own.
• Your inspection data stays on your device. Customers, sites, assets, inspections, photos, signatures, reports and backups are stored in the app on your phone or tablet. Steinwerk Labs never receives them and cannot recover them.
• A few services receive technical data: Firebase Analytics (usage events) and Firebase Crashlytics (crash reports), both only if you consent (off until you agree, changeable at any time), Firebase Remote Config (app configuration), and RevenueCat with Apple or Google for Prüfprotokoll Pro purchases. No customer or inspection content is ever sent to them.
• No advertising, no advertising profiles, no sale of data.
• You can delete everything yourself by deleting records in the app or by uninstalling it.
Prüfprotokoll is a documentation tool and not legal advice. See section 9.
2. What stays on the device
Prüfprotokoll helps inspectors document safety and work-equipment inspections. The app stores the following in a local database and file store in its own private storage:
• customers, sites and location structure, including names, addresses, contact persons, phone numbers, email addresses, notes and logos that you enter;
• assets with identification data (inventory number, manufacturer, model, serial number, QR/barcode values) and their history;
• inspections: checklist answers, measurements, defects, corrective actions, repairs and notes;
• photos taken or imported by you, with annotations;
• signatures drawn on screen (inspector and, optionally, customer representative) with printed name, role, place and timestamp;
• generated reports (PDF), CSV files, QR labels and encrypted backup files that you create;
• your inspector and company profile, templates, reminder settings and app settings.
None of this is uploaded, synced or shared between devices, and Steinwerk Labs cannot read it. There is no Prüfprotokoll account to restore it from: if you delete the app or lose your device without a backup, it is gone. We cannot restore it for you, because we never had it.
Your customers' data. Records about your customers and their sites may contain personal data of third parties (for example contact persons or signatories). You decide what you enter and are responsible, as the data controller for those records, for having a lawful basis, informing the persons concerned and observing retention duties. Steinwerk Labs does not process this data: it is processed only on your device, with the app as your tool.
Camera. The camera is used for scanning QR codes/barcodes and for taking inspection photos. Scanning happens on the device. Photos are stored in the app's private storage and are not uploaded. The camera permission is requested only when you first use these functions.
Notifications. Due-date reminders are local notifications scheduled by the app on your device. The app does not use push notifications, and no notification content passes through any server.
App lock. If you switch on a PIN or biometric lock, a biometric check is performed by Android or iOS; the app only learns whether it succeeded and never receives biometric data. The PIN is stored on your device only, protected by the platform's secure storage.
Operating system backups. Depending on your device settings, Android Backup or an iCloud device backup may include the app's data as part of a whole-device backup. Google and Apple create, store and delete those backups under their own privacy policies, not this one, and Steinwerk Labs cannot access them. You can switch off backup for the app in your device settings.
Reports, CSV and backup files. PDF reports, CSV exports and encrypted backup files leave the app only when you save or share them through the system share sheet or file picker. After that, whoever holds the file (your cloud drive, email provider, your customer) is responsible for it. Steinwerk Labs is not part of that transfer. Backup files are encrypted with a password you set; if you forget the password, the backup cannot be opened.
3. What leaves the device, and who receives it
The app sends data only to the services below. For each one: what it is, what it sends, what it never sends, and how to switch it off. Nothing else is sent anywhere.
3.1 Firebase Analytics (Google), only with your consent
Opt-in. The app asks you once during onboarding. Until you agree, analytics collection is off and nothing is sent. The answer is stored on your device and you can change it at any time in More → Privacy → Usage statistics and crash reports.
What it is for: seeing in aggregate which parts of the app are used and where people get stuck, so we know what to improve.
What it sends: usage events (for example that a screen was opened, that an inspection was started or finalized, that the paywall was viewed or a purchase completed), with fixed values or counts. Firebase also collects standard technical data: app version, operating system version, device model, language, a country or region derived from the IP address, session and engagement times, and a resettable Firebase app instance ID generated for this installation.
What it never sends: customer names, site or asset names, serial numbers, checklist answers, measurements, defects, notes, photos, signatures, report contents or anything else you typed. The events contain no such content.
How to switch it on or off: in More → Privacy → Usage statistics and crash reports. Switching it off stops collection immediately. Steinwerk Labs does not use analytics data for advertising and does not sell it.
3.2 Firebase Crashlytics (Google), only with your consent
Opt-in. Crash reporting is off until you agree in onboarding, and uses the same single choice as analytics.
What it is for: finding out when and where the app crashes so we can fix it.
What it sends: the stack trace (where in the code the crash happened), app version, operating system version, device model, free memory and disk space and similar technical state at the time of the crash, and a Crashlytics installation identifier used to group repeated crashes.
What it never sends: your customers, assets, inspections, photos, signatures or anything else you entered.
How to switch it on or off: together with analytics, in More → Privacy → Usage statistics and crash reports.
3.3 Firebase Remote Config (Google)
What it is for: changing app configuration without a new release: feature switches, the pricing/paywall configuration, the free-inspection allowance, emergency switches, and a minimum app version that must be installed if a build is found to put your data at risk.
What it sends: a standard request containing the Firebase app instance / installation ID, app ID, app version, platform, language and country. It only downloads configuration and keeps the last copy so the app works offline.
What it never sends: anything you have entered. Remote Config cannot be switched off, because it is how we stop a build that we have found to be unsafe for your data. If the app cannot reach it (for example offline), the app keeps working with the last stored configuration.
3.4 Purchases: RevenueCat, Apple App Store and Google Play
If you subscribe to Prüfprotokoll Pro, Apple or Google processes the payment. RevenueCat (RevenueCat, Inc.) validates the purchase and tells the app whether Pro is active.
RevenueCat receives: an anonymous app user ID it generates for this installation, the store receipt or purchase token, product ID, purchase and expiry dates, platform, store country and currency, app and operating system version and your IP address. The app contacts RevenueCat to check your Pro status even if you have never bought anything. No account is created and the ID is not linked to your name or email.
Steinwerk Labs never sees your card number, name or billing address; Apple and Google keep those under their own privacy policies. RevenueCat never receives your customers, assets, inspections or anything else you enter. See RevenueCat's privacy policy (https://www.revenuecat.com/privacy).
3.5 Support email
Our support address is labskiro@gmail.com. If you write to us, we receive your email address and whatever you choose to send, and keep it as long as needed to help you. Please do not send customer data or personal data of third parties that we do not need to solve your problem. We do not use your address for marketing or add it to any list.
3.6 What the app does not do
• No advertising and no advertising SDK; no advertising identifier.
• No tracking across other companies' apps or websites.
• No account, no cloud storage, no server-side copy of your data.
• No location access, no contacts access, no microphone.
• No sale or rental of personal data, ever.
4. Children
Prüfprotokoll is a professional tool and is not directed at children under 13, or under 16 in the European Economic Area. We do not knowingly collect data from children. The app has no account or profile, so it cannot identify any user of any age.
5. Your rights and the legal basis
If you are in the European Economic Area, the United Kingdom or Switzerland, data protection law (GDPR) gives you the rights below. Most of them you can exercise yourself, immediately, in the app.
Controller. Steinwerk Labs (contact in section 10) is the controller for the analytics, crash and configuration data in sections 3.1 to 3.3, for the purchase status handled through RevenueCat in section 3.4, and for support emails. Google (Firebase) and RevenueCat process that data for us as processors. Apple and Google as app stores handle payments under their own responsibility. The inspection data you keep in the app (section 2) is not processed by Kirolabs at all.
Legal basis.
• Usage statistics and crash reports: your consent (Art. 6(1)(a) GDPR and § 25(1) TDDDG for access to information on your device), given in onboarding. You can withdraw it at any time in More → Privacy → Usage statistics and crash reports; withdrawal does not affect processing that happened before.
• Remote Config: necessary to provide the app as intended and keep it safe to use (Art. 6(1)(b) and (f) GDPR).
• Purchases and Pro status: necessary to provide what you bought (Art. 6(1)(b) GDPR).
• Support emails: our legitimate interest in answering you (Art. 6(1)(f) GDPR).
Access and portability. Everything the app holds is visible in the app itself, also without Pro and after Pro ends. CSV export and encrypted backup are free forever. We cannot give you a copy of your inspection data ourselves, because we do not hold one.
Erasure. You can delete single records, or uninstall the app, which removes all local data. Copies you saved or shared elsewhere are outside the app and are not affected. The analytics and crash data we receive is not linked to your name, email or any account, so we usually cannot tell which records are yours (Art. 11 GDPR); it is deleted automatically when its retention period ends (section 6). If you contact us, we will do what we can.
Rectification. You can edit your records in the app at any time (finalized inspections are changed only through an amendment or re-inspection, as the app's records are meant to be tamper-evident).
Objection and withdrawal. Withdraw your consent in More → Privacy → Usage statistics and crash reports.
Complaint. You can complain to a data protection supervisory authority, in particular in the country where you live.
Transfers outside the EU. Google and RevenueCat may process data in the United States. Transfers rely on the EU-U.S. Data Privacy Framework where the recipient is certified, and otherwise on the European Commission's standard contractual clauses.
6. Retention
• Data on your device is kept until you delete it or uninstall the app. Backup files, reports and exports you saved are kept wherever you put them until you delete them.
• Firebase Analytics event data is kept for the retention period set in our Google Analytics property (default 2 months, maximum 14 months) and then deleted automatically. Aggregated reports may be kept longer.
• Crashlytics crash reports are kept for 90 days.
• Remote Config request data is handled by Google for delivering the configuration and is not stored by us.
• Purchase records at RevenueCat and Apple or Google are kept as long as needed to provide Pro and to meet accounting and tax obligations.
• Support emails are kept as long as needed to resolve your issue. We delete them on request.
Record retention duties. Inspection records may have to be kept for periods set by law, your employer, your customer or your insurer. Because we hold no copy, keeping and backing up your records is your responsibility; use the free encrypted backup.
7. Security
Your data sits in the app's private storage, which the operating system keeps separate from other apps and encrypts when your device is locked with a passcode. You can add a PIN or biometric lock in Settings, and backups are encrypted with your password. Firebase and RevenueCat are contacted over encrypted HTTPS connections.
The strongest protection is how the app is built: no Steinwerk Labs server holds a copy of your customers, assets, inspections, photos or signatures, so there is nothing of yours on our side to breach. Please protect your device with a passcode and keep backup files somewhere safe.
No method of storage is perfectly secure, and we do not claim otherwise.
8. Changes to this policy
If we change this policy, we will update the date at the top, and tell you in the app before a significant change takes effect.
One commitment will not change: Steinwerk Labs will not start sending your customers, assets, inspections, photos, signatures or reports to Kirolabs or anyone else without your explicit action. If we ever offer something like cloud sync or an account, it will be optional, off unless you turn it on, explained before you do, and this policy will be updated first.
9. Not legal advice
Prüfprotokoll supports the documentation and organisation of inspections. It does not replace a risk assessment, manufacturer information, applicable laws and regulations, or any required qualification, and it does not guarantee legal or regulatory conformity. See the Terms of Use, section 1.
10. Contact
Questions about this policy, your data or the app:
labskiro@gmail.com
https://kirolabs.io/contact
Terms of Use: https://sites.google.com/view/pruefprotokoll-terms