Legal document

Cookie Policy

This policy explains what cookies are and how Renderly uses them. The short version: a single essential cookie to keep you signed in, and no third-party trackers by default. No consent banner for advertising, because there is no advertising.

Effective date: June 15, 2026Version: 1.0 (Beta)

01What cookies are

Cookies are small text files that a website saves in your browser when you visit it. They allow the site to "remember" information between requests — for example, that you are already logged in — since the HTTP protocol, on its own, does not retain that state.

Cookies can be session cookies (deleted when you close the browser) or persistent cookies (they remain for a defined period). They can also be first-party cookies (set by the domain you are visiting) or third-party cookies (set by another domain, usually for advertising and cross-site tracking). Similar technologies include localStorage, sessionStorage and tracking pixels.

02Which cookies Renderly uses

Renderly takes a minimalist approach: we use only what is strictly necessary for the service to work. Today, that means a single cookie:

Update (Jun 2025): for first-party product analytics (understanding usage to improve), we also use two of our own cookies — no third-party trackers or ad networks:

rnd_anon — first-party anonymous id (no PII), 1 year.
rnd_consent — stores your consent choice (analytics on/off), 1 year.

You control this via the consent banner and in Settings → Privacy & data (including turning analytics off).

renderly_sessionEssentialhttpOnly

Keeps you authenticated across the dashboard pages after login. It is a first-party and httpOnly cookie — meaning it cannot be read by JavaScript in the browser, which reduces the risk of session theft by malicious scripts (XSS). It travels over TLS and has security attributes (Secure and SameSite).

03No third-party trackers by default

By default, Renderly does not install third-party tracking cookies, does not display advertising, and does not sell data. We do not use ad-network pixels or marketing cookies to profile you across sites.

Some sub-processors may set their own cookies only in the context of the function they perform — for example, Stripe may use cookies in the payment flow for fraud prevention and checkout operation. These cookies are triggered when you interact with that specific feature, and not to track you across other sites. The full list of sub-processors is on the Securitypage.

Should we adopt usage analytics or transactional email in the future, this policy will be updated beforehand, with a description of the cookies involved and their purposes.

04Cookie table

Full list of cookies set by Renderly in this version:

Name	Type	Purpose	Duration	Attributes
`renderly_session`	Essential · First-party	Authentication and session maintenance in the dashboard.	Session	`httpOnly`, `Secure`, `SameSite`

Essential cookies like this one are indispensable for providing the service you requested (keeping you logged in) and generally do not require prior consent under applicable laws — unlike marketing or analytics cookies, which we do not use.

05How to control and remove cookies

You can manage cookies directly in your browser — block, delete, or be warned before accepting them. The instructions vary by browser (check the privacy/cookies section in Chrome, Firefox, Safari, Edge, or another).

Deleting cookies already stored ends your session: you will need to log in again.
Blocking the renderly_session cookie will prevent login and use of the dashboard, since it is essential to the operation of the service.
Incognito/private browsing usually discards cookies when you close the window.

Since we do not use marketing or analytics cookies, there are no "advertising preferences" to manage here. Control of essential cookies is handled by the browser itself.

06Changes to this policy

We may update this Cookie Policy to reflect changes in the service, in sub-processors, or in legislation. When that happens, we will revise the effective date at the top of this page and, in the event of a material change (for example, the introduction of analytics cookies), we will communicate it by reasonable means before it takes effect.

This policy forms part of, and should be read together with, the Privacy Policy and the Terms of Service.

07Contact

Questions about this policy or about the processing of your data? Talk to our Data Protection Officer (DPO):

privacy@renderly.dev— Data Protection Officer (DPO)

Document effective as of June 15, 2026. Version 1.0 (Beta). This is an initial template — review with legal counsel before launch.