---
title: "What RShift Support can see"
description: "The exact context support receives, and what it never receives."
image: "https://help.rshift.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.rshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What RShift Support can see

Support is reached through email written to the product’s support address. Nothing is sent to a third-party chat vendor.

## Context that can be sent

- RShift user id.
- Current workspace id or slug.
- Current module, such as integrations, billing, or monitoring.
- Plan, entitlements, and AI credit state.
- Provider, status, error code, run id, or job id.

## Content that is not sent

- Platform tokens, refresh tokens, API keys, client secrets.
- AI prompts, completions, tool inputs, or tool outputs.
- Publishing body text, asset files, or unpublished drafts.
- Raw monitoring data and audit log contents.
- Application package files.
- Payment card numbers or raw payment provider payloads.

If support asks for more, share visible error codes, screenshots, time ranges, and states — never secrets, tokens, or private customer content.

Source: https://help.rshift.com/security/what-support-can-see/index.mdx