Privacy policy.

Rydiq is a tool for cyclists. We store the ride footage you upload, the close-pass reports we generate from it, and the email address you sign up with. We don't sell any of that to anyone, and we don't use it to train models we sell to anyone else. If you delete a ride it's deleted; if you delete your account we wipe everything within thirty days.

• Account info.Your email address and a hashed password. That's it for the account itself.
• Ride footage you upload. The original video file, plus the chunks we generate while analysing it. Stored in our object-storage provider, encrypted at rest.
• Analysis results. Per-ride metadata: how long the clip is, when you uploaded it, every close pass we detected, the per-pass vehicle classification, lateral clearance estimate, and (when present) the license plate text our pipeline read.
• GPS telemetry. If the camera embedded GPS data in the file, we extract a downsampled (~1 Hz) lat/lng track and store it alongside the upload. Used to draw the map and tag incidents with location.
• Standard request logs. IP, user agent, the URL you requested, and the response code. Kept for thirty days for security and debugging, then rotated out.

• We don't use third-party analytics, advertising trackers, or fingerprinting libraries.
• We don't share data with advertising networks or data brokers. There aren't any partner integrations of that shape.
• We don't use your uploaded footage to train models we then sell to anyone else.

• To run the product. Analyse your rides, store the reports, let you log back in and view them, let you download incident PDFs.
• To improve detection accuracy.When the classifier makes an obvious mistake on your footage, an engineer may review the specific frames the pipeline flagged so we can fix the underlying model. We don't crawl your footage for unrelated purposes.
• To send transactional email.When an upload finishes processing, when there's a billing event, and when you specifically request something (password reset, invite). No marketing email goes to your account address unless you separately opted in via the beta waitlist.

We use a few infrastructure providers to actually run the service. They process your data only as needed to provide their service to us, and we've picked vendors whose own policies are compatible with the commitments above.

• Hosting + object storage: DigitalOcean (Managed MongoDB, Spaces object storage).
• Queue: Redis Cloud.
• Vision AI for vehicle make/model + plate recognition:OpenAI's API. Individual frames from your chapter-worthy passes are sent to OpenAI for identification. OpenAI's API policy is not to train on customer data.
• Email delivery: Resend.

• You can delete an individual ride at any time from the dashboard. The original video, all generated chunks, frame captures, and analysis rows are removed.
• You can delete your account at any time from Settings. We wipe everything tied to your account within thirty days, including backups. Request logs may persist as anonymised aggregates only.
• If we ever shut Rydiq down, we'll email every active account at least sixty days before any data is destroyed so you can export your rides and incident reports.

If you live somewhere with a privacy regime that grants you rights to access, correct, port, or delete your personal data, those rights apply. Email support@rydiq.org and we'll respond within the timeframe the relevant law requires (and usually a lot sooner).

If we change anything that meaningfully affects how your data is handled, we'll notify every active account by email at least thirty days before the change takes effect. The updated date at the top of this page always reflects the latest revision.

Questions, complaints, or requests: support@rydiq.org.