Privacy Policy
Last updated: 12 November 2026
1. Who we are
This Privacy Policy describes how QR Loyalty Card, published on Google Play as
QR Loyalty Card App (“we”, “us”, “our”), processes information in the
QR Loyalty Card mobile application and related services.
The service runs on Google Cloud / Firebase infrastructure.
Controller / operator:
Madala Apps
Address: Luky 30, 020 53 Luky, Slovakia (SK)
Contact: qrloyaltycard@gmail.com
Website: https://qrloyaltycard.com/
Important: Customers use QR Loyalty Card without creating an account.
We do not collect customer names, emails or phone numbers.
However, to make the loyalty feature work (count visits and enforce cooldown), we use a
pseudonymous device identifier (see Section 2.2).
2. What data we collect
2.1 Business / admin accounts
- Account identifiers: email address, Firebase Authentication UID.
- Business profile data: business name, logo, contact details, links, reward
description and configuration.
- Store location data: if location verification is enabled, the
business/admin
may save the GPS location of the business or organization so that customer visits can be
verified near that location.
- Content you submit: images and other media stored in Firebase Storage.
2.2 Customers (end users) — no account
Customers can scan a QR code or tap an NFC tag to interact with a business and collect visits.
Customers are not required to register or provide personal details.
-
Pseudonymous device identifier (hashed):
to prevent abuse and to count visits, the backend creates a pseudonymous identifier by
hashing a stable app/device signal (e.g. Firebase installation ID or an equivalent token).
-
Loyalty/visit data:
visit counters and timestamps stored under a pseudonymous identifier.
-
Location verification data:
when a customer records a visit, the app may request the current device location to verify
that the customer is near the business or organization location.
-
No direct identification:
we do not collect names, emails, phone numbers or addresses of customers.
2.3 Push notifications (optional)
If enabled, Firebase Cloud Messaging (FCM) is used to deliver notifications.
FCM tokens are technical device identifiers.
2.4 Diagnostics & security
- Crash diagnostics: Firebase Crashlytics may collect crash logs, stack
traces, app version and device/OS information.
- Security logs: minimal technical logs for abuse prevention and auditing.
2.5 Location verification
QR Loyalty Card may request access to the device’s current location when a customer
records a visit by
scanning a QR code or tapping an NFC tag. Location is used only to verify that the visit is
being
recorded near the relevant business or organization location.
QR Loyalty Card does not collect location data in the background and
does
not continuously track customers.
-
When location verification is used, the app may send the current latitude, longitude and
location accuracy to our server for verification.
-
The server compares the customer’s current location with the saved business or organization
location to determine whether the visit can be recorded.
-
For privacy protection, exact customer location is not used for advertising and is not sold
to third parties.
-
Verification records include only approximate distance from the business location,
location accuracy and whether verification passed. We do not store
customer latitude or longitude, not even rounded coordinates.
The location sent for verification is used only for the check and is not saved.
2.6 Guest / Demo mode
Guest mode is stored only on your device. No account is created, no data is sent to our servers, no tracking is used. Demo data is deleted when you sign in or when you clear the app data.
3. Purposes and legal bases (GDPR)
- Provide the service to businesses / admins: QR/NFC loyalty features under contract (Art. 6(1)(b)). For customers who have no contract with us, the same loyalty features are based on legitimate interest (Art. 6(1)(f)) - to provide the loyalty program the business offers and to prevent abuse.
- Push notifications: only with your consent (Art. 6(1)(a)). You can withdraw consent at any time in device settings. FCM tokens are deleted when consent is withdrawn.
- Crash diagnostics: legitimate interest (Art. 6(1)(f)) to keep the app stable and secure. Crash logs contain only technical data, no customer names or precise location.
- Visit verification: verifying that visits are recorded near the relevant
business or organization location (Art. 6(1)(f)).
- Security & abuse prevention: cooldowns, rate limiting, location
verification
and fraud prevention (Art. 6(1)(f)).
- Legal compliance: statutory obligations (Art. 6(1)(c)).
4. Information shown to businesses
Businesses see only aggregated statistics.
No personal customer identifiers are shared.
Businesses see aggregated statistics such as total visits, number of readers and completion
counts.
They do not receive customer device identifiers, hashes or FCM tokens.
If location verification is enabled, businesses may see whether visit verification is active and
may see general verification-related information, such as whether a visit was accepted or
rejected. They do not receive continuous location tracking data.
5. Sharing and processors
- Infrastructure: Google Firebase / Google Cloud
(Authentication, Firestore, Storage, Functions, FCM, Crashlytics).
- Legal disclosures: when required by law.
Depending on the context, we act as a data controller for business/admin account data and as a
service provider (processor) for pseudonymous loyalty data processed on behalf of businesses
using QR Loyalty Card. In that processor role, the business is the controller for its loyalty program and we process loyalty data only on its instructions. A Data Processing Agreement (DPA) is available on request at qrloyaltycard@gmail.com.
Transfers outside the EU: Data is processed on Google Cloud / Firebase infrastructure and may be transferred to the USA. Such transfers are based on Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
Google Fonts: This website loads fonts from Google Fonts. When you open this page, your IP address may be sent to Google to load the font.
5A. Payments and subscriptions (Google Play)
QR Loyalty Card offers optional paid subscriptions for business/admin
users.
Payments are processed exclusively by Google Play Billing.
-
We do not receive or store full payment card details.
-
Google processes payment information (such as billing account identifiers, purchase tokens
and transaction status) in accordance with its own privacy policies.
-
We store only subscription status (e.g. active, expired), expiry date
and one hashed reference (prefix) of the purchase token to unlock premium features and to handle Google Play notifications (RTDN).
We do not store the full purchase token.
This hashed reference is kept while the subscription is active and for 30 days after expiry, then deleted.
-
For accounting, we keep only a minimal extract (order ID, date, amount, country, VAT)
for 10 years as required by applicable Slovak accounting law (Act No. 431/2002 Coll., where applicable). No token,
device ID or location is kept in that extract.
For more information, see:
Google Privacy Policy
.
6. Retention
We keep data only as long as needed for its purpose. These are the shortest periods that still allow the service to work:
- Security and audit logs: 7 days.
- Business/admin account data: stored while the account is active. After
deactivation, data is permanently deleted within 48 hours, unless longer
retention is required by law (see accounting below).
- Inactive admin accounts: may be automatically deactivated
after 60 days of inactivity if the subscription has expired.
Paying accounts are never auto-deactivated for inactivity.
- Monthly aggregated statistics: kept for up to 3 months.
- Loyalty/visit data (pseudonymous) - readers / rewardProgress:
deleted after 90 days without a visit.
- Reward redemptions: deleted / anonymized after 30 days.
Only an anonymous count remains in business statistics.
- Visit history (visitEvents): 7 days.
- Purchase token links: deleted 30 days after subscription expiry.
Active subscriptions keep their link for Google Play notifications (RTDN).
- Deleted business tombstones: 7 days.
- Notifications: 30 days and at most the most recent 50 notifications per business.
- Location verification data: customer latitude / longitude is
never stored, not even rounded. Only distance, accuracy and
verification result are stored, as part of visit history (visitEvents), and are deleted after
7 days together with visitEvents. Loyalty counters without location are deleted after
90 days without a visit.
- Accounting extract: 10 years, minimal fields only
(order ID, date, amount, country, VAT), as required by applicable Slovak accounting law (Act No. 431/2002 Coll., where applicable)
7. Your rights
EU/EEA (GDPR)
You have the right to access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interest (Art. 6(1)(f)). Where processing is based on consent, you may withdraw consent at any time, without affecting prior processing.
We respond to requests within 1 month (extendable by 2 months for complex requests).
Customers without an account (pseudonymous): Because we do not know your name or email, please tell us the business / QR code or NFC tag you visited and the approximate time of visit so we can locate your pseudonymous record. Without that, we may not be able to identify your record.
You have the right to lodge a complaint with the supervisory authority: Úrad na ochranu osobných údajov Slovenskej republiky (Office for Personal Data Protection of the Slovak Republic), Hraničná 12, 820 07 Bratislava, Slovakia, dataprotection.gov.sk.
California (CCPA/CPRA)
We do not sell or share personal information for cross-context behavioral advertising.
California residents have the right to know what personal information we collect, to request deletion, to correct inaccurate information, and to non-discrimination for exercising these rights. You can exercise these rights by contacting us at qrloyaltycard@gmail.com.
8. Children
The service is not directed to children under 13. Business administrators must be at least 18 years old.
In Slovakia, the age for valid digital consent is 16 years under GDPR Art. 8. Users aged 13 to 16 may use customer features only with parental consent where required by law.
9. Security
We apply industry-standard security measures including encrypted connections and access
controls.
10. Permissions used by the app
- Camera – QR code scanning.
- NFC – reading NFC tags.
- Location – used only when recording a visit, to verify that the customer is
near the business or organization location. QR Loyalty Card does not use background
location
tracking.
- Internet – backend communication.
- Notifications – optional push messages.
11. Data deletion
Business/admin accounts: request deletion in the app under Settings > Deactivate account, or via our Delete Account page, or by email at
qrloyaltycard@gmail.com.
Self-service deactivation: data is permanently deleted within 48 hours. Email requests: we acknowledge within 72 hours and complete deletion within 7 business days, unless longer retention is required by law.
Customers do not have accounts. Uninstalling the app removes locally stored data.
Pseudonymous loyalty records on our servers are automatically deleted after
90 days without a visit (see Section 6).
Customers may request deletion of their pseudonymous loyalty record by contacting us at
qrloyaltycard@gmail.com.
If a customer requests deletion, we will also delete or anonymize related pseudonymous loyalty
and location verification records where technically possible and legally required.
12. Changes
We may update this policy and will revise the “Last updated” date. We will inform you of material changes in the app or by email before they take effect. Continued use after changes constitutes acceptance.
13. Contact
Madala Apps
Luky 30, 020 53 Luky, Slovakia (SK)
qrloyaltycard@gmail.com
https://qrloyaltycard.com/
Terms of Service · Delete Account
This application does not display third-party advertising.
Monetization is based solely on optional subscriptions via Google Play.