Privacy Policy

1. Scope

This policy covers the HomadeBar iOS app provided by Yixuan Fu and this website. HomadeBar concerns cocktails and alcoholic drinks, is not directed to children, and does not encourage underage or excessive drinking.

The current version contains no advertising, behavioral analytics, or crash analytics SDK and does not sell personal information or track people across apps or websites. Content and activity push is available in this release. It is off by default and registers only after you explicitly turn it on under Profile → Notifications and grant system notification permission. Registration processes device push identifiers (a Tencent Cloud RegistrationID and an Apple APNs device token); it does not include your recipes, inventory, photos, or account details. You can turn it off in the same place at any time, or withdraw notification permission in System Settings.

2. On-device data and permissions

Recipes, ingredients, stock lots and adjustments, mixing records, shopping information, venue check-ins, party plans, profile name, avatar, theme, language, and preferences are stored on device by default. Local basics work without sign-in; private sync, brand collaboration, and some member features have separate requirements.

Camera, photos, location, and maps

The camera is used only when you take a bottle, recipe, or avatar photo. Library selection uses the system photo picker. Selected images are cropped, recognized, or composed on device; relevant images may be uploaded to private CloudKit when private sync is on or to a shared brand zone when added to a brand recipe.

While using nearby venues or check-in, the app uses location for positioning, search, and the place you choose to save. Apple Maps may process location, searches, device, and network data under its privacy notice, so we do not claim that location never leaves the device.

3. Private iCloud sync

Members can opt in when the device is signed in to iCloud, CloudKit is available, and a network connection exists. Once enabled, the app automatically uploads and merges recipes, ingredients and inventory, stock adjustments, mixing records, parties, check-ins, profile, preferences, deletion markers, and related images; each upload does not require a separate action.

Turning sync off stops future automatic sync but keeps local data and does not delete an existing cloud copy. Restoring on another device requires the same iCloud account, sync enabled again, and connectivity. Data that was never synced or had not finished uploading cannot be guaranteed to restore.

4. Brand collaboration

Brands use Apple CloudKit sharing for recipes, images, brand details, and members’ stable account identifiers, names, and roles. Owners manage the brand, members, and content; collaborators with active membership can edit; visitors are read-only. Access is limited to authorized participants and is not a public community.

Leaving removes your access and local brand copy while the owner’s shared content remains. Only an owner can dissolve a brand, which requests deletion of its cloud zone and share. If CloudKit or the network fails, the app reports failure and does not present local removal as successful cloud deletion.

5. Sign in with Apple, purchases, and reminders

The app stores Apple’s stable user identifier and the name or relay email first authorized by you to identify the HomadeBar account, brand identity, and account-linked membership. Your HomadeBar sign-in, device iCloud account, and purchasing App Store account serve different purposes.

Apple handles payment, renewal, and refunds. The app reads product, transaction, expiration, and entitlement information and uses an account-linked identifier to match access; it does not receive card numbers or complete payment details. Members can set an expiry date and lead time on a stock lot. The app schedules a local notification from on-device inventory data, subject to system notification permission granted under Profile → Notifications. When membership ends, expiry notifications stop; expiry dates on stock lots and the expiry widget are kept, and reminders resume automatically from the existing dates once membership is restored. This is separate from remote content push.

6. Support contact

When you email us, we process your address, description, and any redacted screenshots or files you choose to attach to investigate, reply, and handle privacy requests. The app does not automatically attach device IDs, logs, inventory, or private recipes. Never send passwords, verification codes, payment data, or certificate private keys.

Support: [email protected]. Google Gmail transmits and stores the message; see the Google Privacy Policy.

7. Retention, deletion, and withdrawal

• Sign out removes the local Apple identity and brand cache, not local personal content, private CloudKit data, or the Apple subscription.
• Delete Account first requests deletion of owned brand zones, leaves joined brands, and deletes the private sync zone. After cloud deletion succeeds, it also clears local recipes, inventory, check-ins, parties, profile data, and photos. The subscription must be canceled separately.
• Leaving affects your access; dissolving affects the full owner-controlled brand zone. Other devices’ caches and Apple backups remain subject to their sync state and Apple retention.
• Deleting the app normally removes local app data but does not automatically remove CloudKit data, support email, or an App Store subscription.

You can withdraw camera, photo, location, or notification permission, turn off private sync, and use the account screen for deletion. Email [email protected] for access, correction, or deletion requests. Provider security, legal, and backup retention may delay deletion from backups.

8. Third parties and website logs

• Apple: Sign in with Apple, CloudKit, StoreKit, and the APNs system notification channel.
• Apple Maps: maps, location, nearby place, and route requests.
• Website hosting: this site is served by hosting we operate or engage. It may log IP address, request time, URL, and browser or device information for delivery, security, and abuse prevention. We do not use these logs for app behavioral analytics.
• Tencent Cloud (TIMPush): used only after you turn on notifications, to register a device push identifier and deliver content and activity notifications. It may process the device push identifier, device and network technical information, and delivery records. Turning notification permission off asks the app to unregister.
• Google Gmail: support messages and attachments you send.

9. Changes

Effective September 9, 2026. We will update this page and use an in-app notice, product page, or system permission flow as appropriate before a material new practice begins. Remote copy changes do not replace required choice or review.