Bexford privacy notice Version: 2026-11-02-starter-v1 This notice covers Bexford’s free customer workspace, website visitors, early-access requests and customers who choose a Starter subscription. Selecting Starter or creating an account does not itself start a payment. Payment details are entered separately on Stripe’s hosted pages. Bexford does not automatically contact prospects on your behalf. Who is responsible for your information Daniel Mclearnon, a sole trader trading as bexford intelligence, is responsible for personal information handled through this website. Business correspondence address: Shean, Seaforth Road, Muir of Ord, IV6 7TA, United Kingdom. Privacy enquiries: hello@bexfordintelligence.co.uk Your Bexford account and business brief Signup asks for your business name, what you sell, ideal customers, selling method, service area and email address. Unfinished answers can remain in this browser tab for up to 24 hours and can be deleted on the review screen. Submitted pending answers are stored for up to 24 hours while you complete verification; submitting the form alone does not verify your identity. Customers sign in using Google or a one-time email code sent by Bexford. Google sign-in provides a verified account identity and email address; it does not by itself give Bexford permission to read your Gmail. An existing email-code account may need to verify its mailbox when linking Google. Authentication and workspace cookies maintain your session. DEVELOPMENT is a separate test environment with restricted access. Your organisation’s brief, prospect workspace, private notes, recorded contacts, pipeline stages, activity and follow-ups are kept separate from other customers’ private workspaces. The free-prospect ledger records which prospects have been unlocked so repeat sign-in or changes to your brief do not create a new free allowance. Research may use permitted sources and budget-limited AI processing to fulfil your request. No payment or automated prospect outreach is activated by signing up. Information we collect When you register interest, we collect your contact name, business name, business email, main trade, service or product, operating regions and selected service tier. You may also provide a website, project preferences, value range and additional requirements. Optional marketing consent is recorded separately. Cloudflare may process technical information such as IP addresses and request logs to deliver and protect the website. The pilot stores short-lived hashed email/IP identifiers for rate limits. Authentication and workspace cookies maintain your secure session; browser session storage preserves unfinished answers. The legacy website request handler stores an hourly IP-derived identifier with accepted early-interest registrations. Why and how we use it We use registration details to review your request, assess whether bexford may be relevant to your business, contact you about the selected service and administer the early trial. This is separate from optional marketing communications. For an individual contracting with Bexford, including a sole trader, we use information needed to take requested steps before a contract and to perform that contract. Where you represent a company, we use relevant business-contact information for our legitimate interests in responding to enquiries, administering the company’s account and providing the requested service. We use relevant information to comply with applicable legal record-keeping duties and for our legitimate interests in security, preventing fraud, enforcing account allowances and resolving billing disputes. Optional marketing relies on the separate choice shown on the form and can be withdrawn at any time. Refusing optional marketing does not prevent use of the service. B2B market assessments and company research A market assessment brief may include your products or services, ideal customer industries, sales territory, exclusions and requested prospect count. It is used to prepare the requested research, not to start marketing campaigns or a subscription. Your brief and customer-specific qualification records are private to your account. Company research uses permitted public business sources. Published business information can still contain personal data. We distinguish facts from assessments, record source provenance, restrict access and support corrections, suppression and deletion requests. Customers can record named business contacts in their private workspace. A recorded name is not a claim that the person has consented to marketing. Public company records are not evidence of consent to marketing. Inactive free assessment requests should be reviewed after 90 days. Account and customer deliverables are retained for the active customer relationship and for as long afterwards as needed for requested access, corrections, support, disputes or applicable legal duties. Deletion is handled through a verified support request and is not automatic when a subscription is cancelled. We assess what can be removed and what limited records remain necessary; provider recovery copies may remain until their recovery period expires. Starter subscriptions and Stripe If you choose a paid subscription, Stripe receives the account/business name, email and billing information needed to administer payment. Stripe’s hosted Checkout and portal collect payment details and support payment-method updates, invoices, receipts, payment recovery and cancellation. Bexford’s application does not receive full card numbers or card security codes. Bexford stores the Stripe customer and subscription identifiers associated with your private account, plan, billing-period and payment status, supplied-lead allocations, webhook/event-processing identifiers and timestamps, and the versions/hashes of the terms and privacy notice accepted by the account owner. The acceptance record also identifies the accepting account user and time. These records link payment to the correct account, prevent duplicate processing and support billing questions, fraud/dispute review and allowance enforcement. Bexford does not use a payment or billing email as consent to marketing. Stripe processes payment information under its own privacy policy (https://stripe.com/privacy). Its role depends on the processing: it can act as our processor to provide payment services and independently as a controller for purposes such as fraud prevention, financial compliance and operating its services. The relevant responsibilities are described in Stripe’s Data Processing Agreement (https://stripe.com/gb/legal/dpa). Billing and legal-acceptance records have no automatic expiry in the current application. On a verified deletion request, we assess the records needed for financial/legal duties, existing disputes, security and the history of supplied leads, minimise information that is no longer needed and remove applicable records through the controlled support process. Ending renewal stops future renewal charging; it does not itself delete billing or CRM history. Storage, sharing and security The live customer pilot uses a separate Cloudflare Worker and D1 database from DEVELOPMENT. It stores verified account membership, your criteria, unlocked prospects and private notes. Approved company-level factual evidence may be reused across customers; private criteria, assessments and notes are not copied between customers. The legacy early-interest request form uses a separate website database. A failed submission is not confirmed as stored. We do not sell personal information. Data may be handled by service providers only where needed to host the site, secure the form or operate the service, or where required by law. Your account information is accessible to your authorised organisation members and the service owner for operation/support; other customers cannot access it. Website code does not contain database credentials or unrestricted storage access. How we protect sensitive Google user data We use HTTPS/TLS to protect information in transit between your browser, Google and Bexford. Bexford account, connection and private CRM records are held in Cloudflare D1, which encrypts stored databases and their metadata at rest using AES-256 with Cloudflare-managed keys. Worker-to-D1 connections use TLS. Server credentials are held in encrypted Cloudflare Worker secrets, rather than delivered to the browser or included in public website code. The Gmail endpoint verifies Google-signed deployment and user identity tokens, including their intended audience, issuer and expiry. Each request checks the linked Google identity, an enabled Bexford organisation membership and the current connection receipt before displaying private prospect information. Customer workspace queries are scoped to the authorised organisation; write permissions and record versions protect changes. Disconnecting invalidates the connection and stale sidebar actions. DEVELOPMENT and LIVE use separate application databases. Temporary Gmail access tokens and the current email’s fetched headers are processed in server memory for that request. They are not saved to Bexford’s database or deliberately included in application logs. The add-on does not retain a Gmail refresh token. Responses containing private information use no-store caching controls. Infrastructure providers may process technical request metadata to operate and secure their services. Access to stored private information is restricted to authorised organisation members and authorised service administration. Human access to Google user data is limited to the user’s documented agreement for specific data, security investigation, legal requirements, or the other exceptions allowed by Google’s Limited Use requirements. We do not sell Google user data, use it for advertising, share it with contact-data providers or copy private Gmail-derived information into the shared company directory. Google data, AI, retention and deletion The current Gmail add-on uses only the open email’s From, To and Cc metadata to match existing prospects. It does not read message bodies, attachments or mailbox history, generate thread summaries, create Gmail drafts or automatically log email activity. Google receives the CRM card information needed to display the sidebar. Cloudflare hosts Bexford’s application and stored records. Current Gmail metadata is not sent to an AI provider. Separately, Bexford’s company-research features may use OpenAI to process the customer’s saved business brief and permitted research evidence; this is not permission to process Gmail messages. Bexford does not use, or permit providers to use, Google user data or data derived from it to create, train or improve general-purpose, foundation or frontier AI models. Any future email summarisation or reply-assistance feature will require appropriate permissions, clear disclosure and any required renewed consent before that processing begins. Fetched Gmail headers and temporary tokens are not retained after request processing. We retain the account email, linked Google identifier, connection choice, policy version, connection/disconnection timestamps and a generation counter that rejects stale actions. Connection receipts have no automatic expiry or deletion schedule. They remain until removed through a verified deletion request. CRM notes, activity and follow-ups that you choose to save remain with your private workspace until deleted or the applicable account-retention process is completed. Disconnecting or uninstalling stops future access but does not itself erase these saved records. To request access, correction or deletion of Bexford-held account, connection or private CRM information, contact hello@bexfordintelligence.co.uk. We verify your authority, review any legal retention obligations and remove the applicable records through a controlled support process; deletion is not automatic on disconnect. Service-provider recovery copies may remain for their recovery period before expiry. You can separately revoke Google permission through Google account connections (https://myaccount.google.com/connections). Bexford’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy) and the Google Workspace API User Data and Developer Policy (https://developers.google.com/workspace/workspace-api-user-data-developer-policy), including the Limited Use requirements. Optional Gmail add-on The optional Gmail add-on has separate Google permissions and a Connect Bexford choice. Read the Gmail privacy information for how it accesses, uses, stores and shares data, and how to disconnect. Customer installation is not available yet. Retention and deletion Unsuccessful or inactive early-interest registrations should be reviewed and deleted within 12 months. Details needed for an active customer relationship or legal record may be retained for longer under the applicable business retention policy. You may ask for deletion sooner using the privacy contact above, subject to any legal requirement to retain information. International processing Our providers can process personal information outside the United Kingdom, including in the United States. Cloudflare’s Data Processing Addendum (https://www.cloudflare.com/cloudflare-customer-dpa/) and Stripe’s Data Processing Agreement and Data Transfers Addendum (https://stripe.com/legal/dta) describe their applicable responsibilities and international-transfer arrangements, including standard contractual clauses and the UK transfer addendum where required. Stripe’s transfer terms also provide for the Data Privacy Framework when applicable. These services are not represented as UK-only storage. Contact hello@bexfordintelligence.co.uk for information about the applicable provider arrangements or a copy of relevant safeguards. Your rights UK data-protection law may give you rights including access, correction, deletion, restriction, objection and data portability, depending on the processing and lawful basis. You can object to processing based on legitimate interests and to direct marketing. You can withdraw optional marketing consent at any time. You may also complain to the Information Commissioner's Office at ico.org.uk (https://ico.org.uk/). Cookies and marketing This site does not intentionally use analytics or advertising cookies. Choosing to receive the requested service or be contacted about it is not treated as consent to unrelated marketing. Last updated: 2 November 2026