Radar, Signals, and optional AI

Radar uses your location to show nearby restaurants. If you opt into automatic mobile reminders, it can use location in the background to monitor nearby geofences. Your GPS coordinates and visit history are not uploaded to Perky or the AI provider. Saved restaurants, enrollment confirmations, monitored places and proximity-alert history are stored on your device. Product analytics counts alert outcomes without venue names, coordinates or visit histories; see Analytics below. Area-directory requests reveal the area you select to our hosting provider. Radar alert-frequency preferences and a limited diagnostic log are also stored on your phone. Diagnostics record registration, permission, background-task and notification outcomes without GPS coordinates, account identifiers or wallet balances. They are not automatically uploaded; you may choose to share a diagnostic report for support. You can turn reminders off or revoke location access in device settings.

Signals offers and aggregate response counts appear publicly with a pseudonymous contributor ID. We retain account-linked submissions, confirmations, abuse reports and blocks to operate and moderate the community. For optional Premium offer alerts, we store an installation ID, push token, time zone and card types in your wallet; Firebase Cloud Messaging delivers the alerts. Turning alerts off removes that device's subscription. Deleting your account removes your authored offers, participation and related private records.

Optional Premium AI sends your typed restaurant question and selected area, or pasted offer text, to Google Gemini along with public restaurant facts when relevant. It does not send your wallet or GPS location. Do not include account numbers or personal details. We store request identifiers, a hashed input fingerprint and usage counts for quotas and abuse prevention, not the full request text or draft result. AI-generated restaurant candidates do not become proximity alerts without review.

Map providers

Radar maps use Apple Maps on iOS, Google Maps on Android, and OpenStreetMap tiles on the web. Loading a map sends requests to the relevant provider, which may receive your IP address and the map area requested under its privacy policy. Perky does not include your wallet balances or visit history in those map requests. Location and visit details are not included in Perky's product analytics.

What We Collect

Card types you track

e.g., "Amex Platinum" - to improve our card database

Perk usage patterns

Manual check-offs and remaining amounts you enter; synced only when account sync is enabled

Email (when you create an account)

Used for sign-in, Premium access and verified community contributions. Authentication is handled by Firebase.

Loyalty program balances

Point/mile balances you manually enter for tracking purposes

Push notification tokens (mobile)

Device tokens for opted-in reminders and Signal offer alerts

What We DON'T Collect

Credit card numbers

We never see your full card numbers - only the optional last 4 digits you choose to add for your own reference

Financial data

No transaction data, balances, or account info

Government identity documents

We do not ask for ID scans or identity verification for Radar or Signals

Bank connections

We never connect to your bank or financial institutions

Data Storage

Your card and loyalty program tracking starts on your device. If you enable account sync, card, perk and loyalty data can also be stored in Firebase so it is available across devices. Radar's background-location matching stays on your device; Signal contributions and optional alert subscriptions use our servers as described above.

If you create an account, the following may be stored securely in Google Firebase (Firestore):

Your email and authentication credentials (via Firebase Authentication - passwords are never stored directly)
Premium subscription status and billing identifiers
Card and perk usage data (for cross-device sync)
Loyalty program balances (for cross-device sync)
App preferences such as theme and notification settings

Account Information

When you create an account, we collect your email (via Firebase Authentication) to:

Create and manage your account
Process payments and manage your subscription
Allow you to restore premium status on other devices
Sync your data across web and mobile
Send important account and billing notifications

Product-update emails are optional and off until you opt in. You can change this preference in Settings or on our email-preferences page, or unsubscribe using the link in a product-update email. This preference is separate from perk reminders and important account or billing notifications.

Payments & Purchases

Premium subscriptions are processed by:

Stripe for web payments - we never see or store your full payment details
Apple App Store for iOS in-app purchases, managed via RevenueCat
Google Play Store for Android in-app purchases, managed via RevenueCat

RevenueCat is a third-party service that manages mobile subscription receipts and entitlements. They receive your Perky account ID (or an anonymous app ID before you sign in) and purchase receipts to validate your subscription. They do not receive your email address from Perky. See RevenueCat's Privacy Policy for details.

Push Notifications

On mobile, you can opt in to perk reminders and Premium Signal offer alerts. Firebase Cloud Messaging delivers server-sent notifications; Radar nearby alerts are generated on the device when a monitored geofence fires. You can change these settings in Perky or your device settings. Radar's location permission is separate from notification permission. We do not send marketing push notifications without your consent.

Analytics

We use PostHog to understand how people use Perky. Before sign-in, events use a device or browser identifier; on the web, signing in links analytics to your account ID, not your email address. We track actions such as cards added, perks marked used, pages viewed, whether the Home summary appears, which card credits you confirm as activated, and how you answer Radar's activation question. We do not send your wallet's dollar totals, card nicknames or fee-waiver status in the Home-summary event. We don't sell this data to third parties.

Radar and Signals analytics. To learn whether these features help, we record:

Radar: opening Radar and from where, switching between list and map, how you browsed (area, Near me, search or place type) with a rounded result count, opening a place, saving one, tapping its listing or directions, suggesting a place, turning nearby reminders on or off and whether setup succeeded, and marking a credit used from Radar.
Radar alerts: that an alert was sent, and the reason an arrival check did not alert (such as quiet hours or no unused credit), counted per day. These are recorded on your phone and sent the next time you open Perky.
Signals: opening Signals, offer feeds loading with rounded counts, opening the share form, submitting or editing an offer and whether it went through, your availability or redemption response, reports, blocks, withdrawals, alert and card-follow changes, and opening an offer from an alert.
Server totals: how long community offers take to be confirmed, and how many offer alerts were sent, delayed or failed. These are anonymous counts not linked to any person.
Upgrades: when a Premium screen is shown and which feature showed it, which plan you chose, and whether the purchase completed, was cancelled, failed, or was charged without Premium switching on. We use the last case to find and fix billing problems. Prices, receipts and payment details are handled by Apple, Google, Stripe and RevenueCat, not sent to analytics.

These events include only the place type (Resy, lululemon or Dunkin'), card type (for example "Platinum Card", never your card or its nickname), offer type and outcomes. They never include the place you were near or opened, its name or address, your location or coordinates, the area found by Near me, search text, offer text or merchant, Signal or contributor IDs, or dollar amounts. When you pick a Radar area from the list, we record that area (for example "Chicago"); we do not record an area derived from your location. Perky enforces these limits in code shared by the app, website and server.

What this data is, and is not. Analytics consists of product interaction (usage) data and the identifiers needed to count it: a random device or browser identifier, and your Perky account ID when you are signed in on the web. It does not include your name, email, card numbers, balances or precise location. We use it only to run, fix and improve Perky.

We do not track you. Perky does not link its data with data from other companies' apps or websites, and does not share it with advertisers or data brokers.
Perky does not use your device's advertising identifier (IDFA or Android advertising ID), does not show ads based on your activity, and does not sell or share your personal information as those terms are used in U.S. state privacy laws.
PostHog processes analytics on our behalf as a service provider, on servers in the United States.
To have analytics tied to your device or account deleted, email privacy@theperkyapp.com. Deleting your Perky account also removes your account records from our systems as described below.

Third-Party Services

Perky uses the following third-party services:

Firebase (Google) - Authentication, data storage, push notifications, remote configuration
Stripe - Web payment processing
RevenueCat - Mobile subscription management
PostHog - Privacy-focused analytics
Vercel - Web hosting
Google Gemini - Optional Premium AI assistance when enabled and used
OpenStreetMap and U.S. Census Bureau - Restaurant-location reference data

Each service has its own privacy policy. We encourage you to review them.

Account Deletion

You can request account deletion from Settings or theperkyapp.com/delete-account. This removes your Perky account, synced records and Signal participation from our systems. Local data may remain on a device until you clear it or uninstall the app. App Store and Google Play subscriptions must be managed through those stores; see the deletion flow for details.

Contact

Questions about privacy? Email us at privacy@theperkyapp.com