Privacy Policy

Effective 5 Oct 2026

This policy explains what LimitKeep ("LimitKeep", "we", "us") collects when you use the app, why, who processes it for us, and how you can get it deleted. LimitKeep is a personal credit-card utilization tracker: you add your own cards, limits and balances — by hand, or on Pro by uploading a statement for LimitKeep to read — and LimitKeep works out your utilization, flags it against your thresholds, and helps you plan payments.

1. Information we collect

Almost everything below is information you enter yourself. The exceptions are statements you choose to upload (section 3) and a small amount of technical data (the last row). LimitKeep has no connection to your bank, card issuer, or credit bureau, and never pulls data from them.

Category	What it includes	Why we collect it
Account	Email, password (stored as a salted hash, never in plain text), first name, and optional last name	Sign you in; greet you by name
Card details	Card nickname, optional last 4 digits, credit limit, current balance, payment due date and statement/reporting dates, and — if you add them — APR, minimum payment, and (Pro) AZEO settings	Calculate utilization, reporting dates, pay-down targets, interest estimates, and payoff projections
Activity history	The balance updates, payments, charges, and interest you log, with their dates (including backdated ones), any memo you add, and — for entries imported from a statement — the transaction description printed on it, usually a merchant name	Show your history and charts, and let you delete or edit entries
Statement uploads (Pro, optional)	The PDF or image you upload, only while it's being read (see section 3). From the results you confirm: the statement period, balances, interest, an estimated APR, and the transactions you approve	Fill in your cards and history for you, for you to review first
Preferences	Your thresholds and closing window, Simple or Advanced mode, whether interest tracking and AZEO are on, reminder settings, cards you've skipped in recommendations, and your walkthrough progress	Personalize the app
Reminders	If reminders are on: a record of which reminders were sent, so you don't get duplicates. If you turn on browser notifications: the push address and keys your browser gives us for that device	Remind you before cards report and payments are due
Billing (paid subscribers only)	Stripe customer ID, subscription plan and status, renewal date. We never see or store your card number — Stripe handles that directly.	Manage your subscription and billing
Technical	Your IP address when you open a one-tap update link from a reminder, and — if you delete your account — the date it's scheduled to be deleted	Stop abuse of those links; run the 30-day deletion window

2. What we never ask for

LimitKeep never requests your full card number, CVV, expiration date, online banking credentials, or Social Security number. The "last 4 digits" field is optional and only for you to tell cards apart — it isn't validated against, or connected to, any real card. A statement you upload may contain more than we need, such as your name, mailing address, or part of your account number; section 3 explains how that's handled.

3. Statement uploads

Statement upload is an optional Pro feature. When you upload a statement:

The file travels over an encrypted connection to our server, which sends it to Anthropic, the AI provider that reads it for us through its API. Anthropic returns what it found: the statement dates, balances, interest, APR, card name, last 4 digits, credit limit, and the transaction lines.
We don't store the file. It's held in memory only while it's being read, and is never saved to our database or any file storage.
Nothing is saved until you review it. The results appear on an editable review screen, and only what you confirm is saved — as history entries, each with its transaction description, and a short summary of the statement.
Anthropic processes the file as our service provider, under its commercial terms: it doesn't use the file to train its models, and it keeps it only for a limited period for safety and abuse monitoring before deleting it.
Everything in the file is sent, including your name, address, and any partial account number printed on it. If you'd rather not share something, crop or cover it before uploading — LimitKeep only needs the balances, dates, and transactions.

4. Where your data lives, and who processes it

Your data is stored in a Postgres database run by Supabase, our database and authentication provider, encrypted in transit (TLS) and at rest. Every row is protected by row-level security rules that scope it to your account, so no other user can read your data. A few server-side jobs — sending reminders, reading statement uploads, billing, and account deletion — use restricted server access to do that one job and nothing else.

These providers process data on our behalf, only to run the service:

Supabase — database and sign-in.
Vercel — hosts the app.
Stripe — payments, for Lite and Pro subscribers. Stripe receives your email and payment details directly from you at checkout; we never see your card number.
Anthropic — reads statements you upload (section 3).
Resend — delivers our emails: sign-up confirmation, password resets, reminders, and account notices. Reminder emails include the names, balances, and utilization of the cards they're about.
Your browser's push service — if you turn on browser notifications, the company behind your browser (for example Apple, Google, or Mozilla) delivers them. A notification includes the names of the cards it's about.

We don't share your data with anyone beyond these providers, and we don't sell it.

5. Cookies, local storage & tracking

LimitKeep doesn't run third-party analytics or advertising trackers. Your sign-in session is kept in your browser's local storage, not a tracking cookie, along with a few display choices (light or dark, and your color palette) and, briefly, a plan you picked before signing up. If you turn on browser notifications, a small background script (a service worker) is installed so your browser can show them. Only LimitKeep reads any of this.

6. Retention & deletion

We keep your data for as long as your account is open. You can delete your account at any time from Profile → Delete account. Your account is then scheduled for deletion and kept for 30 days, so it can be restored if it was a mistake — sign in during that time to get everything back. After 30 days your account and every card, payment, and history record tied to it are permanently and irreversibly deleted. We'll email you the date when you delete it.

Uploaded statement files aren't kept at all (section 3).
IP addresses from one-tap update links are stored only as a one-way hash, and deleted within a day.
Deleted data can remain in our database provider's encrypted backups for a short time before those backups expire.

7. Your rights

You can view and edit almost everything directly in the app. Lite and Pro subscribers can download a full export of their cards, history, and preferences any time from Settings → General → Your data. For anything else — a correction you can't make yourself, or an export if you're on the free plan — email us and we'll handle it by hand.

8. Children's privacy

LimitKeep isn't directed at children and we don't knowingly collect information from anyone under 13. If you believe a child has created an account, contact us and we'll delete it.

9. Changes to this policy

If this policy changes, we'll update the effective date above and post the new version at this same page. Material changes will be flagged in the app.

10. Contact

Questions about this policy or your data: support@limitkeep.com.