Privacy policy
Last updated November 16, 2026
Draft text, not legal advice. Have a lawyer review this page before you rely on it.
Before launch: set the company details in the site build settings, so the name, address and emails on this page are real. A production build refuses to run until you do.
Who we are
Fanouts is a social media scheduler. It is run by the business below, which decides how your data is used and is responsible for it. This page explains what we collect, why, how long we keep it, and how you can have it deleted.
Your registered business name
Your registered business address
General: contact@your-domain.example
Support and privacy requests: support@your-domain.example
What we collect
- Account details: your name, your email address and a hashed password. We store the password only as an argon2id hash and cannot read it.
- Workspace content: the posts, captions, media files, comments, notes and approvals you and your team create, and the plan and team settings of your workspaces.
- Connected account data: what Facebook, Instagram, YouTube and the other networks give us when you connect an account. The next two sections list it.
- Billing details: if you buy a paid plan, a payment provider handles your payment. We do not store card numbers.
- Technical data: one session cookie that keeps you signed in, and server logs with errors and request details. Fanouts has no advertising or tracking cookies.
Facebook and Instagram data
When you connect a Facebook Page or an Instagram professional account, you approve a list of permissions on Facebook or Instagram. Fanouts reads and writes only the following, and only for the account you connected:
- Profile details: the Page or account name, handle or username, profile picture, account type, internal ID and follower count. We use them to show which account you are posting to.
- Posts published through Fanouts: the post ID and link of each post we publish, so we can show it in your calendar and match its results. We also publish the caption, photos, videos and, where you added one and the permission is granted, the first comment that you wrote.
- Insights for those posts and for the account: counts such as impressions, reach, views, likes, comments, shares, saves and followers. We show them in Fanouts analytics and reports. We read counts, not the text of comments.
We do not read your private messages, your personal Facebook profile, your friends or the content of posts that Fanouts did not publish. We do not use Facebook or Instagram data for advertising, we do not sell it, and we share it only as the sharing section below describes.
We keep this data while the account stays connected and in your workspace history afterwards, as the retention section below explains. You can ask us to delete it at any time. We delete it within 30 days of a request.
Fanouts supports Meta’s data deletion callback. When you remove Fanouts in your Facebook or Instagram settings and ask Meta to delete your data, Meta tells us. We then delete, straight away, the access tokens, analytics results, the network’s IDs for our posts and error details, and the profile details (handle, picture, follower count and account type) of the accounts you connected. We keep only the account name, so your past posts still show where they went, and your own posts and media stay in your workspace until you delete the workspace. We give you a confirmation code, and you can check the request on the data deletion status page. If you only remove Fanouts without asking Meta to delete data, we delete the access tokens. To ask for deletion yourself, follow the steps on the data deletion page.
Google and YouTube data
When you connect a YouTube channel, you approve access on Google’s consent screen. Fanouts uses the access for these things only:
- Upload videos that you scheduled in Fanouts to the channel you connected, with the title, description and settings you chose.
- Read the channel’s name, ID, picture and subscriber count, so we can show which channel you are posting to.
- Read view, like and comment counts of the videos that Fanouts uploaded, to show them in analytics and reports.
We do not read your watch history, your playlists, your private videos or videos that Fanouts did not upload, and we do not change or delete anything on your channel except to upload the videos you scheduled.
When you connect a Google Business Profile, Fanouts uses the access to list the locations you manage, so you can pick which to connect, and to publish the updates you scheduled to those locations. We do not read or change your reviews, photos, opening hours or other profile details.
Fanouts uses YouTube API Services. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google’s Privacy Policy explains how Google handles your data.
You can revoke Fanouts’ access to your Google data at any time on the Google security permissions page. Revoking there stops Fanouts from reaching your channel. See “Disconnecting and revoking” below for what we do with the data we already hold.
Google API Services User Data Policy and Limited Use
Fanouts’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
You can read that policy at developers.google.com/terms/api-services-user-data-policy. In plain words, for the data we get from Google APIs:
- We use it only to give you the features you see in Fanouts: publishing your scheduled videos and showing your channel and its results.
- We do not transfer it to others, except where needed to provide those features, to follow the law, or as part of a merger or sale of the business with notice to you.
- We do not use it for advertising, and we do not sell it.
- We do not use it to develop, improve or train generalized AI or machine learning models.
- People at Fanouts do not read it, unless you ask us to for support, it is needed to investigate abuse or a security problem, or the law requires it. Otherwise we use it only in aggregated and anonymized form for running the service.
Access tokens and how we protect them
You sign in on the network itself, so Fanouts never sees your network password. The network gives us an access token, and sometimes a refresh token. We store both encrypted at rest with AES-256-GCM, and decrypt them only inside our servers to publish and to read the data listed above. We never write tokens to logs. Error logs have token values removed.
Your Fanouts password is stored as an argon2id hash, and sessions are random tokens that we store hashed. Connections to Fanouts use HTTPS. Uploaded media is stored in private object storage and reaches a network only through a link that expires.
How we use data
We use your data to run Fanouts: to publish what you schedule, show your calendar and analytics, manage approvals, send service emails (such as invitations, sign-in help and failed-post notices), give support, bill you and prevent abuse. We do not sell your data and we do not use your posts or network data for advertising.
How long we keep data
- Access tokens: kept while the account is connected, and removed when you disconnect it or the network tells us the access was revoked. Unfinished connection attempts are removed within an hour of expiring.
- Account details, posts, media and analytics: kept while your workspace exists. Deleting a workspace removes its posts, media, connected accounts and analytics.
- After you disconnect an account, its name, picture and past results stay in your workspace so your calendar and reports still make sense. We delete them when you delete the workspace or ask us to, within 30 days.
- Backups and records we must keep by law may last a little longer, and are then deleted.
Disconnecting and revoking
Disconnecting an account in Fanouts deletes the access token and refresh token we hold for it, so Fanouts can no longer publish to it or read it. For YouTube and Facebook we also ask the network to cancel the authorization, on a best-effort basis. Instagram gives us no way to cancel an authorization, so for Instagram, and whenever you want to be sure, also remove Fanouts where you granted it. If a publish fails because the network says the access was revoked, we delete the tokens too.
You can remove Fanouts yourself at any time:
- Google and YouTube: Google security permissions.
- Facebook: Settings, Business integrations.
- Instagram: Apps and websites in your account settings.
Deleting your data
- Disconnect a network in Fanouts. This removes the tokens we hold.
- Delete a workspace in Fanouts settings. This removes its posts, media, connected accounts and analytics.
- Remove Fanouts in your Facebook or Instagram settings. This removes the tokens we hold. If you also ask Meta to delete your data, Meta tells us and we delete the data tied to that account straight away.
- Use the data deletion page, which has the full steps, or email support@your-domain.example from the address on your account. We reply within 7 days and delete within 30 days.
Posts already published on a network stay there. Delete them on that network.
Your choices
You can see, correct, export or delete your data. Ask us by email for anything you cannot do in the app. If you think we handled your data wrongly, tell us first so we can fix it, and you may also contact the data protection authority where you live.
Changes to this policy
If we change this policy in a way that matters, we will tell you by email or in the app before the change applies, and we will update the date at the top. If a change needs new permission from Google or Meta, we will ask you again before using it.
Contact
Questions, requests and complaints about privacy: support@your-domain.example.
Your registered business name
Your registered business address
General: contact@your-domain.example
Support and privacy requests: support@your-domain.example