Classicbikemerch Ltd · Version 17 November 2026
Data-processing terms
Hosted-launch documents: enrolment remains closed while we confirm the hosting provider’s processing agreement and retention arrangements. No paid subscription starts from these pages.
Roles, purpose and duration
The subscribing venue is the controller; CLASSICBIKEMERCH LTD, company 17321186, is its processor for hosting, maintaining and supporting its reservation installation. These terms apply during the service and the closure/backup period. The venue instructs us to store, organise, retrieve, back up, transmit and delete records as needed for the documented service and its authorised requests. We will process venue data only on those instructions, including transfers, unless law requires otherwise; where permitted we will tell the venue of that requirement.
People and information
Records may concern guests, venue staff and administrators: names, contact details, reservations, service notes, visit history, marketing permissions, staff roles and authentication records. Guests may supply dietary or accessibility information. The venue must identify an appropriate lawful basis and any additional condition for sensitive data, provide suitable notices, and minimise free-text information. We do not use venue guest data for our own advertising.
Security and confidentiality
Access is limited to people who need it for the service and are subject to confidentiality obligations. Each hosted venue has a separate application process, database, configuration and staff accounts. We use HTTPS, hashed passwords, role checks, private configuration files, encrypted off-server backups, software maintenance and operational checks. These controls reduce risk but cannot guarantee that incidents will never occur. The venue remains responsible for its users, devices and appropriate staff permissions.
Sub-processors
The venue authorises Opalstack for hosting and mail infrastructure (Coverstead application location: Frankfurt, Germany), and Backblaze B2 for encrypted backup storage (EU Central: Amsterdam, Netherlands). Any venue-selected mail provider is recorded during setup. Stripe handles the subscription account separately; it is not sent guest reservation databases by this integration. Before accepting hosted venues, we must have applicable data-protection arrangements in place with each sub-processor. Opalstack’s processing agreement is awaiting confirmation; its privacy policy alone is not being treated as that agreement. We remain responsible for sub-processor obligations under the final terms. We will notify the venue at least 30 days before adding or replacing a venue-data sub-processor, giving it an opportunity to object on reasonable data-protection grounds. We will discuss an alternative or ending the affected service if the objection cannot be resolved.
Assistance and incidents
We assist the venue, taking account of the processing and information available to us, with individual-rights requests, security obligations, impact assessments and regulatory consultation. Requests received directly from guests are referred to the venue. We notify the venue without undue delay after becoming aware of a personal-data breach affecting it, provide known facts and subsequent updates, and help investigate and mitigate the incident. The venue decides its regulatory and individual notifications. Report concerns to hello@coverstead.net.
Backups, return and deletion
The hosted service is configured for hourly local snapshots and daily encrypted off-server backups. Completed local snapshots are kept for 48 hours; off-server snapshots are retained for 35 days, with the latest successful recovery point kept until a newer one is verified. A backup failure requires investigation and may delay normal expiry; we record and address such exceptions. The venue can export booking and customer records through the app, and request assistance with a fuller return of its records. Following termination, it has 30 days to export before operational records are deleted, unless it instructs earlier deletion or law requires retention. Copies in Coverstead’s own backup repository normally expire within a further 36 days (including the storage provider’s deleted-object cleanup). Separately, Opalstack’s published terms describe infrastructure backups retained for 12 weeks. The applicable provider deletion arrangements are being confirmed before hosted enrolment; the shorter Coverstead schedule does not describe those provider backups. If a recovery is necessary, we reapply recorded deletions before returning the service to use. Backup passwords and access credentials are held privately.
Accountability
We make information reasonably needed to demonstrate compliance available to the venue and allow reasonable audits or inspections by it or its appointed auditor, with arrangements that protect other customers’ data and service security. We will tell the venue promptly if an instruction appears to infringe applicable data-protection law. On request at the end of the service, we confirm return/deletion, subject to documented legal-retention obligations. The service terms otherwise continue to apply; these data-processing terms take precedence for the handling of venue personal data.