Where your data goes and who can touch it
What SocialOS does with your accounts, files and posts. Everything here describes how the product works today, and where something does not exist yet, we say so.
Official APIs only
SocialOS publishes through the official Instagram, Facebook and LinkedIn APIs. Meta verified our business as a Tech Provider in August 2026.
There are no browser bots or extensions, and nothing signs in with your password. You connect an account on the network's own sign-in screen and can remove our access there at any time.
TikTok requires a person to confirm every post, so SocialOS never posts to TikTok without your tap.
Where the data is kept
The application and its data run on Hetzner servers in Nuremberg, Germany. Finished images, videos and our backups are stored in Cloudflare R2, in its Eastern Europe location.
To write text and render video, the parts of your data a task needs are sent to AI providers, and some of them run outside the EU. The sub-processor list names each one, what it sees and the country it runs in.
DPA and privacy
When SocialOS handles your customers' data, we act as your processor. The Data Processing Agreement covers what we process, on whose instructions, with which sub-processors and what happens after a breach.
Data about you as our customer is covered by the privacy policy.
Is my data used to train AI?
SocialOS has no model of its own, so we train nothing on your posts, photos or brand facts.
Text, images and video are generated by Google (Gemini), BytePlus and fal.ai through their paid APIs. Google's and BytePlus's terms for that use say they do not train models on customer data without permission, and fal.ai states that it does not train on customer data.
AI labels under the AI Act
Images and videos generated by SocialOS are marked in their IPTC/XMP metadata: the digitalSourceType field is set to trainedAlgorithmicMedia, the standard IPTC value for AI-generated media. Files you upload yourself are left as they are.
This is a metadata label, not a C2PA signature, so it does not prove origin cryptographically. We do not offer C2PA signing yet.
Each post also has a switch that adds a visible line to the caption saying it was made with AI. Whether a post needs one depends on its content, so the choice is yours.
Approvals and autopilot
By default every post waits in the approval queue until someone on your team approves it.
Autopilot is a separate switch for each brand and stays off until you turn it on. With it on, a brand still has a daily publishing limit (10 posts by default); anything over it goes back to the queue. You can set quiet hours when nothing goes out on its own, and switch autopilot off at any moment.
An AI app you connect, such as ChatGPT or Claude, publishes or replies only if you gave it that permission. For each connection you choose: publish immediately when you ask it in the chat (your confirmation there is the approval) or ask you first in SocialOS. A connection that publishes immediately has its own daily limit (10 posts and 30 replies by default), every action is logged with the app's name, and you can switch it to “ask me first” or disconnect it at any time.
When you delete your account
If other people in your organisation still use SocialOS, only your access is removed. Posts, brands and connected accounts belong to the business and stay with it.
If you are the last member, the whole organisation is deleted from our server: brands, posts, media, connected accounts and credits. Before the files are erased, we ask Meta to revoke SocialOS's access to your Instagram and Facebook accounts. LinkedIn tokens are deleted on our side, and you can also remove the app in your LinkedIn settings.
Deleting the account does not reach copies in our backup storage or finished media already uploaded to Cloudflare R2. If you want those removed too, write to us.
Sign-in and secrets
Passwords are stored only as salted PBKDF2-SHA256 hashes with 200,000 rounds, never as plain text.
Access tokens for your social accounts are encrypted on disk, and the key is kept outside the data folder.
Your browser holds a random session token in an HttpOnly cookie that page scripts cannot read. A session ends after 7 days without activity, and repeated failed sign-ins are paused.
Two-factor sign-in is not available yet. If you sign in with Google, your Google account's own two-step verification applies.
Questions before you connect anything?
Ask us first. We reply on working days, usually the same day.