Privacy
The short version
- When you run a check, your app's source files are sent to our server, scanned, and deleted right after. We don't keep your code.
- We never use your code to train AI models, and we don't sell or share it.
- The AI cost figure is worked out on your own computer. Your coding tools' logs never leave it.
- In local mode, nothing is sent to us at all.
- If you create an account, we keep your name, email and company, and a short summary of each check you link to it (app name, score, number of problems and AI cost). Never the code.
Who we are
AppLedger is made by Contenta Software, which is responsible for the data described here. Questions or requests: bruno@contenta-software.com.
What we collect, and why
| What | Why | How long |
|---|---|---|
| Your app's source files, when you run a check (dependencies, build output, media and files over 1 MB are left out) | To scan them for security problems | Deleted as soon as the scan finishes, usually within a minute |
| A one-way, salted hash of your IP address, the time, upload size, scan duration and whether it succeeded | To keep the service running and spot abuse. The hash can't be turned back into your address | Up to 90 days |
| The same IP hash with timestamps | To limit how many checks one network can run per hour | One hour |
| Work email, company, company size and role, if you ask to join the pilot | To contact you about the pilot | Until the pilot ends, or until you ask us to delete it |
| If you create an account: your name, email, company or team name, and your password stored only as a one-way hash | To let you log in and show your organisation's ledger | Until you ask us to close the account |
| For checks run with a connection key: the app's name, score, grade, number of problems by level, the titles of the most serious problems, the scanners used, and the AI token and cost totals | To show the app in your organisation's ledger. People in your organisation can see it | Until you delete the app or close the account |
| Connection keys and password reset links, stored only as one-way hashes, plus hashed login attempts | To link computers to your account, reset passwords and stop password guessing | Keys until you revoke them; reset links one hour; login attempts one day |
What stays on your computer
- Reports and fix requests. They're written to a
.appledgerfolder inside your project. - AI effort. AppLedger reads Claude Code and Codex session logs on your computer to count tokens and estimate cost. Only you see the result.
- Local mode. If you set
APPLEDGER_MODE=local, the scanners run on your computer and nothing is sent to us.
Who else is involved
- DreamHost hosts our server in the United States (Ashburn, Virginia). Uploads are processed there.
- Google Fonts serves the fonts on this website, so Google sees your IP address when you load a page.
- The scanners we use, Trivy and Opengrep, run on our own server. Trivy downloads public vulnerability data; your code isn't sent to anyone.
The public pages set no cookies. When you log in, we set one essential cookie that keeps you logged in for up to 14 days. We use no analytics or advertising trackers.
Account emails, such as password reset links, are sent through DreamHost's mail servers.
Your choices and rights
You can ask us what we hold about you, ask us to correct or delete it, or object to how we use it. Write to the address above and we'll answer within 30 days. If you're in the EU or UK, you can also complain to your data protection authority.
Changes
If we change how we handle data, we'll update this page and the date at the top. For significant changes affecting pilot members, we'll email you first.