Skip to content

Latest commit

 

History

History
172 lines (113 loc) · 12.1 KB

File metadata and controls

172 lines (113 loc) · 12.1 KB

Reckless Rides UK — compliance & standards statement

Document purpose: This statement is provided to complainants, online platforms (including YouTube), and law enforcement to explain how the Reckless Rides UK project is operated, the legal and platform obligations we have considered, and the controls we apply before any clip is made publicly visible.

Data controller: Dynamic Devices Ltd (England & Wales)
ICO registration: Dynamic Devices Limited · register reference ZC180994 (Tier 1 micro; fee paid 23 June 2026; direct debit application C1966226).
Privacy contact: ajlennon@dynamicdevices.co.uk
Channel: @Reckless-Rides-UK
Public site: recklessrides.uk
Public document: github.com/DynamicDevices/reckless-rides-uk/blob/main/COMPLIANCE-STATEMENT.md
Version: 1.10
Last updated: 24 June 2026
Jurisdiction: England & Wales, United Kingdom


1. Who we are and what we do

Reckless Rides UK documents dangerous and illegal cycling in the United Kingdom — including pavement and footpath riding, reckless road cycling, delivery bikes, and similar behaviour. Our purpose is pedestrian safety, road-safety awareness, and supporting proper reporting to the police where appropriate.

We do not operate this project to harass, identify, or encourage action against private individuals. We describe observed behaviour (for example, riding on a pavement or cycling dangerously on the road), not personal attacks.

Reckless Rides UK is operated by Dynamic Devices Ltd, a limited company registered in England & Wales. We are registered with the UK Information Commissioner’s Office (ICO) and pay the annual data protection fee as a Tier 1 micro organisation. This is a structured evidence and awareness programme with documented controls — not informal or vigilante activity.

Awareness · Evidence · Change


2. Legal and regulatory framework considered

We have reviewed how UK law and regulation may apply to recording in public places and publishing short video clips online. This is an ongoing process, not a one-time tick-box. The following areas are explicitly in scope for our design and operating procedures:

Area Our understanding and response
UK GDPR & Data Protection Act 2018 Footage in which a person is identifiable is personal data. Public publication on YouTube is not treated as purely personal/household use. We act as a data controller for material we upload and retain.
Lawful basis We rely primarily on legitimate interests (road safety documentation and public interest in unlawful pavement riding and dangerous cycling), balanced against individuals’ rights through anonymisation, limited publication, and takedown procedures.
Harassment & communications law We do not encourage confrontation, “pile-ons”, or repeated targeting of the same individual. Comments are disabled on all videos (2026-06-23) to prevent doxxing and abuse.
Defamation & misuse of private information We use factual, neutral descriptions of observable conduct. We avoid naming individuals in titles or descriptions unless already necessary for a formal process we are engaged in.
Highway / road traffic context Pavement riding and dangerous cycling may contravene UK highway law depending on circumstances. Documenting this behaviour supports a public-interest purpose; it does not remove our obligations to handle personal data fairly.
Children Extra care applies where under-18s may appear. We withhold publication where effective anonymisation is uncertain.

Important: This statement describes our intended standards and controls. It is not legal advice and does not claim that every publication is lawful in every circumstance—that depends on the facts of each clip. We are committed to correcting mistakes promptly when they are drawn to our attention.

Detailed operating procedures: UK compliance record and publication workflow in our public GitHub repository. Reviewed at least every six months.


3. Platform terms (YouTube)

We operate on YouTube as @Reckless-Rides-UK and aim to comply with:

Editorial standards we apply:

  • No incitement to harassment or vigilantism
  • No publishing with the primary purpose of identifying private individuals for mob justice
  • Factual titles and descriptions (observable conduct — e.g. “ridden on the pavement”, “dangerous cycling on the road”)
  • Privacy notice on the channel; per-video privacy footer with contact email
  • Upload private, review, then set public manually — never skip the review gate
  • Clips published as standard Videos (16:9 letterbox), not Shorts, for searchable descriptions
  • Comments disabled on all videos (YouTube Studio, 2026-06-23) — privacy and harassment risk reduction; contact via email for privacy/takedown

If YouTube or another platform believes content breaches its terms, we will engage constructively and act promptly on valid notices and rulings.


4. Technical and privacy controls (summary)

Before any clip is made publicly visible, we apply a controlled pipeline designed to minimise identifiability and metadata exposure:

Stage What happens
Original recording Retained privately with device metadata (time, location). Not uploaded to YouTube or public repositories.
Face anonymisation Automated face blurring on a working copy; manual review before any upload decision.
Publish copy Embedded GPS/device metadata removed; letterboxed to 1920×1080 so clips appear as standard Videos (not Shorts).
Upload visibility Clips are uploaded as Private (automated via import watcher or manual script), reviewed again on the platform, and only then set to Public manually.
Description Factual incident log text; privacy footer with ajlennon@dynamicdevices.co.uk and link to this statement.
Evidence integrity Original files and integrity records retained for possible handover to police under proper process.

We do not commit video evidence files to public source-control repositories.


5. Transparency to viewers and data subjects

Our YouTube channel description states, in summary:

  • Originals are kept private; published clips are anonymised
  • Faces are blurred before upload; file metadata is stripped from uploads
  • Time and location may appear in descriptions for incident logging
  • Uploads are private until manually reviewed, then made public
  • A public incident map at recklessrides.uk lists uploaded incidents (time, location, title) and links to each clip on YouTube — the map does not embed or host video files
  • Individuals may contact us to request removal or correction

We aim to meet UK GDPR principles including lawfulness, fairness, transparency, data minimisation, storage limitation, and accountability.


6. Rights of individuals and complaints process

If you believe you appear in footage, or that material about you has been processed unfairly, you may contact us (see §9). We will treat requests seriously and in good faith.

UK GDPR response times: we aim to match ICO guidance — respond without undue delay and, for formal rights requests, within one calendar month at the latest; up to two further months only if the request is complex or we receive several requests from you, with notice within the first month. We request identity verification promptly before disclosing private archive material (ICO right of access).

Request type Our intended response
Objection / erasure Review promptly. Published clips: we aim to remove or restrict within 7 days where identification is possible despite blur (voluntary target, faster than the statutory month where we can). Originals: delete unless compelling grounds to retain (e.g. active police investigation) — formal erasure requests within one calendar month (ICO).
Correction If descriptions are materially inaccurate, we will correct or remove them within one calendar month for formal requests; faster where practical.
Subject access One calendar month (ICO standard); verify identity before disclosing private archive material.
Platform report You may also use YouTube’s reporting tools; we do not discourage lawful use of platform processes.

We maintain an internal log of complaints and actions taken.

Emergency or crime in progress: dial 999.
Non-emergency police matters: dial 101 or use your local force’s online reporting.


7. Cooperation with law enforcement

Where dangerous or illegal cycling is reported to the police, we may provide original footage (not the anonymised YouTube copy), together with integrity information, to assist a lawful investigation. We do not publish material for the purpose of bypassing police processes or obtaining hire/operator records directly from operators.

We will verify law-enforcement requests and disclose the minimum necessary material.


8. Openness to constructive feedback

We are very open to constructive feedback from complainants, platforms, regulators, road-safety bodies, and legal professionals to ensure we meet all applicable legal obligations and platform standards while providing this service responsibly.

We welcome specific, actionable input—for example:

  • Where anonymisation appears insufficient
  • Where description text is inaccurate or disproportionate
  • Where publication visibility should be restricted or withdrawn
  • Where our transparency information should be clearer
  • Where our procedures should be strengthened

We will acknowledge substantive contact within 48 hours where possible and aim to resolve or escalate within 7 days for published-clip complaints — voluntary targets where we can; formal UK GDPR requests follow ICO timelines (one calendar month, with extension only as ICO allows).

If feedback reveals a systemic gap, we will update our internal compliance documentation and operating procedures.


9. Contact

Purpose Contact
Privacy, takedown, correction, data rights ajlennon@dynamicdevices.co.uk
YouTube channel @Reckless-Rides-UK
Incident map recklessrides.uk

Please include: URL of the video (if any), date/time/location if known, and the nature of your request. This helps us respond accurately.


10. Document status

Item Detail
Internal compliance record UK-COMPLIANCE.md — reviewed ≥ every 6 months
Operational workflow Documented with ingest, review gates, and publication controls
This statement Intended for external sharing with complainants, platforms, and police

We believe the measures above demonstrate that legal and terms-of-service compliance has been carefully considered and addressed in design and operation, with ongoing review and openness to improvement.


This document is provided for transparency. It does not create contractual rights and is not a substitute for independent legal advice.