Cookie handling in both Silo for Safe Access and Silo for Research (Toolbox) browser environments behave much like traditional web browsers. For instance, if you were to sign-in to amazon.com while in an active Silo session, then accessed an amazon.com hyperlink in a separate Silo tab, the cookie indicating that you're signed-in to amazon.com will persist
Please note that this particular cookie behavior does not extend across individual Silo for Research (Toolbox) instances. For example, if you have multiple Silo for Research browser sessions open, the cookie containers are expected to remain exclusive to each respective session
Silo for Safe Access and Silo for Research have slight differences once a browser session has been closed. For Silo for Research, unless Browser Data Persistence is enabled, all cookies are purged, and a fresh browser environment is presented upon each launch
The same is mostly true for Silo for Safe Access except for end-users who choose to save their login credentials to a particular Web App, along with the Password Saving policy enabled. Some relevant cookies are preserved to help prevent MFA login prompts from constantly appearing, along with various usability reasons. In general, saved cookies will vary from one website to another.
With the release of Web Client v1.9, cookie insertion was implemented to help improve Google's geolocation reporting accuracy when using the Web Client. Also, in an August 2023 infrastructure update, cookie persistence was implemented for Google-based Web App shortcuts, such as Gmail
Please contact Support for any additional questions