PostFling

Privacy Policy

Effective 14 November 2026

This policy describes the PostFling web service (the workspace at /app) and this website. PostFling is a multi-brand video workspace: you plan posts, connect social channels, and deliver videos to the platforms you choose.

Who we are

PostFling is operated by the service owner. For privacy questions or data requests, contact [email protected].

What the service stores

To run your workspace, the service stores the following. All of it lives on the service's own server and database; there is no third-party hosting of workspace content.

• Account — your email address, a salted password hash if you use a password, and your Google account identifier if you use Google sign-in.
• Sessions — a random session token, stored only as a hash, tied to one workspace, kept in an HttpOnly cookie in your browser. The workspace uses a short-lived cookie to complete Google sign-in securely.
• MCP connections — the selected workspace, permissions, client identifier, and expiry. OAuth access and refresh tokens and workspace MCP keys are stored as hashes.
• Workspace content — your drafts, ideas, captions, planned dates, and planner state.
• Channel records — the social channels you list, and, when you connect one, the provider's access and refresh tokens. Tokens are encrypted at rest with a key held separately from the database and backups.
• Media — the MP4 files you upload, stored in a private server directory (owner-only permissions) and served only to the workspace that uploaded them.
• Deliveries and receipts — what you queued, what the provider answered, and platform error text, so you can see what was sent.
• Team data — member emails and single-use invitation codes (stored hashed). Codes expire after seven days.

What we do not do

The service has no usage analytics, advertising, tracking pixels, or ad identifiers. We do not sell your data. Request logs omit query strings to keep authorization codes out of those logs.

What leaves the service, and where

PostFling contacts the provider you choose when you sign in, connect a channel, or deliver a post.

• Google sign-in — Google returns your account identifier and verified email address for PostFling authentication. PostFling keeps those account details and discards Google's tokens after sign-in. See Google’s privacy policy.
• Meta (Facebook, Instagram, and Threads) — sign-in and the social accounts you select. When you deliver, PostFling sends the video and caption to Facebook or Instagram. For Threads, PostFling provides the video through a time-limited signed media URL for Threads to retrieve, along with the caption. Meta's policy: facebook.com/privacy/policy.
• TikTok — sign-in, your user information, and, when you deliver, the video and caption sent to your TikTok inbox as a draft. You finish posting in TikTok. TikTok's policy: tiktok.com/legal/privacy-policy.
• X — sign-in and profile identification. When you deliver, PostFling sends the video, caption, and selected profile destination using the write authorization you grant.
• Bluesky — the app password you provide to link the account, and, when you deliver, the video and caption for the selected profile.
• LinkedIn — sign-in and the member profile or eligible Page you select. When you deliver, PostFling sends the video and caption to that destination.
• Pinterest — sign-in and the board you select. When you deliver, PostFling sends the video and Pin details to create a Pin on that board.
• Snapchat — sign-in and profile information. When you deliver, PostFling sends the video and Spotlight details to Snapchat for the authorized profile.
• Mastodon — the server hostname you choose and the account information returned by that server during authorization. When you deliver, PostFling sends the video and caption to that server to create a status.

Each platform processes your data under its own terms and privacy policy. A delivery confirmed by PostFling is not a guarantee that the platform published the content.

Connected assistants and MCP clients

When you authorize an MCP client, PostFling returns the workspace data requested by that client within the connection's permissions. This may include drafts, media, channel details, delivery receipts and, when you grant workspace management, team details. The client processes the data it receives under its own terms and privacy policy. Use Team & access to disconnect OAuth clients or revoke workspace keys. This ends future access through that connection. You can cancel pending deliveries separately in PostFling.

Connected accounts on your phone

If you use the PostFling Android app with your workspace, your password is entered at sign-in only and the session is held in the app's memory, never written to storage. Developer keys and platform tokens used for direct phone publishing stay encrypted on the device with the Android Keystore and are not sent to this service.

This website

PostFling’s public pages and workspace load typefaces from Google Fonts. Your browser connects to Google to load them, which shares your IP address with Google as part of that request. PostFling serves the workspace application files and private workspace media.

Retention and deletion

Your data is kept while your account is open. You can delete your account at any time from the app: open Team & access, choose Delete account, and confirm with the sign-in method shown, or follow the steps on the account deletion page. Deletion removes your account and every workspace you own, including its channels, saved grants, media files, scheduled deliveries, and receipts, immediately. Workspaces where you are a member but not the owner stay with their owners. You can also remove individual media, disconnect a channel, or sign out sessions from the app. Keep your own backups; the service does not make user-facing copies.

Security

Passwords use PBKDF2 hashing; session tokens are stored hashed and rotate when you switch workspaces or change your password; provider tokens are encrypted before storage; media files are written with owner-only permissions; and production deployments run behind HTTPS. No security measure is perfect, so protect your password and tell us right away if you suspect unauthorized access.

Changes

We may update this policy as the service changes. The effective date above identifies this version, and material changes will be announced in the app.