Privacy Policy
Effective July 13, 2026
This policy explains how Zapappy LLC (“Zapappy,” “we,” or “us”) handles information across zapappy.com and Zapappy services. Product-specific details for Zapappy Cooking appear in a separate section below.
All Zapappy services
Information we collect
- Messages: if you contact us, we store the name, email address, and message you submit. We also use a limited request identifier and timestamp to prevent spam.
- Technical information: our servers and service providers receive ordinary request information such as IP address, browser details, requested pages, timestamps, and diagnostic logs.
- Account information: when a Zapappy service offers sign-in, we may receive identifiers and basic profile information needed to operate and secure your account.
- Information you provide: we process content, settings, preferences, and other information you choose to submit to a Zapappy service.
- Donations: Stripe processes donation checkout and payment details. We do not directly receive or store your full payment-card number.
Cookies and browser storage
Zapappy does not currently use advertising cookies, analytics cookies, or behavioral-tracking cookies. Ordinary visits to the main Zapappy website do not cause Zapappy to set a first-party cookie.
We use browser local storage for functional purposes. Local storage is not a cookie, but it allows information to remain on your device between visits. The main website stores the time of a successful contact-form submission to enforce a cooldown and reduce spam.
Some optional features rely on essential cookies set by service providers. Clerk may use authentication and session cookies when you create an account or sign in to a Zapappy service. Stripe may use cookies when you visit its hosted donation checkout. These cookies support the feature you requested and are not used by Zapappy for advertising.
You can remove cookies and local storage through your browser settings. Blocking essential cookies may prevent account sign-in or payment checkout from working, and clearing local storage may reset preferences saved only on that device.
How we use information
We use information to provide and secure Zapappy services, authenticate accounts, save supported preferences, display content you choose to publish, process donations, respond to messages, prevent abuse, diagnose problems, and improve our products.
Service providers and sharing
We share information only as needed with providers that help operate Zapappy, such as authentication, payment, hosting, database, storage, email, security, and content-delivery providers. These providers handle information under their own terms and privacy policies.
We may also disclose information when required by law, to protect users or the service, or as part of a merger, financing, acquisition, or sale of assets. We do not sell personal information.
Storage, retention, and security
Local app data remains in your browser until you clear it or the app removes it. Server-side information is retained while needed to provide the service, meet legal obligations, resolve disputes, and protect the service. No storage or transmission system is completely secure.
Your choices
You can use many features without an account, clear local data through your browser, and edit or remove supported account content. To request access, correction, or deletion of other personal information, contact us through the form on the About page. We may need to verify your request.
Children
Zapappy services are not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Changes
We may update this policy as the service changes. We will post the revised policy here and update its effective date.
Contact
Privacy questions and rights requests may be sent to Zapappy LLC through the contact form on the About page.
Zapappy Cooking
The following details apply specifically when you use Zapappy Cooking, in addition to the universal policy above.
Cooking browser and account data
Cooking uses local storage to save favorites, pins, pantry and shopping items, timers, checked items, recipe modifications, language, display settings, and similar app state on your device. If you sign in, profile choices, custom recipes, favorites, and other supported app state may also be stored in our database and synced across sessions. Clerk may use essential cookies to keep your Cooking account session active.
Authentication and infrastructure
Clerk processes sign-in identity for Cooking. We receive identifiers and basic profile information needed to operate the account. Cooking also relies on Railway and PostgreSQL infrastructure for hosting and data storage, Tigris for public image delivery, Stripe for donations, and content-delivery providers used to load app software.
Public Cooking contributions
Reviews and recipes you choose to publish may display your chosen name, avatar, profile description, rating, review text, and recipe content publicly. You can unpublish supported custom recipes and delete your own reviews using the controls provided in Cooking.