Legal

Privacy policy

Effective November 9, 2026Last updated November 9, 2026

This policy covers Chappe’s free early access and describes how the service handles data today. We email account holders before a material change takes effect.

  • Chappe never asks for your source code.Your agent sends identifiers and file locations, and it makes the edits itself, in your repository.
  • Chappe’s models never read your data.Chappe’s own model calls read public vendor changelogs only. Your events reach an AI service only if you register it as a destination.
  • Tokens are encrypted, keys are hashed.Tokens you give us are encrypted before they are stored; API keys and OAuth tokens are kept only as hashes.
  • Deleted when you ask.We do not sell your data, use it for ads or train models on it. We delete it from the database within 30 days of your request, and from backups 14 days later.

Who we are

Chappe is a service of Inxpanse Corporation (“Inxpanse”, “we”, “us”). This policy covers the Chappe API and MCP server at chappe-api.inxpanse.com, its sign-in pages and customer console, and the pages under inxpanse.com/chappe. Inxpanse decides how the personal data described here is used, which makes it the controller of that data. Write to us at contact@inxpanse.com.

What we store

The service keeps the following in its database, each for the reason given.

Your account

An account ID, the account name, and when it was created. For you as the person who signs in to it: an ID, your email address, and when you signed up and last signed in. For each of your sign-in methods, the one you sign up with and any you connect later in the console: with GitHub, your GitHub user ID and username, and your primary verified email address; with Google, your Google account ID and your email address, if Google has verified it; and when it was connected and last used. Your email address is that of the sign-in method you have had longest. Also which version of the terms you accepted, and when; when the account was last signed in to; and, if you ask us to delete the account, when you asked. For each API key: a SHA-256 hash, its first 12 characters so we can tell keys apart, the name you give it, and when it was created, last used (to within about five minutes) and revoked. The key itself is never stored. Each email Chappe sends you (a welcome when you sign up, a note when a sign-in method is connected or disconnected, and, if you ask us to delete the account, the date we delete it), with when it was sent. The email address you write to us from stays in our email, where we use it to answer you and send service notices.

To know which account a request comes from, to know who may sign in to it and how, to keep one account per person or team, to record that you accepted the terms, and to reach you.

Console sessions

For each sign-in to the console: a SHA-256 hash of the random value in its cookie, you, the account, whether you signed in with GitHub or Google, when the session started, when it was last used and when it expires. Not your IP address or browser. A session ends a day after its last use, a week after sign-in, or when you sign out, and its record is removed at the next sign-in. For each form that creates a key or an endpoint, a hash of a one-time value, kept with the session.

To keep you signed in, to sign you out, and to make sure a form sent twice creates nothing twice.

Projects and fingerprints

For each repository you register: a project name, the repository name (owner/name), and the fingerprint your agent uploads. A fingerprint holds the vendors and products the code calls; SDK names and versions with the manifest they came from; model IDs, API versions, endpoint paths with their HTTP method, and SDK method names; the names of environment variables that hold them, with any default or example value found in config files; file paths and line numbers; the scanned commit and time; and your agent’s short notes on items it is unsure of.

To match vendor changes to your code.

Impact results

For each project and each vendor change: whether the change affects the project, and which identifiers matched at which locations.

To decide what to send you and to answer impact requests.

Delivery endpoints

For each endpoint: its kind, its URL (your webhook URL, a Claude Code scheduled task’s Fire URL, or the GitHub repository name), its mode, and its secret, which is a scheduled task token, a GitHub token, a Slack webhook URL, or the webhook signing secret we generated. Secrets are encrypted with Fernet (AES-128 with an HMAC-SHA256 check) before they are stored, under a key kept in Google Secret Manager. For a ChatGPT subscription: ChatGPT’s callback URL, its signing secret (encrypted the same way), the project it watches and when it expires. When you delete an endpoint in the console, its secret is erased and its URL cut to the scheme and host at once; the endpoint record and its deliveries stay with your account.

To deliver changes where you asked, and to sign them.

Deliveries

Every event sent to every endpoint: the event as sent, which includes your repository name and the matched file locations; its status and attempts; the status code and response from the receiving service; and any error.

To retry failed deliveries, never send the same event twice, and debug.

Action reports

What your agent or workflow reports: the project, the change, the action and result, the pull request URL, and optional details (the agent, the test result, files and lines changed, issues, duration, and a note of up to 500 characters).

To measure which migrations land, for example how many of the pull requests Chappe causes get merged, to improve the changes we send, and to tell you when a run ended without a pull request.

Updates by email

When something on your projects needs a person and no Slack, webhook or ChatGPT endpoint of the project tells one, a record of it: the project, the change and what happened, such as a deadline reminder, dates that sources disagree on, an endpoint that kept failing with its status code, or a run of your agent that ended without a pull request, with the agent, the test result and the issues it reported (never its note). Chappe emails your account’s owners one digest of these at most once an hour, through Resend. Whether these emails are on is part of your account; turn them off on the Account page of the console.

To tell you about what needs you when nothing else does.

ChatGPT sign-ins

When ChatGPT signs in through OAuth: the client ChatGPT registers (its name, its redirect URLs, and its client secret, encrypted), and authorization codes and tokens stored as SHA-256 hashes, with the account, the hash of the API key used to sign in, the scopes and the expiry. Access tokens last an hour and refresh tokens 90 days. Revoking the API key ends the grant.

To let ChatGPT call Chappe without ever seeing your API key.

Request logs

Google Cloud records each request to the API: time, method, URL with its query, response status, latency, IP address and user agent. The service also logs its own errors, records refused ChatGPT client registrations with only the scheme and host of their redirect URLs, logs each new signup with its account ID and GitHub username, or for a Google signup only the domain of the email address (such as example.com), which sends us an email so we can welcome you, logs each console sign-in the same way, logs each sign-in method connected or disconnected with its account ID, GitHub or Google, and only the domain of its email address, and logs each request to delete an account, and each deletion, with its account ID.

To keep the service secure and fix problems.

The rest of the database is public vendor information: the changelog and deprecation pages Chappe reads, and the changes it finds in them.

What we do not collect

  • Source code or file contents. The scan instructions ask for identifiers, their locations and short notes, never code. Edits happen in your repository, made by your agent.
  • Secret values from your code or environment. The scan records variable names and the default or example values in config files, and the scan instructions forbid outputting any key, token, password or connection string.
  • Payment details. Early access is free.
  • Access to your GitHub repositories or Google account. Signing up, or connecting a sign-in method, asks GitHub only for your profile and email addresses, and Google only for your account ID and email address. Chappe revokes the provider’s token as soon as it has read them, and keeps no GitHub or Google token.
  • Tracking. These pages, the sign-in pages and the console run no analytics or advertising scripts and set no tracking cookies. Signing in sets two cookies for at most 10 minutes: one holds a random value, so that the GitHub or Google sign-in finishes in the browser that started it, and one holds what GitHub or Google told us, encrypted, until you accept the terms. Both are deleted when the sign-in ends. Connecting a sign-in method in the console sets only the first. The console then sets one session cookie, which holds a random value until the session ends.

How we use it

  • To match vendor changes to your projects and deliver them to the endpoints you chose.
  • To run, secure and debug the service.
  • To measure and improve Chappe’s accuracy.
  • To contact you about your account and the service.

We do not sell or rent your data, use it for advertising, or use it to train AI models. Chappe never puts your data into its own model requests. It reaches OpenAI or Anthropic only when you register an endpoint there, as described under Destinations you choose.

Chappe makes no automated decisions about people. Its matching compares code with vendor changes.

Legal bases

If you are in the European Economic Area or the United Kingdom, we rely on these legal bases:

  • Our contract with you, to run the service you signed up for: your account, matching and delivery. Where you use Chappe for an organization, we rely instead on our legitimate interest in serving that organization.
  • Our legitimate interests, to secure and debug the service, to measure and improve its accuracy, and to tell you about your account and the service. We weigh these interests against your rights, and you may object to them. If we ever send product news, each such email will let you opt out.
  • Legal obligations, where the law requires us to keep or disclose data.

We do not rely on consent today. If we ever ask for it, you may withdraw it at any time.

Where it is stored

In Google Cloud, region us-east4 (Northern Virginia, United States). The database is Cloud SQL for PostgreSQL, encrypted at rest by Google and reachable only through Google’s Cloud SQL connectors, over TLS. Secrets are kept in Google Secret Manager, and every read of one is logged. The database is backed up daily; backups are kept for 14 days, with 7 days of point-in-time recovery.

If you are outside the United States, using Chappe means your data is transferred to and stored in the United States. Our providers’ data processing terms cover the data they handle for us. If your organization is in the EEA or the UK and needs a transfer mechanism for the data it sends us, we will sign the Standard Contractual Clauses (controller to controller) and the UK addendum with you.

Who processes it

These companies process data for us:

CompanyWhat it does for ChappeWhat it receives
Google Cloud (Google LLC)Hosting, database, backups, logs and secretsEverything listed under What we store, in us-east4
OpenRouter, Inc.Runs the language models that read vendor changelogsPublic vendor changelog text, the vendor’s package names, and short summaries of changes Chappe already knows. No account, repository, fingerprint, endpoint or report ever goes into a model request.
Google Workspace (Google LLC)Our emailThe emails you send us
Resend (Plus Five Five, Inc.)Sends the emails Chappe sends youYour email address and the text of each email, in the United States. It keeps its record of each email for 30 days.
Cloudflare, Inc.Serves the pages at inxpanse.com, and answers DNS for the API’s domainRequests for these pages, with IP address and user agent. API traffic does not pass through Cloudflare.
Google Fonts (Google LLC)The fonts on these pagesYour IP address and user agent when a page loads its fonts

Signup uses Sign in with GitHub or Sign in with Google, as you choose, and so does connecting another sign-in method in the console. GitHub, Inc. or Google LLC runs that sign-in under its own privacy policy, learns that you use Chappe, and sends us only the details listed under Your account.

Destinations you choose

When you register an endpoint, Chappe sends your events there: to OpenAI for a ChatGPT subscription, to Anthropic for a Claude Code scheduled task, to GitHub for a repository_dispatch, to Slack, or to your own server. An event carries your repository name, the change, and the matched file locations. Those services handle it under your own agreement with them.

When Chappe reads vendor pages, it sends those vendors nothing about you.

Who else sees it

  • People at Inxpanse with admin access can read stored data to run and support the service. Chappe also has a reviewer role for checking vendor changes; it opens only the queue of vendor changes, not customer data.
  • Other customers see only statistics that name no project, and we may publish such statistics. A change’s migration statistics (how many projects merged it, common issues, median size) appear once at least three projects have reported on it. Report notes are never shown to them; we may turn what a note taught into a change’s shared migration notes, without naming you.
  • Authorities, only when the law requires it, or when it is needed to protect someone’s safety or the security of the service. Where we are allowed to, we tell you first.
  • A buyer or successor, if Inxpanse is merged or acquired. This policy keeps applying to your data, and we will tell you before it moves.

How long we keep it

  • Account, projects, endpoints, deliveries and reports: while your account is open. Chappe does not delete any of it on its own today. Expired subscriptions and tokens stop working, but their records stay until you ask us to delete them.
  • Console sessions: until they end, a week at most.
  • A sign-in method you disconnect: deleted from the database at once.
  • On request: we delete a project, an endpoint or your whole account from the database within 30 days of your request. Backups that still hold it expire 14 days later. Asking to delete your account in the console counts as a request: it ends your keys, endpoints and sessions at once, and we delete the account from the database 7 days later, unless you write to us before then to keep it.
  • When your access ends: if early access or your access ends and you do not move to a paid plan, we delete your data within 30 days.
  • Request logs: 30 days.
  • Emails Chappe sends you: 30 days, in the database and at Resend.
  • Updates by email: 30 days after each is recorded, whether or not it was emailed yet.
  • Email with us: as long as we need it to support your account.
  • Statistics that name no project may be kept after your data is deleted.

Your choices

In the console at chappe-api.inxpanse.com/app you can create and revoke API keys, add and delete webhook and Slack endpoints, sign out everywhere, and ask us to delete your account. Write to contact@inxpanse.com to:

  • get a copy of the data we hold for your account, as JSON;
  • correct it (you can also scan and register a repository again);
  • delete a project, an endpoint or your whole account;
  • revoke your API key, which also ends its ChatGPT sign-ins and subscriptions.

To stop deliveries at once, revoke the token at its source: regenerate the scheduled task’s token, revoke the GitHub token, remove the Slack webhook, or remove the plugin in ChatGPT. Chappe’s deliveries to it then fail.

We may ask you to confirm that a request comes from your account’s email address. We answer every request within 30 days, and we do not treat you differently for using these rights.

In the EEA and the UK

You also have the right to receive your data in a portable format (the JSON copy above), to restrict processing, to object to processing based on our legitimate interests, and to complain to your data protection authority.

In California

We honor these requests whether or not the CCPA applies to us. We collect identifiers (such as your email address, GitHub username and IP address), internet activity (the request logs above) and professional information (repository names and the identifiers in fingerprints). We get them from you, from your agent, from GitHub or Google when you sign up and from your browser, use them for the purposes under How we use it, and disclose them only to the service providers under Who processes it, to run the service. We have not sold or shared personal information for cross-context behavioral advertising in the past 12 months, and we do not. We do not use sensitive personal information to infer anything about you. You may ask to know, correct or delete your personal information, yourself or through an authorized agent.

Security

All API traffic uses TLS. API keys and OAuth tokens are stored as hashes, and endpoint secrets are encrypted. The database is reachable only through Google’s connectors, and each production secret can be read only by the services that need it, with every read logged. No system is perfectly secure: if we learn of a breach that affects your data, we will tell you without undue delay. To report a vulnerability, write to contact@inxpanse.com.

Chappe is for businesses and developers, not children. We do not knowingly collect data from anyone under 18, and if we learn we have, we delete it.

Changes and contact

When this policy changes, we post the new version here with a new date, and we email account holders before a material change takes effect.

Inxpanse Corporation, contact@inxpanse.com.