Legal

Privacy policy

Last updated 9 November 2026Bridgehead Communications Ltd

Glister is operated by Bridgehead Communications Ltd ("Glister", "we", "us"). This policy explains what we collect, why, and what a care provider controls when they use Glister.

What we collect

  • Account details: your name, email address, and the provider profile you create (name, postcode, care type, CQC data we look up on your behalf).
  • Content you create in Glister: campaigns, landing page copy, press releases, newsletters, review replies, and media contact lists.
  • Enquiry data captured through your hosted landing pages (name, contact details, message). This belongs to you, not us.
  • Connected-account data: if you connect Google Ads, Meta Ads, Google Business Profile, a Facebook Page, an Instagram professional account, a LinkedIn Company Page, Gmail, or Outlook, we store an access token so Glister can act on your behalf, and the minimum account identifier needed (e.g. your ad account ID, Page ID or connected mailbox address).

Gmail and Outlook access

If you connect Gmail or Outlook, Glister requests permission only to send email as you, specifically the gmail.send or Microsoft Graph Mail.Send scope. Glister cannot read your inbox, your contacts, or any other email through this connection. Every send using this connection happens only when you click send on a specific press release or newsletter inside Glister; nothing is sent automatically or without your review. You can revoke this access at any time from Glister's Connections page, or directly from your Google or Microsoft account security settings.

Google user data

If you connect a Google account, Glister asks Google only for the access each feature needs:

  • Gmail (gmail.send and your email address): to send a press release or newsletter from your own address when you press send. Glister cannot read, search or delete your email.
  • Google Business Profile (business.manage): to list the locations you manage, read the reviews on the one you choose, post the replies you approve and publish the posts you schedule.
  • Google Ads (adwords): to list the ad accounts you can reach, create the campaigns you approve in the one you choose, and read their daily results, such as impressions, clicks and spend.
  • Google Analytics (analytics.readonly): to list the Analytics properties you can read and, for the one you choose, read your website's daily visits, where they came from, your top landing pages and your key events. This access is read-only: Glister cannot change your Analytics settings or data.

We store the access token Google issues, the ID and name of the account or location you choose, and the records Glister creates there: posts, review replies, campaigns and their results. From Google Analytics we store the last 90 days of totals for the property you choose (visits, engaged visits and key events by day, by channel and for your top landing pages), never data about individual visitors, and we delete them when you disconnect. Reviews from your Business Profile are stored so you can read and answer them in Glister. When Glister sorts a review or drafts a reply to it, the review text is sent to Anthropic's API for that purpose only, and Anthropic does not use API inputs to train its models.

Glister's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features above. We do not sell it, use it for advertising, or let anyone read it except with your permission, for security or where the law requires. We do not use it to develop, improve or train generalised AI or machine learning models.

Disconnecting a Google account on Glister's Connections page deletes the stored access token straight away. You can also remove Glister at any time from your Google Account under Third-party apps and services.

Facebook, Instagram and LinkedIn access

If you connect a Facebook Page, Glister asks Meta for permission to list the Pages you manage, read basic details of the Page you choose and of the Instagram professional account linked to it, and publish posts and photos to them. If you connect Meta Ads, Glister asks for permission to create and manage campaigns in the ad account you choose and to read their results. If you connect LinkedIn, Glister asks for permission to see which Company Pages you administer and to publish posts to the one you choose.

From these connections we store the Page or ad account ID and name, the Page and Instagram profile picture and username, the access token the platform issues, and, for each post Glister publishes, the post ID, its link and whether it went out. For Meta Ads we also store the IDs of campaigns Glister created and their daily results, such as impressions, clicks and spend. Glister does not read your personal Facebook profile, your friends or followers, your messages or the comments on your posts.

Glister publishes only posts you have written or approved and then scheduled or sent yourself, and changes ads only when you ask it to. We use this data solely to provide those features to you. We do not sell it, use it for advertising or profiling, or share it with anyone other than the infrastructure vendors listed below.

Disconnecting Facebook, Instagram, Meta Ads or LinkedIn on Glister's Connections page deletes the stored access token and Page details straight away. You can also remove Glister from Facebook under Settings & privacy, then Business integrations. To have the rest of your data deleted, including post history, follow our data deletion instructions.

How we use it

  • To operate the product: generate campaigns, host your landing pages, track enquiries, and run your local Presence Score.
  • To send email you ask us to send: press releases, newsletters, and enquiry notifications.
  • To improve accuracy: e.g. matching your profile to the correct CQC registration.
  • We do not sell your data, and we do not use your connected Gmail/Outlook data for advertising.

Who we share it with

We use a small number of infrastructure vendors to run Glister: Vercel (hosting), Neon (database), Resend (transactional email when you haven't connected your own mailbox), Anthropic (AI drafting of campaign copy and press releases), Ahrefs (SEO metrics, only if you've provided a website address), and Vercel Web Analytics and PostHog (counting visits and how the site is used, without cookies). We do not share your data with anyone else except where required by law.

How we protect your data

The measures below cover everything Glister holds, including the data and access tokens we receive from Google, Meta, LinkedIn and Microsoft when you connect an account.

Encryption in transit

Glister is served only over HTTPS. A request made over plain HTTP is redirected to HTTPS, and every response tells your browser to use HTTPS for Glister for the next two years (HTTP Strict Transport Security). Glister's servers reach our database, and the Google, Meta, LinkedIn and Microsoft APIs, over TLS-encrypted connections too, so your data and your access tokens are encrypted whenever they move between systems.

Encryption at rest

Glister's data is stored in a PostgreSQL database run by Neon on Amazon Web Services in the US East (Northern Virginia) region. Neon encrypts all stored data with AES-256, using keys managed in AWS Key Management Service, and its backups are encrypted the same way. Access tokens for connected accounts are held in that database. They are used only by Glister's server code when it acts for you, and they are never sent to your browser or shown anywhere in Glister.

Because that database is in the United States, UK personal data is transferred there. Neon's data processing agreement covers the transfer with the European Commission's Standard Contractual Clauses and the International Data Transfer Addendum issued by the UK Information Commissioner's Office.

Who can see your data

  • Inside Glister, a provider's data is visible only to the people who are members of that provider: the person who created it and anyone they invite. Glister checks membership on the server before it shows or changes any of a provider's data, and the provider's owner can remove members at any time.
  • You sign in with a single-use link emailed to you, which expires after an hour, or with a password. We store passwords only as scrypt hashes, never in readable form.
  • Bridgehead staff see a provider's data in Glister only if that provider has added them as members, as happens when we run Glister for you as a managed service. A short list of named Bridgehead staff can also open the group accounts we operate for organisations with several locations. That list is held in our hosting configuration, not in the app, and each time one of them opens an organisation they are not a member of, Glister records who did it.
  • Direct access to the production database and hosting accounts is limited to the named Bridgehead staff who administer Glister. They use it only to run, support and secure Glister, or where the law requires.

How long we keep it

We keep an access token only while the account stays connected. Disconnecting an account on Glister's Connections page deletes its stored token and refresh token from our database straight away. The rest of your provider's data, including reviews and campaign results read from Google, stays in Glister until you ask us to delete it. When you do, we delete your account, provider profiles, connected-account tokens and everything listed in our data deletion instructions within 30 days. Copies in Neon's encrypted backup history expire within 24 hours after that. We keep invoices and payment records for as long as UK tax law requires.

If a breach affects your personal data, we will tell you without undue delay and report it to the Information Commissioner's Office where the law requires us to.

Advertising cookies

On Glister's own public pages (not on the landing pages we host for providers, and not inside the app), we run advertising tags from Google, Meta and LinkedIn on every visit, and they set cookies in your browser. They tell us which of our ads brought you to the site and whether you then looked up your rank, asked for your report or asked for a demo, and they let those platforms show you our ads later. We do not show a cookie banner and we do not ask first.

You can stop this at any time. Block or delete cookies in your browser settings, switch off personalised ads at adssettings.google.com, or use the ad preference controls in your Meta and LinkedIn accounts. You can also email wwalter@bridgeheadcommunications.com and we will tell you what we hold.

Screen recording on sign-in

On the sign-in and onboarding pages and inside the signed-in app, PostHog records how a visitor moves through the page (clicks, scrolling, timing, what is typed and what is on screen) so we can see where people get stuck. Recordings can therefore show your email address, name and the provider details you view. Password fields are never recorded, and recording stops as soon as you move to the public pages of the site. Recordings are kept for 30 days.

Your rights

You can access, correct, export, or delete your data at any time. Email wwalter@bridgeheadcommunications.com and we will action the request within 30 days. Disconnecting any connected account (Gmail, Outlook, Facebook, Instagram, LinkedIn, Google or Meta Ads) immediately deletes Glister's stored access token.

Contact

Bridgehead Communications Ltd, Temple Chambers, 3-7 Temple Avenue, London, EC4Y 0HP, United Kingdom. wwalter@bridgeheadcommunications.com