Privacy Policy

1. Information we process

Browsing, scaling, and saving favorites do not require an account. A guest account is created when you first rate, report, or block in the app. Online requests still involve technical information.

• Accounts: Firebase Authentication processes a unique account reference, email, authentication credentials, email-verification status, and account/sign-in timestamps. If you choose Google or Apple, those providers authenticate you and share account identifiers and an email address (which may be an Apple private relay address). Provider profile information may be held by the authentication service, but public authorship uses your separately chosen unique username. We store the username and its account reservation privately until you contribute. We do not receive your Google or Apple password. Guest sessions use a randomly assigned reference without requiring a name or email.
• Ratings: recipe, star value, account or guest reference, and update time. Public files show aggregate counts and averages, not a list of individual voters.
• Contributions: submitted recipes or comments, account reference, username, submission time, moderation status, and review information. Approved content and author names become public.
• Community safety: your reports, reasons, optional details, the reported content or author, account reference, moderation outcomes, and blocked-author preferences. Reports and block lists are private. Public author references let the app apply a block without exposing a private sign-in identifier.
• Account deletion: a temporary deletion job and hashed recovery receipt let us finish an accepted request and show its status even after sign-in is disabled. Apple authorization codes or access tokens are used only to revoke that authorization; they are not published or written to application logs.
• Operation and abuse prevention: request times, account-based usage counters, error information, and provider logs that may include IP address, user agent, device/browser details, and requested URLs.
• Sign-in components: Google’s iOS sign-in component declares processing of name, email, phone number, approximate location, user and device identifiers, usage information, and other authentication data for sign-in functionality and service analytics. Google may estimate approximate location from an IP address for fraud prevention. The app does not ask you to enter a phone number or grant location permission. These provider records are separate from your public recipe username.
• Support: your email address, message, and information you choose to send us. Do not send passwords, sign-in codes, or unnecessary medical information.

2. Information stored on your device

The app saves favorite recipe references, appearance and water/ingredient unit preferences, selected container size, downloaded public recipes and comments, authentication session information, a cached block list for the current account or guest session, and a temporary deletion recovery receipt locally. Favorites and preferences are not synced to an email account. Browser or app storage keeps information between visits. Your device or backup provider may retain copies according to its settings. Clearing storage may remove favorites and the link to guest activity; it does not delete server records.

3. How we use information

We use information to provide sign-in, process and update ratings, review and publish contributions, show your submission status, distribute public content, process safety reports, apply blocks, protect against abuse, investigate errors, fulfill deletion requests, answer requests, and meet legal obligations. Where a legal basis is required, we rely on providing the requested service, legitimate interests in service operation and security, legal obligations, or consent where applicable.

The current app has no advertising SDK, behavioral advertising, general usage analytics SDK, or health-sensor collection. Authentication providers and hosting services can still process service analytics and technical diagnostics as described above. It does not request your precise location, contacts, microphone, or photo library. We do not sell personal information or use it for cross-app targeted advertising.

4. Public contributions

Approved recipes and comments, usernames, public author references used for reporting and blocking, and aggregate ratings are shared in publicly accessible downloadable files. Anyone may view, copy, or save them without signing in. Email addresses and private account references are not included in these public files. Do not put private information in your username or contributions. Pending or rejected contributions are available to authorized operators and the submitting account, not the public catalog.

5. Service providers and other disclosures

Google and Apple process optional provider sign-in under their own privacy policies. Google Firebase and Google Cloud provide authentication, databases, hosting, file delivery, and server functions. Email providers process support correspondence. These providers process information to supply their services, including necessary network and security records. We may disclose information to comply with law, protect rights or safety, address abuse, or as part of a business transfer subject to applicable safeguards.

6. Amazon and external links

Optional shopping links pass through our server to the current retailer destination and may contain an affiliate tag identifying Electrolyte Chef. The redirect does not attach your account reference, email, or username. Our hosting providers can process ordinary request information when you use the link.

After you open Amazon or another external service, that service handles your visit, cookies, purchases, and related information under its own policies. We do not process your payment details or operate the retailer's checkout. As an Amazon Associate I earn from qualifying purchases.

7. Retention and deletion

We retain account records, ratings, contributions, and moderation information while needed to run the service or until a verified deletion request is fulfilled. Public content remains published until removed. Operational counters and service logs have separate purposes and may remain until removed or their provider retention period ends. We retain support, legal, security, and request records only as reasonably necessary for their purposes.

Start account deletion in Account using Delete my account (or Delete guest data). Registered users sign in again before confirming. An accepted request runs automatically and is retried if interrupted; the app distinguishes a pending request from completed deletion. You can also request account or selected-data deletion by email. We verify support requests before acting and aim to complete verified support requests within 30 days, subject to applicable legal deadlines and permitted exceptions; we will explain a necessary extension. The deletion page describes what is removed and possible retention. Provider backups, cached public files, and copies saved by others may remain beyond removal from active systems.

8. Your choices and privacy rights

You may browse without registering, avoid posting publicly or opening retailer links, change local favorites, and contact us about your information. Depending on your location, you may have rights to access, correct, delete, obtain a copy of, restrict, or object to processing, withdraw applicable consent, or appeal our response. We may need to verify identity and legal exceptions may apply. We do not discriminate for exercising applicable rights. You may also contact your relevant privacy regulator.

9. Security and processing locations

We use access controls and encrypted network connections to protect information. No service or device is completely secure. Protect your credentials and avoid posting sensitive information. Nexceed is based in the United States; providers may process information in the United States or other countries, subject to applicable law and safeguards.

10. Children’s privacy

Electrolyte Chef is not directed to children under 13, and we do not knowingly collect personal information online from children under 13. Contact us if you believe a child has provided information so we can review and delete it as required. Account eligibility does not establish that any recipe is appropriate for a child.

11. Changes and contact

We will update the effective date when practices or this Policy change and provide additional notice when required. For privacy questions or requests, contact Nexceed, LLC, Austin, Texas, at the email below.