legal · updated 2026-10-18
privacy policy
This policy covers diff social at diffsocial.dev, run by Aion Consulting, a business based in the United States ("Aion Consulting", "we"). It says what we collect, why, who helps us process it, and how long we keep it. A self-hosted copy of diff social is run by its own operator, whose policy applies there.
what we collect
| what | from where | why |
|---|---|---|
| your name, email and account id | our identity provider, when you sign in | to sign you in, show who wrote what, and contact admins about their tenant |
| your tenants and roles | your organization in the identity provider, or a tenant admin | to decide what you may open and do |
| GitHub link and installation data | GitHub, when you link your account or a tenant claims an installation | to open the code you may read; your GitHub tokens are stored encrypted and never sent to your browser |
| room content | you and your tenant: messages, decisions, the diffs and code a room shows, and agents’ answers | to provide the rooms; it is visible to the members of the tenant it belongs to |
| billing details | Stripe, when an admin subscribes | to know a tenant’s plan and seats; card details stay with Stripe |
| request logs | your browser, with each request: IP address, user agent, page, referrer, time | to run, secure and debug the service, enforce rate limits, and count visits |
| usage events | the service itself: that a room was opened, an agent asked, a proposal accepted | to understand how the service is used; tenant and person ids in them are one-way hashed, and they never hold message text, names, repositories or code |
We do not use advertising or third-party analytics, run no tracking scripts in our pages, and do not sell or rent personal data or share it for advertising.
who processes it
We use these providers, each only for its part of the service, under their own terms and data protection commitments:
| provider | for | what it receives |
|---|---|---|
| Google Cloud (United States, us-central1) | hosting, database, backups, logs | everything the service stores |
| WorkOS | sign-in and organizations | your name, email and organization memberships |
| GitHub | the code rooms are about | requests for repositories, made with your link or your tenant’s installation |
| OpenRouter, and the provider of the model it routes to (today Anthropic) | built-in AI agents | what an agent is asked about: the repository and change title, the selected lines and surrounding code, and the request; not your name or email |
| Stripe | payments | billing contact and payment details an admin gives at checkout |
Remote agents a tenant adds receive what that tenant sends them, under the terms of whoever runs them. Their choice and that sharing are the tenant’s.
cookies and browser storage
We use only the cookies and browser storage the service needs to work: your session, a sign-in in progress, and your choices. None track you, and none come from advertisers or analytics companies. The cookie policy lists each one.
how long we keep it
- Account, tenant and room content: while the tenant uses the service. When a tenant or person asks us to delete it, or a tenant ends, we delete it within 30 days, and it leaves our database backups within 14 more days.
- Sessions: 30 days from sign-in, or until sign-out.
- Request logs: 30 days in Google Cloud’s standard logs, and 400 days in our analytics logs, which hold the same requests.
- Usage events: 400 days.
- Billing records: as long as tax and accounting law requires, at Stripe and with us.
security
Traffic is encrypted in transit. Each tenant’s rooms are kept apart by the database itself, not only by our code. Secrets live in Google Secret Manager; GitHub tokens are encrypted with a key the database does not hold; sessions are stored as hashes. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires.
your rights
You can ask us to show, correct, export or delete your personal data, or object to or restrict how we use it. Write to dj@codetestcode.io. We answer within 30 days, and may need to confirm it is you. Depending on where you live (for example under the GDPR in the EU and UK, or state laws in the United States such as the CCPA), you may have further rights, including to complain to a data protection authority.
Where the GDPR applies, we rely on performing our contract with you or your organization to provide the service, on our legitimate interest in securing, running and improving it for request logs and usage events, and on legal obligations for billing records. Data is processed in the United States; where the law requires, transfers rely on standard contractual clauses or an equivalent safeguard.
When a tenant uses the service for its organization, the tenant decides what goes in its rooms, and for that content we process personal data on its behalf.
california residents
If you live in California, the California Consumer Privacy Act, as amended by the California Privacy Rights Act, gives you the right to know what personal information we collect, use and disclose; to have it deleted or corrected; and not to be discriminated against for using these rights. We do not sell personal information, and do not share it for cross-context behavioral advertising, so there is nothing to opt out of. The categories we collect, their sources, purposes and who receives them are in the tables above, and how long we keep them is under how long we keep it. To use these rights, write to dj@codetestcode.io; an authorized agent may ask for you with your written permission.
children
The service is for people building software at work and is not meant for anyone under 16. We do not knowingly collect their data.
changes
We will post changes here with their date, and tell signed-in admins of changes that matter before they apply. Questions: dj@codetestcode.io.