Privacy Policy
Effective Date: March 14, 2026
We at TailTalk LLC ("we," "us," "our") value your privacy. This Privacy Policy explains how we collect, use, and share information when you use My Kitchen ("the App").
1. Information We Collect
Authentication Data
If you choose to sign in, we collect:
- Your phone number, used solely for SMS verification via Firebase Authentication.
- Your Apple ID credential, if you sign in with Apple, processed via Firebase Authentication.
- A display name you provide, stored in your account profile and household membership records.
Content You Create
- Recipes, ingredient lists, and recipe-ingredient associations you create.
- Images you upload for recipes, stored locally on your device and in Firebase Storage when signed in.
Guest Usage
If you use the app without an account, all recipe and ingredient data is stored locally on your device only and is never transmitted. However, the app initializes RevenueCat at launch for subscription infrastructure purposes — no personal data is transmitted in this process. APNs registration also occurs at launch as part of phone number authentication infrastructure.
Automatically Collected Data
We use Firebase Crashlytics to collect crash reports in production builds only. Crash reports may include your device model, iOS version, app version, and a stack trace of the crash. Crash reports do not include your name, phone number, recipes, or any personal content. We do not collect analytics or usage telemetry, and we do not use advertising SDKs. Your device registers for push notifications solely to support phone number verification — we do not send marketing or promotional notifications.
2. How We Use Your Information
- To provide the app: Your recipes, ingredients, and images are stored and synced so you can access them across devices when signed in.
- Phone verification: Your phone number is used only to verify your identity during sign-in via SMS. It is not used for any other communication.
- Household features: Your display name is visible to other members of households you join or create. Recipes and ingredients you share to a household are visible to all current members.
- Subscription management: We use RevenueCat to manage your subscription status and entitlements. See Section 3 for details on what data is shared with RevenueCat.
- To improve the app: We do not collect usage analytics. Improvement is based on direct user feedback only.
3. Data Sharing
- Firebase (Google): We use Firebase Authentication, Firestore, Firebase Storage, and Firebase Crashlytics — all provided by Google — to store and sync your data securely and to collect crash reports for improving app stability. Crash data collected by Firebase Crashlytics includes device model, iOS version, app version, and crash stack traces; it does not include your name, phone number, recipes, or personal content. Crash collection is enabled in production builds only. Your data is transmitted to and stored on Google's infrastructure subject to Google's privacy terms. You can review Firebase's privacy practices at firebase.google.com/support/privacy. You can request deletion of crash data by deleting your account within the app or by contacting us.
- RevenueCat: We use RevenueCat to manage subscription status and entitlements. When you initiate a purchase, your anonymous app user ID and Apple purchase receipt are shared with RevenueCat. RevenueCat does not receive your name, phone number, or personal contact information. Apple processes all payment transactions — neither TailTalk LLC nor RevenueCat has access to your payment card details. You can review RevenueCat's privacy policy at revenuecat.com/privacy.
- Household members: Recipes and ingredients you explicitly share to a household are visible to all current members of that household. Household recipes and ingredients are stored in Firebase Firestore and are accessible to all current members of the household. When you join a household, you can view and contribute to all shared recipes and ingredients.
- Apple: If you sign in with Apple, your credential is processed by Apple and Firebase. We do not receive or store your Apple email address unless you choose to share it.
- No data sales: We do not sell, rent, or trade your personal data to any third party.
- Legal requirements: We may disclose information if required by law or valid legal process.
4. Data Security
We use commercially reasonable measures to protect your information. However, no method of digital storage or data transmission is 100% secure, and we cannot guarantee absolute security.
5. Retention of Data
Your data is retained as long as your account is active. If you delete your account within the app, we will delete your personal Firestore data and associated images from Firebase Storage. Your Firebase Authentication record is also permanently deleted.
Note: If you are the creator of a household at the time of account deletion, that household and all its data will be dissolved. If you are a member of a household, you will be removed from it — the household and its shared content will remain accessible to other members.
Local data on your device is deleted upon sign-out or account deletion.
6. Children's Privacy
My Kitchen is not directed to children under the age of 13 (or the applicable age of digital consent). We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us immediately.
7. Your Rights and Choices
- Access and update: You can update your display name within the app at any time.
- Delete account: You can permanently delete your account directly within the app in the Profile tab. This will delete your authentication record, all personal recipes and ingredients stored in the cloud, and all associated images. This action is irreversible.
- Guest usage: You may use the app without an account at any time. Guest data is stored only on your device.
- Data portability: We do not currently provide data export. You can view all your data within the app at any time.
8. Permissions We Request
- Photo Library: Used only to let you select images for your recipes. We do not access any photos beyond what you explicitly select.
- Camera: Used only to let you take photos for your recipes. We do not access your camera at any other time.
- Push Notifications: Used exclusively to support phone number verification during sign-in. We do not send marketing, promotional, or any other push notifications.
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will post the new policy and update the "Effective Date" above. Your continued use of My Kitchen after we post any changes indicates your acceptance of those changes.
10. Contact Us
If you have any questions about this Privacy Policy, please contact us at: