Trust & Security Center
At LLMFence, security is our foundational principle. Learn how we protect your proprietary data and AI pipelines.
What happens to your text
Text you send is held in memory for the duration of the request and is not written to our database. What we store per call is metadata — which key, when, the risk score, whether it counted as overage — and never the text itself.
It is, however, transmitted to Google's Gemini API, which performs the analysis. There is no version of this service in which that does not happen, so treat any text you send us as text you have sent to Google. Requests answered by the deterministic scan or the short-lived verdict cache never reach a model at all; the X-LLMFence-Source header on every response tells you which happened. Full detail is in the privacy policy.
Encryption Standards
All data in transit is secured using TLS. Retained metadata is encrypted at rest by our infrastructure providers — Supabase for the database and Vercel for compute — and API keys are never retained in a recoverable form at all: only a SHA-256 hash is stored, so a key cannot be read back out of our database by anyone, ourselves included.
Row-Level Security (RLS)
Every table enforces PostgreSQL row-level security, so a query for another account's keys, usage or policies returns nothing — the isolation is enforced by the database itself rather than by application code remembering to filter. Default privileges are revoked on every table, and the columns a customer may write are granted individually: your plan, your usage counter and your Stripe identifiers are not among them.
To be precise about what that is and is not: this is enforced isolation, not encryption. Your rows are not encrypted under a key only you hold, and we do not claim they are.
Reporting a vulnerability
If you find a security problem, tell us through the contact page and put "security" in the message. We will confirm receipt and keep you updated while we fix it. Please give us a reasonable chance to ship a fix before publishing, and do not access, modify or retain data belonging to anyone else while investigating — testing against your own account is always fine.