Privacy Policy

What HardBeet collects

• Email address or phone number used for sign-in. HardBeet does not show either to approved connections.
• Apple or Google account identifier and authentication data when that sign-in method is chosen. HardBeet does not receive the user's Apple or Google password.
• First name or display name if provided in the app.
• Expo push token for reminders and approved follower alerts.
• Daily check-in timestamps, including the most recent check-in time.
• Supporting signal timestamps and labels, such as app-open updates, coarse motion-triggered attempts, battery-state attempts, and background-task attempts.
• Approved connection records, optional private relationship labels a user adds to their own list, invite codes, check-in settings, preferred language, follower quiet-hours preference, pause state, alert status, and notification delivery records.
• Device platform information needed for push notifications and troubleshooting.

Manual check-ins and private diagnostics

Only an explicit tap on I'm here today creates a daily check-in. App opens, coarse motion, battery changes, and background attempts are private, best-effort diagnostics. They do not create a check-in, change loved-one status, or appear to approved loved ones.

If the phone is offline, a pending check-in time and timezone may be stored on that phone until delivery succeeds or the local queue is cleared. Approved loved ones cannot see it before the backend confirms it.

What HardBeet does not collect

• Live location or location history.
• Messages, call logs, photos, contacts, browser history, app names, or screen content.
• Health records, medical data, biometric values, or diagnosis information.
• Continuous raw motion history.
• Audio or camera data.

What approved loved ones can see

Approved loved ones can see whether the person has checked in today, the most recent daily check-in time, whether sharing is paused, and suggested next steps such as wait or ask the person to open HardBeet. Email addresses, phone numbers, and sign-in providers are not shown through connections.

Approved loved ones cannot see email addresses, phone numbers, sign-in providers, supporting signals, live location, private phone activity, messages, photos, apps, browser history, or health details.

How HardBeet uses information

HardBeet uses collected information to sign users in, maintain approved sharing agreements, show daily check-in status, send push reminders and alerts beginning 60 minutes after the chosen daily time, support pause controls, debug service issues, and protect the service from misuse.

HardBeet does not use SMS for product notifications. Users may sign in with email OTP, Apple, Google, or phone OTP where that option is enabled and delivery has been tested.

Service providers

HardBeet uses Supabase for authentication, database storage, row-level access controls, and backend functions. HardBeet uses Expo push notification services for push delivery. Apple and Google platform services may also process authentication when chosen, app installation, and operating-system notification information.

Push notification timing

Followers can choose normal delivery, silent delivery from 10 PM to 7 AM, or delivery held until 7 AM in their saved timezone. These preferences can delay or silence a follower alert and do not change the person's check-in status.

Retention and deletion

HardBeet keeps account, connection, invite, check-in, setting, push notification token, and notification records while an account is active and as needed to operate the service. Some records may be retained for troubleshooting, security, legal, or abuse-prevention reasons.

Users can start account deletion in the app from Settings > Privacy and account > Delete account. Users who no longer have app access can use the public deletion page.

Request account deletion

Children

HardBeet is intended for adults and family caregivers. It is not directed to children under 13.

Contact

Privacy questions can be sent to legal@gethardbeet.com.