Privacy

What is stored, and for how long

Token hash

Your sign-up token is shown once. RenderSwap keeps only its SHA-256 token hash and never the token. A copy of your domain list sits in a cache under that hash for 5 minutes. The hash stays while the account exists.

Account id and date

A random account id and the date the account was created.

Campaign tag

If you arrived through a link with a campaign tag, the campaign tag is saved with your account. It is up to 40 lowercase letters, digits and hyphens, and it names the link, not you.

Pro link

Once you activate a Pro key, your account points at the Pro record described below.

Verified domains

Each domain you add, the date you added it and the date it was verified. A pending domain is stored the same way until you remove it.

DNS check values

The random DNS check value you publish in a TXT record, the time of the last check, and the number of checks in a row that missed it.

Cache settings

Each domain's cache lifetime, from 1 to 30 days, and a cache generation number that a purge raises.

Copies of public pages

A rendered copy of each public page a crawler asked for, kept up to the cache lifetime of its domain, from 1 to 30 days. A purge stops the copies being served at once, and the nightly sweep deletes them.

Failing URLs

The address of a page that failed to render, cut at 512 characters, with the reason, how many times it failed and when it last failed. Failing URLs are kept 30 days after the last failure, then deleted.

Daily counts

For each domain and each UTC day: cache hits, renders attempted, pages rendered, timeouts, renders a site blocked, other failures, requests handed back to your origin because of a cap, and browser milliseconds. The daily counts hold numbers only, no page address, and they stay after you remove a domain.

Usage counters

For each account and each UTC month: the renders started and the browser milliseconds used, measured against the plan's allowance.

Render leases

One short row per render in flight, with your account id and an expiry time. A render lease frees itself when the render ends or runs out.

Paddle ids

For a Pro purchase, the Paddle subscription id and the Paddle customer id, plus the subscription's status and end date. They come from Paddle's events and stay while the subscription record exists.

License key

The license key you activate, so it can be renewed, with its plan, its expiry date, the date it was first activated, whether it was issued for sandbox or live, and the dates it was last renewed and lapsed.

What is not stored

Sign-up asks for no email address. It asks for no name and no card number either, so RenderSwap holds no way to write to you except what you send it.

RenderSwap does not store crawler IP addresses or User-Agents. The counts above are numbers, and the failing URLs are page addresses on your own domains.

The renderer sends no cookies to your site. The dashboard sets one cookie, rs_session, to keep you signed in for 7 days. It goes only to the RenderSwap API.

Who else handles data

Paddle handles payment and holds your card details. RenderSwap never sees them. The license Worker sends the key email after you buy.

Cloudflare runs the service. The database, the cache of page copies and the queue of background work all sit on Cloudflare.

Questions, or a request about your data: write to hello@brightlabs.app.

The full texts at brightlabs.app