Cookie policy
Last updated: 21 October 2026 · Prelaunch review version
Scope: landing page application code. The checks described concern the Rideriz application. A final inventory of technical cookies and logs used by hosting/authentication infrastructure must be confirmed before public launch.
1. What cookies are
Cookies are small files stored on a device. Other identification tools include local storage, pixels and fingerprinting. Applicable rules depend on their actual purposes and processing characteristics.
2. Current configuration
| Category | Application status | Purpose and duration |
|---|---|---|
| Application cookies | None set by the code | Not applicable |
| Analytics | Not installed | No integrated provider |
| Marketing and profiling | Not installed | No pixels or remarketing |
| localStorage / sessionStorage | Not used by the code | No local records |
| Hosting, security and preview access | To be verified with the provider | Any names, domains and durations will be listed following the infrastructure inventory |
3. Fonts, images and links
Landing page fonts and images are hosted on the same domain. The code does not load Google Fonts from external domains, embedded video, maps, social widgets or trackers. External links such as startes.com are opened only when selected; the destination applies its own notice.
4. Consent
The current application has no optional tracking tools to accept. It therefore does not display a consent banner with fictional choices. “Cookies and tracking” in the footer opens an information panel and stores no preferences. Any future non-essential tracking must remain inactive until valid consent, with refusal, purpose-specific choice and easy withdrawal available.
5. Browser controls
You can view or remove cookies and site data through your browser settings. Removing platform technical data may affect private preview access. The Rideriz panel does not manage cookies on other domains or authentication services.
6. Updates and contact
Controller details and contact information must be completed in the Privacy policy. This cookie policy will be updated for the services actually enabled and the platform inventory.