Privacy
Effective 19 November 2026
Ingrained stores short notes that your team's coding agents write and read, and the little it needs to know who is on your team. It does not receive your source code, your session transcripts, the output of your commands, or what you type to your agents. It does not sell data and it has no advertising or analytics trackers.
Who we are
Ingrained is operated by Enkore Labs LLC ("we"). This page covers the service at app.ingrained.dev, the Ingrained command-line client, and this website. To reach us about anything here, write to hello@ingrained.dev.
What we collect when you sign in
You sign in with Google or GitHub. We ask each of them only who you are.
| From | What we receive | What we never ask for |
|---|---|---|
| Your account's identifier, name and email address, and the company domain of the account when it belongs to an organisation | Mail, calendar, files, contacts or a directory | |
| GitHub | Your account's identifier, name and email address | Repositories, organisations or code |
We use this to know which person you are, to show your name to your teammates beside what you do, and, for a Google work account, to decide whether you may use a team's company link. We do not keep any access token from Google or GitHub after sign-in has finished.
Ingrained's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What the client sends from your machine
The command-line client and its hooks run on your machine beside your agent tool. They send the service only:
- proposed entries: one short statement each, with the commands and file paths it concerns;
- signals about entries, such as that one was shown, that a step it prescribes succeeded or failed, or that an agent confirmed or flagged it;
- counts for each session, such as how many entries were shown and how many commands failed;
- fingerprints of the lines of code an entry is about, and the commit time of the checkout a fingerprint was taken from. A fingerprint is a hash; the code cannot be recovered from it;
- the remote addresses of the repositories where the client is installed;
- the text of a search, when an agent searches the team's entries.
The client does not send source code, session transcripts, command output, or the text of what people type to their agents.
To turn a correction into an entry, the client may ask your own agent tool to read a session on your machine. That request goes to your agent tool's provider under your agreement with them, exactly as your other use of the tool does. It does not come to us.
Entries are written by agents and people. An entry could contain personal or confidential information if someone puts it there. The client and the service both check every entry for things that look like passwords and keys and refuse those, but they cannot recognise everything. Your team can edit or retire any entry on the review page.
What we keep, and for how long
| What | How long |
|---|---|
| Your team's entries, their history and signals | Until your team asks us to delete them. A retired entry stays in the history so the team can see what was decided |
| Members' names and email addresses, and their connected sign-ins | While the person is a member. When a member is removed their sign-ins and sessions are deleted; their name stays beside past actions in the history |
| Session counts | Until your team asks us to delete them |
| The service's logs: which team and member made a request, when, and counts. No entry text and no search text | 90 days |
| Database backups | 7 days |
Who can see your team's entries
Every member of your team can read, confirm, edit and retire the team's entries, and the agents on their machines are given them. Nobody on another team can. Each team's data is separated from every other team's by the database, not only by the application.
A small number of people who operate the service can reach the database to keep it running and to investigate faults. We do not read a team's entries for any other purpose.
Who else handles the data
| Company | What for |
|---|---|
| Amazon Web Services | Runs the service and stores its data, in the United States (Oregon). Data is encrypted in transit and at rest |
| Google and GitHub | Sign-in, as described above. They learn that you signed in to Ingrained |
| Cloudflare | Serves this website and answers DNS for ingrained.dev |
We do not sell personal information, and we do not share it with anyone for advertising. We would disclose information if the law required it, and would tell the team concerned unless the law forbade that.
Cookies
The service at app.ingrained.dev sets one cookie that keeps you signed in, and one short-lived cookie while you are in the middle of signing in. This website sets none. Neither uses analytics, advertising or third-party trackers.
Your choices
- You can disconnect a sign-in, and an admin can remove a member, on the "Team and devices" page.
- You can remove a command-line client's access there too, and uninstall the client from your machine at any time.
- You can ask us for a copy of the personal information we hold about you, to correct it, or to delete it. A team's admin can ask us to delete the team and everything it stored. Write to hello@ingrained.dev; we answer within 30 days.
Depending on where you live you may have further rights under local law, including the right to complain to a data protection authority.
Children
Ingrained is a tool for people who write software at work. It is not directed at children, and we do not knowingly collect information from anyone under 16.
Changes
If we change this page in a way that matters, we will change the date at the top and tell the admins of each team by email before the change takes effect.