In brief
- Necessary cookies keep you logged in to the portal and let the site remember your language and your choices.
- Where the law requires consent, functional and analytics cookies are turned on only after you give it; elsewhere, analytics is on until you turn it off. There are no advertising cookies.
- We issue the playground key for the duration of the session, and it lives only in the tab’s memory.
- You can manage cookies in “Cookie settings” at the bottom of the page and in your browser settings.
1What cookies are
1.1Cookies are small files that a website saves in your browser. Similar technologies are the browser’s storage (localStorage and sessionStorage). We call all of them cookies unless stated otherwise.
2Which ones we use
| Name | Purpose | Duration | Type |
|---|---|---|---|
__Host-access_token | Portal login: a session while you’re in your account. 24 hours and 30 days. | 24 hours | Necessary |
__Host-refresh_token | Portal login: a session while you’re in your account. 24 hours and 30 days. | 30 days | Necessary |
__Host-rg_2fa | Carry a login or a check until you complete it. | 10 minutes | Necessary |
__Host-rg_device | Remembers that this browser has already logged in to an account, and protects the login. | 180 days | Necessary |
__Host-rg_oauth | Carry a login or a check until you complete it. | Up to 15 minutes | Necessary |
__Host-rg_reset_cleanup | Completes a password reset in this browser. 15 minutes. | 15 minutes | Necessary |
__Host-rg_signup_attempt | Sign-up in this browser while you confirm your email. 24 hours. | 24 hours | Necessary |
__Host-rg_tg | Telegram login in this browser. 20 minutes. | 20 minutes | Necessary |
__Host-rg_webauthn | Carry a login or a check until you complete it. | 5 minutes | Necessary |
rg_consent | Your choice in this window, 12 months. | 1 year | Necessary |
rg_locale | The language of the site and the portal, 1 year. | 1 year | Necessary |
rg_ui_locale | The language of the site and the portal, 1 year. | 1 year | Necessary |
rg-auth-start-locale sessionStorage | The language of the page where you started logging in with Google or GitHub: needed so the return page opens in the same language. Stores only the language code, while the tab is open. | While the tab is open | Necessary |
rg-draft sessionStorage | An unsaved prompt in Playground, while the tab is open. | While the tab is open | Necessary |
rg_ref | The partner code you came through, 60 days. | 60 days | Functional |
rg-auth-last localStorage | Which login method you used last on this device. | 60 days | Functional |
rg-docs-lang localStorage | The code sample language in the documentation, until you clear your browser storage. | Until you clear your browser storage | Functional |
rg-theme localStorage | Light or dark theme. | Until you clear your browser storage | Functional |
_ga | Tell one visitor from another and keep the session, up to 2 years. Only when analytics is on. | Up to 2 years | Analytics |
_ga_<id> | Tell one visitor from another and keep the session, up to 2 years. Only when analytics is on. | Up to 2 years | Analytics |
2.1There are no advertising cookies. Analytics (Google Analytics 4): where the law requires consent, it is turned on only after you give it; in other countries it is on by default. The analytics counter is not loaded on login pages, in emails or in the portal. If you yourself allowed analytics, in the choice window or in “Cookie settings”, the identifier from the _ga cookie, if there is one, is passed to our server when you sign in to your account and when a portal page loads: with it we ourselves send Google Analytics 4 two account events (clause 2.7 of the Privacy policy).
3Data in browser storage
3.1The playground in the portal and on model pages receives a short-lived key from us for the duration of the session and keeps it only in the page’s memory. It does not end up in cookies or in the browser’s storage, is not sent to our servers along with the page, and is closed together with the session.
3.2The unsaved Playground prompt (rg-draft) is kept in the tab’s sessionStorage, and the language of code examples in the documentation (rg-docs-lang) in localStorage. They are not sent to our servers on their own.
3.3The login-page language (rg-auth-start-locale) is also kept in the tab’s sessionStorage: the page where you started login with Google or GitHub writes the language code there, and the return page reads it once and deletes it right away. Nothing else is stored in it, and it is not sent to our servers.
4Consent and settings
4.1Necessary cookies work without consent: without them you cannot log in to the portal, and the site cannot remember your language and your choices. Where the law requires consent, functional and analytics cookies are turned on only after you give it. We remember the theme when you switch it yourself, regardless of consent.
4.2We show the choice window in the countries of the European Economic Area, in the United Kingdom, and in Switzerland, and also when we could not determine your country; until you choose, optional cookies are off there. In other countries there is no window, and analytics is on by default. “Cookie settings” opens from the footer of any page in any country.
4.3You can change your choice at any time: Cookie settings.
4.4The “Decline” and “Accept all” buttons in the window are equivalent: declining does not close the site or the portal to you.
5Partner link
5.1If you came through a partner’s link, we remember it for 60 days to tie you to the partner when you sign up. Where the law requires consent, we remember the link only after you consent to functional cookies; until then the code stays only on the open page and is added to the sign-up links. In other countries the link is remembered right away. You can enter the partner code manually when you sign up; this works without cookies too.
5.2More about the program is in the Partner terms.
6How to turn off cookies in your browser
6.1All popular browsers let you block and delete cookies in their settings. If you block the necessary cookies, you will not be able to log in to the portal.
7Changes and contact
7.1We will update the list if the set of cookies changes, and we will state the version date. Questions: support@rendergrid.io.
Still have questions?
Write to us: support@rendergrid.io or Telegram. We answer questions about the terms and about data.