Privacy Policy
This Privacy Policy explains how Harmonise handles information when people use its calendar-first planning, scheduling, sharing, and account features.
Using or accessing Harmonise means that you acknowledge this Privacy Policy and accept the Terms of Service. Questions about this Privacy Policy can be sent to Harmonise through the Harmonise contact address.
Last updated:
Scope and operator
This policy is intended to cover the Harmonise marketing website, web application, mobile applications, backend services, and related support communications. Before publication, it must identify the legal person or entity that operates Harmonise and provide verified privacy contact details. Until then, this draft does not establish an effective privacy notice.
Information Harmonise handles
- Account and profile information: name, email address, public username, profile image, password hash, email-verification status, linked Google or Apple identity, timezone, week-start choice, locale, and notification preferences.
- Authentication and security information: sessions, access and refresh credentials, trusted-device identifiers and names, verification and recovery records, request identifiers, security events, and information used to prevent abuse, including IP address in relevant public or security flows.
- Planning content: calendars, events, tasks, subtasks, recurrence rules, reminders, completion status, descriptions, dates, times, timezones, locations, meeting links, attendees, organisers, availability, conflicts, and other content a user supplies.
- Sharing and booking information: people and group relationships, invitations, public usernames and link slugs, booking names, email addresses, phone numbers, notes, form answers, attendee counts, booking status, and cancellation or rescheduling authority.
- Integration information: provider account identifiers, calendars and events obtained from providers, OAuth permissions, encrypted access or refresh credentials, sync cursors, provider event identifiers, webhook and reconciliation records, and user-supplied CalDAV or feed credentials where supported.
- Files: profile images, event or task attachments, filenames, media types, sizes, upload state, validation results, and storage metadata.
- Device and technical information: app version, platform, installation identifiers, push tokens, local sync state, network and error information, and diagnostic data where diagnostics are enabled.
- Subscription information: store and RevenueCat customer identifiers, product and entitlement information, purchase status, renewal or expiry state, and transaction-related records. Harmonise does not need payment-card details when payment is handled by an app store or its billing provider.
Calendar descriptions, invitees, locations, meeting links, attachments, and booking answers may contain sensitive or confidential information. Users should add only information they are permitted to use and share.
Where information comes from
Information may come directly from a user; from another person who invites, books, shares, or coordinates with that user; from a connected calendar, identity, meeting, device-calendar, subscription, or notification provider; from the user’s device during offline synchronization; or from technical operation of the service.
How information is used
Harmonise uses information to create and secure accounts; operate calendars, tasks, recurrence, reminders, availability, bookings, groups, and sharing; synchronize data across devices and providers; store and deliver files; send requested service communications; administer subscriptions and entitlements; diagnose failures; prevent fraud and abuse; support account deletion; and comply with valid legal obligations.
The lawful bases that apply in each relevant jurisdiction have not been approved. This draft does not claim consent, contract, legitimate interests, or another legal basis where that decision remains unresolved.
Calendar and meeting integrations
When a user chooses an integration, Harmonise may exchange supported calendar, event, attendee, reminder, conference, and account information with that provider according to the permissions granted. Depending on configuration, provider approval, platform, plan, and rollout, supported integrations may include Google Calendar, Microsoft Outlook Calendar, Apple and Yahoo CalDAV, generic CalDAV, ICS import or subscription, Google Meet, Microsoft Teams, Zoom, Discord, and manually entered meeting URLs. Not every provider is necessarily available to every user.
Disconnecting an integration stops future synchronization and removes or revokes stored access where supported, but it does not delete events or other content held by the external provider. Cached data may remain on a device until it synchronizes or local data is cleared. Provider account settings may offer additional revocation controls.
A private ICS subscription address or another secret link can function like a password: anyone who receives it may be able to access the information it exposes. Users should protect, rotate, disable, or revoke these links when appropriate.
Sharing features and information about other people
Availability pages, bookings, invitations, calendar feeds, and similar links may reveal the information selected for that surface. Public booking responses are designed not to reveal private conflict details, but invitees and recipients receive the information necessary for the workflow.
Users may provide information about people who do not have Harmonise accounts, such as attendee, invitee, organiser, or guest details. Users are responsible for having an appropriate basis to provide that information and for giving any notice required by law.
Device and offline storage
Harmonise supports offline and synchronized use. Mobile devices may store account-scoped data in SQLite and use secure or application storage for credentials, device identity, preferences, and compatibility data. The web application may store an account-scoped SQLite replica in browser Origin Private File System storage, along with limited browser storage and secure HTTP-only authentication cookies.
Local copies can include calendars, events, tasks, sync changes, conflicts, and related metadata that also exist on Harmonise servers. Removing the app, clearing browser site data, signing out, or completing account deletion may affect local copies differently depending on device and synchronization state.
Notifications and communications
Harmonise may send verification, password-reset, welcome, account-security, booking, reminder, and other service messages by email, push notification, inbox, or an enabled messaging integration. Users can control supported notification categories in product settings and device settings. Some security or transactional messages may still be necessary to operate an account.
Push notification content may appear on a locked device according to operating-system settings. Delivery is not guaranteed, and a failure to deliver an optional message does not reverse an already completed action.
Diagnostics and analytics
Harmonise calculates planning summaries from calendar and task information for presentation to the user. In environments where it is enabled, Harmonise may also use Sentry for gated error and performance diagnostics, with controls intended to limit the personal information included in diagnostic reports.
Server and hosting systems may generate request, security, operational, and access records. Before this policy becomes effective, Harmonise must confirm which analytics, advertising, cookie, session-replay, sale, targeted-advertising sharing, profiling, and significant automated-decision practices apply in production.
Payments and subscriptions
Harmonise includes purchase capability using RevenueCat and application-store billing. If purchasing is made available, the store or billing provider processes the purchase and may provide Harmonise with customer, product, transaction, entitlement, renewal, and expiry information. Store privacy terms also apply. Production product and offering configuration, public availability, prices, trials, refunds, and renewal disclosures must be confirmed before this policy becomes effective.
Retention and deletion
Harmonise retains information while needed to provide the service, secure accounts, meet legal obligations, resolve disputes, and maintain required business records. The current deletion design uses a 30-day retention period before final purge. Actual production operation, worker enablement, backup handling, and lawful-retention exceptions must be verified before this policy becomes effective.
Under the current design, accepting account deletion disables access and revokes sessions before a later cleanup process removes or anonymises account-owned information, subject to required checks and lawful retention. External-provider events are not deleted by deleting a Harmonise account, and some shared records may need to remain for another person’s workflow.
Users should export any information they need before deletion. Static calendar export may be available for eligible Harmonise calendars, but the scope and availability of a complete data export or privacy-access export require confirmation.
Security
Harmonise uses technical and organisational safeguards intended to protect information, including hashed passwords and verification values, server-side session checks, trusted-device verification, access controls, encrypted provider credentials, signed or temporary file URLs, ownership checks, and deletion workflows. No service can guarantee absolute security, and this policy does not describe local database encryption as end-to-end encryption.
International processing
Service providers and connected integrations may process information in countries other than the user’s country. The operator must identify relevant processing locations and approve any required transfer mechanisms or safeguards before publication.
Privacy rights and choices
Depending on applicable law, a person may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or review of certain decisions, and to complain to a privacy regulator. These rights can depend on location, legal basis, and exceptions.
Product controls may allow users to edit profile information, change notification preferences, disconnect integrations, revoke or rotate certain links, export eligible calendars, and request account deletion. A verified privacy-request channel and identity-verification process must be supplied before this policy becomes effective.
Children
The minimum age and children policy for Harmonise have not been approved. Applicable age rules, any parental-consent approach, and required store declarations must be resolved before this policy becomes effective.
Changes to this policy
When an effective policy is later approved, material changes should be communicated through an appropriate channel and accompanied by an updated effective or last-updated date. Any required renewed consent or notice must be handled according to applicable law.
Contact
The legal operator’s name, address where required, and a monitored privacy contact have not been confirmed. They must be added before this document is approved or takes effect.