What we collect, why, and what we never see.
Last updated August 2, 2026
Permisyn is an authorization and evidence layer that sits in front of your AI provider calls — it decides whether a call is allowed to reach OpenAI, Anthropic, or another provider, and produces a signed record of that decision. This policy explains what personal and account data we collect to run that service, and — because the product's whole premise is that our claims should be checkable — we’ve been specific rather than vague about what actually happens to the content of your AI calls.
Information we collect
Account information. Name, email address, organization name, and password (stored hashed, never in plain text) when you sign up. If you sign up with Google or GitHub, we receive the email and name your OAuth provider shares.
Billing information. Payments are processed by Stripe. We do not receive or store your card number — Stripe shares back a customer ID, subscription status, and plan so we can enforce the entitlements you’re paying for.
AI call metadata — not the content, by default. Every proxied call generates a signed receipt containing the model, provider, token counts, cost, duration, and the allow/deny decision and why. The prompt and the model’s response are not stored or included in this receipt by default. If you explicitly opt in (via a request header your own integration sends), we store a truncated preview of the prompt — capped at 4,000 characters — for your own debugging visibility; that preview is never part of the signed, publicly verifiable receipt and is never returned by the public verification endpoint. Outside of that opt-in preview, we do not log the content of your prompts or completions.
Your AI provider keys. Permisyn supports two modes. In vaultless mode (the default we recommend), you send your own provider key with each request; we use it only to make that one upstream call and never write it to a database — it is not stored. Because Permisyn is the one placing the call to your provider on your behalf, the key does pass through our server process for that single request; "not stored" is an accurate description, "never touches our infrastructure" would not be. In vault mode, you may instead store a provider key with us for convenience; it is encrypted at rest and decrypted only at the moment of an upstream call, never written back to any log or record.
Support communications. If you send us a report or request through the dashboard, we store the message (and any screenshot you attach) so we can reply and so you can see the history. Internally, a copy of the report is also forwarded to our own team notification channel so it gets seen promptly.
Technical data. Standard request metadata (IP address, timestamps, user agent) is processed transiently for rate-limiting, abuse prevention, and debugging.
How we use information
- To operate the authorization and proxy service — resolving identity, enforcing your passports and limits, and producing signed receipts.
- To bill your account according to the plan you’ve chosen.
- To respond to support requests and, where you’ve requested it, to schedule a call.
- To detect abuse and keep the shared service available for every customer.
- To send you account, billing, and — where relevant — security notifications. We do not sell your data or use it for third-party advertising.
Data retention
Your plan determines how far back you can view and query your own history in the dashboard (currently 7 days on Free, 90 days on Team, 365 days on Business, and unlimited on Enterprise) — but that is a viewing window, not an expiry. Signed receipts are retained indefinitely and stay independently verifiable, because a piece of evidence that could quietly disappear would not be trustworthy evidence. Upgrading your plan immediately widens what you can see; it does not create new data, since none of it was ever removed.
Deleting your data
We do not yet have a fully self-service "delete my account" button in the product. If you want your account and associated data deleted, email us at amitcool5115@gmail.com and we will process the request directly. Note that signed receipts already anchored into the public transparency log exist there specifically so they cannot be quietly altered after the fact — deleting your account stops new data from being generated and removes your access to it, but a receipt that was already publicly anchored is, by design, not something anyone (including us) can silently erase from that log.
Who else sees data, and why
We use a small number of subprocessors to run the service. None of them receive your AI prompt or response content:
- Stripe — payment processing.
- Resend — transactional email (account, billing, and notification emails).
- Microsoft Azure — application hosting and database.
- Vercel — hosting for this website and dashboard.
- Cal.com — scheduling, only if you book a call with us.
- Slack — internal notifications when you contact support, and for any outbound alert webhook you configure yourself.
- OpenTimestamps / Bitcoin timestamping services — receive only a one-way cryptographic hash of our transparency log, never any customer data, used to anchor the log’s integrity publicly.
- Your own configured AI providers (OpenAI, Anthropic, or others you point Permisyn at) receive your prompts and responses directly, exactly as they would if you called them without Permisyn in between — that traffic is between you and the provider you chose, under that provider’s own terms.
We do not sell personal data to third parties, and we do not use analytics or advertising trackers on the dashboard.
Security
See our dedicated Security page for how receipts are signed, how keys are encrypted, and how account access is controlled.
Children’s privacy
Permisyn is a business tool and is not directed at, or knowingly used by, children. We do not knowingly collect information from anyone under 18.
Changes to this policy
If this policy changes materially, we’ll update the date above and, for significant changes, notify account owners by email.
Contact
Questions about this policy or your data: amitcool5115@gmail.com.