Privacy policy

Last updated 19 October 2026

This policy explains what personal information stakeholder.services handles, why, and what you can do about it. It covers the platform at this address, including connecting Facebook Pages, Instagram accounts, LinkedIn Pages and X accounts and publishing posts to them.

Who we are

stakeholder.services is run by [Company legal name], [Registered address](“we”, “us”). We are the controller of the personal information described here. For anything about this policy or your information, contact us at [privacy contact email].

stakeholder.services is a private platform used by our own staff to manage stakeholder engagement work for our clients. It is not open to the public to sign up to.

Facebook Pages and Instagram accounts

Our staff can connect a client's Facebook Page, and the Instagram professional account linked to it, to stakeholder.services so they can write, schedule and publish posts to them. They are only ever connected by someone who manages the Page, logging in to Facebook themselves and choosing which Pages and accounts to allow.

What we receive from Facebook and Instagram

The list of Facebook Pages the person connecting manages: each Page's ID, its name, and whether their role on it allows creating posts.
For each of those Pages, the ID and username of the Instagram professional account linked to it, if there is one.
An access token for each Page they choose to connect, which lets us publish to that Page and to its linked Instagram account.
When we publish a post: its Facebook or Instagram ID and web address, so we can link to it.

Instagram publishes photos by fetching them from a web address rather than having them uploaded. While a post is being published to Instagram, we give Instagram a private link to each of its photos that only works during publishing and expires within an hour.

We never see or store anyone's Facebook password. The personal access token Facebook gives us during login is used only to fetch the list of Pages and their linked Instagram accounts, and is not stored.

What we keep and how we use it

For each connected Page or Instagram account: its ID and name, its access token (stored encrypted), which of our staff connected it and when.
The posts our staff write: their text, links and photos, when they are scheduled for, whether they were published, and any error Facebook or Instagram returned.

We use this only to publish the posts our staff write, at the time they choose, and to show them what has been published. We do not use Facebook or Instagram data to read messages, comments, followers or insights, we do not collect information about people who visit or interact with a Page or account, and we do not use it for advertising or profiling.

We do not sell Facebook or Instagram data or share it with anyone else. It is sent only to Meta (Facebook and Instagram) itself, to publish posts.

How long we keep it

An access token is deleted as soon as the Page or account is disconnected in stakeholder.services, or when the client it belongs to is removed.
Records of posts are kept as a history of the client's work until they are deleted in stakeholder.services or you ask us to delete them. Deleting a record here does not remove the post from Facebook or Instagram — that is done there.

LinkedIn Pages

Our staff can also connect a client's LinkedIn company Page, so they can write, schedule and publish posts to it. A Page is only ever connected by one of its admins, logging in to LinkedIn themselves and choosing which Pages to allow.

What we receive from LinkedIn, and what we keep

The list of company Pages the person connecting has a role on: each Page's ID, its name, and whether their role allows creating posts.
Access tokens that let us publish to the Pages they choose to connect. LinkedIn issues these to the person who connected, for a limited time (normally 60 days, or up to a year where LinkedIn allows it to be renewed). We store them encrypted, one copy for each Page connected, and use them only to publish posts to that Page.
When we publish a post: its LinkedIn ID, so we can link to it.

We never see or store anyone's LinkedIn password, and we do not read anyone's profile, connections, messages, or a Page's followers or analytics. When a LinkedIn post includes a link, we read that web page's title, description and picture to build the post's preview, as LinkedIn itself would. LinkedIn data is not sold or shared with anyone; it is sent only to LinkedIn, to publish posts. The same retention as above applies: tokens are deleted when the Page is disconnected or the client removed, and records of posts are kept until deleted.

X (Twitter) accounts

Our staff can also connect a client's X account, so they can write, schedule and publish posts to it. It is only ever connected by someone who can log in to that account, logging in to X themselves and allowing access.

We receive the account's ID and username, and access tokens that let us publish to it. We store the tokens encrypted and renew them as X requires (X's access tokens last two hours), and use them only to post, upload the post's photos, and confirm which account is connected.
When we publish a post: its X ID, so we can link to it.

We never see or store the account's password, and we do not read its timeline, followers, messages or analytics. X data is not sold or shared with anyone; it is sent only to X, to publish posts. The same retention as above applies.

Deleting your data

To stop stakeholder.services having any access to your Facebook Page, Instagram account, LinkedIn Page or X account, and to have the data we hold about it deleted:

Remove our access on Facebook. In Facebook, go to Settings & privacy → Settings → Business integrations (on some accounts, “Apps and websites”), find stakeholder.services, and remove it. This stops our stored access token working straight away, for the Page and its Instagram account.
For LinkedIn, go to Settings & Privacy → Data privacy → Permitted services on LinkedIn, find stakeholder.services, and remove it.
For X, go to Settings and privacy → Security and account access → Apps and sessions → Connected apps, find stakeholder.services, and revoke its access.
Ask us to delete what we hold. Email [privacy contact email] with the name of the Facebook Page, Instagram account, LinkedIn Page or X account, and say you want its data deleted. We will delete the Page's connection and access token and the records of posts made to it, and confirm to you when it's done, within 30 days.

If you work with us, you can also ask the person you deal with to disconnect the Page, which deletes its access token immediately.

Other information the platform holds

Outside Facebook, Instagram, LinkedIn and X, stakeholder.services holds:

Staff accounts — name, email address, a securely hashed password, and preferences such as timezone.
Client records — the organisations we work with, their sites and contacts (names, job titles, email addresses, phone numbers), notes, meetings, calls and emails with them, photos, documents and diary entries, including recordings of meetings.
Correspondence from the public — complaints or enquiries sent to us or our clients, with the sender's name, contact details, postcode and message.
Public information about elected representatives — councillors, MPs and election candidates, taken from official and public sources such as council websites, the UK Parliament and Democracy Club.
Postcode lookups — the postcodes looked up, with the IP address of the request, kept to prevent misuse.

We use this to carry out the work our clients engage us for and to run the platform. Our lawful basis is our legitimate interest in providing those services, or performing our contracts with clients; where we rely on consent, you can withdraw it at any time.

Service providers

We use a small number of providers to run the platform, who process information only on our instructions:

Our hosting provider, which stores the platform and its data.
Meta Platforms (Facebook and Instagram), to publish posts to connected Pages and accounts.
LinkedIn, to publish posts to connected company Pages.
X, to publish posts to connected X accounts.
Mailgun (EU region), to send and receive email.
Deepgram, where used, to transcribe and summarise meeting recordings.
Google Cloud, where used, to assess the tone of complaints.

Postcode and area lookups use public services such as postcodes.io, mySociety MapIt, police.uk and Wikidata; these receive postcodes or area codes, not names or contact details.

Some providers may process information outside the UK. Where they do, we rely on the safeguards UK data protection law requires, such as the UK International Data Transfer Agreement or an adequacy decision.

Keeping it secure

The platform is only available to our staff, who sign in individually. Passwords are hashed, social media access tokens are encrypted, uploaded files are kept out of public reach, and the site is served over HTTPS.

Your rights

Under UK data protection law you can ask us for a copy of the information we hold about you, and ask us to correct it, delete it, restrict how we use it or object to our using it. Contact us at [privacy contact email]; we will respond within one month.

If you are unhappy with how we have handled your information, you can complain to the Information Commissioner's Office at ico.org.uk.

Changes to this policy

We will update this page if how we handle information changes, and change the date at the top when we do.