Calliary Privacy Policy

1. What we do not collect

We do not collect your name, phone number, email, address, date of birth, or any other directly identifying information. Because no company server receives your records, your events, diary, photos, decorations, and health-related records are never sent to us. We do not request the advertising identifier (IDFA) and include no third-party analytics, advertising, or crash-reporting SDKs. If you join the TestFlight beta, however, Apple provides us with the information in Section 16 that it collects through TestFlight, including any screenshots and comments you choose to send as feedback. If you send us a question through "Contact developer" or by email, we also receive the information in Section 17, including your email address and message.

2. Data stored on your device and in your iCloud

The following data is stored on your device and, if you use iCloud, synced to the private CloudKit database of your own Apple Account (except items marked "device only"). It is encrypted per Apple's standards, and we have no access to it.

Stored on the device only, never synced: app-lock setting, medication reminders (name, time, weekdays), scheduled local notifications, daily custom-sticker usage count.

3. Shared calendars

Sharing starts only when you invite someone and is carried out through Apple's iCloud sharing (CloudKit Shared Database). No company server is involved.

• What is shared: events in the calendars/categories you chose to share and the decorations on them are visible to participants, and participants' decorations are visible to each other. Unshared categories, diary entries, and settings are not shared.
• Participant info: a shared calendar stores each participant's chosen nickname and the share-participant identifier assigned by Apple. Other participants' Apple ID email or phone number is neither shown nor stored by the app.
• Co-decorating notifications: when someone decorates, Apple Push Notification service (APNs) wakes your device and the notification text is composed on the device. We do not send or store notification content.
• Cycle sharing (opt-in): only the scope you choose (next expected date only / cycle summary / full history) is shared. Daily details such as symptoms, mood, basal temperature, discharge, and notes are never shared at any scope.
• Stopping: owners can stop sharing or remove participants at any time; participants can leave at any time. A "lock" prevents new participants from joining.

4. Invite codes and QR

Creating an invite code stores one invite record in the Calliary public CloudKit database. The calendar name, nickname, join link, and related details in the record are encrypted so that only the invite code (and the password, if you set one) can open them; we cannot read them. The only unencrypted values are the expiry time, whether a password is used, and the record format number; the password itself is never stored. The record contains none of your events, decorations, or diary. Codes are random strings; a code alone does not reveal whose calendar it is.

• An invite record becomes unusable once the validity period you chose (up to 7 days) has passed, and is deleted when you cancel the invite or joining is complete.
• QR scanning uses the camera. Camera frames are processed on device only while reading the code and are never stored or transmitted.
• Saving an invite card image writes it to your Photos library (Section 6).

5. Importing from other calendars

Import is a one-time action you start yourself. Imported events are copied into your Calliary calendar and never sent to us. Calliary never modifies or writes back to external calendars.

• Apple Calendar: with your permission, events from the calendars you select are read.
• Google Calendar: only after you sign in to Google, events are read with the read-only scope (calendar.readonly). The access token is discarded immediately when the import finishes or is cancelled and is never stored. No account link persists; you sign in again for the next import.
• Calendar files (.ics): files you pick are parsed entirely on device.

Google user data (Limited Use)

Calliary's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used solely to provide the user-facing import feature, is never used for advertising, never sold or transferred to third parties, never transferred to any Calliary server, and never read by humans. Tokens are discarded when the import ends. You can revoke access at any time from your Google Account permissions page.

6. Device permissions: when and why

No permission is requested at first launch. Each is requested only when you turn on or tap the related feature, and declining leaves the rest of the app fully usable.

7. Cycle and health data

Cycle tracking is off by default and runs only if you turn it on. Records you enter yourself are stored as described in Section 2. Predictions and insights are computed on device, are for reference only, and are not medical diagnoses.

• Apple Health sync (opt-in): when you turn it on on iPhone or iPad, the records you enter that have a matching type in the Health app (period dates and flow, spotting, sexual activity and protection, discharge (cervical mucus), basal temperature you type, symptoms, mood) are also written to Health. Notes and other text you write are never sent to Health.
• What is read from Health: the same kinds of records, contraception records in Health (read only), and Apple Watch sleeping wrist temperature are read to inform predictions. Everything read from Health is stored on that device only (excluded from iCloud Backup) and is never uploaded to your iCloud or to us.
• Prediction summary and sharing: on a device with Health sync turned on, predictions such as the next expected date also use records read from Health, and those predictions are shown only on that device's screen and home-screen widgets. The summary values that sync through your iCloud for your other devices and Apple Watch (such as average cycle and period length and the latest period start), and the summary a cycle-sharing partner receives, are calculated only from the records you enter in Calliary. Your partner receives only this summary within the scope you chose (Section 3), and periods imported from Health are not included in the past-period list of the "full history" scope either.
• Turning sync off: turning Health sync off deletes the records imported from Health from Calliary. They remain in the Health app.
• Deletion: "Delete all cycle data" in Settings immediately deletes all records, predictions, and scheduled reminders. Data written to Apple Health is managed and deleted separately in the Health app.
• Never used for ads or analytics: Calliary has no advertising or analytics. Health data is never sent to us for any purpose. Anything you choose to include in TestFlight beta feedback or in an email to us is covered by Sections 16 and 17.

8. Purchases

Calliary Pro (monthly and yearly subscriptions, lifetime pass) is sold through Apple in-app purchase. Apple processes payment; we never collect or store card numbers or other payment details. The app checks entitlement, subscription, and free-trial status with the App Store to unlock features; this check happens between Apple and your device.

9. Widgets, Apple Watch, Mac

Home-screen widgets and the Apple Watch app share data with the app on the same device (or paired watch). Sync between iPhone, iPad, Mac, and Watch happens only through your own iCloud.

10. Export

Exporting a calendar or diary as PDF or image saves it only where you choose (Files, Photos, or the share sheet). Nothing is sent to us.

11. Retention and deletion

• The only user data we hold is the TestFlight beta information in Section 16 and emails you send us, including their entries in our inquiry-handling list (Section 17). Apple sets how long TestFlight beta information is kept, as described in Section 16. We delete emails and their list entries one year after the inquiry is resolved, as described in Section 17.
• On-device data is deleted when you delete it in the app or delete the app on iPhone or iPad. iCloud data can be deleted from iPhone Settings → Apple Account → iCloud → Manage app data.
• Shared-calendar data disappears for a participant when the owner stops sharing or the participant leaves.
• Invite records become unusable once the validity period you chose (up to 7 days) has passed, and are deleted when you cancel the invite or joining is complete (Section 4).
• Records imported from Health are deleted when you turn Health sync off, and the web copy when you turn "Show on the web" off or tap "Delete web copy" (Sections 2 and 7).

12. Your rights

You can view, edit, and delete your records in the app at any time; stop sharing, remove participants, or leave; revoke location, health, camera, calendar, photo, and notification permissions in the Settings app; and revoke Google account access. Apart from the TestFlight beta information in Section 16 and emails you send us, including their entries in our inquiry-handling list (Section 17), we hold no personal data, so access or correction requests to us do not apply, but requests to delete your emails and any other question can be sent to the contact in Section 18. For TestFlight beta information, see Section 16.

13. Children

Calliary is not primarily directed at children under 14 and does not knowingly collect personal information from children. With no company server collecting information, no age information reaches us, and apart from the TestFlight beta information in Section 16 and emails you choose to send us (Section 17), no information reaches us at all.

14. International transfer and processors

Apart from the TestFlight beta information in Section 16 and emails you send us (Section 17), we hold no user data. Emails are kept in the email service we use (Gmail, provided by Google LLC in the United States) and copied into our internal inquiry-handling list, and while we prepare a reply they may be processed by an AI tool that helps draft replies (Claude, provided by Anthropic PBC in the United States) (Section 17). Beyond that, we transfer no user data abroad and engage no processors. Services you use may process data on servers outside your country under their own policies: Apple iCloud/CloudKit (storage, sync, sharing, invite records, web copy, font downloads, Calliary Web sign-in, viewing and saving), Apple Push Notification service, Apple Weather (WeatherKit), Apple Maps (finding a place for an event), Apple Health, App Store purchases, Google Calendar import if you choose it, and Apple TestFlight if you join the beta (Section 16). If you join the beta, the information in Section 16 is processed by Apple Inc. (United States) under Apple's TestFlight Terms and Conditions and provided to us through App Store Connect.

• Finding a place (Apple Maps): text you type in "Find a place" for an event is sent to Apple Maps to get search results. No location permission is requested, and only the chosen place's name is saved to the event.
• Font downloads: extra fonts are only read from the Calliary public CloudKit database; no user data is uploaded.
• Apple Intelligence: filling in an event from a sentence you type is processed by the on-device Apple Intelligence model; the sentence never leaves your device.
• Siri and system search: the kinds of data you choose in Settings → Apple Intelligence (by default, events on; diary and cycle off) are added to the on-device system search index so that Siri and system search can find them. You can check, add, change, and delete events with Siri. The index stays on your device and is not sent to us; turning a switch off removes that data from the index.

15. Security measures

• Data is stored inside the Apple OS app sandbox and encrypted by Apple in iCloud storage and transit.
• App Lock (Face ID / Touch ID) requires verification each time the app opens.
• Google access tokens are used in memory only and never stored.
• No advertising, analytics, or tracking SDKs are included.

16. Information processed when you join the TestFlight beta

The Calliary beta is distributed through a public link on Apple's TestFlight. When you join the beta, Apple collects the information below through TestFlight and provides it to us.

Beta app installs, usage and crashes (collected automatically)

• Number of installs, number of sessions, and number of crashes per beta build
• Crash logs: symbolicated logs that include how long the app was running before it crashed
• Device model and a device identifier, OS version, and device language
• The beta version you installed, how you were invited (public link) and your invitation status

If you send feedback

• The screenshots and comments you choose to send
• At the time you send it: carrier, time zone, CPU type, connection type (Wi-Fi, cellular or not connected), battery level, available storage, screen resolution, and how long the app had been running
• The model and watchOS version of your paired Apple Watch

If you joined through a public link, your name and email address are not shown to us.

We use this information only to find and fix problems and improve the app, and we do not share it with third parties. Apple does not permit developers to share it with third parties.

The Calliary app contains no analytics or crash-reporting tools, so beta builds send us nothing beyond what Apple provides through TestFlight.

Apple sets the retention period. Apple retains beta feedback for one year and may retain crash logs and usage data until the bugs are resolved.

To stop, delete the beta app from your device or stop testing in the TestFlight app.

You can review the data Apple holds at privacy.apple.com. Questions about TestFlight data can be sent to the email in Section 18. Apple's notice: apple.com/legal/privacy/data/en/test-flight

17. Contact developer and emails

We receive the information below only when you send us a question through "Contact developer" in the app or to the email address in Section 18. The app does not send mail on your behalf; you send it yourself from the mail screen.

• What we receive: your email address, what you write or attach, and three diagnostic lines pre-filled in the message body (app version, device model identifier such as iPhone17,3, OS version). The diagnostic lines are shown on screen before you send, and you can delete them from the message. Your device name, unique device identifiers, events, diary, and cycle records are never added automatically.
• Purpose: used only to answer you and to find and fix problems; never shared with third parties or used for advertising or marketing.
• Retention and deletion: emails are kept in the email service we use (Gmail) and copied into our internal inquiry-handling list so we can prepare a reply. We delete the email and the list entry one year after your inquiry is resolved, and without delay if you ask.
• Processors and transfer abroad: inquiry emails are stored on servers of Google LLC (USA, Gmail), and we may use Anthropic PBC (USA, Claude) as an AI tool that helps draft replies, so the content of your inquiry is processed on its servers while we prepare a reply. The information transferred is the information listed above; it is sent over the network when you send the email and while we prepare the reply, and it is kept for the period above. Contacts: policies.google.com/privacy · anthropic.com/legal/privacy. If you do not want this transfer, do not send an inquiry email; we then cannot reply to you by email.

18. Provider and privacy officer

19. Changes

Changes are posted on this page with the effective date. Key changes in this revision (October 3, 2026): Calliary Viewer renamed "Calliary Web"; now that events and to-dos can be added, edited and deleted on the web, what can be changed, where the changes are saved, and the screen state remembered in the browser have been added (Sections 2, 14 and 20).

Key changes in the September 30, 2026 revision: new Section 17 on the information we receive when you email us, and renumbering (the provider and privacy officer section is now Section 18 and this section is now Section 19); the summary and Sections 1, 7, 11, 12, 13 and 14 updated accordingly on what reaches us; Sections 2, 6 and 7 now state what Apple Health sync writes and reads, that records read from Health stay on that device only, and that the summary synced to your other devices and shared with a partner is calculated only from records you enter; the web copy (Section 2) and place search, font downloads and Apple Intelligence (Section 14) are now described; Sections 4 and 11 correct what an invite record contains and its validity period (up to 7 days); Sections 2 and 11 now list the calendar list and theme in the web copy and state that turning "Show on the web" off deletes the web copy; new Section 20 on Calliary Viewer, with the summary and Sections 1, 13 and 14 updated accordingly; Siri and system search described (Section 14); Sections 11, 12, 14 and 17 now state that inquiry emails are copied into our inquiry-handling list, may be processed by an AI tool (Anthropic), and are deleted one year after the inquiry is resolved; the note on deleting on-device data corrected (Section 11); mail-order registration number added (Section 18).

20. Calliary Web

Calliary Web (calliary.honeybeemobility.com) is a page for seeing the calendars you keep in the app in a web browser and for adding, editing and deleting events and to-dos. The page is served from a web server we operate, but your calendar records stay in your own iCloud: the browser reads and saves them directly in iCloud, and they never pass through our servers.

• Sign-in: you sign in with your own Apple Account in the iCloud sign-in window provided by Apple. Apple handles the sign-in, and we do not receive your account information.
• What it shows: events, categories, to-dos, diary entries, decorations (stickers, photos, notes), drawings, custom stickers, and weather records from your own calendars and the shared calendars you have joined, plus the web copy (Section 2). Cycle and health records are not read.
• What you can change on the web: only events (title, dates, repeats, reminders, notes, location, category and so on) and to-dos can be added, edited or deleted. The browser saves your changes straight to your own iCloud, and they sync to your other devices just as changes made in the app do. Shared calendars and shared categories can be changed only within the permission their creator set, and your changes are visible to the other participants. Diary entries, decorations, drawings, custom stickers and weather records are never changed or deleted on the web.
• Stored in your browser: so the page opens faster next time, the records it has read are stored in that browser separately for each account, and they are deleted when you sign out, when your sign-in expires, or when a different account signs in. The language you chose is remembered in the browser, and the screen you were on (calendar, month, date and category selection) is remembered until you close that tab. Whether you stay signed in follows what you choose in Apple's sign-in window.