Last updated: October 2, 2026
ClipCook ("we", "our", "us") respects your privacy. This Privacy Policy explains how we collect, use, store, and protect your information when you use the ClipCook mobile application ("App").
When you sign in with Apple or Google, we receive:
We do not collect or store your password. Authentication is handled securely by Apple and Google.
When you submit a link, recipe text or a photo for AI recipe extraction, we send it to our server for processing. For public social media links we fetch the post's public content (caption, video or images) to read the recipe. The link is saved with the resulting recipe as its source. A photo you submit is saved in our cloud storage as that recipe's image and is deleted when you delete your account. We do not keep submitted recipe text after processing. For abuse prevention we also keep one-way hashes of the submitted input, as described in Section 6.
We collect anonymized analytics data to improve the App, including:
This data is collected through Firebase Analytics and Firebase Crashlytics.
Subscription status and the number of free AI recipes you have used are stored to manage your account. Payment processing is handled entirely by Apple or Google; we do not collect or store credit card or payment information.
| Purpose | Data Used |
|---|---|
| Provide & operate the App | Account info, recipes, collections |
| AI recipe extraction | Submitted links, text or photos (processed; see Section 1c) |
| Manage subscriptions & the free AI recipe allowance | Subscription status, number of free AI recipes used |
| Prevent abuse and fraud | Pseudonymous identifier derived from your sign-in ID, one-way hashes of submitted input, app attestation results, usage counters |
| Improve the App | Anonymized analytics & crash data |
| Customer support | Account info, usage history |
| Send notifications (if enabled) | Device token, preferences |
We use the following third-party services:
| Service | Purpose | Privacy Policy |
|---|---|---|
| Firebase (Google) | Authentication, database, analytics, crash reporting | Link |
| RevenueCat | Subscription management | Link |
| Apple Sign In | Authentication | Link |
| Google Sign In | Authentication | Link |
| Anthropic (Claude AI) | Recipe extraction processing | Link |
| OpenRouter (Google Gemini) | Video analysis for recipe extraction when a post has no written recipe | Link |
| Apify | Fetching the public content of social media links you submit | Link |
| YouTube Data API (Google) | Reading public details of YouTube videos you submit | Link |
| Firebase App Check (Apple DeviceCheck on iPhone, Google Play Integrity on Android) | Verifying that requests come from the genuine app | Link |
We do not sell your personal data. We only share data with:
Abuse prevention. To stop the free AI recipe allowance from being reused by deleting and re-creating accounts, we keep a pseudonymous record derived from your sign-in provider identifier with a secret key (the identifier itself is not stored). While your account is active it holds the number of free AI recipes used and, to safely handle retries, random request identifiers with one-way hashes of the submitted input (link, recipe text or photo) for unfinished requests and up to your 10 most recent successful requests. Unfinished request entries stop affecting your allowance after 3 minutes and are physically removed during the next reservation clean-up or when the record expires. To answer retried requests we also keep the full recipe of up to your 10 most recent successful AI extractions, linked to your account and deleted with it. The whole record is deleted automatically 12 months after its last update. When you delete your account, the request identifiers and hashes are removed and only the count of free AI recipes used is kept, for up to 12 months, based on our legitimate interest in preventing fraud. Records of failed links are kept for up to 2 days. You can ask us to erase this record by contacting support.
Depending on your jurisdiction, you may have the right to:
To exercise these rights, contact us at clipcook.app@gmail.com.
If you are in the European Economic Area (EEA), we process your personal data based on the following legal grounds:
If you are in the EEA, you have the following rights under GDPR:
To exercise these rights, contact us at clipcook.app@gmail.com. We will respond within 30 days.
You also have the right to lodge a complaint with your local data protection authority.
If you are a California resident, you have the following rights under the CCPA:
ClipCook is not intended for children under 13 (or under 16 in the EEA). We do not knowingly collect personal information from children. If we learn that we have collected data from a child under the applicable age, we will delete it promptly.
Your data is processed and stored in the European Union (Firebase europe-west1 region). If you access the App from outside the EU, your data may be transferred to and processed in the EU. We ensure appropriate safeguards are in place for international data transfers in compliance with GDPR.
The App does not use cookies. We use Firebase Analytics SDK for anonymized usage tracking. You can opt out of analytics tracking through your device settings.
We may update this Privacy Policy from time to time. We will notify you of material changes through the App or by email. Continued use of the App after changes constitutes acceptance. The "Last updated" date at the top indicates the latest revision.
The data controller for your personal information is:
Orcun Demir
clipcook.app@gmail.com
If you have questions, concerns, or requests regarding this Privacy Policy or your personal data, contact us at:
clipcook.app@gmail.com