Privacy

Lyra is not a company. It is a personal project built and operated by one individual, reachable at hello@lyracal.com. There is no support desk, no sales team, and no third party being paid for your attention.

• Your account. Your email address. Your time zone. Your display preferences — theme, week start, density, hour format, which fields you want to see. A name and a profile picture only if you signed in with Google and Google supplied them.
• Your calendar. Event titles, notes, start and end times, the time zone an event was written in, whether it is all-day, its colour, the calendar it sits on, reminder offsets, and the email address of every guest you invite along with their answer.
• Delivery records. One row per email Lyra owes you or a guest — which reminder or invitation it was, when it was due, how many attempts it took, and whether it was sent, cancelled or failed. This exists so that “why did that reminder never arrive” has an answer.
• Sign-in. A session row for each browser you are signed in on, the one-time sign-in tokens emailed to you (which expire), and — only if you use Google — the tokens Google issues for your account.

There is no advertising identifier, no device fingerprint, no location, no contacts import and no address book. Lyra does not know what other sites you visit.

When you add a guest, Lyra stores the address you typed and the answer they gave. Guests never need an account. Their address is used to send that invitation, its updates and its cancellation, and for nothing else — no list, no newsletter, no later contact.

Lyra is small, so it rents the parts it does not build. Each of these sees only what it needs to do its job:

• Neon hosts the Postgres database. Everything described above lives there.
• Resend sends every email: sign-in links, reminders, invitations, updates and cancellations. It sees the recipient address and the contents of that particular message.
• Inngest runs the clock that decides when a reminder is due. It sees job identifiers and timings only — no event titles, no notes, no email addresses.
• Anthropic writes the daily briefing, but only when Lyra is configured to use it. See below.
• Google is involved only if you choose to sign in with Google, and then only for the sign-in itself. Lyra does not read your Google Calendar, your Gmail or your contacts.
• The host that serves these pages sees the ordinary web-server things: your IP address, your browser, and which URL you asked for.

The briefing is the sentence at the top of your calendar that tells you what your day looks like. It can be written two ways. By default it is composed on Lyra’s own server from your events, and nothing leaves.

When Lyra is configured with an Anthropic API key, that day’s calendar is sent to Anthropic’s API to be written instead. What is sent, exactly: your event titles, the name of the calendar each one is on, the times as they read on your screen, durations, whether an event is all-day, any note you left on an event (up to 160 characters), reminder offsets, and how many guests are going. What is not sent: your name, your email address, your guests’ email addresses, and anything from any other day.

The written result is cached so the same day is not sent twice. If you would rather no version of your day ever left the server, say so at hello@lyracal.com — a per-account switch is on the list.

Lyra sets a session cookie and a theme cookie. That is the list.

• The session cookie is set when you sign in, so the next page knows it is you. Signing out clears it.
• lyra.theme remembers whether you asked for the light theme or the dark one, so the first paint is the right colour.
• Signing in also briefly sets two Auth.js cookies whose only job is to make that sign-in safe against forgery.

There is no analytics, no tag manager, no advertising pixel, no session recorder and no third-party script of any kind. Fonts are served from Lyra’s own domain, so loading a page tells nobody else that you did. Your browser also remembers which view you were last on (lyra.view); that never leaves your device.

To run your calendar and to send the email you asked to be sent. Nothing is sold, rented, or shared for advertising — there is no advertising. Lyra does not use your events to train anything, and Anthropic’s commercial API terms say inputs sent to it are not used to train their models either.

• Your account and everything on your calendar: until you ask for it to go.
• Delivery records: 90 days after they reach a final state — sent, cancelled or failed. Anything still owed to you is never deleted on age.
• Cached briefings: 30 days.
• Sign-in links are single-use and expire. Sessions expire on their own, and signing out ends them immediately.

Email hello@lyracal.com from the address on the account and ask for a copy of your data, a correction, or deletion. Deletion removes your account, your calendars, your events, your guests’ answers, your reminders and any email still queued for you. There is no self-serve delete button yet; there should be, and there will be.

There is no password to leak: sign-in is a one-time emailed link or Google. Guest RSVP links are signed and expire. Everything travels over HTTPS, and the database is reached over an encrypted connection with credentials that live only on the server.

Lyra is also a young product run by one person. It is built carefully and reviewed, but it is not certified against any standard and it has not been audited by anyone but its author. Treat it accordingly.

Lyra is not designed for children and should not be used by anyone under 13.

The date at the top of this page changes with it. If a change affects what is stored or who sees it, the account email address gets a note about it before it takes effect.