---
title: What Turn Zero support can see
description: Choose whether to share account information with Turn Zero support, understand what it can read, and stop sharing when you want.
slug: /concepts/what-turn-zero-support-can-see
order: 19
visibility: public
redirects_from: []
---

# What Turn Zero support can see

Turn Zero's support agent can use account information to help investigate a problem with your application. It can read that information only after you click **Let support read my account** in a chat on the Questions page.

## You choose when to share

Sharing applies to that chat for one hour. Click **Stop sharing** to end it sooner. Signing out also ends support's access, across your chats.

## What support can read

While you share, support can read information from your account alone:

| Information | What support can see |
| --- | --- |
| Account | Your account's summary, plans, and usage counters. |
| Applications | Status, recent deploy history, and deployment checks. |
| Logs | Recent logs with common email, phone number, and credential patterns removed. Fields named for a person or a credential are removed too. |
| Settings and secrets | Their names and where they apply, never their stored values. Support can also read configuration such as sign-in methods, schedules, and storage areas. |
| Database | Table structure, such as column names and types, indexes, and the names of applied migrations. It does not read your application's data rows. |
| Deployed files | Files from the serving version or the previous version, excluding installed dependencies, environment files such as `.env`, and binary files. These are deployed files, often build output, rather than your repository. |
| tzTrack issues | Issues in spaces your account owns, excluding spaces bound to an application. It cannot read another account's spaces shared with you. |

## What stays private

Support cannot read stored secret or setting values, database data rows, end-user records, or stored user files. It cannot read another account.

Logs, deployed code, and issues can contain information you put there. A secret written into code or printed in a log can still be seen. Log filtering catches common patterns; it does not guarantee that every private detail is removed.

The support agent cannot change your account, edit your application, or deploy a fix.

## Read limits

Each sharing permission allows up to 30 reads a minute. Each chat allows up to 600 reads in any hour, even if you stop sharing and share again. If support reaches a limit, it must wait before reading more.

## Related

- [Sign-in, sessions, and tokens](/cloud/concepts/sign-in-sessions-and-tokens/)
- [What happens without asking](/cloud/concepts/what-happens-without-asking/)