Privacy Policy

This policy explains what Akhmat Sultanov, Individual Entrepreneur (trading as App Builders Club, "we", "us") does with your information when you use the CTR iOS app and the ctr-app.com website (together, the "Service").

It is written to be read. Where a section describes something unusual about how CTR works, it says so plainly rather than burying it.

The short version

What you write stays on your device. We do not run a server that stores it.
Generating a post or transcribing your voice sends that one request through OpenRouter to an AI model provider. We name them, and we ask your permission before the first time.
We keep a technical record of each AI request against your account — when, which model, how much — never its content.
Apple handles payment. We never see your card.

Your content stays on your device

Your topics, posts, reference posts, style profile and edit history are stored locally on your device. CTR does not operate a backend that stores your content, and we cannot read what you write.

Deleting the app deletes that content with it. A standard iCloud device backup may retain a copy under Apple's terms — that copy is governed by Apple's privacy policy, not this one.

What we send to AI providers

Generating a post requires sending that one request off your device. Two third-party services receive it:

OpenRouter — receives the request and routes it to an AI model provider. For a post it receives the idea you typed or dictated, the topic context you set (audience, goal, tone, facts) and the reference posts your style profile was built from. For voice input it receives the audio of the recording you just made and returns text. OpenRouter is set not to store prompts, responses or audio and not to allow their use for training.
AI model providers — the model OpenRouter routes to produces the text or the transcript. Providers may retain a request for a short period under their own policies (typically up to 30 days for abuse monitoring) and then delete it. None of them trains on it.

Requests travel through our gateway, which exists so that API credentials are not shipped inside the app. The gateway keeps no copy of your text or audio. Only the request you just made is sent — never your library, never your other topics, never your history.

We ask first. Before the first generation, CTR shows a consent screen naming these providers and describing what is sent. Nothing is sent until you accept, and every AI request checks that consent first.

What else we collect

Onboarding answers. What you create, your main platform, how often you post and how long a post takes you. They personalise the app and stay on your device; they are not sent to us.
Usage records. For each AI request our gateway keeps a technical record linked to your account: the time, the model used, token counts, cost, duration and whether it succeeded. We use it to enforce plan limits and billing. It never contains your text or audio.
Where an install came from. The app carries no attribution SDK and no advertising identifier. If you arrived from a store link on this website or from an ad, Apple's App Analytics counts the install against that campaign link; we see totals per channel, never who you are.
Subscription state. Apphud, our subscription provider, records whether you are on trial, active or lapsed, against your account. Payment itself is Apple's; we never receive your card details.
Your account. If you sign in with Apple, we receive the identifier Apple issues and the email address you choose to share — including Apple's private relay address, if you use it. The name Apple shares stays on your device; it is never sent to us. We never receive your Apple ID password.
Support messages. If you write to us or send feedback from the app, we keep what you sent so we can reply.
Crash and error logs. Firebase Crashlytics collects technical diagnostics — device model, OS version, what the app was doing when it failed — so failures can be fixed. They never include your content.
Technical access logs. Our gateway logs the time, route and account identifier of each request, without its content. The log is rotated by size on the server, so entries are overwritten within days.

This website

For visit analytics this website uses Webvisor (webvisor.xyz), which receives the pages you view, the referring site and anonymous interaction signals such as clicks and scrolling. We checked what its script does before adding it: it sets no cookies and stores no identifier in your browser. The website sets no advertising or tracking cookies.

Why we are allowed to process this

Where data-protection law requires a legal basis, ours are:

Performing our contract with you — running the app, processing your generations, managing your subscription.
Your consent — sending requests to AI providers. It can be withdrawn by writing to us.
Our legitimate interests — understanding how the app is used so we can improve it, and protecting the Service from abuse.
Legal obligation — where we are required to keep or disclose something.

Who we share it with

Only the providers named above, each processing data on our behalf for the purpose described. We do not sell your personal information and we do not share it with advertisers.

We may disclose information if the law compels us, or to protect the rights, property or safety of our users or the public. If our business were ever sold or transferred, information could pass to the acquirer — we would say so here before that happened.

Where it goes

Our providers operate internationally, so your information may be processed outside your country, including in the United States. Where the law requires it, transfers rest on appropriate safeguards such as the European Commission's standard contractual clauses.

How long we keep it

Content on your device — until you delete it or delete the app.
Your text and audio sent for generation — not kept by us; model providers may keep a request for up to 30 days under their own policies.
Account and subscription records — while your account exists, then deleted when you delete your account.
Usage records — while your account exists; on deletion the link to you is removed.
Technical access logs — rotated by size on the server; entries are overwritten within days.
Support messages — kept while the matter is open, then a reasonable period after.

Your rights

You can ask us to confirm what we hold about you, to give you a copy, to correct it, to delete it, to restrict or object to how we use it, and to withdraw consent you have given. If you are in the EEA or UK you also have the right to complain to your data protection authority — though we would rather you told us first.

Deleting your account. You can delete your account from inside the app (Settings → Delete account). We send a deletion request to our server, which removes your account record and the subscription link held against it and unlinks your usage records; this completes shortly after you ask. You can also revoke CTR's access under Settings → Apple Account → Sign in with Apple on your iPhone. Content on your device goes when you delete the app. If you would rather we did it, write to [email protected].

Security

Keeping your content on your device removes most of the risk that a policy like this usually has to discuss — there is no library of user posts to breach. What we do hold is protected by technical and organisational measures appropriate to its sensitivity. No system is perfectly secure, and we do not claim otherwise.

Children

CTR is not directed at children. We do not knowingly collect personal information from children under 13, or personal data from children under 16 in the EEA. If we learn we have, we delete it.

Changes

If this policy changes materially — a new provider, a new category of data — we will say so in the app rather than quietly updating this page. The date at the top always shows the current version.

Contact

Akhmat Sultanov, Individual Entrepreneur, trading as App Builders Club
[email protected]