Privacy Policy

Last updated 15 October 2026.

1. Who we are

Luminous Emporium Ltd, registered in England and Wales, registered office at 124-128 City Road, London, United Kingdom, EC1V 2NX, company number 16201976, is the controller of personal data we process about our own customers and visitors, such as account details, billing records, usage data and the security data described below, for the purposes of UK GDPR.

Customer content is different. For the articles, drafts, media, channel data and report text a business puts into scatterpost, and any personal data in them, that business is the controller and we act as its processor under our data processing agreement. If your personal data appears in a customer's content and you want to exercise your rights over it, contact that business first; we will help it respond.

2. What we collect and why

Account details (name, email address) to create and secure your account, under the lawful basis of performance of a contract. Workspace content (articles, scheduling data, analytics) to provide the service. For personal data in that content, the business that holds the account is the controller and decides the lawful basis, and we act as its processor under our data processing agreement (see section 1). Platform connection details, including access tokens for the platforms you connect, encrypted at rest, under performance of a contract. Where you connect a channel on behalf of the business that holds the account, we rely on our legitimate interest in providing the service that business has asked for. Billing details, handled by Stripe, under performance of a contract and our legitimate interest in being paid. Usage data from Sentry, PostHog and, once you accept analytics cookies, Google Analytics, under our legitimate interest in keeping the service working and improving it, where those tools are enabled. We process IP addresses for security and to limit abuse, for example rate limiting sign-in emails and sign-ups, under our legitimate interest in keeping the service secure. Our free canonical URL checker uses the same keyed hash of your IP address (or IPv6 /64 network) to limit checks. The page addresses you enter are used only to fetch those pages from our server and are not stored or logged. One check holds the IP address itself in server memory for up to an hour before discarding it; a second stores a keyed cryptographic hash of it, which cannot practically be reversed, for up to 48 hours. We never use IP addresses for marketing. Vercel and Supabase, as our hosting and database processors, also log IP addresses in their own infrastructure logs; see the subprocessors page.

Facebook and Instagram (Meta). If you connect a Facebook Page or an Instagram professional account, Meta shows us the Pages and linked Instagram accounts you manage so you can choose one. We store only the one you choose. Its name (for Instagram, its username) and its Page or Instagram account id are held as ordinary database fields so your dashboard can show them; the Page id, the Instagram username and id, your app-scoped Meta user id and a Page access token are held encrypted at rest. We also keep a keyed, one-way hash of your Meta user id so we can find your connections when Meta sends us a deletion request. We send Meta the posts, images and videos you ask us to publish, and read back reaction and comment counts for those posts, plus share counts on Facebook, to show you how they performed. To have this data deleted, disconnect the channel in scatterpost, or remove scatterpost from your Facebook settings (Apps and websites) and send a deletion request from there: we then delete those connections, their tokens, and the publishing history and performance figures we hold for them. Posts already published on Facebook or Instagram stay there until you delete them on Meta. You can also email hello@scatterpost.io to ask for deletion. After a deletion request you get a confirmation code you can check on our data deletion status page. Meta's app settings point their data deletion request to scatterpost at app.scatterpost.io/api/platforms/meta/data-deletion, which handles the request the way described above.

Threads (Meta). If you connect a Threads profile, you sign in with Threads and Meta gives us your Threads user id and username, plus an access token. We ask only for permission to read your basic profile, to publish posts and to read the insights for those posts. The user id and username are held as ordinary database fields so your dashboard can show the profile; the access token is held encrypted at rest, and we refresh it before it expires. We send Threads the posts, images and videos you ask us to publish, and read back views, likes, replies, reposts and quotes for those posts to show you how they performed. We do not read your other Threads posts or your followers. We do not sell Threads data or share it with anyone other than our subprocessors, as described in section 5. When you disconnect the channel in scatterpost, we delete its token, and the publishing history and performance figures we hold for it. You can also remove scatterpost in your Threads settings (Account, then Website permissions) and send a deletion request from there. Meta's app settings point their removal request to app.scatterpost.io/api/platforms/threads/deauthorise, where we delete the token straight away and keep the profile's id and username, marked as removed, until you disconnect it, send a deletion request or delete the workspace, and their data deletion request to app.scatterpost.io/api/platforms/threads/data-deletion, where we delete the connection, its token and the history and figures we hold for it. Posts already published on Threads stay there until you delete them on Threads. You can also email hello@scatterpost.io to ask for deletion.

Facebook and Instagram access requests. While Meta reviews our app, only people we add as testers can connect a Facebook Page or Instagram account. If you ask to be added, from the Channels page or by email, we store the Facebook account name or email you enter, your optional note, your account email address, your user and workspace ids and the time of the request, and we email them to hello@scatterpost.io so we can handle the request by hand. We use these details only to handle that request, because you asked us to, as part of providing the service (performance of a contract). We delete the request, and the email copy we sent ourselves, 30 days after we close it (whether access is given or not), or sooner if you ask us to or the workspace is deleted.

TikTok. If you connect a TikTok account, you sign in with TikTok and TikTok gives us your account's display name and an app-scoped TikTok user id (open id), plus an access token and a refresh token. The display name and the open id are held as ordinary database fields so your dashboard can show the account and we can recognise it when you reconnect; both tokens are held encrypted at rest, and we refresh the access token when it expires. When you publish to TikTok, we send the video you attached to your TikTok inbox; nothing is posted until you finish the post yourself in the TikTok app, and the caption, privacy and other choices you make there are between you and TikTok. We do not read your TikTok videos, followers or performance figures. When you disconnect the channel, we delete its tokens and ask TikTok to revoke our access; you can also remove scatterpost from your TikTok app permissions. Videos you posted on TikTok stay there until you delete them on TikTok. You can also email hello@scatterpost.io to ask for deletion.

LinkedIn Pages. If you connect a LinkedIn Page, you sign in with LinkedIn and LinkedIn shows us the Pages you hold a role on, and their names, so you can choose one. We store only the Page you choose: its name and its LinkedIn organisation id are held as ordinary database fields so your dashboard can show it, and your role on the Page, the access token and, where LinkedIn issues one, a refresh token are held encrypted at rest. We do not read your own LinkedIn profile. We send LinkedIn the posts, images, videos and PDF documents you ask us to publish as the Page, check the Page's recent posts so that a retry does not post the same update twice, and read back impression, click, reaction, comment and share counts for the posts we published, to show you how they performed. When you disconnect the channel, we delete its tokens; you can also remove scatterpost from your LinkedIn settings (Data privacy, Permitted services). Posts already published on LinkedIn stay there until you delete them on LinkedIn. You can also email hello@scatterpost.io to ask for deletion.

YouTube. scatterpost uses YouTube API Services. If you connect a YouTube channel, you sign in with Google, and by connecting you agree to the YouTube Terms of Service; the Google Privacy Policy applies to how Google handles your data. We ask Google for permission to upload videos and to view your YouTube account. We use that only to upload the videos you ask us to publish, to read your channel's id and name so your dashboard can show the channel, and to read the video ids and statistics (such as views and likes) of the videos we uploaded, to show you how they performed. The channel id and name and the video ids and statistics are held as ordinary database fields; the Google access token and refresh token are held encrypted at rest. We do not sell YouTube data or share it with anyone other than our subprocessors, as described in section 5. We check with Google that your grant is still in force and refresh the stored data within the limits YouTube sets; if the grant ends or cannot be confirmed, we delete the channel, its tokens and its stored YouTube data within those limits. When you disconnect the channel in scatterpost, we delete its tokens and stored YouTube data and ask Google to revoke our access. You can also remove scatterpost's access at any time in your Google account permissions. Videos already uploaded to YouTube stay there until you delete them on YouTube. You can also email hello@scatterpost.io to ask for deletion.

Early access invite requests. If you ask for an early access invite, we store the email address you give and the optional note you write, because you asked us to, as a step towards providing the service (Article 6(1)(b)). We use them only to email you your invite link, to tell our team about the request, and to stop the same address being sent too many links. We do not use them for marketing. A keyed hash of your IP address and of your email address is used to limit requests, as described above.

3. Retention

We keep account and workspace data for as long as your workspace exists. Deleting a workspace deletes its content and deletes its platform tokens from our systems. We keep billing records for as long as required by tax law. Error and analytics data is kept for a limited period set by Sentry and PostHog's own retention settings, and for Google Analytics, as configured in Google Analytics. If you remove scatterpost from your Facebook settings without asking for deletion, we delete the access tokens straight away and keep the connection's ids and names, marked as revoked, until you disconnect it, send a deletion request or delete the workspace. When we act on a deletion or removal request from Meta, we record the affected connection ids and the date in the workspace's audit log, so we can show the request was carried out; the record holds no Meta ids, names or tokens. Early access invite requests are deleted 90 days after the invite link expires, or sooner if you email hello@scatterpost.io to ask.

4. Your rights

Under UK GDPR you can ask us to confirm what personal data we hold about you, correct it, delete it, restrict or object to our processing of it, or receive a copy of it in a portable format. Contact us at hello@scatterpost.io to exercise any of these rights. If you are not satisfied with our response, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk.

5. Subprocessors

We use other companies to help provide scatterpost. The full list, with what each one does and where it operates, is on the subprocessors page. It includes Supabase (database, authentication and image storage, London, no international transfer), Vercel (hosting and video storage), Stripe (payments), Resend (transactional email), Anthropic via the Vercel AI Gateway (in-dashboard AI generation), Sentry (error tracking), PostHog (product analytics, EU cloud) and Google Analytics (website analytics, only after you accept analytics cookies, EU with transfers to the USA under the EU-US Data Privacy Framework and Standard Contractual Clauses). Where a subprocessor is outside the UK and the EEA, the subprocessors page names the specific safeguard we rely on for that transfer. Platforms you publish to, such as Meta, are not subprocessors: they receive your content as independent controllers, under their own terms.

6. Security

Platform access tokens and webhook secrets are encrypted at rest. Access to your workspace data is controlled by row-level security tied to your workspace, and API keys are hashed and revocable.

Internal admin access: authorised scatterpost staff can view account and workspace details, such as your plan, members, channel names and statuses, posts and publication history, and any bug reports you send, to provide support, investigate problems and prevent abuse. Staff access through our internal admin console requires a second sign-in factor, never shows your platform credentials, API keys or access tokens, and every view and change is recorded in an internal audit log.

7. Cookies

On our public pages we ask before any non-essential cookie is set. A first-party cookie called scatterpost_consent records your choice, "granted" or "denied", for 12 months. Product analytics through PostHog and Google Analytics only starts on those pages once you choose "Accept analytics"; if you choose "Decline", or take no action, neither is ever loaded. This also respects a browser's Do Not Track signal and any existing analytics opt-out, whichever is stricter. If you later withdraw consent, we also clear any Google Analytics cookies already set. You can change your choice at any time using the "Cookie choices" link in the footer. The dashboard and the OAuth sign-in screens do not use this cookie and do not show this banner.

8. Contact

Questions about this policy can be sent to hello@scatterpost.io.