Privacy Policy

ConnectHub is a social media management platform. You connect the social accounts you already own, compose a post once, and publish or schedule it to those accounts. This policy explains what we collect, why, how long we keep it, and how you remove it.

We collect only what the product needs in order to work. We do not sell your data, and we do not use the content of your posts or your connected accounts for advertising or for training machine-learning models.

When you create a ConnectHub account we store:

• your name and email address;
• a one-way hash of your ConnectHub password — never the password itself, and hashes cannot be reversed;
• optional profile details you choose to provide during onboarding, such as company name, industry, role, timezone and language;
• account status and the dates your account was created and last updated.

Your timezone is used to schedule posts at the time you actually intend, and your language preference for display.

Every piece of business data in ConnectHub — connected accounts, posts, scheduled jobs, uploaded media and usage counts — belongs to exactly one workspace. Access is granted through workspace membership.

Separation between workspaces is enforced on the server and in the database, not only in the interface. Requests are resolved from your server-side session rather than from identifiers supplied by your browser, and records are always queried within the workspace you belong to. One customer cannot read, publish through, modify or delete another customer's data.

When you connect a social account, we store what is needed to publish on your behalf and to show you which account is connected:

• the platform and the account or page identifier issued by that platform;
• the display name, username and profile image, so you can tell accounts apart;
• the permissions the platform granted us;
• connection status and the date you connected it;
• an encrypted access token (see below).

We request the narrowest set of permissions each feature requires. For Facebook and Instagram this means permission to list the Pages you manage, read the Page details needed to identify a linked Instagram account, and publish the posts you create.

ConnectHub never asks for, receives, or stores your Facebook, Instagram, LinkedIn, or any other social media password.

Connecting an account always happens through that platform's own official authorization flow. You are sent to the platform's website, you sign in there, and you approve the specific permissions you are granting. Your credentials are entered only on the platform's own page and are never transmitted to ConnectHub.

The same applies to two-factor codes and one-time passcodes: those are handled entirely by the platform. ConnectHub has no way to see them, and there is no screen anywhere in the product that asks for them.

What we receive at the end of that flow is an access token — a revocable credential that authorizes the specific actions you approved, and nothing more.

Access tokens are the most sensitive data we hold, and they are treated accordingly:

• They are encrypted before being written to the database using AES-256-GCM, an authenticated encryption algorithm.
• They are decrypted only on our servers, in memory, at the moment a publish request is made — and discarded immediately afterwards.
• They are never sent to your browser, never included in an API response, never written to logs or error messages, and never visible in the administrator interface.
• Tokens are stored per workspace. A token belonging to one customer can never be used to publish to another customer's account.

When a token expires or you revoke it on the platform, we mark the connection as needing attention and stop attempting to publish through it.

Images and videos you upload are stored so they can be published to the accounts you select. We record the file name, type, size, dimensions and a content hash.

Uploaded files are validated on our servers by inspecting the file contents, not by trusting what your browser reports, so unsupported or disguised file types are rejected.

Because platforms such as Meta download media directly from a link rather than accepting an upload from us, each file is served from an address containing a long, randomly generated token. That address is not guessable and is not derived from your account, but anyone you share the link with can view that one file. Deleting the media revokes the link.

We store the content you compose — text, hashtags, links and attached media — along with the accounts you select and, for scheduled posts, the time and timezone you chose. Scheduled times are stored in UTC and displayed in your timezone.

Publishing runs on our servers, so a scheduled post is sent at the time you chose whether or not your browser is open. For each selected account we keep a record of the attempt: its status, the identifier and link of the resulting post on that platform, and any error the platform returned. This is what lets you see exactly which platforms succeeded and retry only those that failed.

The analytics shown in ConnectHub are derived from our own publishing records — how many posts you published, how many failed, and how many are scheduled. They are counted from your own activity within your workspace.

We do not currently read reach, impressions, likes or comments from the social platforms, and we do not display estimated figures in their place.

ConnectHub uses cookies strictly to keep you signed in. The session cookie holds a signed token identifying your session; administrators have a separate one. Both are marked HttpOnly, so they cannot be read by scripts in your browser, and are transmitted securely in production.

We do not use advertising cookies, third-party tracking pixels, or cross-site behavioural tracking. Clearing these cookies signs you out.

To publish on your behalf, ConnectHub sends your post content and media to the platforms you select — for example Meta for Facebook and Instagram. That data is then governed by each platform's own privacy policy and terms.

We share your data with a platform only when you have connected an account for it and selected it for a specific post. We do not share your data with advertisers or data brokers, and we do not sell it.

Your ConnectHub data is stored in a managed MongoDB database. Service providers who process data on our behalf do so only to operate the service.

Measures implemented in the product include:

• AES-256-GCM encryption of access tokens at rest;
• one-way hashing of ConnectHub passwords;
• server-side authorization on every request that returns or changes data;
• authorization flows protected against cross-site request forgery, with each request bound to the user, workspace and platform that started it;
• administrator permissions checked against the database on every request;
• logging that deliberately excludes tokens, passwords and secrets.

No system can be guaranteed completely secure, but we aim to limit both what is collected and what any single failure could expose.

Account and workspace data is kept while your account is active. Posts and their publishing records are kept so you retain a history of what was published and when. Access tokens are kept until you disconnect the account, the token is revoked, or your account is deleted.

Disconnecting a social account stops ConnectHub publishing to it and cancels any queued posts for it. Posts already published to that platform remain on the platform — removing them there is done from the platform itself.

You can remove your data at any time:

• Disconnect a social account from the Connected Accounts page. This stops all future publishing to it.
• Revoke access on the platform. For Facebook and Instagram this is Settings → Business Integrations on Facebook. When Meta notifies us that you have removed ConnectHub, we delete the stored connections and tokens associated with that authorization automatically.
• Delete your ConnectHub account by contacting us. This removes your account, workspaces, connected accounts, tokens, uploaded media and posts.

Depending on where you live, you may have the right to access the personal data we hold about you, to correct it, to have it deleted, to receive a copy in a portable format, to restrict or object to certain processing, and to withdraw consent. Withdrawing consent for a connected account is done by disconnecting it.

To exercise any of these rights, contact us using the details below. We will respond within the period required by applicable law.

ConnectHub is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.

We may update this policy as the product changes. The date at the top reflects the most recent revision. Material changes affecting how your data is used will be communicated before they take effect.

For any privacy question, or to exercise the rights described above, contact the ConnectHub administrator for your organization, or the operator of this ConnectHub deployment.

Operator note: replace this section with your legal entity name, postal address and a monitored privacy contact address before publishing this policy or submitting it for platform app review. This document describes ConnectHub's technical data handling accurately, but it is not legal advice and should be reviewed by a qualified adviser for your jurisdiction.