Privacy Policy

Last updated: April 11, 2026

This document describes what data ClawPipe collects, how it is used, and what choices you have. It applies to clawpipe.ai, app.clawpipe.ai, api.clawpipe.ai, docs.clawpipe.ai, play.clawpipe.ai, and the clawpipe-ai SDK packages.

TL;DR. We don't log prompt or response content. We store the minimum account data required to run the service. Your provider API keys are encrypted at rest. You can delete your account and all associated data at any time.

1. What we collect

Account data

Email address (required for sign-in).
Display name (optional, shown in the dashboard).
Password hash (argon2id). We never see or store the plaintext password.
OAuth provider IDs if you sign in with Google or GitHub.

Project and usage data

Project names and settings you create.
API key hashes (SHA-256). Plaintext keys are shown once on creation and never stored.
Per-request metadata: timestamp, provider, model, token counts, latency, cost, cached/boosted flags, and an opaque prompt hash used for cache lookup.

What we do NOT collect

Prompt text, response text, or any LLM message content.
IP addresses beyond transient use for rate limiting.
Tracking pixels, ad-tech, or cross-site cookies.

2. Provider credentials

If you bring your own provider API keys (OpenAI, Anthropic, Groq, etc.) through the gateway, those secrets are stored encrypted at rest in Cloudflare KV and are only decrypted at request time to forward the call. ClawPipe staff do not have access to plaintext provider keys. You can rotate or remove them from the dashboard at any time.

3. How we use your data

To operate the service — authenticate you, route your requests, show your analytics.
To enforce tier limits and prevent abuse.
To debug issues (aggregate metrics only — no prompt content).
To contact you about your account, security, or major service changes.

We do not sell your data. We do not share your data with third parties for marketing or advertising.

4. Subprocessors

We use the following subprocessors to run the service. Each operates under its own privacy terms and signs a DPA with us where applicable.

Provider	Purpose	Data
Cloudflare	Hosting, DNS, KV, D1, Workers	All service data
LemonSqueezy	Payments and subscription billing	Email, billing details
OAuth providers (Google, GitHub)	Optional sign-in	OAuth profile ID and email

5. Data retention

Account data: retained until you delete your account.
Request metadata: 90 days rolling window for free/pro tiers, configurable for team/enterprise.
Auth and session data: session cookies expire after 30 days of inactivity.
Payment records: retained as required by tax and accounting law (typically 7 years).

6. Your rights

Access. Export your account data at any time from the dashboard.
Correction. Update your name, email, and project settings directly.
Deletion. Delete your account and all associated data from account settings or by emailing [email protected].
Portability. Your data is yours — export as JSON from the dashboard.
GDPR / CCPA. If you are in the EU, UK, or California, you have additional statutory rights. Contact us to exercise them.

7. Children

ClawPipe is not directed to children under 16. We do not knowingly collect data from children.

8. International transfers

ClawPipe runs on Cloudflare's global edge network. Your data may be processed in any region where Cloudflare operates. We rely on standard contractual clauses for transfers out of the EU/UK where applicable.

9. Changes to this policy

We will update this page when our practices change. Material changes will be announced via email to account holders at least 30 days in advance.

10. Contact

Privacy questions: [email protected]
Data deletion requests: [email protected]