Last updated: October 6, 2026
Tericipe is developed and operated by Hess WebTech, LLC ("Hess WebTech," "we," "us," or "our"). This Privacy Policy explains what information Tericipe (the "App") collects, how we use it, who we share it with, and the choices you have.
If you have questions about this policy or your data, contact us at info@hesswebtech.com.
We collect only what the App needs to function. Specifically:
Account information. When you create an account, we collect your name, email address, and password. Authentication is handled by Firebase Authentication (a Google service); we never see or store your password in plain text — Firebase manages it on our behalf. We use your email to verify your account and to let you sign back in.
Profile information. Your display name and, if you choose to add one, a profile photo. Profile photos are selected from your device's photo library. Where the photo is stored depends on whether you have purchased Tericipe Pro — see "Photos and where they are stored" below.
Your recipes and collections. Any recipe you create, scan, or save — including titles, descriptions, ingredients, steps, cooking time, servings, category, and any photos you attach — plus any collections you organize them into. This content is stored in our cloud database (Firestore) under your account and is private to you by default; it is never visible to other users unless you explicitly use the Share feature (see Section 5).
Storage of collected information. If you have not purchased Tericipe Pro, your profile photo and your recipe and collection photos are stored as local files on your own device, and thus won't appear if you sign in on a different device. If you have purchased Tericipe Pro, your profile photo and your recipe and collection photos are also uploaded to our cloud file storage (Firebase Cloud Storage) under your account and will appear if you sign in on a different device. All other content stored by the App is stored in our cloud database (Firestore) under your account.
Photos and where they are stored. Recipe photos, collection cover photos, and your profile photo are treated the same way, and the difference is Tericipe Pro:
Uploading only happens after you save the recipe or profile change, and only for accounts that own Tericipe Pro; if an upload fails, the App retries it later and your photo stays on your device in the meantime. Photos stored this way are private to your account — our security rules permit only your signed-in account to read or write them, and we do not include photos in shared-recipe links (see Section 5).
Camera and photo library access. The App requests camera access so you can photograph physical recipes to scan them or take a photo for a recipe, and photo library access so you can choose a profile photo or a photo for a recipe. We only access these when you actively use the scan, recipe-photo, or profile-photo features — the App does not access your camera or photos in the background.
Scanned recipe text. When you scan a recipe, the photo is processed entirely on your device using Google's ML Kit on-device text recognition. The photo and the recognized text are not sent to any server for this processing — recognition happens locally on your phone.
Scan history (on-device diagnostics). To help you re-check a recent scan and to help us improve recognition quality, the App keeps a short local log of your most recent scans (currently the last 10) — the recognized text plus the captured photo(s). This log is stored only on your device, is never uploaded to our servers, and you can view or clear it from Profile → Scan history. From that screen you may choose to export a scan's diagnostic data (its text and photo(s)) using your device's standard share sheet; if you do, it goes only to the destination you pick — the App does not send it anywhere on its own.
Printing and PDF export (Tericipe Pro). If you own Tericipe Pro, you can print a recipe or save it as a PDF. The printout is generated on your device from the recipe's title, description, details, ingredients, steps, source and, if one is stored on the device, its photo; it does not include your name or email address. When you choose to share the PDF, it goes only to the app, person or printer you pick from your device's share sheet; the App does not send it to us or anyone else. A copy of the shared PDF stays in the App's temporary cache on your device, which your device clears over time and which is removed if you uninstall the App; sharing the same recipe again replaces it.
App verification (anti-abuse). To protect our backend from abuse, the App uses Firebase App Check: when the App calls our servers (for example, when you publish a share link), it attaches a short-lived token proving the request comes from a genuine copy of the App. Producing this token involves an attestation exchange with Firebase (Google). Once the App is distributed through Google Play, this attestation will use Google's Play Integrity service, which evaluates your device and app install to produce an integrity verdict — Google processes device signals for that purpose under its own terms; we receive only the resulting attestation, not your device's contents.
Purchase information (Tericipe Pro). If you buy Tericipe Pro, the purchase is handled entirely by Google Play Billing. We never see or receive your payment details — no card number, billing address, or similar information ever reaches us or is stored by us; Google processes the payment under its own terms. What we receive from Google is a purchase token identifying the transaction, which our server checks with Google to confirm the purchase is genuine. We then store, under your account: a record that your account owns Tericipe Pro, the Google Play order identifier, when the purchase was made, and a one-way (hashed) form of the purchase token used to recognise the same purchase again. We keep that so you can restore your purchase after a reinstall or on a new device.
Information we do not currently collect. As of this version of the App, we do not collect analytics or usage data, crash reports, or advertising identifiers, and the App contains no third-party advertising. As described above, we do not collect or store payment card details. If we add any of these in the future (for example, crash reporting or product analytics), we will update this policy before doing so and describe what's collected, why, and how you can control it.
We use the information above to:
We do not sell your information, and we do not share it with third parties for their own marketing purposes.
We use the following service providers to operate the App:
We do not otherwise sell, rent, or share your personal information with third parties, except:
The App lets you generate a share link for a recipe you own. That link resolves to a public web page, so the recipe can be viewed by someone who doesn't have the App installed. Anyone who has that specific link can view that recipe's content, without signing in.
When you open the Share screen for a recipe, a copy of that recipe is published to a public area of our database and kept up to date the next time you share it. The public copy contains only:
The public copy never includes your recipe photos, your last name, your email address, your account details, or which collections the recipe belongs to.
Shared links are not listed in any public directory in the App or on our website, and the share page asks search engines not to index it — but we can't control what happens to a link after you send it, so treat a shared link like the recipe itself: anyone it's forwarded to can open it.
The public copy stays available until it is removed. You can remove it yourself at any time: open the recipe's Share screen and choose "Stop sharing" — the public copy is deleted and the link stops working for everyone. Sharing the recipe again later creates a new link; old copies of the removed link stay dead. You can also email us at info@hesswebtech.com and we will remove a shared copy for you. Deleting your account (Section 6) also covers removal of your shared copies.
We retain your account and recipe data for as long as your account is active. You can delete your account and all associated data yourself, at any time, from Profile → Delete account. For your security this asks you to re-enter your password, then permanently removes your account, all of your recipes and collections, any photos stored in the cloud for your account, and any recipes you had shared by link (the public links stop working). This is immediate and cannot be undone.
Deleting an individual recipe, or removing its photo, also deletes the photo's cloud copy, but on a best-effort basis: if that deletion doesn't happen (see "Photos and where they are stored" in Section 2), the copy remains in your account's cloud storage until you delete your account, which always removes it.
Deleting your account does not cancel or refund a Tericipe Pro purchase — that purchase belongs to your Google Play account, not to your Tericipe account, and refunds are handled by Google Play. If you create a new Tericipe account later on the same Google Play account, you can restore Tericipe Pro to it. You can also email us at info@hesswebtech.com to request deletion. In either case we may retain certain records where required to by law.
A cached copy of your recipes/collections/profile may also be stored locally on your device (used only to keep the App usable when you're briefly offline). This local cache is tied to your device and account, is cleared when you sign out, delete your account, or uninstall the App.
The on-device Scan history (see Section 2) keeps only your most recent scans (currently the last 10); older entries and their photos are automatically deleted as new scans replace them, and the whole log is removed when you uninstall the App.
Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can:
Depending on your state of residency, you may have certain rights related to your personal information, including:
The exact scope of these rights varies by state. There are also several exceptions where we may not have an obligation to fulfill your request.
To exercise any of these rights, please contact us at info@hesswebtech.com.
If you are a California resident, you have additional privacy rights under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA). This section provides information about those rights and how to exercise them.
Personal information we collect. We collect information that identifies, relates to, describes, references, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household ("personal information"). The categories of personal information we have collected from consumers within the last 12 months include:
We do not collect sensitive personal information as defined by the CCPA.
Sources of personal information. We obtain personal information from the following categories of sources:
How we use personal information. We use the personal information we collect for the business and commercial purposes described in Section 3 of this Privacy Policy, including to:
Disclosure of personal information. We may disclose personal information to service providers and contractors for business purposes as described in Section 4 of this Privacy Policy. We do not sell or share your personal information as those terms are defined under the CCPA.
Your California privacy rights. As a California resident, you have the following rights:
How to exercise your California rights. To exercise your rights to know, delete, or correct, please submit a request by emailing us at info@hesswebtech.com.
We will verify your identity before processing your request. You may only submit a request to know twice in a 12-month period. We will respond to verifiable requests within 45 days of receipt, or notify you if we require additional time (up to 90 days total).
Only you, or someone legally authorized to act on your behalf, may make a request related to your personal information. To designate an authorized agent, please provide written authorization signed by you and the agent.
Tericipe is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13. If we learn that we've collected personal information from a child under 13, we will delete it. If you believe a child under 13 has provided us with personal information, contact us at info@hesswebtech.com.
We rely on Firebase's security infrastructure, including encryption in transit, and Firestore and Cloud Storage security rules that restrict every user's data to that user's own account.
How cloud-stored photos are addressed. When a photo is uploaded for a Tericipe Pro account, Firebase generates a long, unguessable web address for it, and that address is saved privately in your own recipe or profile record. Retrieving the address requires being signed into your account. Anyone who obtained the address itself could open the image without signing in, in the same way a shared-recipe link works — so the address is treated as private data and is never included in shared recipes or shown to other users.
No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
Our service provider (Firebase/Google Cloud) may process and store data in the United States or other countries where Google operates infrastructure. By using the App, you understand that your information may be transferred to and processed in a country other than your own.
We may update this Privacy Policy from time to time, particularly as we add new features (such as analytics, crash reporting, cloud photo storage, or monetization). We'll update the "Last updated" date above, and for material changes we'll provide additional notice (such as an in-app notification) before the changes take effect.
Questions, requests, or concerns about this policy or your data:
Hess WebTech
Email: info@hesswebtech.com