📍 PerkMap
PerkMap Privacy Policy
What the PerkMap app collects, how it's used, and the control you have over it.
Last updated: November 17, 2026
PerkMap (“the app”) is built and operated by AiGenix, 101 IFZA Dubai, Silicon Oasis, Dubai, UAE. PerkMap shows you the discounts your bank card unlocks, on a map. This policy describes exactly what data the PerkMap app collects and how it is used. For AiGenix’s other products and website, see the general AiGenix Privacy Policy.
Data we collect
- Account details — email address and name. Provided by you at sign-up; used to create and secure your account and to send account emails (verification, password reset).
- Optional profile details. You can provide gender and a coarse age group for grouped audience analytics, or choose “Prefer not to say”. We do not request an exact date of birth. Eligible completion and reward records are associated with your account.
- Profile photo (optional). If you choose to add one, it is stored with your profile.
- Deal poster photos and correction evidence (optional). If you choose poster text extraction, the image is sent securely to our vision-processing provider. Scan-only images are not saved after processing. If you attach an image to a submitted offer or correction in supported app versions, a sanitised copy is stored privately for authorised review and audit for up to one year. It is not a public photo feed. Account-erasure processing removes your private submission evidence.
- Content you share. Offer submissions and corrections await administrator review; submitted evidence is private to authorised reviewers. Published offer information and published community/forum content can be visible to other users. Review decisions and notes are stored so you can follow your submission.
- Guest browsing and device context. Read-only guest access expires after 24 hours. We remember a random installation ID and a server-hashed app-scoped device identifier to recognise repeat guest access. Device model/manufacturer, operating-system version, app version/build, locale and timezone help us understand app behaviour. We do not use an advertising ID, IMEI, hardware serial, contacts or a personal device name for this purpose. Optional browsing searches and action history are retained for up to 90 days and can be turned off from the guest banner. A verified sign-in links the installation/guest journey to that account; it does not prove that every account on a shared device is the same person. Account creation dates come from our authentication records. Optional diagnostics choices in Settings continue to apply to signed-in browsing analytics. Inactive installation records are removed after 90 days; guest expiry is not renewed by analytics preferences.
- Invitations and rewards. Referral-link opens, attributed signups, qualification decisions, points, lifetime tiers and voucher claims are recorded to provide and audit the program. Verified email or phone ownership, where provided, is checked for uniqueness; hashed contact references help prevent duplicate rewards. No payment-card number or security code is requested.
- Activity in the app. Deals you save or claim, and the points and tier you earn, are stored with your account.
- Coarse location activity (optional). If you explicitly enable this in Settings, PerkMap uses foreground location while the app is open to create an approximately 1 km grid cell for registered-user audience activity analytics. Exact coordinates are not stored. Merchant heatmaps show only broad “activity detected” for areas with one or two users; a finer cell and user count are shown only when at least three distinct users contribute.
- Explore assistant requests. When you ask Explore for help or nearby recommendations, your message, recent conversation context, saved card-product labels and the location you choose are processed by our server and OpenAI, or Groq when the configured fallback is used. These are card-product descriptions, not payment-card numbers. OpenAI response storage is disabled; each provider's security and retention controls still apply. Exact assistant-request coordinates are not stored as an activity trail.
- Service chat history (disclosed in supported app versions). Updated clients show a chat-history notice before sending under the new service-chat contract. Submitted assistant messages and answers are kept in your PerkMap account for up to 90 days, separately from optional diagnostics. Authorised admins may review retained conversations through restricted, audited tools. Turning diagnostics off does not remove these service chats. There is no individual conversation-delete control. Earlier feedback-linked conversations remain under their original setting and are not silently converted to the new retention purpose.
- Optional app diagnostics (on by default; you can opt out). Unless you turn this off in Settings, we retain submitted-search diagnostics, selected city, named screen/action timelines, outcomes, timings, app/update versions and feedback for up to 90 days. Existing off choices are respected. The app displays a one-time notice and a Settings toggle. Turning diagnostics off stops collection and removes that optional data. Earlier feedback-linked chats retain their original opt-out semantics. We redact common sensitive patterns and do not intentionally capture passwords, authentication tokens, payment-card numbers, exact GPS trails or raw form keystrokes in interaction events. This setting is separate from service chat history, coarse-location analytics and push alerts.
- Push notification data (optional). If you enable push notifications, we store an Expo device token, platform, app version, locale/timezone, your alert preferences, and queued/sent/delivered/open/failure events. This is used only to deliver and troubleshoot the alerts you request.
- Firebase Analytics and Crashlytics. Subject to your app diagnostics choice, Google Firebase receives named screens, aggregate interaction events (including merchant-action intent and outcomes), an opaque account or installation identifier, app/device versions, and reliability reports. Submitted search text, chat content, email addresses, phone numbers and raw location are not included in our Firebase event parameters. Advertising identifiers and personalized advertising are disabled. Firebase reporting has its own provider/project retention settings; the PerkMap activity-log retention periods above apply to our own records. Turning diagnostics off stops our Firebase reporting and clears pending unsent Crashlytics reports. Native crash reports may include SDK-generated technical stack and device information.
- Crash diagnostics. When the app fails, it may send the error message, stack trace, app/update version, platform, time, and your user ID when signed in. This is used to diagnose reliability problems and is retained for up to 30 days.
Location controls and data we do NOT collect
- Exact location is not stored as an activity history. Device location used to centre the catalogue map stays on your device. If you enable Share coarse app activity, the server immediately converts a foreground observation to a coarse grid cell used for privacy-tiered analytics and, when enabled, nearby-deal alerts. Separately, an exact or typed location is transmitted only when you choose it for an Explore assistant request; it is processed to answer that request and is not added to the activity-history table.
- No advertising or sale of data. PerkMap contains no ads or third-party advertising trackers, and we never sell your data. Optional first-party feedback is used to improve PerkMap, not to create advertising profiles.
How your data is used
Solely to provide and secure the app’s features: your account, guest access, invitations, optional profile details, reviewed submissions, saved offers, claims and points, requested assistant answers and their disclosed history, notifications, reliability diagnostics, the community, optional app feedback, and (only when opted in) privacy-tiered registered-user audience activity analytics. Physical footfall is measured separately through merchant-confirmed QR redemptions. We do not use your data for marketing profiles or share it with advertisers.
Service providers
Your data is processed by providers that run requested PerkMap features: Supabase (database and authentication), Amazon Web Services and Render (application hosting), Resend (account email), Mapbox (map display), Expo (app updates and push delivery), OpenAI (Explore answers and deal-poster text extraction), and Groq (the configured Explore fallback). PerkMap requests that OpenAI responses are not stored for later assistant use. Provider security and retention controls still apply.
Security
All data is encrypted in transit (HTTPS/TLS), and database access is restricted server-side so app users can only access their own private history. Authorised admins may review retained service chats and enabled optional feedback through restricted, audited tools; ordinary merchant accounts cannot access these conversations.
Retention and deletion
Coarse location observations and crash diagnostics are automatically deleted after 30 days. Optional diagnostics and disclosed service chat history expire after 90 days and are purged by the configured retention job. Disabling diagnostics deletes optional interaction records and earlier feedback-linked chats; it does not delete new service chat history. Access-audit metadata may be retained for up to one year using its original access clock. Turning off Share coarse app activity immediately deletes all of your stored location observations. Disabling push revokes that installation’s token; signing out also requests token revocation. Guest sessions and events and unattached referral visits expire after up to 90 days. Attached offer/correction evidence is retained privately for up to one year for review and audit. Other account data is generally kept while your account is active. In supported versions, Profile → Settings → Delete account submits an account-erasure request for administrator review. After approval, the configured cleanup removes the login, profile, avatar, private chats, optional location records and private submission evidence. Required business, redemption, points, anti-abuse and access-audit records may be retained in a restricted or pseudonymised form for up to one year; a deletion request does not erase those records immediately. You can also request deletion by emailing contact@aigenix.ai.
Children
PerkMap is intended for users aged 18 and over. We do not knowingly collect personal data from children under 13; if you believe a child has provided us data, contact us and we will remove it.
Changes to this policy
If this policy changes, the new version will be posted at this address with an updated date above.