Privacy Policy

1. Who we are

The controller is Joel Pegueroles Pallares, trading as CalTap, at Calle Pare Palau, 5, Entresuelo 3, 43001 Tarragona, Spain. Contact support@caltap.app for privacy questions or requests. Full business details are in our Terms of Service.

2. Data and purposes

We use account details supplied through Apple or Google, your body profile, goals, preferences and meal records to provide and personalise CalTap. We also process subscription information from Apple and RevenueCat, technical and usage data, privacy choices and messages you send to support. We do not receive your sign-in password or full payment card details.

Account and required profile information are needed to provide the account and automatic nutrition plan. Device permissions are optional, but declining one may prevent the corresponding feature from working. If you enable notifications, we store a device token linked to your account and use it to send them through Apple’s push service; you can turn them off in iOS settings. Optional analytics is not a condition of using your subscription.

Our legal bases are performance of our agreement for account, meal and subscription services; legal obligations for statutory records and rights requests; consent for optional analytics and promotional emails; and legitimate interests for limited app performance monitoring with EAS Observe, responding to other enquiries and handling legal claims. The intended basis for backend analytics is our interest in understanding service performance and feature use; its assessment remains incomplete.

Nutrition and body information may reveal health data. A contract alone is not sufficient for this processing: the described version has no separate explicit health-data consent and withdrawal flow, and no other applicable health-data condition has been established. Accepting this Policy does not provide that consent.

3. When and how we use AI

CalTap uses third-party AI when you request meal analysis, corrections, nutrition-label extraction or Apple Watch transcription. Requests pass through our backend, Convex, to OpenRouter and the model provider handling the request.

• Text and corrections: we send your description or the meal details being corrected and your instructions, with relevant language and date context.
• Food photos and nutrition labels: we send the selected image for analysis or extraction. Food photos may remain on your device; they are not a synchronised cloud photo library. Label images are not stored in the saved meal. Derived text and nutrition results are saved to your account.
• iPhone voice: Apple speech recognition converts speech to text, preferably on-device and, where needed and permitted, through Apple’s online service. CalTap sends the resulting text for AI analysis, not the iPhone audio to OpenRouter.
• Apple Watch voice: we send the recorded audio for transcription through Convex and OpenRouter, with Groq preferred and other providers possible. The resulting text is then analysed or used to correct a meal.

These AI requests do not intentionally include your full account profile, complete diary, payment details or Apple Health readings. Inputs can still contain personal or health information, so avoid including unrelated people, documents or conversations.

We use AI model providers through OpenRouter, and the provider handling a request may vary, including fallback providers. Depending on the provider’s policies and the applicable settings, submitted content and generated results may be retained or used to train or improve models. Providers may also keep request logs and process data outside the EEA. OpenRouter’s own data practices are separate from those of the model providers.

CalTap has not verified the complete production provider list, retention periods, training settings, contractual authorisation for sensitive data or transfer safeguards for every provider. We do not guarantee immediate deletion, exclusion from training or processing exclusively in Europe.

AI results are estimates and may be wrong. Review and correct them; do not rely on them for medical decisions. Nutrition targets use programmed formulas. Barcode lookups use Open Food Facts rather than AI, sending the product code and ordinary connection information. CalTap does not make solely automated decisions with legal or similarly significant effects.

4. Apple Health

With your permission, CalTap reads Apple Health data on your device to support activity summaries and calorie adjustments. The permission request covers active energy, steps, workouts and sleep; the current summary uses active energy and steps. HealthKit readings are not sent to our backend, AI or analytics providers. A derived summary may appear on your paired Watch or a Live Activity. You can revoke access in Apple’s settings. We do not sell HealthKit data or use it for advertising.

5. Analytics and your choice

We use PostHog to understand feature usage and service performance. In-app analytics and session replay run only if you accept. They collect usage and device information and recordings of your interactions with the app. You can change your choice in Settings → Privacy and analytics; withdrawal stops new optional analytics and recordings but does not erase previously collected data.

If you decline, backend events still go to PostHog. They include your account identifier and limited information about feature use, operation results and subscriptions, rather than meal contents, photos, audio or HealthKit readings. These events are account-linked, not anonymous. You may object by contacting support; the optional switch does not stop them, and a separate account-level exclusion is not yet implemented.

EAS Observe measures app performance and stability using load times, initial screen, device and app information, session and random installation identifiers, and IP address. It receives no account details, health data or user content, and is not linked to your account or used for advertising, profiling or cross-app tracking. It runs without requesting consent, independently of optional analytics and session replay.

We use Sentry for error diagnostics and performance monitoring.

6. Providers and international processing

Our providers include Clerk for authentication; Convex for account and meal storage; OpenRouter and model providers for AI; Open Food Facts for barcode lookups; RevenueCat and Apple for subscriptions and push notifications; PostHog for backend events and optional in-app analytics. PostHog and Sentry may retain historical recordings or diagnostics; Apple and Google also process data for their own sign-in or platform services.

Clerk may send necessary authentication emails when sign-in or email verification requires them. These are service messages, not promotions. Resend is our provider for other account emails and promotional emails and receives your email address, message content and delivery information for these sends. Necessary account emails support account operation, security and legally required notices. Promotional emails require your separate opt-in; you can decline without affecting your use of CalTap or withdraw consent at any time through the unsubscribe link in each promotional email. This does not stop necessary account emails.

Expo (650 Industries, Inc., US) processes Observe data for CalTap. Its privacy policy describes Data Privacy Framework participation and Standard Contractual Clauses where required; CalTap’s applicable data processing agreement (DPA) and transfer arrangements remain to be confirmed.

Information may also be shared with authorised support staff, professional advisers or authorities where needed for support, legal obligations or claims. We do not sell personal data or use the described integrations for behavioural advertising.

Providers may process data outside the EEA, including in the United States. Applicable transfers require an adequacy decision or safeguards such as Standard Contractual Clauses; the complete transfer arrangements for CalTap have not been verified. Contact support for information about locations and safeguards.

7. Retention and deletion

Account and meal data remain while your account is in use. Removing a meal from the diary hides it but retains its backend data. The automatic part of account deletion removes profile, meal and account-linked backend analytics records; this does not complete every external deletion step. There is no automatic inactivity expiry or age-based purge of backend analytics records.

Local photos and pending recordings follow device and account cleanup. Retention periods and deletion arrangements for provider data, historical diagnostics and recordings, backups, and support or hosting records have not been verified. Records needed for a specific legal obligation or claim must be limited to that purpose.

Observe’s retention and deletion periods remain pending confirmation with Expo.

Request account deletion in Settings → Account → Delete account. The process combines automatic deletion with manual completion of pending external steps by CalTap’s operator. We complete this process within 14 calendar days of receiving your request. An accepted request is not confirmation that deletion is complete. You do not need to contact support again to complete a request started in the app.

We retain a deletion-tracking record with your account identifier, progress and pending steps until all required steps are complete. An offline Watch is cleaned when it reconnects.

Support remains available as an alternative way to request deletion or ask about progress. Uninstalling the app does not delete your account. Account deletion does not remove your Apple Health data, original Photos library or independently held Apple purchase records, and does not cancel an Apple subscription.

8. Website, storage and security

The app stores credentials, preferences and pending work on your device. The website uses browser storage to remember your chosen language; you can clear it in your browser settings. Its reviewed code sets no own cookies and includes no analytics trackers or data-collection forms. Hosting receives ordinary request information, including IP addresses; external deployment settings and log retention have not been verified. App analytics choices apply to the app.

We use authenticated access and protected transport to safeguard data. No system is completely secure; AI providers must read the content they process. Contact us if you suspect unauthorised access.

9. Your rights

You may request access, correction, erasure, restriction or portability, withdraw consent, and object to processing based on legitimate interests, including EAS Observe monitoring, subject to applicable conditions. Email support@caltap.app or write to the address above. We may need to verify your identity. After an objection, contested processing must stop unless overriding lawful grounds or legal claims justify continuing. Exercising these rights does not require cancelling your subscription.

Requests are normally free and answered within one month. Where legally permitted, we may extend this by up to two months and explain why within the first month. You can complain directly to the Spanish Data Protection Agency (AEPD) or your competent supervisory authority.

10. Policy changes

We will update this Policy and its effective date when practices change, and give appropriate notice of material changes. An update does not override your choices or replace any new consent required.