Privacy Policy

This Privacy Policy explains how Divergent Laboratories, Inc. (“Company”, “we”, “us”) collects, uses, and shares personal data when you use Elliot, the websites at tryelliot.app and its subdomains, and the related services (together, the “Services”). It forms part of our Terms of Use, and capitalized terms not defined here have the meaning given in the Terms. The Services are offered to businesses and professionals, not to consumers or anyone under 18.

We are responsible for the personal data described in this policy. You can reach us at nick@divergentlabs.xyz or at the address in Contact.

1. Data we collect

Account data. When you create an Account we collect your name, email address, and password, which we store only as a hash. If you sign in with GitHub, we receive your GitHub name, email address, profile picture, and the access tokens GitHub issues for the sign-in.

Workspace data. The name of each workspace you create or join, its members and their roles, and invitations, including the email address of each person invited and the name and email address of the person who invited them.

Session data. For each signed-in session we store the IP address and browser user agent, so you and we can recognize and end sessions and investigate misuse.

Repository data. When you install the Elliot GitHub App, we receive the GitHub account name and type, the names, default branches, languages, and visibility of the repositories you grant access to, and the GitHub user ID of the person who approved the installation. To run a scan we download a copy of the repository’s source code at the commit being scanned (see Section 3).

Scan data. The results of each scan: findings, the code excerpts and traces that support them, impact and remediation text, proof-of-concept code and the commands and output from running it, and records of the work our models perform (prompts, tool calls, and responses). Source code can contain personal data, such as names and email addresses in comments or fixtures, and scan data may include it.

Board activity. Comments, assignments, finding statuses, review instructions you give Elliot, and reports you export.

Billing data. Payments are handled by Stripe. You enter card and billing details on Stripe’s pages, and we receive your workspace identifier, your plan, the status of your payments, and, for one-off scans, the name of the repository paid for. We do not receive full card numbers.

Connected agents. When you connect a coding agent or other client to our MCP server, we store the client’s name and redirect addresses, the scopes you approve, and the tokens issued to it.

Communications. Messages you send us, including support requests, security reports, and legal notices.

Usage data. The marketing site and the dashboard use PostHog to measure how they are used. PostHog records the pages you view, the links and buttons you click, your browser and device, and your approximate location, which it derives from your IP address. In the dashboard it also records the actions you take, such as creating a workspace, starting a scan, or changing a finding’s status, and errors that occur in your browser. When you sign in, we send PostHog your user ID, name, and email address, so this activity is linked to your Account, including visits to the marketing site from the same browser.

Website visits. Our hosting provider processes standard request data, such as IP address, browser user agent, and the page requested, to deliver and protect the websites.

2. How we use it

We use personal data to:

  • provide the Services: run scans, test findings in a sandbox, show results on your board, post results to GitHub when you enable it, and export reports;
  • create and secure Accounts, including verifying email addresses and sending workspace invitations;
  • process payments and manage subscriptions;
  • support you, which can include authorized staff viewing the Services as you see them for a limited time to investigate a problem;
  • detect and prevent abuse, including testing of targets you are not authorized to test (Terms, Section 2.7), and enforce our Terms;
  • train, evaluate, and improve our models and the Services, as described in Section 4;
  • understand how the websites and the dashboard are used, and find and fix errors in them;
  • send service messages, such as notices about changes to the Terms or this policy;
  • comply with law and respond to lawful requests.

We do not sell personal data and do not use it for advertising.

If the GDPR or a similar law applies to you, we rely on these legal bases: performance of our contract with you or your organization (providing the Services and billing); our legitimate interests in securing the Services, preventing abuse, and improving our models and the Services (Section 4); compliance with legal obligations; and your consent where we ask for it.

3. Source code

For each scan, Elliot downloads the repository at the commit being scanned to temporary storage on our scanning servers and deletes that copy when the scan ends, whether it succeeds or fails.

To test a finding, Elliot sends a copy of the code to an isolated virtual machine, writes a proof of concept, and runs it there. The machine has no access to our credentials or your servers, runs for at most 30 minutes, and is then destroyed.

Our models read your code to analyze it, and the excerpts that support a finding are stored with that finding. Records of the models’ work, which contain excerpts of your code, are stored with your scans. Elliot reads your code through the GitHub App with read access, and writes to GitHub only to post pull request comments and checks.

4. Model improvement

We use scan data, including records of our models’ work and the statuses and feedback you give findings, to train, evaluate, and improve our models and the Services, as described in Section 2.10 of the Terms. Access to this data is limited to the people and service providers who need it for that purpose. We do not sell it and do not publish your code or findings.

You can opt out by emailing nick@divergentlabs.xyz. The opt-out covers scans run after we confirm it, and we will also leave records of your earlier scans out of models we train after that date. Models trained before your opt-out are not retrained.

5. Who we share it with

We share personal data with the service providers below, which process it on our behalf to run the Services, and with no one else except as described in this section.

Provider Purpose Data
Amazon Web Services Hosting the scanning servers, sandboxes, logs, and secrets All data processed during scans
PlanetScale Database hosting Account, workspace, session, repository, scan, and billing data
Vercel Hosting the websites and the dashboard Account and session data, request data
Wafer Model inference Source code, scan data, and review instructions
Baseten Model inference Source code, scan data, and review instructions
Hopper Model inference Source code, scan data, and review instructions
Modal Model inference Source code, scan data, and review instructions
Stripe Payments and subscriptions Billing data, workspace identifier
Resend Account and invitation emails Names, email addresses, workspace names
GitHub Sign-in and repository access Account data, repository data, results you post to GitHub
PostHog Product analytics and error tracking Usage data, user ID, name, email address

We may also disclose personal data to comply with law or a valid legal request; to protect the Services, our users, or others, including by reporting suspected unauthorized testing to affected parties and law enforcement (Terms, Section 2.7); and to a buyer or successor in a merger, acquisition, or sale of assets, under the same protections as this policy.

Within a workspace, members can see each other’s names, profile pictures, comments, and assignments.

6. International transfers

Our scanning servers and database are hosted primarily in Ireland (AWS eu-west-1). Some providers, including Vercel, Stripe, Resend, and GitHub, process data in the United States and other countries. Where we transfer personal data out of the European Economic Area, the United Kingdom, or Switzerland, we rely on safeguards recognized by law, such as the European Commission’s Standard Contractual Clauses.

7. Retention

  • Account data is kept while your Account exists.
  • Workspace, repository, and scan data are kept while the workspace exists, including after you uninstall the GitHub App, so your findings history stays available.
  • Source code downloaded for a scan is deleted when the scan ends. Sandbox machines are destroyed within 30 minutes.
  • Server logs are kept for 30 days.
  • After termination, you can ask us within 30 days to export your Customer Data and Outputs, after which we delete them (Terms, Section 7).

You can ask us to delete your Account or workspace at any time by emailing nick@divergentlabs.xyz. We delete or anonymize the data unless we must keep it to comply with law, resolve disputes, or enforce our Terms. Data already used to train a model cannot be removed from that model.

8. Cookies

The marketing site and the dashboard set a PostHog analytics cookie on tryelliot.app and its subdomains, and keep a copy of it in your browser’s local storage. It holds a random identifier that recognizes your browser on return visits and links your visits to the marketing site with your Account once you sign in. The cookie lasts one year. You can block it in your browser settings, and both sites keep working.

The dashboard also uses cookies it needs to work: a session cookie that keeps you signed in, and a short-lived cookie, valid for 10 minutes, that protects the GitHub App installation flow. We use no advertising cookies.

9. Security

Connections to the Services and between our systems use TLS. Secrets are kept in a dedicated secrets manager, passwords are stored as hashes, and proofs of concept run in isolated virtual machines without access to our credentials. No system is perfectly secure. If we learn of a breach affecting your personal data, we will notify you as the law requires. To report a vulnerability in Elliot, see our vulnerability disclosure policy.

10. Your rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal data, to object to or restrict how we use it, including for model improvement, and to withdraw consent. Email nick@divergentlabs.xyz to use these rights. We may need to verify your identity, and we respond within the time the law requires.

If your personal data is part of a workspace run by your employer or another organization, we may refer your request to that organization.

If you are in the European Economic Area or the United Kingdom, you can also complain to your local data protection authority.

11. Changes

We may update this policy. We will notify you of material changes at least 30 days before they take effect, by email or in the Services, and update the date at the top of this page.

Contact

Divergent Laboratories, Inc., Attn: Privacy
2810 North Church Street STE 90122
Wilmington, Delaware 19802
Email: nick@divergentlabs.xyz