Content OS
Privacy policy
Last updated
Content OS turns your long recordings into pieces you publish on your own channels. This service is run by CONTENT-OS ("we"). This page says what we collect, why, where it goes and what you can do about it.
Questions about this page or about your data: [email protected].
What we collect
We collect what you give us and what the service needs to do its work for you.
- Your account: your email address and your password, which our sign-in provider keeps as a hash, never as text we can read.
- Your workspace: its name, its members and their roles.
- What you bring in: recordings and other files, their transcripts, the pieces written from them, your notes, plans and settings.
- Your connected channels: when you connect an account on YouTube, LinkedIn, X, Facebook, Instagram, Threads or TikTok, we store the name and identifier of the account and the access tokens the network gives us. Where you choose to have a browser publish to Facebook for you, we store the session cookie you give us for it. Tokens and cookies are encrypted before they are stored.
- What is already on your channels: the titles and details of what you published, and a copy of a video of your own that you ask us to fetch from its public address.
- Results: the figures a network reports for what you published, such as views and likes.
- Public comments under what you published on YouTube: the text of a comment, and the name and channel address of the person who wrote it. These are people who are not members of your workspace.
- A record of the work done for your workspace, such as minutes transcribed, so that usage can be counted.
- Your device, if you install the Apple app: the token Apple gives the app so that we can send it notifications.
- Technical records: the cookies that keep you signed in, the address your requests come from in our providers' logs and, where we have switched them on, error reports, usage analytics and recordings of your sessions in the service, in which what you type and what you wrote is masked.
How we use it
We use your data to run the service for you: to store and transcribe what you bring in, to write pieces from it, to publish the pieces that were approved in your workspace to the channels you connected, to show you their results, to keep the service secure and to answer you when you write to us.
We do not sell your data. We do not use it for advertising.
Google and YouTube data
Content OS uses YouTube API Services. When you connect a YouTube channel you also agree to the YouTube Terms of Service, and the Google Privacy Policy describes what Google does with your data.
You choose whether to connect a Google account, and you see each permission on Google's own screen before you grant it. We ask for these permissions, and use each one only for this:
- Publish to your YouTube channel: we send YouTube a video and its title, description and thumbnail only after it was approved in your workspace.
- Read your channel: its name, its picture, the videos already on it and the public comments under them, so your workspace shows what you have published, plans around it and shows you who answered. We also use it to set the details, such as the chapters in the description, of a video on your channel that you chose to keep in step with your workspace, whether we published it or it was there before.
- Add captions, from the transcript in your workspace, to a video on your channel that you chose to keep in step with your workspace.
- Read how your videos did (for example views and watch time), to show you results and to learn what works for your channel. We never change anything with this permission.
- Only if you link a Google Drive: read the files in the folders you choose, so recordings can be brought into your workspace, list your folders so that you can choose one and, when you ask, look a file up by its name anywhere in your Drive. We never change, move or delete a file in your Drive.
How we handle Google user data
Content OS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain words: we use Google user data only to provide the features above to you. We do not sell it, we do not use it for advertising, and we do not use it to develop, improve or train generalised artificial intelligence or machine learning models. We pass it on only to the providers listed below, to provide or improve the features you use, where the law requires it, or with your consent. Nobody at our company reads it unless you ask us for help, it is needed for security, or the law requires it.
You can take our access away at any time in your Google Account, on the page linked below. From then on we can read and change nothing there. What we already stored stays until you ask: write to [email protected] and we delete the tokens and the YouTube data we stored for that account within 30 days.
Who receives it
We give your data to other companies only so that they can do a part of the service for us or for you, and to an authority where the law requires it. The companies are:
- Supabase: the database, the sign-in and the private file storage.
- Fly.io: the servers the service runs on.
- ElevenLabs: transcription. It receives the audio of a recording you asked to have transcribed, or the public address of your video so that it can fetch it.
- Anthropic: writing and reading. It receives the transcript and your notes when pieces are written, and also titles and file names, the results of what you published and the public comments under it, so that the service can sort your files, learn what works and tell you who answered.
- The networks you connected: each receives the piece that was approved for it, when it is published. Some fetch the file themselves, through a short-lived link we make for them.
- A scheduler or an AI agent, only if you connect one yourself: it receives what you send it or let it read.
- Apple: notifications to the Apple app, if you installed it.
- Canva: only if you connect a Canva account, the designs you make or bring from it.
- Stripe: payments, once paid plans are open.
- Sentry and PostHog: error reports, usage analytics and session recordings, where we have switched them on.
How long we keep it
We keep your data while your account is open. Write to [email protected] to have your account and its data deleted. We delete it within 30 days, except what the law requires us to keep.
How we protect it
Access tokens and session cookies are encrypted before they are stored. Your files are in private storage and are reached only through short-lived links, made for a signed-in member of your workspace or for the network or provider that needs the file. Each workspace reads only its own data. No service can promise perfect security, and if something goes wrong that affects your data we will tell you.
Your choices
You can ask us for a copy of your data, to correct it or to delete it, by writing to [email protected]. You can take our access to a channel away on the network itself, and ask us to delete what we stored for it. Depending on where you live, the law may give you further rights over your data, and you may complain to your data protection authority.
Cookies
We use the cookies that keep you signed in, and your browser's storage for your own settings. Where usage analytics are switched on, they use a cookie too. We use no advertising cookies.
Children
The service is not meant for anyone under 16, and we do not knowingly collect their data.
Changes to this page
When what we do with your data changes, we change this page and its date. If the change is significant we tell you in the service or by email before it takes effect.