Privacy Policy

About this policy

This policy is provided for Cyrena. For any question about these practices, contact hello@cyrena.app. It describes how the Cyrena iPhone app handles information when you plan your day, connect calendars, use Apple Health or track focused work. It also describes this website. Cyrena uses a local profile; it does not require a separate Cyrena online account.

What Cyrena uses, and why

Your profile and preferences

Your chosen name, optional profile photo, calendar selections, event categories, planning settings and notification preferences are stored on your device to personalise the app.

Calendar information

With your permission, Cyrena reads Apple Calendar through iOS and Google Calendar through Google’s API. Calendar information includes calendar names and identifiers, event titles, dates and times, availability, all-day status, editing permissions and attendee information used to recognise commitments.

This information is used to display your schedule, calculate load and free windows, avoid overlaps and suggest changes. When you create, move or delete an event, the change is sent to the calendar you selected. Choosing a calendar in Work settings also enables saving new completed focus segments there. Other people with access to that calendar may see the saved events.

Apple Health

You decide which Health permissions to grant. Cyrena can read menstrual flow, fatigue, state of mind, sleep and active energy data to show your history, display wellbeing context and calculate cycle and fatigue estimates on your device. When you record entries, Cyrena can request permission to write fatigue, state of mind, menstrual flow and selected symptoms (abdominal cramps, bloating and headache) to Apple Health.

Health records are stored in Apple Health. Cyrena processes permitted records locally and stores derived workload snapshots on your device for learning from your history. Health information is not uploaded to a Cyrena health-data server, sold, or used for advertising. Estimates support personal planning; they are not a diagnosis or a guarantee of how you will feel.

Focus sessions and learning history

Session titles, start and end times, timer settings and calendar export status are stored locally for the Pomodoro timer and work statistics. Workload snapshots record day-level features such as scheduled minutes, short gaps and cycle context to look for patterns alongside your fatigue check-ins.

Notifications and widgets

Optional local notifications provide check-in reminders, planning alerts and timer alerts. A local summary is shared with the Cyrena widget on the same device. Information shown in a widget or notification may be visible to someone who can see your screen; you can control notifications and remove widgets in iOS.

Google Calendar data: access, use and storage

Connecting Google Calendar is optional. Cyrena requests the following Google Calendar permissions, shown on Google’s consent screen:

• Read calendars and events (calendar.readonly) to list your calendars and read events for the dates being displayed or assessed.
• View and edit events (calendar.events) to create tasks and rest blocks, move eligible events when you apply a suggestion, delete an event you choose, and save completed focus segments to the calendar you select.

The app requests continuing access so it can refresh the connection without asking you to sign in for every calendar update. You may revoke this access at any time.

Information accessed

Google’s API returns calendar and event records. Cyrena uses calendar names, IDs, colours and access roles; event names, IDs, start and end times, time zones, all-day status, recurring-event occurrences, availability and cancellation status; attendee information and your response to invitations; and event identifiers or markers used to recognise Cyrena-created tasks, rest and focus sessions. API responses may contain additional fields within those records. Cyrena does not request Gmail, Google Contacts or Google Drive access.

How it is used

Calendar data is used to show your schedule, distinguish editable events from commitments, calculate occupied time and free windows, and prepare planning suggestions. Titles help recognise flexible tasks and travel. Attendee and response information helps avoid treating meetings or declined invitations as flexible solo work. Derived daily workload features can be stored locally and compared with your permitted Health check-ins to produce personal fatigue estimates. These calculations happen on your device.

When you save changes, Cyrena sends the relevant calendar and event IDs, title, dates, times and app-generated markers directly to Google. Moving an event updates its times. Selecting a calendar in Work settings authorises saving new completed focus segments there; choosing “Cyrena only” stops calendar export for new segments. Calendar sharing is controlled by Google: people with access to that calendar may see the saved event.

Where it is stored and how long

Calendar lists and source events are fetched as needed and held in app memory for the current view and planning calculations. Cyrena does not upload those records to its own server. Your selected calendar IDs, visibility settings, event-category overrides, work history and pending operation identifiers are stored locally. Derived workload learning is capped at the most recent 180 snapshots, and its model uses the preceding 180 days. A snapshot is not a full copy of a calendar event.

Google access and refresh tokens are stored in the iOS Keychain with device-only protection. An access token is refreshed when needed while the connection is authorised. Disconnecting Google clears these credentials, removes its displayed calendar data and requests token revocation. It does not erase previously saved work history, derived snapshots or Google Calendar events. Reset Cyrena to clear local history and preferences; disconnect Health to clear workload learning.

Sharing and human access

Google API data is not sold, shared with advertisers or data brokers, used for credit or lending decisions, or used to train general-purpose AI models. The developer does not receive routine copies of your calendars and cannot browse the data held inside the app. No external AI service receives your calendar or Health records from Cyrena.

Information leaves your device when you request an operation with the connected service, explicitly share an export, or choose to include it in a support message. Export destinations and support email providers process what you send under their own policies. Do not include private calendar or Health details unless needed for your request.

Connections and sharing

Google sign-in happens through Google. Cyrena stores access credentials in the iOS Keychain and communicates with Google over HTTPS to access the calendars you authorise. Your Google password is not stored by Cyrena.

Cyrena’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used for the calendar and planning features described here, not advertising, sale or training general-purpose AI models.

Optional usage analytics

Usage analytics is optional and off until you choose to share it. Declining does not restrict app features. When enabled, Cyrena sends Amplitude a limited set of app opens, onboarding starts/completions, Summary/Calendar/Work visits, plan-review outcomes, timer actions and subscription-flow events. The payload includes the event name and time, session and event identifiers, a random app-generated user/device identifier, app and operating-system versions, SDK/platform information, the test or production environment and schema version. Subscription-flow events can include a general feature entry point; a Health-related forecast entry point is replaced with the generic value “plus”.

These event payloads do not include your profile name or photo, task or focus-session text, calendar event contents, calendar credentials, Health records, cycle dates, fatigue values or other wellbeing measurements. Amplitude automatic interaction capture, advertising identifier collection, IDFV collection, location derivation and automatic SDK diagnostics are disabled. A random identifier still allows events from the same installation to be associated; these records should not be described as anonymous. Network providers necessarily receive connection information such as the source IP address when delivering requests, even though Cyrena disables IP/location tracking in Amplitude's event configuration.

Change your choice in Settings → Privacy & data → Product analytics. Turning analytics off stops new events and opts the active SDK out. Cyrena also instructs the SDK to clear local event queues. It does not erase events already received by Amplitude. The random identifier remains available in settings so you can include it in a deletion request to hello@cyrena.app. Test and production analytics use separate configured projects.

Screen recordings

Ordinary usage analytics does not record the screen. A separate developer QA preview exists only when launched with the dedicated analytics QA option, on the test environment, and after separate consent. After that separate consent, it sends masked recordings and interactions from the subscription-options screen to Amplitude. It uses conservative text masking, excludes web views and is suspended for purchase dialogs. It shows a recording indicator and stop control. It is not offered in the ordinary TestFlight or production interface. Turning usage analytics off also revokes this separate replay choice.

Subscriptions and free testing

During TestFlight testing, all features are available without a subscription. TestFlight and explicitly configured local testing modes are designed to bypass subscription purchases, leave the free replan allowance unchanged and skip RevenueCat initialization. This testing access does not promise permanently free access after the beta. In the paid app path, Apple processes payments; Cyrena receives verified transaction and entitlement information through StoreKit, not payment-card details. RevenueCat separately receives subscription transactions, purchase/product identifiers and entitlement status for purchase reporting. Its SDK also sends technical metadata including app/build/SDK/OS versions, device/platform details, storefront when available and Apple's identifier for vendor (IDFV). Disabling automatic attribution identifier collection does not remove the IDFV HTTP header in the SDK currently included in Cyrena. Calendar and Health content is not passed to RevenueCat. RevenueCat reporting is separate from the optional Amplitude usage choice.

Cyrena keeps up to 200 payment-flow diagnostic records locally (event type, feature entry point and time); these are exportable and clearable in Help & support. In the paid/free-tier app path, the three-successful-replan allowance is kept in the device Keychain. Resetting app preferences does not reset it. Apple may provide TestFlight diagnostics and feedback that testers choose to send.

Apple and Google process information within their own services under their respective Apple and Google privacy policies.

If you create an export and use the iOS share sheet, the copy goes to the destination you choose. Review it before sharing: it may contain personal information, work titles and a day assessment.

Your permissions and choices

• Connect or disconnect individual providers in Cyrena’s Connections screen.
• Change Health permissions in the Health app and calendar permissions in iPhone Settings. Disconnecting inside Cyrena stops its use of that connection; system permissions are managed separately.
• Disconnect Google in Cyrena to clear its local credentials and request token revocation. You can also remove access in your Google Account connections.
• Choose “Cyrena only” in Work settings to keep new work segments out of a connected calendar. Previously saved calendar events remain there.
• Use Privacy & data → Export your data to create a local JSON export. It includes your profile name, planning preferences, current day assessment, work sessions and health entry counts. It does not contain the full Apple Health history or source calendar event contents.

Storage, retention and deletion

Local profile details, preferences and work sessions remain until you remove them or reset Cyrena. Learning history is capped at the latest 180 snapshots; the workload model uses snapshots from the preceding 180 days. Disconnecting Health clears the stored workload learning history. Editing a calendar event later does not rewrite an earlier snapshot.

To clear local app data, open Privacy & data → Reset Cyrena and confirm. This removes the local profile and photo, preferences, work history, cached insights and connection credentials, and disconnects the providers. You will return to onboarding.

Resetting or deleting Cyrena does not delete records in Apple Health or events in Apple or Google Calendar. This includes check-ins and calendar events previously created through Cyrena. Manage or delete these records in the source service. Exported files and copies you shared must be deleted separately.

Local app data may be included in device backups depending on your Apple settings. Apple manages the storage and retention of those backups. Keep your device and account protected; no storage or transmission method can be guaranteed completely secure.

This website

This website does not access your app’s Health records, calendars or work history. Its pages do not add advertising trackers, product analytics scripts or contact forms. The hosting platform may process technical request information, such as IP address and browser details, and use authentication cookies to deliver and protect the site. Hosting-platform processing is separate from the app’s local data processing; see the hosting provider’s privacy policy.

Support messages and privacy requests

If you email hello@cyrena.app, we receive your email address, message and any attachments you choose to send. We use them to respond, investigate the issue and handle privacy requests. Email is handled by our email service provider, Google Workspace. We keep correspondence for as long as needed to resolve the request and meet applicable obligations; you may request deletion by email.

You can ask about access, correction or deletion of information received by support. We cannot remotely read or erase data that exists only on your iPhone, in your Apple Health account or in your connected calendars. The in-app controls and provider controls described above let you manage those records directly. Depending on where you live, additional privacy rights may apply.

Policy updates

Changes to the app’s data practices will be reflected on this page with an updated date. New access to device or connected-service data remains subject to the relevant permission prompts.

Privacy questions

For privacy questions or requests, email hello@cyrena.app.

For instructions on permissions, exporting and resetting data, visit Support.