Frequently Asked Questions

Only through the official APIs that each social platform provides. We never ask for the password of your social accounts.

None of our social automations, on their own, lead to a suspension or a ban. A platform can only act on your account because of what gets published: if an automation is used to post content that breaks the platform's terms of use, the platform may restrict the account, exactly as it would for a post published by hand.

Yes. Every token we use to connect to your social accounts is stored encrypted, never in plain text.

Security is part of how we build every product, from the first line of code. Each release goes through automated tests, and security scanners monitor our software around the clock: they alert us automatically as soon as a known vulnerability affects anything we use, so we can fix it straight away.

Not yet. Obtaining a security certification is planned for the near future, and we will update this page as soon as we have it.

We act straight away. First we revoke the access tokens, so nobody can use the connection to your social accounts. Then we secure the affected servers and temporarily put the services into maintenance until the issue is fully fixed. We also inform every user by email, as required by the European GDPR and the Californian CCPA.

We don't use any cloud provider at the moment: your data is stored on our own servers, hosted by OVH. A migration of our infrastructure is planned for the future, and we will update this answer when it happens. You can read how we handle your data in our Privacy Policy.

Yes, at any time. To disconnect a social account, open the Content Publisher in IntraOS, go to the list of your connected social accounts and unlink it. To delete all your data, simply delete your IntraOS account. Some data may be kept for up to 7 years, only where United States federal law requires it. All the details are in our Privacy Policy.