Legal / plain language

Privacy notice

This notice describes the current CardCompass landing page and application data flows. It separates waitlist processing from the signed-in product because they collect different information.

Effective and last updated: 15 August 2026

On this page

The short version: the waitlist stores the details you submit. The signed-in product can use read-only Gmail access to find statement PDFs, extracts their text in the app, sends relevant statement text through our Supabase function to Google Gemini, and stores structured account, card, statement and transaction records in Supabase.

Who handles the data

CardCompass is responsible for the product and this website. Questions, access requests, corrections and deletion requests can be sent to support@cardcompass.in. We may need to verify that a request relates to you before acting on it.

Waitlist and early access

When you join, we store your email address and the time you accepted this notice. If you finish the optional qualification step, we can also store your name, card-count range, monthly-spend range, primary goal, free-text problem detail and up to two card names. We also store first-touch attribution when present: acquisition source, landing variant, UTM values and the referring path.

We use this information to administer the waitlist, rank and invite suitable early users, understand acquisition channels and contact you about your application. Product marketing is a separate optional checkbox. The public form records only a pending marketing request; it does not set verified marketing consent, and no marketing mail may be sent until email ownership is verified and an unsubscribe workflow is operational. Leaving it unchecked does not stop operational messages about your waitlist application or invitation.

Signed-in account and profile

Google sign-in and Supabase Auth provide account identifiers and basic profile information such as email and name. The current OAuth request includes gmail.readonly and user.birthday.read in addition to email and profile scopes. Date of birth can be fetched from Google or entered by you. The app attempts to store the date of birth in the Supabase user profile so the product can generate common bank statement PDF password patterns. If the profile row or update is unavailable, the date may remain in memory in the app and could be requested again.

Gmail statement access

The product uses Gmail read-only access to search for messages with PDF attachments and statement-like subject lines. For each matching result, the current Gmail messages.get request uses Google's default full format, so the full parsed message is retrieved into app memory. Application logic uses message headers and the MIME-part tree to find attachment identifiers and filenames; it does not intentionally persist the message body. It stores Gmail message ID, subject, sender, received date, attachment ID and attachment filename in Supabase for deduplication, card assignment and status tracking.

The app downloads a matching PDF attachment to process it. The gmail.readonly scope does not give CardCompass permission to send, edit or delete your Gmail messages. The current pipeline does not upload the original PDF file to Supabase; it extracts text in the running app and stores the resulting structured records.

PDF passwords and extracted text

If a statement PDF is locked, CardCompass can try common patterns using your name, email, date of birth and last four card digits. It may ask for your statement PDF password. A password that successfully opens a statement is cached locally in browser or app preferences for later statements from that bank. It is not deliberately sent to Supabase or Gemini by the current flow. Local preferences are not represented as hardware-backed secure storage; clearing the app or site data may remove them.

The current UI does not request or send a full card number (primary account number or PAN), card expiry, CVV, PIN, OTP or banking password. This repository includes a hardening migration for logical active-schema removal of legacy PAN/expiry columns and older RPC signatures. Until that migration is applied and verified in the deployed Supabase project, the live backend may still retain those legacy columns or RPCs. Provider backups and write-ahead logs (WAL) follow provider retention and restore policies; dropping a column is not a claim of immediate physical erasure from every retained copy. Never enter a banking login password, OTP, CVV, PIN or full PAN into CardCompass.

Google Gemini processing

After PDF text extraction, the product prunes and sends statement text in authenticated requests to a CardCompass Supabase edge function. That function proxies the request to the Google Gemini Generative Language API. The text can include statement dates, balances, last four card digits, merchant descriptions, transaction dates and amounts. Gemini returns structured statement and transaction information. This processing is not solely on-device.

Google and Supabase process data on our behalf or under their applicable service terms. Network, security and operational logs may exist at those providers. CardCompass does not make a promise here about a third party's independent retention beyond the controls actually configured.

What Supabase persists

Area Examples Purpose
Account/profile User ID, email/profile fields, date of birth Sign-in and statement password pattern generation
Cards Current UI fields: catalog card, last four digits, holder name, credit limit and statement/due day; deployment-gated legacy caveat described above Represent your wallet and match statements; PAN/expiry hardening must be verified in the deployed backend
Statements Statement and due dates, balances, payment and rewards fields Track bills, spend and milestones
Transactions Amount, date, merchant, description, category, card and statement link Spend analysis and recommendation inputs
Email processing Message IDs, subject/sender, dates, attachment metadata, status Find, deduplicate and process statements
Waitlist Email, application answers, consent timestamps, attribution Early-access operations and measurement

Website analytics

The landing page uses Plausible for pageviews and a small allow-list of funnel events. Before transport, CardCompass strips query parameters and fragments from the page URL, removes referrer data, and permits only non-sensitive properties such as placement, step, variant and outcome. The analytics payload is designed not to include your email, name, cards, spend band or free-text answer. The landing analytics setup is cookie-free; first-touch waitlist attribution is stored separately in local storage and submitted to Supabase only when you join.

When data is disclosed

Data is shared with service providers needed to run the product, including Supabase for authentication, database and edge-function processing; Google for OAuth, Gmail, Gemini and hosted font files; jsDelivr for the exact-pinned Supabase browser library; and Plausible for limited website analytics sent through CardCompass's local audited transport. We may also disclose information when legally required or to protect users and the service. We do not describe submitted personal data as being sold.

Retention and deletion

We keep data while it is needed to provide the service, administer early access, resolve disputes, protect the service and meet legal obligations. The current product does not expose a self-service account deletion control. Email support@cardcompass.in to request deletion of waitlist or product data. We will verify and act on valid requests, subject to data we must retain for security, legal or dispute purposes. Local PDF-password preferences must be cleared through your browser or app data controls.

Your choices

  • Do not join the waitlist if you do not want the submitted details stored.
  • Leave optional marketing consent unchecked, or use an unsubscribe route in marketing mail.
  • Revoke CardCompass Google access in your Google account; this stops future Gmail/People API access but does not automatically delete records already stored.
  • Ask for access, correction or deletion at the support address.

Changes to this notice

We may update this notice as the product changes. The effective date at the top identifies the version. Material changes should be presented through an appropriate product or email notice where practical.