Gmail privacy · gmail-2026-10-27-v1
Your prospects, beside your email.
Bexford Intelligence provides an optional Gmail add-on for viewing and updating the prospect records you can already access in Bexford.
Who operates Bexford
Daniel Mclearnon is a sole trader trading as bexford intelligence. Business correspondence address: Shean, Seaforth Road, Muir of Ord, IV6 7TA, United Kingdom. For privacy enquiries, email [email protected].
What Google permissions allow
The add-on requests your Google account email identity, permission to run in Gmail, and temporary access to metadata for the email currently open. When the add-on is active, it reads only the From, To and Cc headers to find a saved prospect. It does not fetch the subject, message body, attachments, other messages or inbox history.
Your choice to connect
After Google permission and Bexford sign-in, you choose Connect Bexford before any email matching or private prospect display. Google identity alone never grants access to another customer’s records. Each request checks your linked Google identity, enabled Bexford membership and current connection choice.
How information is used and shared
Current-message addresses are used in memory to match your permitted prospect records. Bexford returns the matching record, its saved contact details, private notes, stage, follow-ups and recent activity to Google so Gmail can display the card. Google processes this information to provide the add-on interface. Bexford’s application and account records are hosted by Cloudflare. Header data is not sold, used for advertising, disclosed to contact-data providers or sent to an AI model. Bexford does not use, or permit providers to use, Google user data or derived data to create, train or improve general-purpose, foundation or frontier AI models. Current Gmail data is not sent to AI providers.
Protection of sensitive data
HTTPS/TLS protects data in transit. Stored account, connection and private CRM records use Cloudflare D1 encryption at rest (AES-256, Cloudflare-managed keys); server credentials use encrypted Worker secrets. Google-signed deployment and identity tokens, organisation membership, role checks and connection-generation checks protect access. Private responses use no-store caching. Temporary Gmail tokens and fetched headers are processed in memory, without database persistence or deliberate application logging. Read the main privacy notice for security, sharing, human access, AI restrictions and deletion details.
What is stored
Google tokens, message IDs and fetched headers are not persisted or included in application logs. We store your account email, linked Google account identifier, connection choice, policy version, timestamps and a connection-generation counter used to reject stale actions. Disconnecting records the disconnection rather than automatically deleting that receipt. Notes, stage changes, follow-ups and activity entries you explicitly save are stored in your private Bexford workspace. Opening an email creates no contact-history entry and sends no email.
Disconnecting and deleting data
Use Disconnect Gmail in the sidebar or on the Gmail setup page. This blocks subsequent sidebar access; an already displayed card may remain visible until Gmail closes or refreshes it. Your saved Bexford records remain available on the website. You can separately remove Google’s permission through your Google account connections and uninstall the add-on. For access, correction or deletion of Bexford-held information, email [email protected]. Connection receipts have no automatic expiry; they remain until a verified deletion request is completed. Saved CRM records remain until deleted or the applicable account-retention process is completed. Deletion is handled through verified support, subject to legal requirements and service-provider recovery-copy expiry. The main Bexford privacy notice covers account records and retention.
Availability and updates
The current production trial is restricted to [email protected]. Public customer installation and Google Marketplace review are not complete. Changes to Google data access or use will be disclosed before the changed processing begins, with a new connection choice where required.
Limited Use
Bexford’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Security disclosure updated: 28 October 2026. Google verification remains pending; this update does not grant additional Gmail permissions.