Skip to content

Legal

Social Data Disclosure

Last updated:

Provider-by-provider explanation of why Creators connect social accounts, what Postvertise receives, what appears publicly or to Brands, and how to disconnect or request deletion.

This document is provided for informational purposes and is subject to final legal review. It does not constitute legal advice.

1. How Postvertise Uses Connected Social-Account Data

RightBack.com LLC d/b/a Postvertise ("Postvertise") lets Creators connect supported social accounts so we can verify identity, sync permitted metrics through official platform APIs, and display marketplace-relevant profile information.

Supported providers today are Instagram, Facebook Pages, TikTok, and X.

YouTube is not a Postvertise integration. LinkedIn is not a Postvertise integration.

Postvertise is independent from social platforms and is not sponsored or endorsed by them unless we expressly say so in writing.

This page summarizes current production behavior. Full privacy detail is in the Privacy Policy. Deletion steps are on Data Deletion. Support contact is on Contact.

2. Shared Practices Across Providers

Why connect: enable Creator profile/marketplace display and Creator analytics based on authorized data.

What we do: store connection identity, encrypted OAuth tokens, and synced snapshots/metrics/content where the provider integration supports it.

What stays private: access/refresh tokens, credential rows, and non-public sync internals are not shown on public profiles.

Disconnect: Dashboard → Social Accounts. Disconnect deletes that connection’s stored tokens and synced social data.

Deletion requests: see Data Deletion. Authenticated users can also delete their Postvertise account from Dashboard → Settings, which disconnects social accounts and removes stored connection data.

Provider-side OAuth revocation: Postvertise removes credentials stored on its side; it does not currently revoke authorization with the social platform. Use each platform’s own settings if you want to revoke Postvertise’s access there.

Synchronization: after you connect an account, Postvertise may sync data automatically and when you trigger a manual sync. While an account remains connected, automatic synchronization may run on a periodic schedule (the application currently checks for due accounts about hourly and typically re-syncs an eligible connected account about every six hours after a successful sync). Exact timing is not guaranteed and can vary with queue load, retries, and configuration. Synchronization uses official platform APIs only—Postvertise does not scrape social websites.

Publishing: Postvertise does not publish posts to social networks in the current product.

Webhooks: Instagram webhook verification exists as a stub only; webhook-driven product features are not implemented.

Platform demographics: availability depends on the provider, account type, granted permissions, platform API eligibility, and whether the platform returns the requested metric. Where available through a connected Instagram account and Meta’s follower demographics Insights APIs, Postvertise may process aggregated audience geographic information, including country- or city-level audience segments, as well as age and gender aggregates. City-level segments appear in Creator analytics when returned and are not currently published on the public Creator profile. Facebook Page audience-country Insights are experimental and disabled by default in Postvertise; Facebook age/gender Page Insights are not available through the current integration. TikTok and X do not provide creator follower demographics through the currently authorized APIs. Postvertise does not scrape platforms, infer demographics from individual followers, or invent percentage values.

Metric availability is never guaranteed for every connected account even when a permission is requested.

3. Instagram

Why connect: link an Instagram Professional account for profile, content, Insights, and audience metric sync where Meta returns them.

Categories received (where returned): identity fields (such as id, username, name, profile picture), follower/audience counts, media metrics/captions/permalinks, account Insights, and—when Insights eligibility and scopes permit—aggregated follower demographic breakdowns (country, city, age, gender). Demographic availability is not guaranteed for every account.

Default Business Login path requests `instagram_business_basic` and `instagram_business_manage_insights`. A legacy Facebook Login for Instagram path may still exist for older connections with a different scope set; media Insights availability can differ on that path.

Use: Creator analytics, public aggregate metrics on Creator profiles/search, connection management.

Public profile: provider label, username/display, profile URL/image, follower and engagement aggregates when available. When Instagram Insights return audience age/gender/country aggregates, allowlisted top segments may appear on the public Creator profile as audience demographics—not as the Creator’s personal age/gender. City-level Instagram audience segments are used in Creator analytics when returned and are not currently part of the public profile allowlist.

Visible to Brands: same public aggregates via discovery/profile; not tokens or city-level audience breakdowns beyond what appears on the public profile.

Private: tokens and full private analytics payloads (including city-level audience segments when synced).

Disconnect/deletion: Section 2 and Data Deletion.

Independence: Not affiliated with Meta/Instagram.

4. Facebook

Why connect: link a Facebook Page you manage for Page profile, audience, post, and Insights metric sync where Meta returns them.

Production OAuth requests: `pages_show_list`, `pages_read_engagement`, `read_insights`, and `public_profile`. Postvertise does not request `pages_read_user_content` (visitor comments / UGC moderation).

Categories received (where returned): Page identity and engagement fields, recent posts and engagement summaries, and—when the stored Page token includes `read_insights` and the Page has ANALYZE access—post media-view Insights and other Page Insights the API returns. Not every Page receives every Insights metric.

Audience country: Meta’s `page_follows_country` Insights path is experimental in Postvertise and disabled by default (`FACEBOOK_AUDIENCE_COUNTRY_ENABLED`). Do not treat Facebook audience-country demographics as a generally available production capability. Facebook age/gender Page Insights have no official replacement in the current Graph integration and are not synced.

Use: Creator analytics and marketplace display of public aggregates when a Page is connected to a Creator profile.

Public / Brands: public aggregate fields when available; not tokens or Page selection session data.

No publishing to the Page via Postvertise.

Independence: Not affiliated with Meta/Facebook.

5. TikTok

Why connect: link TikTok identity and public stats for profile/marketplace display.

Categories received: user info permitted by `user.info.basic`, `user.info.profile`, and `user.info.stats` (profile and stats such as follower/following/likes/video counts). Creator follower demographics (country, age, gender) are not available through the currently authorized TikTok APIs and are not inferred.

Content: Postvertise does not ingest TikTok video items in the current sync implementation (`video.list` is not requested in production OAuth).

Public / Brands: aggregates when available.

Private: tokens.

No publishing.

Independence: Not affiliated with TikTok.

6. X

Why connect: link an X account for public metrics and a limited sample of recent posts for analytics/display.

Categories received: user profile and public metrics plus recent tweet text/metrics under scopes `tweet.read`, `users.read`, and `offline.access`. Follower demographics (country, age, gender) are not available through the currently authorized X APIs and are not inferred.

Use: Creator analytics and public aggregates—not posting tweets.

Public / Brands: aggregates when available.

Private: tokens; full ingested tweet sample in Creator analytics contexts.

Independence: Not affiliated with X Corp.

7. Contact

Questions: support@postvertise.com

Related: Privacy · Terms · Cookies · Data Deletion · Contact.