Legal · draft
How WePostSocials collects, uses and protects personal information.
WePostSocials is a social media content platform for small businesses and agencies. WePostSocials is a trading name used for a proposed UK private limited company, WePostSocials Ltd, which is not yet incorporated. Until incorporation and any assignment are complete, the proposed company is not the contracting party or the data controller.
Current website operator and data controller: OWNER INPUT REQUIRED — current operator's legal name and trading address. The current operator is the person or entity responsible for this website before incorporation; that identity has not been confirmed.
ICO position: OWNER INPUT REQUIRED — ICO data-protection-fee assessment and reference, if any. No ICO registration is claimed.
Privacy contact: hello@wepostsocials.com. The mailbox is the intended route for privacy and data requests but is UNVERIFIED until its operation is confirmed. A working privacy contact is a publication blocker. No statutory Data Protection Officer is currently appointed.
This policy covers the public marketing site and the private WePostSocials application. The application is currently a preview: live publishing, billing and some social integrations are not operational. The data controls described here are implemented in the local application; they are not a promise that an unbuilt feature exists.
Early-access enquiries: full name, email address, optional business name, account type (individual business or agency), optional message, the fact that consent was given, a reference and the submission time. We use this only to review and respond to the request. The public site does not expose the stored record. The proposed retention period is 365 days unless you ask us to delete it sooner or a legal obligation requires longer retention.
Account and authentication: name, email address, a password hash handled by Better Auth, email-verification state, session records and security metadata such as IP address and browser user-agent.
Workspace and business profile: workspace name, membership and role, business name, website, category, description, audience, tone, goals, timezone, services, products, service areas, opening hours, preferred call to action and verified business facts.
Brand and content: logos, uploaded photographs, background assets, colours, banned words, captions, hashtags, calls to action, on-image copy, drafts, revisions, platform adaptations, approvals and generated images.
Social connections: the platform, display name, external Page id, requested/confirmed permissions and connection status. Access tokens are encrypted at rest and are never included in a customer export or sent to the browser.
Scheduling and publishing: planned times, timezone, target accounts, publish jobs, attempts, remote ids and failure reasons.
Usage and support: generation requests, prompts/briefs, AI suggestions, token and cost accounting, plan usage, audit events and emails you send to support.
Technical logs: the hosting layer necessarily processes IP address, requested URL, referrer, time and user-agent for delivery, security and abuse prevention. We do not run third-party analytics or advertising trackers.
Early-access enquiries: we use the enquiry details to assess your request and, where a working contact route exists, respond to you. The current draft relies on the opt-in consent box on the form, which is unchecked by default. We do not add enquirers to a marketing list. Consent can be withdrawn at any time, but withdrawal does not affect processing that already happened. We are also assessing whether legitimate interests would be more appropriate for a requested business enquiry; that assessment is documented separately and has not been adopted without an owner decision.
We use account and workspace data to provide the service you request, authenticate you, save your work, render images, record approvals and schedules, and support you. This is processing necessary to perform our contract with you.
We use security logs, rate limits and audit events for the legitimate interests of keeping the service secure, preventing abuse and investigating failures. We balance those interests against your rights and you may object.
We use business contact details and records required for tax or accounting where the law requires it. Optional product emails are controlled by your email preferences and marketing consent where consent is required.
Text generation is deterministic/mock by default in the current preview. If a live AI provider is deliberately enabled by the operator, the material needed to produce the requested content — including your brief, relevant business-profile facts, tone/audience instructions and brand context — may be sent to that provider.
PROVIDER RETENTION VERIFICATION REQUIRED — the live AI provider, contractual data retention, training use and processing location must be confirmed and added before a live provider is enabled for customers. We do not claim that a provider retains nothing or never trains on data unless that is separately verified in writing.
Branded template images are rendered by our own code. Paid generative AI image creation is not implemented and is not advertised as available. If a paid image provider is enabled in a future phase, the prompt and brand colours may be sent to it; the same verification requirement applies. Uploaded logos and photographs are rendered by our local image pipeline.
AI output can be wrong. You must review facts, prices, claims, images and platform rules before approving or publishing anything.
The public marketing site is hosted on Render in Frankfurt. When the early-access form is enabled, the enquiry record is intended to be stored on a Render persistent disk in that region. Render is a processor; a signed data processing agreement has not been verified for this deployment.
GoDaddy provides DNS/domain registration and GitHub stores the source repository; neither is intended to hold enquiry records in this launch. Resend is intended for later email notification but is not active. Stripe, live AI providers and social publishing providers are not active. The private application is not deployed.
The EEA is covered by the UK adequacy framework, but no transfer mechanism is claimed as verified here. If a provider processes data outside the UK/EEA, an appropriate transfer mechanism must be documented before that processing begins. No international-transfer or retention claim is made until the owner approves the providers, regions and contracts.
OWNER INPUT REQUIRED — complete subprocessor list, processing locations, signed DPAs and transfer mechanism.
Account and workspace data is kept while the account/workspace exists. Drafts, images, approvals, schedules, generation history and audit records are kept until you delete them or delete the workspace/account, subject to backup rotation and legal retention.
Sessions expire after 7 days and are renewed at most once per day. Disconnected social credentials are deleted immediately. Expired sessions are not used for access.
OWNER INPUT REQUIRED — approved retention periods for server logs, audit events, generation history, media and backups. No specific period is invented here.
Under the UK GDPR you may request access, correction, erasure, restriction, objection and portability. In the signed-in application you can download a structured workspace export and delete a workspace or account from the Privacy and data page. That page is not available on this marketing-only preview. You can also contact support to request a copy or deletion. We may need to verify that you control the account.
We aim to respond to a rights request within one month. If a request is complex, we may extend that period by up to two further months and will tell you why. There is normally no fee. You may withdraw consent at any time where consent is the basis.
You may complain to the Information Commissioner's Office at ico.org.uk. Tell us first so we can try to put it right.
Self-service workspace deletion cancels future jobs, cancels scheduled targets, removes workspace rows by cascade, deletes local social credentials and deletes stored media files. Account deletion also removes the account and every workspace you solely own; it is blocked if you own a workspace with other members.
Backup copies may remain until their normal rotation cycle. We do not promise immediate erasure from backups. Invoices and transaction records required by law may be retained without your content. Posts already published on a social network are outside our control.
See the Data Deletion Instructions for the full process.
We receive information from you when you submit an enquiry, create an account, complete onboarding, upload content or contact support. We also receive technical information from your browser and our hosting layer, and account/profile information from a social platform only when you deliberately connect it.
We do not currently make solely automated decisions that produce legal or similarly significant effects. AI-assisted drafting is a tool for a human to review; it is not used to decide whether you get access, a workspace or a subscription. If that changes, we will update this policy and provide the required information.
On the early-access form, name, email, account type and the privacy choice are required so we can process and respond to the request. Business name and message are optional. If you do not provide the required information, we cannot review the request. Do not send passwords, social access tokens, identity documents or sensitive personal data.
Submitting an early-access enquiry is not a marketing subscription. We will not add you to a promotional list from that form. If we offer product updates or marketing emails later, we will ask separately and provide a clear opt-out; consent will not be bundled with the enquiry.
If you use WePostSocials to process personal data for clients, you may need a data processing agreement. Request one at the contact address. The DPA must name the controller, processing purpose, subprocessors, security measures, breach process, deletion/return terms and international transfers.
OWNER INPUT REQUIRED — DPA template, legal entity and subprocessor schedule.
We will update this policy when the product, providers or law change. Material changes will be communicated before they take effect where practicable.
PROFESSIONAL LEGAL REVIEW REQUIRED — whole policy, controller identity, lawful bases, retention, transfers and DPA terms.
Draft prepared 9 November 2026. This draft is not legal advice and is not approved for publication.
Social account connections
Connecting a Facebook Page, Instagram professional account or LinkedIn profile/Page uses the provider's OAuth flow. We request only the permissions needed to identify the account and, when enabled, publish content. Tokens are encrypted; raw tokens are not written to logs or exported to customers. Automatic LinkedIn refresh is implemented locally; Facebook and Instagram Page tokens use reconnect as the safe fallback.
Disconnecting a Page deletes the stored credential and marks the account disconnected. Deleting a workspace or account also removes local credentials. We do not call a social provider to revoke or delete anything in this phase. Posts already published remain on the social platform until deleted there.