Security & data handling
A plain-language explanation of how UnblockingAPI handles the pages you fetch, what we store about your account and requests, and how that data is protected. For the full legal detail, see our Privacy Policy.
Response bodies aren't persisted
Rendered HTML is held in memory only, gzipped, and returned to you in the same request. Nothing is written to disk.
Metadata only, never content
We keep what's needed to bill and debug - timestamps, status codes, target URLs - not the pages themselves.
Encrypted in transit
All API and dashboard traffic is served over TLS.
Card data never touches us
Billing runs through Stripe. We never see or store full card numbers.
1. Response data
When you call /unblock, the page we fetch - and the HTML we hand back to you - is never written to a database or disk.
The response body is held in memory for the duration of your request, compressed and streamed straight back to you as the API response. Once the request completes, it's gone. We don't keep a searchable archive of pages our customers have fetched, and we can't retroactively hand your scraped content to anyone because we never had a copy of it.
This applies to every request, whether or not JavaScript rendering was used.
2. What we do store
To run the service, bill correctly and help you debug, we keep metadata about each request - not its content. That includes things like:
- the target URL or domain you requested
- timestamp, status code and response time
- which API key and plan the request was made under
- routing details such as country/location and whether rendering was used
This is the same data described in more detail in our Privacy Policy. It's what powers your usage dashboard and lets us investigate a failed request - the actual HTML body isn't part of it.
3. Encryption & access
All traffic to the API and dashboard - including requests, responses and your API key - is encrypted in transit over TLS. Nothing is served over plain HTTP.
Access to production systems is limited to the engineers who operate the service.
4. Payments
Billing and card payments are handled entirely by Stripe. When you subscribe to a plan, your card details go directly to Stripe's PCI-compliant systems - we never see, process or store your full card number.
We keep billing metadata such as your plan, subscription status and invoice history, which is what's shown in your dashboard.
5. Reporting a vulnerability
If you believe you've found a security issue in UnblockingAPI, please tell us before disclosing it publicly. We take reports seriously and will work with you to understand and fix the issue.