1. Overview & Scope
PostSocials (“PostSocials,” “we,” “our,” or “us”) operates a unified social media publishing platform and developer REST API located at https://www.postsocials.dev (collectively, the “Service”). This Privacy Policy applies to all workspace owners, team members, API developers, website visitors, and end-users who link social accounts through our hosted Connect pages.
By creating an account, connecting a third-party social network, or calling the PostSocials API, you acknowledge the data practices described in this policy. Capitalized terms not defined here have the meanings given in our Terms of Service.
2. Information We Collect
2.1 Account & Authentication Information
- Identity details: Email address, display name, profile avatar URL (when signing in with Google OAuth), and unique Firebase Authentication UID.
- Team membership details: Email addresses and workspace roles (
owner,editor,viewer) of invited collaborators.
2.2 Billing & Subscription Information
- Payments and subscriptions are processed by Stripe. PostSocials never receives, processes, or stores full payment card numbers, CVV codes, or bank credentials.
- We store only billing metadata required to enforce your plan entitlements: Stripe Customer ID, Stripe Subscription ID, plan tier, billing interval, subscription status, billing period timestamps, and Stripe webhook event IDs (for idempotency).
2.3 Connected Social Account & OAuth Data
- When you connect a social media account (such as YouTube, Instagram, TikTok, X, LinkedIn, Facebook, Threads, Pinterest, Reddit, Bluesky, Google Business Profile, Mastodon, Discord, or Telegram) to a Profile, we receive and store the platform's external account identifier, handle/username, display name, avatar URL, granted OAuth scopes, token expiration timestamp, and OAuth access/refresh tokens.
- All OAuth access and refresh tokens are encrypted at rest using AES-256-GCM before storage and are inaccessible to client-side browser SDKs.
2.4 Uploaded Media, Post Metadata & Analytics
- Media files (videos, photos, carousels) uploaded directly to Firebase Storage via V4 signed URLs, together with post titles, captions, target platform selections, per-platform settings, scheduling timestamps, and external post URLs/IDs returned by social networks.
- Aggregated post performance snapshots (views, likes, comments, shares, clicks) retrieved for posts published through PostSocials.
2.5 Developer Credentials, Webhooks & Operational Logs
- API key names, non-sensitive prefixes (
ps_live_...), SHA-256 hashes (we never store plaintext API keys after creation), assigned scopes, and last-used timestamps. - Webhook destination URLs, AES-256-GCM encrypted HMAC-SHA256 signing secrets, subscribed events, and delivery logs (HTTP status codes, latency, and truncated response snippets).
- Standard server telemetry and security logs (IP addresses, request timestamps, user-agent headers, rate-limit counters, and administrator audit trails).
3. How We Use Information
We process collected data strictly to:
- Authenticate your workspace, enforce server-side monthly upload quotas, profile limits, and API rate limits.
- Refresh OAuth credentials and publish, schedule, or manage posts on the specific social networks you explicitly select.
- Deliver signed webhook notifications and display cross-platform post analytics inside your dashboard or API responses.
- Process subscriptions, invoices, plan upgrades, and cancellations through Stripe.
- Detect abuse, prevent unauthorized access, enforce our Terms of Service, and comply with legal obligations.
Strict Prohibitions: PostSocials does not sell your personal information, does not rent or share connected social account data with data brokers or advertisers, and does not use your uploaded media, captions, or third-party API data to train generalized artificial intelligence or machine learning models.
4. Third-Party Social Platform APIs & Mandatory Disclosures
4.1 Google & YouTube API Services (Limited Use Disclosure)
PostSocials integrates with YouTube Data API v3 and Google Business Profile APIs via Google OAuth 2.0. PostSocials's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We request only the minimum Google/YouTube scopes needed to identify your channel, upload videos/Shorts you explicitly submit, and read basic channel/post metadata.
- By connecting a YouTube channel, you also acknowledge the Google Privacy Policy and YouTube Terms of Service.
- In addition to disconnecting your channel inside PostSocials, you may revoke PostSocials's access to your Google account at any time via Google Security Settings.
4.2 Meta Platforms (Instagram, Facebook, Threads)
When you authorize Instagram, Facebook Pages, or Threads via Meta OAuth, we access only the Page/Profile identifiers, publishing permissions, and engagement insights needed to publish and report on your scheduled content. You may revoke access at any time from Dashboard → Profiles or in your Facebook/Instagram Business Integrations settings. See Section 8.2 (Data Deletion Instructions) for complete deletion procedures.
4.3 TikTok & Other Supported Networks
For TikTok (Content Posting API), X (Twitter API v2), LinkedIn, Pinterest, Reddit, Bluesky (AT Protocol), Mastodon, Discord, and Telegram, PostSocials accesses only the permissions you grant during OAuth authorization solely to publish content you initiate and fetch post-level analytics. Your relationship with each social platform is independently governed by that platform's own privacy policy and terms.
5. Whitelabel Hosted Connect Portal
Customers on Professional, Advanced, and Business plans may generate single-use Connect URLs (/connect/[token]) branded with their own name, logo, and accent color so their end-users can link social accounts into a customer-owned Profile.
- For end-user data linked via a Whitelabel Connect Portal, our SaaS customer acts as the Data Controller and PostSocials acts as a Data Processor / Service Provider processing tokens and publishing requests strictly under the customer's instructions.
- End-users may revoke access directly through their social network's connected-apps settings at any time or request disconnection through the application that provided the Connect link.
6. Security & Encryption
We implement administrative, technical, and cryptographic safeguards designed to protect your data:
- Encryption at rest: All OAuth access tokens, refresh tokens, and outbound webhook signing secrets are encrypted with authenticated AES-256-GCM prior to Firestore persistence.
- Encryption in transit: All traffic between your browser, API clients, Firebase Storage signed uploads, social platform APIs, and webhooks is encrypted via HTTPS/TLS.
- One-way API key hashing: Developer keys (
ps_live_...) are stored exclusively as SHA-256 digests; plaintext keys are revealed once at generation. - Server-side access isolation: Sensitive Firestore collections (OAuth connections, API key hashes, webhook secrets, connect sessions, Stripe event logs, and admin audit logs) are strictly blocked from client SDK access via Firestore Security Rules and accessed only through authenticated server routes.
7. Sub-Processors & Data Sharing
We share data only with vetted infrastructure sub-processors required to operate the Service, or when required by law:
| Sub-Processor | Purpose | Location |
|---|---|---|
| Google Cloud / Firebase | Authentication, Cloud Firestore database, Cloud Storage media uploads | United States / Global |
| Vercel Inc. | Application hosting, serverless API execution, scheduled cron dispatch | United States / Global Edge |
| Stripe, Inc. | Subscription checkout, invoicing, billing portal, payment processing | United States / Global |
| Connected Social Platforms | Receiving posts, media, and captions you explicitly publish to selected networks | Per platform |
We may also disclose information if required by subpoena, court order, or applicable law, or in connection with a merger, acquisition, or asset transfer (with advance notice to affected users).
8. Data Retention & Deletion
8.1 Retention Periods
- OAuth tokens: Retained only while a social account remains connected to a Profile. Disconnecting an account immediately deletes the encrypted token record from Firestore.
- Account, profile, upload & analytics records: Retained while your account is active so you can manage schedules, inspect delivery results, and review analytics.
- Billing & tax records: Retained by Stripe and in our transaction logs as required by tax, accounting, and anti-fraud laws (typically up to 7 years).
8.2 Data Deletion Instructions (Self-Service & Email)
You can delete your data at any time using any of the following methods:
- Disconnect a single social network: Open Dashboard → Profiles and click the disconnect icon next to any connected network. Its encrypted OAuth tokens are deleted immediately.
- Delete a Profile: Open Dashboard → Profiles and click Delete on a Profile to remove the Profile and all connected account tokens under it.
- Complete account & data deletion: Email privacy@postsocials.dev from your registered account email with the subject line
Account Deletion Request. We verify ownership and permanently erase your Firebase Auth account, Firestore documents, OAuth tokens, API keys, webhooks, and uploaded Storage files within 30 days (typically within 5 business days), except minimal billing records required by law.
Note: Deleting data inside PostSocials does not delete posts that have already been published on external social media platforms; those must be deleted directly on each social network.
10. International Data Transfers
Our infrastructure operates primarily in the United States and across global edge locations. If you access the Service from the European Economic Area (EEA), the United Kingdom, or Switzerland, your information is transferred to and processed in jurisdictions with different data protection laws under appropriate safeguards, including the European Commission's Standard Contractual Clauses (SCCs) maintained by our sub-processors (Google Cloud, Vercel, and Stripe).
11. Your Privacy Rights (GDPR, UK GDPR & CCPA/CPRA)
11.1 EEA, UK & Swiss Residents (GDPR / UK GDPR)
Our legal bases for processing personal data are performance of a contract (providing the Service you requested), legitimate interests (security, fraud prevention, service reliability), legal obligation (billing/tax compliance), and consent (connecting optional third-party OAuth accounts). You have the right to:
- Access a copy of the personal data we hold about you.
- Rectify inaccurate or incomplete personal data.
- Request erasure (“right to be forgotten”).
- Restrict or object to certain processing activities.
- Receive your data in a structured, machine-readable format.
- Withdraw OAuth consent at any time and lodge a complaint with your local supervisory data protection authority.
11.2 California Residents (CCPA / CPRA)
California residents have the right to know what categories of personal information we collect and disclose, request deletion or correction of personal information, and exercise these rights without discrimination. PostSocials does not “sell” or “share” personal information for cross-context behavioral advertising as defined under the CCPA/CPRA.
To exercise any privacy right, email privacy@postsocials.dev. We will respond within 30 days (or 45 days where permitted under CCPA).
12. Children's Privacy, Policy Updates & Contact
Children's Privacy: The Service is a business and developer platform and is not directed to individuals under the age of 13 (or under 16 in the EEA/UK). We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, contact us immediately for deletion.
Changes to This Policy: We may update this Privacy Policy periodically to reflect changes in our platform, integrations, or legal requirements. When we make material changes, we will update the “Last Updated” date above and, where appropriate, notify workspace owners by email or in-app banner.
Contact Us: For privacy questions, data subject requests, or security inquiries, contact privacy@postsocials.dev or general support at support@postsocials.dev.