Privacy, without the guesswork.

Who operates this app

Dean & Dana HQ (“HQ”) is developed and operated by Home Based Daddy, LLC as a small, private household application. It is not a public calendar service and has no open registration. This policy explains the personal information HQ uses when an approved member connects a Google account or uses a paired household device.

Google Calendar information we access

• Read-only personal calendar access: When separately authorized, HQ retrieves selected calendar events and associated details, such as event titles, dates and times, and locations when present, to display on the family dashboard and phone view.
• Read-only free/busy access: When authorized through a personal Google account that can access a shared work calendar, HQ retrieves scheduled busy intervals. The work-availability feature is designed to use only those time blocks, not customer names, meeting descriptions, attendees, or meeting links.
• Separately authorized event creation: HQ can create an event on one selected personal Google Calendar after the phone user reviews and confirms it. The Google-owned-events permission itself can grant broader technical rights to view, create, modify, or delete events on calendars the account owns. HQ's application interface and server restrict that workflow to creating new events on the configured personal calendar only; editing and deleting existing appointments are not features of HQ.
• Account verification: During connection, HQ uses information needed to confirm that the intended Google account and authorized calendar were selected.

Calendar information is accessed only following Google OAuth consent. Revoking Google access stops future API retrieval or creation once that revocation takes effect.

Other information used by HQ

HQ stores household shopping items, quantities, preferred stores, purchase/checkoff history, named checklists, task due dates, and other household reminders that approved users choose to enter. It also maintains device-pairing records, session information, synchronization state, and calendar-save receipts to operate the app and avoid accidental duplicate events.

How we use this information

We use authorized data to show schedules and upcoming events, indicate scheduled availability, synchronize lists between household devices, create expressly confirmed personal calendar events, protect access, resolve synchronization errors, and maintain recoverable backups.

We do not sell household data, share Google Calendar data with advertisers or data brokers, use it for targeted advertising, or train generalized AI models on it. Information obtained through Google APIs is used only to provide or improve these user-facing features, subject to the Google API Services User Data Policy, including its Limited Use requirements.

Where information is stored and who receives it

The private HQ application is hosted through Railway. Approved household browsers/devices exchange data with that server over HTTPS. Google Calendar data travels between Google services and the private HQ backend when syncing or saving an approved event. Infrastructure providers necessarily process information required to host and operate the service; they are not given permission by HQ to use household calendar data for their own advertising.

The public informational pages you are reading are hosted on Netlify at homebaseddaddy.com. They do not themselves expose, fetch, or display your private household calendars or shopping lists.

Security, device copies, and access limitations

HQ uses approved-device pairing and protected sessions. OAuth credentials remain on the private server rather than in the public website or browser app. The service may maintain cached schedule information so the dashboard can load promptly. The home Frame can keep a recent local calendar/household view; the mobile app can optionally keep a read-only shopping snapshot for poor reception. These copies may remain on a device while it is offline. Revoking a device blocks future server access but cannot remotely erase a device that is disconnected from the internet.

Encrypted export bundles may be used for recovery, with their recovery keys stored separately. The active service's authorized credential files are held on the server and are not encrypted by that export mechanism while in use. We restrict access to the hosting account and household devices, but no system can guarantee absolute security.

Retention and deletion

Household records and calendar connection data are retained while needed for the private household service. Copies may also be held in operational or off-provider recovery backups. When a verified household member requests removal, the developer can remove the relevant live records and account tokens, then address backup copies as feasible under their applicable retention schedules. Revoking Google consent stops new access but does not automatically remove already cached or backed-up data.

To revoke Google's authorization, visit your Google Account third-party connections settings. To request review, export, correction, or deletion of HQ-stored information, contact the email below. Google Calendar events remain in Google Calendar unless the account owner deletes them there.

People with access

HQ is intended only for approved household users and their paired devices. The developer or authorized service operator may access information when necessary to maintain security, fulfill a user request, or restore the service. Information may also be disclosed if legally required.

Changes to this policy

If HQ's data use changes materially, we will update this page and seek any additional consent required before using Google data for new purposes. The effective date at the top will reflect the latest substantive update.