Security: what DeployIt does with your code
What DeployIt reads, what it keeps, what it sends, and to whom. No slogans: what you need to decide.
Where your code goes
DeployIt reads your repositories
Through the DeployIt GitHub application, or through an OAuth authorization on GitLab (gitlab.com), on the repositories you connect and no others. It adds one webhook per repository, to be told about new commits, and removes it with the repository; no commit, branch or PR ever comes from DeployIt. On GitLab, the access requested (the api scope) would allow writes: DeployIt uses it only for that webhook.
It keeps a working copy
The content of each selected source file (secret and key files are excluded) and its summary, to answer without rereading the whole repository. It is hosted by DigitalOcean in London (United Kingdom), kept while the repository is connected and erased when you remove the repository from DeployIt. You can also keep it in your own database.
A language model reads your code
At indexing time, the content of each selected file is sent to the model to write a summary; after that, what it needs to answer a question or read a commit. OpenAI by default; the provider whose key you bring, for each role (agent, expert, mini) where you add it. We do not train or fine-tune any model on your code.
The answer goes out, filtered by profile
It goes back to the assistant of the person who asked. What it can show depends on that person's profile, not on their question.
What gets out, profile by profile
| Profile | Code | Developer names | Statistics |
|---|---|---|---|
| Everyone | No line, no file path | Removed, when DeployIt knows them | None |
| Developers | Excerpts and paths | Shown | None |
| Leadership | No line, no file path: commit subjects, PR titles, module names, and links to the commits and PRs at your Git host | Shown | Team and individuals |
| Data tool | No questions about the code; the statistics carry the detail (modules, paths) | Shown | Team and individuals, in bulk |
The filter removes what it recognizes: code blocks and fragments, file paths, secrets, personal email addresses. It does not prove their absence: the leak test measures what still gets through.
Who gets in, and how
- One link per company. It carries a code. Whoever adds it to their assistant signs up themselves, with their name and email, on the Everyone profile. The email isn't verified: the code is the door.
- A profile is given to a person, never to an address. An administrator raises the profile of a sign-up they can see. Signing up again with the same address gives Everyone back, never more.
- One token per person. After signing up, each person's assistant presents a token that belongs to them alone, valid for an hour and renewed. Removing a person cuts their access without touching anyone else's. With the link, they can sign up again, on the Everyone profile: change the link's code as well.
- A code you can change. If the link has left the company, you change its code: nobody can sign up with the old one, and people already signed up keep their access. In an emergency, you can also sign everyone out at once.
- Your identity provider, if you have one. If your Claude organization manages sign-ins through its identity provider, automatic sign-in is available in beta, on request: write to us. An administrator then declares that issuer; each person's address is attested when the issuer is Claude or when your provider marks it verified, and stays self-declared otherwise.
- A key for machines. A data warehouse doesn't sign up: it presents a key, shown only once, that opens the statistics and nothing else.
What we commit to
No training
We do not train or fine-tune any model on your code.
Encryption
In transit, over HTTPS. Your model keys, the secrets of your tool servers and the address of your database are encrypted separately (AES-256-GCM). According to DigitalOcean's documentation, the database and the cache it manages also encrypt data at rest (LUKS).
A leak test
DeployIt attacks each no-code profile, on demand, and after a settings change that affects the output (at most once an hour, 10 times a day), and tells you what gets out.
A log
Who asked what, what was answered, and who changed which setting.
Deletion
For a removed repository or a deleted company, access is cut at once, then a queued job erases the data, usually within the following hours, and retries if it fails. A removed repository's statistics are erased only if you ask. The daily database backups hold the data until they rotate: DigitalOcean keeps them for seven days. A company can be deleted once its last paid period has ended; the end of a subscription erases nothing: the company moves to the free plan.
Notice within 72 hours
If there is a data breach, you are told within that time at the latest.
What we don't promise
- That a model is never wrong. That is why every answer says whether it is verified, backend only, not found or inconclusive.
- That a shared link won't travel. Anyone with the link can sign up. You see every sign-up, you can remove a person, and you can change the code.
- That a filter or a leak test proves nothing can get out. The test catches the leaks it knows how to provoke. It warns you; it doesn't close anything for you.
The companies that handle your data
| Company | Role |
|---|---|
| DigitalOcean | Hosts the application; PostgreSQL database (where the working copy lives), cache and queues (Valkey), managed by DigitalOcean. In London (United Kingdom). |
| OpenAI | Receives the content of the files to index, to write their summary, then what is needed to answer a question or read a commit. Nothing is sent if you bring your key for each role (agent, expert and mini); otherwise, the roles without a key stay with OpenAI. |
| Paddle | Payment and invoicing, as reseller. Sees neither code nor statistics. |
| alwaysdata | Sends service emails (alerts, invitations). French company, servers in France. |
| GitHub, GitLab | The sources: the repositories you connect. DeployIt reads the code and history there, and sets one webhook per repository. |
Found a vulnerability? Write to [email protected]: a person will get back to you.
Connect your code, ask your first question
30-day trial, no card required. DeployIt reads your repositories: no commit, no branch, no PR.