Privacy policy

Privacy policy

Last updated 1 November 2026.

In short

Ridelark works on your phone. Your rides, places and settings stay there, and you don’t need an account. A few things do go online, to us and to others, and they’re all listed below.

Who we are

Ridelark is made by Matt Cockayne, in the UK, who decides how the information below is used. Questions about privacy, or a request about your data: [email protected].

What stays on your phone

Ridelark has no adverts, no tracking and no crash reporting of its own.

What leaves your phone

Each of these services sees your internet address, as any website does, and has its own privacy policy: komoot, Google, OpenFreeMap and Cloudflare.

This website

The site is hosted by GitLab Pages and reaches you through Cloudflare, which sees each visit as any web host does. We count visits with Cloudflare Web Analytics, which uses no cookies and doesn’t collect personal data. The site sets no cookies of its own.

If you join the beta, your email address comes to us through the testers’ Google Group and Google Play’s test, and is used only to run the test. If you email us, your message is forwarded by Cloudflare to our inbox, and kept as long as it’s needed to answer you.

Payments

Nothing is for sale today. If paid extras are added, Google Play will handle the payment, and this policy will say what that involves before they arrive.

Under UK data protection law, the reasons we rely on are our legitimate interest in keeping the maps for genuine copies of the app, and in running a test with the riders who asked to join it.

You can ask what we hold about you, and ask us to correct or delete it, by emailing [email protected]. If you’re unhappy with how we’ve handled your data, you can complain to the Information Commissioner’s Office, ico.org.uk.

Your choices

Changes

If this policy changes, the new version goes here with its date.