Your privacy choices

We would like to measure how Receitz is used and whether our ads bring people here. Both are off unless you turn them on. Signing in, saving and sharing recipes, scanning, and subscribing work either way.

Read our Privacy Policy

We also keep the cookies and records needed to run Receitz securely. Those cannot be switched off, and you can change these choices at any time from the Privacy choices button.

Public

salad

lunch

vegan

Lemon Chickpea Cucumber Salad

A refreshing chickpea salad with cucumber, lemon zest, and parsley.

4 servings Prep 15 min Cook 0 min

From: Original AI-assisted recipe; AI-generated dish image.

Ingredients

Applies while you are on this page.

Ingredients

•2 cans chickpeas (15 ounces each), drained and rinsed
•1 English cucumber, diced
•1/4 red onion, finely diced
•1/3 cup chopped parsley
•3 tablespoons olive oil
•3 tablespoons lemon juice
•1/2 teaspoon dried oregano
•1/2 teaspoon salt
•1/4 teaspoon pepper
•1 teaspoon lemon zest

Instructions

1Combine chickpeas, cucumber, onion, and parsley in a large bowl.
2Whisk oil, lemon juice, oregano, lemon zest, salt, and pepper.
3Pour dressing over salad and toss thoroughly.
4Rest 10 minutes for the flavors to mingle, then serve or refrigerate.

Privacy Policy

Effective date: October 24, 2026

Receitz is operated by DigBI LLC ("we," "us," or "our") at receitz.app. This Privacy Policy explains what information we collect, why we collect it, how we process and share it, and the choices available to you.

Receitz allows you to save and organize recipes, scan recipes using artificial intelligence, and share recipes with others.

1. Information we collect

Sign-in and account information

You can sign in using Google, Facebook, or Apple. Depending on your chosen provider and the information it makes available with your permission, we receive:

A unique account identifier used to recognize you when you sign in.
Your email address, including an Apple private relay address if you choose to hide your email.
Basic profile information, such as your name and profile picture, when provided.

For Google sign-in, we request the openid, email, and profile permissions. These allow us to identify your Google account and receive your email address and basic profile information.

We do not receive your Google, Facebook, or Apple password.

We also collect the name and other account information you provide directly within Receitz.

Recipes and uploaded content

We collect content you submit or save, including recipes, recipe boxes, notes, and images or other recipe material you submit for scanning.

Uploaded content may contain personal information, such as names or handwritten notes. Any information visible in material you submit for scanning may be processed along with the recipe.

Support communications

If you contact us, we receive your contact details and the information you include in your message.

Technical information

Our service and hosting infrastructure may collect IP addresses, browser and device information, request timestamps, error reports, and activity logs needed to operate the service, diagnose problems, and protect against unauthorized access or abuse.

Usage analytics and diagnostics

Receitz uses the usage analytics built into Base44, the platform it runs on, to understand how the app is used and to keep it working. That covers page visits and feature interactions, for example a completed AI recipe scan, a checkout that was started, or an opened shared recipe link, together with technical details of the session such as the IP address the request came from, browser and device information, and when the events happened. These records are made only if you switch usage analytics on: until then the app's own events, the platform's usage telemetry and the page and session information described here are all switched off.

When it is on, a record is connected to the session it came from, so it is not anonymous. What we ask the analytics service to record is still limited to counts, flags and short labels: we do not send recipe text, recipe titles, recipe photos, or account identifiers as analytics details. The mobile app shows these same web pages inside the app, so the same choice applies there.

Records we keep in order to run the service securely, such as sign-in records, security events and error logs, are separate: they are kept whether or not you switch analytics on, and they are not used to measure how the app is used.

2. How we use information

We use information for the following purposes:

Authentication: Verify your identity, create your account, and maintain your signed-in session.
Account management: Associate your recipes and preferences with the correct account.
Recipe storage: Save, organize, retrieve, and display your recipes and recipe boxes.
AI recipe scanning: Process submitted recipe material and convert it into recipe content you can review and save.
Sharing: Display recipes you choose to share, together with your provided name.
Support: Respond to questions and help resolve account or service issues.
Security and operation: Troubleshoot errors, maintain reliability, and detect or prevent misuse.
Legal obligations: Respond to valid legal requests and meet applicable legal requirements.
Analytics: Understand which parts of Receitz are used, including page visits, completed AI recipe scans, opened shared recipe links, and checkouts that were started.
Advertising measurement: Measure whether our advertising brings people to Receitz and which campaigns lead to sign-ups or paid subscriptions.

3. Google user data

We use the information received through Google sign-in as follows:

Google account identifier. Recognize your account and connect you to your saved content.

Email address. Identify and manage your account and communicate about account or support matters.

Name and profile picture, when supplied. Populate basic profile information.

Google sign-in does not give us access to your Gmail messages, Google Drive files, Google Calendar, or Google contacts. We do not request permission to access those services.

Google sign-in information is collected for authentication and account functionality. Recipe scanning processes the material you submit to that feature; it does not obtain recipe content from your Google account.

We do not sell Google user data or use it for advertising.

Receitz' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements where applicable.

4. AI recipe scanning

When you use recipe scanning, the images, text, or other recipe material you submit are processed using artificial intelligence to identify and structure recipe information, such as ingredients and instructions.

This processing involves transmitting submitted material to the AI services used by the application. Base44 and applicable AI service providers process that material as needed to deliver the scanning feature.

The processing may include personal information appearing within your uploaded material. Submit only material you want processed by this feature.

The resulting recipe information is returned to the application for you to review and save. AI results can contain errors, so you should review them before use.

5. Storage and service providers

Receitz is built on Base44. We use Base44 to support the application's operation, including hosting and storage of application data. For more information, see the Base44 Privacy Policy .

Account information and recipe content are processed through the application's supporting infrastructure. Base44 and other providers involved in delivering particular features may process information needed to perform those services, including authentication, storage, AI scanning, security, advertising measurement, and payment processing.

Two of those providers are worth naming here. Google receives the advertising measurement described in section 7, and Stripe handles subscription payments as described in section 8.

We use reasonable technical and organizational measures to protect information. No internet transmission or storage system can be guaranteed completely secure.

6. When information is shared

Recipes you choose to share

Recipes are private by default. You can make recipes available to others by marking them public, sharing a recipe link, or using sharing features for friends and family.

When you share a recipe, the name you provided is visible to people who can view that recipe. Depending on the sharing option you choose, the audience may include the public, people with the link, or members of your sharing group.

Others may retain copies of information you have shared.

Service providers

We share information with providers supporting the application, including Base44, sign-in providers, and the AI services used for recipe scanning, as needed to deliver the relevant functionality.

Legal and security purposes

We may disclose information when reasonably necessary to comply with applicable law or a valid legal request, investigate misuse, or protect the rights and safety of users and others.

Business transfers

Information may be transferred in connection with a merger, acquisition, or sale of the business, subject to applicable law and the protections described in this policy. Where Google's Limited Use requirements apply, any transfer subject to those requirements will comply with them, including obtaining prior consent when required.

We do not sell your personal information.

7. Advertising measurement (Google Ads)

We advertise Receitz online, and we measure whether that advertising brings people to the app. To do this, our website and app load Google's advertising tag, which is part of Google Ads, on their pages.

A conversion is reported to Google at three moments: a new account completing sign-up, a member starting a paid checkout, and a paid subscription being confirmed as paid. Each report says which moment it was and which of our advertising tags it belongs to. The sign-up report also carries an account reference Receitz generates, which is not a Google identifier; the name, email address, profile picture and Google account identifier we receive through Google sign-in are not included in these reports. The subscription reports carry the subscription value and currency (US dollars), and the paid-subscription report also carries the reference of the checkout that paid for it. We do not include recipe content or photos in these conversion reports.

Google's tag also uses cookies and similar technologies and reads advertising identifiers, such as the click identifier added when an ad is clicked, together with the IP address, browser and device information, and the page address. That is what allows Google to connect a sign-up or purchase to the campaign that led to it. Google processes this under its own policies: Google Privacy Policy and How Google uses information from sites that use its services . It also describes its responsibilities when handling data for businesses at https://business.safety.google/privacy/ .

We use this only to measure and improve our advertising. We do not use Google's advertising products to display ads inside Receitz, and the information we receive from Google sign-in is not used for advertising.

Our pages are used wherever the app is opened, including inside our mobile app, which displays those same web pages. The two subscription reports describe web checkout only: subscriptions are purchased through checkout on the web, and the Android app has no checkout or in-app purchasing, so neither a checkout-start nor a paid-subscription report is sent for activity in the Android app. A sign-up report is not tied to a purchase, so it can also be sent when a new account is created in the mobile app.

The Google tag is fetched only after you switch advertising measurement on. Until then no Google script is loaded and no measurement request is sent to Google at all, not even a cookieless one. Switching it on grants ad_storage and ad_user_data only: ad_personalization stays denied, because we do not run remarketing or build advertising audiences, and the tag is not given analytics_storage, because these pages carry no analytics product of Google's.

Switching advertising measurement off tells Google to stop at once and clears the advertising cookies it set on our site, and the page is rebuilt without the tag. We honor the Global Privacy Control signal: when your browser sends it, advertising measurement stays off whichever option you choose. A choice is kept for 180 days, after which we ask again and measurement stays off until you answer.

8. Payments and subscriptions

Paid Receitz Plus subscriptions are processed by Stripe, our payment provider. When you subscribe, your payment details are entered on Stripe's checkout page and are received by Stripe. We do not receive or store your full card number.

We keep a subscription record in Receitz: the plan, its status (such as active, trialing, canceled or expired), the billing interval, the price and currency, the current billing period, and references that connect that record to the billing provider, including the identifiers Stripe uses for the customer, the subscription and the price, and the identifier of the most recent billing event. We use it to keep your access to the plan you paid for in step, to handle renewals, cancellations and refunds, and to answer billing questions.

Stripe's privacy policy is available at https://stripe.com/privacy .

9. Cookies and session information

We use cookies or similar technologies to maintain sign-in sessions, support authentication, remember preferences, and protect the service. Depending on the features you use, this can include local storage in your browser.

Google's advertising tag also stores and reads cookies and similar identifiers on your device, as described in section 7.

You can control or delete cookies, local storage and site data through your browser or device settings, and Google's own ad settings let you control how Google uses information for advertising, as described in section 11. Receitz asks before it stores anything optional: nothing beyond the cookies and storage needed to run the service is used until you switch a purpose on, and switching a purpose off clears what it left behind.

Blocking cookies may limit advertising measurement. Blocking cookies or storage that sign-in depends on will prevent sign-in and other features from working correctly.

10. Retention and account deletion

We retain account information and saved recipe content while needed to provide the service to you. Support records and operational information may be retained as needed to resolve issues, maintain security, and meet legal obligations.

You can delete your account using the account-deletion option within Receitz. You may also contact support@receitz.app for assistance or to request deletion of your personal information.

Deletion requests apply to the information we control. Some information may remain temporarily in backups or be retained when necessary for legal obligations, security, or resolving disputes. Retained information remains subject to the protections in this policy.

Deleting your account cannot remove copies of shared recipes that other people have independently saved.

11. Your privacy choices

You can:

Manage your recipes and choose which recipes to share.
Change what may be measured at any time from the Privacy choices button, on any screen.
Use the account-deletion feature.
Contact us to request access to or correction of your personal information.
Revoke the application's access through your sign-in provider's account settings.
Limit advertising measurement using your browser's or device's cookie and storage settings and Google's own ad controls.
Contact us with questions about analytics records, or to request deletion of your information.

For Google, you can manage access through your Google Account connections settings.

Revoking a sign-in connection does not itself delete information already stored by Receitz. Use account deletion or contact us to request removal.

Depending on where you live, you may have additional rights concerning your personal information. We may need to verify your identity before fulfilling a request.

Google's ad settings let you control the advertising identifiers and information associated with your device or Google account: Google Ads Settings and My Ad Center . Clearing or blocking cookies and site data in your browser or device settings also limits what the advertising tag can associate with your visits.

Receitz provides a Privacy choices control on every screen, including inside the mobile app: a banner on your first visit, and a Privacy choices button that stays available afterwards, whether or not you are signed in. It holds two separate switches, usage analytics and advertising measurement, and both are off until you turn them on. Nothing is pre-selected, and no choice is inferred from how you browse. Your decision is saved with its date and the version of the wording you saw, and we ask again after 180 days. Where a saved choice cannot be read or written, everything optional stays off and we ask again rather than assuming consent. Changing or withdrawing a choice takes effect immediately, including from another browser tab or window. Signing in, saving and sharing recipes, scanning, and subscriptions are never affected by these choices. If your browser sends a Global Privacy Control signal, advertising measurement stays off whatever you choose. If you browse with JavaScript turned off, the choices control cannot run and nothing optional is measured at all.

12. Children's privacy

Receitz is not directed to children under 13. We do not knowingly collect personal information from children under 13.

If you believe a child has provided personal information, contact us at support@receitz.app so we can investigate and take appropriate action.

13. International processing

Information may be processed in countries other than your country of residence, including countries where our service providers operate. Where applicable law requires protections for international transfers, those requirements apply to our handling of your information.

14. Changes to this policy

We may update this Privacy Policy when our features or data practices change. We will publish the revised policy on this page and update its effective date.

Where required, we will provide additional notice or obtain consent before using information for a new purpose.

15. Contact

Operator: DigBI LLC

Email: support@receitz.app

Website: https://receitz.app