Luma

Last updated: October 2, 2026

Privacy policy

This privacy policy describes how Luma Calendar ("Luma") collects, uses, stores, and shares information about you when you use our website, mobile-friendly web application, and tablet display experiences at lumacalendar.com (collectively, the "Service"). Luma Calendar is a product of CoRecruiter, Inc., a Delaware corporation ("CoRecruiter," "we," "our"), with its principal office in New York, New York. Privacy questions: privacy@lumacalendar.com.

Connecting Google is optional. If you do connect Google Calendar or sign in with Google, Section 3 explains exactly what Google user data we access, how we use it, how we store it, who we share it with, and how you can delete it.

1. Information we collect

We collect only what we need to provide the Service. Specifically:

  • Account data. Email address, full name (optional), password hash (managed by our authentication provider, Supabase Auth — we never see your plaintext password), and the timestamps of account creation and last sign-in. If you choose Sign in with Google, Google provides your Google account identifier, email address, name, and profile picture for authentication only.
  • Household data. Household name, household timezone, list of household members, role of each member (owner / admin / member), and pending invite records.
  • Calendar data. Native Luma calendars and events you create (title, description, location, start/end times, recurrence rules, the calendar a given event belongs to). Google Calendar data is described in Section 3.
  • Lists data. Items in your household's grocery and to-do lists.
  • Tablet device data. When you pair a tablet with your household, we store a name you give the tablet, a hashed device refresh token, and a "last seen" timestamp.
  • Operational telemetry. Page views, in-app event names (e.g., "event_created", "tablet_active"), and crash reports. Telemetry is associated with your user id, never your email. We use PostHog for product analytics (including session replay with input fields masked by default) and Sentry for error tracking.
  • Server logs. Standard request logs (IP address, user agent, timestamp, URL) retained for up to 30 days for security and debugging. We do not sell or share these logs.

2. How we use your information

  • To operate the Service and synchronize your calendars between providers.
  • To send transactional emails (welcome, password reset, household invite).
  • To diagnose bugs and improve the product. Session replays are reviewed only when we are investigating a specific issue you've reported or a bug we've detected.
  • To enforce our Terms of Service and prevent abuse.

We do not use your information for advertising. We do not sell your information. We do not train AI or machine-learning models on your calendar contents.

3. Google user data

This section applies when you choose to connect a Google account to Luma. It is the disclosure Google requires for apps that access Google user data through Google APIs. We use Google user data only to provide or improve user-facing features of Luma Calendar.

What Google user data we access

After you click Connect and grant permission on Google's consent screen, we access only the following:

  • Google identity (Sign in with Google, optional). Your Google account identifier, verified email address, name, and profile picture, used only to create or sign in to your Luma account. This uses Google's standard identity scopes (openid, email, profile).
  • List of calendars. The names, identifiers, and sharing metadata of calendars in your Google Calendar account, so you can choose which calendars to show in Luma. Scope: calendar.calendarlist.readonly.
  • Calendar events. Event titles, descriptions, locations, start and end times, time zones, all-day flags, recurrence rules, attendees as stored on the event, and related identifiers needed to keep Luma and Google in sync. We read existing events and, when you edit from Luma, we create, update, or delete events on the Google calendars you connected. Scope: calendar.events.
  • OAuth tokens. An access token and refresh token from Google so we can sync on your behalf after you leave the consent screen.

We do not request access to Gmail, Google Drive, Contacts, Photos, or any other Google product. We cannot see Google calendars you do not connect. The full Google scope URLs are https://www.googleapis.com/auth/calendar.calendarlist.readonly and https://www.googleapis.com/auth/calendar.events.

How we use Google user data

We use Google Calendar data solely to:

  • Display your connected calendars and events on the Luma web app, kitchen tablet, and household dashboard so your family can see a shared schedule.
  • Keep Luma and Google Calendar in sync both ways: a change you make in Google appears in Luma, and a change you make in Luma is written back to Google.
  • Let you pick which of your Google calendars to import when you connect, and which remain visible.
  • Answer questions you ask Ask Luma AI about your household schedule (for example, "what's on Saturday?") and to propose new events you confirm. That may include events originally synced from Google.

We do not use Google user data for advertising, marketing, credit, lending, or resale.

How we store Google user data

  • OAuth access and refresh tokens are encrypted at rest with AES-256-GCM using a server-side key. Tokens are never stored in plaintext.
  • Event copies are cached in our database so the kitchen tablet can render your schedule in real time without calling Google on every screen refresh. The cache is scoped to your household and protected by Postgres Row-Level Security.
  • All Google user data is stored on infrastructure operated by our subprocessors in the United States (see Section 5) and transmitted over TLS.

How we share, transfer, or disclose Google user data

We do not sell Google user data. We do not transfer or disclose Google user data to third parties except as needed to operate the features you use:

  • Household members. Other members of your Luma household can see calendars and events you choose to display, including events synced from Google.
  • Infrastructure providers who process data only to host Luma: Supabase (database and authentication), Vercel (hosting). They are contractually limited to providing services to us.
  • Ask Luma AI. If you use Ask Luma, we send your question and the relevant calendar events (which may include Google-synced events) to our AI provider (OpenAI) solely to generate the answer or event proposal you requested. We do not allow that data to be used to train generalized or non-personalized AI or machine-learning models.
  • Optional iCal feed. If you generate a secret calendar subscription URL in Settings, anyone with that URL can read the events on that Luma calendar. If the calendar includes events synced from Google, those events appear in the feed. You can rotate or disable the URL at any time.
  • Product analytics and errors. PostHog session replay may capture calendar titles that are visible on screen (input fields stay masked). Sentry receives crash reports. These are associated with a user id, not your email, and are used only to operate and improve Luma.
  • We may disclose information if compelled by valid legal process, or to protect the rights, property, or safety of Luma, our users, or the public.

Limited Use

Luma Calendar's use of information received from Google APIs adheres to the Google API Services User Data Policy (including the Limited Use requirements). In particular:

  • We use Google user data only to provide or improve user-facing features that are prominent in Luma Calendar's user interface.
  • We do not transfer Google user data to third parties except as necessary to provide or improve those features, for security purposes, to comply with the law, or in a merger or acquisition of Luma, and then only with equivalent protections.
  • We do not use or transfer Google user data for serving ads, including personalized, retargeted, or interest-based advertising.
  • We do not allow humans to read Google user data unless you give us permission to investigate a specific issue you reported, it is necessary for security or legal reasons, or the data is aggregated and no longer associated with you.
  • We do not use Google user data, including data obtained from Google Workspace APIs, to develop, improve, or train generalized or non-personalized AI or machine-learning models.

How long we keep Google user data, and how you delete it

  • Disconnect Google. In Settings you can disconnect a Google account. We immediately revoke our OAuth tokens at Google and stop reading or writing your Google Calendar. Cached copies of previously synced events may remain in your household until you delete those events, delete the household, or delete your Luma account. You can also revoke Luma from your Google Account permissions page.
  • Delete your Luma account. We revoke Google tokens and delete your account data, including cached Google events in households you solely owned, within 30 days. Email privacy@lumacalendar.com if you need help.

4. How we share information (generally)

We share information only with service providers who help us operate Luma. We have contracts with each that limit their use of your data to providing services to us:

  • Supabase (database, authentication)
  • Vercel (hosting)
  • Resend (transactional email delivery)
  • Google (only the calendars and identity you choose to connect; see Section 3)
  • OpenAI (Ask Luma AI, only when you use that feature)
  • PostHog (product analytics, session replay)
  • Sentry (error tracking)

We may disclose information if compelled by valid legal process, or to protect the rights, property, or safety of Luma, our users, or the public.

5. Where data is stored

Luma stores data on infrastructure operated by Supabase and Vercel, in U.S.-based data centers. If you access the Service from outside the United States, your data will be transferred to and processed in the United States.

6. Data security

We use industry-standard security controls: TLS for all transport, AES-256-GCM encryption for OAuth tokens at rest, Postgres Row-Level Security to ensure one household cannot see another's data, hashed and rotated tablet refresh tokens, and access logs. No system is perfectly secure. If we discover a breach affecting your data we will notify you within 72 hours.

7. Data retention and deletion

  • Account and household data is retained as long as your account is active. When you delete your account, we delete your account data within 30 days.
  • Google OAuth tokens are revoked and we stop accessing Google as soon as you disconnect. See Section 3 for cached event copies.
  • Server logs are retained for 30 days.
  • Telemetry events are retained for 24 months.

Email privacy@lumacalendar.com to request access to, correction of, or deletion of your data.

8. Your rights

Depending on where you live, you may have rights under the GDPR, CCPA, or similar laws to access, correct, delete, or port your personal information. To exercise any of these rights, email privacy@lumacalendar.com. We will respond within 30 days.

9. Children

Luma is not directed to children under 13. We do not knowingly collect personal information from children under 13. Parents may add a child's name to their family calendar; this is data the parent controls and can remove at any time.

10. Changes to this policy

We will post any changes to this policy on this page and update the "Last updated" date. If we change how we use Google user data, we will notify you and obtain consent before using that data in a new way. If other changes are material, we will notify you by email.

11. Contact

Questions, concerns, or requests: privacy@lumacalendar.com.

CoRecruiter, Inc.
124 Nassau Street, Suite 2
New York, NY 10038
United States