Nimply Sidekick Browser Extension Privacy Policy

What Sidekick collects

Sidekick handles four things, and nothing else:

• Your sign-in token. Sidekick signs you in to your existing Nimply account and stores the resulting token so you do not have to sign in again on every use.
• The content you click to save or draft from. This is the text of a post, comment, or article; the link to it; and the links to any images or video it contains. Sidekick reads this only for the one item you clicked on.
• The display name and profile link of that content’s author, kept alongside the saved item so you can see and credit where it came from.
• Your workspace choice and your preferences, stored on your own device so the extension opens where you left it.

Sidekick does not collect your browsing history, the pages you visit, your cookies, or your logged-in sessions on any website. It contains no analytics or advertising code of any kind, and it loads no code from anywhere other than the extension package your browser installed.

When it collects it

Only when you click. Reading a page happens after you click the Sidekick toolbar icon, choose a Nimply entry from the right-click menu, or press the extension's keyboard shortcut — and it reads only the page you were on when you did so, once.

Sidekick never reads pages in the background, never runs on a schedule, never follows links on its own, and never reads a page you have not clicked on. Your browser enforces this: the extension is granted access to the current tab by your click, and that access lapses when you navigate away. Even after it has read a page, nothing is sent to Nimply until you confirm in the side panel where you want it to go.

Where the information goes

Content you confirm is sent to your own Nimply workspace — your Ideas board, your media library, or your post composer — over an encrypted connection, and is treated like anything else you put in that workspace. It is visible to the members of that workspace, and to no one else. We do not sell it, we do not share it with data brokers or advertisers, and we do not use it to build profiles of you or of anyone whose post you saved.

When you ask an AI agent to draft a post or suggest replies, the source text is sent to the third-party AI model providers we use as service providers for Nimply's AI features, solely to produce that draft for you. We keep a current list of these sub-processors and will provide it on request at privacy@nimply.io.

Comment or message text you capture for reply suggestions is used to produce those suggestions and is not stored by Nimply afterwards.

If someone saved a post you wrote

This section is for people who are not Nimply customers. When a Nimply customer uses Sidekick to save a public post, that customer decides what to save; Nimply processes it on their instructions. What we process about the author of a saved post is the content of that public post and the author's public display name and profile link, kept for reference and attribution inside that customer's private workspace. We do not collect email addresses, phone numbers, or other contact details, we do not build profiles, and nothing about you is published anywhere by the extension.

We rely on legitimate interests (Article 6(1)(f) GDPR) for this limited processing of publicly posted professional content, and we rely on the disproportionate-effort exemption in Article 14(5)(b) GDPR for notifying you individually — this page is the public notice that takes its place.

If you would like content about you removed, or want to object to this processing or exercise any other right (Articles 15 to 22 GDPR, including erasure under Article 17), write to privacy@nimply.io with the link to the post. We will act on it, and respond, within 30 days.

How long it is kept

Anything you save with Sidekick stays in your workspace until you delete it — deleting the card, the media item, or the draft removes it. Archived captures are purged 180 days after archiving. Deleting your Nimply account removes the workspaces you own and their contents, as described in the main Privacy Policy.

The extension itself keeps nothing about the pages you visit, so there is nothing to retain there. Removing Sidekick from your browser deletes the sign-in token and preferences it stored on that device; you can also sign out from the panel, which revokes the extension's access to your account.

Limited Use

Nimply's use of information received from the browser extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Specifically:

• We use the information only to provide and improve the features described on this page and in the store listing.
• We do not transfer it to third parties except as necessary to provide those features (for example, the AI model providers named above), to comply with applicable law, or to investigate abuse and protect the security of the service.
• We do not sell it, and we do not use it for advertising, ad targeting, credit assessment, or lending purposes.
• We do not allow humans to read it, except with your explicit permission (for example, when you ask our support team to look at something), where it is necessary for security or to comply with applicable law, or where the data has been aggregated and anonymised.

What is stored on your device

Sidekick stores only what is strictly necessary for the features you asked for: your sign-in token (encrypted at rest in the browser's extension storage) and your preferences, such as the workspace and board you last used. Under the EU ePrivacy Directive and the UK Privacy and Electronic Communications Regulations, this is strictly-necessary storage, so no separate consent banner applies to it. Sidekick sets no analytics cookies, no advertising identifiers, and no tracking identifiers of any kind, and it does not read cookies set by the websites you visit.

Permissions the extension asks for

Sidekick asks for six permissions and no more. Your browser will show them at install time; grouped by what they are for, they are:

• Active tab and scripting — to read the post or article you are looking at, and only after you click the toolbar icon, a right-click menu entry, or the keyboard shortcut.
• Storage — to keep your sign-in token, chosen workspace, and preferences on your device.
• Side panel (side bar in Firefox and Safari) — so the extension’s own screen lives beside the page instead of being injected into it.
• Context menus — to add the right-click entries for saving a post or an image.
• Identity — to sign you in to your Nimply account.

The only web addresses Sidekick is permitted to contact are Nimply's own (api.nimply.io and app.nimply.io). It does not request access to all websites, to your cookies, to your network requests, or to your list of tabs or installed extensions.

Firefox data collection disclosure

For the Firefox listing, Sidekick declares two categories of required data collection, matching this policy: authentication information (your Nimply sign-in token) and website content (the post, comment, image link, or article you click to save or draft from). No optional data collection is declared.

Security

All communication between Sidekick and Nimply uses encrypted connections. Sign-in tokens are encrypted at rest on your device, are short-lived, and are revoked when you sign out. The extension executes no code fetched from the internet, and content it reads from a page is treated strictly as text, never as instructions or markup to run.

Children

Sidekick is part of a business tool and is not directed to children under 16. We do not knowingly collect personal information from children under 16.

Changes to this policy

If we change what the extension collects or how it is used, we will update this page, change the "Last updated" date above, and show the change in the extension before the new behaviour takes effect.

Contact

For privacy questions, removal requests, or a copy of our current sub-processor list: