Privacy Policy

This policy applies to:

• The H2O website at henhoonline.net.
• The H2O mobile application.
• H2O features, including profiles, posts, comments, photos, messages, friends, dating, appointments, and subscriptions.
• Interactions between users and H2O, including support requests.

H2O collects the categories of information described below. Information you add to your H2O profile is separate from the basic account information received when you sign in with Google.

H2O uses information to:

• Create, authenticate, and manage your account, including Google Sign-In and the other sign-in methods described above.
• Provide dating, social, search, and messaging features.
• Display your profile and content according to the feature and your settings.
• Suggest other users.
• Verify email addresses and support optional two-factor authentication.
• Review uploaded images and filter prohibited text.
• Prevent fraud, spam, and abusive or fake accounts.
• Protect users and the community.
• Send service notifications and service-related email.
• Measure and improve the service.
• Show advertisements on the website.
• Process subscriptions and related purchases.
• Respond to support requests, disputes, and complaints.
• Comply with legal requirements.

H2O is a community and dating platform. Information in your profile, and content you post, may be visible to other users.

Information that may be displayed includes:

• Display name.
• Age, where the product shows it.
• Gender.
• Profile photos.
• Area of residence or hometown, where the product shows it.
• Bio or personal description.
• Interests.
• Other profile indicators the product displays with your profile, such as like counts.

Consider what you share on your profile and in posts before you publish it.

Some details can be limited by settings, including whether your birthday, age, or online status is shown and whether your profile can be found in search. What another person sees depends on those settings and the feature they use.

H2O stores messages on its servers so it can deliver chat between participants and keep conversation history available in the service.

Messages are not end-to-end encrypted. Because they are stored by H2O, H2O can access message content.

Before a text message is saved, H2O checks it against H2O's prohibited-content rules.

H2O may access stored messages, including images and voice messages, when needed to:

• Operate the chat feature for the people in the conversation.
• Investigate reports and complaints.
• Address spam, fraud, or abuse.
• Protect the service and the community.
• Comply with law or a request from a competent authority.

To protect accounts and the community, H2O may:

• Verify email addresses. An email received through Google Sign-In is treated as verified.
• Offer optional two-factor authentication by an email one-time code or an authenticator app.
• Run automated checks on images you upload, including profile photos and post images.
• Have staff review content that an automated check flags for review.

H2O does not collect a government identity document for account verification, and it does not verify a phone number with a separate phone-verification code. A phone number is stored only if you add it to your H2O profile.

Verification and security information is used to authenticate users, review uploaded images, and protect the service.

H2O runs automated checks on its own systems to:

• Check uploaded images for nudity or sexual content and, where that check is used for a profile image, whether a face is detected.
• Detect QR codes in uploaded images.
• Filter prohibited language in posts and messages.
• Limit abusive sign-in, messaging, and other high-volume activity.

These checks can support decisions such as holding content for review, removing content, or restricting an account. H2O does not use a separate deepfake-detection service.

H2O uses these providers for the purposes stated:

• Firebase Authentication and Google Sign-In, to authenticate users.
• Sign in with Apple on the iOS app, to authenticate users who choose Apple.
• Google reCAPTCHA, to check website sign-in and sign-up for abuse.
• Cloudflare R2 and the media address cdn.henhoonline.net, to store and deliver photos and other media.
• Google SMTP, to send service email from [email protected].
• Google Tag Manager and Firebase Analytics, to measure use of the website.
• Google AdSense, to show advertisements on the website.
• Firebase Cloud Messaging, to deliver push notifications to devices that register a token.
• Apple App Store and Google Play, to process subscription purchases in the mobile app.
• Telegram, where H2O provides payment instructions for a subscription purchase.

These providers process information as needed to perform those functions. H2O does not sell personal information.

H2O does not sell users' personal data.

H2O shares information in the situations below.

The Google user data H2O receives is limited to the authentication information in section 2.4: a Google and Firebase user identifier, the Google account identifier, email address, display name or name, and a profile picture if Google provides one. H2O stores the Firebase user identifier, the Google account identifier, the email address, the display name, and a record that the account signed in with Google. When an email address is present, H2O marks it verified.

H2O needs this information to authenticate you, create your H2O account, associate the Google-authenticated identity with that account, let you sign in later, and maintain and secure the account.

This information is stored in H2O's application database. Firebase Authentication also holds the authentication record, which can include the email address, name, and profile picture URL if Google provides one. H2O does not save that profile picture as your H2O profile photo.

H2O does not sell Google user data and does not use Google Sign-In data for advertising. H2O does not share it with data brokers. Firebase Authentication processes it to perform sign-in. If H2O sends a service email to the account email address, Google SMTP processes that address to deliver the message. Website analytics and advertising tools described in the cookies section collect their own browser data. H2O does not send those tools the Google account profile received at sign-in.

H2O keeps Google authentication information while the H2O account is active. When you delete the H2O account, H2O deletes the Firebase Authentication user, clears the email stored on the H2O account, and removes the stored Google sign-in association. Sections 13 and 14 explain other information that may remain.

H2O's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. H2O uses that information to provide and secure the authentication and account features described in this policy.

This table summarizes the main categories of information H2O handles, why each category is used, and who can see or process it.

H2O applies reasonable technical and organizational measures to protect user data, including:

• Encryption of data in transit.
• Access controls.
• System logs.
• Security monitoring.
• Backups.

No method of transmission or storage is absolutely secure.

Messages and profile content are not end-to-end encrypted. Deleting an account does not instantly erase every backup or stored copy.

H2O does not apply one retention period to every category of information:

• Active account data is kept while the account remains active so H2O can provide the service.
• User-generated content, including posts, comments, and messages, is kept while it remains on the service. H2O does not publish a fixed deletion period for that content.
• Authentication information is kept while the account is active. The Firebase Authentication user is deleted when the H2O account is deleted.
• Security and log information is kept as needed for security, fraud prevention, and troubleshooting. Some short-lived security and session records expire automatically. H2O does not publish a fixed retention period for logs.

After an account is deleted, some information may remain as described in section 14.

You can delete your H2O account in the product:

• On the website, open your profile, open the profile menu, choose Delete Account, and confirm.
• In the mobile application, open Settings, open Account, choose Delete account, and confirm.

You can also request deletion by emailing [email protected].

When an account is deleted, H2O marks the account deleted, clears the stored email, removes the stored sign-in provider association, deletes the Firebase Authentication user, and blocks further sign-in to that account.

H2O does not immediately erase every copy of profile information, posts, messages, media, or backups. Some information may be retained where necessary for legal compliance, fraud prevention, security, dispute resolution, and legitimate record keeping.

You may:

• Access your personal data.
• Update your profile information in the product.
• Ask H2O to correct inaccurate account information.
• Delete your account as described in section 14, or ask H2O to delete it.
• Ask H2O to restrict processing where the law provides that right.
• Withdraw consent for a processing activity that depends on consent.

These requests may be limited where the law allows, or where H2O must keep information for security, fraud prevention, or legal compliance.

H2O and the website tools it uses rely on cookies and similar technologies to:

• Keep you signed in.
• Remember preferences, including your time zone.
• Measure website use through Google Tag Manager and Firebase Analytics.
• Show and measure advertisements through Google AdSense.

You can control cookies in your browser. If you block cookies, some features may not work.

More detail is in the Cookie Policy:

H2O is intended only for people aged 18 and older.

H2O does not knowingly collect personal information from anyone under 18.

If H2O identifies an account belonging to someone under 18, H2O may lock or delete that account.

H2O uses providers that may process information in countries other than the country where you live. In particular, Google and Firebase, and Cloudflare, may process information in the countries where those providers operate.

Those providers process the information for the purposes described in this policy, including authentication, email delivery, media storage, website measurement, and advertising on the website.

If H2O is involved in a merger, acquisition, restructuring, or transfer of all or part of its business, user information may be transferred to a successor that continues the service, as permitted by applicable law.

H2O may update this Privacy Policy from time to time.

If H2O makes a significant change, H2O will provide notice through the website, the application, or the email address on the account.

The updated policy applies to continued use of H2O after it is posted.