--- title: "Trust & Security" description: "How EnConvert earns your trust: render-quality honesty, SSRF screening, key handling, signed webhooks, auditable billing, plain-English data handling, and continuity commitments from two named, reachable founders. Written for engineers, not lawyers." canonical: "https://www.enconvert.com/trust" locale: "en" --- Trust & security · last updated 25 July 2026 # You're about to depend on us. Here's why that's safe. Built and run by two founders, Het and Om. This page is everything we would want to read before making a small, unknown API a production dependency — every claim points at its mechanism, and where we fall short we say so here first. Receipts [status.enconvert.com ↗](https://status.enconvert.com)[/changelog](/changelog.md)[/docs](/docs/introduction.md)[/privacy](/privacy.md)[/terms](/terms.md)[security.txt ↗](/.well-known/security.txt) 01 The honesty contract ## Most scrapers lie to your agent. Ours files a report. The failure that scares every AI engineer isn't the crash — it's the silent lie a customer finds first. The core of EnConvert is a refusal to do that. Every read is scored, 0.0 to 1.0 ⌄ A blocked page is named, not hidden ⌄ We don’t spend your money on a page that beat us ⌄ Reserved paths return 422, never a silent 200 ⌄ The honest limits of this - · 92% catch rate, 4% false alarms on our 50-page labeled corpus — roughly 1 in 12 block pages can still slip through, and we publish the misses. - · /v2/ingest renders pages but doesn’t gate on the score yet, so a blocked page can enter a RAG corpus unflagged; that gate is roadmap, not done. - · A low score flags and warns — it doesn’t block delivery or refund the call, and it never silently withholds your content. 02 Operational transparency ## Here is exactly what happens to your data. No abstractions — two flows cover almost everything EnConvert does. A file you upload A URL your agent reads (V2) 1. 01 Arrives over TLS 2. 02 Checked against your plan’s size limit and accepted extensions 3. 03 Filename sanitized — path components and traversal sequences stripped 4. 04 Bytes held in memory, passed straight to the converter — your source file is never written to our storage 5. 05 Only the converted output is stored, private, under your account’s own key prefix 6. 06 Downloaded via a pre-signed URL: 15-minute expiry, ownership-checked before signing 7. 07 Deletable by you, at any time Retention notes — what we keep, and the opt-out header ⌄ 03 Security ## No badges. Mechanisms. We can't hand you a SOC 2 report — so here are the specific controls it's a proxy for, including where each one stops. SSRF screening on V2 endpoints ⌄ API keys and access ⌄ Webhooks you receive ⌄ Billing you can audit ⌄ Keep sk\_ keys server-side Use a pk\_ key, locked to your domains, for anything client-side — browsers reject sk\_ on purpose. Verify webhook signatures Recompute HMAC-SHA256 over ., compare in constant time, reject anything older than 5 minutes. Scope your keys A key restricted to the one endpoint it needs can’t do anything else if it leaks. Rotate on exposure Rotate a secret or revoke and re-create a key the moment you suspect exposure — revocation is immediate. Your side of the fence — four things that keep your account safe 04 Reliability ## Receipts, not promises. What is actually built, what is actually tested, and honest answers to the failure simulations you're already running in your head. A restart never strands your job ⌄ One bad input fails only itself ⌄ A monitor that goes blind tells you ⌄ The safety behaviors are the ones we test ⌄ [status.enconvert.com](https://status.enconvert.com) · monitored since 29 June 2026 — four honest weeks beat a fabricated year What happens when you have an outage? ⌄ What happens when a founder is unavailable? ⌄ What happens when your traffic spikes? ⌄ What happens when EnConvert shuts down? ⌄ 05 Your data ## What we will never do with your files. - We never train models on your files or your content - We never sell or share your data - Source files are processed in memory, never stored — only your converted output is, under your prefix, deletable by you - Downloads are private and time-boxed: signed URLs, 15-minute expiry, ownership-checked before signing Every subprocessor, named DigitalOcean Spaces ⌄ Anthropic, PBC ⌄ OpenAI OpCo, LLC ⌄ Google LLC ⌄ Serper ⌄ PayPal ⌄ 06 Honest fit ## Reasons not to use EnConvert. Every honest pitch includes the cases where it's the wrong call. Here are ours. You need SOC 2 or HIPAA attestation today We don’t have them. If a certificate is a hard procurement gate, we’re not there yet. You need a contractual 99.99% SLA with penalties A two-person company cannot honestly write that — use a larger vendor. You need on-prem or self-hosting Not offered; EnConvert is a hosted API only. You process very large files Per-plan size caps run from small on Free up to the Production tier — past that, wrong tool. A tiny team is a dealbreaker Legitimate. Everything on this page is designed to make it a smaller risk than it sounds, but we won’t pretend it’s zero. 07 Accountability ## Two names. Reachable. Bootstrapped, no investors — revenue is subscriptions only, so the product's only job is to keep working for the people paying for it. Support is answered by the people who wrote the code. Het Dave Co-founder [het@enconvert.com](mailto:het@enconvert.com) Om Co-founder [om@enconvert.com](mailto:om@enconvert.com) ## Don't trust this page. Check it. Run 100 operations on the free tier, point /v2/perceive at a page you know is hard, and read the score it gives back. Free while in beta — no credit card. [status.enconvert.com ↗](https://status.enconvert.com)[/changelog](/changelog.md)[/docs](/docs/introduction.md)[/privacy](/privacy.md)[/terms](/terms.md)[security.txt ↗](/.well-known/security.txt) [Get a free API key](/auth?mode=signup)[Read the docs](/docs/introduction.md) support@enconvert.com · security reports answered within a business day