# CardCompass > Machine-readable product and source guide. Public claims here are limited to behavior visible in the current product and landing implementation. ## Product - Name: CardCompass - Website: https://cardcompass.in/ - Market: India - Category: credit-card reward decision support - Status: early access / waitlist - Support and data requests: support@cardcompass.in CardCompass is being built for people managing several Indian credit cards. It aims to present a card choice with estimated value, caps, milestone context, caveats, source and verification date. Recommendations are informational estimates, not financial advice or issuer guarantees. ## Public pages - Product and waitlist: https://cardcompass.in/ - Privacy: https://cardcompass.in/privacy/ - Terms: https://cardcompass.in/terms/ - Data and security: https://cardcompass.in/data-security/ - Recommendation disclaimer: https://cardcompass.in/recommendation-disclaimer/ - Best-card purchase calculator: https://cardcompass.in/tools/best-card/ - Milestone tracker calculator: https://cardcompass.in/tools/milestone-tracker/ - Movie-offer savings calculator: https://cardcompass.in/tools/movie-offers/ ## Current product flows ### Card and statement organisation Signed-in users can associate cards from the CardCompass catalog with their account. Current UI flows use catalog identity, last four digits, optional holder/limit fields, and statement/due dates; they do not ask for or send a full primary account number (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 it 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; this is not a claim of immediate physical erasure from every retained copy. Broad acquisition is gated on verifying that deployment. ### Gmail read-only statement import Google OAuth requests Gmail read-only access (`gmail.readonly`) and birthday read access (`user.birthday.read`) in addition to profile scopes. The app searches for statement-like emails with PDF attachments. For each matching statement, its current Gmail `messages.get` request uses the default full format, retrieving the full parsed message into app memory. Application logic uses headers and attachment identifiers and does not intentionally persist the message body. It downloads the matching statement PDF for processing. Read-only access does not authorise sending, editing or deleting Gmail messages. The app attempts to store the date of birth in the Supabase profile; if that row/update is unavailable, the date may remain in memory and may be requested again. ### PDF extraction and password handling PDF text is extracted in the running app. A password-protected statement can use date-of-birth/card-pattern candidates or a statement PDF password entered by the user. Successful statement PDF passwords and learned patterns are cached locally in app/browser preferences by the current code. The original PDF is not uploaded through the current statement repository path. ### Gemini processing Extracted and pruned statement text is sent through an authenticated Supabase edge-function proxy to the Google Gemini Generative Language API. Gemini returns structured statement and transaction data. This AI processing is not solely local or on-device. ### Supabase persistence Supabase provides authentication, database storage, waitlist RPCs and the Gemini proxy. It stores account/profile, Gmail processing metadata, card, transaction and statement records for product users. It separately stores waitlist email, application answers, consent timestamps and attribution fields for early-access operations. ### Analytics The public landing page uses Plausible. CardCompass strips query parameters and URL fragments before analytics transport, blanks referrer data and allow-lists non-sensitive event context. Waitlist attribution is handled separately and submitted to Supabase when the visitor joins. ## Calculator limits The public calculators use arithmetic based on visitor inputs. They do not query issuers or confirm merchant category, eligibility, benefit inventory, posting, cap state or reward fulfilment. Official issuer and merchant terms remain authoritative. ## API CardCompass does not currently offer a public developer API. --- Last reviewed: 2026-08-15