Privacy Policy

Who is responsible for your data

The data controller is Daniil Laureanti, the independent developer of SynAirgy.ai. For privacy enquiries, contact the Telegram bot @SynairgyCrosspostBot, using the command /privacy.

Data we process

• Your Telegram ID, name, username and interface language.
• Identifiers, names and connection status of linked channels.
• Videos, captions, publication times, queue entries, delivery results and error details.
• For Facebook: the ID and name of a managed Page, the Meta user ID used for data deletion, granted permissions and the Page access token.
• For Instagram: the professional account’s ID, username and type, granted permissions and access expiry.
• For TikTok: Open ID, username, selected posting settings, permissions and access/refresh token expiry.
• For YouTube: channel ID, title and handle, video title and visibility, granted Google permissions and access/refresh token expiry.
• For Threads: profile ID and username, granted profile and publishing permissions, encrypted access token and expiry, and identifiers for video containers and published posts. Replies, messages, followers and advertising data are not requested.
• For LinkedIn: personal profile ID and name, permissions, encrypted access and its expiry, and identifiers for uploads and published posts. LinkedIn email addresses, contacts and messages are not requested.
• Technical information needed to protect webhooks, prevent duplicates and retry operations safely.
• For payments: Stripe Customer and Subscription IDs, the selected plan, subscription status and billing period. Card details are entered on Stripe and are not received by Crosspost Engine.
• Minimal product telemetry: the action started, whether it succeeded or failed, the network, plan and an error code without identifying content. Post text, file names, access tokens and IP addresses are not recorded in this report.

Facebook, Telegram, Instagram, Threads, TikTok, LinkedIn and Google passwords are never requested or stored. Facebook, Instagram, Threads, TikTok, LinkedIn and YouTube tokens are stored only in encrypted form.

Why we need this data

• verify your identity and keep your workspace separate from others;
• connect the channels and professional social accounts you select;
• queue your video and publish it at the scheduled time;
• notify you of success, retries, errors or a connection that needs attention;
• protect the service from duplicates, failures and unauthorised access;
• manage your subscription and apply the limits shown before purchase;
• identify popular features and recurring errors from aggregated actions to improve the product.

Legal bases

We process data to provide the service you request and carry out your settings. Facebook, Instagram, Threads, TikTok, LinkedIn and YouTube connections require your explicit consent on the network’s official authorisation screen. Service security, error logs, minimal product analytics and duplicate prevention are based on our legitimate interest in reliable and secure operation. Payment data is processed to perform the contract.

Where data is processed

The app is hosted through ChatGPT Sites (OpenAI), with the main database and temporary videos on Cloudflare infrastructure. These hosting providers process information as needed to operate the service. Information is also sent to providers needed for your selected actions: Telegram for the bot and channel publishing; Meta/Facebook and Meta/Instagram for account connections and Reels; Meta/Threads for connecting your profile and publishing selected videos; TikTok for connecting accounts, checking available settings and publishing selected videos; Google/YouTube for identifying the selected channel and uploading videos; LinkedIn for connecting personal profiles and publishing selected videos; and Stripe for subscriptions and billing. These providers also process data under their own terms and may use infrastructure outside the EEA.

Crosspost Engine does not sell personal data or use it for advertising profiles.

The YouTube integration uses YouTube API Services. Google processes the data sent to it under its Google Privacy Policy. The youtube.readonly permission identifies the selected channel’s ID, title and handle. The youtube.upload permission uploads the video you select with your chosen title, description, visibility and audience setting. YouTube data is not used for advertising or AI training.

How long data is kept

• Settings, connections, queue and delivery history are kept for as long as the workspace exists or until the user requests deletion.
• Connected YouTube channel data and access are checked daily. The channel title and handle are refreshed from YouTube. If the data cannot be refreshed for 29 days, the connection and its API data are deleted. Uploaded video IDs, upload session URLs and YouTube error responses are removed from history after 29 days.
• A temporary copy of a video for external publishing is kept until the task is complete and a seven-day recovery period has passed, then deleted automatically.
• A single-use Facebook, Instagram, Threads, TikTok, LinkedIn or YouTube authorisation link is valid for 10 minutes and cannot be used afterwards.
• After deletion is complete, only an anonymous status associated with a random code remains so the user can check the outcome.
• Raw product analytics events are kept for up to 90 days, then deleted or retained only as aggregates without post content.
• Stripe and the data controller may retain payment records longer where required for tax and accounting obligations.

Your rights

You can request access, correction, portability, restriction of processing or deletion of your data, and object to processing where the law provides this right. Requests can be submitted electronically through the bot and are handled free of charge. You can also contact the relevant data protection authority.

How to delete your data

You can disconnect an individual Facebook Page, Instagram, TikTok or YouTube account, Threads profile, or LinkedIn personal profile in Connections in the Mini App. Identifiers and connection data are deleted immediately, and unfinished posts are stopped. The exception for tokens awaiting Google access revocation is described below.

When you disconnect YouTube, we immediately request revocation of Google access. If a temporary error occurs, an encrypted token is kept in a separate queue solely to retry revocation, until it succeeds or for a maximum of six days. The same revocation takes place when workspace deletion is completed. Google permission may cover several channels; those channels will need to be reconnected after revocation.

Open bot, send/delete_me and confirm the request separately. The system provides a code and a status page. Detailed instructions are on the data deletion page.

Deleting Crosspost Engine data does not delete posts already published on Facebook, Telegram, Instagram, Threads, TikTok, YouTube or LinkedIn. You manage those posts in the relevant social network.

You can also revoke SynAirgy’s permissions on the Google connections page. A confirmed revocation detected during the next daily check deletes saved channel data and stops its queue. To delete it immediately, disconnect the channel in Connections.

Cancelling a subscription stops future charges but does not request data deletion. To delete all workspace data, use the separate command /delete_me.