Nederlands

PRIVACY EXPLANATION OF MAINTENANCE REPORT

Version 19.0 · 22 November 2026

1. Who is responsible?

Marco Hoogewerf, Netherlands, manages this app and is responsible for the processing of account, rights and agreement data for the app. Contact: Onderhoudsapp@hotmail.com. For personal data that you process in reports on behalf of an employer or client, that organisation may be responsible for this. Therefore, agree to use it.

2. What data and why?

For login and account management, we use your email address, a unique user code, your email confirmation status and registration data via Firebase Authentication. Firebase also processes authentication data, including your password, and technical data such as IP address and user information from the device for security and abuse prevention. Marco does not see a readable password via the normal management function.

Cloud Firestore stores your profile with e-mail address, possibly your name and creation date, any editing rights and the moment and administrator of rights changes. When agreeing, we keep under your user code the terms and privacy version, content features (SHA-256), the time at which the server records the agreement and whether this happens during registration or later. The app stores a confirmation locally to not need internet every time after a successful agreement.

For abuse prevention, Firestore stores under your user code the start of the limit period, the number of requests, the last application time and any document code. Per request, we store the document code and the creation time, and if necessary a removal mark to prevent repeated uploading of deleted cloud files. These records do not contain any report content and will be kept until your account with associated data is deleted.

The basis for necessary account and rights management is implementation of the agreement for use of the app. Security, abuse prevention and the ability to demonstrate agreements serve legitimate interests: a trustworthy app and the settlement of disputes. We weigh these interests against your privacy and limit the data to what is necessary for this purpose. Where a legal obligation applies, it can be the basis. The check for terms of use is not a general consent for additional use of personal data.

3. Reports, photos and recipients

Project data, addresses, names, answers, measurements, comments and selected photos are processed locally into PDFs. Local drafts, imported report photos and archive PDFs are encrypted with Android Keystore. Temporary partial copies are readable and are cleared with active app usage. Personal logo templates, templates and exported PDFs are not covered by that additional encryption. After your storage selection or shipping confirmation, PDF and search metadata (project, installation, mechanic, type, time, content attribute and end date) are linked to your user code in Cloud Storage. The cloud period depends on the subscription. Marco can view cloud reports for support; other users can only view their own files.

For the necessary storage and provision in the report service requested by you, we use the performance of the agreement as the basis for your personal data. For personal data of colleagues, customers or others who are entered on behalf of an organisation, that organisation must determine in advance the purpose, the basis and the competence to share with Marco. Where Marco processes only on behalf of that organisation, appropriate processor arrangements must be made before actual business data is uploaded. Agreement with these terms does not give general consent on behalf of other persons. When choosing a photo, the app that copies to its own storage. Original photos remain outside that storage.

When viewing PDF, downloading to your phone or sharing, you give another app access to the chosen PDF. When emailing, your email service and the recipients you choose will receive the content. This will also apply to their own privacy and retention policies. Add as little personal data as possible. Your device or operating system may back up or transfer app data depending on settings. Such copies are also covered by the policy of the chosen backup service.

For personal lists, we keep under your user code in Firestore the name, optional layout section, original list type, revision, modification time and the full definition with cover fields, sections, questions and response options. This is necessary to store and re-use your own forms. Do not include customer data in the preview questions; real report answers remain part of the report. The app can store a local cache of the lists. The lists are only readable by the creator via the app; other users, including the owner's account, cannot request them there. Technical project management remains possible for the provider via the secure management environment, for example, with a removal request. Templates remain valid until you delete them or delete your account with the corresponding data. An existing report copy follows the retention period of that report.

Support and messages: send new general questions from your own email app to Onderhoudsapp@hotmail.com. The app prepares an email draft; Marco only receives your email address, message and any attachments after you send it. These new questions are not stored as conversations in Firestore. Previous support conversations remain available to read and delete in the app. They contain your user ID, account email address, subject, question, replies and timestamps; only you and the developer can access them through the app. The existing inbox holds up to 20 conversations. Only optional bug reports are still sent directly from the app; their data and retention period are described below. App announcements retain up to the latest 20 online messages; your overview shows the latest 20 online and built-in update messages together. Reports and photos are not attached automatically. Do not share PINs, passwords or unnecessary customer data. This processing serves to respond to your support request.

4. Who has access and where is data processed?

Marco can manage account, rights, and agreement data and access completed cloud reports from all users of this app through its owner's account. Other users can only access their own reports. Google/Firebase provides technical services. The app uses access rules to enable users to read their own permitted account data and the owner has the right to manage it. This does not mean that any security incident is excluded.

Firebase Authentication processes data in the United States. Firestore and PDF storage are set to europe-west4 (Netherlands). This does not mean that all technical data or all processing of Google takes place exclusively in the Netherlands; processing by Google may also take place outside the European Economic Area. Google describes the applicable processor conditions and transfer guarantees, including standard contractual clauses and where applicable the EU-US Data Privacy Framework, at https://firebase.google.com/support/privacy. You can ask Marco for information about the project settings and applicable safeguards.

5. How long do we keep data?

Account and permission data are needed while you use your account. Under My profile > Delete account, confirm with your password that you want to permanently delete your account and online data. Once the server receives the request, access is blocked and the account, profile, permissions, consent records, cloud reports, personal templates, support data and abuse-prevention records are deleted automatically. A technical deletion record containing your user ID and status is retained for up to 30 days after completion to block old sessions and safely handle retries. Failures may delay completion; failed tasks are retried. Local files and recipients’ copies are not erased remotely. For help without access to the app, email Onderhoudsapp@hotmail.com. Technical backups and service-provider logs follow Google’s retention periods and are not immediately erased by the app.

The following cloud and local report storage limits apply: BASIC: 25 cloud files, 1 calendar month, 3 days of local PDF storage, 8 MB and 8 images per report, 2 new reports per day. BRONS: 75 files, 3 calendar months, 7 days locally, 10 MB, 10 images, 5 reports per day. SILVER: 150 files, 9 calendar months, 10 days locally, 20 MB, 15 images, 10 reports per day. GOLD: 250 files, 20 calendar months, 14 days locally, 30 MB, 20 images, 20 reports per day. MB means 1,000,000 bytes. The cover photo counts towards the image limit. You may keep up to 20 drafts per phone/account, without automatic expiry. Existing files retain their assigned expiry date after a downgrade. The server blocks access to expired cloud files. Scheduled physical deletion may be delayed during failures. Your own downloads, original gallery photos and email attachments are not affected.

Remembering the email address option only saves your email address and the preferred local address. Disables deletes the memorized address. The app does not save a password for this. Firebase manages the login session.

Concepts do not have an automatic expiry date in the app. You can delete them yourself. The local archive PDF and complete input of completed reports expire after the assigned 3, 7, 10 or 14 days after storage in cloud or your shipping confirmation; local cleanup occurs when the app is actively used. Then, we store only project/location, project number, maintenance number, location/address, installation, report type, shipping date and technical references/status for your shipping summary. This short rule does not have an automatic expiration date; delete it yourself when you no longer need it. For a self-preserved or linked PDF, the app also preserves the file reference and read permissions. This PDF is not part of the automatic clearance. Only an accessible PDF button gets a PDF button. Manual removal of a rule does not clear the own PDF. Photos that are still used by other reports. E-mails, exported PDFs, original photos and photos. device backups have their own storage periods. Logout does not delete your local reports.

6. Your Rights and Contact

You can request access, correction, deletion, restriction and, where applicable, transferability of your personal data. You may object to processing on the basis of legitimate interest. Please email us at Onderhoudsapp@hotmail.com. We can verify that the request comes from you in an appropriate way. You will, in principle, receive a response within one month; if a legal extension is required, we will explain it. You can also submit a complaint to the Dutch Data Protection Authority via https://autoriteitpersoonsgegevens.nl.

7. Security and Modifications

Use a screen lock, keep your device updated and keep PDFs safe. Report suspected abuse, theft with possible access to app data or data loss from Marco. The provider retains its own security and any reporting obligations. Changes to this privacy policy will be given a new version date and will be published in the app. Reading this statement is not a waiver of your privacy rights.

Subscriptions and advertisements

Paid subscriptions are purchased through Google Play. The payment screen shows the current price, billing period and renewal. Manage or cancel in Google Play; deleting the app or app account does not cancel a Play subscription. Restore purchases in My profile using the same app account. BASIC may display ordinary ads; paid tiers do not. Optional rewarded videos remain available to every tier, up to three per day in the Netherlands. The app uses Google AdMob and requests advertising consent through Google where required. Reopen privacy choices under My subscription.

For purchase control, we store the product code, purchase token, subscription status, end date and a technical code linked to your app account. Google processes the payment; the app does not store card data. For advertising rewards, user code, a temporary random code, transaction feature and day counter are processed to award a reward once. AdMob can process device, advertising, IP and interaction data according to Google's privacy choices and policy. Report content is not sent as an ad parameter.

One-time transition to 2.0

In this explicitly announced transition, old app reports, drafts, report photos, cloud copies, personal templates and logos will disappear. Accounts will continue to exist. Personally exported PDFs, gallery photos and email attachments will be retained. New 2.0 data will be separate; this reset will not be repeated at every update.

Installation link and optional bug reports

New accounts start with BASIC. To limit repeated registration, the app uses a derived Android ID code. The server stores this code with a registration marker and, while needed for registration and support, your user ID, a derived email address and a derived attempt code. The password is only securely passed to Firebase Authentication and is not stored in Firestore or app files. Registration or signing in with an existing account marks the device as used. Signing in with another existing account remains possible and does not change its permissions. Clearing app data or reinstalling with the same signing key on Android 8 or later normally does not change this code. A factory reset, another Android profile, another signing key or a modified device may change it; this is not an absolute hardware block or an IP block. After account deletion, only the derived device code and the used marker remain to limit re-registration. The account and registration-attempt links are removed. This security record remains until the developer releases it after a support request or this protection is discontinued. For questions, objections or an incorrectly blocked second-hand phone, contact Onderhoudsapp@hotmail.com. A separate random installation code is still used for bug support and is removed on account deletion.

If you choose Report a bug, the developer receives the displayed error, app section, user ID, app version and derived installation code. No photos or report files are attached; the error text may contain details shown on screen. After three bug reports within 24 hours, further bug reports are blocked until 24 hours after the third report. The rest of the app remains available. The developer can review how often this limit is reached and how many new attempts are made during a block. These counters are retained until account deletion; repeatedly reaching the limit is not automatic proof of abuse. Reports are periodically deleted after 90 days; outages may delay deletion. You may close the dialog without sending anything.