Privacy Policy

When you create an account or use our services, we may collect your name, email address, password, billing details, profile information, and any content (text, images, video) you choose to upload, draft, or schedule through the platform.

When you type a question into the Ask box on our website, we send it to Anthropic, our AI provider, to write the answer. Anthropic is listed on our subprocessors page. If you accept analytics cookies, we also record the question in Google Analytics, with email addresses and phone numbers removed, together with the page you asked it on and whether it was answered. This shows us which parts of our website are unclear. Google Analytics keeps this data for up to 14 months. Please do not include personal details in your question.

Some features process data about people who are not OmniSocials users: people who comment on, reply to, react to or message your connected accounts (shown in the social inbox and answered by automations you set up), and people or companies you tag in a post. We receive this data from the social platforms through your connected accounts, use it only to run these features for you, and delete it as described under Data Retention. For this data you decide what is processed and why, and we process it on your behalf under our Data Processing Agreement.

We collect technical data each time you use our service: IP address, browser type, operating system, device information, and usage data such as pages visited and time spent. This helps us secure, debug, and improve the platform.

We use Google Tag Manager to load our measurement and advertising tools. With your consent, we use Google Analytics to understand how visitors use our website, Dub to attribute affiliate referrals, and Meta's Pixel and Conversions API and Google Ads to measure advertising performance. This can include sharing a hashed (irreversibly scrambled) version of your email address, your IP address, and information about account signup, trial activation, or purchases, so these advertising partners can attribute them to the ad that brought you here. Analytics tools are only activated when you accept analytics cookies, advertising tools only when you accept marketing cookies, and you can withdraw consent at any time through your cookie preferences.

For connected Instagram, Facebook, Threads, TikTok, YouTube, Pinterest, Bluesky and Mastodon accounts, we also read the posts the account made outside OmniSocials, for example in the platform's own app or another tool. We store each post's caption or title, link, publish time, media type and statistics. For Instagram, Facebook, Threads and TikTok we also store a small copy of the picture or video cover in our EU storage, because the platform's own picture links expire. The first time we read an account, we go back up to 90 days. We update the statistics of each post for up to 90 days after it was published, and show them in Analytics and on the calendar to the people who have access to that workspace. When you disconnect the account, we delete these posts and pictures within 30 days (YouTube: 7 days).

Through Meta's Graph API we access your Facebook profile (name and email), the Facebook Pages and Instagram professional accounts you choose to connect, their posts, comments and messages (Messenger and Instagram Direct, for the social inbox and automations), Page and account insights, and post analytics. When you connect through Facebook, the permissions are email, public_profile, pages_show_list, pages_read_engagement, read_insights, pages_manage_posts, pages_manage_metadata, pages_messaging, pages_manage_engagement, publish_video, business_management, instagram_basic, instagram_manage_comments, instagram_manage_insights, instagram_content_publish, instagram_manage_messages. When you connect Instagram directly, they are instagram_business_basic, instagram_business_content_publish, instagram_business_manage_messages, instagram_business_manage_comments, instagram_business_manage_insights. We comply with Meta's Platform Terms, Developer Policies, and Community Standards. See Meta's Privacy Policy.

When you set up a comment-to-DM automation, we receive the comments and messages people send to your Page or Instagram account, check them for the keywords you chose, and send the reply you wrote as a private message, at most once per person. We store the person's platform ID, username or name, the comment or message that matched, and what we sent, so that nobody gets a second reply and you can see the automation's activity.

Through Meta's Threads API we access your Threads profile, posts, engagement metrics (views, likes, replies, reposts, quotes), and publishing capabilities. Our use complies with Meta's Threads API requirements and Platform Terms.

Through LinkedIn's Developer APIs we access your profile (name, headline, email, profile picture), the company pages you administer, posts you publish through OmniSocials, and basic engagement metrics where available. When you tag a company or person in a post, we look up the names you type, and we keep these search results for up to 6 hours. Our integration complies with LinkedIn's User Agreement and Developer API Terms. See LinkedIn's Privacy Policy.

OmniSocials uses YouTube API Services. We access your channel information, video upload capabilities, channel analytics, and video performance data, including the titles, covers and statistics of videos you uploaded outside OmniSocials. We do not sell or transfer Google user data to third parties, do not use it for advertising, and do not use it to train AI or ML models. You can revoke access at any time through Google security settings. When you disconnect YouTube in OmniSocials, we delete your YouTube data within 7 days; when you revoke access in Google's security settings, we delete it within 30 days. Use of our YouTube integration is also subject to the YouTube Terms of Service and the Google Privacy Policy.

Through TikTok's Developer APIs we access your profile, account statistics, video content, engagement metrics, and publishing capabilities. Our integration complies with TikTok's Developer Terms and Content Sharing Guidelines. See TikTok's Privacy Policy.

Through X's API v2 we access your profile, account statistics, and post engagement metrics for content published via OmniSocials. Requested scopes are tweet.read, tweet.write, users.read, media.write, and offline.access.

Through Pinterest's Developer APIs we access your profile, the boards you manage, and your Pins, along with related analytics. To let you tag products in a Pin, we read your product Pins and, if you choose to connect your catalog, your product catalog. Our integration complies with Pinterest's Developer Guidelines and Terms of Service.

For decentralized platforms, we connect via AT Protocol (Bluesky) or your chosen instance's API (Mastodon). We access your profile, your posts, and engagement metrics where available. Note that decentralized platforms may have additional instance-specific rules that apply to your usage.

Through Google's Business Profile APIs we access your business profile information, posts you publish through OmniSocials, and account-level performance metrics (impressions, direction requests, calls, website clicks). As with all Google user data, we do not sell it, share it with advertisers, or use it to train AI models.

We connect to Telegram through the OmniSocials bot and the Telegram Bot API. When you connect a channel or group, we receive your Telegram user ID to check that you are an admin of that chat, and the chat's ID, type, title, username, photo and subscriber or member count. We store the messages we send for you and their reactions and poll votes. The bot does not read the other messages in your chat. Our use is subject to the Telegram Bot Platform Developer Terms of Service.

We post to Discord through a webhook in the channel you choose. When you connect with Discord, Discord makes that webhook and adds our bot to the server, with no permissions. The bot reads only the name and type of the channel you picked and the server's name, icon and member count, when you connect and once a day after that. It never posts, never reads messages and never sees who is in your server, and we do not store your Discord login token. (When our bot is switched off, Discord shows us your server list once instead, and we use it only to find the name and icon of the server you picked.) When you paste a webhook URL instead, we read only that webhook's name and picture, and you can tell us the channel name yourself. We store the server name, icon and member count, the channel ID, name and type, the webhook's name and picture, the webhook link (encrypted), and the messages we send for you with their reactions and poll results. We do not read the other messages in your server. When you disconnect Discord, we delete the webhook link and the connection details at once; the webhook stays in your server until you remove it in Discord, and our bot leaves the server within two days once no OmniSocials workspace posts there. Our use is subject to the Discord Developer Terms of Service and the Discord Developer Policy. See Discord's Privacy Policy.