Privacy

What IL Co collects, why, what it keeps, and how to have it removed. Written to match what the product does today.

Last updated 24 October 2026

What we collect, and why

Your account. Name, email address and a hash of your password (never the password itself), so you can sign in. Sign-in sessions are kept so you stay signed in, and end when you sign out or change your password.

What you create in IL Co. Handoffs, their edits and approvals, comments, questions and notes, so your team can work from them.

What you connect. When someone in your workspace connects Slack, Linear or GitHub, IL Co reads the messages, issues and pull requests a handoff draws on, and the channels your workspace chooses to import. It keeps the excerpts it cites and links back to the originals. GitHub access is read-only.

Other tools, only when a handoff cites them. If your workspace connects Jira, Confluence, Notion, GitLab, Google Docs, Sentry, PagerDuty, Figma or Microsoft Teams, IL Co reads only the issue, page, merge request, document, incident, file or message a handoff links to, and keeps the excerpts it cites. It never writes to these tools.

Meeting transcripts you paste. If you add a transcript when starting a handoff, it is kept in your workspace so the handoff can cite it. IL Co does not join or record meetings.

Your GitHub account, if you link it. Your GitHub username and numeric id, so a pull request of yours that is merged can start a handoff draft for you. You prove the account by signing in with GitHub; IL Co keeps no GitHub token for it, and you can unlink it at any time.

AI clients you connect. When you connect ChatGPT, Claude, Cursor, Codex or another MCP client, IL Co records the connection: its name, the workspace and permissions you chose, and when it was last used. Its tokens are stored only as one-way hashes.

The beta form. Your email, and the company and message if you give them, so we can reply.

Operational records. Request logs (address, path, time, a request id) to run and protect the service, and error reports, which are configured not to attach personal data such as email addresses or tokens. IL Co also records how the product is used (for example, that a handoff was approved) to understand what works; it does not sell this or use it for advertising.

The public pull-request tool

Turning a public GitHub pull request into a handoff needs no account. IL Co reads that pull request from GitHub, builds the handoff without an AI model, and keeps the result in memory for up to ten minutes so a repeat request is fast. Your network address is used only to limit how often one caller can ask, and is not stored with the request. Private repositories are refused.

AI drafting

When AI drafting is on, IL Co sends a handoff's own cited sources (at most 40 excerpts, each at most 1,200 characters) to its AI provider, Anthropic, to draft the text. Nothing else in your workspace is sent. The draft is checked against those sources, and its author reviews it before anyone else in the workspace sees it or anything is posted (with the Handoff Concierge service, the team's agreed reviewer sees it first; see below). Anthropic processes the request under its API terms.

Handoff Concierge (human review)

A team that takes the Handoff Concierge service agrees, in writing, that a person at IL Co reviews each draft before its author does. That reviewer is a member the team invites to its own workspace, so they see only what the workspace's connections already give it. They see a draft only while it is in that review — not the author's own review, other drafts, or anything rejected — and every edit, question and sign-off they make is recorded in the handoff's history. The author still approves every handoff; the reviewer cannot.

When the service ends or is paused, drafts stop going to the reviewer at once. Removing the reviewer from the workspace and disconnecting tools are the team’s own controls, described below.

Who else receives data

IL Co runs on these services, each receiving only what its job needs: Render (runs the API), Cloudflare (serves this website and stores uploaded files), Neon (the database), Upstash (short-lived counters and caches), Resend (sign-in and invitation email), Sentry (error reports), and Anthropic (AI drafting, as above). Slack, Linear and GitHub receive what an approved handoff posts back to them.

IL Co does not sell personal data and does not share it for advertising.

How it is protected

Connection tokens for Slack, Linear and GitHub are encrypted by IL Co before they are stored. Passwords and AI-client tokens are stored only as hashes. Every request is checked against workspace membership, and a draft is visible only to its author until they approve it (and, for a Handoff Concierge team, to its agreed reviewer during the review). More on the security page.

How long it is kept

Workspace content stays until it is deleted in IL Co or the workspace is deleted. AI-client connections end when they expire or are revoked. The public tool keeps nothing beyond its ten-minute cache.

When you delete your account, it is closed at once and every session ends; it can be recovered for 30 days. Permanent erasure is not yet automatic: to have your data erased, email cto@ilconcetto.org and we will confirm when it is done.

Your controls

In Settings you can export your account data, delete your account, and see and revoke every connected AI client. A workspace admin can disconnect Slack, Linear or GitHub at any time, which stops IL Co reading from it.

Questions or requests: cto@ilconcetto.org.

Changes

When this page changes, the date above changes.