Your cards. Your control.
Privacy and your data
Here you can read which data PasKluis uses, why we use it and which choices you have.
Who is responsible for your personal data?
Ronald Bakker is the data controller for the processing of personal data by PasKluis described below. He determines why and how personal data is processed. Jordi Doppenberg supports PasKluis and provides hosting and technical maintenance on Ronald's behalf. Jordi only has access to personal data insofar as necessary for this work and is bound by confidentiality and security agreements. For legal and privacy questions, contact info@paskluis.com.
Your own cards
Your own loyalty cards, QR codes and gift cards are stored on your device. The card database is stored encrypted, with a key in secure device storage. From version 1.5.3, your own card images are also stored encrypted, with a key in secure device storage. During an update, the app converts existing managed images. Older versions before this security update did not apply additional encryption to individual images. Scanning and text recognition take place on your device.
Optional cloud backup is available during the testing phase through Settings → Backup. Once enabled, your own cards, PINs, notes and images are stored encrypted with your account on our own server running Supabase software. PasKluis manages the keys needed to restore data after you lose your phone; this is not end-to-end encryption. Unless you enable backup, your own cards remain local. Only successfully uploaded changes can be restored.
Account and Plus
Opening the app is not recorded as acceptance of the Terms of Use. If you explicitly accepted them in an earlier app version, the version, document identifier, language and time of acceptance may have been stored locally and with your account. The server also records the time of receipt. These existing records are deleted when your account is deleted. Without an account, any earlier acceptance records remain only on your device.
For your account, we process your email address, any name you provide, authentication details, language preference and Plus status on our own server running Supabase software. Our support team cannot see your password. Apple and Google process payments. PasKluis verifies purchase details to link Plus to the correct account and prevent misuse.
Only one device can be active online on an account at a time. We use a device identifier and session data for this. When you log in on another device, you can take over an existing session.
Shared cards
When you share a card, its details are stored online and made accessible to your chosen recipient. A gift card is shared in full, including its PIN or scratch-off code. Only share with someone you trust.
You can revoke shared access. This does not prevent a recipient from having already copied a code or taken a screenshot. Shared cards are not end-to-end encrypted.
Location and nearby shops
Location is optional. PasKluis only uses your location while you use the app if you enable the feature and grant permission. Your search location and the shop or card names for which you search for branches are sent to our server. For recognised retail chains, our server uses Google Places to find actual branches. An approximate search area and shop results are reused for up to 24 hours. The server does not build a personal movement history from this. If location cards are enabled, the app may store the last location used with a card on your device. These usage coordinates are not included when sharing or in new app backups; they are ignored when restoring older app backups. Distances are approximate straight-line distances.
From version 1.9, you can separately enable gift-card store reminders on iPhone and Android. This is off by default and requires notification permission and Always location permission. While you use the app, PasKluis retrieves store coordinates as described above. iOS or Google Play services on Android then locally monitors up to twenty saved stores in your last refreshed area, with a radius of around one hundred metres. It does not automatically monitor every branch in the Netherlands. There is at most one reminder per store every twenty-four hours. Open the app regularly to refresh nearby stores and card details; without refreshing, saved reminder data is no longer used after seven days.
For these reminders, your device stores store coordinates, notification text, an expiry time and the last notification time. Notifications can show the store name and your manually maintained balance, including on the lock screen. You can hide the balance in Settings. Card codes and PINs are not passed to this location monitor. Entering a store is not sent to our server for this feature. Turning off store reminders or location cards removes the saved store reminders and stops their location monitoring. You can also revoke permission on your phone.
Customer service and notifications
When you ask a question, we store your message, contact details, conversation status, language and limited technical information such as app version and platform. A screenshot you deliberately attach is kept in private storage and is only available to the conversation owner and authorised staff. Hide sensitive card details before sending a screenshot. Staff with the appropriate role can answer your question. Internal staff notes are not available to ordinary users.
Safe Support Mode is optional and requires a logged-in account. If you enable it yourself, the app generates a single-use code valid for ten minutes. After the code is used, an authorised staff member can view and adjust a limited set of technical settings, such as language, display and sorting, for up to thirty minutes. The app shows this capability before you grant support access. Activation, access and changes are logged, and you can revoke access. Card codes, card numbers, barcodes, QR codes, PINs, card images, passwords, payment details and your precise location or location history are never made available through this mode.
For support without an account, the app stores a secret access code in secure device storage. This lets you return to the conversation on the same device. Keep important answers yourself: recovery of guest conversations is not guaranteed after you erase the app.
Push notifications use Firebase and Apple's or Google's notification services. We register a notification address for your device for this purpose. You can turn notifications off in your phone's settings. A notification does not contain a full card code, PIN or the text of your support conversation. Support replies remain visible in the app when push notifications are turned off.
Retention and deletion
Your own cards stay on your device until you delete them. For cloud backup, we keep up to three successful versions, totalling no more than 10 MB per account. Turning backup off stops new uploads; existing backups remain until you delete them or your account. Received shared cards are not included in your own backup. Online account details and shared access remain necessary while you use those features. Delivered notification logs are deleted after 30 days when the configured cleanup runs. Customer service conversations and internal notes are kept for up to six months after closure for possible follow-up questions. Screenshots and attachments are kept for up to thirty days after closure. They are then deleted during daily cleanup, including from the administration system. Copies of conversations in the activity log are also erased when the conversation is deleted. If a question is reopened, the retention period only restarts once it has been resolved again. Open questions are regularly reviewed to assess whether they still need to be kept. Only where there is a demonstrable need, such as an ongoing dispute, can authorised staff record a reasoned exception, which must be reviewed again within ninety days at the latest.
Using ‘Remove from my overview’ only hides a conversation in your app; the retention periods above still apply. A new support reply makes the conversation visible again. This is not a request to erase your personal data. For that, contact info@paskluis.com. Read status and the choice to hide a conversation are stored with the conversation and disappear when it is permanently deleted.
Use Delete account to delete your account and associated personal data. Your own local cards are only erased if you choose that option in the app. A limited transaction reference may remain without a link to an account to prevent a purchase from being used twice. Daily encrypted server recovery copies on our server and in a restricted Google Drive folder are kept for up to fourteen days and deleted at the next scheduled cleanup. Data deleted from the active service may therefore temporarily remain in a recovery copy. These copies are only used for recovery, not for normal use of your data. The private recovery key is stored separately and is not uploaded to Google Drive.
Your choices and questions
PasKluis is ad-free. We do not sell your personal data or use your card details for advertising. The online service uses Supabase software on our own server. We use Google Places for shop searches, Firebase and Apple or Google for push notifications, and the app stores for payments. Encrypted server recovery copies are also stored in Google Drive. Technical processing by these service providers may take place outside the European Economic Area. You can request information about the service providers involved and applicable transfer safeguards through info@paskluis.com.
For access, correction, deletion, restriction, data portability, an objection or a privacy question, contact info@paskluis.com. We may ask you to confirm your identity without asking for your password. Where processing is based on consent, you can withdraw it without affecting the lawfulness of processing before withdrawal. The rights that apply depend on the processing. We normally respond to your request within one month. You can also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Updated on 8 October 2026.