Calmical Privacy Policy

Effective date: September 26, 2026
Last updated: October 9, 2026 (documents shared into ✨ Import)
Who we are: Calmical (calmical.com) is run by Chairlook, LLC ("we", "us"). Contact: support@calmical.com.

The short version

Calmical is a shared calendar for your household. What you add is seen by the people in your household, and by other families only if someone shares a calendar with them. We don't sell your information, show ads, or use it to profile you.
The optional cycle tracker is private to you. Your logged days are encrypted on your device with a passphrase only you know, before they're saved. We can't read them. Some cycle settings aren't encrypted (see below).
You can export your information, leave a household, or delete your account at any time.

What we collect

Your account. You sign in with Google, with Apple, or with an email address and a password.

With Google: your name, email address, profile photo and a Google account identifier, from Google.
With Apple: an Apple account identifier and an email address, from Apple, and your name if you choose to share it (Apple shares it only the first time). If you choose Apple's "Hide my email", we get a private relay address from Apple instead of your real one; email we send to it is forwarded to you by Apple.
With an email and password: your email address and your password. The password is kept only as a secure one-way hash by our sign-in provider (Google Firebase Authentication); we never see it. We email you a link to confirm the address before you can start or join a household, and a link to reset the password if you ask. An account that never confirms its address is deleted after 7 days.
One email address is one account: if you use both Google and a password with the same address, they sign in to the same account. A relay address from Apple is different from your real one, so you connect Apple to an existing account yourself (Family → "Your data and account").

Age. Accounts are for people 13 and older. The person who starts a household confirms they're 18 or older. When an admin invites someone to their own login, they confirm that person is 13 or older. We keep only that confirmation (that it was given, by whom and when), never a date of birth.

What your household adds:

members' names, colors and photos;
events, including times, notes and places, packing lists, whether an event is marked private, and comments people write on them;
repeating events and special days such as birthdays;
co-parenting schedules (which days a child is with each parent, the other parent's name, and handoff times and places);
lists, recipes and meal plans;
family info cards (for example doctors, school, contacts, Wi-Fi, insurance and clothing sizes), which can be limited to admins or to the person who made them;
chores, stars and rewards;
outside calendars you connect;
calendars shared with or from other families;
a household name and timezone.

Anyone in your household can see this, apart from outside calendars marked private, family info cards limited to admins or to one person, and the cycle tracker. Family info cards aren't encrypted: please don't store bank or account passwords in them.

Contact details you choose to add: a phone number, and whether you agreed to text messages. Text messages aren't sent yet.

Places: when you type in "Where", what you type is sent to Google Maps Platform to suggest places. The place you pick (name, address, coordinates) is saved with the event.

"Leave by" alerts: if an admin adds the household's home address, it's saved with the household. On the day of an event with a place (unless its alert is switched off), our server sends that address and the event's place (never names or titles) to Google Maps Platform to estimate the drive time in traffic, and keeps only the minutes.

Outside calendars: the private calendar link you paste is stored so we can fetch the calendar. It is never shown to anyone, including you, after you add it. Events from it are copied in so your household can see them (or only you, if you choose). The same goes for a school system's assignment calendar (Canvas, Blackboard, D2L) that you add to a course: its assignments are copied in as the course's items.

Recipe import: the web address you give is fetched by our server. The recipe and one photo are saved.

Importing events: if you use "✨ Import", the photos you take or choose (shrunk on your device first), the text you paste, or a document you share into the app from another app are sent to Google's Vertex AI (Gemini), in the United States, to find the events in them. "🎓 Import school schedule" does the same with syllabi and other school documents. For documents, PDFs are sent as they are, and Word, Excel and CSV files are turned into text on your device and only that text is sent. You review every event before anything is added.

We don't store the photos, documents or text: they're used for that one request and discarded.
Google doesn't use them to train its models. Google may keep them briefly for security and abuse checks, as its terms describe.
What you add from the review is saved like any other event.

Notifications: if you turn them on, a push token for that device and a label such as "iPhone". We also keep a list of recent changes for your notification bell, and the number of them you haven't read, for the badge on the app's icon.

Widgets (in the iPhone, iPad and Android apps): so the widgets can show your family's day, your device gets a key that reads only that summary (events, your next drive, dinner and chores; never notes, comments or anything from the cycle tracker). We keep only a fingerprint of the key, with the device's type. It stops working when you sign out, leave the household or delete your account, or after 90 days unused. The summary is kept on your device for the widgets.

Wall displays: a paired tablet uses an anonymous account and the name you give it (for example "Kitchen").

Technical information:

Our hosting and database providers keep standard logs: IP address, browser and time of each request.
To keep the app installable and working offline, it stores data on your device: a local copy of recent calendar data, the app's files, and small settings such as when you dismissed a banner. In the iPhone, iPad and Android apps, this data is left out of your phone's backups.
We use Firebase App Check to check that requests come from our app:
on the website, with Google reCAPTCHA Enterprise, which may collect device and browser signals under Google's terms;
in the iPhone and iPad app, with Apple's App Attest (DeviceCheck on older devices);
in the Android app, with Google Play Integrity.

These check that the device and the app are genuine, under Apple's and Google's terms; they don't tell us who you are or what you do in the app.

In the apps, push notifications reach your phone through Apple's and Google's notification services.

We do not use advertising or analytics cookies, and we don't track you across other sites.

A member can share their calendar with another household (for example grandparents or a co-parent), and an admin can share any member's. A teen's own share needs an admin's approval before it works. The person sharing chooses what the other family sees:

Busy times only: just when, shown as "Busy".
Details: the title, time and place. Notes are never shared.
Can add events: details, and the other family's adults can add events to that calendar. Their name and family are shown on what they add, and they can change or delete only what they added. Drop-offs and pick-ups that still need a driver are shared too, so they can offer to drive; whoever takes one is shown to your family.

Events marked private show only as "Busy" to other families, at every level. The other family sees copies we make for them; they can't see anything else in your household. Either family can stop sharing at any time, and the copies are deleted at once. People in the other family can choose to be notified about changes.

Carpools. When your household shares a calendar with another family (either way), you can ask one of their adults to do a drop-off or pick-up. To offer the choice, we show you the first names of that family's adults with a login. The person you ask sees that one drive in their calendar: your child's first name, the event's title, the place and the time, and who asked. If they say yes, they get its reminders; if it changes or is cancelled, they're told and their copy is updated or removed.

The cycle tracker (health information)

The cycle tracker is off unless you turn it on. It is never visible to other members of your household, including admins, or to other families, unless you choose to share predicted dates with someone in your household.

What's encrypted on your device:

each logged day (flow, symptoms and how strong, mood, notes);
your own symptom names.

Before anything leaves your device:

it's encrypted with AES-GCM, using a key made from your passphrase (PBKDF2-SHA256, 600,000 rounds);
each day is stored under an identifier that hides its date.

Your passphrase and keys are never sent to us. The keys are stored only on your devices, in a form the browser won't let any script read. **If you forget your passphrase, we can't recover your history.**

What's not encrypted:

your cycle settings: typical cycle and period length, which reminders you want and the date of the next one, and who you share with;
any predicted dates you choose to share with someone in your household;
roughly how many days you've logged.

Our server reads only the next reminder date, to send your reminder. Reminders say only "Reminder from Calmical" unless you choose more detail.

Limits you should know about:

Our security rules stop every other account in the app from reading this information.
People with administrative access to our cloud project could see the unencrypted parts listed above. They would see only scrambled data for your logged days.
Because the app is delivered by our website, a compromised version of the app could capture a passphrase as it's typed. We work to prevent this but can't rule it out.

Pausing and deleting:

Pausing keeps your encrypted history.
"Turn off and delete everything" permanently deletes your cycle data and any shared dates.

Consent: we collect cycle information only after you turn the tracker on and set your passphrase, and only for the purposes described here: showing your history and predictions, and sending the reminders you choose.

How we use information

To run the service for your household: showing, syncing and backing up your calendar, sharing it with the families you choose, and sending the notifications and reminders you choose.
To keep it secure and working: fighting abuse, fixing problems, enforcing limits, and watching for errors and unusual activity.
To contact you about your account or important changes.

We don't sell or rent personal information. We don't use it for advertising. We don't use cycle information for anything except showing it to you and the reminders you choose.

People in your household, as described above.
Families you share a calendar with, only as described in "Sharing a calendar with another family".
Service providers who process data for us under contract:
Google Cloud and Firebase: hosting, database, backups, authentication, file storage, Cloud Functions, push notifications, App Check (reCAPTCHA Enterprise on the website, Play Integrity in the Android app), and Vertex AI (Gemini) for importing events;
Google Maps Platform: place suggestions, and drive times for "Leave by" alerts;
Apple: Sign in with Apple, if you use it (Apple receives the sign-in request, as its terms describe); in the iPhone and iPad app, push notifications (Apple Push Notification service) and App Attest.

Data is stored in the United States.

Websites you ask us to fetch (outside calendars, recipe pages) receive a request from our server.
When required by law, or to protect people's safety, and in a sale or merger of the service. You'll be told beforehand, and this policy will still apply.

Children and teens

Under 13: children don't have their own login. A parent adds them to the household as a member (a name, a color, optionally a photo) and manages their events, lists and chores. We don't collect information directly from children under 13.
13 to 17: a teen can have their own login only when an admin of their household (a parent or guardian) invites them and confirms they're 13 or older.
A parent can review, change or delete their child's information from the Family screen, or by contacting us.

How long we keep it

We keep your household's information while the household exists.

Backups: we back up the database every day and keep each backup for 14 days, so we can recover from mistakes. Something you delete can remain in a backup for up to 14 days, and is then gone.
Deleting an event, list or recipe removes it right away (and from backups within 14 days).
Deleting a household removes everything in it, including photos, after a 7-day undo period. Calendars it shared with other families stop at once.
Deleting your account (Family → Delete account, all in the app) removes your account, notifications, device tokens, the comments you wrote, your "only me" family info cards and cycle data. If you signed in with Apple, we ask Apple to revoke the app's access to your Apple ID. Your name may remain as a member of a household you were in, until an admin removes it. If you were the only person in a household, the household and everything in it are deleted with your account, right away. If you were its only admin, the adult who joined first becomes the admin.
Unpaired wall display accounts are deleted after 24 hours.
Server logs are kept for 30 days.

Your choices and rights

Export:
Household admins can download the household's data.
Anyone can download their own account data.
Your cycle history is exported on your device, decrypted there.
Correct: edit anything in the app.
Stop sharing a calendar with another family at any time, from the Family screen.
Leave a household, or delete your account, in the Family screen.
Notifications: turn them on or off per device.
Depending on where you live, you may have more rights, such as knowing what we collect, deleting it, and appealing a decision. Contact support@calmical.com. We answer within 45 days. We don't discriminate against anyone for using their rights.

Security

Data is encrypted in transit (HTTPS) and at rest by our cloud provider.
Access is limited by security rules that are tested with every change.
Cycle days are also encrypted on your device.
No system is perfectly secure.

If there's a breach

If your information is involved in a breach of security, including any unauthorized access or disclosure, we'll notify you without unreasonable delay.

Where the law requires, we'll also notify the Federal Trade Commission and others. This includes the FTC's Health Breach Notification Rule for health information such as cycle data.

Changes

We'll post changes here and update the date. For important changes we'll tell you in the app first.

Contact

Chairlook, LLC, which runs Calmical: support@calmical.com.