Privacy Policy

This policy explains what Drinq does with information when you use the app. Drinq has no user accounts and does not require a login, email address or other contact detail to use the app. During onboarding, you may optionally enter a preferred first name so the experience can address you personally. You can continue without entering one.

Who is responsible (controller)

The controller for the processing described here is:

• Rami Alzoubi

• Einzelunternehmer (Drinq AI)

• Mathildenstraße 3

• 42105 Wuppertal

• Germany

Contact for privacy questions: support@drinqai.app. We are not required to appoint a Data Protection Officer; privacy requests are handled at the address above.

What stays on your device

Your fasting profile and protocol, the answers you give during onboarding (such as preferred first name, goal, age, height, weight, gender and experience), your daily check-ins, symptoms, completed checkpoints, chat history and fasting history are stored locally on your device.

The complete local profile is not uploaded as a server-side user profile, and the local copy is deleted when you reset the app data or uninstall the app. Selected fields are transmitted only in the situations described below, including AI features and subscription-offer personalisation.

What is sent to our services

To generate or adapt protocol content and answer your questions in the AI chat, the app sends the relevant context of that request (for example your preferred first name, profile answers, fasting phase, day, goal, protocol items, check-in information and the message you typed) to our backend, which forwards it to an AI model provider for processing.

These requests are not linked to a user account or contact details. They are linked to an anonymous identifier generated on your device, but request content may include your preferred first name and the personal or health information needed to provide the feature.

If you choose Contact us, Report a bug or Send feedback in Settings, the app opens an email draft addressed to us. The AI chat may also offer the matching support action when it recognizes that developer help is appropriate. To make bug reports useful, the app keeps a small capped history on your device of recent screen, calendar and protocol-transition actions, together with recent technical errors. A draft opened from chat can include the AI summary, relevant recent conversation, current plan and transition state, calendar diagnostics when relevant, and this local diagnostic history. Support drafts also include the app version and build, platform, device user-agent information, locale, timezone, display and network state, and current date. You can review, edit or remove any of this information before sending the email. The local history is not uploaded automatically, and nothing is sent unless you send it through your email app.

Anonymous device identifier

The app generates a random identifier the first time it runs and stores it on your device. It is used to apply fair-use limits to AI requests, to protect the service from abuse, and to keep your paywall and experiment assignment consistent between sessions.

It is not tied to your identity and cannot be used to contact you. Resetting the app data or reinstalling ends its association with you.

Purchases

Subscriptions are processed by Apple or Google. We never see or store your payment details. Our paywall and subscription provider receives the anonymous identifier above and the outcome of a purchase so the app knows whether your subscription is active.

To select, personalise and test subscription offers, the app also sends the paywall and subscription provider attributes including your preferred first name, primary goal, selected fasting duration, gender, age, fasting experience, prior-fast answer, preferred fasting cadence and whether preparation is enabled. The provider may also process paywall views and interactions, experiment assignment, app and device information, internet address, subscription status and purchase events. This information is used for subscription management, offer personalisation and measuring paywall performance, not for third-party advertising.

What we do not do

• We do not sell your data

• We do not show advertising or use advertising trackers

• We do not build a marketing profile of you

• We do not share health information with third parties for their own purposes

Health data

Any health-related information you enter is used only to generate and adapt your fasting protocol and the content shown in the app. It is not used for advertising, and it is not sold or shared for third-party marketing under any circumstances.

Stage insights about fuel use, insulin rhythm, inflammation, cellular recycling and focus are general education selected for the current place in the plan. They are not readings from your body, laboratory results or clinical measurements.

Retention

Local data stays until you reset it or uninstall the app. Request data processed by our backend is retained only briefly, for operational and abuse-prevention purposes, in a form that is not linked to your identity.

Subscription, paywall, live-update, analytics and diagnostic providers retain the information they process for the periods needed to provide their services, prevent fraud, meet legal obligations and support our legitimate operational needs. Retention periods vary by record type and provider. We require providers to delete or anonymise data when it is no longer needed, subject to legal and security requirements.

Your rights

Under the GDPR you have the right to access, correct, delete, restrict and object to the processing of your personal data, and to data portability.

Where we rely on your consent, you can withdraw it at any time without affecting processing that already happened. Withdrawing consent for health information means stopping use of the feature and resetting the app data.

Entering optional check-ins, symptoms, notes or chat details is never a legal or contractual requirement. You can use the planner without adding them, although related personalisation will be more limited.

Because the app holds your data locally and without an account, you can exercise deletion yourself at any time with "Reset app data" in Settings. For any other request, contact support@drinqai.app.

Automated processing

Your protocol, checkpoints and daily adjustments are generated automatically from the answers you give, combined with AI models. This is not a decision with legal or similarly significant effects on you within the meaning of Article 22 GDPR: it is educational wellness content that you are free to ignore, change or override at any time, and you can ask us to review anything the app produced.

Younger users

Younger users should involve a parent or guardian and speak with a qualified healthcare professional before changing their eating pattern. Drinq does not require an account and does not knowingly collect contact details from children.

Legal basis for processing (EEA / UK)

We process the information you enter to perform the service you asked for, which is generating and adapting your fasting protocol (Article 6(1)(b) GDPR). Where that information concerns your health, we rely on your explicit consent (Article 9(2)(a) GDPR), which you give by choosing to enter it and which you can withdraw at any time by resetting the app data.

We process the anonymous device identifier for our legitimate interest in keeping the service secure, available and fairly used (Article 6(1)(f) GDPR).

We process the minimal technical information needed to check for and deliver app updates for our legitimate interests in maintaining a secure, reliable and current app (Article 6(1)(f) GDPR). This update delivery is necessary app infrastructure and is separate from optional product analytics.

We process minimal onboarding funnel events, consisting only of an ordinal step number and action joined within the current in-memory onboarding session, for our legitimate interest in finding and fixing onboarding drop-off (Article 6(1)(f) GDPR). The temporary session identifier is not stored on your device, is not joined to your installation identifier or profile, and disappears when the app process ends. We do not include screen names, answers, health information or other onboarding content in these events. You can object to future onboarding analytics by choosing “Don’t share analytics” or by turning detailed product analytics off in Settings.

We process subscription and paywall events as necessary to provide and administer your subscription (Article 6(1)(b) GDPR). We process detailed product analytics only after you choose “Allow” (Article 6(1)(a) GDPR); at that point we record a new onboarding-completion marker under the consented installation identifier so later activation and retention can be measured. We do not link, alias or rewrite the earlier temporary onboarding-session events. You can withdraw consent at any time in Settings. We process limited diagnostics and crash reports for our legitimate interests in understanding app performance, fixing faults, preventing fraud and improving reliability (Article 6(1)(f) GDPR).

Processors and international transfers

We use a small number of service providers acting on our instructions: Supabase for cloud hosting and backend infrastructure, OpenAI for AI processing, Superwall for paywalls and subscription management, Capgo for secure live app updates, PostHog for minimal onboarding funnel measurement and optional detailed product analytics, and Sentry for diagnostics and crash reporting. Purchases themselves are handled by Apple or Google as independent controllers under their own policies.

Some of these providers operate outside the European Economic Area. Where that happens, transfers are based on the European Commission's Standard Contractual Clauses or an equivalent lawful transfer mechanism.

Security and incidents

We use encryption in transit, restricted access to our backend and minimal data retention. No system can be guaranteed completely secure. If a breach ever affects personal data and is likely to create a risk to you, we will notify the competent supervisory authority and affected users as required by law.

Complaints

If you believe we have handled your data unlawfully you can complain to your local data protection supervisory authority. You are also always welcome to contact us first.

Advertising, affiliate links, analytics and diagnostics

We do not run third-party advertising and we do not use advertising or cross-app tracking identifiers, so no App Tracking Transparency permission is requested.

The app may contain links to products, services or partners, and some of those links may earn us a commission. Such links are marked, and following one may take you to a third-party website with its own privacy policy, which we do not control.

Before you make an analytics choice, we use PostHog in its European data region to measure onboarding drop-off. PostHog receives only whether a numbered onboarding step was viewed, completed or exited, plus a random identifier held only in memory for that onboarding session. We disable person-profile creation and location enrichment for these events. We do not send the screen name, total screen count, time spent, device or installation identifier, answers, health information, app platform or other device properties. Choosing “Don’t share analytics” stops future minimal onboarding events and records your objection.

If you choose “Allow”, PostHog also receives a random installation identifier shared with Superwall, a new onboarding-completion marker, detailed screen and feature interactions, coarse time-on-screen and completion buckets, broad fasting protocol categories, app and platform information, and paywall or subscription events. The new completion marker begins the consented activation and retention funnel; PostHog does not link the earlier temporary onboarding-session events to this identifier. We disable autocapture and session recording. You can withdraw consent at any time in Settings, which stops future detailed collection and also stops future minimal onboarding collection on the device. Withdrawal does not erase information already processed; contact us if you also want us to request deletion of prior analytics associated with your installation identifier.

We use Capgo in its European service region to check for and securely deliver eligible web-layer app updates. An update check can include a random identifier scoped only to this app installation, internet address and request country, app identifier and version, installed bundle and channel, platform and operating-system version, updater-plugin version, and whether the build is production, development or an emulator. We do not give Capgo your preferred name, account identifier, analytics identifier, onboarding answers, health information, chat content or a custom user ID. Optional Capgo lifecycle statistics are disabled. This processing is used only for update eligibility, delivery, security and reliability, not advertising or cross-app tracking.

We use Sentry, operated by Functional Software, Inc., for application error monitoring, crash reporting, structured diagnostic logs and performance tracing. Our Sentry organisation uses the European data region. Sentry receives only the diagnostic fields configured by us and processes them on our behalf as a service provider. We configure request and response bodies, authentication credentials, cookies, headers, URL query parameters, AI inputs and outputs, health entries and direct identity fields not to be collected.

We do not intentionally send your preferred first name, onboarding answers, measurements, symptoms, notes, exact schedules, checkpoint content, health entries, chat messages or AI content to analytics or crash-reporting tools. Diagnostic records can sometimes capture incidental technical context, so we configure these tools to minimise collection and restrict access. Analytics and diagnostic data is not used for advertising or cross-app tracking and is not sold.

Changes and contact

We will update this policy when the app changes and the current version is always available here and at https://drinqai.app/privacy.

Questions: support@drinqai.app.