Privacy Policy

Data we process

• Selected Telegram channel and group content, including message text and related metadata.
• Channel registry data such as channel keys, usernames, titles, tags, and folder mappings.
• API request and authentication metadata needed to operate, secure, and audit the service.
• Export job metadata, runtime logs, and operational diagnostics generated by the system.

Where the data comes from

• Telegram, through authenticated ingestion of channels and groups selected by the operator.
• Operator-managed runtime configuration such as channel registry YAML and service settings.
• Requests made to the API directly or through OpenAI/ChatGPT Actions.

How the data is used

• To ingest, store, search, count, export, and analyze Telegram content.
• To operate authenticated API access, rate limiting, export delivery, and reliability tooling.
• To investigate failures, verify behavioral parity, and maintain service security and integrity.

Storage and service providers

• Current production runtime stores primary data in PostgreSQL; compatibility or local deployments may still use other configured datastores.
• Large export artifacts may be stored in object-storage-backed export paths.
• Operational state and job coordination may use Redis and related runtime infrastructure.
• Telegram and OpenAI/ChatGPT are external platforms involved in the end-to-end workflow.

Retention

Data retention is driven by the active runtime policy and may vary by channel. Settlenova does not promise one fixed retention period for all imported Telegram data.

Security baseline

• Public API access is expected to run over HTTPS.
• Authenticated API requests require bearer-style credentials or equivalent configured auth.
• Operational access is restricted to the service runtime and authorized operators.

Contact

Privacy and service questions can be sent to support@settlenova.com.