Privacy policy

Last updated 2026-10-05

SociaOS is a self-hosted tool run by one owner to publish the owner's own posts to the owner's own social media accounts. Everything it stores lives in the owner's own database on the owner's own server. There is no other user. The data is sent only to the platforms the owner posts to and, for backups, the owner's own Drive.

What is collected

• OAuth tokens for each connected account (access and refresh tokens). They are encrypted at rest in the owner's database.
• The post content the owner authored: captions, titles, hashtags, schedule times and the links of the published posts.
• The media files the owner uploaded: images and videos.
• The Drive file ids of the media SociaOS copied from the owner's Drive and the id of the owner's Google Sheet.
• The account id and handle (display name) of each connected account. For YouTube that is the YouTube channel id and the channel handle or title. For TikTok it is the TikTok open id, the username and display name, and the posting options TikTok returns for the account (its nickname, the address of its avatar, the privacy levels it offers, whether comments, duets and stitches are switched off, and the longest video it allows).
• The ids and links of the videos and posts SociaOS itself published for the owner, so it can show their status and delete them on request. They stay on the post records as the owner's own publishing history.
• Operational records: the import log (what was imported and with what result), the log lines and response ids of each publish attempt, and the container logs, which rotate at 3 files of 10 MB per service. They hold no tokens.
• If the owner connects their own Google account for backups, its tokens, encrypted, in the settings table. Disconnecting it in Settings deletes them at once.

SociaOS does not collect or store anything about other people: not their profiles, comments, followers, watch history or videos.

Why

Only to do what the owner asked: sign in to the owner's accounts, publish the owner's posts at the chosen time and report the result. The data is used for nothing else.

Retention and deletion

How to delete data, and what each deletion removes, is on the data deletion page.

• Tokens are kept until the owner disconnects the account. Disconnect deletes the stored tokens at once. It asks the platform to revoke the grant only when the grant is identified and no other SociaOS connection holds it, which today is never, because grants are not recorded yet; so also remove SociaOS in the platform's own connected-apps settings. Disconnect also deletes the stored account id, handle and other connection details of that account.
• Post records, including published links, are kept as the owner's history. Deleting a post removes it from the platforms and marks the record deleted.
• Uploaded media copies on the server are removed by a weekly cleanup once they are older than 30 days (or the period the owner sets) and no open post needs them. The cleanup only reports what it would remove until the owner turns it on, so the copies stay until then. The originals stay in the owner's own Drive.
• Backups: the database is dumped nightly. The server keeps the last 7 nightly files. A copy encrypted with a key derived from the owner's secret is saved to a folder in the owner's own Google Drive, where it stays until the owner deletes it.

Sharing, sale and tracking

Data is never sold. It is sent only to the platforms the owner posts to and, for backups, the owner's own Drive. There is no advertising and no third-party user data. There are no analytics and no tracking.

Cookies

Only first-party cookies for the signed-in owner: the session, the selected brand, and a short-lived state cookie while an account is being connected. No third-party, analytics or advertising cookies. These public pages set no cookies.

Google user data

SociaOS'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.

Google access is used only for the features the owner turns on: reading the owner's Google Sheets and Drive folders that the owner shares with SociaOS, writing results back to that sheet, saving backups into a folder SociaOS creates in the owner's Drive, and the YouTube features below.

YouTube API Services

SociaOS uses YouTube API Services to upload the owner's own videos to the owner's own channels and to set their visibility. By connecting a YouTube channel, the owner agrees to be bound by the YouTube Terms of Service and acknowledges the Google Privacy Policy. SociaOS stores the channel id and the channel handle or title and the ids of the videos it uploaded, and no YouTube data about anyone else.

For YouTube, Disconnect also deletes the stored channel id and name. If access is removed at Google instead, SociaOS deletes them within 7 days of noticing. Post records keep the link and id of each video SociaOS uploaded, as the owner's own publishing history. Backups made before then may still contain these values: up to 7 nights on the server, and in the owner's Drive until the owner deletes them.

To revoke SociaOS's access to YouTube, remove SociaOS at myaccount.google.com/permissions. Disconnect on the Accounts page deletes the stored tokens and channel details at once; it does not end the grant at Google today, so also remove SociaOS at that page.

TikTok

Data accessed through TikTok's API (the open id, the username, the display name and nickname, the avatar address and the posting options TikTok returns for the account) is used only to post the owner's content to the owner's own account. To revoke access, press Disconnect on the Accounts page or remove SociaOS in the TikTok app settings.

Contact

Questions or requests about this policy: tvoda25@gmail.com.

See also the about page and the terms of service.