Privacy Policy

TeamPost (https://teampost.app) is a collaborative social publishing workspace. This policy explains what we collect when you use the product, including data from Meta (Facebook, Instagram, and Threads), LinkedIn, TikTok, and — when that integration ships — X.

Contact: privacy@teampost.app. Support: support@teampost.app.

1. Data we collect

Account data. Name, email, password hash, profile photo, workspace membership, and role.

Workspace content you create. Posts, captions, media you upload, comments, approvals, tags, assignees, and schedule times.

Connected platform data. When an admin connects a social account we store encrypted OAuth access and refresh tokens, token expiry, the platform account ID, display handle, follower count at connect time, and limited profile metadata needed to publish or show the connection.

• Meta (Facebook and Instagram). Facebook user ID of the person who authorized the app, Page ID and name, Instagram professional account ID and username, Page access tokens, and — if you use analytics — impressions, reach, engagement, likes, comments, shares, captions, and thumbnails for posts we publish and for a 90-day backfill of existing Page/IG media.
• Threads. Threads user ID, username, name, and profile picture URL, plus a long-lived token used only to publish content you compose.
• LinkedIn. Member ID (OpenID sub), display name, and profile picture. We request openid, profile, and w_member_social only. We do not collect your LinkedIn email.
• TikTok. Open ID, username, display name, avatar URL, follower count, and the publish settings you choose (privacy, comment/duet/stitch, commercial disclosure, and consent).
• X. Not connected today. If we add it, this policy will be updated before we request write access.

2. How we use it

We use this data to operate your workspace: authenticate you, let teammates plan and approve content, publish and schedule posts to accounts you connect, show Instagram and Facebook performance, send transactional email (invites, password reset, publish failures), and keep the service secure. We do not sell personal data. We do not use connected-platform data to advertise on those platforms.

3. Storage and security

OAuth tokens are encrypted at rest. Media is stored in private object storage and shared with platforms only as short-lived signed URLs at publish time. Analytics snapshots and backfilled Meta posts are stored so your team can see performance inside TeamPost.

4. Sharing

We send the content you compose to the platforms you connect, using their official APIs. Infrastructure processors (hosting, email, object storage, error reporting) may process data on our behalf. Teammates you invite can see workspace content according to their role.

5. How to delete your data

You can disconnect a social account at any time in Settings → Connected accounts. Disconnecting revokes the platform token where the platform supports it and clears stored tokens and profile metadata for that connection.

Workspace admins can delete a workspace, which removes its posts, media, members, and connected accounts.

To request deletion of your TeamPost account or remaining platform data, email privacy@teampost.app from the address on the account. We will confirm and complete deletion without undue delay.

Meta users. Step-by-step instructions are on /data-deletion. If you remove TeamPost from Facebook Settings → Apps and Websites and send a data deletion request, Meta calls our callback at /api/integrations/meta/data-deletion. We then delete Facebook/Instagram tokens, profile metadata, and analytics we stored from that authorization, and return a confirmation code. Check status at /data-deletion/<code>. The same process exists for Threads at /api/integrations/threads/data-deletion.

6. Cookies

We use essential cookies for sign-in and to complete OAuth (including a short-lived cookie while you choose a Facebook Page). We do not use advertising cookies.

7. Children

TeamPost is for business teams. It is not directed at children under 16, and we do not knowingly collect their data.

8. Changes

We will update this page when our practices change. The date at the top is the latest revision.