Last updated: August 8, 2025
Contact: cookies@render-a.com
1) What Are Cookies?
Cookies and similar technologies (local storage, pixels) help us run the site securely, remember preferences, and understand usage. Under the ePrivacy rules and GDPR, we request consent before placing non‑essential cookies.
2) Consent Management
On first visit, our banner lets you Accept all, Reject non‑essential, or Manage preferences by category. You can change your choices at any time via Cookie Settings in the footer. Your consent choices are stored and periodically refreshed.
3) Categories We Use
- Strictly Necessary (no consent): authentication/session management, load balancing, security.
- Preferences (consent): UI settings like language or theme.
- Analytics (consent): usage metrics to improve the Service (e.g., first‑party analytics or Google Analytics configured with IP anonymisation and short retention).
- Marketing (consent, if enabled): measuring campaign performance and attribution.
4) Example Cookie Table (indicative — update per deployment)
| Name | Purpose | Provider | Type | Duration |
| __stripe_mid | Payment fraud prevention | Stripe | 3rd‑party | 1 year |
| __stripe_sid | Payment session | Stripe | 3rd‑party | 30 minutes |
| _ga | Analytics (anonymised) | 3rd‑party | 13 months* | |
| _gid | Analytics (session differentiation) | 3rd‑party | 24 hours | |
| rendera_session | Authentication session | Rendera | first‑party | Session |
| cookie_consent | Stores consent choices | Rendera | first‑party | 6–12 months |
* configure to a shorter duration if feasible (e.g., 6 months) and honour consent.
5) Third‑Party Cookies & Signals
Third‑party providers may set cookies subject to their own policies. We honour consent signals and, where supported, Do Not Track/Global Privacy Control for non‑essential tracking.
6) Managing Cookies
You can delete cookies or block categories via browser settings. Blocking strictly necessary cookies may impact functionality.
7) Changes
We may update this Cookie Policy as technologies or regulations change. Material changes will be communicated via the cookie banner or in‑app notice.
Publishing Checklist (internal – remove before going live)
- Link Terms, Privacy, and Cookie pages in the site footer and sign‑up flow.
- Ensure the cookie banner is wired to block non‑essential scripts until consent.
- Add links to the current Subprocessor List and DPA (PDF or web page).
- Confirm contact emails (legal@, privacy@, cookies@) are monitored.
- Verify Estonian company details (registry number, address) on all pages.