Privacy notice

1. Identity and contact

BridgeBot is operated by Bridge The Gap Sales Ltd, company number 17123996, registered office: Marron Bank, Branthwaite, Workington, United Kingdom, CA14 4SZ.

Privacy, rights requests and complaints: bridgethegaphq@gmail.com, or write to the registered office marked “Data protection”. A dedicated privacy inbox must be provisioned and tested before it is advertised. ICO fee registration/payment evidence remains outstanding; no registration number or exemption is asserted.

2. Different uses of BridgeBot

This common notice covers accounts, billing, security and simulated practice. Read the separate public subscriber CRM notice or BTG programme CRM notice for third-party contact data. The products have different purposes and access rules; one role allocation is not assumed to cover both.

BTG acts as controller for its account administration, billing and security purposes. Allocation of CRM roles, lawful bases and any joint responsibilities is subject to written adviser approval. Providing hosting does not determine our role for compulsory coaching.

3. Information and purposes

Account data includes email, optional name, authentication identifiers and access decisions. Billing records include Stripe customer, checkout and subscription references and payment history; card entry is handled by Stripe. Training records include fictional roleplay messages, generated personas, scores and analyses. Security data includes IP addresses, device/request metadata and access events.

CRM separately holds real prospect names, social handles, offers, business notes, activities and reminders entered by a member. Prospects may never have visited BridgeBot. Do not put real prospect information into simulated training transcripts, or sensitive or unnecessary personal details into CRM notes.

4. Bases and choices

Proposed bases for account and practice delivery are performance of the user contract; statutory accounting duties for required billing records; assessed legitimate interests for security and fraud prevention; and consent for optional analytics and marketing where required. CRM prospect processing requires a separate documented basis, not the prospect’s supposed agreement to a subscriber contract. Final bases and legitimate-interest assessments require approval.

Optional analytics require a consent choice. Rejecting optional cookies does not prevent essential sign-in. See the cookie notice.

5. Providers and communications

Simulated training content is transmitted to configured AI providers for inference. CRM endpoints make no AI calls. Provider retention, training-use restrictions, processing countries, contracts and transfer mechanisms must be verified; we do not claim data exists at a provider only during a request.

Our internal welcome-email queue stores references and delivery/retry metadata, not a copied email body or recipient address. To send an email, Resend receives the recipient address and the rendered message body, including a sign-in link where applicable. These are different processing stages. A provider-accepted message cannot necessarily be recalled.

The vendor register distinguishes observed deployment locations from unresolved vendor processing/support locations. No blanket assertion is made that agreements, IDTAs or UK-US data-bridge coverage have been verified.

6. Closure and retention

Local implementation draft, not deployed: AI spending controls record an account reference, reserved and recorded cost amounts, and timestamps, without prompts or conversation content. These records are included in self-service exports. Closure removes their account link while retaining platform accounting amounts so uncertain charges cannot reopen spending limits. Operational cleanup and retention of this accounting metadata still require adviser review and implementation before launch.

A member can export their data and request closure using Your data. The current self-service workflow requires a saved export confirmation. A person can also request erasure by email or post without using that workflow or purchasing a subscription. BTG must assess requests independently of the export requirement.

Current closure disables access, removes profile name/email and deletes live CRM leads, their activities/reminders and queued welcome-delivery records. Training, billing and authentication records currently require separate retention work and may still identify a closed user. Closing an account is not proof that every copy is erased.

Revised retention targets for adviser approval and implementation: training content deleted on account closure unless a specific documented legal hold applies; security/authentication event logs kept for 90 days; required billing records kept for six years after the relevant financial year; recovery backups expire within a proposed 35-day maximum. No general post-closure training purpose has been established. Lapsed accounts that remain open need a separately agreed inactivity/deletion rule.

These shorter targets are NOT yet enforced or represented as current configuration. Existing recovery code checks 365 days for current backup versions plus 365 days after a version becomes noncurrent, which can approach two years before final removal; provider deletion timing must also be checked. The earlier “up to 365 days” claim was insufficient. Live lifecycle changes, noncurrent-version deletion, provider retention and deletion-job evidence are launch blockers.

An independently durable closure register is not yet demonstrated. Restoration must stay isolated and blocked unless current closure information can be verified and closed-account data purged. This is a release requirement, not a claim that end-to-end recovery erasure is operational.

7. Rights and transparency

Depending on the processing and applicable law, individuals may request access, correction, erasure, restriction or portability and object to processing. Contact BTG by email or post; you do not need a BridgeBot account. We may need proportionate identity verification and will explain any lawful restriction. If you are unhappy with how we handle your information you can complain to us — see the complaints route; we aim to acknowledge a complaint within 30 days and respond without undue delay, and you do not need an account to complain. You can also complain to the ICO.

For indirectly collected prospects’ data, the responsible controller must provide the applicable Article 14 information within the required time, normally no later than one month and earlier at first communication or disclosure where applicable. BTG must not assume a member’s promise discharges BTG’s own duties. Notices, responsibilities and any claimed exemption need documented adviser approval before CRM launch.

8. Security and updates

Access controls include user-scoped CRM queries, explicit coach assignments, privileged MFA and protected backend requests. These controls do not establish compliance by themselves. Vendor evidence, operational incident handling and retention remain subject to the launch review.

This document is a dated draft. Material changes will be communicated by appropriate means under the applicable legal and contractual requirements; no unimplemented blanket email-notification promise is made.