Skip to main content

Third Party Cookies

Minnit uses cookies to store user account information and preferences. These cookies are set when you sign into a chat for the first time, or log into your account.

If you're accessing a Minnit chat that's embedded on another website, these cookies will be considered third party cookies since they are not being set from the current website that you are on.

Some web browsers block third party cookies by default, which means that you will lose your account data and preferences when you refresh.

"Tap or click to enter the chatroom"

If users have third-party cookies blocked, they may see "Tap or click to enter the chatroom" when loading the chat. Once they tap or click the button, a first-party window is opened that can read their user data and send it back to the chatroom. This allows the chatroom to function properly, and for users to avoid having to constantly re-login, if third-party cookies are disabled.

To prevent abuse, all users may see this screen if your chatroom has a large volume of users entering. An individual may also see this if they're refreshing a lot.

If you own the chat, you can avoid third party cookies entirely by serving the chat from your own domain by using custom domains. Custom domains are available for Organizations on the Lite plan and higher.

Alternatively, if you use the <script> embed method on your Organization, user data will be stored using Local Storage on the site that is embedding the chat. This means that data is stored on the first-party window and will not be impacted by third-party cookie settings.

Using Zero-Click Single Sign On (SSO) will also prevent this from showing up, as the user's data is sent via the SSO parameter rather than the user's cookies.

Allowing third party cookies

If you are unable to do any of the above, users may be able to third-party cookies in their browser settings, depending on their device.

Some browsers offer a white list option (e.g. Chrome, Edge and Opera) where you can allow specific websites to set third party cookies.

In this case, allowing [*] is more secure than allowing third party cookies to be set by all websites.

For organizations, you would need to allow cookies to be set from the organization domain.

Instructions are available for:

Internet Explorer

Google Chrome


Safari (Does not apply to iOS or iPadOS)