Privacy Policy

01Information We Collect

To provide session capture, restoration, and sharing, Niango collects the following categories of data:

• Authentication session data. When a session is captured, or while you are connected to a session, Niango reads the authentication state of the target service from your browser. This includes browser cookies (including secure and HTTP-only cookies), localStorage entries, and IndexedDB contents for the relevant domains. Together these represent your logged-in session and are treated as sensitive data. Niango does not collect or store your account passwords.
• Account identifiers. An identifier from your sign-in provider (e.g. your Google user ID), along with your email, name, and profile picture.
• Package data. Metadata about the packages you create or acquire and the sessions within them.
• Usage and access records. Records of when a session is accessed — including the user, package, session, and timestamps — used to keep shared sessions valid and to show usage history to package owners.

02When & How We Collect It

Niango collects authentication session data in two situations:

• On capture. When you (or a package owner) create or update a session, Niango takes a snapshot of the current logged-in state of the target service.
• Continuously while connected. While you are connected to a session through Niango, the extension may periodically re-read the evolving session (cookies, localStorage, and IndexedDB) and send it to our servers so the shared session stays valid and up to date. This periodic collection applies to every session you connect through Niango — including packages you own, not only packages acquired from others.

Before Niango applies a shared session to a site where you were already signed in, it also makes a one-time backup of your own pre-existing session for that site so it can be restored when you disconnect. That backup is kept locally on your device (see Data Storage).

03How We Use Information

Information is used solely to operate the Niango service. This includes:

• Capturing and restoring sessions on your request
• Keeping shared sessions valid and up to date across a package's members
• Managing packages, access keys, and members
• Registering and authorizing your devices
• Providing usage and access history to package owners
• Maintaining the reliability, security, and performance of the service

Niango does not use your data for advertising, and does not sell or rent it.

04How We Process Data

• Session data is compressed and transmitted over encrypted connections (HTTPS) between your browser and Niango servers.
• Your Niango sign-in credentials are stored in encrypted form on your device.
• As a security measure, session cookies applied by Niango are given a short lifetime and are refreshed while a session is active, so a shared session cannot persist unattended after you disconnect.

05Data Storage

On Niango servers. Session data is stored on Niango servers so it can be restored on your devices and made available to authorized members of the same package. This server-side copy is the reference version of the session and may be updated over time as the session changes. Account, package, device, and access-history data are also stored on our servers.

Locally in your browser. Niango stores locally: your encrypted Niango sign-in token; the session currently applied to the active tab; and a temporary, one-time backup of your own pre-existing session for a site, so it can be restored when you disconnect. The personal-session backup is not uploaded to our servers.

06Data Sharing

Niango's core function is to let users share access to online services through packages. As a result, authentication session data is shared between the members of a package:

• If you create or own a package, the session data captured for that package is made available to the members you grant access to.
• If you acquire access to a package, you receive the session data needed to use it.
• While a session is active, the session of the member currently using it may be captured and redistributed to the package so that all authorized members keep valid access.
• Package owners can view access history for their packages, including which member and device connected to a session and when.

This data is shared only with the users you authorize as members of your package. Niango does not sell, rent, or share your personal information with third parties for advertising or marketing purposes.

07Data Retention & Deletion

You remain in control of your data. You can update or delete sessions, remove members, or leave or revoke access to a package at any time. Deleting a session or a package removes the associated session data from Niango servers, and revoking a member ends their access to that package's sessions.

08User Consent

By installing and using Niango, you acknowledge and consent to the collection, processing, storage, and sharing of data described in this policy. When you share a package, you are responsible for granting access only to people you trust, and only for services whose terms permit shared access. You retain control over when sessions are created, restored, shared, or removed.

09Third-Party Services

Niango only interacts with third-party websites when the user explicitly accesses those services through the extension. Niango is not responsible for the privacy practices of external platforms.

10Data Security

Niango implements technical safeguards to protect stored information and prevent unauthorized access, including encryption in transit (HTTPS), encryption of locally stored credentials, short-lived shared session cookies, and per-device authorization.

11Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with a revised date. Continued use of Niango after changes are posted constitutes acceptance of the updated policy.

12Contact

If you have questions or concerns about this Privacy Policy, please reach out: