Privacy notice

Privacy and data rights

Version 2026-10-23.2

RUZGAR is operated from Germany and is designed around private riding records and deliberate public sharing. This notice explains how personal data is handled for all account holders. Depending on where you live, additional local rights may apply. RUZGAR records the account-eligibility confirmation described in the Terms, not a birth date.

Who is responsible

What the service stores

An account can include profile and sport settings, private rides and launch points, recorded-activity metrics, gear, saved Places, posts, follows and Shakas, Place familiarity, contributions, safety reports, and privacy-request history. Uploaded activity source files are validated, parsed, and discarded; the resulting private ride and activity records remain until you remove them or complete an erasure request.

Why data is used

Provide your requested account service

Account, private journal, gear, saves, posts, follows, and the sharing choices you initiate are processed to perform the service you request (GDPR Article 6(1)(b)). Optional public visibility is never required for a private journal.

Optional location and public visibility

Broad rider-map presence and public-at-Place familiarity require a separate affirmative opt-in (Article 6(1)(a)). They can be withdrawn without deleting the private account or ride history.

Keep the service safe and trustworthy

Rate limits, abuse reports, security logs, moderation, source review, fraud prevention, and minimal service analytics rely on RUZGAR's legitimate interests (Article 6(1)(f)), balanced against rider rights and limited to what is necessary.

Meet legal and rights obligations

Privacy requests, defensible completion evidence, and incident notification records are processed where necessary for legal obligations (Article 6(1)(c)) or the establishment, exercise, or defence of legal claims.

Visibility and precise location

Rides, exact launch points, routes, journals, stays, and detailed gear records are private by default. A public profile, public post, shared ride summary, public-at-Place familiarity, and broad rider-map presence are separate choices. A rider can explicitly share their selected exact launch pin with a public or follower ride; the chosen audience can then see and save that point, including on the rider’s session map. A separate per-ride choice can also list a public exact pin on the worldwide Community rides map; it is not enabled for existing shares. Hiding it later cannot recall copies others made. Public projections omit private journals, hidden locations, and raw routes. RUZGAR does not infer public Place membership from GPS, rides, an IP address, or a home location. If you choose to attach a point or drawn area to a Rider Note, that location appears publicly with the Note until it is removed.

Retention baseline

Active account and rider content

Kept while the account is active or until the owner deletes the item. Verified account closure removes live account data within 30 days unless a documented exception applies.

Operational and error telemetry

Cloudflare Worker request and error logs are sampled and retained for up to seven days. Supabase authentication and service logs follow its plan-specific retention. Brevo transactional email delivery logs are set to one month; new email previews are not stored. RUZGAR's own log entries are designed not to include passwords, tokens, exact private coordinates, routes, journals, stays, or uploaded content.

Identity-free outbound-link events

Raw events are deleted daily once older than 90 days. Each event keeps only its time, a broad RUZGAR page section, and the external host opened. It does not keep a rider or ride ID, link label, URL path or query, cookie, IP address, or user agent, and is not a count of unique visitors.

Aggregate public-page activity

If enabled, we measure aggregate visits to public pages and approximate time spent viewing them to improve RUZGAR. This measurement uses no analytics cookies or visitor identifiers. Daily totals are kept for 90 days. We count sign-up-page visits and confirmed accounts separately; we cannot link a visit to an account.

Moderation and security evidence

Report decisions, appeals, admin actions, and closed security incidents: 24 months, followed by deletion or irreversible aggregation unless a legal claim or authority requires a longer documented hold.

Privacy-request evidence

The minimum evidence needed to show receipt and resolution: three years after closure, then deletion unless a longer legal hold is documented. Export packages are generated on request rather than retained as a second copy.

Backups

During this limited beta, RUZGAR has not verified a recoverable hosted backup of the database or uploaded files. A service failure could therefore cause data loss. If provider-managed backup copies exist, deleted data may remain in them until the provider's applicable retention period expires. RUZGAR will verify database and file recovery separately before claiming a recovery window; any restore must respect completed erasure requests before serving users.

Service providers

RUZGAR uses service providers to host and operate the service, store account information and uploaded content, deliver essential emails, and provide maps and search. They may process only the information necessary to provide those services and are subject to appropriate data-protection safeguards. Where personal data is processed outside the European Economic Area, an applicable legal transfer mechanism and safeguards are used. Contact privacy@rideruzgar.com for more information about current providers and transfers.

Cookies and similar storage

RUZGAR's launch baseline uses only first-party authentication and security storage needed to sign in and provide requested features. It has no advertising, cross-site tracking, embedded autoplay media, or non-essential analytics cookies, so it does not display a performative consent banner. Any future non-essential cookie, analytics SDK, advertising, or personalization requires a new review and prior valid consent where applicable.

Your choices and requests

Signed-in riders can download a machine-readable copy of their data. Email privacy@rideruzgar.com for access, correction, restriction, objection, portability, or erasure. An ordinary signed-in rider can delete their account from Settings after entering a confirmation phrase and current password; Admin approval is not required. The service removes active uploaded media, Auth identity, and owner-linked data, then checks completion. If automation fails or a legal, security, or privileged-account exception applies, privacy support follows up without undue delay. Provider backup expiry is not yet verified. Other rights requests are normally answered within one month. If a request is refused, RUZGAR explains why and the right to complain to a supervisory authority.

Open account & data settings

Contact without an account

Email privacy@rideruzgar.com for privacy, account-access, or data-rights help. Do not send passwords, raw GPS files, or identity documents unless requested through a verified process.

Report a suspected vulnerability or security incident privately to security@rideruzgar.com. Do not publish rider data, credentials, or exploit details in a community post.

Regulatory references

This baseline follows the GDPR principles of purpose limitation, data minimisation, storage limitation, privacy by default, accountability, security, and data-subject rights. It is an operational baseline, not legal certification. The real controller must verify the final notice, completed DPIA and legitimate-interest assessments, provider contracts, lead supervisory authority, and jurisdiction-specific rules before opening registration.