Terms of Service

1. Agreement, authority, and eligibility

These Terms of Service form a legally binding agreement between the person or organisation using HoneyNotify (the “Customer”) and the HoneyNotify operator identified in the Customer's account, order, invoice, or other contractual record (“HoneyNotify”, “we”, “us”, or “our”). They govern the public website, hosted dashboard, application programming interfaces, software development kits, push-delivery platform, documentation, support, and related services we make available.

The agreement includes these Terms, the Privacy Notice, the Acceptable Use Policy, any Data Processing Addendum (“DPA”) that applies, any plan or service terms displayed when the Customer subscribes, and any order form signed or expressly accepted by both parties. By creating an account, ticking an acceptance box, using the Service, or signing an order form that refers to these Terms, the Customer accepts the agreement. If the Customer does not agree, it must not create an account or use the Service.

A person accepting for an organisation confirms that they have authority to bind it. If they do not have that authority, they must not accept or use the Service for that organisation. The Service is intended for people aged 18 or over acting for business, professional, development, or organisational purposes. It is not directed to children as account holders.

If mandatory consumer law applies despite the business-facing nature of the Service, nothing in the agreement removes rights that cannot lawfully be waived. A consumer should contact support before subscribing if the business terms, automatic renewal, digital-service start, or cancellation arrangements are unclear.

The agreement begins when the Customer first accepts it or uses the Service and continues until terminated. An order form may specify a separate subscription start date, committed term, or renewal arrangement. Customer purchase orders are for administrative convenience only; additional or inconsistent terms in them do not amend the agreement unless HoneyNotify expressly agrees in writing.

2. Key definitions

“Account” means the Customer's HoneyNotify organisation or workspace. “Authorised User” means an employee, contractor, agent, or other person whom the Customer permits to access that Account. “Customer Application” means an app, website, or service owned or controlled by the Customer and connected to HoneyNotify.

“Customer Data” means information, content, configuration, credentials, device records, user identifiers, attributes, events, instructions, and other material submitted to or processed through the Service by or for the Customer. “Customer Content” means the part of Customer Data communicated to recipients or incorporated in a notification, including titles, bodies, images, links, actions, and custom payloads. “Recipient” means a user or device to which the Customer directs communications or whose activity the Customer records through the Service.

“Documentation” means the current technical and user documentation HoneyNotify makes available for the Service. “Order Form” means a written or electronic ordering document expressly accepted by the parties. “Plan” means the package and associated features, allowances, and support level selected by the Customer. “Provider” means an upstream delivery service such as Apple Push Notification service (“APNs”), Firebase Cloud Messaging (“FCM”), or a browser's Web Push infrastructure.

“Service” means the HoneyNotify website, dashboard, APIs, SDK-related services, delivery infrastructure, analytics, journeys, exports, support, and Documentation made available under the agreement. “Subscription Period” means the paid billing period or committed term shown at purchase or on an Order Form. “Usage Data” means technical and operational measurements about use of the Service, excluding Customer Data in a form that identifies the Customer, an Authorised User, or a Recipient after it has been aggregated or irreversibly de-identified.

Headings are for convenience. “Including” means “including without limitation”. References to writing include email and authenticated in-service communications where appropriate. A singular term includes the plural and vice versa where the context permits.

3. The HoneyNotify Service

HoneyNotify provides hosted tools for registering iOS, Android, and browser push destinations; associating devices with customer-defined users and attributes; defining audiences; creating, scheduling, and localising notifications; sending through configured Providers; receiving engagement events; reporting results; operating webhooks; creating exports; and automating customer-defined journeys.

The Service separates client and server trust. Restricted public client keys may be used by a Customer Application for supported registration, event, and removal operations. Secret server API keys are used by trusted Customer systems for sending and management. The Documentation describes current endpoints, permissions, payloads, limits, and supported SDK behaviour. The Customer must follow it and must not infer that a public key is safe for an undocumented operation.

HoneyNotify grants the Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the agreement to access and use the hosted Service for its internal business purposes and to integrate its Customer Applications, subject to the Plan and agreement. The Customer may permit Authorised Users and contractors to use the Account on its behalf, but remains responsible for their compliance.

The Service passes delivery requests to Providers and records available outcomes. A response indicating that HoneyNotify or a Provider accepted a request is not a guarantee of final delivery, display, timing, or human attention. Delivery depends on valid credentials and tokens, device connectivity, operating-system settings, browser state, Provider policies, network conditions, recipient permissions, battery controls, and other matters beyond HoneyNotify's control.

HoneyNotify does not provide a general emergency alert network, medical device, payment authorisation system, or guaranteed communications channel. The Customer must not rely on push notifications as the sole method for emergency, safety-critical, life-critical, legally required, or time-critical communications. It must maintain appropriate alternative channels, escalation, monitoring, and human oversight.

4. Accounts, Authorised Users, and security

The Customer must provide accurate registration and organisation information, keep it current, and use an email address it is entitled to control. Each Authorised User must have an individual account. Shared logins obscure accountability and are not permitted where individual access can reasonably be provisioned. The Customer controls its team membership and role assignments and must promptly remove access no longer needed.

The Customer is responsible for activity performed through its Account, Customer Applications, and credentials except to the extent directly caused by HoneyNotify's breach of the agreement. It must apply least-privilege access, use strong unique passwords, enable multi-factor authentication where appropriate, protect recovery methods, and ensure its devices and systems are adequately secured.

The Customer must protect API keys, identity-signing keys, webhook secrets, provider credentials, browser subscription keys, device tokens, session information, and export files. Secret keys must not be embedded in a mobile application, browser bundle, public repository, downloadable package, analytics event, crash report, or client-visible log. If a credential could have been exposed, the Customer must revoke or rotate it promptly rather than waiting for confirmed misuse.

The Customer must notify HoneyNotify promptly through the support channel if it suspects unauthorised access, compromised credentials, tenant-boundary failure, or other security incident involving the Service. It must provide reasonable information and cooperation, preserve relevant evidence, and avoid public disclosure that would unnecessarily increase risk before a coordinated remedy is available.

HoneyNotify may require password changes, credential rotation, re-authentication, additional verification, or temporary access restrictions when reasonably necessary to protect the Account or Service. HoneyNotify will not ask the Customer to disclose a password or complete secret API key through ordinary support correspondence.

5. Customer Applications and integration duties

The Customer is responsible for its Customer Applications, servers, code, Provider accounts, developer memberships, domains, certificates, credentials, and configuration. It must use supported protocols, maintain current integration code, test new releases, process token changes, and implement permission and event hooks correctly. HoneyNotify support may offer guidance but does not assume control of the Customer's code or release process.

The Customer must configure the correct APNs environment, FCM project, Web Push origin, application identifiers, and Provider credentials. It must have authority to use every credential and destination it supplies. Using credentials belonging to another organisation or mixing development and production environments can cause failed, misdirected, or duplicate communications and is prohibited.

Where the Customer uses verified user identity, it must generate signed identity tokens only on a trusted server, derive the subject from an authenticated session, use the correct app issuer, restrict token lifetime as documented, and prevent one Recipient from claiming another person's identity. The Customer must not accept an arbitrary user identifier supplied by an untrusted client and sign it without authentication.

The Customer must implement retries safely. For notification creation, it must reuse the same idempotency key when retrying the same logical message. A new idempotency key may create a new notification and can result in duplicate delivery. The Customer must respect HTTP status codes, retry guidance, rate limits, pagination, scheduling constraints, and maximum payload sizes.

The Customer must test notification appearance, deep links, actions, permissions, localisation, timezones, expired links, missing media, offline behaviour, and Provider failure on supported platforms. It must ensure that links and app routes remain safe after delivery. HoneyNotify is not responsible for defects in Customer Applications, customer-controlled URLs, or content rendered by operating systems and browsers.

Migration tools are provided to assist supported imports, not to guarantee perfect identity continuity. Provider tokens may rotate, become invalid, belong to a different app or environment, or change before first registration. The Customer must validate the source export, use matching Provider credentials, review import results, and plan a reversible rollout.

6. Customer responsibilities and acceptable use

The Customer controls its Recipients, purposes, content, targeting, timing, frequency, and event collection. It must comply with the Acceptable Use Policy, applicable law, Provider rules, app-store requirements, browser policies, consumer-protection rules, advertising standards, and industry requirements that apply to its communications.

Before collecting device or activity information or sending a notification, the Customer must provide required notices and obtain, record, and maintain any necessary permission or consent. It must honour withdrawals, opt-outs, operating-system permission changes, suppression requests, quiet hours, age restrictions, and frequency expectations. It must be able to explain its lawful basis and provide evidence of permission where reasonably requested during an escalated abuse investigation.

The Customer must ensure that Customer Content is accurate as to its sender and purpose. It must not use the Service for unsolicited bulk messaging, spam, deceptive promotions, impersonation, fraud, phishing, credential theft, malware, unlawful surveillance, harassment, stalking, threats, hate, exploitation, sexual abuse material, unlawful discrimination, intellectual-property infringement, or content that facilitates illegal conduct.

The Customer must not send content likely to cause serious harm when displayed unexpectedly on a lock screen or shared device. Sensitive health, financial, authentication, precise-location, government-identifier, or similarly confidential information should not be placed in visible notification content. One-time passwords or security alerts require appropriate expiry, rate controls, anti-enumeration protections, and an alternative recovery process.

The Customer must not:

• access or attempt to access another customer's tenant, data, keys, or systems;
• probe, scan, or test vulnerabilities without prior written authorisation under an applicable security-testing process;
• reverse engineer the hosted Service except to the limited extent a restriction is prohibited by law;
• interfere with integrity or availability, introduce malicious code, or overload HoneyNotify or a Provider;
• bypass authentication, plan allowances, rate limits, safety controls, or technical restrictions;
• use multiple Accounts, false details, rotating identifiers, or other means to evade enforcement or charges;
• benchmark the Service for publication in a misleading, insecure, or unlawful manner;
• rent, lease, sell, sublicense, white-label, or provide the Service as a standalone service bureau without written permission; or
• use the Service or its output to create a competing hosted notification platform by copying protected non-public features, Documentation, or interfaces.

The Customer must investigate complaints and promptly stop communications that are unlawful, unauthorised, or materially inconsistent with recipient expectations. HoneyNotify may ask for integration details, consent evidence, content samples, sending patterns, or remediation steps. Failure to cooperate may result in throttling or suspension.

7. Customer Data and Customer Content

The Customer retains ownership of Customer Data as between the parties. The Customer grants HoneyNotify and its subprocessors a worldwide, non-exclusive, limited licence during the agreement to host, copy, cache, validate, transmit, transform, display to Authorised Users, and otherwise process Customer Data only as needed to provide, secure, support, and maintain the Service, follow documented instructions, enforce the agreement, and comply with law.

The Customer represents that it and its Authorised Users have all rights, permissions, notices, and lawful bases needed to provide Customer Data and instruct its processing. It is responsible for accuracy, quality, legality, and appropriateness; for mapping its external user identifiers to the correct people; and for avoiding excessive or irrelevant data. HoneyNotify does not review every message or audience before sending and does not endorse Customer Content.

The Customer must not submit special-category, highly sensitive, regulated, or children's data unless the processing is lawful, necessary, supported by the agreement and DPA, and protected by appropriate controls. Unless HoneyNotify expressly agrees in writing, the Service is not designed to store full payment-card data, account passwords, private cryptographic keys unrelated to Provider configuration, government identification numbers, medical records, or data subject to sector-specific hosting obligations.

HoneyNotify may generate Usage Data and aggregated or de-identified statistics from operation of the Service. HoneyNotify may use that non-identifying information to operate, secure, analyse, and improve the Service, plan capacity, and report general performance. HoneyNotify will not attempt to re-identify information it has represented as irreversibly de-identified and will not disclose Usage Data in a way that identifies the Customer or a Recipient.

Customer exports are provided for portability and operational use. The Customer is responsible for securing downloaded files, limiting access, transferring them safely, and deleting obsolete copies. Export availability is time-limited and is not a backup service. The Customer should retain independent copies of information it needs to meet its own legal or continuity duties.

8. Plans, usage, fees, and payment

Plan features, allowances, and prices are those displayed when the Customer subscribes or set out in an Order Form. Allowances may concern active devices, applications, team members, API use, support, storage, or other resources. “Unlimited” describes the absence of the stated ordinary billing counter; it does not remove the Acceptable Use Policy, reasonable rate and safety controls, Provider limits, technical capacity, or restrictions against abusive or unlawful traffic.

A monthly active device is determined using the measurement described on the pricing page or in the applicable Plan. HoneyNotify's good-faith service records are the basis for usage calculations. The Customer must choose a Plan suitable for expected use and may be required to upgrade, reduce usage, or agree custom terms if use materially exceeds the selected allowance or creates unusual operational cost or risk.

Paid Plans renew automatically for successive periods of the same length unless cancelled before renewal or an Order Form states otherwise. By adding a payment method or starting paid checkout, the Customer authorises Stripe or another identified payment provider to charge recurring fees, taxes, and properly disclosed adjustments. The Customer must keep billing details and payment authority current.

Fees are quoted exclusive of taxes unless stated otherwise. The Customer is responsible for VAT, sales, use, withholding, and similar taxes arising from its purchase, except taxes based on HoneyNotify's net income. If law requires withholding, the Customer must provide evidence and, where legally permissible, ensure HoneyNotify receives the amount it would have received without the withholding. Valid tax-exemption documentation must be provided before invoicing or charge where practical.

Plan changes take effect at the time and price shown during confirmation. An upgrade may be immediate and prorated; a downgrade may wait until renewal. Except where the agreement, an Order Form, or mandatory law says otherwise, fees already charged for a started Subscription Period are non-refundable and unused time or allowance does not carry over.

If payment is overdue or fails, HoneyNotify may retry collection, ask the Customer to update its payment method, restrict paid features, prevent new sends, downgrade the Account where technically suitable, or suspend access after reasonable notice. The Customer remains responsible for amounts accrued before cancellation or suspension. It must raise a good-faith billing dispute promptly and continue paying undisputed amounts.

Free or promotional Plans may be changed, limited, or withdrawn on reasonable notice and may carry lower allowances or support. Credits, trials, coupons, and promotions have no cash value, may be subject to separate conditions, and may not be combined or transferred unless stated.

9. Privacy, data protection, and deletion

Each party must comply with data-protection law applicable to its own processing. The Privacy Notice explains HoneyNotify's controller processing. Where HoneyNotify processes personal data in Customer Data on the Customer's behalf, the DPA applies and forms part of the agreement. If there is a conflict about that processor activity, the DPA takes priority over these Terms.

The Customer is the controller of Recipient data in ordinary use and is responsible for lawful instructions, transparency, legal bases, consent where required, data minimisation, accuracy, retention, rights handling, and any data-protection impact assessment. It must not instruct HoneyNotify to process personal data unlawfully. HoneyNotify may notify the Customer if, in our reasonable opinion, an instruction infringes applicable data-protection law and may pause the affected processing while the parties address it.

HoneyNotify uses subprocessors to provide infrastructure, delivery, payment, security, support, and related functions. The Customer authorises subprocessors under the DPA and acknowledges that APNs, FCM, and browser push services are essential to requested delivery. The Customer also independently chooses its Provider accounts, webhook destinations, integrations, Recipients, and regions, and is responsible for transfer and disclosure consequences of those choices.

HoneyNotify provides supported export, user deletion, device disablement, retention, and organisation-deletion controls. Organisation deletion is scheduled with a seven-day safety period and can be cancelled while pending. API export files expire after 24 hours. Backups and records subject to legal, security, billing, or dispute retention may age out separately as explained in the Privacy Notice and DPA.

The Customer must export needed information before termination or deletion. Once a deletion request is processed, HoneyNotify has no obligation to recover Customer Data from live systems. Data may remain temporarily in protected backups and will not be restored to ordinary use except as needed for disaster recovery, after which applicable deletion processes continue.

10. Confidentiality

“Confidential Information” means non-public information disclosed by one party (“Discloser”) to the other (“Recipient”) that is marked confidential or should reasonably be understood as confidential given its nature and circumstances. Customer Data, secret credentials, non-public security information, product roadmaps, pricing in a private Order Form, and business and technical information may be Confidential Information.

The Recipient will use the Discloser's Confidential Information only to perform or exercise rights under the agreement. It will protect it with at least reasonable care and no less care than it uses for its own similar information. It may disclose Confidential Information only to personnel, affiliates, professional advisers, and subcontractors who need it for the relationship and are bound by confidentiality obligations.

Confidential Information does not include information the Recipient can demonstrate was lawfully known without restriction before disclosure, becomes public without breach, is received lawfully from another source without duty, or is independently developed without use of the Discloser's information. Feedback is governed by the licence below rather than this confidentiality section.

If law or a valid authority requires disclosure, the Recipient may disclose the minimum required. Where legally permitted, it will give prompt notice so the Discloser can seek protection and will provide reasonable cooperation at the Discloser's expense. Nothing requires a party to challenge lawful process or risk penalty.

On request or termination, the Recipient will return or delete Confidential Information where reasonably practicable, subject to ordinary backups, legal retention, security evidence, and information needed to establish or defend claims. Any retained information remains protected. These duties continue for five years after disclosure, and for trade secrets and personal data for as long as they remain protected by applicable law.

11. Ownership, SDKs, Documentation, and feedback

HoneyNotify and its licensors retain all rights in the Service, hosted software, designs, Documentation, branding, domain names, improvements, and related intellectual property. Except for the limited access right expressly granted, the agreement transfers no ownership to the Customer. Rights not expressly granted are reserved.

HoneyNotify SDK source code and sample code may be made available under a separate open-source or repository licence. That licence governs copying, modification, and distribution of the relevant code. The hosted Service, credentials, HoneyNotify marks, and non-code materials are not automatically licensed under the SDK's licence. Third-party libraries remain subject to their own notices and licences.

The Customer may use Documentation internally to integrate and operate the Service and may copy reasonable extracts for its Authorised Users and contractors, provided notices are preserved and access remains limited. It must not publish substantial non-public Documentation, misrepresent examples as a delivery guarantee, or use HoneyNotify marks in a way that implies endorsement or partnership.

If the Customer voluntarily provides suggestions, ideas, or feedback, it grants HoneyNotify a worldwide, perpetual, irrevocable, royalty-free right to use and incorporate that feedback without restriction or payment. This does not grant HoneyNotify ownership of Customer Data or permit disclosure of Customer Confidential Information.

If either party believes material accessible through the Service infringes its rights, it should send a sufficiently detailed notice through support. HoneyNotify may remove or restrict disputed material while investigating and may ask for evidence of ownership, authority, identification of the work, location of the material, and a good-faith statement. False or abusive notices may breach these Terms.

12. Providers and third-party services

The Service interoperates with third-party services, including APNs, FCM, browser push infrastructure, Stripe, Customer webhook destinations, and other integrations the Customer chooses. Those services are governed by their own terms, privacy notices, developer rules, availability, and technical limits. The Customer is responsible for maintaining every third-party account and permission it needs.

HoneyNotify does not control and is not responsible for a third party's service, content, security, policy change, suspension, API change, data handling, or decision to reject or delay a request. We may adapt or discontinue an integration if the third party changes or withdraws the relevant service, or if continued integration creates material legal, security, or operational risk.

The Customer authorises HoneyNotify to transmit Customer Data to a selected third party as necessary to carry out the Customer's instructions. This includes sending tokens and message payloads to Providers, billing references to Stripe, and event payloads to Customer-configured webhook endpoints. The Customer must not configure a destination unless it has authority to disclose the relevant data there.

Links from HoneyNotify to third-party websites are supplied for convenience and do not imply endorsement. The Customer is responsible for evaluating third-party products and for charges they impose. HoneyNotify fees do not include Apple, Google, domain, certificate, hosting, connectivity, or other third-party costs unless an Order Form expressly says so.

13. Availability, maintenance, and support

HoneyNotify will provide the Service with reasonable skill and care and operate the HoneyNotify-controlled network against the commitments published in the Service Level Agreement. The standard network availability commitment is 99.999%. Free service has a 48-hour initial ticket-response target. Paid service has a two-hour initial ticket-response target through the ticket system, 24 hours a day, seven days a week, 365 days a year. Response targets are not guaranteed resolution times, and an accepted Order Form may set different or additional service levels.

HoneyNotify prepares for planned maintenance by bringing additional nodes online and moving traffic away from the affected infrastructure. If a server fails, automatic failover routes traffic through another available HoneyNotify server while engineers investigate and resolve the failure. Provider outages, customer-controlled systems, internet failures outside the HoneyNotify-controlled network, attacks, and events outside reasonable control remain subject to the boundaries described in the SLA.

Support availability and priority depend on the Plan. Paid customers may receive service credit when verified HoneyNotify-controlled downtime qualifies under the SLA, subscription terms, or Order Form. Support covers reasonable help with documented Service behaviour. It does not include writing or debugging the Customer's application, managing Provider accounts, legal advice, data-cleaning projects, custom development, or guaranteed recovery of information the Customer deleted. HoneyNotify may require reproducible details, request IDs, timestamps, redacted payloads, logs, and cooperation.

The Customer must monitor its own sends, Provider credentials, webhook endpoints, integration errors, usage, and recipient complaints. It must maintain business-continuity measures appropriate to the importance of its communications. HoneyNotify may provide dashboards and alerts, but the Customer remains responsible for acting on them.

Rate limits, queueing, payload validation, frequency caps, and other safeguards protect shared reliability. HoneyNotify may adjust reasonable technical limits as traffic and threats change. We will use reasonable efforts to avoid applying them in a way that arbitrarily prevents ordinary compliant use of a paid Plan.

14. Service changes, beta features, and Terms updates

HoneyNotify may add, improve, replace, or remove features to maintain security, comply with law or Provider requirements, address abuse, improve performance, or develop the product. We will use reasonable efforts not to materially reduce the core paid functionality the Customer purchased during a current Subscription Period without advance notice, unless urgent legal, security, or third-party circumstances make notice impracticable.

If a change materially reduces paid core functionality and no substantially equivalent alternative is available, the Customer may contact support promptly. Where appropriate, the parties will seek a reasonable remedy, which may include migration assistance, a proportionate credit, or termination of the affected paid Service. This paragraph does not apply to free, beta, preview, deprecated, or third-party-dependent features.

Features labelled alpha, beta, preview, early access, evaluation, experimental, or similar are provided for testing. They may be incomplete, less secure or reliable, subject to additional terms, and changed or withdrawn at any time. The Customer must not use them for production, sensitive, or business-critical processing unless HoneyNotify expressly confirms suitability. Feedback and diagnostic information about them may be used to improve the Service.

HoneyNotify may update these Terms for legal, security, Provider, service, or commercial reasons. The current version and effective date will be posted on the website. For a material change that adversely affects an existing paid Customer, we will provide reasonable advance notice through email, dashboard, or another appropriate channel where practical. Changes required urgently by law or security may take effect sooner.

Continuing to use the Service after updated Terms take effect constitutes acceptance. If the Customer does not agree, it must stop using and cancel before the effective date. Changes do not retroactively rewrite a claim that arose before they took effect unless law permits and the parties expressly agree.

15. Investigation, throttling, and suspension

HoneyNotify may investigate activity and preserve relevant records where we reasonably suspect abuse, compromise, unlawful processing, a Provider complaint, excessive operational risk, or breach of the agreement. The Customer must cooperate, provide truthful information, and take reasonable remedial steps. HoneyNotify is not required to disclose security-sensitive detection methods or information that would prejudice another customer or investigation.

We may throttle, quarantine, reject, disable, or suspend affected messages, devices, keys, integrations, Authorised Users, features, or the Account where reasonably necessary to:

• contain a security incident or credential compromise;
• stop spam, fraud, unlawful content, or harm to Recipients;
• protect HoneyNotify, Providers, customers, or shared infrastructure;
• comply with law, valid process, or a Provider requirement;
• address overdue payment or Plan-limit evasion;
• prevent material breach or repeated complaints; or
• avoid material liability or reputational damage arising from the Customer's use.

Where practicable, HoneyNotify will give notice, explain the general reason, and allow a reasonable opportunity to remedy. We may act without advance notice where delay could increase harm, expose data, breach law or Provider obligations, or impair the Service. Suspension will be scoped and no longer than reasonably necessary where practicable.

The Customer remains responsible for fees during a suspension caused by its breach or non-payment. Suspension does not waive either party's termination rights or other remedies. HoneyNotify may report credible threats or apparently unlawful conduct to affected Providers or authorities where legally required or reasonably necessary to protect people or systems.

16. Cancellation, termination, and consequences

The Customer can cancel an ordinary self-service paid Plan through the billing controls. Cancellation stops renewal at the end of the current paid period unless the confirmation states an immediate effect. The Customer may continue using paid features until that end date if the Account remains compliant. Deleting an Account is separate from cancelling billing and follows the privacy deletion workflow.

A committed Order Form may be non-cancellable during its stated term except for breach or another express right. Either party may terminate if the other materially breaches the agreement and does not remedy a remediable breach within 30 days after written notice. A party may terminate immediately if the breach cannot be remedied, the other becomes insolvent or ceases business subject to applicable insolvency law, or continued performance would be unlawful.

HoneyNotify may terminate or close a free Account after reasonable notice if it is inactive, presents risk, or the free Plan is withdrawn. We may terminate immediately for serious or repeated abuse, fraud, deliberate security interference, unlawful messaging, attempted tenant access, sanctions restrictions, or evasion of a prior suspension.

On termination, the Customer's right to use the Service ends and it must stop using credentials and HoneyNotify materials. Outstanding fees become due. The Customer should export needed data before the effective date. HoneyNotify will delete or return Customer personal data in accordance with the DPA, privacy controls, seven-day safety period where applicable, backup cycle, and legal retention duties.

Provisions that by nature should survive will survive, including accrued payment obligations, confidentiality, ownership, disclaimers, indemnities, liability limits, dispute provisions, and general interpretation. Termination does not affect rights or liabilities accrued beforehand.

17. Warranties and disclaimers

Each party warrants that it has authority to enter the agreement. HoneyNotify warrants that it will provide paid Services with reasonable skill and care and will not knowingly introduce malicious code into the hosted Service. The Customer's exclusive remedy for breach of this service warranty is for HoneyNotify to use reasonable efforts to correct the affected Service or, if correction is not commercially reasonable, permit termination of that affected paid Service and refund prepaid fees for the unused remainder.

The Customer warrants that its use, instructions, Customer Data, Customer Applications, and Customer Content comply with the agreement and law; that it has necessary rights and permissions; and that it will not make misleading claims about HoneyNotify or delivery outcomes.

Except for express warranties and rights that cannot lawfully be excluded, the Service is provided “as is” and “as available”. HoneyNotify disclaims implied conditions and warranties of merchantability, satisfactory quality, fitness for a particular purpose, non-infringement, uninterrupted or error-free operation, and results arising from use. We do not warrant that every defect will be corrected, every attempted send will be delivered, analytics will reflect activity unavailable from Providers or devices, or the Service will meet requirements not documented and agreed.

Security measures reduce risk but do not guarantee that the Service or internet transmission is invulnerable. The Customer is responsible for evaluating whether the Service is suitable for its data, recipients, regulatory environment, availability needs, and intended communications. Documentation, examples, estimates, roadmap statements, and support suggestions do not create a warranty unless incorporated into an Order Form.

18. Indemnities and third-party claims

The Customer will defend HoneyNotify and its personnel against a third-party claim arising from Customer Content, Customer Data, a Customer Application, the Customer's relationship with Recipients, or the Customer's breach of sections 5 to 7, and will pay damages, settlements, and reasonable external legal costs finally awarded or agreed. This obligation does not apply to the extent the claim was caused by HoneyNotify's unauthorised use of Customer Data or breach of the agreement.

HoneyNotify will defend the Customer against a third-party claim that the unmodified paid hosted Service, when used as authorised in the United Kingdom, infringes that party's patent, copyright, or registered trade mark, and will pay damages, settlements, and reasonable external legal costs finally awarded or agreed. HoneyNotify has no obligation for claims caused by Customer Data, Customer Content, Customer Applications, third-party services, combinations not supplied by HoneyNotify, modification by others, use outside the agreement, or continued use after notice of an alleged infringement.

If an infringement claim is likely, HoneyNotify may obtain the right to continue use, modify or replace the affected feature with a materially equivalent non-infringing alternative, or terminate it and refund prepaid fees for the unused remainder. This states HoneyNotify's entire liability and the Customer's exclusive remedy for intellectual-property infringement by the Service.

An indemnified party must notify the indemnifying party promptly, allow it to control the defence and settlement, and provide reasonable cooperation at the indemnifying party's expense. Delay in notice reduces the obligation only to the extent it causes material prejudice. No settlement may admit fault by, impose non-monetary obligations on, or fail to fully release the indemnified party without its written consent, not to be unreasonably withheld.

19. Limits of liability

Nothing in the agreement excludes or limits liability for death or personal injury caused by negligence; fraud or fraudulent misrepresentation; breach of a term implied by section 12 of the Sale of Goods Act 1979 or section 2 of the Supply of Goods and Services Act 1982 where applicable; the Customer's obligation to pay fees; or any other liability that cannot lawfully be excluded or limited.

Subject to that paragraph, neither party is liable under or in connection with the agreement for indirect or consequential loss, or for loss of profit, revenue, business, contracts, anticipated savings, goodwill, reputation, opportunity, or data, whether direct or indirect, to the extent such categories may lawfully be excluded. HoneyNotify is not liable for loss caused by a Provider, third-party service, Customer Application, customer-controlled credential or destination, Recipient setting, or the Customer's failure to follow Documentation or maintain a reasonable fallback.

Subject to the first paragraph, each party's aggregate liability arising out of or relating to the Service, whether in contract, tort including negligence, misrepresentation, restitution, statute, or otherwise, will not exceed the fees paid or payable by the Customer for the affected Service during the 12 months immediately before the first event giving rise to the claim. For a free Service, HoneyNotify's aggregate liability is limited to £100.

The limitations apply to the maximum extent permitted by law and reflect the allocation of risk and pricing. They apply collectively to the Customer and its Authorised Users and to HoneyNotify and its suppliers. Multiple claims or events do not increase the cap. If an Order Form expressly provides a different cap for a particular Service, that cap controls for that Service.

A party must take reasonable steps to mitigate loss. No claim may be brought more than one year after the claiming party knew or ought reasonably to have known the facts giving rise to it, unless a longer period cannot lawfully be shortened. Nothing prevents a party from seeking an injunction or other urgent equitable relief for misuse of intellectual property, Confidential Information, credentials, or systems.

20. General legal terms

Force majeure

Neither party is liable for delay or failure caused by events outside its reasonable control, including natural disaster, epidemic, war, terrorism, civil disorder, labour dispute not limited to its own workforce, government action, utility or internet failure, widespread cyberattack, Provider outage, or failure of third-party networks. The affected party will use reasonable efforts to reduce impact and resume performance. Payment obligations already incurred are not excused.

Assignment and subcontracting

The Customer may not assign or transfer the agreement without HoneyNotify's prior written consent, except with notice as part of a genuine merger, reorganisation, or sale of substantially all relevant assets where the successor is not a direct competitor, is able to perform, and accepts the agreement. HoneyNotify may assign the agreement to an affiliate or successor as part of a reorganisation, financing, or sale of the business. An invalid attempted assignment is void. HoneyNotify may use subcontractors and remains responsible for its contractual obligations.

Notices

HoneyNotify may send operational and legal notices to the Account email, through the dashboard, or by posting where the agreement expressly permits. The Customer must keep contact details current. Notices to HoneyNotify must be sent through the support contact identified in the dashboard or an address stated in an Order Form and clearly identify the Customer and subject. A notice is deemed received when delivered, or for dashboard notice when made available to an active Account, subject to evidence of failure.

Relationship and third-party rights

The parties are independent contractors. The agreement does not create a partnership, joint venture, agency, fiduciary, employment, franchise, or exclusive relationship. Neither party may bind the other. A person who is not a party has no right to enforce the agreement under the Contracts (Rights of Third Parties) Act 1999, except a permitted successor or an indemnified HoneyNotify affiliate or person may rely on a provision expressly benefiting it.

Entire agreement and order of precedence

The agreement is the entire agreement about the Service and replaces prior proposals, representations, and discussions on that subject. The parties do not rely on statements not set out in it, without limiting liability for fraud. For a conflict, an expressly negotiated Order Form takes priority, then the DPA for personal-data processing, then these Terms, then incorporated policies, then Documentation. A more specific term controls over a general one only for its subject.

Waiver, severability, and interpretation

Failure or delay to exercise a right is not a waiver. A waiver must be clear and applies only to the stated instance. Rights and remedies are cumulative. If a provision is unlawful or unenforceable, it will be modified to the minimum extent necessary to make it effective or removed if modification is impossible; the remainder continues. No rule construing ambiguity against the drafter applies. The English version controls to the extent permitted if a translation conflicts.

21. Governing law, disputes, and contact

An Order Form may identify governing law and jurisdiction. If it does not, the agreement and any non-contractual obligations are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction. Mandatory rights to use another court or law remain unaffected where they cannot be waived.

Before filing a claim, each party should give the other written details and allow at least 30 days for good-faith efforts to resolve the dispute, unless urgent injunctive relief, a limitation deadline, security containment, or non-payment makes that impracticable. Discussions intended to settle a dispute may be treated as without prejudice where law permits.

Questions about these Terms, the identity of the contracting operator, billing, or notices can be sent through the support details shown in the HoneyNotify dashboard. Do not include passwords, full API keys, identity-signing keys, provider credentials, or unnecessary recipient information in an initial message.