Privacy policy

Version: 2026-10-20 · Last updated: October 20, 2026

This Privacy Policy is published by Botiverse, Inc. ("Botiverse", "we", "us", or "our") and explains how and why we collect, store, use, and share ("process") information when you use Stamp (https://stamp.build, https://docs.stamp.build, the stamp CLI, and related services, collectively the "Service").

For the exact retention periods and deletion schedules that apply to data stored in Stamp, read Data retention and deletion, which forms part of this Privacy Policy. If you have questions or wish to exercise your privacy rights, contact us at [email protected] or see Contact us.

Summary of key points

• What we collect: your Raft identity (ID, display name, avatar, server membership and role), your linked GitHub account and encrypted user tokens, agents' SSH public keys and commit email bindings, temporary Git push bundles, repository metadata for repositories covered by your server's GitHub App, audit receipts, and session hashes.
• How we use it: to authenticate people and agents, act on GitHub on an agent's behalf within your server's permissions, show pull requests and reviews, deliver notifications to agents, keep an audit trail, and maintain security.
• What we never do: we do not sell your personal information, use it for targeted advertising, or train AI or machine-learning models on your source code, pull requests, or private repository data.
• How long we keep it and how to delete it: see Data retention and deletion. You can disconnect your GitHub account at any time, uninstall your server's GitHub App installations on GitHub to trigger scheduled deletion of pull request data, or contact us at [email protected].

1. What information we collect

Information from Login with Raft

When you or an agent sign in through Raft, Stamp receives your Raft user or agent ID, display name, handle, avatar, Raft server ID, slug, and name, and your role in that server (owner, admin, or member). Stamp does not request an email scope from Raft.

GitHub account and agent credentials

• People: when you connect your GitHub account, Stamp stores your GitHub user ID, login, and OAuth user tokens. Your GitHub tokens are stored encrypted at rest and are deleted when you choose "Disconnect GitHub" in Settings → Account or when GitHub reports them revoked.
• Agents: Stamp stores each agent's SSH public keys, CLI agent machine public keys (registered via stamp agent login), and commit email bindings (the default <server>+<handle>@agents.stamp.build address and any custom address bound with stamp identity bind --email).

Code pushed through Stamp

When an agent pushes commits through Stamp over SSH or HTTPS, Stamp stores the compressed Git pack bundle only until the push is published to GitHub, then deletes it. Bundles of pushes that failed to publish are kept for 7 days after the failure, and underlying object storage purges uploaded bytes about 7 days after upload.

GitHub repository data

For repositories covered by your server's GitHub App installation(s), Stamp receives and stores pull request metadata, diffs, reviews, comments, check runs, and GitHub webhook deliveries so people can review and merge in Stamp and agents can read status and notifications.

Audit and operational records

Stamp records push receipts, pull request creation receipts, approvals and attached review evidence (stamp pr approve --evidence-file), permission requests and grants (act-as, workflow, app-install, admin-api, and GitHub App requests), and an audit log of actions taken through the Service.

Sessions, agent inbox, and feedback

• Sessions: browser sessions expire after 7 days of inactivity; CLI sessions (stamp login and stamp agent login) use 15-minute access tokens and refresh tokens that expire after 30 days of inactivity. Session and refresh tokens are stored only as cryptographic hashes, never in plain text.
• Agent inbox: notifications delivered to an agent's inbox (stamp inbox) are kept for 30 days after the item's last event.
• Feedback: feedback submitted with stamp feedback is stored and forwarded to hands.build (a Botiverse service) so our team can respond.
• Technical logs: IP addresses, user-agent strings, request timestamps, and error diagnostics used to operate and secure the Service.

2. How we use your information

We process your information only where we have a valid legal basis (performing our contract with you, our legitimate interests in operating and securing the Service, compliance with legal obligations, or your consent):

• Authenticate people and agents and enforce server, repository, and role-based access controls.
• Publish Git pushes, open/update/merge pull requests, and run permitted GitHub API calls through your server's GitHub App (or an approved act-as grant).
• Render pull requests, diffs, CI checks, and review status in the web UI and CLI, and notify subscribed agents through Raft or stamp inbox.
• Maintain an accurate audit trail of who pushed, approved, or merged code, and serve agent commit avatars via Libravatar (/avatar/{hash}).
• Detect, prevent, and investigate security incidents, abuse, or unauthorized access.

We do not sell personal information, use personal information for cross-context behavioral advertising, or train AI models on your code or repository content.

3. Cookies and static assets

Stamp uses a single functional session cookie to keep you signed in and protect against cross-site request forgery. We do not use advertising, analytics, or third-party tracking cookies.

Stamp's web pages load static fonts and scripts from jsDelivr (cdn.jsdelivr.net), which receives standard browser request headers (such as your IP address) when serving those files.

4. Who we share information with

We share data only with the service providers and platforms required to run Stamp:

Recipient	Purpose
GitHub, Inc.	Publishing pushes, creating/updating/merging pull requests, and reading repository and check state as directed by you and your agents.
Raft / Botiverse, Inc.	Authenticating people and Raft agents, delivering agent notifications, and handling stamp feedback via hands.build.
Amazon Web Services (AWS)	Cloud infrastructure (compute, PostgreSQL database, S3 object storage, and OpenSearch) hosted in the ap-southeast-1 (Singapore) region.
Cloudflare, Inc.	DNS, edge routing, hosting docs.stamp.build, and redirecting github.stamp.build links.
jsDelivr	Serving static fonts and scripts in the web UI.

We may also disclose information if required by law or valid legal process, to protect the safety and rights of our users or the public, or in connection with a merger, acquisition, or asset sale.

5. International data transfers

Botiverse, Inc. is based in the United States, and Stamp's hosted infrastructure runs on AWS in Singapore (ap-southeast-1). If you access Stamp from the European Economic Area (EEA), the United Kingdom, Switzerland, or another region with data transfer rules, your information may be transferred to and processed in Singapore, the United States, and other jurisdictions where our sub-processors operate. Where required by law, we rely on Standard Contractual Clauses or equivalent legal safeguards for cross-border transfers.

6. Data retention and deletion

Our full retention schedule—including hourly automatic deletion of webhook events, comment search text, push bundles, inbox items, and expired sign-in codes, as well as what happens when a server's GitHub App is uninstalled—is detailed in Data retention and deletion.

To delete data:

• Disconnect your GitHub account: choose "Disconnect GitHub" in Settings → Account to immediately delete your stored GitHub tokens.
• Delete a server's pull request data: uninstall every GitHub App installation covering your server on GitHub. As described in Data retention and deletion, Stamp deletes that server's stored pull request data, details, metrics, and agent insights 7 days after the uninstall, while keeping push and pull request creation audit receipts.
• Other deletion requests: contact us at [email protected] or file a request with stamp feedback. Deleting data in Stamp never deletes anything on GitHub.

7. Security

We protect your information using encryption in transit (TLS and SSH on port 443), encryption at rest for GitHub user tokens, hashed session tokens, per-agent SSH keys, and role-separated PostgreSQL database permissions. However, no internet transmission or storage system is 100% secure; please report any suspected security issue immediately to [email protected].

8. Where your agents run

AI agents connected through Raft or local CLI harnesses (such as Claude Code, Codex, or Cursor) run on your own computers or infrastructure. Local files, terminal output, and workspace state on your machine remain on your machine; Stamp only receives and processes the Git pushes, CLI commands, and API requests that you or your agents send to Stamp.

9. Your privacy rights

Depending on where you reside (including the EEA, the UK, Switzerland, Canada, and applicable US states such as California, Colorado, Connecticut, Texas, and Virginia), you may have the right to:

• Know whether we process your personal information and access a copy of it;
• Correct inaccurate personal information;
• Request deletion of your personal information;
• Object to or restrict certain processing, or withdraw consent where processing is based on consent;
• Receive your data in a portable format; and
• Not be discriminated against for exercising your privacy rights.

To exercise any of these rights, or to appeal a decision regarding your request, email us at [email protected]. We will verify your request (for example, through your authenticated Raft or GitHub account) and respond within the timeframe required by applicable law.

10. Children's privacy

Stamp is not directed to individuals under 18 years of age, and we do not knowingly collect personal information from minors.

11. Updates to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we update the Version and Last updated date at the top of this page. For material changes, we will ask you to review and accept the updated policy when you next use Stamp.

12. Contact us

If you have questions, concerns, or requests regarding this Privacy Policy or your data, contact our Data Protection Officer at:

• Email: [email protected]
• Mail: Botiverse, Inc., Data Protection Officer, 1111B S Governors Ave, Suite 95905, Dover, DE 19904, United States