QUEST LABS · CAL TALE
Privacy Policy
Cal Tale is operated by Quest Labs: Maloney Media Pty Ltd (ACN 622 109 522) as trustee for Maloney Family Trust (ABN 45 178 962 621), trading as Quest Labs in Australia. In this policy, “Quest Labs”, “we”, “us” and “our” refer to that operator. Contact us at hello@caltale.app.
This policy describes the current Cal Tale app, including its TestFlight version, and our website. It explains information kept on your device and information processed by us and our service providers.
The main points
- Your diary, saved photos, profile answers and Quest progress are saved on your device. There is no Cal Tale login or cloud diary backup in this version.
- Food analysis sends selected food information through our server to external services. It is not entirely on-device processing.
- Apple and RevenueCat handle purchases and subscription status. Our server keeps generated device identifiers and usage counters.
- PostHog receives selected app events with generated identifiers. We do not send diary content or body measurements in those analytics events.
1. Information saved on your device
The app saves information you enter or confirm, including your preferred name, setup answers, age, sex used for estimation, height, weight, goals, activity choices, nutrition targets, meal records, saved photos, water entries, preferences, reminders and Quest progress. Some of this may be health-related or sensitive information.
These records are stored locally rather than uploaded as a cloud diary. Our analysis, billing and analytics integrations do not receive your complete diary or profile as part of their normal requests. If you include personal information in a photo, description or feedback message, that information can be sent with that submission.
App storage is not an encrypted medical-record vault. Device security, operating-system backups and transfers are also subject to your device settings and platform services. We do not provide a Cal Tale cloud backup or recovery service.
2. Food analysis and barcode lookups
When you use photo or description analysis, the app sends the selected meal photo or description through our HTTPS server hosted on Render to OpenAI to generate nutrition estimates. Photos are resized and re-encoded for upload; the original saved diary photo stays on your device. Meal rescoring sends the meal name, ingredients, portions and nutrition needed for that request.
Opening an older analysed meal without a nutrition score, or saving an ingredient nutrition edit, can also request a score. These analysis requests do not deliberately include your preferred name, weight, calorie targets, setup answers or full diary history.
Our analysis service processes these food requests in memory and does not save uploaded images, meal descriptions or analysis results as a server-side diary, or log their request bodies. We request that OpenAI not store responses for later retrieval. That setting does not mean zero provider retention: OpenAI may retain content and related data for abuse monitoring, security or legal purposes under its own controls. See https://developers.openai.com/api/docs/guides/your-data.
Barcode lookups send the barcode through our server to Open Food Facts to retrieve product information. See https://world.openfoodfacts.org/terms-of-use. Manual calorie entry does not require a food-analysis upload; subscription checks and app analytics can still occur.
3. Subscriptions and device verification
Apple processes App Store payments. RevenueCat processes subscription and transaction information, product identifiers, trial eligibility, purchase and renewal status, and technical information needed for billing. We use a generated customer identifier rather than requiring an email account. We do not receive your full payment-card details.
Apple App Attest helps verify access from a genuine app installation. Our server stores a verification public key, verification counter and generated customer identifier, together with daily and monthly request counters used to enforce analysis allowances and prevent abuse. Short-lived verification challenges and sessions are also processed. These are service-access records, not meal images or diary history.
Restoring purchases can associate an existing subscription with the current installation. Apple and RevenueCat may retain purchase records separately from your local data. See https://www.apple.com/legal/privacy/ and https://www.revenuecat.com/privacy.
4. App analytics
We use PostHog to understand app use and improve reliability and the onboarding experience. Selected events include app opens, onboarding steps, purchase attempts and outcomes, food-analysis success or failure and duration, saved-food actions and Finish tracking actions.
These events use generated installation and session identifiers, selected plan or logging method, result, and app environment. Our event configuration excludes names, emails, food descriptions, barcodes, photos, calorie targets and body measurements. Session recordings, automatic screen capture, automatic exception capture and person profiles are disabled.
The app can provide its generated analytics identifier to RevenueCat to associate subscription events with app events. The PostHog project used for TestFlight is hosted in the United States. The app currently has no analytics opt-out switch. See https://posthog.com/privacy.
5. Feedback, support and TestFlight
If you send in-app feedback, we receive your message, an optional reply email, app version, interface language, feedback identifier and receipt time. Food records, photos, weight and Quest history are not automatically attached. Feedback is saved in our server inbox. Where email forwarding is configured, it is also processed by our email delivery provider, Resend, and our support email service. See https://resend.com/legal/privacy-policy.
If you contact us by email, we receive the contents and contact information you send. Avoid including information that is not needed to address your request.
Apple separately operates TestFlight and may provide us with tester feedback, screenshots, crash information and testing metrics according to its TestFlight terms and your sharing choices. This is separate from the app’s own feedback and analytics.
6. Website, hosting and technical information
Our website is hosted on Netlify. It has no Quest Labs email signup form, advertising pixels or app analytics SDK. Hosting and network providers may process IP addresses, browser or device information, request times, requested URLs and security logs when serving the website or app API. Netlify may also provide its own hosting or site-management features.
Render hosts the app API and persistent service-access and feedback records. See https://render.com/privacy and https://www.netlify.com/privacy/. Providers have their own data-handling obligations and policies; this policy does not describe every service they may provide directly to you.
7. Why we use information and who receives it
We use information to provide the features you request, calculate local targets, verify access, process subscription status, manage analysis allowances, respond to support, understand selected app usage, maintain security and comply with legal obligations. We do not sell your personal information or use your diary, food photos or body measurements for targeted advertising.
Information is disclosed to the providers described above as needed for those services. We may also disclose information when legally required, to respond to lawful requests, or where reasonably necessary to protect people, prevent fraud or establish or defend legal rights.
Providers may process information outside Australia, including in the United States. Other processing locations depend on the provider and its subprocessors; PostHog’s current US hosting does not establish the location of every other service. Contact us if you need more information about international processing.
8. Retention, deletion and your choices
Local records remain on your device until changed or removed. You can edit or delete meal records, water entries and weight records through the relevant app screens. Deleting a meal record may leave its stored photo file on the device. The current app has no whole-app export, deletion or restore control. Removing the app or clearing its storage can permanently remove local records; operating-system backups may be governed separately by the platform.
Our current server does not automatically expire stored device-verification, usage or feedback records. Contact us to request access, correction or deletion. Removing local app data does not automatically delete server records, subscription transactions, analytics or information already processed by providers.
Provider retention periods vary. Purchase records, support correspondence, security records and backups may remain where needed for their purpose or applicable legal obligations. We assess deletion requests against those requirements and explain any information we cannot delete. We do not promise that deleting the app immediately deletes all provider-held data.
Camera and notification permissions can be managed in your device settings. The system photo picker lets you select which photo to share. Notifications are optional; trial reminders require your choice, notification permission and a confirmed trial expiry. Declining notifications does not prevent a purchase. Deleting the app does not cancel an Apple subscription.
You can request access to or correction of personal information we hold, or raise a privacy concern, using the contact below. Where applicable law provides additional rights, such as deletion, restriction, objection or portability, you may also ask to exercise them. We may need proportionate information to verify and locate your records; with generated identifiers and no account, an email address alone may not identify app records. We cannot retrieve a diary held only on your device.
9. Children and changes to this policy
Cal Tale’s automated target estimator is designed for adults aged 18–100. We do not intentionally solicit children’s personal information. Contact us if you believe a child has provided personal information through our services.
We will update this page when our information-handling practices change and revise the date above. Where required, we will provide an additional notice or obtain consent for a material change.
10. Contact and privacy complaints
Contact Quest Labs at hello@caltale.app with your question, request or complaint. We will review it, may ask for relevant details, and respond with the outcome or next steps.
If you are dissatisfied, you may contact the privacy regulator relevant to you. In Australia, information about privacy complaints is available from the Office of the Australian Information Commissioner at https://www.oaic.gov.au/privacy/privacy-complaints.