Privacy policy

Who this is for

Family Calendar (also known as Karaman Calendar) is a private household calendar dashboard for a single family. It is not a public or multi-family product.

Sign-in

Calendars, family data, and Google connections require a household administrator login or a time-limited guest invite link. Those sessions are kept in an HTTP-only cookie for up to 12 hours, or until a guest invite expires or is revoked. This privacy policy is public and does not require that login.

Google Calendar

Connecting Google Calendar requests only openid, email, profile, and read-only Calendar access (https://www.googleapis.com/auth/calendar.readonly). The app cannot create, change, or delete Google events.

Google events are displayed on the household dashboard. They are not imported as family events.

Where Google credentials are stored

Google access and refresh tokens are encrypted with AES-256-GCM and stored in Postgres. The browser never receives those provider credentials. It only receives the event details needed to draw the calendar.

A short server-side cache of Google events may be kept so the calendar loads quickly. That cache is not an import into the family calendar, and it is deleted when the Google account is disconnected.

Household data

Family events, family members, guest invite records, and preferences (calendar views, AI Planner settings, and per-event reminder timing) are stored in Postgres for this single-family deployment.

Notifications

If Web Push reminders are enabled on an installed device, the push subscription is stored encrypted in Postgres. When and how often to notify for family and Google events is stored as a household preference and is not written back to Google.

AI Planner

When an authenticated user submits a planning request, scheduling text and any attached calendar screenshots may be sent to the selected model through Vercel AI Gateway. That happens only for that request. The planner does not save events until the user confirms the proposals.

Sharing, transfer, and disclosure of Google user data

Google user data is shared only with the service providers and parties listed below, and only as needed to operate this household calendar. We do not sell Google user data. We do not share it with advertisers, data brokers, or unrelated third parties.

Google: OAuth sign-in and read-only Calendar API calls to fetch events for display.

Neon (Postgres hosting): encrypted Google OAuth tokens, a short-lived server-side cache of Google events, and other household calendar data are stored in a managed Postgres database.

Vercel (application hosting): the app and its API routes run on Vercel infrastructure. Google user data passes through these servers only to provide calendar features.

Vercel AI Gateway (optional AI Planner): when an authenticated user submits a planning request, scheduling text and any attached calendar screenshots may be sent to the selected model through Vercel AI Gateway for that request only.

Household members: anyone who signs in with the household administrator login can view Google events displayed on the dashboard.

Invited guests: a household administrator can create a time-limited, revocable link for a friend. Guests see only busy times for the family-member calendars the administrator selected. Event titles, descriptions, locations, attendees, and conference links are removed on the server before the calendar is shown. Guests cannot create, change, or delete events, and they cannot open integrations, family settings, or the AI Planner.

Data protection for sensitive data

All traffic between your browser and this app uses HTTPS (TLS) in transit.

Google OAuth access and refresh tokens are encrypted at rest with AES-256-GCM before storage in Postgres. The browser never receives those provider credentials.

Web Push subscription keys, when enabled, are also encrypted at rest with AES-256-GCM.

Household and guest sessions use an HTTP-only, signed cookie with a 12-hour lifetime. Guest access is also checked against the stored invite on each request so it can be revoked immediately. Calendar and integration APIs require a valid session.

Google Calendar access is read-only. Disconnecting a Google account revokes the grant and deletes stored encrypted credentials and cached events for that account.

Limited use of Google user data

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

Google user data is used only to provide or improve user-facing calendar and planning features in this app. It is not used to create, train, or improve generalized or foundational AI or machine learning models.

Selling and advertising

We do not sell Google user data or other household data. We do not use it for advertising.

Disconnecting Google

Disconnecting a Google account revokes the Google grant and deletes the stored encrypted credentials for that account.

Contact

Questions about this policy: alexkaraman85@gmail.com.