Frequently asked questions

Cookrange targets iOS 14+ and Android 8+. It’s currently being tested in internal alpha via TestFlight and Play beta and isn’t on the App Store or Google Play yet. Track current status on the download page.

There’s no exact date yet — public launch depends on feedback from the internal alpha and expanded beta stages. Follow the overall direction on the roadmap page and dated updates on the changelog. Joining the waitlist prioritizes your beta access.

Barcode scanning doesn’t run against a country-specific database. Cookrange pulls data from Open Food Facts, a global, open product database — if a product is listed there, the barcode matches; if not, no match is found. See the nutrition & planning page for details.

A squad is an accountability group where members see each other’s streaks side by side — there’s no single shared streak; if one member’s column flattens, the others see it. During beta, squads are formed via in-app invites. Read how it works on the community & squads page.

Yes. Snacks like a banana, an apple or a protein bar sit in the plan as their own layer, and you can add or remove them with a single tap; suggestions are matched to your budget rather than defaulting to an expensive “superfood.” Tap a snack and describe what you actually did to it — something like “poured chocolate sauce on the banana” — and calories and macros recalculate on the spot, without changing anything you’ve already logged. Details on the nutrition & planning page.

Not yet. The Privacy Policy describes wearable and health-platform integration as something that could be added in the future, and only with your explicit permission — not something active today. So there’s no live Apple Health, Google Fit, or smartwatch connection right now; when one ships, it won’t be on by default, it’ll ask for your permission separately. If it ships, it’ll be announced in the changelog — details on the Privacy Policy.

Marketing emails, SMS, and push notifications are entirely optional, and you can withdraw consent at any time, no reason required — from in-app notification settings, or the link at the bottom of any marketing email. Transactional notifications like account security, password resets, or subscription confirmations sit outside that consent and keep being sent as part of delivering the service. Details on the Marketing Consent notice (Turkish law).

Mobile only for now: Cookrange targets iOS 14+ and Android 8+, and is currently being tested in internal alpha via TestFlight and Play beta. There’s no separate web or desktop app described anywhere on the site; the download page will be updated with a desktop QR code once the app stores go live — so desktop access will work by pointing your phone at the code, not a browser app.

There’s no dedicated offline mode described anywhere on the site, so the cautious answer is: mostly no. Barcode scanning looks up products through Open Food Facts, a global, crowd-sourced database, and Cookrange AI runs a server-side generation whenever it updates your plan — both need a live connection. We’d recommend using it over a normal mobile data or wifi connection.

It doesn’t yet — joining the waitlist doesn’t give you a referral link or a queue position today. Signing up is a single step: your email, platform, and optional marketing consent. We’ll email you as beta slots open.

No. The health disclaimer in the Terms of Service is explicit: Cookrange is not a medical device and doesn’t provide medical advice, diagnosis, or treatment — the nutrition and training suggestions it generates are for general information and motivation only. If you have an existing health condition, are pregnant, or have a chronic illness, you should consult a health professional. Details on the Terms of Service.

Yes, the core of the app is free. Today’s free tier includes unlimited meal logging, gym check-in, squads, and long-term progress history. It also includes 2 generations a day through Cookrange AI — a shared pool covering plan regeneration, recipe generation, and chat. Premium raises that to 20 a day — see the exact price on the pricing page.

Premium purchases, billing, and cancellation aren’t handled directly by Cookrange — they run through the relevant app store (App Store or Google Play) at the time of purchase, and refund requests follow that store’s own policy. The Terms of Service don’t replace those store terms, they only sit alongside them. What Premium actually buys is explained on the pricing page and the Terms of Service.

Your data is stored on Firebase (Google Cloud infrastructure) with per-user access rules. Location-based features like nearby gym and coach ranking are computed on-device; no coordinate is ever stored on a server. See the security page and Privacy Policy for details.

By default, your gym sees its own check-in count and the last 60 days’ peak-hour pattern. You see your member list and check-in records at display-name level, and can export them as a CSV. You never get access to a member’s nutrition history, weight data or measurements. If a member chooses to, they can separately share a narrow summary with you through a tiered, default-off permission — check-in frequency, logging consistency, or the direction their weight is moving — see the full tier boundaries on the progress analytics page. For the commission model and more, see the page for gyms and coaches; for the check-in mechanism, see the gym ecosystem page.

Yes. In the app, tap “Download My Data” in Settings to export everything (meal logs, progress history, profile data and more) as a JSON file in one tap. Under the portability right described on the Data Subject Request page, you can also request it by email — KVKK-based requests are answered within 30 days, GDPR-based ones within 1 month. Details on the Privacy Policy.

You can close your account any time from in-app settings, or send a deletion request through the Data Subject Request page. Except for data under a legal retention obligation (e.g. billing records), your data is deleted or anonymized within a reasonable period — it isn’t kept around as a backup. Exact, category-by-category retention periods will be published on the Privacy Policy once finalized.

Even if a coach or gym is connected to you, they can’t read your progress by default — you turn that on yourself through a tiered, default-off permission: each tier adds to the one before (your check-in frequency, streak and last visit → plus how consistently you’re logging → plus the direction your weight is moving), your raw weight history is never shared through this path, and you can turn it off any time — the moment you do, any existing summary is deleted too. When a coach generates an AI report for you, your name and streak data are sent to our AI provider — a cross-border transfer — and today that doesn’t go through a separate consent step. Your squad only sees each other’s streak status, never nutrition history or weight. There’s no family or multi-user account plan described on the site — the Terms of Service hold the registered user responsible for keeping their account credentials confidential and for all activity under the account. Details on progress analytics and the security page.

You do. The Terms of Service say this directly: the data you enter into the app (meal logs, notes, and so on) stays your property, and Cookrange only uses it to provide the Service and for the purposes described in the Terms and Privacy Policy. That runs the opposite direction from the limited license Cookrange grants you to use its brand, code, or design. Details on the Terms of Service.