Back to home

Privacy Policy

Last updated: 24 October 2026

1. Who we are

MijnPas is a product of Appieo, a sole proprietorship (eenmanszaak) registered with the Dutch Chamber of Commerce (KVK) under number 92310729, VAT number NL004948484B06, established in Bussum, the Netherlands. Appieo is the controller responsible for the processing of personal data described in this policy. You can reach us at [email protected].

2. Our privacy principles

MijnPas is built around one rule: your data belongs to you, not to us. By default, everything you store in the app - loyalty cards, gift cards, membership cards and Authenticator codes - stays on your device and works fully offline. No account is required to use MijnPas. We do not sell personal data, we do not build advertising profiles, and we do not share your data with data brokers.

3. What data we process

Card data you add to the app (card numbers, names, colours, categories, barcodes) is stored exclusively in local storage on your device. It is never transmitted to Appieo's servers, because Appieo does not operate a server that stores user card data. The app does not require you to create an account, so we never collect an email address, password, or real-world identity to let you use MijnPas.

Website enquiries are separate from the data stored in the app. If you use our contact or partnership form, we process your name, email address, message and any company details you supply to respond to your enquiry. Resend delivers the internal notification and your acknowledgement, and Microsoft 365 stores the correspondence in our mailbox. Google reCAPTCHA processes technical information to protect the forms against abuse. Please do not submit passwords, recovery codes or sensitive documents.

4. Cloud Backup and end-to-end encryption

Cloud Backup is optional and off by default. If you turn it on, your data is encrypted on your device with AES-256-GCM before it ever leaves your phone, using a key that is generated and stored only on your device. The encrypted file is then uploaded to your own iCloud account (iOS) or your own Google Drive account (Android) - never to a server operated by Appieo. The encryption key itself is protected by a recovery code that only you see, once, when you set it up. Appieo cannot read, view, recover or reconstruct your backup contents under any circumstances, including in response to a support request, because we never have access to the key that decrypts it. If you lose both your device and your recovery code, that backup cannot be recovered by anyone - not by Appieo, not by Apple, not by Google. See our Terms & Conditions for how this affects recovery assistance, and the FAQ on this website for common questions about what this means in practice.

5. Permissions the app requests

MijnPas only requests a device permission when a feature genuinely needs it, and explains why at the moment it is requested:

  • Camera - to scan barcodes and QR codes when you add a card.
  • Photo library - to let you choose an existing photo of a card, or save a generated card/recovery image back to your library.
  • Location (while using the app, and optionally always) - to show the right card when you are near a matching store (Near Me) and to send a local notification when you enter one (Smart Store Notifications). This is entirely opt-in and processed on your device; your location is never uploaded, stored, or used to build a profile of where you shop.
  • Face ID / biometrics - to unlock the optional Privacy Lock protecting your Authenticator codes, and to protect Cloud Backup encryption on devices that support it, using your device's own secure biometric APIs. Appieo never receives your biometric data.
  • Notifications - to deliver the in-store alerts described above, entirely locally generated on your device.

6. Analytics, crash reporting and local diagnostics

MijnPas uses two separate tools from Google's Firebase platform - Firebase Analytics and Firebase Crashlytics - and separately keeps a fully local diagnostic log that never leaves your device. All three serve a different purpose, follow different rules, and are never combined into one system.

Analytics (enabled in release builds): MijnPas uses Firebase Analytics to understand how the app is used, so we can improve it. In release builds of the app, Firebase Analytics is active. What is collected: a per-installation identifier (a unique identifier Firebase assigns to each app installation, not linked to you personally or to an account), your device model, your operating system version, and your country or region (derived from your IP address, not GPS). Our own code sends a closed, reviewed set of usage events (feature interactions and counts) - never your card data, barcodes, gift card codes, OTP secrets, recovery codes, your PIN, encryption keys, backup contents, or your location or store-visit history. We use this data to understand which features people use and to improve the app. It is not used for advertising, not shared with advertisers, and not used to build a profile of you. The Firebase SDK also records a few standard events automatically, such as the first time the app is opened, the start of a session, and, on iOS, in-app purchases (the product, its price and currency, not your payment details). The legal basis for Analytics is our legitimate interest in understanding and improving the app (Article 6(1)(f) GDPR); you have the right to object to this processing at any time via [email protected]. Analytics data is processed by Google, our processor for Firebase, and may be processed outside the European Economic Area, including in the United States, under the safeguards Google provides for such transfers, such as the EU-U.S. Data Privacy Framework and standard contractual clauses. You can request deletion of analytics data associated with your installation by contacting [email protected].

Crash Reporting (optional, off by default): MijnPas uses Firebase Crashlytics to help us find and fix technical errors. Crash Reporting is off by default and only becomes active if you turn it on yourself, in Settings > Privacy & Data > Diagnostics. As long as you leave it off, no technical error report ever leaves your device. If you turn it on, a technical error or crash sends only strictly technical diagnostic information - such as an error code, the app version, and the technical cause of a failure - never your card data, barcodes, gift card codes, OTP secrets, recovery codes, your PIN, encryption keys, backup contents, or your location or store-visit history. You can turn Crash Reporting back off at any time. The legal basis for Crash Reporting is your consent (Article 6(1)(a) GDPR), which you withdraw by turning it off. We also use Firebase Crashlytics' 'Crash insights' feature for this, which compares technical crash patterns - never your personal data - against crash patterns from other apps that use Firebase, to help identify more quickly whether a failure has a known, cross-app cause, such as an operating system bug.

Local Diagnostics (optional, off by default, never leaves your device): Separately from Analytics and Crash Reporting, Settings > Privacy & Data > Diagnostics lets you turn on a local diagnostic log that records technical events only on your own device, for a retention period you choose of 3, 5, or 10 days. This data is never sent to Appieo, Firebase, or any other party; you can view it yourself and choose to share it, for example with a support request, but only if you decide to. Turning Local Diagnostics off clears the existing log immediately.

Analytics, Crashlytics, and local diagnostics collection are all disabled entirely in development (debug) builds of the app. Test builds distributed through TestFlight are release builds, so Analytics is active in them too.

7. Cookies on this website

mijnpas.app uses NEXT_LOCALE to remember your language preference. Cloudflare and Google reCAPTCHA may use security cookies to protect the website and its forms. Google Analytics cookies are only used if enabled and you consent through the cookie notice. See our Cookie Policy for details.

8. Your rights

Under the GDPR, you have the right to access, correct, delete, restrict, and export your personal data, and to object to its processing. Because your card data lives only on your device by default, you exercise most of these rights directly and instantly inside the app - deleting a card deletes it, and exporting your data gives you a full copy. Uninstalling the app removes everything stored locally on that device. If you want your encrypted Cloud Backup removed as well, use 'Delete Everything' in Settings before uninstalling: this deletes your local data and, where technically possible, the corresponding backup in your own iCloud or Google Drive account - see Section 9 for how this interacts with retention. For anything relating to analytics, or a request you cannot resolve yourself in the app, contact [email protected]. You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

9. Data retention

Card data and Cloud Backup files are retained for as long as you keep them in the app or in your own cloud storage - there is no separate retention period set by Appieo, because Appieo does not hold this data. Choosing 'Delete Everything' in Settings deletes your encrypted Cloud Backup immediately, where technically possible (this requires, for example, an internet connection at that moment) - see Section 8 for what to do if that deletion cannot be confirmed. Analytics data (usage events, device model, OS version, country/region, and per-installation identifier) is collected in release builds and processed by Firebase Analytics; Firebase retains this data under its own standard retention settings. Crash and technical-error diagnostics only exist if you have chosen to enable Crash Reporting in Settings; turning it off stops any new diagnostic data from being collected, and previously sent reports are retained by Firebase Crashlytics under its own standard retention settings. Local Diagnostics (see Section 6) stays only on your device, for a retention period you choose of 3, 5, or 10 days, and is cleared immediately when you turn it off.

10. Security

Sensitive local data - PIN hashes, recovery code hashes, biometric preferences, and Cloud Backup encryption keys - is stored in your device's dedicated secure storage (Keychain on iOS, Keystore-backed encrypted storage on Android), never in plain application storage. All network connections the app makes use HTTPS/TLS.

11. Children's privacy

MijnPas is designed to be usable from age 10 upward, as a practical tool for organising physical cards, not a service aimed at collecting children's data. We do not knowingly collect personal data from children beyond what is described above (which, for all users, is limited to locally-stored card data, and, only if you choose to enable them yourself, Crash Reporting or Local Diagnostics as described in Section 6).

12. Business transfers

If Appieo becomes involved in a merger, acquisition, restructuring, or sale of assets, your data remains protected by the privacy commitments described in this policy. Any successor or new owner may only use your data in accordance with these commitments, and any change to them follows the same process as any other update to this policy - see Section 13.

Today, your local card data, encrypted Cloud Backup, and usage data are not used for advertising or profiling, and are not sold to third parties, and Appieo (MijnPas's current owner) has no plans to change this. Appieo cannot read the contents of your encrypted Cloud Backup, protected by encryption we do not hold the key to - see Section 4.

If MijnPas ever changes ownership, a future successor could decide to change how your data is collected, stored, accessed, or used. Whoever owns MijnPas at that time will inform you at least 30 days in advance before any such change takes effect. You may delete your data - including your local card data and your encrypted Cloud Backup - through the app at any time before the change takes effect; see Section 8 for how.

A transfer of ownership does not by itself give a new owner additional rights to your data beyond what this policy, as it stands at the time, allows.

13. Changes to this policy

We may update this policy as the app evolves. Material changes will be announced in the app or on this website at least 30 days before they take effect.

14. Governing law and contact

This policy is governed by the laws of the Netherlands. Questions about this privacy policy can be sent to [email protected].

Appieo KVK 92310729 - VAT NL004948484B06 Bussum, the Netherlands