Skip to content
New AI Custom Form BuilderDescribe the intake form. It ships branded and end-to-end encrypted.AI Custom Form Builder is here See it build
Integrations

Support for Third-Party Cookie Restrictions in the SendSafely Zendesk Agent App

Modern browsers are increasingly focused on user privacy — and one area seeing major changes is third-party cookie (3PC) handling.

Brian Holyfield · 2 min read
Support for Third-Party Cookie Restrictions in the SendSafely Zendesk Agent App

Modern browsers are increasingly focused on user privacy — and one area seeing major changes is third-party cookie (3PC) handling. This affects many apps that operate inside iFrames, including our own SendSafely Zendesk Agent App. We’re excited to share a new enhancement that ensures our app continues to work seamlessly, even when third-party cookies are blocked.

What’s Changing with Browsers?

Each browser handles third-party cookies in different ways:

Since the SendSafely Zendesk Agent App runs in an iFrame, cookies used for key functionality (like session tracking and authentication) are classified as third-party by the browser. Previously, when these cookies were blocked by the browser, agents were unable to use the SendSafely agent app.

Solution: The Storage Access API

To maintain a seamless experience, we’ve implemented a new fallback mechanism using the Storage Access API — a browser-native standard specifically designed to replace third-party cookies in privacy-conscious environments. Where available, the API provides a secure, consent-based mechanism for data access between SendSafely and Zendesk.

####

How It Works:

####

User Experience: What Agents Will See

On the first session where 3PCs are blocked:

  1. The agent will see a SendSafely in-app prompt:

Zendesk Prompt

  1. After clicking OK, the browser will display a one-time prompt asking if you wish to allow SendSafely to share information with Zendesk. Once access is granted, the prompt won’t appear again for future sessions.

Browser prompt

⚠️ NOTE: The Storage Access API prompts vary slightly by browser, but all clearly indicate that SendSafely is requesting cross-site access to function properly.

Here at SendSafely, we are committed to keeping your Zendesk workflows secure and ready for the evolving privacy landscape. If you have any questions or feedback on this update, please reach out to support@sendsafely.com.


SendSafely: Encrypted File Transfer for Modern Business

If your organization needs a secure way to transfer files with customers or business partners, our platform might be right for you. Contact us today.

Request a Demo

Frequently asked questions

Does the SendSafely Zendesk Agent App work when third-party cookies are blocked?

Yes. Since July 2025, when third-party cookies are blocked and the browser supports the Storage Access API, the app asks the agent once for permission and then works normally without relying on traditional cookies.

Why does blocking third-party cookies affect the SendSafely Zendesk app?

The SendSafely Zendesk Agent App runs in an iFrame, so the browser classifies cookies used for session tracking and authentication as third-party. Before the update, agents couldn’t use the app when the browser blocked those cookies.

What is the Storage Access API?

The Storage Access API is a browser-native standard designed to replace third-party cookies in privacy-focused environments. It provides a consent-based mechanism for data access between SendSafely and Zendesk.

What will Zendesk agents see when third-party cookies are blocked?

On the first session with cookies blocked, agents see a SendSafely in-app prompt. After clicking OK, the browser shows a one-time prompt asking to let SendSafely share information with Zendesk. Once granted, it doesn’t reappear in future sessions.

Which browsers support the Storage Access API fallback in the SendSafely Zendesk app?

The update works across all major browsers supported by the Zendesk Agent App: Chrome, Firefox, Edge, and Safari. The exact prompt wording varies slightly by browser. See the Zendesk integration.

Written by Brian Holyfield