Legal
Privacy Policy
What the service stores, why, who it shares data with and how to delete it. No legal fog: what follows describes what the code actually does.
What we store
About your account: email address, whether it has been confirmed, interface language, creation date, a password hash, and the date and edition of the Terms and Privacy Policy you accepted. The password itself is not stored — it cannot be recovered from the hash.
When you sign in with Google: we request only openid email profile and store your Google identifier and email address. We have no access to your mail, files or contacts, and we do not request it.
About your project: name, time zone, publication language, topic, schedule, connected material sources, stop words. Material sources are the feeds and channels you point us at — RSS feeds and public Telegram channel previews; your own Telegram account is not connected to the service.
About connected social accounts: username, platform identifier, granted permissions and the access token. The token is stored encrypted (AES-GCM); the encryption key lives in the server configuration rather than in the database and is bound to that specific account row — a stolen database without the server key yields no tokens. For networks connected through Postproxy, the access token is stored by Postproxy, not by us.
About pipeline activity: collected material, drafts, review results, published posts and their statistics (views, likes, replies), plus records of model-call spending.
About payments: plan, subscription status and period dates, amounts charged and promo codes applied, the Creem customer and subscription identifiers, and the payment notifications Creem sends us (they include the email used at checkout). Card details are processed by Creem and never reach us. Payment notifications are kept after account deletion for accounting and dispute handling, with email addresses removed.
Retention periods
Data is deleted automatically, not “as needed”:
- source material — 90 days;
- completed pipeline jobs — 30 days;
- publication statistics snapshots — 400 days;
- stop-word triggers — 180 days;
- unused material in the pool — 14 days;
- model spending records — indefinitely: this is financial accounting, it contains no texts and is not tied to post content.
Who we share data with
We do not sell data and do not pass it to advertisers. Sharing happens only where the service cannot work without it:
- Connected social networks — only the social networks you connected: publishing posts and comments approved by you or your AI agent, or published automatically if you enabled auto-publishing, auto-comments or agent replies, as well as collecting publication statistics. Nothing is sent to a network you did not connect.
- Postproxy — the publication broker for accounts connected through it. It receives your project name, the texts, images and scheduled times of publications, and the comments and replies posted on your behalf; it stores network access tokens, delivers publications to the respective networks and returns their status, statistics and the comments under your posts.
- Language model providers — the text of the material and the draft is sent for processing to produce a finished post. Your email address and account data are not sent.
- Speech-to-text providers — when you dictate a brief or a rework comment by voice, the recording goes for transcription. The recording itself is not stored: only the transcribed text enters the brief or the comment.
- Search providers — Tavily, Keenable and the search engines behind our own SearXNG instance. The search query is sent to them, so they see what we are looking for at that moment.
- Google reCAPTCHA — on the sign-in and sign-up pages, to tell a human from a bot. Google receives browser technical data to the extent described in its own policy.
- Resend — email delivery (address confirmation, password recovery).
- Payment provider: Creem — taking card payments in USD, refunds, and subscription renewal: we transfer the plan, period, amount, currency (USD), order id, internal user identifier, and the account email address (for invoices, receipts and customer portal access); card details are processed and stored by Creem in its own contour under its own policy.
Backups
The service takes daily backups of the database.
- How long copies live. 14 daily copies, plus one copy for each of the last 8 weeks.
- How they are transferred. A copy sent to another server goes over SSH, so the transfer itself is encrypted. A copy kept on the same server does not count as an off-site copy.
- How they are stored. The archives are compressed, not encrypted — whoever can read the copy file can read the data in it.
- How fresh the off-site copy of the deletion journal is, we have not verified, so we do not promise a specific recovery point.
A separate thing is the project export archive: it stays available for 72 hours, and then the file and the link are deleted.
Cookies and sessions
There are no advertising or analytics cookies. Only technical ones are used: a session identifier (to keep you signed in) and a request-forgery protection token. Your theme choice and form drafts are stored locally in the browser and never reach the server.
Your rights
Download personal data. In your profile (Profile → Account), you can download a full archive of your personal data: account profile, subscription, payment history, notifications, and project archives. Separately, each project's settings include an export of that project's material, drafts, and publications (the project archive and download link are kept for 72 hours, then deleted).
Delete your account. Deletion is available in the “Danger zone” section and requires identity confirmation using an available method: a password (plus a two-factor authentication code if enabled), or a passkey. Along with the account we delete projects, material, drafts, publications and social connections. Deletion cannot be undone.
Disconnect a social account. Disconnecting a connected social account stops publishing and statistics collection immediately.
Cancel auto-renewal. You can cancel auto-renewal at any time from your account via the Creem portal (“Manage subscription”).
For questions about data processing write to support@growthhack.social.
Security
The connection to the service runs over HTTPS. Passwords are stored as hashes, social tokens in encrypted form. Administrator access to service areas is protected by a second factor, and all administrator actions are written to a log.
Nobody can guarantee complete security, and we will not pretend that we do. If you have found a vulnerability, write to support@growthhack.social.
Changes to this policy
For material changes we will update the date at the top of the page. If a change affects what data is shared, we will notify you by email.