File Manager

Privacy and Cookies

How Outcome uses cookies

Outcome uses cookies and similar browser storage to operate this site, maintain secure sessions, remember necessary settings, and help protect user accounts. Your organization may provide additional privacy information for services and integrations it has configured.

Browser sign-in alerts

After you successfully sign in, Outcome stores a necessary security cookie in your browser. The cookie helps Outcome recognize that your account has previously signed in successfully from that browser. If you later sign in successfully from a browser we do not recognize, Outcome queues a security email to the email address associated with your account. Delivery may be delayed while notification delivery is temporarily paused.

The cookie contains a random identifier. It does not contain your name, username, email address, password, IP address, location, browser details, or authentication credentials. Outcome stores a protected hash of the random identifier on the server and associates it with your account.

Outcome does not use this security identifier for advertising, general analytics, cross-site tracking, or browser fingerprinting.

When the security cookie is created and updated

Outcome creates the cookie only after a successful completed sign-in, including multi-factor authentication when required. It is not created or updated after an unsuccessful sign-in.

After each later successful sign-in from a recognized browser, Outcome refreshes the cookie expiry and the associated server record. The random identifier normally stays the same; refreshing it does not give the browser access to your account.

How long recognition lasts

The cookie and server association are active for up to 90 days after the most recent successful sign-in from that browser. Each successful sign-in starts a new 90-day period. Outcome uses a scheduled process to remove inactive server associations.

Your browser or device settings may remove cookies sooner. Clearing site data, using private browsing, changing browsers, changing browser profiles, or using software that removes cookies will cause a later successful sign-in to be treated as coming from an unrecognized browser.

Your choices

This cookie supports an automatic account-security feature and does not have an Outcome preference or opt-out control. You can remove it using your browser site-data controls, but the next successful sign-in will be treated as unrecognized. That sign-in will also queue another security email, which may be delayed while notification delivery is temporarily paused.

Information in a sign-in notification

The email may show the sign-in time, IP address, approximate location, browser, and operating system. These details help you assess the activity, but they do not prove which person or physical device signed in. IP-based location can be inaccurate, especially when a VPN, proxy, mobile carrier, corporate gateway, or privacy service is used.

If you do not recognize a sign-in

Contact your organization administrator or security team immediately. If you use a local Outcome password, change it and review your multi-factor authentication settings. If you use single sign-on, follow your organization process to secure the identity-provider account.

For questions about how your information is handled, contact your organization using the support or privacy contact information provided on this site.