Android · Hapiga Vietnam Company Limited

Privacy Policy

Last updated: 22 October 2026

Hapiga Vietnam Company Limited provides Sippy: Alcohol Moderation Pet ("Sippy") for Android. We decide how personal data is used to run this app and its services. Contact support@hapiga.com with privacy questions.

Sippy helps adults record alcohol use and work toward personal goals. Your drinking records and messages can contain sensitive health information. Read this policy before you enter that information.

1. Data that we collect

• Account data. The app creates an installation identifier and a Firebase account. For email sign-in, Firebase Authentication processes your email address and password. We use your email address to identify the account. If you link Google, we can receive the account identifier, name and email address that the provider shares. An installation identifier can link your activity, even when you do not give your name.
• Information that you enter. Your name, onboarding answers, age range, gender, drinking habits, drink counts, goals, intentions, reasons for change, lifestyle answers and preferences. We also store progress, rewards and settings.
• AI chat. Your messages, generated replies and facts saved from earlier conversations. Messages can include personal or health information that you choose to share.
• AI choices and reports. We store whether you allow AI processing, the notice version and the time of your choice. If you report a generated reply, we store its identifier, a copy of the reply, your selected reason, the report time and review status.
• Purchases. Product and transaction identifiers, subscription status, purchase history, trial status, renewal dates and the app user identifier. Google Play processes payments. We do not receive your full payment card number.
• Device and service data. App and operating system versions, device and installation identifiers, IP address, connection information, country or region, local time information, push tokens, errors and crash reports.
• Usage and campaign data. Screens, actions, onboarding and paywall events, purchase events and campaign details. We filter health values and message content from marketing and general analytics event parameters. These events can be linked to the app user identifier.
• Support. Your email address, message and any information that you send with a request.

2. How we use data

We use data to provide accounts, restore access, save drinking records and goals, show progress, generate chat replies, verify subscriptions, send reminders when enabled, provide support, find errors and protect the service. We also use usage and campaign data to understand app use and measure marketing results. Reply reports help us review content problems. We use the limited deletion marker described below to stop late service events from restoring deleted records.

Where data protection law applies, we use the legal basis that fits the purpose: provide the service you request, meet a legal duty, protect legitimate interests such as service security, or obtain consent where required. A privacy policy does not replace a separate consent that the law requires. You can contact us to ask which basis applies to a specific use.

3. AI processing

AI is optional. Before AI processing, the app asks you to allow the personal-data use described in its AI notice. You can continue habit tracking without AI. The current consent applies to user chat and automatic AI messages, including safety review and memory extraction. In chat, select Turn off AI to stop future AI requests after the server saves your choice. A request already sent to a provider can still finish. Turning off AI does not erase earlier chat, memories or provider copies; use account deletion or contact support to request further removal.

AI features send information from our Firebase service to OpenRouter and the model provider that processes the request. This can include your message, earlier conversation, first name, drinking goals and recent drink history, intentions, selected onboarding answers, saved memories, progress and relevant subscription state. AI can also create short closing messages during app flows.

For the default OpenAI GPT-4o mini model, OpenRouter currently lists qualifying endpoints operated by Microsoft Azure. The processing provider can change, but our requests allow only endpoints that meet the restrictions below.

AI replies can be wrong. They are not medical advice. Do not put passwords, payment details or another person's private information in chat. Our requests require OpenRouter to use inference endpoints classified as zero data retention and exclude providers that use request data for training. If no qualifying endpoint is available, the AI request fails. These requirements apply to user chat, automatic messages, safety review and memory extraction. See OpenRouter's zero data retention information.

These restrictions apply to model processing. They do not delete our saved chat, memories, consent choices or reply reports, or all technical, account and billing records held by services. OpenRouter and providers have their own policies. Read the retention and deletion section below for the records that we keep.

4. Services that receive data

Optional services operate only when configured and available. A service listed here is not necessarily enabled in every app version or session.

• Google Firebase and Google Cloud provide authentication, database storage, server functions, notifications, hosting, analytics and crash reports.
• RevenueCat manages purchase validation, subscription access and purchase records. The app can share its Firebase analytics identifier, Adjust identifier, campaign details, app and account attributes, and linked-account name and email with RevenueCat. This supports customer records and connects purchase and campaign reports.
• Adjust, when configured, receives install, device, campaign and selected event data to measure marketing. Connected advertising partners can receive campaign or conversion data under the integration settings and device permissions.
• Meta (Facebook), through configured SDK features and advertising integrations such as Adjust, can receive technical device, app, install, advertising identifier and campaign information to measure advertising results. The data depends on the integration and device tracking permissions.
• OpenRouter and qualifying providers with zero data retention, including Microsoft Azure for the default OpenAI GPT-4o mini model, process AI requests as described above.
• Google Play and Google sign-in handle purchases or linked sign-in under their own policies.

We can disclose information when law requires it, to protect rights or safety, or as part of a business transfer subject to applicable law. We do not offer your private drinking history or chat as a product for sale. Advertising measurement can still count as sharing under some privacy laws. Contact us about the rights that apply to you.

5. Device permissions and choices

You can change notification permission in device settings. You can manage advertising ID and ad privacy settings in Android settings. Email sign-in and linking a sign-in provider are optional. You can refuse the AI notice or turn off AI in chat. The app does not currently provide a separate switch for general analytics or crash reporting. Device advertising or tracking settings do not stop all service data flows. Contact us to ask about access, deletion, objections or other privacy choices. We will explain available options and any limits.

6. Storage, security and transfers

App data is stored on your device and in our Firebase service. Service providers can process data in countries other than your country, including the United States. Data protection rules can differ. We use access controls and encrypted network connections to help protect data. No system can guarantee complete security. Ask us for information about safeguards that apply to an international transfer.

7. Retention and deletion

Active account records, drinking history, settings and chat remain until you delete the account or we remove them. We have no fixed automatic expiry for these account records. Service logs, purchase records, analytics, crash reports, backups, support messages and AI provider records can remain under provider retention settings or for legal, security, billing or dispute needs. We do not promise a single retention period for all providers.

The in-app account deletion function removes your main Firebase user record and its related data, including drink entries, intentions, progress, chat, saved memories, AI consent choices and reply reports, then deletes the Firebase sign-in account and clears app storage on that installation. It does not automatically erase every record held by analytics, crash reporting, RevenueCat, AI providers or the app store. Separate billing event records can also remain. We keep a limited technical deletion marker with the Firebase account identifier and deletion time. It prevents late events and in-flight work from restoring deleted account data. There is no fixed automatic expiry for this marker; contact us to ask about its retention. Send a data request so that we can review further deletion with the providers that we control. We will explain what can be removed and any reason for retention.

Account deletion and app removal do not cancel a subscription. Cancel through Google Play. Read the account and data deletion instructions for both in-app and email requests.

8. Your rights

Depending on your location, you can ask for access, correction, deletion or a copy of personal data. You can also ask to restrict processing, object to certain uses, withdraw consent, or opt out of sale or sharing where those rights apply. You can complain to your local data protection authority. Send requests to support@hapiga.com and identify Sippy and Android. We may need information to find your account and verify the request. Do not send a password or sign-in token. We respond within the time required by applicable law.

9. Adults only

Sippy is for people aged 18 or older. It is not intended for children. If you believe that a child gave us personal data, contact us so that we can review and remove it.

10. Website and policy changes

These legal and support pages contain no advertising, analytics script or account form. Firebase Hosting can process technical request data to deliver them. We update this page when our practices change and show the date above. We provide additional notice or request consent when required.

11. Contact

Hapiga Vietnam Company Limited
Sippy for Android
support@hapiga.com