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 social accounts so we can verify identity, sync permitted metrics, and display marketplace-relevant profile information.

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.

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.

Sync: after connect and when you run manual sync—not continuous scheduled monitoring.

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: Instagram and Facebook may sync aggregated audience location, age, and gender breakdowns when the official platform Insights APIs return them for an eligible connected account. TikTok and X do not provide creator follower demographics through the currently authorized APIs, so those dimensions stay unavailable. Postvertise does not scrape platforms, infer demographics from individual followers, or invent percentage values.

3. Instagram

Why connect: link an Instagram Professional account for profile and content metric sync.

Categories received: identity fields (such as id, username, name, profile picture), audience counts, media metrics/captions/permalinks, and—when Insights eligibility and scopes permit—aggregated follower demographic breakdowns (country, age, gender) under scopes `instagram_business_basic` and `instagram_business_manage_insights` (default Business Login 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.

Visible to Brands: same public aggregates via discovery/profile; not tokens.

Private: tokens and full private analytics payloads.

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 metric sync.

Categories received: Page identity and engagement fields plus recent posts metrics under scopes `pages_show_list`, `pages_read_engagement`, `pages_read_user_content`, and `public_profile`. Aggregated Page audience demographics (country, age, gender) are ingested only when Meta Page Insights return them for the connected Page; Meta also documents `read_insights` for Insights access, which is not yet part of Postvertise’s production OAuth request set.

Use: same as other sync-capable providers—analytics and marketplace display.

Public / Brands: public aggregate fields when the Page is connected to a Creator profile.

Private: tokens; 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.

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.