Security

Your data, your control.

Finstracker never asks for bank credentials, never sells your data, and lets you export your data or delete your account whenever you want.

How we handle your account

Passwords are hashed with bcrypt (12 rounds) before they are stored. The plain password is never logged or stored. Sign-up and password resets are confirmed with a 6-digit code sent to your email; codes are stored only as a hash, expire after 15 minutes and lock after 5 wrong tries.

Signing in gives your browser a session token signed with a server-only secret. It lasts up to 30 days if you keep Stay signed in on, or until you close the tab if you turn it off. Signing out removes it from your browser.

If you used the original Finstracker app, the new dashboard checks your existing email or username and password against your original account, and copies your cards, perks, offers and points history into the new dashboard the first time you sign in. Your original account is not changed.

What we collect

  • Your email address, or the username from your original Finstracker account
  • Your dashboard card layout, visibility and comparison choices, plus an optional greeting name
  • A bcrypt hash of your password, or your Google account ID if you sign in with Google
  • The cards, accounts and recorded balance observations, transactions, budget settings and month-specific targets, manual savings contributions, goals, holdings, perks, offers and trips you add yourself
  • Receipt files you upload, their metadata, line items, notes and transaction links, plus daily upload and scan counts used to apply limits
  • Daily counts of assistant questions and bill script drafts, used to apply the limits
  • If you use bill negotiation: bill details, scripts, call notes, outcomes and agreed rates, saved with your money data
  • If you turn on reminders: your reminder settings, a record of which reminders were sent (kept for about 13 months), and, for text reminders, your mobile number and when you agreed to get texts
  • If you create API tokens: a one-way hash of each token, its name, the last 4 characters and when it was created and last used. The token itself is shown to you once and never stored.
  • For nearby offers, nothing about your location is kept with your account: your position (or the place you type) is sent with the search and not saved with your account. Store results are cached by a rounded area of about 1 km, with no link to who searched.
  • If you upgrade: your Stripe customer ID, plan, renewal date and subscription status. Card details are handled by Stripe and never reach our servers.
  • Page-view analytics, only if you choose Accept all in the cookie banner (see Cookies)

No bank credentials, no email tracking pixels, no advertising or third-party analytics. Reminder emails are sent through Resend and texts through Twilio; they get only the message and the address or number it goes to. Every reminder email has a one-click link to turn them off, and you can reply STOP to any text.

Price watches: your watches and the prices you log are saved with your trips. To show matching deals, the route, city, program and target are compared on our server with our own deal and transfer-bonus feeds. If you enable commercial automatic flight checks, your route, departure date, cabin and program are sent to Seats.aero. These checks remain disabled until commercial permission and credentials are configured. Cached observations are not booking guarantees.

Trip photos: destination covers use attributed public Wikimedia Commons photographs. For other places, our server searches Wikipedia and Wikimedia Commons using the place name, destination and a location rounded to about 1 km when available. We refresh cached public photo metadata after seven days and do not attach your account identity to it. Your browser loads photographs from Wikimedia, which receives your IP address. Trip dates, notes, booking confirmations and financial data are not sent for photo lookup. If a venue photograph is unavailable, a destination photograph is clearly labeled.

Nearby offers: to find stores, our server sends the merchant names from your offers and a position rounded to about 1 km to Photon (komoot), a search service for OpenStreetMap data. The map in your browser loads its images from OpenStreetMap's tile servers, which see your IP address and the map area you view. Neither gets your account details.

Receipts: originals and reviewed details are stored in our MongoDB database and served only through authenticated, account-scoped endpoints. They do not have public file links. JPEG, PNG and PDF files are limited to 3 MB each, 100 files or 100 MB per account. Archive schedules permanent removal after 30 days; you can restore before then. MongoDB cleanup runs asynchronously, so purge timing is approximate. Associated transactions are kept. Account deletion removes receipt files and metadata. Download originals separately before deleting; CSV exports do not contain the files.

Optional receipt scanning: disabled until an administrator configures the feature, provider key and vision model. When available, each scan requires your consent to send the selected JPEG or PNG image to xAI for data extraction. Passwords and session tokens are not sent. Extracted fields are saved as unreviewed, never automatically matched or used to create a transaction. PDFs are entered manually. We do not access your email inbox or retail accounts for receipts.

Optional investment comparisons: disabled until a licensed market-data source is configured. When enabled, security ticker symbols are sent to Financial Modeling Prep to retrieve historical closing prices. Holding quantities, account names, balances and your identity are not sent. Market comparisons use fixed current holdings and exclude dividends and cash flows.

The assistant: when you ask a question, the question and a text summary of your dashboard data, including forecast assumptions and modeled outcomes when financial context is enabled, are sent to our AI provider, xAI, to generate the answer. Your password and session token are never included.

Bill negotiation: when you choose Draft call script, the provider, bill type, monthly amount, optional target, tenure, competitor offers and context in that form are sent to xAI. Your other accounts, balances, password and session token are not sent with the draft. Keep account numbers and other private identifiers out of the form. Scripts, outcomes and call notes sync with your account; outcome notes are not sent to xAI. We don't contact your provider. If xAI is unavailable, we provide a standard script using your bill details.

Other records: issuer offer statuses and point valuations are your own records, saved with your wallet. Card application link history records only which catalog link you opened and when; it does not imply submission or approval. Public contact messages are stored for up to 180 days in an administrator-only inbox. Spending insights are computed from your saved data on your device or our server.

Privacy policy

We don't sell, share, or rent your data. We don't run ads. We don't profile you for any purpose other than running the app you signed up for.

You can delete your account from the menu under your name in the dashboard. That deletes your account and all of your dashboard data from our database right away, and clears it from your browser. Export a CSV first if you want a copy. Data in your original Finstracker account is separate; contact us to have it deleted too.

Plaid (optional bank linking)

Bank linking is implemented for Premium and remains unavailable until the provider is configured. In Accounts → Linked banks, read the data-access notice and agree before opening Plaid Link. Sandbox connections are explicitly labelled test connections.

Data access: the Transactions product supplies account names, balances and transaction history from your chosen institution. This version imports USD accounts and transactions only. It does not request Plaid Identity or Liabilities and does not initiate payments.

Credentials: credentials are entered into Plaid Link, never into Finstracker. Access tokens are stored on our server in AES-256-GCM envelopes, with the encryption key outside the database. Webhook signatures, timestamps and body hashes are verified before events are queued.

Retention and revocation: imported data is retained with your money data while connected. In Accounts → Linked banks, Disconnect calls Plaid's item/remove endpoint and removes the connection, encrypted token and imported accounts and transactions. Manual entries stay. Account deletion first revokes bank access; if revocation fails, deletion stops so you can retry. Plain bank access tokens are never returned to your browser.

Provider: Plaid Inc. handles bank connections under its terms and privacy policies. Bank linking requires separate provider configuration and approval before a production launch.

Google Calendar integration

Finstracker Premium offers an optional Google Calendar sync that adds reminder events for your unused credit-card perks, offer deadlines and annual-fee renewals, so you don't miss them. It is off by default and only activates if you click Connect Google Calendar in Perks & Offers → Reminders and approve Google's consent screen.

What we request: the https://www.googleapis.com/auth/calendar.events scope, which lets us create, update and delete events on your primary Google Calendar, plus openid and email so we can show which Google account is connected.

What we do with it: when you click Sync now, we create or update one all-day event per unused perk, offer and upcoming annual fee, with pop-up reminders at the times you picked. The event contains the title, dollar value and card. Each event is tagged privately as created by Finstracker. To avoid duplicates we look up only events carrying that tag, and we delete a tagged event when the perk or offer it belongs to is marked used or deleted.

What we do not do: we never read, change or delete events that Finstracker did not create. We never send your Google Calendar data or access token to our servers or to any third party.

Where the access token lives: only in your browser's localStorage on the device you connected from. It expires after about an hour, and it is removed when you sign out of Finstracker or click Disconnect.

How to revoke: click Disconnect and the access token is revoked with Google and erased from your browser. You can also revoke access any time at myaccount.google.com/permissions. Events already created stay in your calendar until you delete them.

Finstracker's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Terms of service

Premium. Premium costs $4 a month or $36 a year in US dollars, billed through Stripe. Every account gets a 30-day free trial with no card required; nothing is charged unless you choose a plan. Paid plans renew automatically at the end of each period until you cancel. You can cancel any time in Plan & billing; Premium then stays on until the end of the period you paid for. Deleting your account cancels Premium. If something went wrong with a charge, contact us within 14 days.

Finstracker is provided as-is. You're responsible for the accuracy of the data you enter. We make a best effort to keep the service available, but for a beta-scale deploy there is no formal SLA.

You may not use Finstracker to track activity that is not yours, or to circumvent any credit card issuer's terms.

Cookies

When you first visit, a banner asks you to choose Essential only or Accept all. You can change your choice any time with Cookie settings, linked in the footer of every page. If your browser sends a Global Privacy Control signal, we treat it as Essential only until you choose otherwise.

Essential (always on)

These are needed for the site to work, so they don't need your consent.

  • fins_consent cookie: remembers your cookie choice. Kept for 12 months.
  • pointwise.token in browser storage: keeps you signed in, for up to 30 days or until you close the tab, depending on Stay signed in.
  • pointwise.* in browser storage: a copy of your dashboard data and layout so pages open instantly. Cleared when you sign out.
  • If you sign in with Google, Google sets its own cookies in the sign-in window under Google's privacy policy.
  • If a CAPTCHA is shown on sign-up or password reset, Cloudflare Turnstile may store data needed to tell people from bots, under Cloudflare's privacy policy.

Analytics (only with Accept all)

  • fins_anon cookie: a random ID, so repeat visits from the same browser count once. Kept for 13 months from your last visit.
  • fins_session in browser storage: a random ID that groups page views into one visit. Ends after 30 minutes without activity.

With these we record which pages are visited, the page title, the site you came from (just the domain), the time, and a one-way hash of your IP address. It is sent only to Finstracker's own servers, is not linked to your account, and is deleted automatically after 13 months. We use it to see which pages and features people use. We never use it for ads or share it.

If you switch to Essential only, analytics stops right away and the analytics cookie is removed.

We don't use advertising cookies or third-party tracking cookies.

Known trade-offs

A stolen session token is valid until it expires because there is no server-side revocation list yet; signing out removes it from your browser. Shorter-lived tokens with refresh and a rate limiter on sign-in are on the roadmap.

Reporting a vulnerability

If you find a security issue, please email us directly rather than opening a public issue. We'll respond within 48 hours.

See what your cards are actually doing for you.

Free to use. No credit card required.

Get started free