Privacy and control

Unbound is designed to connect you to apps without keeping a massive database of your personal profile on its own servers. However, it still needs to handle some information just to make the sign-in process work securely.

Information handled during sign-in

To get you signed in safely, Unbound temporarily handles:

• the profile information sent by your chosen provider (like your name or email);
• the web address of the app you are trying to use;
• the specific information the app is asking for;
• some technical security data to make sure no one intercepts your sign-in; and
• standard internet traffic logs (like error messages and security checks).

The exact information depends on what your provider sends and how the service is set up.

How Unbound remembers you

After you sign in, Unbound saves an encrypted "cookie" in your web browser. This acts like a secure, temporary ID badge so you don't have to keep signing in every time. Because this data is kept safely in your browser, Unbound doesn't need to save your profile in a central database.

If you clear your browser cookies, Unbound will forget you're signed in. However, this won't delete your main provider account (like Google or GitHub), sign you out of the apps you already accessed, or erase the information those apps already collected.

Unique IDs for every app

To help protect your privacy, Unbound creates a different, unique ID for you every time you sign in to a new app. This means if you use two unrelated apps, they won't realize you are the same Unbound user just by looking at that ID.

While this makes tracking you across the internet harder, it doesn't make you completely invisible. Apps might still recognize you through other means—such as the email address they asked you to share, or the device you are using—depending on their own privacy policies.

Temporary records

During the sign-in process, Unbound has to temporarily process your data so it can securely tell the app who you are. The system might also store check-ins temporarily to prevent security risks (like someone trying to use your sign-in twice), but this isn't used to build a persistent profile of you.

Everyone plays their part

Your chosen provider (like GitHub or Discord) entirely manages your main account. They have their own terms and privacy rules. Unbound just receives the data they send to help you log in.

The app you sign in to is its own totally separate service. Once you approve a request, the app is responsible for keeping your data safe and deciding what you can do on their site. Unbound can't force an app to delete your data or revoke access once you've handed your info over.

Your choices

You are always in control of the basics. You can:

• deny a sign-in request at any time;
• only approve requests when you recognize the app and are comfortable with what they're asking for;
• clear your browser cookies to sign out of Unbound;
• manage your security directly with your provider (like changing passwords or turning on two-factor authentication); and
• contact the app directly if you want them to delete or change the data they hold.

For the exact legal details, please read the live Privacy Policy and Terms, which explains in details on how the service runs.