What PostRoost collects when you use the website and the application, why, who helps us process it, how long we keep it and how to ask us about it. Written in plain language, based on what the product actually does.
Last reviewed 22 October 2026
This policy covers the PostRoost website (including the blog, free tools, contact form and billing pages) and the PostRoost application where agencies plan, approve and publish social media posts. In this policy “PostRoost”, “we” and “us” mean the operator of PostRoost; “you” means a visitor, an account holder or a person invited to an agency or client.
PostRoost decides why and how personal data is processed for the website, for accounts, for billing and for running the service. Agencies decide what they put into PostRoost about their own clients and the people they invite; for that content, PostRoost processes data on the agency’s behalf and following its instructions. Questions about this policy go through our contact page.
When you sign up we collect your name, your business or agency name, your e-mail address and a password. Passwords are stored only as a one-way hash, never in readable form. When someone invites you, we store your e-mail address, the role you were given and the agency or client you belong to. We use this data to create and secure your account, send invitations and password resets, and apply the right permissions.
Inside the application, agencies store clients (name, colour, logo, time zone, brand voice and approval setting), posts (captions, per-network versions, links, first comments, alt text, schedules and status), comments, approval decisions with notes, and the list of people who belong to each client. We process this to provide the service: showing calendars, routing approvals, publishing posts at the scheduled time and keeping a record of who approved what.
When you connect a social account, the network sends us an access token and basic account details such as the account name, handle and identifier. Access tokens are encrypted at rest with AES-256-GCM. We use them only to publish the posts you schedule, post first comments, keep the connection valid and read the numbers the network makes available. Disconnecting an account stops this; its post history stays until the account or the client is removed.
Images and videos you upload are stored in Cloudflare R2 object storage when media storage is configured for the service, organised by agency and client, and served from a public address so that each network can fetch the file when the post is published. Uploaded images are converted to JPEG and have embedded metadata removed in the process; logos are re-encoded as PNG without metadata. When you paste a link to an image or a web page instead, we use that link as given and may fetch the page to find its share image. Because Instagram accepts only JPEG images, an outside image sent to Instagram may be copied into our storage and converted at publishing time.
After a post goes out we ask the network for its numbers (for example impressions, reactions, comments, shares, saves, clicks and video views) for up to 90 days, and we record each account’s follower count once a day. These are aggregate figures supplied by the networks, not data about individual people who saw your posts.
When you use the writing assistant, the text of the post or brief, the selected networks and their limits, the client’s name and the client’s brand voice are sent to Anthropic, which provides the AI model, to generate suggestions. We count requests to apply plan allowances. Under Anthropic’s commercial terms, inputs and outputs from its commercial products are not used to train its models by default. Do not put information into a brief that you would not want processed in this way.
Subscriptions are bought and managed on the PostRoost website, and payments are processed by Stripe. Card details are entered on Stripe’s own pages and are never received or stored by PostRoost. We receive and keep the information needed to run your subscription: the plan, billing interval, trial use, payment status, paid-through date, invoices and the Stripe customer and subscription references. Using the billing pages creates a website account linked to your agency.
We send service e-mails such as invitations, e-mail confirmations and password resets, and replies to messages you send us, through an e-mail delivery (SMTP) provider. That provider handles the recipient address and the content of the message to deliver it.
When you use the contact form we store your name, e-mail address and message so we can reply, and send a copy to our team by e-mail. To limit spam we keep only a salted hash of your IP address for a short time, never the address itself.
We keep records of important changes, such as plan changes, people added or removed, role changes, clients created or deleted and accounts connected or disconnected, with the person and time, to protect agencies and investigate problems. Our servers also keep short-lived technical logs.
The website and the application use only cookies that are needed for them to work: cookies that keep you signed in, remember which agency you are working in, and protect forms against misuse. WordPress sets its own sign-in cookies on the website when you use the billing pages. We do not use advertising cookies, social-media pixels or third-party analytics trackers, so there is nothing to opt out of. You can delete cookies in your browser at any time; you will then need to sign in again.
We share personal data only with service providers that help us run PostRoost, and only as much as they need:
| Provider | What for |
|---|---|
| The social networks you connect (Meta for Facebook and Instagram, LinkedIn, X, TikTok, Google for YouTube, Pinterest) | Publishing your posts and reading their numbers, under each network’s own terms |
| Anthropic | Generating AI writing suggestions when you use the assistant |
| Stripe | Processing payments and managing subscriptions |
| Cloudflare (R2) | Storing and serving uploaded media and logos, when configured |
| Our e-mail delivery provider | Sending service e-mails and replies |
| Our hosting and database providers | Running the website and the application |
We may also disclose data when the law requires it, or to protect our users, the service or others from fraud or abuse. If PostRoost is sold or reorganised, data may transfer to the new operator under this policy. We do not sell personal data.
When an agency asks us to delete its data, we delete it from the live service, except records we must keep by law, and it disappears from backups as they expire.
You can view and change most of your data yourself: your name and sign-in e-mail under Settings, your clients, posts and connected accounts inside the application, and your subscription on the billing page. You can also ask us to give you a copy of your personal data, correct it, delete it, restrict or object to how we use it, or move it to another service. Depending on where you live, you may have further rights, including the right to complain to a data protection authority.
Send requests through the contact page from the e-mail address on your account. We may need to confirm your identity first. If you are a client user or were invited by an agency, we may pass your request to that agency, because it controls the content it put into PostRoost.
Access tokens are encrypted at rest, passwords are hashed, connections to the website and application use HTTPS, and every person only sees the agencies and clients they belong to. Paid access is granted only from payment state confirmed directly with Stripe. No system is perfectly secure; if we become aware of a breach that affects your data, we will tell you as the law requires.
Our service providers may process data in countries other than yours, including the United States. Where the law requires it, we rely on appropriate safeguards for those transfers.
PostRoost is a business tool and is not intended for children. Accounts are for adults acting for a business or organisation. Do not upload personal data about children unless you have the right to do so.
We will update this page when PostRoost’s data handling changes and change the date at the top. For significant changes we will tell account owners by e-mail before they take effect.
For privacy questions or requests, write to us through the contact page and mention “privacy” in your message.
10 questions
No. We do not sell personal data, and we do not share it with advertisers.
No. The website and the application use only the cookies needed to sign you in and keep your session secure. There are no advertising, social-media or third-party analytics trackers.
The access tokens that networks issue when you connect an account are encrypted at rest with AES-256-GCM. We use them only to publish the posts you schedule and to read the numbers the network shares.
No. Payments are handled by Stripe on its hosted checkout and billing pages. We receive the payment status, plan and billing details Stripe returns, never your full card number.
Assistant requests are sent to Anthropic to generate suggestions. Under Anthropic's commercial terms, inputs and outputs from its commercial products are not used to train its models by default.
When media storage is configured, files you upload are stored in Cloudflare R2 object storage under your agency and client, and served from a public address so the networks can fetch them for publishing.
No. Client users only see the clients they were added to. Agency staff see the clients of their own agency.
Cancelling stops the next renewal; it does not delete anything. You keep access to sign in, read, export and tidy up your data. Ask us if you want the agency deleted.
Send a request through the contact page from the e-mail address on the account. We may need to confirm it is you before acting on it.
Yes. We update the date at the top of this page, and for significant changes we tell account owners by e-mail before they take effect.
Moving an agency to a new scheduler is mostly about not losing anything and not posting anything twice. A step-by-step checklist from inventory to cut-over to cancelling the old tool.
Read more: Switching social media schedulers: a migration checklist for agenciesMost monthly social reports are exported charts nobody opens twice. A structure for a one-page report that answers the client's question, explains the numbers and ends with decisions.
Read more: How to write a monthly social media report clients actually readAI can draft a caption in seconds, but someone still signs it off. A practical checklist for reviewing AI-assisted social posts: facts, claims, voice, per-network fit and accessibility.
Read more: Reviewing AI-written captions: a checklist before anything is approved
