Your household information.

House Beasley at housebeasley.com is a personal household application operated by Michael Beasley for two approved users. Contact beasleybytes@gmail.com about privacy, access, or deletion.

Information we use

Google sign-in provides your verified email, name, and basic profile information. House Beasley uses your email to authorize access and determine which lists you can see. With your consent, House Beasley accesses event titles, dates, times, descriptions, and locations from the configured Google calendar, and sends new event information to Google when you add an event.

House Beasley also stores information you enter, such as tasks, house notes, uploaded files, people and birthday details, shopping and gift lists, and income and expense amounts. Optional push notifications store a device subscription and reminder preferences.

Connecting Contacts is optional and read-only. You can preview names, birthdays, email addresses, phone numbers and postal addresses from your Google Contacts, then select which to import. Only selected contacts are saved as shared household People profiles visible to both approved users. Contact previews are not saved automatically. Imports can fill empty fields of existing people without replacing your notes and interests.

How information is used and shared

Information is used to provide the household dashboard, calendar integration, list permissions, and reminders. Private lists are available only to their owner. Shared records are available to both approved household accounts. Information is not sold, used for advertising, or used to train AI models.

Vercel hosts the application, Neon provides its PostgreSQL storage, and Google provides authentication, Calendar and optional Contacts services. Optional notifications use your browser’s push service. These providers process information needed to deliver those services; hosting services may process operational request logs. House Beasley does not send household content to an AI assistant.

Storage and security

Household records and uploaded files are stored in the application database. Google connection credentials are encrypted in the database and used server-side; older Calendar sessions migrate from encrypted HTTP-only cookies. Credentials are not returned to client JavaScript. Calendar results are retrieved from Google for display rather than saved as household records. Authentication cookies keep you signed in; browser storage keeps display and reminder preferences. Access controls restrict the dashboard to the two approved emails.

Your choices and deletion

Signing in connects Google Calendar. Contacts remains optional. Settings lets you disconnect either service for your account; Calendar connects again when you next sign in. This removes the saved connection credentials but preserves existing events and imported people. You can delete imported people separately, or revoke the app’s Google permission in your Google Account.

You can edit or delete household records through the dashboard. Deleting a record with uploaded attachments also removes its associated attachments. Records remain until you delete them; signing out or revoking Google access does not delete saved household records. Contact the owner for account-related deletion requests or information that cannot be removed through the interface. Infrastructure logs or backups may remain subject to provider retention.

You can revoke House Beasley’s Google access in your Google Account settings and disable push reminders in House Beasley settings. Events created in Google Calendar remain there after you sign out or disconnect; manage them in Google Calendar. The household JSON export excludes uploaded file contents and Google events.

Google API data

House Beasley’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Changes

This page will be updated if House Beasley’s data practices change. The date above identifies the latest revision.