Privacy Policy
1. Introduction
Bargo ("we", "our", "us") is an Australian price comparison app developed and operated by Christian Biehl (ABN: 91 523 719 179), trading as Biehl Digital, Canberra ACT, Australia.
This Privacy Policy explains how we collect, use, store, and disclose your personal information when you use our mobile and web application (the "App"). It also explains your rights under the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).
By creating an account or using the App, you agree to the collection and use of information as described in this policy.
2. What Information We Collect
2.1 Account Information
When you create an account, we collect:
- Email address
- Password (stored as a secure hash — we never store your plain-text password)
- Display name (optional, if you choose to provide one)
- Account creation date and last sign-in timestamp
Authentication is handled by Google Firebase Authentication. We do not store your password directly.
If you sign in using Google Sign-In or Sign in with Apple, we receive your name and email address from that provider as part of the authentication process. We do not receive your password or payment details from these providers. You can revoke Bargo's access to your Google or Apple account at any time through your Google Account settings or Apple ID settings respectively.
2.2 App Usage Data
As you use the App, we store in Google Firestore:
- Shopping lists you create, including product names, quantities, and store assignments
- Household member names (if you use the household sharing feature)
- Saved products and price alerts you set
- Staples you save (items you buy regularly)
- Photos you attach to list items and staples (see §2.9)
- Product details you submit to help us add a missing product (see §2.9)
- Recipes, meal plans and recipe photos you create (see §2.10)
- Your store and category preferences
- Age verification status (whether you have confirmed you are 18 or older, for access to bottle shop pricing — see §2.7)
- Subscription tier and status
Household sharing and privacy: If you use the household sharing feature, shared lists are visible to all members of your household. Personal lists, search history, price alert history, and individual browsing activity are always private and are never visible to other household members, even within the same household account.
2.3 Location Data
If you choose to find stores near you (for example, to set your nearest IGA or Harris Farm store), the App will request access to your device's location. Specifically:
- What we collect: Your device's approximate geographic coordinates at the moment you tap "Allow location."
- How we use it: Solely to display a list of nearby stores. Your coordinates are sent to our Google Cloud Function, which queries the relevant store's API and returns a list of nearby locations.
- What we don't do: We do not store your location on our servers or in your account. We do not track your location over time. We do not use your location for advertising or share it with third parties beyond the store API query described above.
- What we do save: Once you select a store from the list (e.g. "IGA Ainslie"), that store name and identifier are saved to your account as a preference so you don't have to choose it again. This saved preference tells us which store you shop at — it does not tell us where you are, and it is not linked to the coordinates used to find it.
- When it's used: Only when you explicitly tap "Allow location" in the store picker. The App does not collect location data in the background.
- Your control: You can decline location access at any time by tapping "Not now" in the prompt, or by revoking location permission in your device settings. Declining location access means we cannot show you nearby stores — you can still use all other features of the App normally.
On iOS, location permission is requested as "While Using the App" only. We do not request background location access.
Typing a postcode instead: if you prefer not to share your location, you can type a four-digit postcode. The postcode is sent to our Google Cloud Function, which turns it into an approximate point using a public postcode list (GeoNames, licensed CC BY 4.0) and uses that point to find nearby stores. We do not store the postcode or the point, and no personal information is sent to GeoNames.
2.4 Crash Reports and Technical Data
If the App or the bargo.au website crashes or hits an error, it sends an error report to Sentry (Functional Software, Inc.), our error-reporting service, so that we can find and fix the fault. A report can include:
- The error message and the technical details of where in the code it happened
- Device type, operating system and App version (or web browser and version), and basic device state such as free memory, battery level and screen orientation
- The page or screen you were on, without any search words or other details added to the web address
- A short trail of recent actions in the App leading up to the error (for example, "opened the shopping list")
We set the service up so that it does not record your internet address or the approximate place (such as the city) that it points to, and we do not send your name, email address or account ID with these reports. We take steps to keep personal information out of them, but an error message can occasionally include a little text from what you were doing (for example, a product or recipe name). Reports are kept for a limited period, are used only to fix faults, and are not used for advertising.
What we do not do: we do not run analytics tools that track what you do in the App, and we do not use advertising identifiers.
Counts from the data we already hold: to understand how Bargo is used, we count, in total, how many accounts use features such as recipes, meal plans, shopping lists and households, and how many accounts have signed in recently. These counts come from the information described in §2.1 and §2.2 and are not used to look at individual people.
2.5 Payment Information
We do not directly collect or store your payment card details. Subscription payments are processed by Apple (App Store) or Google (Google Play) depending on your platform. Their respective privacy policies govern payment data handling. We receive only a confirmation of your subscription status.
2.6 Price Data (Not Personal Information)
The App displays product prices sourced from publicly available retailer websites. This price data is not linked to you personally and is not stored against your account.
2.7 Age Verification for Bottle Shop Pricing
Bargo displays pricing from bottle shops including Dan Murphy's, BWS, Liquorland, and Cellarbrations. In compliance with responsible service of alcohol obligations, access to this pricing requires you to confirm that you are 18 years of age or older.
When you confirm your age in the App, we store a single boolean value (ageVerified: true) against your account in Google Firebase. This record:
- Does not store your date of birth
- Does not involve any third-party identity verification service
- Is self-declared — you confirm your age by tapping "Yes, I'm 18 or older"
- Is stored only to avoid asking you again on future sessions
- Can be deleted by deleting your account
If you do not confirm your age, you can still use all other features of the App. Bottle shop prices will not be shown or added to your shopping list until age confirmation is provided.
2.8 Push Notifications
If you enable push notifications, we collect and store your device's push notification token (issued via Expo, our notification platform). This token is used solely to deliver:
- Price alerts — when a product you are watching reaches your target price
We do not use push tokens for advertising or share them with third parties for any purpose other than delivering the above notifications. You can disable push notifications at any time in your device's system notification settings, or by adjusting individual notification types in the App under Account → Notifications. Your push notification token is deleted when you delete your account.
2.9 Camera and Photos
Barcode scanner: the App uses your camera to read a barcode on your device and looks that number up to find the product. The picture itself is not saved or sent anywhere.
Photos you attach: if you add a photo to a list item or a staple (taken with the camera or chosen from your photo library), it is uploaded to Google Firebase Storage under your account. On a shared household list, other members of your household can see the photos on shared items.
Products you submit: if you submit a product that is missing from the App (its barcode, name, brand, size and category and, if you choose, a price, a store and a photo), we store the submission together with your user ID and review it. If we approve it, the details and the photo become part of the shared product catalogue shown to everyone, and are kept when you delete your account.
Your control: you can decline camera or photo access in your device settings. Barcode scanning and photos will not work, but everything else will. You can remove a photo at any time, and deleting your account deletes your photos (except for approved product submissions, above).
2.10 Recipes and Meal Planning
What we collect: the recipes you create or save (title, ingredients, method, notes, servings, category, tags you choose, and a source name and web address if you add them), the photos you attach (up to eight per recipe), and your meal plans (which recipe or note you plan for which day, and the number of servings). We store these in Google Firestore and Google Firebase Storage under your account. Every new account is given one sample recipe, which you can edit or delete.
How we use it: solely to provide the Recipes feature: storing and showing your recipes, scaling servings, adding ingredients to your shopping list, planning meals, and showing which recipes you can make from what you have.
Who can see it: recipes are private by default. If you turn on "Share with my household", every member of your household can see the recipe and its photos and can save their own private copy; only you can change or delete the original. Turning sharing off, leaving the household, or the household being dissolved ends their access (this can take a few seconds to a minute to take effect). A copy that someone saves is theirs alone: you cannot see or change it, and deleting the original does not delete it. A person who hides a recipe someone else shared does so privately: the hidden list is kept on their own account and is not visible to you or to other members. Meal plans are your own, or shared by every member of your household if you belong to one.
Importing a recipe:
- From a web address: the address you paste is sent to our Google Cloud Function, which requests that one public page from the website on your behalf and returns the recipe details to your screen. The website sees a request from Bargo's servers that identifies itself as BargoRecipeImport and gives our contact address; it does not receive your name, email, account or device details. We do not keep the page or the address: our logs record only the website name and a result code. Nothing is saved unless you tap Save. We do not import photos. Imports are limited to 20 an hour per person.
- From pasted text: the text is sorted into a recipe on your device. It is not sent anywhere until you save the recipe, like any recipe you type.
- From a screenshot or picture (phone app): the words in the picture are read on your phone. The picture is not sent to Bargo or to anyone else; only the text you then save in a recipe is stored. On Android the reading is done by Google's ML Kit through Google Play services, which may download a text-reading model to your phone and, according to Google, collects technical and diagnostic information about its use (not the picture). On iPhone the reading is done by the text recognition built into iOS (Apple Vision), and the picture stays on your phone.
- From another app's Share button, or the "Save to Bargo" browser extension: the link, text or picture is handed to Bargo on your own phone or in your own browser. The extension reads the page you are viewing only when you click it and sends nothing to our servers; the recipe it finds is handed to the Bargo web app in your browser, where you check it before saving.
Sharing a recipe out of Bargo: "Share this recipe" creates plain text on your device, which you send through the app you choose. "Share as a link" is different: we store a copy of the recipe (and the address of its first photo, only if you tick "Include the first photo") for up to 30 days under a long random code, so that anyone who has the link can read it without signing in and save their own copy. We do not show your name on the page, and we ask search engines not to list it. You can turn the link off at any time, and deleting the recipe or your account removes it. If you included the photo, anyone who kept the photo's address may still be able to open the photo for as long as it stays in your recipe. If you see a shared recipe that should not be there, use "Report this recipe" on its page.
"What can I make?": the ingredients you type are kept on your device and used to rank your own and your household's recipes. On the "My recipes" side they are not sent to us.
"What can I make?" on the web: if you switch to "The web" and press Search, the foods you picked (up to five, such as "onion, rice") are sent to our Google Cloud Function, which asks TheMealDB (themealdb.com), a recipe website, for matching recipes and sends them back to your screen. TheMealDB receives the food words from our server; it does not receive your name, email, account or device details from us. We keep a short-lived counter to limit how often one account can search, and our log records only how many words were searched and whether it worked, not the words. We do not store the recipes that come back; they disappear when you leave the screen, and the app does not save them into your recipes. Your choice to use this is remembered on your device only.
If you contact us about a recipe: if you send us the address of a recipe page that did not import, we use it only to look at that page, improve the importer and reply to you.
Your control: you can edit or delete any recipe you created, stop sharing it, and turn off its link at any time. Deleting your account deletes your recipes, recipe photos, link copies and your own meal plans (see §7). If a household is dissolved, recipes shared with it are not deleted: former members lose access and each person keeps the recipes they created as personal recipes.
2.11 Contact Form
If you use the contact form at bargo.au/contact, we collect your name, email address, the topic you choose, your message, and, if you add them, the address of a store, product or recipe page. The form sends this to our business mailbox, which is hosted by Zoho Mail (we use Zoho's Australian service). We do not keep it in the Bargo database. We keep the email for as long as we need it to answer you and for our records, and use it only to reply to you. To limit spam, we count how many messages come from one internet address in an hour, using a one-way scrambled form of the address that cannot be turned back into the address; the count expires after about an hour.
2.12 Launch Waitlist
If you ask on bargo.au to be told when Bargo launches, we store your email address, the date, and where you signed up in our Google Firestore database. We use it only to tell you about the launch. Any email we send you will say who we are and how to unsubscribe. To be removed at any time, contact us at contact@bargo.au.
2.13 Technical Logs and Browser Storage
Logs: our hosting and server functions (Google Firebase and Google Cloud) keep logs of requests, including the internet address the request came from, the time, and which page or function was used. We use them for security, to limit abuse and to find and fix faults. Google keeps them for a limited time. We also keep short-lived counters (for example, how many searches an account has made in the last hour) to prevent abuse.
Browser storage (web app): the Bargo web app stores your sign-in session and a few settings (for example, your choice about searching recipes on the web) in your browser's storage on your device, so the app works as you expect. We do not use this storage for advertising.
3. How We Use Your Information
We use the information we collect to:
- Create and manage your account
- Provide the core features of the App (price comparison, shopping lists, household sharing)
- Provide the Recipes feature (store your recipes, share them with your household, plan meals and shop from them)
- Review products you submit and add approved ones to the shared catalogue
- Process and manage your subscription
- Send transactional emails (e.g. account verification, password reset)
- Deliver push notifications for price alerts (if enabled)
- Find stores near your location when you explicitly request it (store picker feature)
- Find and fix faults through crash reports, and understand how many accounts use each feature (see §2.4)
- Comply with our legal obligations
We do not use your personal information for advertising purposes, and we do not sell your data to third parties.
4. Disclosure of Your Information
We may share your information with the following third parties, solely to operate the App:
- Google Firebase (Google LLC) — authentication, database, file storage, hosting and server functions. Data is stored on servers in the australia-southeast1 region (Sydney, Australia). Google is certified under applicable data transfer frameworks.
- Sentry (Functional Software, Inc.) — receives crash and error reports from the App and website (see §2.4). We have chosen for Sentry to store these reports in the European Union (Frankfurt, Germany).
- Apple Inc. / Google LLC — subscription and payment processing via their respective app stores.
- Expo (Expo Technology, Inc.) — our app build, update, and push notification platform. If you have enabled push notifications, your device's push token is processed by Expo's push notification service to deliver price alerts to your device.
- IGA / Metcash (igashop.com.au) — when you use the IGA store finder, your approximate coordinates are used to query the igashop.com.au store locator API to find nearby IGA stores. No personal information other than coordinates is transmitted.
- Harris Farm Markets — when you use the Harris Farm store finder, a list of all Harris Farm store locations is retrieved from Harris Farm's public API. No location data is transmitted for this feature.
- Open Food Facts — when you submit a missing product, its barcode number (not you) is sent to world.openfoodfacts.org to pre-fill the form.
- TheMealDB — only if you use "The web" in "What can I make?": the food words you pick are sent from our server to TheMealDB, and the recipes and pictures shown come from them (see §2.10). Recipe data and imagery: TheMealDB (https://www.themealdb.com/).
- Websites you import recipes from — when you import a recipe from a web address, our server requests that page from the website (see §2.10). The website does not receive any personal information about you.
- Google ML Kit (Google LLC) — Android only: reads the words in a recipe screenshot on your phone through Google Play services (see §2.10). The picture is not sent to us.
- Apple Vision (Apple Inc.) — iPhone only: reads the words in a recipe screenshot on your phone using text recognition built into iOS (see §2.10). The picture is not sent to us and stays on your phone.
Zoho Mail (Zoho Corporation) — hosts our business mailbox, which receives contact-form messages and our replies (see §2.11).
Where your information goes: your account data, recipes and photos are stored in Google's Sydney region (see §6). Some of our service providers handle information outside Australia: Google (Firebase and Google Cloud) may process data in other countries; Sentry (crash reports) is a United States company that stores reports in Germany; Expo, Apple and Google (push notifications, app stores, payments) operate globally, including in the United States; TheMealDB, the recipe website used for the web search, is based in the United Kingdom; and Zoho Corporation, which provides our mailbox, is headquartered in India with a United States office, although we use Zoho's Australian service for our mail. Where we send information to these providers, we do so only for the purposes described in this policy.
We will not disclose your personal information to any other third party without your consent, except where required by Australian law or a court order.
5. Price Data and Store Availability
Bargo is a price comparison service, not a retailer. All purchases are made directly with the relevant retailer and are subject to that retailer's terms, age verification requirements, and fulfilment policies.
We attempt to retrieve the latest prices from all supported stores multiple times per week. Some stores actively restrict automated price lookups, which may mean certain prices are several days behind. We always show the most recently confirmed price.
IGA store availability: Bargo sources IGA pricing from the Metcash igashop.com.au online platform. Not all physical IGA stores participate in this platform — smaller independent "IGA Local Grocer" format stores may not have pricing available in Bargo. You can find all physical IGA store locations at iga.com.au/stores.
Store-specific pricing: IGA and Harris Farm prices may vary between store locations. Where you have selected a preferred store, Bargo will display pricing for that store where available. For stores without a selected location, Bargo displays the most representative available price.
Unit pricing: Where a store does not provide unit pricing directly, Bargo calculates an approximate unit price from the product name and size. Calculated unit prices are marked with a ~ symbol and may not be exact.
6. Data Storage and Security
Your data is stored on Google Firebase infrastructure in the australia-southeast1 region (Sydney, Australia). Google maintains industry-standard security certifications (ISO 27001, SOC 2).
We take reasonable steps to protect your personal information from misuse, interference, loss, unauthorised access, modification, and disclosure. These steps include:
- Encrypted data transmission (HTTPS/TLS) for all data in transit
- Data at rest encrypted by Google Firebase using AES-256 encryption
- Firebase Security Rules restricting database access to authenticated users
- Passwords hashed using industry-standard algorithms by Firebase Auth
No method of transmission over the internet is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
7. Data Retention
We retain your personal information for as long as your account is active or as needed to provide the App's services.
If you delete your account, we will delete or anonymise your personal data within 30 days, except where we are required to retain it for legal or accounting purposes.
Recovery history and backups: our database keeps a short recovery history, and we may also keep backups, so that we can restore data after a mistake or a fault. Neither is kept for longer than 30 days. When you delete your account, copies of your information in that history and in any backups are overwritten as they expire, within 30 days.
Photos, recipes and shared links: your photos, recipes, meal plans and recipe-link copies are kept while your account exists and are deleted when you delete your account. A recipe link expires after 30 days. Product submissions we have approved, with their photos, become part of the shared product catalogue and are kept.
Inactive accounts: If your account has had no sign-in activity for 11 months, we will send a notification to your registered email address advising that your account will be deactivated. If no login occurs within a further 30 days (12 months total inactivity), your account and all associated personal data will be permanently deleted. This policy ensures we do not retain personal data beyond what is necessary. You may reactivate your account by logging in at any time before the 12-month threshold.
8. Your Rights
Under the Australian Privacy Act 1988 (Cth), you have the right to:
- Access the personal information we hold about you
- Request correction of inaccurate or out-of-date information
- Delete your account and all associated personal data (including your photos and recipes) at any time, directly within the App via Account → Delete account, or by contacting us at contact@bargo.au (see how to delete your account)
- Opt out of non-essential communications (including push notifications)
To exercise any of these rights, contact us at contact@bargo.au. We will respond within 30 days.
9. Children's Privacy and Age Requirements
The App is intended for users aged 13 and over. We do not knowingly collect personal information from children under the age of 13. If you believe a child under 13 has provided us with personal information, please contact us and we will delete it promptly.
Users between 13 and 17 may use all core grocery comparison features of the App. Access to bottle shop pricing (Dan Murphy's, BWS, Liquorland, and Cellarbrations) is restricted to users who have confirmed they are 18 years of age or older (see §2.7). If we become aware that a person under 18 has confirmed age verification, we will remove that verification and restrict access to alcohol-related pricing accordingly.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting a notice in the App or by email. Your continued use of the App after any changes constitutes your acceptance of the updated policy.
The date at the top of this document indicates when it was last updated.
11. Contact Us
If you have questions or concerns about this Privacy Policy or our data practices, or wish to make a privacy complaint, please contact:
Christian Biehl
Trading as Biehl Digital
Canberra ACT, Australia
Email: contact@bargo.au
If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.