Privacy policy
Version dated October 11, 2026
1. Operator and scope
Operator: Retalk project owner — legal details are awaiting completion. Personal data contact: din.tezekbayev@gmail.com. This document describes data processing when using the Retalk landing site and application. Future channels will be connected only after the documents are updated and necessary consent is obtained.
2. Data we process
| Data | Purpose |
|---|---|
| Connected Threads account ID, name and permissions | Authorization and linking the channel to a workspace |
| OAuth tokens | Meta requests authorized by the user; tokens are stored encrypted on the server |
| Drafts, schedules, posts, comments and prepared replies | Publishing, inbox and reply preparation |
| Knowledge base, system prompts and assistant settings | Generating content and replies using business data |
| Links and text of manually added public posts, search rules | Finding relevant public conversations |
| Technical logs, job queue and session cookies | Operation, security and diagnostics |
| Email and information submitted in an inquiry | Handling support, access or data deletion requests |
3. Grounds and limitations
We process data to provide the requested service, fulfill agreements with users and maintain security. Connecting Meta requires separate authorization. You may revoke access. We do not sell user data or use API data for purposes that have not been agreed upon.
4. AI and third-party services
For generation requests, the necessary request text, settings and relevant knowledge are sent to the configured AI provider (in the current architecture, OpenAI through an isolated AI Core). Do not add knowledge base data that you are not entitled to share for this purpose. Meta processes data under its own policies. The landing site may be hosted on Vercel; application infrastructure is determined before launch.
5. Retention and deletion
We retain data for as long as needed to operate the workspace and meet legal obligations. Disconnecting a channel removes its OAuth token from active storage; saved posts and knowledge remain until separately deleted. Full deletion can be requested via din.tezekbayev@gmail.com. The planned response time is up to 30 days after account ownership is verified. Backups are deleted according to a retention cycle that will be specified before production launch.
6. Security and access
The application separates workspace data, stores tokens encrypted and verifies webhook signatures. Access is provided to the workspace owner and necessary processors. API secrets are not included in the client interface or a public repository.
7. Your rights
You may request access, export, correction, deletion or restricted processing of your data, and revoke Meta permissions. Send your request to din.tezekbayev@gmail.com. To protect data, we will ask you to confirm your right to the account; do not send passwords or OAuth tokens.
8. International processing and changes
Connected providers may process data outside the user's country. Applicable terms and transfer mechanisms will be established before launch. If purposes, providers or channels change materially, we will update this document and request renewed consent where necessary.