What we collect, what we don't

Privacy policy · Last updated 20 October 2026 · Effective 5 October 2026 · UK / English law

Who we are

SitePost is operated by Skyla's Choice Ltd, a company registered in England & Wales (company number 16059710), registered office 9 Beverley Drive, Kimberley, Nottingham, England, NG16 2TW. Skyla's Choice Ltd is responsible for the personal data described in this policy.

What we collect

When you create an account: name, email, business name, billing details (handled by Stripe — we never see card numbers).

When you use SitePost: your uploaded photos, captions, brand voice configuration, connected social account tokens, post performance data we fetch from Meta, LinkedIn and YouTube on your behalf, and — if you use the Engagement Inbox — the public comments left on your connected channels' posts and the replies you approve (see “Comments and the Engagement Inbox”).

Server logs include IP address, browser, basic page-visit data — used for security and debugging only, retained 90 days.

Photo location (mobile app)

The SitePost mobile app can tag the photos you upload with where they were taken. This is optional. If you allow it, the app asks your phone for your precise location (GPS) at the moment you upload or take a photo, and saves that location with the photo in your account. We use it only to show where a photo was taken and to help describe it. We do not track your location in the background and we do not collect it at any other time.

You can turn this off at any time in your phone’s settings (Settings, Apps, SitePost, Permissions, Location), and the app works the same without it; your photos are then saved with no location. Removing a photo from SitePost removes the location saved with it.

The marketplace

If you list a photo for sale on the SitePost marketplace, buyers see your seller display name (the name on your creator profile), your photo, its title and category, and how many photos you have sold. They do not see your email address. You choose your display name and can change it.

Payments and payouts are handled by Stripe. Buyers pay through Stripe, and sellers are paid out through a Stripe Connect account, for which Stripe collects the identity and bank details it needs directly from you. We never see card numbers or bank account numbers. We keep a record of each sale (the listing, buyer, amount, our fee and your payout) for our accounts and for HMRC, typically for 6 years.

Anyone signed in can report a listing, and can hide a seller’s listings from their own view. A reported listing is hidden while we review it. We keep the report, the reason given and our decision so that we can deal with repeat problems.

People you invite to your team

If you invite someone to your workspace, we store their email address, the brands you gave them access to and who invited them, and we email them the invitation. We use their email address only to send and manage that invitation and, once they join, to run their account. Invitations expire after a few days; an invitation that is not accepted is deleted when you delete your account. Please only invite people who would expect to hear from you.

If we emailed you about our products (business outreach)

We sometimes email businesses that may benefit from our products. Skyla's Choice Ltd is the controller for this.

What we hold: the company's name, number, registered address and industry codes, and a business contact's name, job title and work email address or the company's general email address.

Where it comes from: the public Companies House register, and the company's own public website.

Who we email: only limited companies, PLCs and LLPs (corporate subscribers under the Privacy and Electronic Communications Regulations). We do not cold-email sole traders or partnerships.

Why, and our lawful basis: to tell the business about products that may be useful to it, under legitimate interests (UK GDPR Art. 6(1)(f)). We think a short, relevant business email to a work address is something a business can reasonably expect, and every email lets you opt out.

Your choice: every email has an unsubscribe link, or email [email protected]. Once you opt out we never email that address again; we keep the address on a suppression list only so we can honour that. You can also ask what we hold, ask us to correct or delete it, or complain to the ICO.

How long we keep it: only while it is useful for this kind of business outreach. We review prospect records at least once a year and delete what we no longer need, except the suppression list.

Email delivery is handled by our email provider (Resend), which processes the data only on our instructions.

What we don’t collect

We don’t sell email lists, use Google’s advertising or ad-personalisation features, or fingerprint your device. Inside the signed-in dashboard we run no tracking other than the Google Analytics choice described below.

With your consent, we use one optional Google Analytics cookie — including on your dashboard once you’re signed in — to see aggregate usage. It’s off until you accept it, Google keeps it for 14 months, and you can withdraw any time from “Cookie settings” in the footer or Dashboard → Settings. It never carries advertising or ad-personalisation signals. Full details, including what Google collects, are in our cookie policy.

Separately, and only if you accept the “Advertising” category in the cookie banner, we load the Meta Pixel on our public pages (never on the dashboard) and send Meta a sign-up event from our servers, so we can measure our own Facebook and Instagram ads. The email address in that event is hashed (SHA-256) before it is sent, alongside your IP address and browser details. Meta receives this data and acts as a joint controller for this measurement; we use it only to measure our advertising. It’s off until you opt in, and you can withdraw any time from “Cookie settings” in the footer. See our cookie policy, section 3B.

The SitePost mobile app uses Firebase Analytics (Google) to count which screens are viewed and key actions such as sign-up, sign-in, purchases and publishing a post. It does not use your device’s advertising ID, does not carry your name, email, photos or captions, and is not linked to your account.

Where it lives

Your data is stored in UK and EU regions only. Photos and media are encrypted at rest in S3-compatible object storage. The database is encrypted at rest in PostgreSQL. Backups are encrypted and rotated daily; we keep 30 days.

Who can see it

Inside your account: only people you explicitly invite, scoped by role.

Inside SitePost: a small UK-based team, with access logged. Engineers access production data only when investigating a specific issue you’ve raised.

Sub-processors: DigitalOcean (hosting, managed PostgreSQL, and Spaces object storage — London / lon1), Stripe (payments), OpenAI (caption generation and drafting comment replies — on request, never training), Google (generating brand graphics from scratch — a transfer to the US; never your own photos), Meta and LinkedIn (publishing on your behalf), Resend (transactional email), Cloudflare (CDN).

Comments and the Engagement Inbox

If you switch on the Engagement Inbox for a connected Facebook Page, Instagram professional account or YouTube channel, SitePost reads the public comments left on that channel's posts — the comment text, the commenter's public name or handle, and when it was posted — so it can show them to you, flag anything that needs a person (complaints, safety, legal or payment issues always do), and draft replies in your brand's voice.

Drafting a reply sends the comment and the post's caption or video description to our AI provider (OpenAI). Nothing is posted unless you approve it, or unless you have switched on automatic replies for low-risk comments on that channel. Every draft, approval, edit and published reply is logged in your account so you can see what happened and why.

Comments and replies are stored with the channel they belong to and are deleted when you remove that channel from SitePost. We don't use commenters' data for advertising, and we never contact commenters outside the platform they commented on.

Facebook & Instagram (Meta) data

If you connect a Facebook Page or Instagram professional account, SitePost accesses the Page and account name, id and profile picture, the access token Meta issues (stored encrypted), the posts SitePost publishes and their performance figures, and, if you switch on the Engagement Inbox, public comments on your own posts. We use this only to publish, report on and manage your own content.

We also keep the id Meta gives your Facebook login for SitePost, so that if you ask Meta to delete your data we can find the Pages and accounts you connected.

You can disconnect a Facebook Page or Instagram account at any time from Dashboard → Accounts, which removes its access token straight away. If you remove SitePost in your Facebook settings and ask for your data to be deleted, Meta tells us and SitePost automatically disconnects the Pages and Instagram accounts you connected, deletes their access tokens, Instagram handle, profile picture and follower count, and deletes the comments and replies held for the Engagement Inbox. This normally happens as soon as Meta tells us, and always within 7 days. Meta gives you a confirmation code and a link where you can check the result.

The posts SitePost published for your business, and their performance figures, are your business's own content and stay in your SitePost account until you delete them or your account.

YouTube & Google account data

If you connect a YouTube channel, we access: the channel's identity (its id, title, and public handle) so we can show you which channel is connected; permission to upload videos you've approved in SitePost to that channel; video statistics (views, likes, comments, and watch-time analytics) for videos we've published, so your dashboard can show how they're performing; and the comments on your own channel's videos, so SitePost's Engagement Inbox can show them to you, draft replies in your brand's voice, post the replies you approve (or that match low-risk reply rules you have switched on), hold spam for review on your channel, and delete replies SitePost posted.

This access exists only to publish and manage the content of your own YouTube channel through SitePost. To draft a reply, SitePost sends the comment text and the video's title and description to our AI provider (OpenAI). We never read, download, or act on any other content in your Google account, and we never act on channels you don't own.

Your YouTube access and refresh tokens are encrypted at rest, the same as every other connected account (see “Where it lives”), and are never shared with anyone, including our other sub-processors.

You can disconnect a YouTube channel at any time from Dashboard → Accounts — this immediately stops SitePost publishing to it. To fully revoke SitePost's access to your Google account, visit Google's own permissions page at myaccount.google.com/permissions and remove SitePost from the list.

We do not use data received from Google APIs to develop, improve or train generalised AI or machine-learning models. Comment text sent to our AI provider is used only to draft your reply and is not used for training.

SitePost's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your rights (UK GDPR)

You can ask us for a copy of everything we hold on you. Email [email protected] and we will send it.

You can delete your account yourself, at any time. In the SitePost mobile app go to Me, then Delete my account. On the website go to Dashboard, Account, then Delete my account. You confirm by typing DELETE and entering your password. Deletion happens straight away: your account is deactivated and your personal data is erased from our live systems, and if you are the only person in your workspace it is deleted too, with its brands, posts, photos and connected accounts. If other people use your workspace, you must make one of them an administrator first. Your marketplace listings are withdrawn. We keep only records the law requires us to keep, such as payment records, without your name. Backups are overwritten within 30 days. Full details are on the data-deletion page, and you can still ask us to do it by email.

Data we received from Meta can be deleted on its own, within 7 days (see “Facebook & Instagram (Meta) data”).

You have the right to object, restrict processing, or lodge a complaint with the ICO.

Contact

Email [email protected] with the subject "Privacy". Our DPO is Richard Crofts. We answer in plain English.

Questions? We answer in plain English.Email us