A few signals.
A clear explanation.

Why we use analytics

Limited usage analytics helps us understand whether the app is being used and which external merchant and credit card links people find useful. It is separate from your personal rewards calculations and does not determine which card ranks highest.

Points Points! is always free to use. The core recommendations work with analytics turned off.

The three activities we measure

• App foreground activity. The app launches into the foreground or returns from the background.
• External merchant-link taps. You deliberately tap an external merchant link. The event includes a public merchant identifier.
• Official card-link taps. You deliberately tap an official card product or application link. The event includes public issuer and card-product identifiers.

A card-link tap does not say that you own that card. A link tap does not tell us whether you bought something or submitted an application. Custom event details also include a schema version.

Identifiers & connection information

When analytics is enabled and configured, the app uses PostHog US Cloud. Alongside the permitted events, the service can receive event timestamps, a random installation identifier, a session identifier, and limited app/device metadata such as app and SDK versions, operating-system version, device model or type, and distribution or simulator indicators.

The random installation identifier can associate permitted events from the same installation. These events do not contain your name, but they are pseudonymous rather than fully anonymous.

Network requests also expose an IP address to PostHog and network infrastructure. Geographic enrichment is disabled; this does not mean network providers cannot see an IP address.

What these analytics exclude

• Your wallet contents and owned-card selections.
• Loyalty balances, goals, benefit usage, and personal point valuations.
• Financial calculations and reward-comparison inputs.
• Location, searches, assistant questions, and notification activity.
• Raw outbound URLs, bank credentials, and payment credentials.

The integration does not use advertising identifiers, session replay, screen recordings, automatic screen or interaction capture, person profiles, or identity merging. These limits describe the analytics integration; optional functional services such as Apple maps have separate data handling.

How to turn analytics off

Turn off Share limited usage analytics on the first setup page, or open Wallet → Privacy & Data in the app and change the same setting.

For the US-launch configuration, analytics is on by default for new installations without an existing choice. Saved opt-outs are preserved. Older analytics preferences do not automatically authorize the broader current event set.

Turning analytics off stops new analytics transmission and clears pending local analytics captures. It does not delete events already delivered to PostHog or necessarily replace the SDK’s random installation identifier. Core reward recommendations still work. Location permissions and notification settings are controlled separately.

Deleting your local profile also disables analytics. It does not delete information already held by third-party services.

The website is separate

This website does not include PostHog or other tracking analytics.

GitHub Pages, when used to host the site, logs visitor IP addresses for security. Read the website privacy details for the hosting disclosure and its source.

Retention & deletion

Turning analytics off stops new transmission; it does not delete events already delivered to PostHog. Deleting your local profile also does not delete information already held by third-party services.

Read the full privacy policy for the app’s local profile, optional permissions, Apple services, extensions, and analytics controls. You can also read PostHog’s privacy information.