Privacy Policy
How TeleGain processes operator, workspace, Telegram account, target, log and support-request data.
Operators, workspace owners and support
Summary
- The panel stores data needed for sign-in, job control, truthful evidence, support and security.
- Telegram session assets, proxies, targets, logs, artifacts and AI settings are workspace data and must remain isolated from other workspaces.
- Export, deletion and support access are governed by the data retention rules.
Data we process
TeleGain may store operator identity, email, roles, workspaces, subscription status, login history, panel sessions, audit events and support requests.
For Telegram operations the panel stores imported accounts, proxy binding, session assets, account statuses, targets, datasets, prompts, job results, logs, artifacts and error reasons.
How data is used
Data is used for panel access, job planning, actions selected by the operator, result display, prevention of repeated unsafe launches, support and incident investigation.
TeleGain must not show one workspace's data to another workspace. Export, preview, artifacts and lists must check access before returning data.
AI and external providers
When text generation is enabled, only data needed for the specific generation task may be sent to the selected AI provider. Secrets, session files, access hashes and private keys must not be sent in prompts.
The operator is responsible for source data and instructions sent to generation, and should review generated text before scaling it.
Support and security
Support may see data only for help requested by the operator, failure analysis, access recovery or security review. Secrets should be masked, and support actions must be auditable.
Export or deletion requests are handled under the data, export and deletion rules.