RewardSensei

Privacy policy

Last updated: October 7, 2026

1. Who we are

RewardSensei ("we," "us," or "our") is a credit card benefits and rewards optimization tool operated by an independent developer. We may incorporate as a separate legal entity in the future; if we do, this policy will be updated accordingly.

2. Information we collect

When you use RewardSensei, we may collect or process the following types of information:

  • Waitlist information: the email address you submit, the time and version of your consent, and limited campaign attribution included in the page URL. If the security check does not finish, we keep the submission in a private pending state for up to 30 days so you can confirm the address or we can review the failed signup. A minimal suppression record may be retained after a bounce, complaint, or provider suppression so we do not send more verification email to that address. A separate provider-message routing record may include the address for up to 90 days so delayed delivery or bounce reports can be applied correctly.
  • Account and profile information: your email address, account settings, household membership and sharing choices, and saved trip details such as destinations and dates.
  • Card metadata: the credit cards you add to your wallet (card name, last four digits, issuing bank). We never store full card numbers, CVVs, or bank login credentials.
  • Offer and benefit data: credit card offers, benefit usage, and reward point balances synced from bank websites via our browser extension.
  • Spending data: raw individual transaction descriptions stay in extension storage. When you use account sync, the extension may derive and sync monthly category totals, transaction counts, the month, and the relevant card or account last four digits. These aggregates support portfolio guidance without syncing raw merchant descriptions.
  • Ask Sensei questions and context: when you use Ask Sensei, the question you type and the relevant RewardSensei context needed to answer it are sent to the AI provider configured for the service. Depending on your question, that context can include card names and last four digits, credit limits and current balances, reward rates, benefits and usage, offers, spending-category totals, loyalty balances, point-value settings, household member labels and information they chose to share, and saved-trip destinations and dates. Do not put bank passwords, MFA codes, or full card numbers in an Ask Sensei question.
  • Usage analytics: explicit app interactions and limited technical context collected through PostHog. Signed-in web and mobile events use an app-scoped pseudonymous identifier; extension events remain anonymous. Automatic page views, autocapture, performance capture, and exception capture are disabled. Sampled session replay may be enabled for up to 15% of sessions; text, form inputs, and element attributes are masked, and request headers and bodies are not recorded. We do not add emails, names, card numbers, bank credentials, or free-form financial text to PostHog events. Mobile analytics may record a first app open and controlled source, medium, campaign, and content labels from an incoming RewardSensei app link to measure acquisition and product activation. Only explicitly allowlisted labels are sent; an unknown value is reported as "other". The app does not send the raw link, advertising click identifier, or user-supplied campaign text. Ordinary website and App Store or Google Play links do not transfer store-install attribution into the app; Apple and Google provide that attribution in their own consoles.
  • Diagnostic data: crash, error, and limited performance details sent to Sentry after sensitive properties are removed. Reports may include app, device, operating-system, and runtime context plus an app-scoped pseudonymous account identifier. Default personal-information collection and session replay are disabled. Sentry may also process technical connection data, such as an IP address, when it receives a report even though RewardSensei does not deliberately add an IP address to the report.
  • Purchase and subscription data: RevenueCat processes an app account identifier, product and transaction identifiers, purchase and renewal history, subscription status, entitlements, refunds, and restore status. Apple or Google processes native purchases, and eligible web checkout may use Stripe. RewardSensei does not receive or store your full payment card details.
  • Advertising conversion data: if server-side Meta measurement is enabled, RewardSensei may report when this browser completes a web account registration that it initiated, starts a supported web Pro checkout, or completes an eligible paid web Pro purchase. A bounded browser-local marker containing the RewardSensei account identifier and creation time may be kept for a maximum of 30 days so a failed web-registration conversion capture can be retried; it is removed after the server accepts the capture. An account created in a native app is not reported as a registration merely because it later signs in on the web. The report may include the event type and time; product, amount, currency, and web-purchase platform when applicable; a one-way hash of the normalized account email address; a one-way hash of a stable RewardSensei account identifier; a pseudonymous event identifier; an optional Meta click identifier derived from an incoming fbclid; the IP address and user agent observed by our server for the registration or checkout request; and the applicable RewardSensei source page URL without its query string or fragment. For an eligible paid web purchase, the most recent unused matching checkout context from the preceding 30 days may be copied to the purchase conversion. No Meta script runs in your browser, including a Meta browser Pixel; we do not set or send a Meta browser cookie or fbp, and we do not report native-app purchases, sign-ins, page views, or automatically captured browsing activity. RewardSensei does not send Meta card, bank, offer, household, trip, location, or free-form Advisor data.
  • Push-notification identifiers: if you enable mobile notifications, RewardSensei associates your account and platform with an Expo push token. Expo and the Apple or Google notification service process that app-installation or device delivery identifier to route notifications.
  • Location data: if you enable mobile location recommendations, the app can receive approximate or precise device location in the background, including when the app is closed or not in use. It uses that location on the device to identify nearby airports and rank nearby places. For merchant lookup, it rounds the coordinates before sending them to the OpenStreetMap Overpass service. RewardSensei does not save location coordinates in your account database.
  • Support communications: messages and verification information you provide when you contact support, including an account-deletion request.

3. How we use your information

  • To verify a pending waitlist request, confirm waitlist registration, and send the product or launch updates you requested. At signup, you can optionally request product updates, getting-started guides, and rewards tips by email. This choice is unchecked by default and is not required to use RewardSensei.
  • To provide and personalize the RewardSensei service (benefit tracking, card recommendations, offer syncing).
  • To answer questions you submit to Ask Sensei using the relevant account context described above.
  • To send notifications that you enable, such as benefit, trip, annual-fee, statement, or location reminders.
  • To process purchases, restore access, and keep subscription entitlements current.
  • To improve the product and fix bugs using privacy-safe analytics.
  • To measure whether advertising leads to browser-confirmed web registration, supported web Pro checkout, or an eligible paid web Pro purchase.
  • To respond to support, privacy, and account-deletion requests.

4. Browser extension

The RewardSensei Chrome extension accesses bank websites using your existing browser sessions. This means:

  • RewardSensei does not ask for or store your bank username, password, or MFA code.
  • The extension reads offer, benefit, and reward data only while you are actively logged in to your bank's website.
  • You can use the extension in local-only mode without creating an account. In this mode, bank-derived data stays in your browser's local storage and is not synced to RewardSensei's cloud database. Anonymous product analytics and sanitized diagnostics may still be sent to PostHog and Sentry as described in this policy.
  • If you create an account, supported offer, benefit, loyalty, and derived monthly spending-category data may sync to our cloud database. Raw transaction descriptions stay in extension storage.

5. Third-party services

We use the following third-party services:

  • Supabase: database hosting, authentication, and serverless functions (data stored in the US).
  • RevenueCat: app account identifiers, product and transaction identifiers, purchase history, subscription status, entitlements, refunds, and restore status across supported purchase platforms.
  • Stripe: payment processing beneath eligible web checkout flows.
  • Apple and Google: native-app distribution, store purchase processing and purchase history, and device notification delivery.
  • Configured AI provider: Ask Sensei questions and the relevant card, rewards, financial, household, and trip context described above, only when you use Ask Sensei.
  • Resend: delivery of account confirmation, password recovery, waitlist verification and confirmation, and other transactional email, including delivery and bounce events.
  • Zoho Campaigns: storage and delivery of waitlist and launch communications after a waitlist registration is confirmed. A pending address is not added to the launch mailing list until it passes the security check or the address owner confirms it. Signup marketing opt-ins are added only after the account email is verified. We record your choice, its wording version, signup source, and time; changing your email does not subscribe the replacement address.
  • Cloudflare Turnstile: abuse prevention for the public waitlist. Cloudflare processes the challenge token and technical connection or browser signals needed to classify and verify the request.
  • PostHog: explicit product interactions using app-scoped pseudonymous identifiers and sanitized event properties.
  • Sentry: crash, error, and limited performance monitoring using pseudonymous account identifiers, sanitized diagnostic data, and technical connection data that may be processed when a report is received.
  • Meta: optional server-side measurement of browser-confirmed web registration, supported web Pro checkout, and eligible paid web Pro purchases using the limited conversion data described above. Native-store purchases are not included, and no Meta Pixel or other Meta code runs in your browser.
  • Expo: mobile push-token registration and notification delivery.
  • OpenStreetMap Overpass: nearby-place lookup using rounded coordinates when you enable mobile location recommendations.

We do not sell or rent your personal data. If Meta measurement is enabled, only the limited browser-confirmed web registration, checkout, and eligible paid-purchase conversion data described above is shared for advertising measurement; card, bank, offer, household, trip, location, and automatically captured browsing data are not.

6. Affiliate links

RewardSensei may include affiliate or referral links to credit card application pages. If you apply for a card through one of these links, we may receive compensation from the card issuer. Affiliate availability does not change recommendation order. Recommendations use the relevant card, reward-rate, offer, fee, point-value, spending, and benefit inputs; a compensated action is disclosed near the link when it is available.

7. Data security

We use access controls, authenticated sessions, database row-level security policies, telemetry sanitization, and security controls provided by our infrastructure and payment processors. Access to account data is restricted by user and household permissions. No electronic transmission or storage method is completely secure, and we cannot guarantee absolute security.

8. Data retention

We retain account data while your account is active and as needed to provide the Service. An unconfirmed waitlist submission is kept for up to 30 days, then deleted. Unverified signup marketing choices are also deleted after 30 days. When you delete your account or change its email, we queue suppression of the old address in Zoho; a minimal delivery record is retained until suppression succeeds. Confirmed signup and waitlist consent history are retained as needed to send the requested product and launch communications, honor unsubscribe requests, and meet limited security or compliance needs. A minimal address-level suppression record may be retained as long as needed to honor a complaint, bounce, or provider block and prevent additional waitlist email, including by reconciling that address with the Zoho Campaigns Do-Not-Mail registry. Provider-message and token-digest routing records may retain the submitted address for up to 90 days to reconcile delayed email-provider events without retaining the confirmation link token itself. When account deletion succeeds, it deletes your RewardSensei sign-in, active cloud account, and account-linked rows through the deletion workflow. Limited security, fraud-prevention, financial-reconciliation, and backup records may remain where needed, and identifiers in retained billing-webhook records are removed. This does not cancel external billing or delete records independently controlled by Apple, Google, RevenueCat, Stripe, PostHog, Sentry, Meta, Expo, the configured AI provider, your browser, or our email provider. Those services may retain purchase, transaction, telemetry, diagnostic, request, delivery, or support records under their own legal and operational policies. RewardSensei stores advertising-conversion delivery records, including any limited click, IP-address, user-agent, and source-page matching context described above, in a private service-only delivery queue. Rows containing that matching context become eligible for bounded deletion no later than 30 days after creation, including rows awaiting delivery or left behind by a stale processing lease; an actively leased row is protected until the short lease becomes stale. The browser-local registration retry marker also expires after 30 days. Account deletion removes account-linked conversion-delivery rows from the active database. You can clear local extension data in extension settings or remove it by uninstalling the extension, subject to your browser's storage behavior. See the public account-deletion instructions for the in-app steps, email-request fallback, and deletion details.

9. Your choices and rights

Depending on where you live, privacy law may give you rights over your personal data. You can use RewardSensei controls or contact us to:

  • Ask for access to the personal data we hold about you.
  • Request correction of inaccurate data.
  • Request deletion of your account and RewardSensei data, subject to the limited retention described above.
  • Export your account data in a portable format.
  • Manage notification and location permissions in RewardSensei or device settings.
  • Unsubscribe from marketing, waitlist, or launch emails using the link in those messages.
  • Ask about available choices for non-essential communications and analytics.

To exercise any of these rights, visit RewardSensei support or contact us at rewardsensei@myhappy.family.

10. Children's privacy

RewardSensei is not intended for use by anyone under the age of 18. We do not knowingly collect personal information from children.

11. Changes to this policy

We may update this privacy policy from time to time. We will notify you of material changes via email or in-app notification. The "Last updated" date at the top reflects the most recent revision.

12. Contact us

If you have questions about this privacy policy, please contact us at rewardsensei@myhappy.family.