Pare is a local-first personal finance tool. All financial data stays on your machine — there are no network calls, telemetry, or cloud sync.

Do not open a public issue for a security vulnerability. Email the maintainer directly at security@pare.money with a description and steps to reproduce. You'll get an acknowledgement, and fixes are coordinated before public disclosure.

All of the above are listed in .gitignore and must never be tracked.

1. No personal identifiers in lib/ or app/. No real names, account numbers, transit numbers, e-transfer handles, or other PII hardcoded in any tracked file.
2. Personal rules live only in the gitignored DB. Category rules that reference private info (e.g. a rent e-transfer handle) are added via the /categories UI and stored in data/pare.db + data/user-rules.json — both gitignored.
3. Real PDFs live outside the repo. Statement PDFs belong in the parent directory (../), which is not a git repository. Never git init the parent folder.
4. No telemetry or network calls. The app makes zero outbound requests. All parsing and categorisation happens locally.
5. Tests use synthetic fixtures only. Test data must be fabricated — never copy real transaction descriptions or amounts into test files.

Run these three commands from the repo root. Each should print nothing. If any produces output, fix it before pushing.

# 1. No sensitive files tracked
git ls-files | grep -iE '\.(db|pdf|csv|xlsx)$|^data/'

# 2. No personal identifiers in source (replace placeholders with your real values)
git grep -niE '<your-etransfer-handle>|<your-account-number>|<your-transit-number>|<your-surname>'

# 3. No sensitive files in any past commit
git log --all --oneline -- 'data/*' '*.db' '*.pdf' '*.csv'

If a sensitive file was committed but not yet pushed:

git rm --cached <file>        # unstage
echo '<file>' >> .gitignore   # prevent re-add
git commit -m "remove tracked sensitive file"

If the file exists in pushed history, the data is considered exposed:

1. Rewrite history with git filter-repo or BFG Repo-Cleaner to strip the file from all commits.
2. Force-push the cleaned history.
3. Treat any exposed account numbers, transit numbers, or e-transfer handles as compromised — contact your bank to rotate or monitor them.
4. Ask all collaborators to re-clone (their local copies still contain the old history).