Privacy notice
CM-HUB Website Privacy Notice
Effective date: 15 November 2026
Introduction
This notice explains how CM-HUB LTD collects and uses personal data through this website, why we use it, who we share it with, how long we keep it and the choices and rights available to you.
We process personal data in accordance with applicable data protection and privacy law, including the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and, where applicable, the EU General Data Protection Regulation (EU GDPR). Other privacy rights may apply depending on where you are located.
We apply the privacy principles and individual rights described in this notice regardless of where you are located, except where local law requires a different approach.
1. Who We Are
Data controller: CM-HUB LTD
Company registration number: 17194656
Registered office:
Stockport Business & Innovation Centre
3rd Floor Broadstone Mill
Broadstone Road
Stockport
SK5 7DL
United Kingdom
Email: info@cm-hub.io
Website: https://cm-hub.io
CM-HUB LTD is a subsidiary of Op-tec Systems Ltd.
CM-HUB LTD operates as a separate legal entity and is responsible for determining how personal data collected through the CM-HUB website is used and protected.
Op-tec Systems Ltd provides technical, administrative and operational support, including IT infrastructure and Microsoft 365 administration.
Where authorised Op-tec personnel access CM-HUB personal data, access is restricted according to their responsibilities and subject to appropriate confidentiality, security and data protection arrangements.
CM-HUB LTD remains the controller of the website personal data described in this notice.
Privacy enquiries can be directed to info@cm-hub.io.
2. Personal Information We Collect
We collect personal data when you interact with our website, request information, contact us or use our demonstration services.
2.1 Contact and enquiry forms
When you submit an enquiry, we collect:
- Your name.
- Your work email address.
- Your company name.
- Your job role, where voluntarily provided.
- Your message, where provided.
- Your preferred contact method.
- Your telephone number and preferred call-back time, if you request telephone contact.
- The page from which you submitted the enquiry.
- Relevant campaign identifiers, including UTM parameters.
- The referring website domain, where available.
- Your optional marketing consent preference, together with the wording version and the date and time of your submission.
Your name, work email address and company name are required to process an enquiry.
Your job role is optional. You can submit an enquiry without providing it.
Where provided, your job role is included in the enquiry and transferred into the corresponding lead record within Twenty CRM.
2.2 Telephone call-backs
If you request telephone contact, we collect your telephone number and preferred time of day.
We use this information to respond to your enquiry and carry out related follow-up communications.
We do not use enquiry call-back numbers for unsolicited marketing calls or text messages.
2.3 Website analytics
When you agree to analytics, we collect information about your interactions with the website, including:
- Pages visited.
- Website sections viewed.
- Video playback and completion.
- Guided demonstration interactions.
- Selected demonstration roles.
- Animation preference changes.
- Requests for full demonstration access.
- Demonstration launches.
- Enquiry form submissions, excluding message content.
- Email and telephone contact-link interactions.
- Campaign and referral information.
When you switch the animation on or off, we also record whether your device is set to reduce motion.
We use Umami, a self-hosted website analytics platform.
Umami receives technical information associated with web requests, including IP addresses and browser user-agent information.
It uses this information to generate website statistics and pseudonymous visitor identifiers.
Umami may also derive and record approximate geographic information from visitors' IP addresses, including country, region and city.
This information is used to understand website traffic and visitor engagement.
We do not intentionally send names, email addresses or enquiry message contents to Umami.
2.4 Technical and security information
Our systems process technical information necessary to maintain website security and reliability, including:
- IP addresses.
- Browser user-agent information.
- Requested website paths.
- Access dates and times.
- HTTP response information.
- Failed authentication attempts.
- Security and rate-limiting events.
This information is used to detect suspicious activity, prevent misuse and investigate technical problems.
2.5 Demonstration information
When you request access to the full CM-HUB demonstration, we collect:
- Your work email address.
- Your name.
- Your company name.
- The demonstration you select: the side (CM-HUB's own team or a contractor), your role, and a module or package.
- Your demonstration start time.
- Relevant campaign information.
- Your optional marketing consent preference.
- Technical information required for email verification and session management.
Available demonstration roles include Engineer, Maintenance Manager and Technician.
The demonstration is deliberately separated from your identity. The demonstration application receives a session identifier, selected role and session expiry time. It does not receive your name or email address from the website verification process.
The demonstration is intended for evaluation using non-confidential test information. Please do not enter personal data, confidential information, production data or other information relating to real people or operational assets unless expressly authorised to do so. Information entered into the demonstration may appear in application records and audit history until the relevant demonstration data is reset or expires.
While you use the full demonstration, we also record analytics events about your visit. On our website, these events are linked to the work email address you verified. Section 22 describes them.
3. How We Use Your Information
We process personal data for the following purposes.
Responding to enquiries
We use information supplied through contact forms and direct communications to answer questions, provide product information and follow up on business enquiries.
Submitting an enquiry or requesting a demonstration does not subscribe you to marketing communications. We only send marketing communications where you have separately chosen to receive them, or where another lawful basis permits us to do so under applicable law. You can opt out at any time.
Managing customer relationships
We maintain enquiry and demonstration lead records in Twenty CRM, which is hosted and managed on CM-HUB infrastructure.
These records enable authorised personnel to manage enquiries, track business relationships and provide relevant follow-up.
Providing demonstration access
We use work email verification to confirm access to the email address supplied and to manage demonstration sessions.
The demonstration session that follows also lets you switch side and role during your visit without a new code.
Demonstration analytics
We record how the full demonstration is used, to understand which parts visitors use and to improve the demonstration. These records are linked to the work email address you verified.
Marketing communications
We send occasional product announcements, company news and service updates to individuals who have provided valid marketing consent.
Website analytics
Where analytics consent has been given, we use website statistics to understand visitor engagement and improve our website.
Security and reliability
We process necessary technical information to protect our systems, manage authentication, prevent spam, maintain backups and investigate security incidents.
How we do not use your information:
- We do not sell personal data.
- We do not use personal data for behavioural advertising.
- We do not provide personal data to advertisers or data brokers.
- We do not use third-party advertising trackers on this website.
- We do not make decisions about individuals using solely automated processing that produce legal or similarly significant effects
4. Our Lawful Bases for Processing
We process personal data under the lawful bases established by the UK GDPR.
Legitimate interests
We rely on legitimate interests for:
- Responding to business enquiries.
- Managing prospective customer relationships.
- Recording requests for product demonstrations.
- Providing proportionate business follow-up.
- Maintaining website and system security.
- Preventing fraud, spam and misuse.
- Managing demonstration verification and access.
- Maintaining security and administrative audit records.
- Protecting our infrastructure and data.
We balance these interests against the rights and reasonable expectations of individuals.
Consent
We rely on consent for optional marketing communications and non-essential website analytics.
Consent can be withdrawn at any time.
Contractual necessity
Where applicable, we process personal data to take steps requested before entering into a contract or to fulfil contractual obligations.
Legal obligations
We process and retain information where necessary to comply with applicable legal requirements.
5. Marketing Communications
We send occasional news and product updates by email only where you have actively selected the separate, optional marketing consent checkbox presented on the relevant form.
The checkbox is not preselected.
You can submit an enquiry or request a demonstration without agreeing to marketing communications.
We record your consent choice, the wording version presented and the time at which consent was given.
Your marketing preferences are maintained within our customer records.
Marketing consent is separate from our processing of enquiry and demonstration lead information.
You may withdraw marketing consent at any time by emailing info@cm-hub.io.
Marketing communications also provide a way to stop receiving further messages.
Where you withdraw consent, we stop sending marketing communications and retain appropriate suppression information to respect your preference.
6. Website Analytics
We use Umami, a self-hosted analytics platform, to understand how our website is used.
Analytics are optional and operate only when visitors have accepted analytics through the website's consent mechanism.
Where a browser communicates a recognised Do Not Track or Global Privacy Control preference, we treat this as a preference not to enable optional analytics.
Analytics inside the full demonstration work differently: they are always on, are not affected by these choices, and are described in section 22.
Information processed by Umami
Umami processes website interaction information, including page visits, selected events, browser information and technical request information.
IP addresses and browser user agents are used by the analytics system to calculate visitor statistics.
Umami may derive approximate location information from IP addresses and record geographic fields such as country, region and city.
This information helps us understand which locations visitors access the website from.
Umami does not use analytics cookies.
The platform generates pseudonymous visitor identifiers using technical request information and a periodically changing value.
We do not intentionally transmit personal details entered into enquiry forms to analytics.
Analytics retention
Umami does not currently have an automatic data retention period configured.
Analytics records remain in the database until they are deleted through database administration or another deliberate deletion process.
This means analytics information may be retained for an extended period.
The analytics database is hosted on CM-HUB-controlled infrastructure with restricted administrative access.
Withdrawing analytics consent
You can change your analytics preference using the Cookie settings link in the website footer.
Withdrawing consent stops future analytics collection from your browser.
Previously collected aggregated information that no longer identifies or relates to an identifiable individual may be retained.
We do not use third-party advertising trackers.
7. Cookies and Similar Technologies
We use a limited number of cookies to provide website functionality and remember your preferences.
Consent preference cookie
Cookie: cmhub_consent
Purpose: Stores your analytics consent choice and the version of the consent information presented.
Duration: 180 days.
This cookie is used to remember your privacy preference.
It does not contain your name or email address.
Staff authentication cookies
Authentication cookies are issued to authorised staff and content editors when they sign in or preview restricted content.
These cookies maintain secure authenticated sessions.
Ordinary website visitors do not receive staff authentication cookies.
Full demonstration cookies
The full demonstration access process uses three essential cookies.
Cookie: __Host-cmhub-demo-v
Purpose: Supports email verification during the demonstration access process.
Duration: 40 minutes.
Cookie: __Host-cmhub-demo-s
Purpose: Maintains demonstration session information, supports session management and lets you switch side and role during your visit.
Duration: 3 hours.
Cookie: __Host-cmhub-demo-h
Purpose: Transfers the session identifier and selected role into the separate demonstration service.
Duration: 2 minutes.
This cookie is used once during the demonstration handover.
These cookies do not contain visitors' names or email addresses.
They support functionality requested by visitors and are used for authentication and session management.
We do not use advertising or social media tracking cookies.
8. Guided Website Demonstration
The guided demonstration on our website can be used without creating an account.
It operates within your browser without requiring personal information.
The guided demonstration does not independently store your selections in our CRM.
Where you have accepted analytics, interaction events may be recorded by Umami.
The guided demonstration does not require additional tracking cookies or persistent browser storage.
9. Full Demonstration Access
The full CM-HUB demonstration operates as a separate service accessed through our website.
Email verification
To request demonstration access, you provide a work email address.
We send a six-digit verification code to that address using Resend, our transactional email delivery provider.
Verification codes are valid for 10 minutes.
The verification email identifies CM-HUB and contains the code needed to continue.
It does not contain advertising or marketing tracking elements.
Verification emails are operational service messages sent in response to demonstration access requests.
If you receive a code that you did not request, you can ignore the message.
Starting a demonstration
After successful email verification, you provide your name and company name, and choose the side (CM-HUB's own team or a contractor), the role and the module or package you want to see.
You can separately choose whether to receive marketing communications.
Marketing consent is not required to access the demonstration.
Before you start, you are asked to confirm this notice, including the demonstration analytics described in section 22.
You can start a new demonstration visit up to 3 times in 24 hours with the same work email address. Switching side or role during a visit does not count towards this limit.
CRM lead records
When you start a demonstration, CM-HUB records your name, work email, company name and demonstration interest in Twenty CRM.
The record includes the name of the demonstration you started with, campaign information and demonstration start time. Switching side or role during a visit does not create another record.
This information allows CM-HUB to manage business enquiries and provide proportionate follow-up.
The CRM record is kept while its purpose applies and is reviewed at least every 12 months, as described in section 16.
Demonstration privacy
The demonstration receives a session identifier, the side, role and module or package you selected, and the session expiry time. When you switch side or role, it also receives the identifier of your previous demonstration session.
It does not receive your actual name or email address.
You interact with the system using a made-up demonstration account created for your visit.
A demonstration visit lasts no more than 3 hours. It ends sooner after 30 minutes without activity (a click, key press, touch or pointer movement), or when you choose "End my demo". When your visit ends, your demonstration account is blocked and then deleted.
Switching side and role
During a visit you can switch to another side or role without a new email code. Each switch gives you a new made-up demonstration account and ends the previous one in the same way as the end of a visit. A switch keeps your visit's original end time. You cannot switch in the last 5 minutes of a visit, and a visit allows up to 10 switches.
If you ask us to erase your data
When the full demonstration is available, if you ask us to erase your data, we remove the following from the demonstration straight away, without waiting for the usual periods:
- your access to your demonstration account;
- your IP address, browser details and session identifier in the demonstration's audit records;
- bug reports from your visits, and error log entries written while you were signed in to the demonstration;
- the demonstration's sign-in audit records for your account;
- the link between your website session and your demonstration account.
Records you created in the demonstration go at the next nightly reset, described in section 22. Some records stay after an erasure, including the demonstration's audit log of actions. Section 16 says which, and why, under "Records inside the full demonstration".
Security and misuse prevention
We maintain temporary records to prevent excessive verification requests and misuse.
Temporary plain-text email verification records are cleared as part of the verification process and associated cleanup procedures.
Hashed verification and rate-limiting information is retained for 24 hours.
Hashed records of demonstration starts are retained for 25 hours.
Pseudonymous demonstration session records are retained for 90 days after the session ends.
These records support security monitoring and investigation of misuse.
We also use pseudonymous website session records to identify demonstration sessions associated with an individual when responding to personal data requests, including requests for erasure. This enables us to locate relevant demonstration records without routinely passing visitors' names or email addresses into the demonstration application.
Demonstration content
The demonstration uses example accounts and illustrative information.
The demonstration is a shared sandbox, and the CM-HUB demonstration team can see what you enter. Section 22 says more.
Visitors should not enter real personal information, sensitive information or confidential business material into demonstration fields.
10. Customer Relationship Management
We use Twenty CRM to organise and manage enquiries and demonstration leads.
Twenty operates on CM-HUB-controlled infrastructure.
Lead records may contain:
- Name.
- Work email address.
- Company name.
- Optional job role.
- Telephone number, where provided.
- Contact preferences.
- Enquiry details.
- Demonstration activity.
- Marketing consent information.
- Campaign information.
- Interaction and follow-up history.
Access is restricted to authorised personnel with a legitimate operational requirement.
CRM retention
We keep CRM records only while their purpose applies.
We review CRM records at least every 12 months and document each review.
We delete or anonymise a lead when its purpose no longer applies, that is when there is no continuing engagement, no active opportunity and no other genuine business reason to keep it.
We retain business enquiry and CRM information for as long as we reasonably need it to manage our relationship with you, pursue an active business opportunity, maintain appropriate business records or meet legal requirements. We periodically review inactive records and delete or anonymise personal data that we no longer need.
Records can be deleted through authorised CRM administration and in response to applicable data protection requests.
Individuals may request access, correction, restriction or deletion of their records by contacting info@cm-hub.io.
Deletion requests are considered and processed in accordance with applicable legal requirements.
11. Email Services
We use different email services for different functions.
Microsoft 365
Microsoft 365 hosts the info@cm-hub.io mailbox.
The account is administered for CM-HUB by authorised Op-tec Systems Ltd IT personnel.
The mailbox is used to receive and respond to business enquiries, privacy requests and other correspondence.
We retain correspondence for as long as reasonably necessary to deal with the enquiry, manage our relationship with you and maintain appropriate business records. We may retain correspondence for longer where it forms part of a contract, dispute, legal requirement or other business record that we need to preserve.
Resend
Resend is used for transactional service emails, including:
- Staff invitations.
- Staff password resets.
- Full demonstration verification codes.
When a new enquiry or call-back request arrives, Resend also sends a short alert to our own mailbox. The alert contains no details about you.
Resend processes the information necessary to deliver these messages.
The service maintains message delivery and operational records in accordance with its processing arrangements.
Resend is not used to automatically subscribe demonstration visitors to marketing communications.
12. Staff Accounts and Access Controls
Access to CM-HUB's internal website administration facilities is restricted to individually authorised users.
Staff accounts cannot be created through public self-registration.
Account information includes:
- Work email address.
- Assigned access role.
- Account status.
- Protected password hashes.
- Authentication configuration.
- Failed sign-in and security events.
Staff authentication uses two-step verification through an authenticator application.
Authentication secrets are stored within the application database, with restricted database access and protected backup arrangements.
Accounts are temporarily locked for 30 minutes after five failed password sign-in attempts.
Access permissions follow the principle of least privilege.
Op-tec personnel are provided with individual accounts where their operational responsibilities require access.
Administrative audit records
We maintain an audit trail of important administrative actions, including:
- Content changes.
- Account creation and modification.
- Sign-in activity.
- Failed authentication attempts.
- Account lockouts.
- Password resets.
- Two-step authentication configuration.
Audit records identify the relevant account, event, affected fields and event time.
They do not record password contents, visitor IP addresses or browser user-agent information.
Audit records are restricted to authorised administrators.
They are automatically deleted after 400 days.
13. Server Logs and Website Security
Our web server maintains access and security logs to protect the website and investigate technical problems.
Access logs contain technical request information, including:
- IP address.
- Requested website path.
- Request date and time.
- Browser user-agent information.
- HTTP response status.
Passwords, authentication tokens, session cookies and sensitive secret links are excluded from the logging process.
Server log retention
Server logs are managed by storage size rather than by a fixed retention period.
Each service retains up to five log files, with a maximum size of 10 MB per file.
This provides a total storage limit of approximately 50 MB per service.
When the storage limit is reached, older log files are rotated out and replaced by newer records.
The length of time that a log entry remains available therefore depends on the volume of website traffic and server activity.
On a low-traffic service, log entries may remain for several months.
There is no separate automatic deletion rule based solely on the age of a log entry.
Logs are accessible only to authorised personnel responsible for system operation, troubleshooting and security.
Spam and rate limiting
We use temporary technical controls to prevent repeated submissions and abusive access requests.
IP-based rate limits may be applied in memory to restrict excessive activity.
These controls are used for operational security and do not add IP addresses to enquiry lead records.
14. Sharing Personal Information
We share personal data only where necessary for the purposes described in this notice.
Recipients include:
Authorised CM-HUB personnel
Employees and authorised representatives who need access to perform their duties.
Op-tec Systems Ltd
Our parent company provides authorised IT, administrative and operational support.
Fasthosts
Provides the UK-based hosting infrastructure used to operate the website and associated systems.
Microsoft 365
Provides business email hosting and related communication services.
Resend
Provides transactional email delivery for staff administration, demonstration verification and internal enquiry alerts.
Supabase
Supabase provides database and authentication infrastructure for the separate full demonstration service. It processes technical and authentication information required to operate and secure the demonstration.
Acronis
Provides whole-server backup and recovery services.
Other backup and storage services
May hold operational or encrypted copies of application data for business continuity and recovery purposes.
Public authorities and legal advisers
Information may be disclosed where legally required or otherwise lawfully necessary.
We do not sell personal data.
We do not share personal information with advertisers for behavioural advertising.
15. Where Your Information Is Stored
Our website, Twenty CRM and Umami analytics operate on CM-HUB-controlled infrastructure hosted by Fasthosts in the United Kingdom.
Databases are placed on restricted networks and are not directly accessible from the public internet.
We use backup and recovery systems to protect data against accidental loss and service interruption.
These include local application-level backup arrangements and Acronis whole-server backups.
Some service providers may process or store information outside the United Kingdom.
Resend's processing arrangements include the United States.
CM-HUB is based in the United Kingdom and we aim to keep personal data within the UK or European Economic Area where practical. Some of the service providers we use may process personal data in other countries, including the United States.
Where data protection law restricts an international transfer, we use an applicable legal transfer mechanism or other safeguard required by law. Depending on the circumstances, this may include an adequacy decision or regulation, approved standard contractual clauses, the UK International Data Transfer Agreement or UK Addendum, or another recognised transfer mechanism.
You can contact us at info@cm-hub.io if you would like more information about the safeguards applying to your personal data.
16. How Long We Keep Personal Information
We retain personal information according to its purpose, the systems used and the applicable deletion or rotation arrangements.
Website copies of enquiries and demonstration leads
When you submit an enquiry or start a full demonstration, the lead is first recorded on the website server and then transferred to Twenty CRM.
A daily clean-up task clears the identifying details in the website's copy once 30 days have passed since the lead was successfully transferred to the CRM.
These include your name, work email address, company details, job role, telephone number, message and referring website information.
After identifying details have been cleared from the website's copy of an enquiry or demonstration lead, limited operational information may remain, including consent records, campaign information, timestamps and CRM references. These records are retained for consent management, administration and operational record-keeping until they are no longer required and are removed through our records management processes.
This clearing applies only to the website's copy. The CRM record is separate and is kept as described under "CRM records" below.
If a transfer fails, the website tries again automatically. If it still cannot transfer the lead, the website keeps its copy, including your details, until authorised staff resolve the problem by sending it again or deleting it. The 30 days start only after a successful transfer.
CRM records
Enquiry and demonstration lead records are kept in Twenty CRM while their purpose applies.
We review them at least every 12 months and document each review.
We delete or anonymise a lead when there is no continuing engagement, no active opportunity and no other genuine business reason to keep it.
The CRM does not currently apply an automatic deletion period based on the age of a record.
Authorised personnel manage deletion, including requests made under applicable data protection rights.
Email correspondence
Business correspondence remains in the Microsoft 365 mailbox until removed through mailbox administration or applicable records management processes.
Marketing consent
Marketing consent information is maintained as part of the relevant customer record.
Consent can be withdrawn at any time.
Information needed to record and respect an opt-out may be retained to prevent unwanted marketing.
Analytics data
We retain pseudonymous website analytics for up to 13 months. Aggregated statistics that no longer identify or relate to an identifiable visitor may be retained for longer.
Records remain in the analytics database until deleted through an administrative or database-management process.
Demonstration analytics
Analytics records from the full demonstration are kept for 13 months.
Consent preference cookie
The cmhub_consent cookie lasts 180 days.
Full demonstration cookies
The demonstration cookies last 40 minutes, 3 hours and 2 minutes respectively.
Server access logs
Server access logs do not have a fixed time-based retention period.
Each service uses size-based log rotation, with up to five files of 10 MB each.
Older log entries are removed as newer entries cause the storage limits to be reached.
Retention therefore depends on service activity and may extend to several months on a quiet website.
Temporary demonstration verification data
Plain-text email verification records are cleared through the verification and cleanup process.
Verification and rate-limiting hashes are retained for 24 hours.
Hashed demonstration start records are retained for 25 hours.
Demonstration session records
Pseudonymous demonstration session records on our website are retained for 90 days after the relevant session ends.
Records inside the full demonstration
When the full demonstration is available, records inside it are kept as follows:
- Your made-up demonstration account: blocked and deleted when your visit ends, or when you switch side or role.
- The link between your website session and your demonstration account: deleted 90 days after your visit ends.
- Your IP address and browser details in the demonstration's audit log: removed after 90 days.
- The demonstration's email log: kept for 7 days. Demonstration visitors cannot see it.
- Emails you cancel in the demonstration: deleted at the next nightly reset.
- Other demonstration email records, sent or unsent: kept for 90 days.
- Search entries created from text you type: removed at the next nightly reset.
- Files you upload: removed at the next nightly reset.
- Error log entries written while you are signed in to the demonstration: they carry your made-up account's identifier, are kept through the nightly reset and are deleted after 90 days. They can contain text you typed, for example where an error message repeats a value. Only demonstration staff who hold the error-log permission can read them.
- Error log entries written by the demonstration's servers without a signed-in visitor: they cannot be linked to you, so an erasure request cannot find them and the 90-day deletion does not apply to them. They can repeat text from an error message. Only demonstration staff who hold the error-log permission can read them.
- Bug reports you send from the demonstration: kept, with no fixed period, through the nightly reset. They are text only, checked and shortened when you send them, and show only the made-up account as the sender; once the link to your session is deleted after 90 days, a report can no longer be tied back to you. If you ask us to erase your data before then, your bug reports are deleted.
- Data exports: not possible in the demonstration, so none are created.
- Sign-in logs and web server access logs kept by the services that host the demonstration: kept for the periods those services set, and not changed by an erasure request.
If you ask us to erase your data, some of these records go sooner, as set out in section 9.
Demonstration error and sign-in records are maintained for operational security and troubleshooting. Where records can be associated with a visitor and are controlled by the demonstration application, applicable records are removed when an erasure request is fulfilled. Separately maintained hosting-service logs follow their own retention arrangements.
The full demonstration maintains a tamper-evident audit log for security and accountability. Visitor IP addresses, browser details and session associations are removed according to the applicable 90-day retention arrangements.
The underlying audit entries are retained to preserve the integrity of the audit history. These entries may include text entered into demonstration records, which could contain identifying information.
If you use AI troubleshooting, the audit entries also include the text of the run, such as outcome notes, a session summary and the evidence for each step. These entries are kept through the nightly reset, like the other audit entries described above.
AI usage records are also kept through the nightly reset. Each one shows the simulated model used, the number of tokens, how long the step took, and the identifiers of the case and the site. A usage record holds no text.
The filter keeps the original details it replaced, such as an email address or a name, until the next nightly reset, when they are cleared. Until then only our highest-level administrators can read them. This does not change the audit entries described above, which can still hold text you typed.
We restrict access to these records and use them for security, accountability and investigation purposes. Requests concerning personal information retained within audit entries are considered in accordance with applicable data protection rights and legal requirements.
Visitors are instructed not to enter real personal information or confidential material into the demonstration.
Transactional email records
Transactional email delivery information is retained by Resend according to its service retention arrangements.
Staff accounts
Staff account information is maintained while the relevant account remains authorised and required.
Administrative audit records
Website administrative audit records are retained for 400 days.
Application-level backups
We maintain backups for business continuity and disaster recovery. Personal data deleted from our live systems may remain in protected backup copies until those backups expire through their normal retention cycle. Backups are not used for normal business purposes. Where a backup is restored, applicable deletion requests and retention controls are reapplied.
17. How We Protect Personal Information
We maintain technical and organisational security measures to protect personal information.
These include:
- HTTPS encryption for website connections.
- Restricted administrative access.
- Private database networks.
- Individual user accounts.
- Role-based access permissions.
- Two-step authentication for staff.
- Account lockout protection.
- Security monitoring.
- Administrative audit trails.
- IP-based restrictions for sensitive management systems.
- Backup and recovery arrangements.
- Data minimisation.
- Controlled access to customer records.
These measures are designed to reduce the risk of unauthorised access, accidental loss, misuse, alteration and disclosure.
Access to personal information is limited according to legitimate business responsibilities.
18. Automated Processing and Decisions
We use automated checks to protect our website and demonstration services from spam, excessive requests and misuse.
These include restrictions on enquiry submissions, verification code requests and demonstration access attempts.
These checks do not make decisions that produce legal or similarly significant effects on individuals.
Where an automated security control prevents an action, visitors can retry later or contact info@cm-hub.io.
We do not use automated profiling to make legally significant decisions about website visitors.
19. Your Data Protection Rights
We respect the following rights regardless of where you are located, subject to any limitations or exceptions under applicable law. You may ask us to:
provide a copy of the personal data we hold about you;
correct inaccurate or incomplete personal data;
delete personal data we no longer need;
restrict how we use your personal data in certain circumstances;
stop using your personal data for direct marketing;
consider an objection to other processing based on our legitimate interests;
provide personal data you supplied to us in a portable format where applicable; and
withdraw consent where our processing is based on your consent.
You will not be discriminated against or receive a lower level of service because you exercise a privacy right.
Exercising your rights
Contact:
Email: info@cm-hub.io
Post: CM-HUB LTD, Stockport Business & Innovation Centre, 3rd Floor Broadstone Mill, Broadstone Road, Stockport, SK5 7DL, United Kingdom.
We may need to verify your identity before acting on a request. We aim to respond within one month, or sooner where applicable law requires it. Some rights are subject to legal limitations and we will explain those if they apply.
UK and European Economic Area
If you are in the United Kingdom, our processing of your personal data is subject to the UK GDPR and the Data Protection Act 2018.
Where the EU GDPR applies to our processing, individuals in the European Economic Area have the rights provided by the EU GDPR in addition to any other rights described in this notice.
If you are in the UK, you have the right to make a complaint to the Information Commissioner's Office (ICO). If the EU GDPR applies to our processing, you may also have the right to lodge a complaint with the competent supervisory authority in the relevant EU Member State.
We would appreciate the opportunity to resolve any concern first, so you are welcome to contact us at info@cm-hub.io before making a complaint.
Visitors in the United States
Depending on the state in which you live and whether the relevant privacy law applies to CM-HUB LTD, you may have additional rights concerning your personal information. These can include rights to access, correct or delete personal information and to opt out of certain uses or disclosures.
CM-HUB does not sell personal information or use personal information for behavioural advertising. We will not discriminate against you for exercising a privacy right.
You can make a privacy request by emailing info@cm-hub.io. We will apply the rights described in this notice wherever reasonably possible, regardless of whether a particular state privacy law requires us to do so.
20. Complaints
We take privacy concerns seriously.
If you have a concern about how your information has been handled, contact info@cm-hub.io.
We investigate privacy complaints and respond in accordance with applicable legal requirements.
You can also complain directly to the Information Commissioner's Office (ICO), the United Kingdom's independent data protection regulator.
ICO website: https://ico.org.uk
ICO complaints: https://ico.org.uk/make-a-complaint/
You do not need to contact CM-HUB before exercising your right to complain to the ICO.
21. Information About Children
The CM-HUB website and demonstration services are intended for business users and individuals interested in our products and services in a professional capacity.
They are not directed towards children.
We do not knowingly collect children's personal data for marketing or demonstration lead-generation purposes.
22. Privacy Within the Full Demonstration
The full CM-HUB demonstration operates as a separate environment.
The website's collection of information before entry is described in section 9.
The demonstration uses example accounts and illustrative information.
Visitors' real names and email addresses are not transferred into the demonstration application.
Demonstration access is managed using session identifiers and the side, role and module or package you select.
The full demonstration runs on its own Supabase project (section 14), separate from the live CM-HUB service that customers use. It uses a fictional company, Quillmere Foods, and synthetic data only. It holds no customer data, so what you enter never sits beside real customer records. If you choose the contractor side, you use the demonstration as a member of a fictional contractor firm, Torvane.
The demonstration is a shared sandbox. The CM-HUB demonstration team can see what you enter, including files you upload. Do not enter personal or confidential information.
Files you upload
You can upload PDF, JPEG, PNG, WebP and HEIC files of up to 10 MB each. A file you upload can be seen by you and by the CM-HUB demonstration team. It is removed at the next nightly reset.
Simulated services
Some services in the demonstration are simulated inside the demonstration service: AI troubleshooting and AI search, text recognition in documents (OCR), virus scanning, data from connected equipment (MQTT) and email (shown to you, never sent). Code and tag scanning and voice dictation happen on your device: camera images and audio do not leave your device.
Voice dictation is optional. The first time you tap the microphone, your browser asks for permission to use it, and the demonstration downloads speech-recognition software and a model of about 60 MB from our demonstration service to your device, once for each of the two demonstration apps you use it in. They are kept in your browser's storage so that they do not need to download again. A short message also tells you that your voice stays on your device. Your speech is turned into text on your device: the audio is not recorded and is not sent to us or to anyone else. The software and model contain no personal data; you can remove them by clearing this site's data in your browser.
The demonstration never sends email. Where it would send one, for example to a supplier, as a case notification or as an invitation, you see a short notice, and the email is shown to you instead in a view called "Emails CM-Hub would send", with its sender, recipients, reply-to address, subject and text. You see only the emails that your own actions produced. Emails are shown to you, not sent, and nothing leaves the demonstration.
Demonstration analytics
Analytics in the full demonstration are always on. They do not depend on the analytics choice you make on our website, and there is no setting to turn them off.
We record these events about your visit:
- the start of your visit, with the side, role and module or package you chose;
- each page you view, recorded as the app and the pattern of the page address, without the identifiers of the records on the page;
- each guided walkthrough step you complete, with its module and step number, and which walkthrough you finish;
- when you change the guide mode, and the mode you choose;
- offers you take up;
- switches of side or role, with the side and role before and after;
- when you open an email that the demonstration would have sent;
- the end of your visit and how it ended: after 30 minutes without activity, with the "End my demo" button, or at the end of the visit's time.
Each event holds only values from fixed lists. It holds no text you type, no names and no identifiers of records in the demonstration. The page title, the referring page, your browser language and your screen size are not sent.
Only visitor accounts send these events; CM-HUB team accounts do not. The demonstration keeps no copy of them.
The events are sent from your browser to Umami, our self-hosted analytics platform described in section 6. Umami sees your IP address and keeps only its pseudonymous visitor identifier, which is calculated with a value that changes each month. The events are kept in a separate analytics site for the demonstration and are not mixed with website analytics.
The web server in front of Umami also records your full IP address and browser details in its access log, which is kept by size, as described in section 13.
Each event carries a random analytics identifier made for your visit. It is not your session identifier. It stays the same when you switch side or role, and a new visit gets a new one. The events carry no name or email address.
The demonstration apps hold the analytics identifier only in memory while a page is open. It is not stored on your device, in a cookie or in any other browser storage, and it is gone when you close the tab or app. No analytics data or analytics key is stored on your device. The apps do store your demonstration sign-in in your browser, and the Field app keeps an offline store on your device; these hold no analytics data and are cleared when your visit is cut off and at the nightly reset. If you use voice dictation, each app also keeps its speech-recognition software and model (about 60 MB) in your browser's storage; they hold no personal data and no analytics data, and you can remove them by clearing this site's data in your browser.
Inside the demonstration, the analytics identifier is kept with the link between your website session and your demonstration account, which is deleted 90 days after your visit ends (section 16). On our website, we link that identifier to your demonstration lead, which holds the work email address you verified, so the events are associated with you. Because every event carries that identifier, the events can be found and deleted if you ask us to erase your data.
Demonstration analytics records are kept for 13 months, as set out in section 16.
AI in the demonstration
AI troubleshooting in the full demonstration is simulated. It runs inside the demonstration service and answers with prepared replies. The text you type, the answers you give and the details of the case, the asset and related records are not sent to any external AI provider.
Text that you save in demonstration records, such as cases, case notes, asset notes, documents and maintenance reports, is processed inside the demonstration service to make it searchable. It is not sent to any external AI provider. This happens even if you never use AI troubleshooting.
An automatic filter replaces some details before the simulated AI uses the text, such as email addresses, phone numbers, web and network addresses, serial numbers and some names. The filter can miss things. Do not enter personal or confidential information.
Photos and files themselves are not used, but their titles and descriptions are.
The nightly reset
When the full demonstration is available, it resets every night from 01:00 UK time, all year. On the night the clocks go forward, when 01:00 does not happen, it starts at 02:00. From then no new visits start and no one can switch side or role; visits already running can finish, for up to 3 hours. New visits can start again when the reset is done, at the latest 3 hours 30 minutes after it started: 04:30 UK time on most nights, 05:30 on the night the clocks go forward and 03:30 on the night they go back.
During the reset:
- the made-up visitor accounts are blocked and deleted;
- the business data goes back to the made-up company's starting point, and files that visitors added are removed;
- unsent and cancelled visitor emails, readings for deleted equipment, and search entries made from visitor text are cleared;
- the original details kept by the AI filter are cleared;
- the demonstration's safety settings are applied again.
If the demonstration is switched off, the same clear-out runs straight away.
What is kept through the reset
The demonstration's audit log, email log, bug reports and error log are kept through the reset. How long each is kept is set out in section 16 under "Records inside the full demonstration".
Demonstration audit records use demonstration account identifiers rather than visitor contact details.
The audit log will also hold your IP address and browser details for 90 days, after which they are removed.
If you use AI troubleshooting, the audit log also keeps the text of the run, such as outcome notes, a session summary and the evidence for each step. AI usage records, which show the simulated model, token counts, timing and case and site identifiers but no text, are kept through the reset as well. Section 16 gives the details.
The demonstration's email log is kept for 7 days and cannot be seen by demonstration visitors.
Visitors should avoid entering real names, personal data, confidential information or sensitive business information into demonstration fields.
23. Changes to This Privacy Notice
We review this Privacy Notice when our services, processing activities or applicable legal requirements change.
Updates are published on the CM-HUB website.
The effective date is updated to reflect changes to the notice.
Where required, we provide additional information about material changes affecting personal data processing.
24. Contact Us
If you have questions about this Privacy Notice, our processing activities or your data protection rights, contact:
CM-HUB LTD
Stockport Business & Innovation Centre
3rd Floor Broadstone Mill
Broadstone Road
Stockport
SK5 7DL
United Kingdom
Email: info@cm-hub.io
Website: https://cm-hub.io
Effective date: 15 November 2026