CasaLife LLC

Privacy Policy

Effective date: July 15, 2026

Last updated: July 15, 2026

CasaLife LLC ("CasaLife," "we," "us," or "our") provides CasaLife, a household intelligence service that helps invited members capture information, organize household context, connect calendars and email intake, and use Ask Casa. This Privacy Policy explains what information CasaLife handles, how it is used and shared, and the controls available during the founder-only pilot.

The CasaLife Terms of Service govern use of the Service.

1. Scope and pilot status

This policy applies to the CasaLife website and authenticated Production service at casalife.app. Production access is currently restricted to an allowlisted founder household. Public signup and activation for additional households are not enabled.

The public Demo uses fictional data and simulated provider fixtures. It is separated from Production and is not intended for real personal, household, email, calendar, or credential data.

2. Information CasaLife handles

Account and household information

CasaLife handles account and profile information such as name, email address, authentication identifiers, household membership, invitation status, and role. Household roles may include owner, adult, teen, child, guest, or service roles. Authorization is based on an authenticated, active household membership.

Member-provided household content

Members may provide notes, captures, voice recordings, documents, images, receipts, tasks, events, reminders, questions to Ask Casa, approval decisions, and other household information. CasaLife may create structured records, relationships, summaries, proposals, receipts, and audit events from this content.

Unsynchronized capture drafts may remain on the member's device until CasaLife confirms server receipt or the member deletes them. After confirmed synchronization, the local raw copy is removed as designed and the server copy becomes the authorized record.

AI requests and results

When an authorized member uses Production AI features, CasaLife may send the member's request and the limited, authorized household context needed to answer it to the OpenAI API. CasaLife also handles the returned answer, structured tool requests, proposed actions, usage counts, model name, latency, success or failure class, and estimated cost.

CasaLife configures OpenAI Responses API requests with store: false. OpenAI still processes request content as needed to provide the API response under its applicable terms and policies. CasaLife does not use AI output as authority to bypass household permissions, approvals, or provider consent.

Email intake

When a member forwards or sends email to a CasaLife intake address, CasaLife may handle the provider message identifier, routing address, sender and recipient information, subject, message body, forwarding provenance, timestamps, and attachment metadata or bytes. The current provider is Resend.

Email intake is routed only through an active, household-bound opaque address. Operational telemetry is designed to exclude message bodies, attachment contents, and sender addresses. During the founder pilot, attachments are treated as unscanned, kept private, and quarantined; ordinary member download or open access is not enabled.

Connected calendar information

For calendars a member chooses to connect, CasaLife may handle provider account identity, calendar names and identifiers, selected calendars, read/write capability, event titles, descriptions, locations, attendees, dates and times, time zones, recurrence, cancellation and update status, provider event identifiers, sync cursors, source health, and source provenance.

CasaLife supports the following connection methods:

Google Calendar: OAuth access using calendar-list read access and calendar-event access.
Microsoft Calendar: Microsoft identity OAuth using delegated Calendars.ReadWrite access plus sign-in and offline-access scopes.
Apple/iCloud Calendar: when available, an Apple-supported Apple Account authorization flow. CasaLife does not request or accept an Apple Account password or an app-specific password for Calendar access. This connection remains unavailable while CasaLife completes the required provider registration and implementation.
ICS/webcal: a member-provided private feed URL. These feeds are read-only in CasaLife.

Google and Microsoft access and refresh tokens, any future Apple authorization grant or token, and private ICS/webcal URLs are treated as credentials. They are stored through server-side protected credential references and are not included in client bundles, calendar records, ordinary browser responses, or content-bearing operational logs.

Technical, security, and operational information

CasaLife may handle request and correlation identifiers, timestamps, environment, provider, connector status, retry and duplicate state, rate-limit state, error classification, worker health, and bounded counts needed to operate, secure, and troubleshoot the service. Content-free audit records may record actions such as connection, synchronization, visibility changes, approval, deletion, revocation, or Undo.

3. How CasaLife uses information

CasaLife uses information to:

authenticate members and enforce household isolation;
provide captures, calendar, email-intake, Today, Ask Casa, approval, receipt, and Undo features;
discover and synchronize calendars selected by a member;
normalize, deduplicate, and connect household information;
generate AI-assisted answers and proposed actions;
perform an approved event write to the destination calendar selected by the member;
apply privacy, role, and visibility choices;
maintain connector health, retries, auditability, security, and incident recovery;
prevent abuse, cross-household access, duplicate processing, and unauthorized external actions; and
operate and improve the founder pilot based on authorized use and feedback.

CasaLife does not sell member personal information or use household content for third-party targeted advertising.

4. Household visibility and roles

Household information is not automatically visible to every household member. The available control depends on the feature.

Calendar sources support separate audience and detail controls:

audience: private to the connected member, visible to selected adults, or visible to the household; and
detail: full details, title and time only, or busy/free only.

Microsoft work calendars default to busy/free detail. Work-calendar details are not shown to child, teen, guest, or other members without an explicit authorized configuration. Selected-adult visibility is limited to the adults chosen for that calendar.

Other captures default to the connected member where implemented and may be promoted to household visibility only through an explicit control. Household owners may administer membership and certain connectors, but ownership does not override member-specific visibility unless the product expressly provides an authorized administrative path.

Members are responsible for choosing appropriate household sharing settings, especially for work, school, medical, financial, or other sensitive information.

5. When information is disclosed

CasaLife may disclose information in these circumstances:

Within the household: according to the member's audience, detail, role, and sharing choices.
To service providers used to operate CasaLife: for example, Supabase for authentication, database, and private storage; Netlify for application hosting and runtime; OpenAI for authorized AI processing; and Resend for email intake. These services process information only as needed for the applicable CasaLife function and under their own applicable terms and policies.
To connected calendar providers: when CasaLife reads a selected calendar or performs a member-approved write or Undo through Apple, Google, Microsoft, or the operator of an ICS/webcal feed.
At a member's direction: when the member connects a provider, selects a calendar, changes household visibility, approves an external action, or otherwise directs a disclosure.
For safety, security, or legal reasons: when reasonably necessary to protect CasaLife, members, or others; investigate misuse; enforce applicable terms; or respond to valid legal process.
In a business transaction: if CasaLife is involved in a financing, reorganization, acquisition, or transfer, subject to appropriate protections and applicable notice requirements.

CasaLife does not require a personal calendar to be public and does not copy personal events into a CasaLife-owned provider calendar.

Connected personal calendars remain owned and controlled by the member and the original provider. Connecting a calendar does not transfer ownership to CasaLife.

6. Provider access, disconnection, and revocation

Members connect their own provider accounts through the normal CasaLife connection flow. A pause stops scheduled connector activity without necessarily deleting existing CasaLife records. A disconnect marks the connector revoked and removes its active CasaLife credential reference. Google or Microsoft access may also be revoked through the provider. When Apple Calendar authorization becomes available, its grant may be revoked through Apple Account Data Sharing. An ICS/webcal feed can be deleted or its source URL changed by the member.

Revoking access at a provider stops future authorized access but does not by itself delete CasaLife records already created from prior authorized synchronization. Members may use available CasaLife deletion controls or contact CasaLife for pilot support.

7. Retention and deletion

CasaLife does not currently promise a fixed retention period. Information is retained while needed to provide the founder pilot, maintain authorized household context, support receipts and auditability, operate connectors, address security or reliability issues, or meet legal obligations.

Available deletion behavior depends on the record:

deleting an eligible capture removes its raw text and private voice object and removes unapproved processing content;
a minimal, content-free audit tombstone may remain, and an explicitly approved derived outcome may retain reduced, non-content approval provenance;
archiving hides a capture from active work but does not delete its raw content;
deleting an unsynchronized local capture removes that device copy;
disconnecting a calendar connector removes the active CasaLife credential reference but does not automatically erase previously synchronized records; and
provider-side deletion or revocation is controlled by the provider and may need to be performed separately.

A complete self-service account export or account-deletion workflow is not represented as available during the current pilot. Members may contact CasaLife to request assistance with data access or deletion. CasaLife will explain what can be deleted, what has already been deleted, and what limited content-free or approved-action records must remain rather than silently overstating deletion.

8. Security

CasaLife uses technical and organizational safeguards designed for the founder pilot, including authenticated server boundaries, active-household authorization, database row-level access controls, private storage, server-only provider credentials, scoped Production environment variables, audit events, rate limits, kill switches, and approval requirements for supported external writes.

No method of storage or transmission is completely secure. CasaLife does not guarantee that unauthorized access, loss, misuse, or technical failure can never occur. Members should protect their account, provider credentials, and devices and should promptly revoke access they no longer want CasaLife to have.

9. Children and teen household roles

The founder pilot is intended for invited adults. Children and teens cannot independently sign up. Child and teen roles are household permission labels managed by an authorized adult; they do not enable public or independent child signup. Adults are responsible for deciding what information about a child or teen is entered, connected, or shared and for configuring appropriate visibility.

CasaLife does not knowingly invite a child to create an independent founder-pilot account. If information about a child was provided without appropriate adult authorization, contact CasaLife so the issue can be reviewed.

10. Choices and rights

Depending on the feature, members may be able to review or change profile information, calendar selections, calendar audience and detail levels, connector pause state, provider access, and eligible content. Additional privacy rights may apply based on a member's location. During the pilot, requests may be sent to the contact below. CasaLife may need to verify the requester's identity and household authority before acting.

11. Changes to this policy

CasaLife may update this policy as the pilot, product, providers, or legal requirements change. The published policy will show its effective date. Material changes will be communicated through an appropriate member-facing method before they take effect when required.

12. Contact

Questions, requests, or concerns about this Privacy Policy or CasaLife’s handling of personal information may be sent to:

CasaLife LLC

Email: privacy@casalife.app

Website: https://casalife.app

CasaLife may need to verify the requester’s identity, account, household membership, or authority before responding to a request involving personal or household information.