Terms of Service

Agreement and operator

Once approved and made effective, these Terms would govern access to the Harmonise website, applications, backend services, and related features. The legal operator has not yet been identified in this draft, so no person or entity is presently offering these Terms and they do not create a binding agreement.

An approved version must state when acceptance occurs, identify the operator, and provide verified contact details.

Eligibility

The minimum age for Harmonise has not been approved. Before launch, the operator must decide the age requirement and any parental-consent rules. A person using Harmonise for an organisation must have authority to accept the final Terms for that organisation.

Accounts and security

Users must provide accurate, current information and keep it updated. They are responsible for protecting their credentials and devices, using only authentication methods they are entitled to use, and promptly responding to suspected unauthorised access.

Depending on availability and configuration, Harmonise may support password and verified provider sign-in, server-side sessions, trusted devices, verification challenges, recovery flows, and account linking. Users must not share verification codes or private credentials. The operator may require reauthentication or verification before sensitive actions, including account deletion.

The service

Harmonise is a calendar-first planning and scheduling service. Depending on platform, configuration, plan, and rollout, it may provide calendars, events, tasks, recurrence, reminders, availability links, bookings, people and groups, shared coordination, offline use, synchronization, calendar feeds, attachments, planning summaries, and external integrations.

Some Harmonise features may be unavailable, limited, in preview, or still under development. Only features actually made available to a user form part of that user’s service. Preview features may be incomplete, change materially, or be withdrawn.

Scheduling limitations

Harmonise helps users plan; it is not an infallible record. Calendar and task data may be stale, delayed, duplicated, missing, or conflicting because of offline changes, synchronization timing, provider rules, recurrence interpretation, timezone data, expired permissions, network failure, or user input.

A displayed availability slot is advisory until a booking is finally validated and accepted. Users remain responsible for checking important dates, times, timezones, recurrence, attendees, locations, conflicts, and confirmations. Reminders, emails, and push notifications may be delayed or fail and must not be the only safeguard for an important commitment.

Sharing, bookings, and other people

Users control what they submit to invitations, groups, bookings, availability pages, feeds, and other sharing features. A booking may collect an invitee’s name, email, phone number, timezone, notes, guests, and form answers. Users must handle information about other people lawfully and provide any required notice or permission.

Public, private, management, feed, and secret links may grant access to information or actions. Anyone with a bearer-style link may be able to use it. Users must protect links, share them only with intended recipients, and disable, revoke, or rotate them when the product offers that control.

Changing or deleting a link may stop future use without removing prior bookings, events, messages, or records that must remain for participants or legitimate operational purposes.

Third-party integrations

When a user connects an identity, calendar, meeting, device-calendar, messaging, subscription, CalDAV, ICS, or other third-party service, the user authorises Harmonise to exchange information and take supported actions within the granted permissions. The third party’s own terms and privacy policy also apply.

Supported behavior varies by provider and permission. Some calendars are read-only; some writes remain provider-controlled; and some fields cannot be represented consistently. Harmonise does not guarantee uninterrupted integration availability, permanent API compatibility, or that external calendars always remain synchronized.

Disconnecting stops future Harmonise access and provider work where supported but does not itself delete content stored by the provider. Users may also need to revoke access or app-specific passwords in provider settings.

User content and files

Users retain their rights in content they submit. They grant the Harmonise operator a limited, non-exclusive licence to host, store, cache, validate, reproduce, format, synchronize, transmit, and display that content only as needed to operate, secure, and support the service and to comply with law.

Users must have the rights and permissions needed for their content and for information about other people. Content must not be unlawful, infringing, malicious, deceptive, abusive, or designed to compromise systems or other users.

Files are subject to type, size, count, safety-validation, access, storage, and lifecycle rules. Harmonise may reject, quarantine, or remove unsafe or unsupported files. Technical validation cannot guarantee that every harmful file will be detected. Users should retain independent copies of important content.

Acceptable use

Users must not:

• access another account, calendar, booking, file, integration, or system without permission;
• probe, scan, test, circumvent, or exploit security or rate limits without prior written authorisation;
• scrape, harvest, spam, overload, disrupt, or automate access outside supported interfaces;
• reverse engineer, decompile, disassemble, or attempt to derive source code, except to the extent applicable law expressly permits;
• upload malware or use Harmonise to distribute unlawful, infringing, harassing, or harmful content;
• misrepresent identity, availability, authority, invitations, bookings, or payment status; or
• use Harmonise for emergency, safety-critical, medical, legal, financial, or other mission-critical decisions where delay or error could cause serious harm.

Harmonise rights and feedback

The operator and its licensors retain rights in Harmonise, including its software, design, documentation, branding, and trademarks, excluding user content. Open-source components remain governed by their respective licences.

If a user voluntarily provides feedback, the final Terms may permit the operator to use it without restriction or compensation, while not identifying the user publicly without permission. The exact feedback clause remains unapproved and requires legal review before publication.

Privacy and communications

The approved Privacy Policy will explain how Harmonise handles personal information and will form part of the final service terms where appropriate. Users may receive necessary verification, security, billing, booking, reminder, and service messages. Optional communications are subject to available preferences and applicable law.

Device settings control how notifications appear, including whether content is visible on a locked screen.

Paid functionality

Harmonise may offer Free, Pro, or Business access depending on the platform and current product offering. Purchase capability may use RevenueCat with Apple App Store, Google Play, or web purchase paths. Exact products, prices, taxes, billing intervals, trials, promotions, public availability, and renewal terms have not been verified and are not offered by this draft.

Where a store processes a purchase, that store’s billing, cancellation, and refund rules apply. Store subscriptions generally continue until cancelled through the relevant store, even if the Harmonise account is deleted. Users should cancel recurring billing separately. Refunds remain subject to store rules, the operator’s approved policy, and non-excludable statutory rights.

An effective version must clearly disclose automatic renewal where applicable, how to manage and cancel, when access ends, how price changes are handled, and any trial conversion terms before a purchase is requested.

Service changes and availability

Harmonise may add, change, suspend, or retire features; apply plan limits; perform maintenance; or change integration availability. Where reasonable, the operator should provide notice of material changes that adversely affect paid functionality.

The service depends on networks, devices, stores, hosting, databases, email and push delivery, and third-party APIs. Interruptions, provider outages, permission expiry, data conflicts, and loss can occur. Harmonise should use reasonable care but cannot promise continuous, error-free, or permanently available service.

Export and account deletion

Users should export information they need before ending service. Static export may be available for eligible native calendars; a complete portability export is not promised by this draft.

The current account-deletion design disables access and begins a 30-day deletion process after required verification. Production operation and lawful-retention exceptions must be confirmed before these Terms become effective. Deletion does not cancel app-store subscriptions or delete events held by an external provider. Some shared records may be anonymised rather than removed where another person’s workflow must remain coherent.

Suspension and termination

Users may stop using Harmonise and may request account deletion through supported controls. The operator may suspend or terminate access to protect the service or others, address serious or repeated violations, comply with law, respond to non-payment, or discontinue the service.

Where circumstances allow, the operator should give notice and an opportunity to remedy. Immediate action may be necessary for security, unlawful conduct, or risk of harm. On termination, the user’s right to access the service ends; provisions that by their nature should survive may continue, and data handling follows the approved Privacy Policy and applicable law.

Disclaimers and consumer rights

Harmonise is a planning aid. Users remain responsible for confirming information and maintaining suitable backups and alternative communication methods. Third-party services are controlled by their providers.

Any final warranty disclaimer must be limited to what applicable law permits. Nothing in the final Terms should exclude, restrict, or modify consumer guarantees, statutory warranties, remedies, or liabilities that cannot lawfully be excluded.

Liability

No liability cap, exclusion of damages, indemnity, or allocation of risk has been approved. Those provisions depend on the operator, customers, governing law, product stage, insurance, and counsel review. They must not be inferred from this draft.

Governing law and disputes

No governing law, court, venue, arbitration requirement, or class-action waiver has been selected. Any such clause requires jurisdiction-specific legal review and must preserve non-excludable consumer rights.

General terms

An approved version should address notices, assignment, severability, waiver, the entire agreement, and how changes to the Terms become effective. Exact wording must be reviewed with the operator’s identity and governing law; this draft does not create those provisions.

App-store terms

Apple, Google, and other distribution platforms are not parties to these draft Terms. Final store-specific provisions must reflect the distribution agreement, the applicable storefront, purchase handling, licence scope, support responsibility, and any required third-party-beneficiary language. Nothing here changes a user’s rights against the store or operator under applicable law.

Contact

The operator’s legal name, service address where required, and monitored legal contact have not been confirmed. They must be supplied before these Terms are approved or offered.