HOUSEHOLD CONTINUITY

Privacy And Your Household Information

Updated October 20, 2026

Limited Preview: use sample household details until real-information use is approved. This service is not yet your backup or emergency fallback.

This notice describes the service as it works today. Operator: Anthony Cammarano (Florida, USA). For privacy questions or requests, contact housecon13@gmail.com.

What We Store And Why

• Account and session information: your email, account ID, confirmation/recovery state and authentication sessions, used to sign you in and control access. Supabase Auth handles account credentials; household fields are not password storage.
• Your shared plan: household and member names entered, tasks, schedules, linked bills/instructions, reviews, practice notes, dated progress, cover requests and takeover observations. These let two adults coordinate and prepare handoffs.
• Access and change records: invitation records, emergency drill designations/grants/events, acting account IDs and timestamps. Private support metadata records successful plan-change areas, item IDs and revisions without names, emails, instructions or note bodies.

Do not enter unsupported secrets or sensitive records. Read What To Store for examples and limits.

Who Can Access A Shared Plan

Both active household accounts can read/edit the shared plan and delete individual items. Only the owner can rename/delete the household or revoke the other account. Named household members do not create sign-in accounts. An emergency designation is a separate limited drill; it does not grant household membership. Necessary service administrators and infrastructure providers may process information to operate, secure and support the service.

Revocation stops future authorized access. It cannot recall screenshots, exports or information someone already copied. The service is not end-to-end encrypted against its operator, and the operator can access stored content through privileged administration. Do not treat the shared plan as a secret vault.

Where Information Is Processed

Supabase provides the shared database and authentication. The configured database region is AWS us-east-1 (North Virginia, USA); plan: Supabase Free. Vercel hosts the website and server functions. Providers may process delivery, security and service information in additional locations under their own terms; the database region is not a promise that every operation stays there.

Earlier local tools and the Parker sample store their separate drafts in your browser. We do not automatically import those drafts into your online household. Exports and feedback downloads are files on your device; feedback is shared only when you choose to send it.

Usage Collection, Cookies And Logs

This release collects no optional product analytics. There is no product-event delivery, session replay, screen recording, advertising tracking or automatic content capture in the application. Existing optional usage preferences do not activate collection. A future change would need an updated notice and a separate explicit opt-in.

Authentication/session cookies and local preferences still support the service. Security/access records and provider operational logs are separate from optional analytics and may include account/request metadata and errors. Do not send private information in page URLs. We do not intentionally put household content or authentication links into application alerts or logs; provider-side settings and retention are separate.

We do not sell household information or use it for targeted advertising. Shared household content is not sent to an AI service by this application.

Backups, History And Retention

Current backup availability/retention: No managed production backups are configured. A production backup schedule and retention period have not been established. A production database restore has not been tested for this service. A household download is not an automatic backup or restore. Keep an independent, securely stored copy of essential instructions and do not rely on this preview as your only copy.

Your active plan stays available until you remove items or delete the household, subject to service limits. The app is not a permanent audit archive: a new takeover replaces the previous takeover; each task retains one previous differing takeover note; repeating dated updates and orphaned updates can be pruned near storage limits. Old terminal cover requests are pruned when a new request is created. Private support metadata older than 180 days is removed on the household’s next successful write, so idle households can retain it longer. Provider logs/backups have their own retention; we do not promise an unverified expiration period.

Export, Deletion And Requests

The owner can download the shared plan and delete the household in Household Settings. That deletion removes the online shared household and its related cover/drill/support records, while leaving sign-in accounts and separate browser-local data in place. Removing a named person does not revoke a real account. Delete local drafts and downloaded files separately on your devices.

Contact housecon13@gmail.com for account removal, correction/access questions or prior optional usage-data requests. We verify account control before changing access. We will explain what can be removed, any applicable retention and what remains outside our control. Copies already downloaded or retained in provider backups/logs cannot necessarily be removed immediately. Do not send passwords, recovery links or a household export by email.

Email, Payments And Changes

Account confirmation/recovery emails support sign-in. Household invitations and the emergency drill do not automatically send an email. Optional cover-email delivery is not enabled for this release. Payments are disabled; existing households will never be automatically enrolled or charged. The proposed subscription is not an active purchase.

Material changes to collection, sharing or supported information will be described here before the new behavior is enabled. We will not treat continued use of the preview as permission to activate billing or optional analytics.