renderFy

Security & Privacy

Your data passes through. It doesn’t stay.

Renderfy is a stateless rendering engine. You send content, we return a PNG, JPEG, WebP, or PDF, and the input is gone. That’s the whole design — which makes it a comfortable fit for invoices, reports, and documents built from data you’d rather not hand to a third party.

Stateless by default

The HTML, Tailwind, Markdown, or data you send is rendered in memory and discarded when the response is returned. We keep render metadata (type, format, credits, duration) for billing and history — never the content itself.

Encrypted in transit

Every request is served over TLS. The API only accepts HTTPS, and the dashboard runs behind the same encrypted connection.

API keys are hashed

We store only a SHA-256 hash of your API key. The plaintext is shown once at creation and is never recoverable from our side — a database leak can't expose a usable key.

Scoped database access

Every table is protected with row-level security, so an authenticated session can only ever read its own account's rows. The rendering path uses a separate, tightly-scoped service role.

What we store

  • • Your email address (for sign-in)
  • • Render metadata: type, format, credits, duration, status, time
  • • A one-way hash of your API key
  • • A one-way hash of guest IPs (playground rate-limiting only)
  • • Templates you explicitly choose to save

What we don’t

  • ✕ The content you render
  • ✕ The output images/PDFs we generate*
  • ✕ Variable data you pass into a template at render time
  • ✕ Raw IP addresses
  • ✕ Your plaintext API key or password

* The one exception, and it’s opt-in

If you send an Idempotency-Key header, we briefly retain that single rendered output so a retry can return the same result without charging you twice. That copy is encrypted at rest, used only for replay, and automatically deleted after a short window (24 hours by default, configurable). Don’t send the header and nothing is retained. We’d rather tell you exactly how this works than pretend the trade-off doesn’t exist.

EU-based processing

Rendering is stateless — your content is never stored — and the only data we retain lives in a managed database hosted in the EU. For EU customers, that means your account data stays within the EU rather than being shipped across the Atlantic.

GDPR

We collect as little as possible, and you can access, export, or delete your data at any time. The specifics — controller, processors, retention, and your rights — are in our Privacy Policy.

What we don’t claim

We are not currently HIPAA-certified and don’t offer a BAA, so Renderfy isn’t the right tool for protected health information today. If you have a specific compliance requirement, talk to us first rather than assuming — we’d rather scope it honestly than oversell.

Reporting a vulnerability

Found something? Email [email protected] with the details. We read every report and will work with you in good faith to confirm and fix it.