Privacy policy
Last updated: 21 October 2026 · Prelaunch review version
Prelaunch document awaiting completion. Before public launch, the controller’s identity and contact details, infrastructure providers, log retention and any international transfers must be confirmed. This version describes the landing page and does not certify unverified processing activities.
1. Controller and contact details
Rideriz is presented as a STARTES startup project. The brand and the startes.com link do not by themselves identify the legal entity acting as controller. Its full legal name, registered address and privacy contact must be confirmed before public launch. Details of any appointed or required DPO or representative will be provided where applicable.
2. Scope
This notice concerns the Rideriz prelaunch landing page. Delivery services are not yet operational. No orders, payments, Rideriz accounts, newsletters or application forms are active. Application buttons open an information message only and do not submit data.
3. Browsing data and purposes
Requesting pages necessarily transmits technical data to the network infrastructure, including IP address, requested URL, date and time, browser information and server responses. Such data may be processed to deliver the site, maintain security, diagnose errors and prevent abuse. Actual log access and provider settings must be verified.
The controller must identify and document the relevant legitimate interest and balancing assessment for security and service continuity under GDPR Article 6(1)(f). Applicable legal obligations must be assessed under Article 6(1)(c). Consent is not represented as the necessary legal basis for technical page delivery.
4. Cookies and tracking
The landing page application code does not set cookies or use localStorage or sessionStorage. It includes no analytics, advertising pixels, fingerprinting or session replay tools. Images and fonts are served from the same domain. See the Cookie policy for the assessment scope and infrastructure checks still required.
5. Recipients and providers
Hosting, content delivery and security services are involved in serving the site. This site is published through Sites and is available on rideriz.es. The contracting entities, their roles and any processor agreements required by GDPR Article 28 must be confirmed before public launch. The application code does not collect visitor data for sale or advertising.
6. Retention
The application does not create a visitor or applicant database. Infrastructure data and log retention depend on provider settings and contracts, to be confirmed before launch. Any further retention must be limited to documented security needs, legal duties or the protection of rights.
7. Transfers outside the EEA
We do not claim exclusively European processing without verification. The controller must assess provider locations, access and any transfers outside the EEA, and identify the applicable safeguards under GDPR Articles 44 onwards where required.
8. Your rights
Where the GDPR conditions are met, you may request access, rectification, erasure and restriction, object to processing based on legitimate interests and obtain portability where applicable. If a future activity relies on consent, you may withdraw it without affecting the lawfulness of prior processing. The rights request channel must be completed with the controller’s contact details; any identity verification must be proportionate.
You may lodge a complaint with the competent supervisory authority. In Spain you can consult the Agencia Española de Protección de Datos. Competence also depends on the actual establishment and processing activities.
9. Automated decisions
The landing page does not profile visitors or make automated decisions producing legal or similarly significant effects. The project’s commitment to human rider coordination does not replace the information required when an employment relationship begins.
10. Applications and future changes
A dedicated recruitment notice will be provided before applications are enabled, covering the controller, purposes, legal basis, recipients, retention and rights. Only data necessary for selection will be requested. Marketing consent will not be a condition of applying. Newsletters, analytics, third-party services and advertising require a separate assessment before activation.
11. Security and updates
The application serves assets locally, restricts browser resource sources and offers no personal data submission endpoints. These measures do not replace organisational obligations, provider contract checks or data breach procedures. This notice will be updated when missing details are confirmed or new functionality is introduced.