Classicbikemerch Ltd · Version 17 November 2026
Privacy notice
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.
Who is responsible
CLASSICBIKEMERCH LTD (company 17321186), 66 Paul Street, London, England, United Kingdom, EC2A 4NA, operates Coverstead. Contact hello@coverstead.net. We are the controller for enquiries, subscription accounts, billing administration and support records. Each venue is the controller for its guests’ and staff’s information; we host that information on the venue’s instructions under our data-processing terms.
Information and purposes
We use account-holder names, email addresses, authentication records, subscription identifiers, service history and support correspondence to set up, secure and support the service. We process account information to perform our contract with the customer; business-contact and security information for our legitimate interests in operating a reliable service; and accounting information to meet legal obligations. Passwords are stored as salted hashes. Stripe collects payment details and handles payment processing under its own privacy terms. We receive subscription and payment-status information, not full card numbers.
Enquiries and website activity
The enquiry form explains its separate consent and 90-day retention arrangements. Enquiring does not subscribe you to marketing. Optional website activity counts contain daily resource totals, not visitor profiles or analytics cookies. The demo keeps fictional data in your browser tab. Staff and billing sign-in use essential session cookies; verification and recovery links expire and can be used once. The host also processes technical access and security logs to operate and protect the service.
Providers and locations
Opalstack provides hosting and mail infrastructure; the Coverstead application runs in Frankfurt, Germany. Backblaze B2 in the EU Central region (Amsterdam, Netherlands) is the selected destination for encrypted hosted-service backups. Stripe handles subscription payment processing. Providers may also process account, support or security information internationally. Backblaze incorporates processing agreements into its service terms; Opalstack’s processing agreement, sub-processor list and applicable transfer safeguards remain to be confirmed before hosted venues are accepted. We do not sell your information. The data-processing terms describe the venue sub-processors, and we can provide details of applicable safeguards on request. Guest mail may be delivered through the venue’s chosen mail provider when agreed during setup.
Retention
We retain service-account and support records while needed to provide the service and normally for up to 12 months after closure. We retain accounting records for six years from the end of the financial year they relate to, or longer where legally required. Necessary records may be kept longer for an unresolved dispute or legal obligation. Venue records follow the venue’s instructions and the closure/backup schedule in our data-processing terms. Application security logs are reviewed and normally removed within 90 days; hosting-provider logs follow its operational retention. We do not use backups for marketing or ordinary access to deleted information.
Your rights
Depending on the circumstances, you can request access, correction, deletion, restriction, portability or object to processing based on legitimate interests. You can withdraw consent where we rely on it without affecting earlier lawful processing. We may need to verify your identity. For a booking or a venue staff record, contact the venue first; we assist it with requests. You can complain to the Information Commissioner’s Office. We do not make automated decisions with legal or similarly significant effects about you.
Changes and contact
We will update this notice when our processing changes and notify affected customers of material changes. Send privacy or security concerns to hello@coverstead.net; please avoid putting guest records in public GitHub issues.