Guidelines & Compliance
Last updated: June 2026
This page describes the concrete technical measures SocialsGenie takes to respect each connected platform's developer policies and posting guidelines, and how we safeguard your accounts and data. It documents how our integration is built to comply — it is not a claim of certification, partnership, or endorsement by any platform.
1. Cross-platform commitments
These apply to every network we publish to:
- Official APIs only. We publish exclusively through each platform's official API. We do not scrape, automate the web UI, or use unofficial endpoints.
- You are always in control. We publish only on your explicit action or on a schedule you set. We never post autonomously.
- Least-privilege access. We request the minimum OAuth scopes required to publish and read basic account info on your behalf.
- Encrypted credentials. Your OAuth tokens are encrypted at rest and never exposed to the browser or third parties.
- Revocable any time. You can disconnect any account or delete your data from Settings, and we honor platforms' deauthorize and data-deletion callbacks.
- Rate-limit aware. We respect each platform's published rate limits and media requirements rather than retrying blindly.
2. Meta — Facebook & Instagram
We operate within Meta's Platform Terms and Developer Policies:
- We use the official Meta Graph API (v23) and keep the version current as Meta deprecates older ones.
- We publish only to Facebook Pages and Instagram Business/Creator accounts you connect and authorize, using the Page-token model.
- Instagram media validation: before publishing we validate media against Meta's published specs (supported formats, file size, and aspect ratio) so we never push non-conforming content.
- Publishing rate limit: we check the account's content-publishing usage and respect Instagram's limit of 100 API-published posts per rolling 24 hours.
- We request only the permissions needed to publish and read engagement (e.g.
pages_manage_posts, instagram_content_publish). - We implement Meta's Deauthorize and Data Deletion callbacks: removing the app or requesting deletion purges the associated stored data.
3. TikTok
We follow TikTok's Content Sharing Guidelines and use the official Content Posting API:
- You choose each post's privacy level before publishing, from the options TikTok reports as available for your account.
- Commercial-content disclosure: when you mark a post as commercial content, we require the appropriate disclosure (your own brand and/or branded content), matching TikTok's requirements.
- We enforce TikTok's disallowed combinations — for example, branded content cannot be posted as private.
- We surface creator information from TikTok (such as who can view a post and duration limits) and respect those constraints.
- We publish only after your explicit confirmation in the composer.
4. Other platforms
The same cross-platform commitments above apply to every other network we support. For each, we use the official API, request minimal scopes, respect rate limits and media rules, attribute content correctly, and publish only on your action:
- X (Twitter) — official v2 API; automatic token refresh; media uploaded via the official endpoints.
- LinkedIn — posts to the member or organization you authorize, via the official Share/Posts API.
- Pinterest — pins created via the official API to boards you select.
- YouTube — uploads via the official Data API to the channel you authorize.
- Bluesky — posts via the AT Protocol using your authenticated session.
- Mastodon — posts to your instance via the official API using a token scoped to your account.