AIPWN / TRUST & PRIVACY DIRECTIVES
Privacy Policy
AIPwn separates browser-local tools from optional cloud inspection and documents what each path sends and retains.
Last updated
Local and cloud paths
C2PA credential inspection runs in your browser and does not send the selected image to AIPwn. Cloud inspection sends the submitted bytes to AIPwn, which reads the provenance metadata embedded in the file; no third-party detection provider receives them.
Cloud report retention
AIPwn does not persist raw cloud inputs or source URLs. Reports retain the input SHA-256, byte size, media type, the provenance findings, and a report-evidence digest.
Agent Security evaluations
Agent Security requests are processed by AIPwn and a configured semantic-analysis provider (TypeSafe). Well-formed secret literals are masked before the redacted content is sent; AIPwn persists only the input digest, decision, risk codes, policy and model versions, and charge metadata — never raw prompts, tool arguments, outputs, or traces. AIPwn's zero-raw-retention commitment covers AIPwn storage, not the provider's own processing and retention terms.
Evaluation feedback
You can label one of your own evaluations as a false positive, false negative, or correct from the Console or the API. A short note may accompany the label. If you explicitly opt in, a sample you paste (up to 8 KB) is stored separately from evaluation metadata, kept for at most 90 days, used only to correct rules and policy thresholds, and deleted with your account. Feedback never includes evaluation input unless you paste it yourself.
Service providers
Cloudflare hosts the site, API, and account database. TypeSafe processes redacted Agent Security inputs for semantic signals; its own retention terms are separate from AIPwn's. Stripe handles checkout and billing details when you top up. Google or GitHub supplies account profile data when you choose that sign-in provider. Google Analytics receives optional site analytics only after consent and is disabled on the detector, Console, and report routes.
Authentication data
Google and GitHub sign-in stores the provider identifier, verified email, display name, and avatar needed for the account. The requested scopes do not include Google Drive, personal messages, or private repository contents.
Cookies and optional analytics
A HttpOnly session cookie maintains sign-in; a separate language cookie and local preferences are readable by the browser. Google Analytics loads only after explicit consent and is disabled on the detector, Console, and report routes. Global Privacy Control is honored. Public pages also report aggregate page-load measurements to Cloudflare Web Analytics, which sets no cookies and does not identify visitors; it is blocked on the same detector, Console, and report routes.
Export and deletion
The Console can export account metadata, reports, API-key metadata, and the credit ledger. Account deletion removes local reports, keys, sessions, and ledger data and deletes the linked Stripe customer before local deletion when a billing profile exists.