Privacy
What Lodeline stores, why, and for how long.
What we store
- Usage metadata from your coding tools: tool, model, token counts, cost, repository name, time, the tool's version, whether it is paid by subscription or per token, and the session ID the tool generates (a random ID, not a person).
- Counts of lines changed and of edits accepted or rejected, per repository and model, from Claude Code. Counts only, never the code.
- Daily team totals of AI suggestions shown and accepted, and of requests by type, from Cursor and Copilot.
- A salted, one-way hash of each tool account, used only to avoid counting the same usage twice. It cannot be turned back into a name or email.
- Teams, repository mappings, budgets and invoice totals that you enter.
- Email addresses and roles of your workspace members, for sign-in and notifications.
What we never store
Source code, prompts, completions, keystrokes or file contents. Nothing is scored or ranked per person; every figure is a team or repository total.
How long we keep it
- Individual usage events: 90 days.
- Daily totals per tool: while your workspace exists, so older invoices can still be checked.
- After you delete your workspace: it can be restored for 30 days, then everything is deleted. Database backups can hold it for up to 14 more days.
Who processes it
These providers run parts of the service on our behalf:
- Tiger Data: database
- Vercel: web app
- Fly.io: data intake
- Redis Cloud: job queue
- Clerk: sign-in
- Resend: email
- Sentry: error reports, without usage data or credentials
- Slack: only if you connect it
- Google Workspace: our own email
What each one handles and where: Sub-processors.
We do not sell data or use it to train models.
Who is responsible
For usage data your workspace sends, your company decides how it is used and we process it on its behalf under our agreement. For your sign-in account, demo requests and messages you send us, we are responsible.
Why we process it
- To provide the service under our agreement with your company (GDPR Art. 6(1)(b)).
- To keep it secure and prevent abuse, our legitimate interest (Art. 6(1)(f)).
- To answer a demo request you send (Art. 6(1)(b)).
Cookies
Only the ones the service needs: your sign-in session, and two short-lived cookies while you connect Slack. No analytics or advertising cookies. Your light or dark theme is kept in your browser and not sent to us.
IP addresses
Used to limit how often a form or endpoint can be called, and kept for minutes. Our hosting providers keep request logs with IP addresses for their own limited periods.
Your rights
You can ask to see, correct, delete or export your data, or object to its use, and you can complain to your data protection authority. We reply within 30 days. If the data belongs to your company's workspace, we pass the request to its admin.
California
We do not sell or share personal information.
Your controls
Export everything as CSV, or delete the workspace, from Settings › Danger zone. Owners and admins are emailed when a deletion is scheduled.
Questions: privacy@lodeline.ai
This page describes how the product handles data. The data processing terms in your contract govern.