WritecastPrivacy Policy
Writecast lets businesses write, schedule and publish posts to the Facebook Pages and LinkedIn profiles and company pages they manage. We collect only what's needed to publish those posts, and we don't collect data about the people who see or interact with them.
Who we are
[Your organization’s legal name], [registered address] ("we", "us") operates Writecast. Contact us at [privacy contact email] with any privacy question or request.
What we collect and why
| Data | Source | Why we use it |
|---|---|---|
| Your name, email address and a hashed password | You, when you create an account | To sign you in and let workspace owners add you to their team |
| Workspace names and team membership | You and your team | To keep each organization's accounts and posts separate |
| Facebook Page ID, name, picture and Page access token | Facebook, when you connect your Pages | To publish posts to those Pages |
| LinkedIn member ID, name, profile photo and access token | LinkedIn, when you connect your profile | To publish posts to your own LinkedIn profile, at your request |
| LinkedIn company page IDs and names | LinkedIn, for pages where you are an administrator or content admin | To publish posts as those pages |
| Post text, links, images and scheduled times | You and your team | To publish each post at the chosen time |
| Reaction and comment counts for your own published posts | To show how a post performed. We read totals only, never who reacted or commented. | |
| Plan, subscription status and Paddle customer and subscription IDs | Paddle, our payment reseller | To apply your plan's limits. Card and payment details go to Paddle directly; we never see or store them. |
| Your choices about email: the "product tips and updates" box, when and where you made the choice, and when you unsubscribed | You, at sign-up, in Settings or through an unsubscribe link | To honour your choice, and to be able to show when you gave or withdrew your consent (the consent record) |
| A record of each AI rewrite: when it ran, which workspace and member asked, the outcome, and the number of characters and tokens. Never the text itself | Writecast, when you use Rewrite with AI | To enforce each plan's monthly allowance and the daily limit per person, and to spot abuse. The text you choose to rewrite goes to Anthropic only for that rewrite (see the subprocessors below) |
| Which lifecycle emails we sent you (welcome, setup reminders, product tips) and when | Writecast | So we never send the same one twice and can show what we sent you |
How you signed up (the sign-up source): the plan you looked at, the campaign tags (utm_ values, up to 100 characters each) and the name of the website in the link you came with | The link you used to reach sign-up | To see which pages and launches bring people. Stored with the workspace you created. |
| The day of your last request to the app | Writecast | Only to decide whether you have been away for a while before we send you a product-tips email you opted in to |
| Cookies | Writecast | To keep you signed in and to finish sign-in safely. See Cookies below. We use no tracking or advertising cookies. |
What we don't do
- We don't collect, store or analyze data about LinkedIn or Facebook members who view, react to or comment on your posts.
- We don't sell, rent or share your data with advertisers or data brokers. We share it only with the service providers listed under Subprocessors, to run Writecast. Paddle processes payments under its own privacy policy as the merchant of record.
- We don't use platform data to build profiles, target ads or train machine-learning models.
- We never post anything you or your team didn't write or schedule.
Subprocessors
These providers process data on our behalf, only for the purpose shown.
| Provider | Purpose |
|---|---|
| Cloudflare | R2 storage for your uploaded images, CDN, and Turnstile bot checks on sign-up and sign-in forms |
| OneSignal | Email and push notifications we send you |
| Paddle | Payments, as merchant of record (cards and taxes) |
| SSLCommerz | Payments in Bangladesh |
| Anthropic | AI rewrite: only the text you choose to send for a rewrite |
| Sentry | Error reports, so we can fix bugs |
| Grafana Labs | Metrics and logs about how the service runs |
| Sign-in with Google, if you choose it | |
| Meta and LinkedIn | Publishing the posts you schedule to your Pages and profiles |
| our hosting provider | Hosting provider: the servers and database that run Writecast |
Cookies
We set only essential cookies. They are needed to sign you in and to keep sign-in safe, so they don't ask for consent. We use no third-party analytics and no advertising cookies; how we count visits is described next.
| Cookie | Purpose |
|---|---|
wc_session | Keeps you signed in |
wc_device | Recognizes a device you have signed in from, to protect against password guessing |
wc_oauth | Protects a sign-in with Google while it is in progress |
wc_mfa | Holds a two-step verification challenge between your password and your code |
Counting visits and product use
We count how our own site and app are used, with our own software on our own servers. No other company receives this data, and nothing is set on your device: no cookie and no browser storage.
- Our public website: when a page loads or you click a "Start free" button or the pricing switch, your browser tells us the page, its language, the campaign tag in the link you came with (
utm_values) and the website you came from (its name only). We do not store your IP address or your browser details. To count visitors we turn them into a short code: a one-way hash of your address and browser made with a secret that is replaced every day. We do not use the code to identify you or to follow you from day to day, and a different day gives a different code. The secret is kept for at most 48 hours, and is removed from the server's disk log at its next daily compaction; until then the code is a pseudonym, not an anonymous number. Where our network provider tells us, we also keep your country. - Objecting: we do not count you at all if your browser sends the Global Privacy Control or Do Not Track signal, and we ignore robots. Treat that signal as your objection to this counting.
- Inside the app (signed in): we record the main steps (for example signing up, verifying your email, connecting an account, creating, scheduling or publishing a post, reaching a plan limit, upgrading, and that you were active on a day), with your account and workspace identifiers and a few non-personal details such as the plan or platform name. They contain no message text, no names and no email addresses. A few events belong to a workspace and not to a person (for example that a workspace's payment went through); turning counting off in your own settings does not stop those, and they are removed when the workspace is deleted. We use these events to see where people get stuck and whether the product works, not for advertising.
- Your choice: you can turn product-use counting off at any time in Settings › Security & privacy. It stops recording new events for your account from then on. Your own events are included in "Download your data" and are removed when you delete your account.
- How long: each individual event is kept for 180 days and then deleted. We keep only daily totals (counts per day, with no identifiers) after that.
We rely on our legitimate interest in running and improving the service with the least data possible. This basis is still being confirmed by our compliance review, and we will update this notice if it changes.
Emails we send you
- Account and security email (confirming your address, password resets, sign-in links, security notices, receipts and deletion notices) is always sent and cannot be switched off while you have an account. Unsubscribing from the other emails never stops it.
- Setup email (service messages): when you sign up we send a welcome email and, if you have not yet connected an account or scheduled a post, up to two short reminders. They help you finish what you started, we send them without a checkbox on the basis of our legitimate interest in helping new users, at most three ever, they stop when the step is done, and each has an unsubscribe link and our postal address.
- Product tips and updates (including win-back emails such as "we miss you" after you haven't used Writecast for 30 days) are marketing. We send them only if you ticked the unchecked "Send me product tips and updates" box at sign-up or switched it on in Settings › Notifications, which is your consent. To decide that you have been away we use your last request to the app, your sign-in dates and the "active on a day" events (
session_active), and only for people who opted in. - Withdrawing consent and unsubscribing: switch the option off in Settings › Notifications, or use the "Stop these emails" link in any of these emails (also available as the one-click unsubscribe of your mail app). The link stops all setup and marketing email; the Settings switch stops product tips. Either takes effect before the next email. We keep a consent record: when and where you opted in, and when you withdrew or unsubscribed.
- Emails go through OneSignal (see Subprocessors). They contain your workspace's name and no post content; links in them are not rewritten for click tracking.
How we protect data
Platform access tokens are encrypted at rest with AES-256. Passwords are stored only as salted hashes. Each workspace's data is kept separate, and only its members can see it. Data is stored on servers we control and is sent to Facebook or LinkedIn only to publish your posts or read their totals.
How long we keep data
- Connected accounts: until you disconnect them, or until the platform expires or revokes access. Disconnecting deletes the token immediately.
- Posts and images: until you delete them.
- Visit and product-use events: 180 days; daily totals without identifiers are kept longer.
- Post totals: fetched when viewed, not stored.
- Email choices and the consent record, which lifecycle emails we sent you, and your last-request date: kept for as long as your account exists and deleted with it (the record of what we sent is removed when your account is deleted).
- Sign-up source (campaign tags, plan you looked at, referring site): kept with the workspace for as long as the workspace exists, and deleted with it; the daily totals made from it are kept without identifiers, and a tag seen on fewer than five visits in a day is not kept as its own value.
- Emails we sent you (outbox): kept 90 days after sending or failing. When your account is deleted, we delete every email row for your address, queued or already sent or failed.
- Rate-limit counters: short-lived counters (for sign-in attempts and similar) kept for at most one hour, then discarded.
- AI rewrite records (when, workspace, outcome, character and token counts; never the text): kept 400 days, then deleted. Your own records are in your data export.
- Billing events from Paddle: kept 1 year, for support and accounting.
- Data exports: available to download for 7 days, then deleted.
- Your account: when you delete it in Settings, it stays recoverable for a 14-day grace period (you can cancel in that time). After that we delete your user record and any workspace where you are the only member. Shared workspaces keep their posts, which no longer name you.
Your rights
You can export your data and delete your account yourself in Settings › Security & privacy. An export is a zip of your profile (including your email and analytics choices and your consent record), memberships (with your sign-up source for workspaces you own), your own posts, the accounts you connected (never their tokens), the lifecycle emails we sent you, the product events recorded about you and your uploaded images. Deleting your account has a 14-day grace period, then it is permanent. You can also email [privacy contact email] to ask for access, correction or deletion. We respond within 30 days.
Facebook data deletion
If you connected Facebook Pages, you can delete that data at any time: disconnect the Page in Writecast, remove the app in your Facebook settings (we then delete the Pages you connected through it), or email us. Details and your request's status: Data deletion instructions. LinkedIn offers no deletion callback; to remove LinkedIn data, disconnect the profile or page in Writecast or delete your account.
Your choices
- Disconnect any Page or profile from the sidebar in Writecast.
- Revoke on LinkedIn: Settings → Data privacy → Permitted services.
- Revoke on Facebook: Settings → Business integrations.
- Access or deletion: in Settings › Security & privacy, or email [privacy contact email]. We respond within 30 days.
Platform terms
Our use of LinkedIn and Facebook data follows the LinkedIn API Terms of Use and the Meta Platform Terms. We request only the permissions needed to publish posts and read your own posts' totals.
Changes
If we change this policy, we'll update the date above and tell workspace owners by email before material changes take effect.
Contact
[Your organization’s legal name]
[registered address]
[privacy contact email] · https://writecast.app