Skip to content
CloakPipe
DocsBlogChangelog
Star50Sign inSign upGet started →
DocsBlogChangelog
Star50Sign inSign upGet started →
Legal · Privacy

Privacy policy

Last updated 6 November 2026. Applies to cloakpipe.co, the hosted CloakPipe Cloud at app.cloakpipe.co and api.cloakpipe.co, and the sign-in service at auth.cloakpipe.co. The open-source gate you run yourself sends nothing to us.

Who we are

CloakPipe is operated by Rohan Sharma, trading as CloakPipe ("we"). Contact: rohan@cloakpipe.co.

What we collect

When you create an account

  • Email address, name and avatar, from the sign-in method you choose: Google, GitHub, or an email address with a password. Sign-in is handled by Logto, an open-source identity service that we self-host; it stores your credentials (password hashes, OAuth identity links) and session records.
  • Verification codes sent to your email address when you sign up or reset a password. These are delivered through Resend.

When you use the dashboard

  • Workspace data you create: gates, policies, approver seats, alert destinations (for example a Slack webhook), team invites and the roles of your teammates.
  • Events your gates send us: signed decision records (which tool was called, whether it was allowed, denied or escalated, and the argument fields your manifest marks as shareable). Argument values that your manifest does not mark as shareable never leave your gate.
  • Approval requests and receipts, when you route approvals through CloakPipe Cloud.
  • API keys you create, stored as hashes.

When you visit the website

  • Aggregate analytics (page views, referrer, browser, country) through a self-hosted Umami instance. Umami does not use cookies and does not identify you.
  • Waitlist and contact details you submit on purpose, such as an email address on the waitlist form.
  • Server logs with IP addresses and request paths, kept for a short time for security and debugging.

What we do not collect

  • The prompts, tool arguments or outputs of the agents you protect, unless your manifest explicitly marks a field as shareable or you send it to our proxy yourself.
  • Payment card numbers. If you buy a paid plan, payment is handled by Stripe, which holds your card details; we receive a customer id and the plan you bought.
  • Data from the open-source gate when it runs without a Cloud connection.

Why we use it

  • To run the service: sign you in, show your workspace, deliver alerts and approvals, enforce plan limits.
  • To keep it secure: verify signed events, detect abuse, investigate incidents.
  • To talk to you about your account: verification codes, invites your admin sends, service notices. We do not send marketing email unless you opt in.
  • To understand how the website is used, in aggregate.

We do not sell personal data and we do not use it to train models.

Who processes it for us

ProcessorWhatWhere
Hostinger (our own server)CloakPipe Cloud, Logto sign-in, Umami analyticsIndia (Mumbai)
VercelThis websiteGlobal edge, origin US
Google, GitHubSign-in, only if you choose themUS
Resend (Amazon SES)Transactional emailUS
StripePayments for paid plansUS / EU
Slack, Discord, PagerDutyAlert delivery, only to destinations you configurePer provider

How long we keep it

  • Account and workspace data: until you delete your account or ask us to.
  • Gate events and issues: for the retention period of your plan (7 days on Free, longer on paid plans), then purged automatically.
  • Verification codes: 10 minutes.
  • Server logs: up to 30 days.

Your rights

You can ask us to show you, correct, export or delete the personal data we hold about you, and you can object to or restrict how we process it. Email rohan@cloakpipe.co from the address on your account and we answer within 30 days. If you are in the EU or UK you can also complain to your data protection authority.

To stop using Google or GitHub sign-in, revoke CloakPipe's access in your Google account or GitHub settings; your CloakPipe account stays until you delete it.

Cookies

app.cloakpipe.co and api.cloakpipe.co set strictly necessary cookies to keep you signed in (a sealed session cookie and a short-lived sign-in state cookie). auth.cloakpipe.co sets a session cookie for the same purpose. This website sets none; your theme choice is kept in your browser's local storage.

Children

CloakPipe is not directed at children under 16 and we do not knowingly collect their data.

Changes

We update this page when our practices change and note the date at the top. Material changes are announced in the dashboard or by email.

CloakPipe

Policy enforcement for AI-agent tool calls. A self-hosted, MIT-licensed gate: model proposes, code disposes.

Product

Get startedMCP tool gateEvidence & verificationHosted alerts & approvals

Developers

DocumentationIntegrationsFAQ & limitationsChangelogGitHub

Company

BlogDesign partnersContactPrivacyTerms
© 2026 · CLOAKPIPE · MIT OPEN-SOURCE COREGITHUBCLOAKPIPE.CO