Privacy Notice
How Tinplate handles requests, zero-logging isolation, and optional edge caching.
1. Zero Payload Logging & Stateless In-Memory Processing
Tinplate APIs inspect and process request payloads strictly in volatile V8 isolate memory on Cloudflare Workers for the duration of the HTTP request and immediately discard them. We never log, store, sell, or retain request bodies, response bodies, signing secrets, PII, HTML, emails, or tokens.
2. 100% Tracking-Free, Ad-Free & Zero-Payload Telemetry
Cloudflare Workers Observability and Invocation Logs are explicitly disabled (observability.enabled = false, head_sampling_rate = 0, invocation_logs = false) across Web, Gateway, and Fetcher Workers:
- Anonymous Aggregate Metrics Only: Analytics Engine records only
apiId,plan,authProvider,method,sizeBucket,ms,status, andbodyBytes—never IP addresses, headers, keys, or payloads. - No Invocation Logs, Logpush, or Third-Party Cookies: Worker invocation logging and Cloudflare Logpush (
logpush = false) are disabled, with zero third-party trackers, ad pixels, cookies, or third-party font/script CDN requests. - One-Way Hashed Counters Only: Rate-limit buckets (
RATE_LIMITER, failed Bearer throttling, per-key Polar RPM) and D1polar_usagestore salted/keyed SHA-256 prefixes only. KV rate-limit buckets expire within60–120 s, Polar validation caches for300 sinpolar:lk2:<hash>(evicted immediately onPOST /portal/erase), and D1polar_usageauto-purges after 13 months. - Polar Key Cache & CORS: Authenticated
/v1/*endpoints are server-to-server and omit browser CORS headers;/free/*limits CORS strictly to site origins.
3. Marketplace Proxy Infrastructure vs. Direct Bearer-Key Access
- Requests via RapidAPI or Zyla API Hub: Requests traverse that marketplace's proxy before reaching Tinplate under their privacy policies.
- Direct Bearer-Key Access: Customers requiring zero intermediary proxies can use a Direct Bearer Key straight to
https://api.tinplate.dev. Note: Standard plans do not execute a HIPAA Business Associate Agreement (BAA); do not submit unredacted PHI.
4. Short-Lived Public Caching, Outbound Lookups & Optional Workers AI
- Public Cache Only: Public EU VIES lookups and URL-fetched Markdown conversions (unless
cache: false) may cache briefly in KV; raw POST inputs and secrets are never cached. - Optional Outbound Lookups: Disabled on keyless
/free/*,/demo/*, and/mcp. Paid flags (verify_vies: true,check_mx: true,check_dns: true) transmit only the queried domain/VAT/URL. - Optional AI Judge (
use_ai_judge: true): Disabled by default. When enabled, PII/secrets are redacted before internal Workers AI inference. - Billing Data: Handled by Polar Software, Inc. (Merchant of Record), RapidAPI, or Zyla; Tinplate never touches card details.
5. Sub-Processors, Retention & Data Controller Rights (GDPR)
Because Tinplate stores zero payloads and no user profiles, GDPR access/erasure primarily applies to hashed polar_usage counters (13-month auto-purge; prior-month erasure via /portal). See Standard DPA, Incident Response SLAs, or Support.
| Sub-Processor | Purpose | Data Touched |
|---|---|---|
| Cloudflare, Inc. | Workers compute, KV cache, D1 polar_usage, Analytics Engine, optional Workers AI | Ephemeral payloads in RAM, hashed quota counters, non-PII latency aggregates |
| Cloudflare 1.1.1.1 DoH | Optional live DNS/MX/SPF/DMARC/DNS-rebinding lookups | Target domain / hostname only (when caller enables live DNS) |
| European Commission (VIES) | Optional live EU VAT registration lookup (verify_vies: true) | Country code + VAT number only |
| Polar Software, Inc. | Merchant of Record & Direct Bearer license validation | Checkout billing details (held by Polar) and SHA-256 key validation |
| RapidAPI / Zyla API Hub | Marketplace proxy & billing (marketplace callers only) | API traffic & subscription headers if called via marketplace proxy |