Privacy Policy

Last updated: 2026-05-30.

1. What this app is

This is a personal publishing assistant built for one individual creator — the owner of the Threads account @i.am.nikolai.iarina. The app generates short text drafts in the creator's own voice, sends them to the creator's private Telegram bot for manual approval, and publishes approved posts to his Threads account via the official Meta Threads Graph API.

This is not a SaaS product. There is no public sign-up, no marketplace listing, no second user. The operator and the only end-user is the same person.

2. Data the operator provides

• Topics typed into the Telegram bot as plain text (e.g., "why founders avoid hard conversations with co-founders").
• Inline-button clicks: Approve / Edit / Reject.
• Optional one-line edit instructions and optional rejection reasons.

3. Data generated and stored locally

• LLM-generated draft posts.
• Approved post text and the resulting Threads post id (so the operator can see his own publishing history).
• A single long-lived Threads access token belonging to the operator, encrypted at rest and refreshed automatically 5 days before its 60-day expiry via the standard th_refresh_token grant.

4. Data we do NOT collect

• No data about other Threads users.
• No follower lists or audience data.
• No analytics SDK data, no device fingerprints.
• Nothing from anyone other than the single operator.

5. Where data lives

All persistent data is stored in a single SQLite database file on a single small VPS controlled by the developer on the operator's behalf. There is no shared multi-tenant database, no cloud object storage, no third-party data warehouse.

6. Third-party services we talk to

• Telegram Bot API — to render the bot UI to the operator. Only the operator's user_id is allowed past the ACL middleware.
• Anthropic Claude API — to generate the drafts. We send the topic text and prompt context (which consists of the operator's own past posts and style rules).
• Meta Threads Graph API — to publish the approved text. We send the post text and the operator's access token to two endpoints (/<user-id>/threads and /<user-id>/threads_publish).

No other third parties. No data sold. No data shared for advertising.

7. Retention

Topics, drafts, edits and rejection reasons are kept indefinitely so the model's voice profile keeps improving on the operator's own feedback. The operator may request a full wipe at any time by messaging the developer (see Contact).

8. Operator rights

The operator can request, at any time, to (a) export all data stored about him, (b) delete all data, (c) revoke the Threads access token, (d) stop the app entirely. Each of these is a single message to the developer.

9. Children

This app is not directed at, used by, or accessible to anyone under 18. The single operator is an adult professional.

10. Security

Communications with Telegram, Anthropic and Meta Threads use TLS. The Threads access token is stored encrypted at rest. Telegram bot access is restricted to a single hard-coded admin user_id via a server-side ACL middleware. The VPS uses key-based SSH and a host firewall.

11. Changes

If we materially change this policy, the new version will replace this page and the "Last updated" date will change. There are no email notifications because there is no mailing list — the only user is the operator who will see changes directly.

12. Contact

Operator and developer contact for any data request, revocation, or question: springvoice7@gmail.com.