Privacy Policy
Effective 2026-08-21
What Rendershed does with data, in plain terms. The summary is that there is very little of it: no cookies, no analytics, and no account beyond what Stripe hands us when you pay. See also the terms of service.
1. Who we are
Rendershed operates rendershed.com and the API at shots.rendershed.com, from the Republic of Lithuania. For anything in this policy, including a request to see or delete your data, use the support address at the bottom of this page.
2. The short version
This site sets no cookies, runs no analytics, and carries no third-party tracking of any kind. There is no signup form, no password and no profile. We hold an email address because Stripe gives us one when you pay, and counters so we can enforce a quota. That is close to all of it.
3. What we process
Your email address and plan, passed to us by Stripe when you subscribe, along with the Stripe customer and subscription identifiers. A SHA-256 hash of your API key together with a short public key id — never the key itself. Per-day counts of how many renders a key has made. Your IP address, briefly, where you call the API without a key, because the anonymous tier is metered per address and there is nothing else to meter it against.
4. The URLs you render
A render is keyed in the cache by a SHA-256 hash of its parameters, not by the URL in readable form, and the application does not write the URLs you request to its logs. The rendered image itself is stored so the same request can be served from cache, and it is discarded when the cache entry expires or is evicted. If a page you render happens to contain personal data, that data is in the image for as long as the image is cached — send cache_ttl: 0 and the render is never written to disk at all. Note that fresh: true is not the same thing: it skips reading the cache but still stores the result.
5. The public demo
The demo on the landing page runs without a key and shows a short list of recently rendered sites, so visitors can see it is live. That list holds hostnames only — never a full URL, never a path or query string, and nothing tying a hostname to whoever rendered it. Do not put anything confidential through the public demo; use a key.
6. Server logs
Our web server keeps ordinary access logs — address, timestamp, request line, status and user agent — which we use to investigate abuse and outages. They rotate on a short cycle.
7. Why we are allowed to
Contract, for everything needed to give you the service you are paying for and to bill you. Legitimate interest, for rate limiting, abuse prevention and keeping the service standing up. Legal obligation, for the tax and accounting records an invoice creates. We do not rely on consent, because we are not doing anything that needs it.
8. What we do not do
We do not sell or rent personal data, we do not share it for advertising, we do not build profiles, and we do not use what you render to train anything.
9. Cookies
None. The light and dark setting is kept in your browser's local storage, which never leaves your device and is not sent to us.
10. Who else touches it
Stripe, for payments, billing and the customer portal — it takes the payment and holds the card, and its own privacy policy governs what it keeps. Hetzner, for hosting, in the EU. Cloudflare, in front of the site for DNS, TLS and abuse protection. That is the whole list.
11. Where it is
The service runs in the EU. Some processors are US-headquartered and may process data outside the EEA; where they do, EU Standard Contractual Clauses or an equivalent safeguard applies.
12. How long we keep it
Only as long as the purpose needs, or as long as the law requires. Address-based rate limiting is short-lived by design and expires on its own. Account and usage records last while your account does. Invoices are kept for the statutory accounting period. Ask us to delete your account and we will, apart from what tax law requires us to keep.
13. Your rights
Under the GDPR you can ask for access, correction, erasure, restriction, portability, or object to processing based on legitimate interest. Write to the support address and we will answer within a month. You can also complain to the Lithuanian supervisory authority, the State Data Protection Inspectorate (VDAI), or to the authority where you live.
14. Children
This is a developer tool and it is not directed at anyone under 16.
15. Changes
We may update this policy. The current version is always posted here with its date.
Contact
Write to . Billing questions are usually faster through the billing portal, which shows your invoices and lets you change or cancel a plan yourself.