Privacy Policy

Last updated: September 8, 2026

At Familia, we believe trust starts with privacy. This policy explains what data we collect, why we collect it, and how we protect it.

1. Who we are

Data Controller and Provider of Familia is Asynq Labs LLC, 30 N Gould St Ste N, Sheridan, WY 82801 US.

For privacy questions, contact us at privacy@asynq.org.

2. How the product works without registration

Familia works even without account registration.

Household membership is tied to a device identity, so families can use core functionality immediately.

Signing in is optional in Settings and is mainly for backup/restore continuity (for example if a device is lost, replaced, or broken).

Sign-in options may include Apple ID and Google account, depending on the platform and release stage.

3. What data we collect

3.1 Household and app data

When you use Familia, we may process:

  • device identity and technical app identifiers
  • household and membership metadata
  • member metadata (for example display name)
  • agreement content and related metadata
  • plans, schedules, calendar event metadata, checklist/list content, photo attachment metadata, and related links
  • invitation metadata

Parents may invite grandparents and also children (typically teenagers 13+). For invited members, we only store minimal member metadata such as name.

Shared plan links

When you choose to share a plan, Familia creates a link containing two randomly generated codes. Anyone who has the complete link, including people it is forwarded to, can view the shared title, time, timezone, location and plan note without an account. Attachments and responsibilities are not exposed. We do not collect guest email addresses, upload contacts, or send invitation emails. You choose the guests in your device’s sharing interface; the selected messaging or email service handles delivery under its own terms.

The link shows current source-plan details and cancellation status. It remains accessible until revoked; ordinary plan deletion shows a cancelled event. Adding the event to Google Calendar sends the displayed details and link to Google when you follow that button. Google Calendar and iCalendar downloads save one-time copies. Within Familia, we store a link between the invitation, guest account, guest household and imported plan to synchronize the title, date, location, note and cancellation status. Accepting and importing confirms attendance without joining the organizer’s household. The organizer manages shared details; removing an imported plan cancels the guest’s attendance and notifies the organizer. Revoking the public link does not disconnect plans guests have already added. App Store download QR codes do not contain invitation codes.

We store guests’ names and attendance responses (accepted, declined or cancelled) and show them to the event organizer. Familia guests use their account display name; web guests provide a name. We do not show guest household names or email addresses to the organizer. A private random token lets each web guest manage their own response; its hash is stored on the server, and the browser stores the token locally and in the personal link. Calendar export is available after acceptance and includes that private link. Keep the link private, as anyone holding it can change your response. We use short-lived hashed invitation/IP counters to limit abusive submissions. Push services deliver attendance changes to organizers and event updates/cancellations to Familia guests, subject to device notification settings.

Availability booking

Smart and Founder organizers can store a weekly availability schedule, timezone, excluded periods and meeting details, and share a personal booking link. Anyone holding that link can see the organizer’s display name, public meeting details and available times. We calculate available times from the organizer’s plans, timed tasks and calendar events without publishing their private titles or busy-event details. A booking stores the guest’s name, selected time and a hashed private token, creates a private organizer plan and sends an attendance notification. If a guest opens their private invitation in Familia, they can link that response to their account while retaining their cancellation link. Ending a subscription pauses new bookings without deleting existing meetings.

3.2 Email data

Familia does not require an email address for core planning. Optional Google account features are described separately below.

On the website, we may collect an email address and optionally a first name only in forms where you explicitly provide them, such as a waitlist, platform availability notification, or feedback form. We use this data only for the stated purpose. Public promo and feedback forms may be recorded internally through Asynq Teams.

3.3 Operational telemetry

We may process minimal technical telemetry required for reliability, abuse prevention, and security.

We do not use advertising profiles or cross-site behavioral tracking.

3.4 ChatGPT and MCP-compatible assistants

If you explicitly connect Familia to ChatGPT or another MCP-compatible assistant, the assistant may receive Familia data needed to answer your requests or perform authorized actions.

Depending on the permissions you approve, this may include household names, member display names, tasks, agreements, plans, schedules, calendar event metadata, checklist/list content, photo attachment metadata, item IDs, household IDs, links back to Familia, and related notes, descriptions, dates, and locations.

Read-only access lets the assistant retrieve and summarize Familia data. Write access lets the assistant create, edit, or delete tasks, plans, lists, and attachments through Familia.

You can revoke MCP access from Familia. Data sent to ChatGPT or another assistant is also handled by that assistant provider under its own terms and privacy policy.

Google Calendar data is not included in MCP or assistant responses by default. It is shared with an assistant only when you explicitly enable Google Calendar access for that MCP token or OAuth authorization and confirm that the assistant provider, plan, or configuration does not use connected-app data to train generalized AI models.

3.5 Google user data

If you sign in with Google, Familia may process your Google account identifier and email address to link your Google account to your Familia account.

If you connect Google Calendar, Familia may access and store Google Calendar data from calendars you authorize and select, including calendar identifiers, calendar names, colors, event identifiers, event title, time, all-day status, status, location, description, event link, update timestamp, and related event metadata.

Familia uses Google Calendar data only to show selected external calendar events inside Familia, synchronize your family timeline, troubleshoot the integration, and provide functionality that you explicitly authorize.

OAuth access and refresh tokens for Google Calendar are stored encrypted on Familia's backend infrastructure.

3.6 Google data sharing, transfer, and disclosure

We do not sell Google user data. We do not use Google user data for advertising, credit, lending, data-broker, or cross-site profiling purposes.

We may share, transfer, or disclose Google user data only as follows:

  • Cloudflare processes Familia backend, storage, security, and infrastructure workloads where Familia data is hosted.
  • Google receives OAuth and API requests needed to authenticate your Google account and retrieve the Google Calendar data you authorized.
  • MCP-compatible assistant providers, such as ChatGPT or another assistant you explicitly connect, may receive Google Calendar event data only when you enable Google Calendar access for that MCP token or OAuth authorization and confirm that the provider, plan, or configuration does not use connected-app data to train generalized AI models.
  • Legal, security, or compliance recipients may receive data only when required by law or necessary to protect Familia, users, or the service.

Familia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

4. What we do not do

We do not sell personal data. We do not build cross-site advertising profiles. We do not use Google Workspace API user data to create, train, or improve generalized AI or machine learning models.

5. Cookies

We use only technically necessary mechanisms required for secure service operation.

6. How we use data

We process data to:

  • provide and operate Familia
  • synchronize shared household context
  • connect and synchronize Google account and Google Calendar integrations that you explicitly authorize
  • provide integrations that you explicitly authorize, including ChatGPT and MCP-compatible assistants
  • maintain security and prevent abuse
  • troubleshoot and improve service quality

7. Storage and security

We use technical and organizational safeguards, including encrypted transport and access controls.

No system is perfect, but we maintain a very high level of protection as we are used to from robust global systems.

8. Data retention

We keep data only as long as needed for service operation, legal obligations, and legitimate operational needs.

Data that is no longer required is deleted or anonymized.

Waitlist email data is deleted after one launch notification is sent.

Shared-link records are retained with the source plan. Revocation immediately prevents further access through the old link; ordinary source-plan deletion retains cancellation information for guests. Permanent erasure of source data also removes sharing associations and ends synchronization. Copies already saved or messages already shared remain under the control of their recipients. Creating a replacement link does not restore access through a revoked link.

9. Processors

We use a limited set of trusted processors:

  • Cloudflare (infrastructure and edge platform)
  • Cloudflare Workers AI (AI processing for smart capture and search features; Google Calendar data is not sent to Workers AI for generalized model training)
  • Resend (email delivery for waitlist/transactional communication where applicable)
  • Apple (Sign in with Apple and related platform services)
  • Google (Google Sign-In, OAuth, and Google Calendar API where you authorize those integrations)

These providers act as processors under contractual safeguards.

10. Your rights

Depending on applicable law, you may have rights to:

  • access your personal data
  • correct inaccurate data
  • request deletion
  • request export
  • object to or restrict processing

To exercise these rights, contact privacy@asynq.org.

11. Children

Familia is designed for family coordination and may include invited members who are teenagers (typically 13+), under parental oversight.

We do not intentionally collect more data than necessary for household coordination.

12. Changes

We may update this policy as the product evolves. We will update the date above accordingly.