Privacy Policy

protectwith.ai is built to be private by design. We do not run advertising, we do not use analytics or tracking, and the public site sets no tracking cookies. This policy explains exactly what is — and isn't — collected.

What we don't do

The live demo (/api/demo)

When you run the on-page demo, the text you submit is sent to our guardrail for analysis and the decision is returned to your browser. We do not store your raw text: the guardrail's audit log records only a SHA-256 hash of the input plus non-identifying metadata (which detectors fired, the decision, latency). Your input is never used to train any model.

Public MCP server & APIs

Like any web service, our infrastructure (Cloudflare) processes standard request metadata — IP address, timestamp, and request details — to operate the service, enforce rate limits, and protect against abuse. This is transient operational data, not a user profile, and is not sold or shared.

Cookies

The public site (protectwith.ai) sets no cookies. A small localStorage flag remembers that you dismissed the privacy notice — it stays in your browser and is never transmitted. The authenticated endpoints (mcp.protectwith.ai, the guard dashboard, the agent) are protected by Cloudflare Access, which sets a session cookie used solely for authentication.

Third-party services

Your rights (GDPR / CCPA)

Because we don't build user profiles, there is little personal data to access or delete. If you have any privacy question or request, email burademirung@gmail.com and we'll respond.

Changes

We may update this policy; material changes will be reflected by the "last updated" date above.

Contact

Questions: burademirung@gmail.com · Source: github.com/burademirung/protectwithai