Privacy Policy

Last updated July 23, 2026

What Klarity is

Klarity is a private household management workspace. Access is limited to approved Google accounts.

Information we collect

Klarity stores structured workspace information such as line-item names, values, ownership labels, review states, comments, notes, Drive file links, and timestamps. Authentication is handled by Google Sign-In.

Google user data

When you connect Google Drive, Klarity requests permission to create and manage files it creates or opens, plus read-only Drive metadata access so it can list files inside the configured private workspace folders. Klarity uses this access to create section folders, write README ledgers, list evidence files, and associate selected Drive files with workspace line items.

Klarity uses a dedicated service identity to read the shared “Parent Time” and “Ketchum Family Calendar.” The official Parent Time calendar remains read-only and supplies the main parenting schedule. Klarity creates or updates only its own generated events on “Parent Time - Klarity” as a derived view. After Russ confirms the end of an otherwise unbounded daytime-care block, Klarity may reconcile one source-bound pickup event on the Family Calendar. When an approved household member turns on Flex, Klarity creates transparent, time-bounded events prefixed with “Flex:” on the Family Calendar. These blocks annotate the official schedule; they do not replace it. Ending Flex records who ended it, when, and the reason.

To make Klarity load quickly, the backend stores a normalized, time-bounded copy of the household schedule in Firebase Firestore. This copy contains only the display fields Klarity needs, such as dates, times, titles, parent and child assignments, source type, and freshness metadata. It does not store raw Google Calendar responses, attendee lists, private event descriptions, authentication tokens, or Calendar sync tokens in the household-facing read model.

Klarity may use Vertex AI to classify the meaning of a calendar event that its deterministic schedule rules do not understand. This processing happens only on the backend. Klarity replaces the known household parent and child names with role labels, then sends a bounded event title, dates and times, a coarse location category, source-calendar type, and nearby Parent Time context. Event titles can still contain other names or personal details entered by a household member. Klarity does not send Google credentials, attendee lists, addresses, or unrelated financial and workspace data. Model output is restricted to a validated set of schedule labels and cannot update a calendar or change the effective Parent Time schedule. Ambiguous results are shown to approved household members for confirmation.

Klarity's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

How information is used

Information is used only to operate the private workspace, maintain section ledgers, show the shared household schedule, track review status, and generate user-requested exports.

Sharing

Klarity does not sell personal information or use Google user data for advertising. Workspace data is visible only to approved workspace users and to service providers needed to run the app, including Firebase and Google.

Storage and security

Klarity stores structured workspace data and normalized schedule read models in Firebase Firestore. Source documents remain in Google Drive, and the shared Google calendars remain the authoritative schedule sources. Raw source calendar records, Flex audit details, Google access tokens, and backend Calendar sync state are not included in the household-facing Firestore read models. Validated Vertex AI classifications are cached by a source-content hash to avoid repeat processing and are invalidated when the source event changes. Google may temporarily retain request data for service operation or abuse monitoring under the applicable Vertex AI data-governance terms; Klarity does not use that data to train a household-specific model. Klarity does not enable persistent storage of sensitive household data on the device; the app keeps only an in-memory session copy and its non-sensitive application shell. Google Drive access tokens are kept temporarily on the user's device and expire automatically. Access rules restrict the workspace, read models, and calendar endpoints to approved, verified Google accounts.

Your choices

You can revoke Klarity's Google Drive access from your Google Account permissions page. You can also request removal of workspace access or stored workspace data. Removing the Klarity service identity from a source calendar prevents Klarity from refreshing that source. Removing its event-edit permission from “Parent Time - Klarity” prevents the derived calendar from being reconciled. Removing its event-edit permission from “Ketchum Family Calendar” prevents Klarity from recording reviewed pickup events or Klarity-created Flex blocks.

Contact

For privacy requests, contact the workspace owner at rketchum@gmail.com.