Terms of service

Effective date: 1 May 2026 Version: 1.0 — initial publication

In short: qub lets you seal a message and lock it until a date you choose. Once sealed, it's permanent in permanent storage — even we can't delete it. You own the encryption key (it lives in your share link); we are not in the trust chain. Read §3 (Permanence) before you seal. Your local consumer-protection rights always apply, no matter what these terms say below.

Who We Are

qub.social is operated by VSPRY AUSTRALIA PTY LIMITED (ABN 41 631 026 330), Level 38, 71 Eagle Street, Brisbane QLD 4000, Australia. References to "qub", "we", "us", "our", and "the Operator" mean that entity, together with its successors and permitted assigns.

General contact: support@qub.social. Subject prefixes are listed in §20.

1. Agreement

By accessing or using qub.social ("the Service"), you agree to these Terms of Use. If you do not agree, do not use the Service. These terms constitute a binding agreement between you and the Operator.

1.1 Order of Precedence

These terms govern. If the Refund Policy, User-Generated Content Policy, Sanctions & Restricted Use Policy, or Privacy Policy is more specific on a topic those policies cover, the more-specific policy wins for that topic. If any sub-policy gives you a stronger right than these terms, that stronger right applies.

2. What qub Does

qub is a timed commitment and publication platform. It allows you to:

  1. Seal a qub — your content is encrypted on your device using timelock encryption.
  2. Store the sealed qub — the encrypted payload is written to permanent, tamper-proof public storage.
  3. Share a link — recipients see a countdown until the reveal date.
  4. Reveal — after the reveal date, the content becomes publicly decryptable by anyone with the link.
  5. Sign your qubs — optionally generate a signing key and attach a cryptographic signature to prove authorship. You may verify your email against your public key to make your identity visible to viewers.
  6. Agree via pacts — seal structured terms between two parties. Both sides commit to the same conditions before the reveal date.
  7. Get notified — subscribe to a sealed qub to receive an email when it reveals.
  8. Embed — paste a single-line snippet into a blog, Notion page, Substack post, or any HTML to render any sealed qub on your own site. The embed displays the live countdown and the reveal in place.
  9. Connect via MCP — AI agents and programmatic clients can interact with qub through the qub MCP server, which exposes the same seal, read, and status surface as the developer API.

We provide the tools to seal, sign, upload, and view content. We do not host or control the permanent storage layer or the drand timelock beacon that governs when content becomes decryptable. By design, we are not in the trust chain — locking and unlocking happens on your device, and a sealed qub can be verified by anyone in the world without our participation. As more of the internet becomes machine-generated, the value of this kind of provable temporal commitment grows.

3. Permanence — Read This Carefully

Content sealed through qub is designed to be stored permanently in permanent public storage. Subject to the continued operation of the permanent storage layer and the cryptographic assumptions disclosed in §13.3, sealed content cannot be deleted, edited, or recalled by you, by us, or by anyone.

By sealing a qub, you acknowledge and accept that:

Do not seal content that you may want to delete, retract, or keep private indefinitely. This is not a limitation we can engineer around — it is a fundamental property of the storage layer.

Long-horizon unlocks. When you choose a reveal date more than 2 years in the future, the seal confirmation screen shows an extra disclosure. Long-horizon qubs depend on the drand timelock network staying operational. If drand needs to migrate to a new chain, you may need recovery steps to unlock your qub at reveal time.

For reveal dates more than 5 years out, you must check a second box explicitly accepting this risk before the seal proceeds. By completing the seal, you confirm that you have read and accepted this disclosure.

EU and UK consumers — express request for immediate performance. If you are a consumer resident in the European Union or the United Kingdom and you are sealing a qub on a paid plan, by completing the seal you (a) expressly request that we begin performance of the Service before the end of the 14-day cancellation period under the EU Consumer Rights Directive and the UK Consumer Contracts Regulations 2013 and (b) acknowledge that, to the extent the Service is fully performed for the qubs you seal during that period, you lose your statutory right of withdrawal for those consumed units. Unconsumed billing periods remain refundable — see the Refund Policy §4.

4. Eligibility

You must be at least 13 years old to use qub, or the minimum age required for digital consent in your jurisdiction, whichever is higher. By using the Service, you represent that you meet this age requirement. If you are between 13 and 18 (or the age of majority in your jurisdiction), you represent that your parent or legal guardian has reviewed and agreed to these terms on your behalf. We do not knowingly provide the Service to anyone under 13. See the Privacy Policy §9 for the data-protection treatment of users below the applicable minimum age.

4.1 Sanctions and Restricted Use

You must not use the Service if doing so would cause us, our infrastructure providers, or our users to breach applicable sanctions laws or related restrictions. The full set of restricted-use rules — who must not use qub, what it must not be used for, and how we respond when we believe the Service is being used in breach — is set out in the Sanctions & Restricted Use Policy. That policy is incorporated into these Terms by reference; if it conflicts with these Terms on a sanctions-specific topic, the Sanctions & Restricted Use Policy wins.

5. Your Content

5.1 Ownership

You retain ownership of the content you seal. Sealing a qub does not transfer any intellectual property rights to us.

5.2 Licence to Operate

By sealing a qub through qub, you grant us a limited, non-exclusive, royalty-free licence to transmit the encrypted payload to permanent storage and to facilitate its display through qub's viewer — including the qub embed iframe rendered on third-party sites — after the reveal date. This licence is necessary for the Service to function.

5.3 Responsibility

You are solely responsible for the content you seal. Because we cannot read your content before or during the sealing process (subject to the narrow exception in our Privacy Policy §2.1 for server-side seals via the API), you acknowledge that content moderation is necessarily reactive.

At the point of sealing, you confirm that:

6. Prohibited Content

The categories below are the high-level prohibitions; the canonical, plain-English list with examples and the moderation, intellectual-property, and notice-and-action procedures live in the User-Generated Content Policy.

You must not use qub to seal or distribute:

We take the timed-release nature of qub seriously. Abuse patterns specific to timed publication — such as doxxing timed to an event, coercive "dead man's switch" threats, or defamation timed for maximum impact — are explicitly prohibited and will be treated with the same severity as the underlying prohibited conduct.

7. Abuse Reporting and Enforcement

The full notice-and-action mechanism — including the report shape, response-time commitments, statement-of-reasons obligation, appeal route, and intellectual-property notice / counter-notification procedure — is set out in the User-Generated Content Policy. The clauses below remain the authoritative summary.

7.1 Reporting

qub's viewer includes a report function. You may report a qub for: illegal content, harassment or threats, publication of personal information, or other concerns. Reports submitted before a qub's reveal date are accepted, but content verification may not be possible until after the reveal.

7.2 Enforcement Actions

If we determine that a qub violates these terms — whether through a user report, a lawful order, or our own review after reveal — we may:

Denylisting is the primary enforcement mechanism. It provides practical removal from qub's product surface but does not remove the underlying data from permanent storage.

If you disagree with an enforcement decision, you may appeal under the procedure in the User-Generated Content Policy §6.5. EU users may also refer disputes to a certified out-of-court dispute settlement body under Article 21 of the EU Digital Services Act.

7.3 Moderation Limitations

We do not receive or have access to your plaintext content during or after the sealing process (subject to the narrow exceptions in our Privacy Policy §2.1 and §2.3, and to the server-side seal trust model disclosed in §9.2 below). Moderation is necessarily reactive and metadata-driven until a qub becomes publicly decryptable. We do not and cannot pre-screen content.

8. Pricing, Payments, and Fulfilment

8.1 Free Tier

The free tier provides a limited number of qubs at no charge. The free tier is soft-enforced and subject to change. We currently subsidise the permanent storage costs for free qubs. The commitment to subsidise future free-tier qubs is not perpetual — we may change the free-tier offering at any time, but qubs already sealed remain in permanent storage at the time of upload regardless of any subsequent change to the free-tier policy.

8.2 Paid Tiers

Paid tiers are subscriptions processed through Stripe — currently a Pro plan for human creators (available as a monthly or annual subscription) and a Builder plan for AI agents and programmatic clients (monthly subscription with API access, server-side seal, and webhook delivery). A previously-sold one-time Creator purchase ($19.00 AUD) remains serviced for existing customers but is no longer available for new sales; refund mechanics for that legacy plan live in the Refund Policy §2. Authoritative current pricing is displayed on /pricing and on the purchase screen within the app. Prices are listed in United States Dollars (USD); Stripe Adaptive Pricing may display and charge the local-currency equivalent at checkout, with the conversion handled by Stripe.

Applicable taxes are determined by Stripe at checkout.

8.3 Fulfilment and Delivery

qub is a digital service. When you complete a purchase, your paid entitlement is activated automatically and immediately. There is no physical delivery. Your entitlement is confirmed on the purchase success screen and is available for use straight away.

Entitlements are delivered by writing a record to our entitlement store, keyed to your device identifier. You will also receive an email confirmation of your purchase from Stripe.

8.4 Entitlements

Paid entitlements are bound to a per-device identifier in your browser. Restoration on a new device — or after browser data has been cleared — is automatic via two paths: (a) when you complete a Stripe purchase, the post-purchase webhook links the device to the email Stripe collected at checkout, so the success page hydrates the linked record without any extra step; and (b) you may sign in on any device via magic link to inherit your existing paid entitlement. The legacy manual-restoration path remains available — email support@qub.social with the subject prefix [BILLING] if neither automatic path resolves your situation.

8.5 Refund Policy

Refunds are governed by our standalone Refund Policy, which is the canonical statement of when refunds are available, how to request one, and how long it takes. The summary below is provided for convenience only — the Refund Policy controls if there is any inconsistency.

In short: a 14-day cooling-off refund is available on Pro and Builder subscriptions if you have not yet sealed any qubs or consumed any billable API quota. Once you have used the Service, the units you have consumed are not refundable on a discretionary basis, but you remain entitled to a refund where the Service fails to deliver, where you have been charged in error, or where your local consumer-protection law (including the EU/UK right of withdrawal and the Australian Consumer Law's non-excludable consumer guarantees) gives you a stronger right.

To request a refund, email support@qub.social with the subject-line prefix [REFUND] and the email address you used at checkout. See the full Refund Policy for the complete process, eligibility, and timelines.

8.6 Cancellation Policy

Both Pro and Builder subscriptions can be cancelled at any time via the Stripe-hosted Customer Portal, reachable from the account popover (Pro) or the developer portal (Builder). Cancellation takes effect at the end of your current billing period — you keep access for the time you have already paid for, and you are not charged again. Annual Pro mid-term cancellations stop the next renewal but do not automatically pro-rate the remaining months; pro-rata refunds are discretionary and considered case-by-case under the Refund Policy.

8.7 Price Changes

We may change pricing for future purchases at any time. Price changes do not affect entitlements you have already paid for. For active monthly or annual subscriptions, we will give at least 30 days' advance notice of any price increase before it takes effect at your next renewal. For Builder business users, the additional notice and timing rules in §9.3 also apply.

8.8 Disputes and Complaints

If you have a problem with a purchase — including an entitlement that did not activate, an incorrect charge, or any billing concern — please contact us at support@qub.social with the subject line [REFUND] before initiating a chargeback or dispute with your bank or card issuer. We will work to resolve the issue promptly.

We aim to respond to payment-related inquiries within 2 business days.

8.9 Payment Processing

All payments are processed by Stripe. We do not receive or store your credit card number, expiry date, or CVC. Your payment is subject to Stripe's terms of service and privacy policy. By completing a purchase, you authorise Stripe to charge the amount displayed at checkout to your chosen payment method.

9. API and Developer Access

9.1 General

If you access qub through our API, you are bound by these terms together with the usage notes published in the developer documentation at https://qub.social/api (rate limits, fair-use rules, request shape, the server-side trust-model disclosure, and changelog). API keys are personal to you, non-transferable, and must not be shared. We may revoke API access for abuse, excessive usage, or violation of these terms — subject to the suspension and termination procedure in §17 and, for Builder business users, the additional protections in §9.3.

9.2 Server-Side Sealing — Trust-Model Change

Server-side sealing through the API is a deliberate trust-model change from client-side sealing: when you use the seal endpoint, our servers temporarily process your plaintext to encrypt and upload it. By using the seal endpoint, you accept this distinction. The plaintext is encrypted in-process and is not retained.

9.3 Builder Plan — Business User Terms

The Builder plan is offered to business users within the meaning of EU Regulation 2019/1150 (the "P2B Regulation"). Where you access qub as a Builder customer, the additional clauses below apply in addition to the rest of these terms. Where the Builder-specific terms in this §9.3 conflict with another clause on a Builder-specific topic, this §9.3 controls.

Statement of reasons (P2B Art. 4). If we restrict, suspend, or terminate your access (for example, by disabling an API key, blocking a device identifier, or removing access to a feature), we will provide a statement of reasons in writing on a durable medium at the time of the action — except where the restriction concerns illegal content notified to us by a public authority, where it would conflict with a legal obligation, or where we have given prior notice for a repeated breach and the statement of reasons has already been issued. The statement will identify the specific facts and circumstances that led to the action and reference the term, condition, or law allegedly breached.

T&C change notice (P2B Art. 3). We will give Builder business users at least 15 days' notice of any material change to these terms before it takes effect. Where the general 30-day notice in §18 applies (material changes that reduce your rights), the longer notice period controls. Earlier changes are permitted only where (a) required by law or court order, (b) necessary to address a security incident or material risk of harm, or (c) the change introduces a new feature or service or is otherwise unambiguously favourable to the Builder business user, in which case it may take effect immediately on notice.

Termination notice (P2B Art. 4). We will give a Builder business user at least 30 days' written notice before terminating their access, except where (a) we are subject to a legal or regulatory obligation that requires earlier termination, (b) the business user has repeatedly infringed these terms despite prior notice for the same conduct, or (c) earlier termination is necessary to address a security incident or material risk of harm.

Internal complaint-handling (P2B Art. 11). Builder business users may submit complaints — about alleged non-compliance with these terms, technological issues directly related to the Service, or measures taken or behaviour by us that affects the business user — by emailing support@qub.social with the subject prefix [BUILDER]. The system is free to use. We will acknowledge receipt within 5 business days and provide a reasoned outcome within 30 business days. We track complaints for the purposes of P2B Art. 11(4) reporting.

Mediation (P2B Art. 12). For disputes between us and a Builder business user that are not resolved through the internal complaint-handling system above, we identify the following two mediators with which we are willing to engage in good faith to attempt to reach an out-of-court settlement:

  1. The Law Society of England and Wales — Mediation Service, 113 Chancery Lane, London WC2A 1PL, United Kingdom — https://www.lawsociety.org.uk/topics/mediation.
  2. Centre for Effective Dispute Resolution (CEDR), 70 Fleet Street, London EC4Y 1EU, United Kingdom — https://www.cedr.com.

Both mediators provide remote mediation, are accessible to business users across the European Economic Area, can mediate in English (and provide multilingual mediator panels for other EU languages), and are independent and impartial. Mediation costs are shared between the parties as agreed at the time, subject to the mediator's published fee schedule. Engaging in mediation does not affect either party's right to commence court proceedings under §16 if mediation does not lead to settlement.

Ranking, ancillary services, and differentiated treatment. The Service does not present rankings of business users or their content to consumers, so the ranking-transparency obligations in P2B Art. 5 are not engaged. The Service does not offer ancillary services to business users that are also offered by third parties (Art. 6). We do not engage in differentiated treatment between Builder business users on factors that materially affect their ability to use the Service (Art. 7).

Data access (P2B Art. 9). The data Builder business users have access to through the Service is described in the developer documentation. Builder business users have direct access to the data they generate through the Service — qubs sealed via their API key, webhook delivery records, and usage metrics — for the duration of their subscription and for at least 30 days after termination, after which the data is deleted in accordance with our retention practices.

10. Identity, Email, and Signing

10.1 Signing Keys

If you generate a signing key, it is created and stored on your device. You are responsible for safeguarding your private key. We do not have access to your private key. Under the current architecture we cannot recover it if it is lost from your device. Loss of your private key means you can no longer sign new qubs with that identity — previously signed qubs remain verifiable.

10.2 Email Attestation

When you verify your email against your signing key, qub records the attestation on your identity record so that publicly-attributed qubs can display a "verified email" badge alongside your handle on the viewer countdown. The email address itself is never published — viewers see only the boolean badge and your chosen @handle. The address is held in our metadata store and shared only with the third parties listed in the privacy policy. You may revoke your attestation at any time, which removes the badge from future viewer displays. Revocation does not retroactively change qubs that were signed while the attestation was active — those qubs are stored permanently in permanent storage.

10.2a Public Attribution

When you seal a qub, the upload includes an optional Author storage tag carrying your signing-key fingerprint. The reference creator app attaches this tag only when you explicitly enable "Public attribution" at seal time. By default the tag is omitted and the qub is unattributed in permanent storage; nothing in permanent storage links the qub to your handle, your email, or your other qubs. When you enable attribution, the fingerprint resolves to your handle and any associated public profile fields at viewer-render time. The decision is per qub and is recorded permanently along with the qub itself.

10.3 Notify-Me Subscriptions

When you subscribe to a sealed qub's reveal notification, we store your email address until the notification is delivered, then delete it. Notifications are best-effort — we do not guarantee delivery. You may receive at most one email per subscription.

10.4 Pacts

A pact is a private contract between the parties to it. We are not a party to any pact, do not interpret its terms, and accept no responsibility for its formation, performance, enforceability, or the consequences of its publication after the reveal date. We provide the staging, signing, and storage tools only.

By creating or counter-signing a pact, you accept that the terms you commit to — and the identifiers of both parties (names, contact details) — will become permanently and publicly visible after the reveal date, subject to the same permanence disclosures in §3. You are responsible for ensuring that all parties to a pact consent to its terms and to the inclusion of their identifier in the sealed body before sealing.

Email binding for co-sign. When you stage a pact against a counter-party email address, that counter-party must verify the same address via a single-use link before they are permitted to co-sign. The verified address is bound to the staged pact server-side for 15 minutes. This is a deliberate anti-impersonation measure — it prevents a bystander with the staging link from completing the agreement in place of the intended counter-party.

Frozen acknowledgement text. Pacts in the structured/v1 schema embed verbatim acknowledgement language covering statutory rights, legal capacity, authority, and (for sellers) unencumbered title. These strings are frozen — both parties sign the exact bytes, regardless of UI language. A separate structured/v2 schema is required for any wording change.

Pact invite rate limits. To protect recipients from being used as a spam relay, we impose a per-recipient daily cap (currently ten invitations per email address per UTC day — see Privacy Policy §2.3) on the number of pact invitations that can be emailed to a single address, and a per-device daily cap on staging attempts (current value documented in the in-app error message). These limits are soft-enforced and subject to change. Exceeded caps return a descriptive error and do not consume your entitlement quota.

Retraction. The initiator of a pact may retract a staged pact at any time before the counter-party co-signs. Retraction is cryptographically authenticated and deletes the staged record; no qub is ever written to permanent storage for retracted pacts. Once co-signed and sealed, retraction is no longer possible — the permanence disclosures in §3 apply.

11. Embedding qubs on Third-Party Sites

The <qub-embed> web component lets you embed a sealed qub on a blog, Notion page, Substack issue, or any HTML surface using a two-line snippet. The countdown — and the reveal, when the date arrives — render inside a sandboxed iframe loaded from qub.social. The qub still decrypts in the visitor's browser, so we are not in the trust chain even when the qub lives on someone else's site. Publishers should pin against the production loader URL (/embed/v1.js) for stability across major-version cutovers; the unpinned /embed.js alias is provided for convenience but may break on a v2 release. By embedding a qub on a site you control, you agree that the same content terms in §5 and the prohibited-content rules in §6 apply to that surface, and that we may denylist a qub from the embed if it is denylisted in the qub viewer.

If you embed a qub on a site you operate, you are responsible for compliance with the laws and your own site's terms in respect of the embedded content, including any disclosures required to your visitors (such as cookie banners, age gates, or content warnings). The qub embed iframe processes no data the host site has not already loaded.

12. Intellectual Property

qub, qub.social, and the qub logo are trademarks of VSPRY INTERNATIONAL PTY LIMITED ABN 59 631 026 027, used under licence. The Service software is proprietary. These terms do not grant you any right to use our trademarks or to access, copy, or modify our source code.

13. Disclaimers

13.1 Third-Party Infrastructure

qub depends on third-party infrastructure that we do not control, currently including (without limitation):

The specific providers may change. We are not responsible for the availability, performance, or policies of these services. If the permanent storage layer becomes unavailable, sealed qubs may become inaccessible. If drand becomes unavailable, content may not become decryptable at the expected time.

13.2 No Guarantee of Availability

We provide qub on an "as is" and "as available" basis. We do not guarantee that the Service will be uninterrupted, error-free, or available at all times. We may suspend or discontinue the Service, or any feature, on at least 30 days' notice to active paid subscribers, except where a shorter notice period is required by law, court order, security incident, or material risk of harm. On discontinuation we will refund the unconsumed portion of any prepaid subscription under the Refund Policy.

13.3 Encryption

qub uses timelock encryption based on the drand network — your content is locked with a time-based key, and the unlock key is released publicly by drand only when the date you chose arrives.

On top of that, we add an outer encryption layer. Its key lives in your share link's URL fragment (the part after the #); browsers don't transmit fragments to any server, so the key never reaches us by default.

We make no guarantee that the cryptographic methods used will remain secure indefinitely. Advances in computing or cryptanalysis could theoretically affect the security of sealed content before its intended reveal date. We will disclose any known material risks as they arise.

13.4 Beta and Experimental Features

We may from time to time make beta, preview, or experimental features available, identified as such in the product. These features are provided as-is, may be modified, withdrawn, or made paid at any time without notice, and are not subject to the price-change notice in §8.7 or the change-notice timings in §9.3 and §18. The statutory-rights savings in §13.6 continue to apply.

13.5 Force Majeure

Neither party is liable for delay or failure to perform caused by events outside its reasonable control, including failure of third-party infrastructure (including any service named in §13.1), outages of public communications networks, government action, war, civil unrest, pandemic, natural disaster, or any other event of a similar nature. Where such an event materially prevents performance of a paid plan for more than 30 consecutive days, either party may terminate the affected paid plan by written notice and the unconsumed portion of any prepaid amount will be refunded under the Refund Policy. This clause does not apply to your obligation to pay for Service already provided.

13.6 Statutory Rights

Nothing in §13.1, §13.2, or §13.3 limits any non-excludable consumer guarantee under the Australian Consumer Law, any right under EU Directive 2019/770 (Digital Content and Services), the EU Consumer Rights Directive, the UK Consumer Rights Act 2015, or any other consumer-protection law that cannot lawfully be excluded. If you are an EU or UK consumer and the Service is not in conformity with our description of it or with reasonable expectations, your statutory rights — including the right to have the Service brought into conformity, a price reduction, or termination with refund — apply in addition to anything in these terms.

14. Limitation of Liability

Statutory rights savings. Nothing in these terms excludes, restricts, or modifies any consumer guarantee, right, or remedy you have under the Australian Consumer Law, the EU Consumer Rights Directive, EU Directive 2019/770 (Digital Content and Services), the UK Consumer Rights Act 2015, or any other applicable consumer-protection law that cannot lawfully be excluded; and nothing limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot be limited or excluded by law.

Liability cap. Subject to the savings clause above, our total aggregate liability to you for any and all claims arising out of or in connection with the Service is limited to the greater of (a) the total amount you have paid to us in the 12 months immediately preceding the event giving rise to the claim and (b) AUD 100.

Re-supply election (services not for personal use). Where, under section 64A of the Australian Consumer Law, our liability for breach of a consumer guarantee in respect of a service that is not of a kind ordinarily acquired for personal, domestic, or household use may be limited, our liability is so limited at our election to either (a) the supplying of the services again or (b) the payment of the cost of having the services supplied again.

Excluded losses. Subject to the savings clause above, and except for liability that cannot lawfully be excluded, we are not liable for:

15. Indemnification

Builder business users only. If you are a Builder business user, you agree to indemnify and hold harmless the Operator, its directors, employees, and agents from and against any third-party claim, loss, damage, regulatory fine, or reasonable legal cost arising from (a) your content sealed or distributed through the Service, (b) your breach of these terms, including the prohibited-content rules in §6, (c) your unlawful use of the Service, or (d) your sealing of personal data about a third party without that third party's consent in violation of applicable data-protection law. This indemnity does not apply to losses to the extent caused by our own breach, negligence, or wilful misconduct.

Procedural conditions. As a condition of indemnification we will (a) promptly notify you of the claim, (b) allow you (at your expense) to assume control of the defence and settlement negotiations with counsel reasonably acceptable to us, and (c) not settle any claim that admits your liability or imposes a non-monetary obligation on you without your prior written consent (not to be unreasonably withheld).

Consumer users. Consumer users (including users on the free tier and on the Pro plan) are not subject to the indemnity in this §15. Consumers remain solely responsible for the content they seal under §5.3, but we do not require an indemnity from them, in line with the consumer-protection principle that broad indemnities by consumers are unenforceable in many jurisdictions.

16. Governing Law and Forum

These terms are governed by the laws of the State of Queensland, Australia. Any dispute arising from these terms or your use of the Service is subject to the non-exclusive jurisdiction of the courts of Queensland.

If you are a consumer resident in the European Union, the United Kingdom, or another jurisdiction with mandatory consumer-protection law, (a) you may bring proceedings against us in the courts of your country of residence and we may bring proceedings against you only in those courts; (b) the mandatory provisions of the law of your country of residence apply to your contract with us in addition to the laws of Queensland; and (c) nothing in these terms displaces those mandatory provisions.

17. Termination

Suspension and termination by us. We may take action against your access to the Service in proportion to the seriousness of the conduct:

For Builder business users, the additional termination-notice protections in §9.3 also apply.

Statement of reasons. Except where giving reasons would conflict with a legal obligation or compromise an investigation by a public authority, we will give you a written statement of reasons at the time of any suspension or termination, identifying the specific facts and the term or law allegedly breached.

Appeal. You may appeal a suspension or termination decision under the procedure in our User-Generated Content Policy §6.5. We will review appeals on the merits within a reasonable time.

Termination by you. You may stop using qub at any time. There is no account to close. If you wish to have your device identifier and associated entitlement records deleted, contact us at support@qub.social with the subject line prefix [PRIVACY]. Deletion requests are handled under the timelines in the Privacy Policy §6.2.

Effect on sealed qubs. Termination does not affect content already sealed — it remains in permanent storage regardless of your account status, subject to denylisting under §7.2 and the User-Generated Content Policy §6.

17.1 Survival

Sections 3 (Permanence), 5.1 (Ownership), 5.2 (Licence to Operate), 12 (Intellectual Property), 13 (Disclaimers, including 13.1–13.6), 14 (Limitation of Liability), 15 (Indemnification), 16 (Governing Law and Forum), 19 (Severability), 19.1 (Entire Agreement), 19.2 (No Waiver), and any other obligation that by its nature should survive, survive termination of these terms.

17.2 Assignment

We may assign these terms, in whole or in part, to an affiliate, to a successor in connection with a merger, acquisition, or sale of substantially all our assets, or to a successor operator of the Service, on notice to you. You may not assign these terms without our prior written consent, except that you may transfer your account on death or incapacity to a person legally entitled to receive it.

18. Changes to These Terms

We may update these terms from time to time. The current version number and effective date appear at the top of this page.

Material changes that reduce your rights take effect 30 days after we post the revised terms and provide in-app notice. For Builder business users, the additional 15-day notice in §9.3 also applies, with the longer of the two notice periods controlling. Other changes take effect on the revised effective date.

If you do not accept a material change, you may stop using the Service before it takes effect; cancellation rights under the Refund Policy continue to apply.

A summary of material amendments is maintained in §21 below.

19. Severability

If any provision of these terms is found to be unenforceable, the remaining provisions continue in full force.

19.1 Entire Agreement

These terms, together with the Refund Policy, the User-Generated Content Policy, and the Privacy Policy, are the entire agreement between you and us about the Service and supersede any prior understanding. Nothing in this clause excludes liability for fraudulent misrepresentation, for any consumer guarantee that cannot lawfully be excluded, or for any statutory right preserved under §13.6.

19.2 No Waiver

Failure or delay by either party to exercise a right under these terms is not a waiver of that right or of any other right. A waiver of any right is effective only if it is in writing and signed by the party waiving the right.

20. Customer Service and Contact

For all inquiries — including billing, refunds, entitlement issues, abuse reports, and general questions:

Email: support@qub.social

Use the following subject prefixes to help us route your request:

We aim to respond within 2 business days.

20.1 Notices

We will give you formal notice (a) by email to any address you have given us (sign-in, attestation, purchase, notify-me); (b) by in-app banner shown on the next session that authenticates your device identifier or signed identity; or (c) by posting to the relevant page on qub.social. Notice given by any of these channels is effective when sent or posted, as the case may be.

You may give us notice by emailing support@qub.social with the relevant subject prefix above. Notice is effective when received.

21. Change Log

Subsections inserted into a stable section retain a letter suffix (for example §10.2a) so that cross-references to surrounding sections remain valid across revisions.

Version Effective date Summary
1.0 1 May 2026 Initial publication.