# Example Support Responses for Privacy Center Download Issues (/docs/privacy-center/troubleshooting/download-support-responses)

Use these replies when a data subject reports a problem with a data report download from your Privacy Center. For the steps the data subject follows, see [Troubleshooting Data Report Downloads from the Privacy Center](./troubleshooting-downloads.mdx).

Adapt the messages below when you respond to an end-user or relay through your support team. Choose the version that best matches the situation.

## Initial Response (Standard) [#initial-response-standard]

Use when a download failure is first reported and you don't yet know the cause.

<Callout type="info" title="Standard initial response">
  Thank you for reaching out. We'd like to help get this resolved as quickly as possible.

  Could you try the following and let us know the result?

  1. **Use Google Chrome.** It has the best compatibility with our download system.
  2. **Disable any ad blockers or privacy extensions** for the Privacy Center domain before starting the download.
  3. **Stay on the page** during the entire download. Don't navigate away, close the tab, or start another download at the same time.

  If the issue persists, could you let us know which browser and version you're using, whether you have any extensions or privacy shields enabled, and roughly how far the download gets before failing?
</Callout>

## When the Download Is Small (Under 1 MB) [#when-the-download-is-small-under-1-mb]

Use when you know the download is small. File size is ruled out, so focus on browser and extension troubleshooting.

<Callout type="info" title="Small file response">
  We looked into this and the download is quite small, so file size is definitely not the issue. This points toward a browser or extension conflict.

  Could you ask the end-user to:

  1. Try the download in Google Chrome (if they aren't already using it)
  2. Temporarily disable all browser extensions and privacy shields for the Privacy Center domain
  3. Stay on the download page until it completes (don't navigate away or close the tab)

  If it works with extensions disabled, the culprit is one of those extensions. They can re-enable them one at a time to find which one, then add an exception for the Privacy Center domain.
</Callout>

## When the Download Is Large (Over 100 MB) [#when-the-download-is-large-over-100-mb]

Use when the download is large and likely timing out or failing due to network constraints.

<Callout type="warn" title="Large file response">
  This data report is quite large, which makes it more sensitive to network conditions and browser limitations. For large downloads, our system uses time-limited secure links that expire after approximately 15 minutes.

  To give the download the best chance of completing:

  1. Use **Chrome on a desktop computer** (not mobile).
  2. Connect to a fast, stable network (wired Ethernet is ideal).
  3. Avoid running other bandwidth-heavy tasks (streaming, large uploads) during the download.
  4. Stay on the page until the download completes.

  If it still fails, a member of your team with admin access can download the report directly from the Transcend Admin Dashboard as an alternative.
</Callout>

## When the Download Succeeded but the User Can't Open the File [#when-the-download-succeeded-but-the-user-cant-open-the-file]

Use when the user has successfully downloaded the zip but can't extract it or view the HTML report inside.

<Callout type="info" title="Post-download zip and report response">
  Thanks for confirming the download completed. Here are a few steps to help open the report:

  **To extract the zip file:**

  - On a Mac, double-click the `.zip` file to extract it automatically.
  - On Windows, right-click the file and select "Extract All."
  - On mobile, you may need a file manager app (e.g., Files on iOS, or a file manager app on Android) to open zip files.

  **To view the report:**

  Open the extracted folder and double-click the `report.html` file to open it in your browser. If it opens but looks broken, try opening it in Google Chrome with browser extensions disabled.

  If the zip file won't open at all, the download may have been incomplete. Please try downloading again in Chrome and stay on the page until the download finishes.
</Callout>

## When the User Is Frustrated or Escalating [#when-the-user-is-frustrated-or-escalating]

Use when the user has already tried basic steps, is frustrated, or the issue is time-sensitive. Lead with empathy, offer an immediate workaround, and take ownership of the investigation.

<Callout type="error" title="Frustrated user de-escalation">
  We completely understand the urgency and apologize for the difficulty. Getting your data to you is our top priority.

  **Immediate workaround:** A member of your team with admin access to Transcend can download the report directly from the Admin Dashboard and securely transfer the files to the end-user. This bypasses the Privacy Center download entirely.

  In parallel, we are investigating this on our side. To help us pinpoint the root cause and push a permanent fix, any of the following details would be extremely helpful:

  - Which browser and version the end-user is using
  - Whether they have any browser extensions, ad blockers, or privacy shields enabled
  - How far the download gets before failing (percentage, or does it never start?)
  - Any error messages shown on screen

  We don't need all of these at once. Even one or two details will help us narrow things down. In the meantime, the Admin Dashboard workaround should get the data to the user right away.
</Callout>

## Requesting Advanced Debugging Info [#requesting-advanced-debugging-info]

Use when basic troubleshooting has already been tried and you need more technical details to investigate. Only request HAR files or console logs if the user is willing and somewhat technical.

<Callout type="info" title="Advanced debugging request">
  Thank you for working through those steps. Since the issue is persisting, we'd like to collect a bit more information to investigate on our end. Here are a few options depending on what's easiest for the end-user:

  **Option A (quick):** A screenshot of the download page at the moment it fails, including any error messages or the progress indicator.

  **Option B (more detail):** Open the browser's Developer Tools (press F12), go to the Console tab, reproduce the download failure, then screenshot or copy any red error messages that appear.

  **Option C (most helpful, only if comfortable):** Capture a HAR file: open Developer Tools > Network tab > check "Preserve log" > start the download > after it fails, right-click in the Network panel and select "Save all as HAR". This gives us a complete picture of what happened during the download.

  Any of these options would help. There is no pressure to do all three. Even a screenshot goes a long way.
</Callout>
