Privacy

Lull is a calendar client. It keeps as little as it can: your account, your settings and the keys to your calendar provider. Your events stay with your provider and are not stored on Lull's servers.

Last updated November 2026

What Lull stores

  • Your account. The name, email address and profile picture that Google shares when you sign in, and which plan you are on.
  • Your settings. Preferences such as theme, week start and time format, and the labels you give event colors. They are also kept in your browser so the app opens the way you left it.
  • Connections to your providers. For each account you connect (Google for calendars, and Zoom if you connect it for meeting links): the provider's account identifier and email, the permissions you granted, and the access and refresh tokens that let Lull act for you. The tokens are encrypted before they are stored.
  • Calendar display preferences. Which calendars are shown and any color you chose for them in Lull.
  • Feedback you send. Your message, whether it is a bug or an idea, your plan, and a short technical description of your browser and of the screen you were on.
  • Assistant usage counts. For each request to the Pro assistant: the time, the model used and how large the request was. This is for metering and rate limits. The content of the request is not kept in this record.
  • Calendar change counts. When you change your calendars through Lull: the time of each change, and for each guest invited or emailed a one-way code made from their address with a key only Lull's servers hold, never the address itself. This is for limits that stop Lull being used to send invitations in bulk. These records are kept for about a day, then deleted.
  • Billing references. If you subscribe: your Stripe customer and subscription identifiers, the subscription's status and the end of the current period. Lull never receives or stores your card details.

What Lull does not store

Your events. Lull fetches events from your calendar provider when you use the app and sends your changes back to it. They pass through Lull's servers on the way, but they are not saved in Lull's database. So that the app opens at once, your browser keeps its own copy of your calendars and the events around today; it is refreshed every time the app opens and removed when you sign out.

What you type into quick add. Plain-language quick add is read by a language engine that runs in your browser. Nothing is sent anywhere to be understood; when you save, the finished event goes to your calendar provider like any other change.

The demo. The demo runs entirely in your browser on sample data. What you do there stays on your device.

Others who handle your data

Lull relies on a small number of services. Each receives only what it needs.

  • Google. Sign-in, and reading and writing the calendars you connect. When you ask Lull to make room, and only if you granted that permission, Lull also asks Google whether the guests on a meeting are free or busy at a proposed time. It receives busy times only, never the details of their events, and does not store them. When you apply a plan that moves a meeting with guests, Google emails those guests about the change unless you turn that off before applying.
  • Zoom. Only if you connect it, to create meeting links for your events.
  • Supabase. Hosts the database and sign-in sessions described above.
  • Vercel. Hosts the application and provides privacy-friendly, aggregate page analytics that do not use cookies to follow you.
  • OpenRouter and the AI model provider behind it. Only when you use the Pro assistant: your question or request, and the parts of your calendar needed to answer it, are sent to an AI model through OpenRouter and the answer comes back the same way.
  • Stripe. Takes payment for Pro and keeps your payment details.
  • Sentry. Receives reports of errors in the application so they can be fixed. Personal fields are removed from these reports before they are sent.
  • GitHub. Feedback you send is filed as an issue in Lull's issue tracker, with your plan and the technical description, so please leave private details out of feedback.

Lull does not sell your data and does not show advertising.

Data from Google

Lull uses the information it receives from Google APIs only to provide the calendar features you see in the app. Its use and transfer of that information adheres to the Google API Services User Data Policy, including the Limited Use requirements. It is not used for advertising and Lull does not use it to train AI models.

Cookies and storage in your browser

Lull sets the cookies needed to keep you signed in, and one that tells the app which account is signed in on this browser. It also keeps your settings, the copy of your calendars and the events around today that the app opens on, and the demo's sample calendar in your browser's local storage. The copy is removed when you sign out. There are no advertising or cross-site tracking cookies.

Your choices

  • You can remove Lull's access at any time from your Google account's third-party access settings, and from Zoom's if you connected it.
  • You can cancel Pro at any time from Settings, then Billing.
  • You can ask for a copy of what Lull holds about you, or for your account and the data above to be deleted, through the feedback form inside the app. Deleting your account removes your profile, settings, connections and preferences; feedback you sent is kept without your account attached.

Changes and contact

If this page changes in a way that matters, Lull will say so in the app before the change takes effect. For questions about privacy, use the feedback form inside the app. See also the terms.