Privacy policy
Last updated 19 November 2026
transmit4u is a tool for writing a post once and publishing it to several social networks. This page explains where your data is hosted, what data we store, how long it is kept, and how it is removed.
Where your data is hosted & what we store
transmit4u does not operate in-house physical servers. Our web application and dedicated cloud database are hosted on managed cloud infrastructure provided by Railway (Railway Corp.), which is provisioned and controlled by transmit4u:
- Your transmit4u account — name, email address, and a hashed password if you signed up with one, stored in our managed Railway database. If you sign in with Google, we store the identifier Google gives us; we never see your Google password.
- Connected social accounts — for each network you connect, the account’s public handle, display name, avatar URL, and the access token the network issued. Tokens are encrypted at rest with AES-256-GCM before being stored in our managed Railway database. transmit4u never sees or stores your password for any social network.
- Your posts & media — the caption text, schedule time, target accounts, and publish status. Uploaded images and videos are stored in our Railway-hosted storage and database only until the post is published to your targeted social media accounts. Immediately after a post is published to the targeted accounts, the uploaded media is permanently removed from our database and storage.
7-day (one-week) data retention & scheduling policy
We keep post and media data in our Railway database only for as long as needed to deliver your posts:
- Maximum 7-day scheduling window — Across all plans, posts can be scheduled up to 7 days (one week) in advance.
- Immediate media removal after publishing — Uploaded images and videos remain in our Railway storage only while a post is in draft, scheduled, or awaiting retry. As soon as the post is published to the targeted social media accounts, the media files are immediately deleted.
- Automatic 7-day expiration — All post records—including drafts, scheduled posts, failed or partial retries, and published post history—are retained in our Railway database for only 7 days (one week). After 7 days, drafts, unretried failures, and old post data are automatically and permanently deleted.
- Unattached uploads — Media uploaded in the composer that is not saved to a draft or scheduled post is automatically removed after sign-out or shortly after your browser tab closes or becomes inactive.
Google and YouTube data
If you sign in with Google, we use the Google account identifier, verified email address, and available name and profile picture to create or find your transmit4u account. We verify the Google sign-in token and do not store your Google password.
If you connect a YouTube channel, we use YouTube read-only access to retrieve its channel ID, name, handle, and thumbnail so you can identify and select it on the Accounts page. We use YouTube upload access to publish the video, title, and description you choose to that channel when you publish now or schedule a post. We store the channel details, encrypted connection tokens, and the post and its result in our managed Railway database as described above. We do not read your YouTube video contents, analytics, subscribers, or other channels’ data.
Who receives Google user data
Railway (Railway Corp.), our cloud infrastructure and database hosting provider, processes Google sign-in details, connected YouTube channel details, and encrypted Google connection tokens on our behalf to host the transmit4u application and database. We use this processing solely to keep your account and connections available and to carry out the posts you request.
When you choose to publish to YouTube, we send the video, title, and description you selected to YouTube through its API. We do not send your Google account identifier, email, YouTube channel details, or Google connection tokens to other connected social networks. We do not sell Google user data or share it with advertisers, data brokers, or other third parties for their own purposes, and we do not use it for advertising.
How we protect your data
Our public website uses HTTPS to protect data sent between your browser and transmit4u. We encrypt connected-account access and refresh tokens, including Google tokens, before storing them in our Railway database using AES-256-GCM. The encryption key is supplied to the app separately from database storage. Account passwords are stored as cryptographic hashes, not as readable passwords. Sign-in sessions use random session tokens in HTTP-only cookies; on our HTTPS site, these cookies are marked Secure. App requests for your connected accounts and posts require a valid signed-in session.
TikTok data
If you connect a TikTok account, transmit4u uses TikTok Login Kit and the TikTok Content Posting API with these permissions:
- user.info.basic — your TikTok account’s open ID, display name and avatar, so you can see and select the account on the Accounts page.
- video.upload — to send a video you chose to your TikTok drafts (inbox), where you finish and post it in the TikTok app.
- video.publish — to post a video you chose directly to your TikTok account, when you publish now or at the time you scheduled.
We store the open ID, display name, @username, avatar URL, which of these permissions you granted, and the access and refresh tokens TikTok issues (encrypted at rest with AES-256-GCM) in our managed Railway database. Before each direct post we ask TikTok for your current posting options (who can view your videos, whether comments, Duet and Stitch are allowed, and the longest video you can post) so the compose screen can show them; we use these only to display the choices and do not store them.
When you publish to TikTok, we send TikTok the video, caption and the settings you chose (who can view it, comments, Duet, Stitch, and any commercial content disclosure), and then check TikTok for the post’s status. The video is removed from our storage after publishing, as described above. We do not read your TikTok videos, likes, comments, followers, messages, analytics, or anyone else’s TikTok data, and we do not sell TikTok data or use it for advertising.
To stop transmit4u’s access, disconnect the account on the Accounts page (this deletes its tokens from our database immediately), or in the TikTok app go to Settings and privacy → Security → Apps and services → transmit4u → Remove access. See also Data deletion.
AI mode
When AI mode is available and you choose to use it, the description you write, the networks you selected, and any Instagram usernames you added as collaborators or tags are sent to OpenAI through its API so it can suggest a caption, and for YouTube a title, for each network. We send nothing else: no media, no account tokens, no email address. The suggestions are placed in your post, where you can edit them before publishing. OpenAI processes this text under its privacy policy and API terms. If you don’t use AI mode, nothing is sent to OpenAI.
Data from other social networks
For other connected networks, transmit4u requests the permissions needed to identify the account and publish your posts. If you connect a Facebook Page, the Page activity screen also reads that Page’s name, picture, follower and like counts, and its recent published posts (text, image, link, date, and like, comment and share totals) so you can see how your posts are doing. This is fetched from Facebook each time you open the screen and is not stored. It does not read the content of comments, your messages, who your followers are, or anyone else’s data. Instagram usernames you add as collaborators or tagged people are stored with the post and sent to Instagram when it publishes, so those accounts can be invited or tagged. Use of Meta platform data is governed by the Meta Platform Terms.
Deleting your data
You can disconnect any social account from the Accounts page at any time; this immediately deletes its token from our Railway database. You can also delete any post at any time from the Posts or Calendar page, or let it automatically expire after 7 days. For a whole-account deletion request, see Data deletion.
Cookies
transmit4u sets one session cookie to keep you signed in, and a short-lived cookie during a network connection to protect against forged requests. No tracking or analytics cookies.
Contact
Questions about this policy or your data? Contact support without signing in.