Privacy policy

1. Who we are

NioConnect is a service of Capgimini Infotech. We provide the service described below and are the data controller for the information on this page, except where we act as your processor (see section 10). For any privacy question, request or complaint, write to info@nioconnect.com.

2. What NioConnect does

NioConnect connects the social accounts you already have, lets you compose a post once and adapt it for each platform, and publishes it for you. You can put a post on a calendar for a future time, or send it immediately.

Publishing is unattended, and that is the point of the product. A scheduled post goes out at the time you chose whether or not you are signed in, whether or not your computer is on, so the service holds the access it needs to act on your behalf while you are away, and tells you loudly if a post fails rather than letting it disappear. That is the whole reason it stores the credentials described below.

It is a business tool, for people and teams who publish to more than one platform. It is not a social network, it has no feed, and it shows you no content but your own.

3. Information you give us directly

• Your email address and a password. The password is never stored: we keep only an Argon2id hash of it, which cannot be turned back into your password.
• Your workspace and its members. The name you give your organization, the people you invite, and the role each of them holds.
• The content you compose. Post text, the media you upload, the schedule you set, and the channels you chose to send it to.
• Sign-in sessions. A random token in a cookie, stored as a hash so that we can end a session on request. It can be revoked, and signing out revokes it.
• Billing details, if you subscribe to a paid plan. Your plan, subscription status, invoice history and billing email. Card numbers never reach our servers. They are collected by our payment provider, and we receive only a token, the card brand, its last four digits and its expiry.
• What you send us. Messages to support, bug reports and feedback, and your notification preferences.

4. Information we receive from a connected platform

When you connect a social account, we ask that platform only for the access described in the next section, and we store only the following about the connected account:

• The account’s identifier: the platform’s own stable id for the account that authorized. We key on this rather than on your handle, because handles change.
• Its display name, handle and profile picture, so you can tell your connected accounts apart in the app.
• The destination you chose: which Page, board, channel, subreddit, server or chat you selected, on the platforms where you select one.
• Your server address, for Mastodon, where your account lives on an instance you name rather than a single central host.
• The access token itself (and a refresh token where the platform issues one), which is what lets us publish on your behalf. See how credentials are stored.
• The published post’s id and link, read back from the platform after publishing so that we only ever report a post as published when the platform has confirmed it.

When you connect a platform, NioConnect uses the permissions you authorize on that platform’s own consent screen (the screen that lists them at the moment you grant them) to identify the account you connected, list the destinations you can publish to (Pages, boards, channels, servers), publish the content you composed and scheduled, upload the media it needs, read the published post back to confirm it exists, and keep the connection alive by renewing its access. Nothing more.

Connected platforms may include Facebook, Instagram, Threads, YouTube, LinkedIn, TikTok, Pinterest, X, Bluesky, Mastodon, Twitch, Nostr, Discord, Reddit, Slack and Telegram. We send content and its related metadata to a connected platform only to carry out the action you asked for. Once it arrives, that platform processes it under its own privacy policy and developer terms, not this one.

We request no permission that would let us read your inbox or your direct messages, run advertising, or act on your account beyond the publishing you asked for. On platforms that offer separate permissions for content you have marked private or secret, we do not request them, because the product has no feature that would use them.

Some publishing permissions are broader than the use we make of them. On Meta’s platforms, the permission that lets us confirm you administer a Page, and read a post back after publishing it, also carries access to that Page’s metadata and follower information; connecting a business account can require access to the business assets your account administers. On YouTube and LinkedIn the equivalent read permissions let us confirm the destination you chose and read the published post back. We do not build audience analytics, we do not store follower, reach or engagement figures, and no screen in the product displays them.

You can see exactly what you granted, and withdraw it, in the connected-app settings of the platform itself. Doing so takes effect immediately and does not depend on us.

5. Google user data (YouTube)

If you connect a YouTube channel, NioConnect uses YouTube API Services. Through them we access only:

• Your channel name and id, to identify the channel you connected and show it in the app.
• Metadata for a video we uploaded: its id, title, privacy status and the channel it landed on, read back after upload so we only report a video as published when YouTube confirms it.
• Permission to upload the video you scheduled, set its thumbnail, and post the comment when you schedule a thread.

We do not access your watch history, your playlists, your subscriptions, your comments, anyone else’s videos, or any YouTube data beyond what the features above need. Google OAuth tokens are encrypted at rest and used only for those actions.

NioConnect’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your use of these features is also subject to the YouTube Terms of Service and the Google Privacy Policy. You can revoke NioConnect’s access to your Google account at any time at myaccount.google.com/permissions.

6. Information we collect automatically

When you use the service we record what we need to keep it secure and to show you what happened in your workspace:

• The IP address and browser user-agent of a sign-in session, so a session can be recognised and revoked.
• The IP address recorded against an audited action (who invited whom, who connected or disconnected a channel, who changed a role). This is the audit log your workspace owner can read.
• Operational logs: errors and request traces, kept so we can diagnose a failed publish. Access tokens are never written to them.

We do not run third-party analytics, advertising pixels, session recorders or heat-mapping on the application.

7. Cookies

NioConnect sets one cookie, and it is a strictly necessary one: your sign-in session. It holds a random token, it cannot be read by JavaScript running in the page, it is not sent with requests another site makes on your behalf (a cross-site form post, or an embedded image or frame), it is transmitted only over an encrypted connection in production, and it expires after 30 days or when you sign out; signing out revokes it on our side too, so an intercepted copy is worthless.

There are no advertising, analytics or tracking cookies, so there is no consent banner to dismiss. Your theme preference is stored in your browser’s local storage and never sent to us.

8. Why we process it

To do the thing you asked for: publish the content you composed, to the accounts you connected, at the time you scheduled; show you which accounts are connected and whether they are still working; and tell you when something failed. We also keep an audit record of actions taken inside your workspace, so that you can see who did what.

We do not use your content or your platform data to train models, to build advertising profiles, or for any purpose other than operating the product for you.

9. Our legal bases (UK/EU GDPR)

Where the UK or EU GDPR applies to you, we rely on:

• Performance of a contract: publishing your posts, storing your connected accounts and their tokens, running your workspace. Without this processing there is no service.
• Legitimate interests: keeping the service secure, preventing abuse, keeping an audit record of who did what, and diagnosing failures. We have balanced these against your interests and they are what any user of a publishing tool would expect.
• Consent: connecting a social account. You grant it on that platform’s own consent screen and you can withdraw it there or here at any time, without affecting anything already done.
• Legal obligation: tax and accounting records for paid plans.

10. When we are a controller, and when we are a processor

For your own account (your email, your workspace, your sign-in sessions, your billing) we are the data controller, and this page describes what we do.

If you use NioConnect to publish on behalf of your own clients (grouping their connected accounts under a Customer in your workspace), then as regards their data you are the controller and we act as your processor. We process it only on your instructions, only to run the service, and we do not use it for anything of our own. Deleting or disconnecting is your instruction to give, and we act on it.

11. How your platform credentials are stored

Access tokens are encrypted with AES-256-GCM under a data key that belongs to your organization alone, and that data key is itself encrypted under a separate master key, which is never stored beside the data it protects. A token is stored only as ciphertext bound to the row it belongs to, so a copied blob cannot be decrypted in another organization’s context.

Beyond storage, a platform credential is:

• never returned by any API we expose: there is no endpoint, for you or for anyone, that can read one back;
• never written to a log;
• never present in an audit entry, a notification, or an error message.

It exists in plain form in exactly one place: in memory, for the moment it takes to sign a request to the platform it belongs to.

Your NioConnect sign-in password is a separate thing entirely and is never handled like this: it is hashed, not encrypted, and cannot be recovered by us or by anyone.

12. Who we share it with

Nobody. We do not sell, rent or share your personal data or your platform data with third parties for their own purposes. There are no data brokers, no advertising partners and no analytics resellers involved.

The only outbound transfers that happen at all are the ones you asked for (your post going to the platform you scheduled it to), plus the infrastructure that runs the service (hosting, our database, and the provider that sends transactional email such as an invitation or a password reset), each of which processes data only on our instructions. If we are ever legally compelled to disclose data, we will do so only to the extent required.

13. Where your data is processed

Your data is stored and processed on our hosting provider’s infrastructure. Where that involves a transfer out of the UK or the European Economic Area, we rely on the UK/EU Standard Contractual Clauses, or an adequacy decision where one covers the destination.

Publishing itself is, by its nature, an international transfer: when you schedule a post to a platform, its content and the connected account’s identifier go to that platform, wherever it operates. That is the instruction you gave.

14. How we protect it

Everything travels over TLS. Passwords are hashed with Argon2id and cannot be recovered. Platform access tokens are sealed as described above. Access inside your workspace is governed by roles, and every consequential action is written to an append-only audit log that the application provides no way to edit or delete, not for you and not for us.

Every query the application makes must name the organization it is for; one that does not is refused before it becomes a database query, so one customer’s data cannot be returned to another by mistake. No security is absolute, and we will tell you promptly if a breach affects your data.

15. How long we keep it

Your content and connected accounts are kept for as long as your workspace exists. When you disconnect a channel, its stored access is retired immediately and cannot be used to publish again; reconnecting requires a fresh authorization from the platform.

Being straight with you about what “deleted” means here: our database marks a record as deleted rather than erasing the row on the spot. So disconnecting a channel retires its encrypted token immediately (the application can no longer read it and it can no longer publish) while the encrypted row itself remains in our database, unusable, until the workspace is erased.

Erasing a workspace outright is something you ask us for and a person carries out. It is not a button in the product today. It is described, with the response time we hold ourselves to, on the data deletion page. Once it is carried out, records are erased or anonymised. Our encrypted backups are retained for up to 30 days, so a copy can survive there for that long afterwards before it rolls off.

Audit records are append-only by design: they are the record of who did what in your workspace, and a log that could be edited would not be one. Nothing in the application can remove them; they are erased or anonymised only as part of erasing the workspace itself.

The periods we hold ourselves to:

• Account, workspace and content: for as long as the workspace exists, then erased or anonymised within 30 days of a deletion request we have carried out.
• A disconnected channel and its token: retired immediately and unusable; the encrypted row is removed with the workspace.
• Sign-in sessions: 30 days, or immediately on sign-out or password reset, both of which revoke every session on the account.
• Operational logs: up to 12 months.
• Encrypted backups: up to 30 days, then they roll off.
• Billing and tax records: as long as the law requires, which is longer than any of the above and is not ours to shorten.

16. Children

NioConnect is a business tool. The service is intended for use by adults acting for themselves or for an organization, it is not designed for or marketed to children, and it is not directed to them.

You must be 18 or over to create an account, the same requirement the terms of service state. We do not knowingly collect personal data from anyone under 18. In particular, the service is not directed to children under 13 within the meaning of the U.S. Children’s Online Privacy Protection Act, and we do not knowingly collect personal data from them; where the UK or EU GDPR applies, we do not rely on a child’s consent as a basis for any processing.

If you are a parent or guardian and believe a child has given us personal data, write to info@nioconnect.com. We will delete the account and the data promptly, and we will confirm to you when it is done. You do not need an account with us to make that request, and we will not ask you to create one.

17. Marketing and communication choices

Some email is part of the service and cannot be switched off while your account is open: a password reset, a workspace invitation, a security alert, and (the one that matters most here) a notice that a scheduled post failed or that a connection needs reconnecting. Turning those off would defeat the product.

Anything else is optional. If we ever send you product or marketing email, every message carries an unsubscribe link, unsubscribing takes effect immediately, and it does not affect the messages above. You can also change your in-app notification preferences from your account settings.

We do not use your content, your connected accounts or your platform data to target advertising, and we run no advertising on the service.

18. Your choices and your rights

• Disconnect an account at any time, from Channels in the app. This is immediate and needs nobody’s help.
• Revoke our access at the platform, from that platform’s own apps or connected-services settings. That is your unilateral off switch and it does not depend on us.
• Ask for a copy of your data, a correction, or erasure by writing to info@nioconnect.com. See the data deletion page for what happens then and how long it takes.

If you are in the UK or the EEA, you have the rights to access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent at any time. Exercise any of them by writing to info@nioconnect.com. You also have the right to complain to the data protection supervisory authority where you live or work.

If you are a California resident, you have the rights to know, delete, correct and to limit use of sensitive personal information, and the right not to be discriminated against for exercising them. We do not sell or share personal information as those terms are defined by the CCPA/CPRA, so there is nothing to opt out of.

We answer any of these requests within 30 days, and we will not charge you for it. We may need to confirm you are who you say you are before we act.

19. Links and third-party services

The connected platforms are not ours, and once your post reaches them it is governed by their own terms and privacy policies rather than this one. Links from our pages to their documentation are for your convenience; we are not responsible for what those sites do.

20. Changes to this policy

If this policy changes in a way that affects what we collect or what we do with it, we will update the date at the top of this page and notify workspace owners.

21. Contact us

For any privacy question, to exercise a right, to ask about a deletion request, or to complain, write to info@nioconnect.com. A person reads it. We answer within the time the law allows and usually much sooner.

If you are not satisfied with our answer, you can complain to the data protection supervisory authority where you live or work.