Updated: November 16, 2026
Privacy policy
This policy explains which data the Tredgen service (the website tredgen.com and the app app.tredgen.com) processes, why we use it, how long we keep it, who we share it with, and how to delete it. The data operator is the seller named at the end of this page. We process data under the personal data laws of the Republic of Kazakhstan.
By using Tredgen, you agree to this policy. If you do not agree, do not use the service and delete your account.
Data we process
- Account: email, a password hash (we never store the password itself), name, interface language, time zone, and the country of your brand.
- Threads connection: the ID, name, avatar, and bio of your Threads profile, the permissions you granted, and the access token. The token is stored encrypted. We never receive your Threads password.
- Content: up to 50 of your latest Threads posts, which we import to learn your style; your style profile and brief; your niche map; the posts Tredgen writes; the plan and the posting schedule.
- Facts about you: what Tredgen finds in your own posts and in your Threads profile bio: your product or service, lead magnet, experience, city, and life stories. Posts say only these true things about you. We do not keep the bio itself, only the facts found in it. You see the facts on the Voice page and can remove any of them.
- Metrics: views, likes, replies, reposts, quotes, and followers of your posts and account, as Threads reports them.
- Comments: the texts of the answers Tredgen writes. While an answer is in progress and for 30 days after, we keep a snapshot of the post or comment it answers: the text, the author’s name, and the link. After that, the text, name, and link are deleted, and only the numbers of our answer remain.
- News hooks and Threads trends: to see what people discuss now in your niche and across Threads, Tredgen searches public posts of other people on the topics of your niche and on wide topics of your country and language. We keep such a post for 72 hours after it was published: its text, the author’s name, the link, the time, the media type and image link, the topic tag, and the number of replies under it. Then the post is deleted. The trend card and the history of picks keep only our own wording of the topic, without the text or the author’s name. Tredgen writes posts on trends in your words and with facts about you: it never retells other people’s posts or names their authors. For news, we store the headline, a short summary, the link, and the source’s publication date.
- Chats with the Tredex assistant: your messages to Tredex and its answers, the cards with your account data it showed, and the actions it proposed with your decision on each.
- Voice input: the recording you dictate to Tredex. We send it for recognition and forget it at once: neither we nor the recognition provider keep it. Only the text you send is kept.
- Feedback: the text you sent in the feedback window, the phone number if you left one, and how many times we showed you that window.
- Payments: the order number, plan, period, sum, currency, and status of a payment. Only Robokassa receives card details; they never reach us.
- Pictures for posts: the pictures and carousels Tredgen draws for your posts, their scripts (the title, the text, and what to draw on each slide), and the pictures you upload to a post yourself.
- Technical data: the sign-in session cookie, the session’s IP address and browser, a log of AI calls without the prompt texts, and product events (IDs only, no emails or texts).
- Meta pixel: the website and the app run the Meta pixel. It sets the
_fbpand_fbccookies and sends Meta the page address, IP address, browser, and actions: viewing pages and plans, signing up, connecting Threads, starting a payment, a payment with its plan, sum, and currency, and turning on the post and comment autopilots. Meta may receive the email from the sign-up form only as a hash — an irreversible code by which Meta recognizes its own account. Post texts, comments, and Threads data never reach the pixel.
Why we use it
- to create your account and keep it secure;
- to write, plan, and publish posts, answers, and comments on Threads on your behalf — only after you connect Threads and only within the features you turn on;
- to show analytics, prepare the AI review, and use your best posts when writing the next ones;
- to let Tredex answer your questions about your account and carry out the actions you confirm with its button or a reply in the chat; Tredex changes and publishes nothing without your confirmation;
- to send emails about your first publication, failures, Threads reconnection, and account recovery;
- to read your feedback and, if you left a phone number, to call you about it;
- to find errors and protect the service from abuse;
- to learn which Tredgen ads on Meta bring users, and to show them to people the service may help.
We never sell data. Only the Meta pixel serves the advertising of Tredgen itself; we show no ads of other companies.
Threads data
Tredgen connects to Threads through the official Threads sign-in. We ask only for the permissions the features need:
| Permission | Why |
|---|---|
threads_basic |
your profile, its bio, and your posts: to learn your style and the facts about you |
threads_content_publish |
publishing posts and chains |
threads_manage_insights |
post and account metrics |
threads_read_replies |
replies under your posts |
threads_manage_replies |
publishing answers and comments |
threads_keyword_search |
finding discussions and posts on the topics of your niche |
Threads data is used only for these features and for one rule: there is one trial per Threads account. So we keep the ID of the Threads account your trial ran with, so that no other Tredgen account gets a new trial with it. This mark is deleted with your Tredgen account and on Meta’s data deletion request. You can disconnect Threads in the Tredgen settings: the token is deleted, the autopilot turns off, and scheduled posts go back to drafts. If you remove Tredgen in your Threads settings, Meta sends us a request and we delete the data we received from Threads — see Data deletion.
AI processing
To learn your style, write posts and answers, pick news hooks and trends, and prepare the review, we send the necessary texts to language models through OpenRouter: your posts, brief, niche map, the post or comment that needs an answer, and public posts from the Threads search, to understand what they say and how they are written. OpenRouter passes the request to the model provider. We send only what a task needs and never send your email, password, or tokens. Code checks every model answer; raw model output is never published.
Pictures and carousels for posts are drawn by an OpenAI model (GPT Image) through OpenRouter. The request carries the post text, the script of the slides, and the picture style you chose: its description and the sample we drew. Pictures you upload yourself and pictures from your Threads posts are never sent to a model. Finished pictures are kept in a separate public storage on our server: Threads fetches a picture by its link, so anyone who has the link can open the file. The links are random and carry none of your data.
When you write to Tredex, the model receives your message, the earlier messages of that chat, and the account data the answer needs: numbers, the plan, posts, settings, reviews, and comments. Tredex sends requests only to providers that do not keep request data. A dictated recording goes through OpenRouter to a speech recognition model (ElevenLabs Scribe, or OpenAI Whisper when it fails) at providers that do not keep the recording.
Who we share data with
| Processor | Why | Where |
|---|---|---|
| Sole proprietor WOW MEDIA (V. K. Vovchuk) | development and technical support of the service, including the Tredgen app at Meta; processes data on the seller’s behalf | Kazakhstan |
| Meta Platforms (Threads) | publishing and Threads data for your connection | USA |
| OpenRouter and model providers, including ElevenLabs and OpenAI | language models, speech recognition for Tredex, and pictures for posts | USA and other countries |
| Resend | sending emails | USA |
| Robokassa (Russia and Kazakhstan) | card payments and fiscal receipts; card details are entered only at Robokassa | Russia, Kazakhstan |
| Sentry | app error reports without IP addresses, cookies, or post and comment texts | USA |
| Cloudflare (R2) | private storage of database and file backups; copies are deleted after 14 days | Europe and other countries |
| Meta Platforms (Meta pixel) | measuring and showing Tredgen ads: the _fbp and _fbc cookies, IP address, browser, pages, and actions on the website and in the app |
USA |
The data is stored on our server in Almaty, Kazakhstan. Using these processors means part of the data leaves Kazakhstan; by using the service, you agree to this transfer. We also disclose data when the law requires it.
How long we keep data
- The account, posts, style profile, niche map, metrics, and AI call log — while the account exists.
- The mark of the Threads account your trial ran with — while the account exists or until Meta’s data deletion request.
- Chats with Tredex — until you delete the chat or the account. Voice recordings are not kept.
- Feedback and the phone number in it — as long as the account exists.
- Snapshots of other people’s posts and comments — 30 days after our answer.
- Public posts of other people from the Threads search — 72 hours after they were published.
- Sign-in sessions — until you sign out or the session expires.
- Pictures for posts — while the post and its picture exist. The file is deleted within two hours after you remove the picture or delete the post or the account.
- Database and file backups — 14 days on our server and in Cloudflare R2: deleted data leaves the backups within that time.
- Product events remain after the account is deleted, but they contain no emails or texts.
- The Meta pixel cookies
_fbpand_fbc— up to 90 days after the last visit. Meta keeps the data the pixel received under its own policy. - Payments — the order number, sum, currency, plan, and status, without card details — as long as accounting requires; after the account is deleted they stay without a link to it.
Your rights
You can learn which data we keep, correct it, withdraw your consent, and delete the account with all its data. You can delete the account in the app settings — see Data deletion. For any question about your data, write to hello@tredgen.com from the email of your account.
Cookies
The app uses the cookies it needs to keep you signed in. The website tredgen.com and the app run the Meta pixel: it sets the advertising cookies _fbp and _fbc so that Meta recognizes a visit after an ad click. You can delete or block them in your browser settings — the service works the same without them.
Age
Tredgen is not intended for people under 18.
Changes
We update this policy when the service’s features, processors, or legal requirements change. The current version is always on this page, with its date at the top. We will email you about significant changes.