Information Notice

Who operates HoHoHo

HoHoHo is provided by Arda Tor. You can contact us about your information at helphohoho@gmail.com. This notice explains the data flows in the HoHoHo application; the Privacy Policy is a separate document.

Accounts and device guest access

HoHoHo uses Google Firebase Authentication for account access. Google sign-in, and Apple sign-in on iOS, provide an account identifier and the name or email made available through the provider. The app uses these details to create or find your HoHoHo profile and connect you to your draws.

Guest access also creates or accesses a server account. It uses a device-related identifier: identifierForVendor on iOS or Android ID on Android. It is not a no-data or anonymous browsing mode. A guest account is tied to the device; access and transfer to another device can differ from a linked sign-in account.

Draws and profile information

Google Cloud Firestore stores HoHoHo account/profile records and draw records. These include account identifiers, a display name, email, optional gift hints, draw names, membership, organizer information, status and gift assignments. Profile records can also contain device and notification identifiers. Language and account/session information are also stored on the device.

You can choose to put interests, sizes or a delivery address in the gift-hints field. Do not add sensitive details or information about another person that you do not want to share. The result screen shows the selected recipient’s name and gift hints. Members can see the participant names in their draw. A person receiving a valid draw code can use it to join, so share codes carefully.

This describes how the app presents information. It is not a promise of end-to-end encryption or a guarantee that another participant cannot save, copy or share information they can see.

Service messages and purchases

HoHoHo uses OneSignal for notification-related functions. Notification identifiers and account-related details, including the account email, are passed to this provider by the app. Device notification permission controls whether notifications may be displayed. This is separate from the optional usage-and-diagnostics choice.

The app store and RevenueCat support the purchase options and entitlement records used for in-app support purchases. RevenueCat is initialized separately from the optional-sharing choice. Declining optional usage analytics does not switch off these purchase-related service functions.

Optional sharing and advertising

With your permission, HoHoHo enables Firebase Analytics and Mixpanel for usage information and Firebase Crashlytics for crash reports. The app uses a separate random analytics identifier and filters selected direct-identification properties from its analytics wrappers. This does not mean that all technical or network information is anonymous.

Optional advertising uses Google Mobile Ads/AdMob. Google’s consent flow, where required, runs before eligible ad requests. Depending on the choices you make and the ad service operation, ad requests, device/network information and ad interactions can be processed to deliver and measure advertising.

Sharing is optional. You can decline when asked or change Usage & diagnostics in Settings. Where available, advertising privacy options can also be opened in Settings. Withdrawing the optional-sharing choice stops future optional collection and ad loading through the app’s controls; it does not by itself delete your account, draw records or information already received by providers. Essential account and draw functions remain available.

A support ad is optional. You can continue without watching, and closing it early does not prevent you from seeing your gift assignment.

Your choices and requests

You can edit your profile and gift hints in Settings and use the account-deletion option there. The current app records a deletion request and removes authentication access. For requests about stored records or information already shared, contact helphohoho@gmail.com. We do not state a fixed deletion deadline in this notice.

For the broader privacy terms and contact route, read the separate Privacy Policy.