ChefVoice Privacy Policy

Effective date: August 18, 2026

This Privacy Policy explains how ChefVoice (the “App,” “ChefVoice,” “we,” “us,” or “our”) accesses, collects, uses, stores, shares, and deletes information when you use ChefVoice on Android or through its web/PWA experience.

1. Information ChefVoice handles

Depending on the features you choose to use, ChefVoice may handle the following categories of information:

• Account and authentication information: email address, Firebase user ID, email-verification status, authentication/session information, and information needed for password reset and account management. Password authentication is provided through Firebase Authentication; ChefVoice does not display your password to other users.
• Profile information: display name, profile photo, cover photo, profile text or other profile information you choose to provide.
• Recipe and Community content: recipes, titles, descriptions, ingredients, cooking steps, recipe photos or videos, public ChefVoice audio clips, comments, replies, likes, bookmarks, follows, reactions, and related timestamps.
• Private communications: private conversation records and messages between ChefVoice users.
• Live cooking content: information needed to create or join live cooking sessions, live comments and reactions, and real-time media/signaling information. If you host or join a live audio/video feature, your camera and microphone content is intentionally transmitted to the other participants/viewers as part of that feature.
• Cooking-session audio: microphone recordings created when you use Cook & Capture or related voice features. Cooking-session audio can remain local on your device. If you deliberately run ChefVoice “Second Pass,” the original cooking-session audio for that recipe is uploaded to private cloud storage and processed with Google Cloud Speech-to-Text to create a transcript and timing information. This private raw session audio is not published as Community recipe media.
• Photos and video: camera or media content you create or select for profiles, recipes, or live features. Recipe/profile media is uploaded only when you use features that require cloud publishing or synchronization.
• Notifications and device/service identifiers: Firebase Installation identifiers, Firebase Cloud Messaging registration information, platform type, notification preferences, and related timestamps used to deliver and manage notifications.
• Safety and moderation information: reports you submit about users or user-generated content, report reasons/details, identifiers of the reporting and reported accounts/content, moderator notes, moderation actions, and related timestamps.
• Operational and security information: upload authorization records, service quotas/usage counters, app-integrity or attestation information, request metadata, and technical information processed by Google/Firebase services for security, abuse prevention, authentication, and reliable operation. Service providers may process information such as IP address, user agent, or device/application identifiers as part of providing these services.

2. Device permissions

ChefVoice may request the following Android permissions when needed for a feature:

• Microphone: for voice-based cooking capture, voice clips, and live audio/video.
• Camera: for recipe media, profile media, and live video features.
• Notifications: to show activity, message, follow, live-session, or other ChefVoice notifications.
• Internet: to sign in, synchronize cloud content, use Community and messaging features, upload media, run Second Pass, and receive online services.

The current Android release does not request precise location permission for ChefVoice functionality.

3. How we use information

ChefVoice uses information described above to:

• create, authenticate, verify, secure, and manage ChefVoice accounts;
• save and synchronize profiles, recipes, media, Community activity, follows, bookmarks, comments, messages, live sessions, and notification preferences;
• provide Cook & Capture, voice clips, Second Pass transcription, and live audio/video features;
• send notifications requested or enabled through ChefVoice;
• enforce upload limits and other service-protection controls;
• detect, investigate, prevent, and respond to abuse, safety issues, policy violations, fraud, and technical problems;
• process user reports and perform moderation actions; and
• maintain, troubleshoot, protect, and improve the reliability of ChefVoice.

4. Public content and information shared with other users

ChefVoice includes social and Community features. Information you intentionally publish—such as your display name, profile media, public recipes, recipe media, public voice clips, comments, replies, likes/reactions, or live-session content—may be visible to other ChefVoice users according to the feature you use.

Private messages are intended for conversation participants rather than the public. Reports submitted for safety/moderation are available to authorized moderation systems and personnel as needed to review the report.

5. Service providers and data sharing

ChefVoice does not sell personal or sensitive user data. ChefVoice uses Google/Firebase and Google Cloud services as service providers to operate the App. Depending on the feature, information may be processed by:

• Firebase Authentication for email/password sign-in, email verification, password reset, and account management;
• Cloud Firestore for account-linked profiles, Community content, messaging records, notification records, safety/moderation data, and operational records;
• Cloud Storage for Firebase / Google Cloud Storage for profile media, public recipe media/voice clips, and private cooking-session audio used by Second Pass;
• Cloud Functions for Firebase / Google Cloud for server-side account, moderation, notification, storage-authorization, and transcription workflows;
• Firebase Cloud Messaging and Firebase Installations for push notifications and installation-specific notification registration;
• Firebase App Check / Google Play Integrity for app-integrity and abuse-protection signals; and
• Google Cloud Speech-to-Text when you explicitly use Second Pass to transcribe private cooking-session audio.

ChefVoice may also disclose information when reasonably necessary to comply with applicable law, legal process, or a valid governmental request; to protect users or the public; to investigate fraud or abuse; or as part of a business transfer where legally permitted and appropriate notice is provided.

6. Advertising, payments, analytics, and location

The current ChefVoice release source does not include an advertising SDK, Google Play Billing flow, or Firebase Analytics dependency, and it does not request Android location permission. ChefVoice does not use the information described in this policy to sell personal data or to provide targeted advertising.

7. Local data

ChefVoice can keep Cook & Capture recipes and related cooking data locally on your device. Local information is separate from your cloud account and may remain on the device when you sign out or delete your cloud ChefVoice account. You can remove local data using the controls provided by your device/App where available, or by clearing/uninstalling the App, subject to the behavior of your Android device.

8. Data retention

ChefVoice keeps cloud information for as long as reasonably necessary to provide the relevant feature, maintain the account, satisfy user choices, protect the service, or meet legitimate legal, safety, and security needs.

• Cloud account/profile information is generally retained while your ChefVoice account remains active.
• Published recipes and their cloud media remain until they are deleted, unpublished through moderation where applicable, or removed through account deletion.
• Private cooking-session audio stored for a recipe is removed when that cloud recipe is deleted or when the ChefVoice cloud account is deleted.
• Notification-device records are removed from the signed-in account during sign-out when the installation record is available, and are also removed as part of account deletion.
• Operational quota/security records are retained only as needed for service protection and are removed with the account where they are stored under the user account.
• Safety/moderation reports may be retained after account deletion when needed for safety, abuse prevention, or moderation history. When a ChefVoice account is deleted, the deletion workflow replaces that deleted account’s direct user identifier in retained reports with a pseudonymous deleted-account identifier.

9. Account and data deletion

ChefVoice provides an in-app account-deletion function. For security, you may be required to sign in again before completing permanent cloud-account deletion.

When a ChefVoice cloud account is deleted, the server-side deletion workflow removes the Firebase Authentication account and associated cloud profile data, user-owned recipes and cloud media, private cooking-session audio, social relationship records, applicable comments/replies and activity records, private conversations involving the deleted account, hosted live-room records, known notification/device records, and other known private user subcollections. Safety/moderation reports may be retained in pseudonymized form as described above.

Local Cook & Capture data stored only on your device is not automatically deleted when the cloud account is deleted.

To request account/data deletion outside the App, visit the ChefVoice Account Deletion page or contact REPLACE_WITH_PRIVACY_CONTACT_EMAIL.

10. Security

ChefVoice uses security controls including authenticated access, email-verification gates for certain cloud features, Firebase Security Rules, scoped upload authorization, media validation, HTTPS/encrypted network transport, app-integrity monitoring, and access controls for private content. No method of electronic storage or transmission is guaranteed to be completely secure, but ChefVoice is designed to limit access and processing to the functionality described in this policy.

11. Your choices

Depending on the feature, you can choose whether to create an account, publish Community content, upload profile/recipe media, enable notifications, use camera or microphone features, use Second Pass, participate in live sessions, or submit reports. Android permission controls can be changed in your device settings. You can also delete individual cloud recipes and use the in-app account deletion flow.

12. International processing

ChefVoice relies on Google/Firebase cloud infrastructure. Your information may therefore be processed in countries other than the country where you live, subject to the safeguards and legal requirements applicable to the relevant service and jurisdiction.

13. Changes to this policy

We may update this Privacy Policy when ChefVoice features, data practices, service providers, or legal requirements change. The effective date at the top of this page will be updated when the policy changes materially.

14. Contact

ChefVoice is the application covered by this Privacy Policy. The developer identity is the developer identified for ChefVoice in its Google Play listing.

For privacy questions, requests, or account/data deletion inquiries, contact: REPLACE_WITH_PRIVACY_CONTACT_EMAIL