Terms of Service
Clear terms.Clear boundaries.
This page sets out Quantaible's current pre-release terms framework. Preview access, product commitments, and unfinished legal details stay distinct. Paid acceptance remains closed until the final agreement and service match.
Pre-release legal framework
Updated 17 August 2026. This page is not yet the final binding paid-service agreement. Final operator, acceptance, billing, liability, provider, and jurisdiction-specific details remain release gates.
Document status
What this page does—and does not—do.
A terms page must not create false certainty. Product and commercial commitments can be locked now while unresolved legal details remain visibly incomplete. A paid relationship does not open until professional review, final publication, affirmative acceptance, and runtime verification are complete.
Current public framework
Public terms framework
This page records the public pre-release contract framework before broad paid release. Locked product and commercial rules are release conditions; unresolved legal details remain visibly gated rather than being implied as complete.
Locked product rule
Product rules
Original preservation, Q proposal status, one QHub shell, Persistent Investigations on every plan, the public Q actions, Same Q across plans, explicit Retain, no silent provider switching, and separate retrieval permission are product release conditions rather than optional wording.
Required before paid release
Binding operator details
The contracting legal entity, service address, formal legal contact, effective date, acceptance record, and jurisdiction-specific notices must be complete, published, and verified before binding paid acceptance.
Required before paid release
Billing and liability review
Final refund mechanics, tax treatment, plan transition rules, fair liability limits, insurance alignment, and business contracting provisions remain paid-release gates and require professional legal review before checkout opens.
Agreement boundaries
Three boundaries remain distinct.
The service can help examine material without taking ownership of it or replacing the person responsible for the final decision. A capability does not release if ownership, Q proposal, and user-authority boundaries can collapse.
You retain your rights in your material
You retain the rights you hold in questions, files, claims, notes, decisions, retained outcomes, and other material you provide or create. Quantaible receives only the limited permission needed to provide actions you request.
Q proposes
Answers, source assessments, explicit inferences, routes, and proposed retained outcomes remain proposals until you explicitly review and decide. No model, provider, workflow, or plan can promote Q output into evidence or user authority.
You remain responsible for use
You decide what to accept, reject, share, rely on, or act upon. High-impact use requires appropriate human judgment, verification, and professional advice where relevant.
Terms at a glance
The essential agreement in plain language.
The detailed sections below qualify this summary. Where a paid legal term is not yet settled, the release gate stays visible rather than being replaced by a one-sided placeholder. Where a product or commercial commitment is locked, implementation must satisfy it before paid release.
Clear service status
Preview, operational, and planned capabilities must remain distinguishable. A planned feature is not promised as currently available, while a locked capability contract remains a release condition before that feature opens.
Account responsibility
Use accurate information, keep credentials secure, and act only for organisations you are authorised to represent.
Permissioned processing
Processing mode and source scope remain separate permissions. Provider choice must be disclosed and scoped, web retrieval stays off by default, and one permission never silently authorises another.
Transparent billing
Prices, renewal periods, taxes, plan entitlements, managed-resource allowances, payment recovery, and cancellation effects must be visible and enforceable before a paid commitment is made.
Fair acceptable use
Do not use Q unlawfully, interfere with security, evade limits, upload material without authority, or use proposals as hidden automated authority over other people.
Statutory rights preserved
Nothing in these terms removes rights or remedies that cannot lawfully be excluded, including applicable New Zealand consumer protections.
Using the service
Access, accounts, and service scope.
Service status
Use only the capabilities currently presented as available.
Quantaible may provide public pages, controlled previews, founding pilot features, Q tools, account functions, storage, exports, Receipts, and related services. The interface and relevant disclosure determine whether a capability is operational, preview, restricted, or planned.
Preview and planned descriptions do not guarantee a release date, permanent availability, or compatibility with every device, provider, file type, jurisdiction, or use case. A planned capability also does not inherit permission, billing authority, or user authority merely because it appears on a roadmap.
Eligibility
You must have legal capacity and authority to accept.
You may use an account only if you can lawfully agree to the applicable terms. Quantaible is not currently presented as a service designed for children. If you act for an organisation, you confirm that you are authorised to bind or administer that organisation's use.
Account security
Keep access accurate, personal, and appropriately controlled.
Provide accurate registration and billing information, protect authentication methods, and promptly report suspected compromise. Do not share access in a way that defeats plan, security, authority, or audit boundaries. Team and organisation administrators are responsible for assigning access appropriately.
Your material and generated output
Possession is not ownership.
Quantaible needs limited technical permission to provide the service. That permission does not silently become a transfer of ownership, training permission, advertising permission, publication permission, or an unrestricted right to reuse private work.
You retain your material
You retain the rights you hold in submissions, files, claims, notes, decisions, feedback, branches, retained outcomes, and other material you provide or create. You confirm that you have the rights, permission, or lawful basis needed to provide it.
Limited service permission
You grant Quantaible a limited, non-exclusive permission to host, copy, transmit, process, preserve, display, export, and delete your material only as reasonably needed to provide, secure, support, and comply with the service actions and legal obligations that apply to your use.
Output may not be unique
Subject to applicable law and disclosed provider terms, you may use output made available to you. Similar output may be generated for others, and Quantaible does not promise that output is unique, protectable, accurate, complete, or free of third-party rights.
Quantaible retains platform rights
Quantaible and its licensors retain rights in the software, system mark, public Q visual language, interfaces, documentation, interpreter contracts, platform architecture, trademarks, and service improvements. These terms do not transfer those rights.
Voluntary product feedback is different from private work.
Feedback and suggestions you intentionally submit for product improvement may be used to evaluate and improve Quantaible. That permission does not extend to private conversations, investigations, files, notes, retained work, Receipts, or other customer material for model training, advertising, or unrelated product development unless a separate, explicit permission applies.
Acceptable use
Capability does not remove responsibility.
Use Q lawfully and in a way that preserves the rights, safety, and authority of other people. Attempts to bypass safeguards or convert proposals into hidden authority are outside the service agreement.
Do not use Q for unlawful or rights-infringing activity.
Do not provide material without authority, violate privacy or intellectual-property rights, facilitate fraud, impersonation, abuse, exploitation, or other unlawful conduct.
Do not interfere with security or service integrity.
Do not introduce malware, extract credentials, probe without permission, evade technical limits, overload the service, access another person's workspace, or circumvent paid or preview access.
Do not use Q as undisclosed automated authority over another person.
Q output must not be the undisclosed sole basis for consequential decisions about employment, housing, credit, healthcare, education, eligibility, legal status, safety, or similar interests where human review, explanation, consent, or due process is required.
Respect safety and disclosure boundaries.
Follow warnings, permission prompts, provider limits, export restrictions, and applicable professional or regulatory duties. Do not misrepresent generated material as verified fact or human authorship where disclosure is required.
Founding pilot
Early participation stays separate from pricing.
Founding access is a controlled early-participation relationship. Participants may receive selected previews and provide structured feedback while Quantaible validates product behaviour, managed capacity, retrieval, persistence, controls, and cost assumptions. Founding status does not create a separate paid plan or discounted subscription rate.
Controlled early access
Founding pilot participants may receive selected tools, workflows, and material product changes before wider release. Preview access can be limited, changed, paused, or withdrawn where safety, reliability, privacy, or feasibility requires it.
Structured pilot feedback
Participants may be asked what worked, what did not, where capacity or controls became limiting, and what should change. Participation helps validate the product and its operating assumptions.
Founding status is not a price tier
Founding access describes participation in the early pilot. It does not create a permanent discount or separate paid plan. Paid access uses the published pricing ladder in force when billing opens.
Feedback remains advisory
Pilot feedback can inform product sequencing and priorities, but it does not create shares, ownership, fiduciary rights, binding roadmap control, or authority to override safety, privacy, accessibility, legal, or architectural requirements.
Founding describes the relationship. Pricing describes the plan.
Pilot participation may affect access to selected preview rounds or feedback opportunities. It does not create a permanent discount, ownership interest, or binding product-control right.
Compute and retrieval boundaries
Choose how Q is powered without expanding what Q may access.
How Q is powered and what Q may retrieve are separate controls. Provider identity, model selection, usage mode, source scope, costs, limits, and proposed fallbacks remain visible where relevant. A provider path does not open if Q can silently switch providers, expand retrieval scope, conceal cost, or turn provider output into evidence or user authority.
Release-gated managed mode
Quantaible Managed
When released, Quantaible Managed is the default processing mode and does not require the user to select or connect a provider. It operates an approved provider path within the plan's managed usage allowance and disclosed cost controls. The managed path does not create a different commercial version of Q and does not open until provider, model, cost, permission, and execution-record boundaries pass release verification.
- Works without a separate provider account.
- Provider and model details remain attributable in the execution record.
- Managed compute and online capacity may vary by plan without changing Q's identity or the core Persistent Investigation model.
- A material provider or model boundary cannot be switched silently.
Release-gated connected mode
Your provider
A supported mode may allow a user or organisation to connect separately issued provider or API credentials. It remains closed until credential storage, removal, disclosure, provider billing, routing, fallback, and failure boundaries are verified. Consumer ChatGPT or Claude account credentials are not provider connections and must never be requested.
- Provider usage is billed by that provider where applicable.
- Credentials stay server-side, encrypted, redacted, revocable, and excluded from browser code, logs, Receipts, and exports.
- Execution records identify the provider, model, usage mode, important limits, retries, and any proposed fallback.
- Choosing a provider does not authorise web retrieval or change which version of Q the user receives.
Supported where available
Local / self-hosted
Supported local or self-hosted models may power the same Q without sending that model-processing action to an external provider path. Local execution is not represented as identical to external providers in latency, context, raw output, capability, availability, or model behaviour.
- The Q and user-authority boundary remain the same.
- Local capability depends on supported models, hardware, runtime, and security requirements.
- Local processing does not imply that every account, storage, synchronisation, or ancillary service is local unless expressly stated.
- Local compute does not silently authorise Local + web retrieval.
- A local model's output remains a Q proposal rather than evidence, Retain authority, or a user decision.
This selects how Q is powered for an action. Provider and model behaviour can differ without creating a different commercial version of Q. Same Q does not mean identical provider output. Changing processing mode does not by itself change source permissions, provenance requirements, or retained state.
This selects what Q may retrieve. Web retrieval is off by default and must be explicitly enabled. Processing choice never silently expands the permitted source scope.
Third-party provider services are also governed by their own terms, billing, availability, and data practices. Quantaible remains responsible for the boundaries it controls and must not use a provider clause to conceal its own processing responsibilities. Provider data handling remains subject to the Privacy & data disclosures for the boundaries Quantaible controls. Provider choice is not a premium-intelligence feature: capacity and administration may vary by plan, but the current Q system version does not.
Plans, billing, and cancellation
The commitment must be visible before payment.
Paid checkout remains closed. Before it opens, the relevant plan, checkout flow, entitlement system, and billing runtime must agree on price, currency, billing period, taxes, plan entitlements, managed resource allowances, seat minimums, renewal, payment recovery, cancellation effect, and any provider charges that sit outside Quantaible. Persistent Investigations remain part of the core plan architecture, and plan differences must not be implemented as access to a smarter Q.
Recurring plans
Monthly and annual subscriptions renew for the disclosed period until cancelled. The final checkout flow must record affirmative acceptance and make renewal timing clear.
Failed payments
The final paid-service terms must disclose any payment-recovery period, retry behaviour, service limitation, and effect on the subscription before those rules are enforced.
Cancellation and plan changes
The effective cancellation date, access period, export opportunity, renewal effect, and plan-change treatment must be shown before confirmation. A later subscription uses the pricing and terms presented and accepted at that time.
Refunds and remedies
Final refund mechanics will be shown at checkout. Change-of-mind refunds are not implied unless offered, but statutory remedies for services that fail applicable legal guarantees remain intact.
Preview tools and service changes
Experimentation needs a visible boundary.
Early tools can change more quickly than stable paid features. That flexibility cannot become a general right to remove already-earned access, rewrite earlier agreements, or make undisclosed detrimental changes without notice.
Preview features
Preview tools may be incomplete, rate-limited, unavailable, changed, or withdrawn. Important known limitations must be disclosed before access, and user material must not be silently stranded by a change.
Material service changes
Material changes to a paid core service, pricing, or contractual rights receive reasonable notice and a fair cancellation path. Emergency security, safety, or legal changes may take effect sooner when necessary, with the changed boundary disclosed as soon as reasonably practicable.
Versioned terms
Accepted versions, effective dates, and material changes must be recorded for binding paid acceptance. A new version does not silently rewrite the meaning of actions or rights that occurred under an earlier version.
Suspension, termination, export, and deletion
Ending access does not erase the boundary.
Account or service access may end, but user material, export, deletion, Receipts, payment obligations, and legally required records remain separate questions that must be handled explicitly.
Suspension
Quantaible may limit or suspend access to protect users, investigate misuse, respond to legal requirements, prevent security harm, or address material payment failure. Where appropriate, the reason and available review path are provided.
Termination
Either side may end the relationship under the final accepted terms. Quantaible gives reasonable notice for non-urgent termination and does not use termination to avoid accrued contractual or statutory obligations.
Export opportunity
Where record state is stored by the service, a documented export path is a paid-release condition before ordinary account closure, subject to security, technical, legal, and plan boundaries disclosed at the time.
Deletion and residual records
Removing an item from a workspace and permanently purging recoverable copies are different actions. Minimal payment, fraud-prevention, legal, security, or non-reconstructive integrity records may remain where lawfully required and disclosed.
Reliability and responsibility
A proposal can still be wrong.
Governance improves visibility and control. It does not make model output infallible, remove the need for source verification, or turn a general-purpose system into a licensed professional.
Verify consequential material
Check sources, dates, jurisdiction, assumptions, uncertainty, and important omissions before relying on output. Obtain qualified advice for legal, medical, financial, engineering, safety-critical, or other regulated decisions.
Availability and errors
Services can be interrupted, delayed, changed, or affected by third parties. Quantaible does not promise uninterrupted operation or error- free output, but remains responsible for guarantees and obligations that cannot lawfully be excluded.
Fair legal limits
Nothing excludes fraud, deliberate wrongdoing, or liability that cannot legally be excluded. Any paid-service liability cap or business allocation must be conspicuous, proportionate, and legally reviewed before binding acceptance.
Questions, complaints, and disputes
Start with a clear record and a direct path.
Raise a service, billing, privacy, accessibility, or terms concern through the published contact channel. Before paid release, the complaint process must support acknowledgement, preservation of relevant records, an explained response, and any applicable review or external complaint path.
The intended governing law is New Zealand law. Mandatory consumer, privacy, employment, or other rights that apply in a user's jurisdiction remain unaffected where they cannot lawfully be excluded. The final accepted terms must identify the contracting operator and forum.
Contact QuantaibleTerms questions
Clear answers, including what remains unfinished.
Are these the final binding paid-service terms?
Not yet. This is the public pre-release terms framework. Before paid acceptance, Quantaible must publish the contracting legal entity, effective version, legal contact, billing detail, final liability treatment, and an acceptance record. The accepted version presented at sign-up or checkout will govern that service relationship.
Does Quantaible own what I upload?
No. You retain your rights in your material. You grant Quantaible only the limited permission needed to host, process, preserve, export, or otherwise handle that material for actions you authorise. You must also have the right or permission to provide the material.
Who owns generated output?
You may use output made available to you subject to applicable law, third-party rights, these terms, and any disclosed provider terms. Generated material may not be unique, and Quantaible does not promise that every output is protectable, exclusive, accurate, or free of third-party rights.
Is Q professional advice?
No. Q can help examine material and expose uncertainty, but its proposals can be incomplete or wrong. Legal, medical, financial, safety-critical, employment, eligibility, and other consequential decisions require appropriate verification and qualified human judgment.
Can Quantaible change a paid plan?
Services evolve, but material changes to paid core features, pricing, or contractual rights receive reasonable notice and a fair opportunity to cancel, except where an urgent security, safety, or legal change requires faster action. Preview features can change more quickly because they are explicitly experimental. Changes cannot silently rewrite rights that already accrued under an earlier accepted version.
What happens when I cancel?
The final checkout terms will state the effective cancellation date and any refund treatment. Cancellation generally ends renewal rather than erasing the current paid period. Export and deletion options, statutory remedies, and any legally required residual records remain separately governed.
Does every plan include Persistent Investigations?
Yes. Free, Student, Individual, Student Pro, Pro, Team, and Organisation all use the same Persistent Investigation architecture. A plan does not become more expensive merely because a local investigation accumulates a large body of evidence, subject to practical device and system limits.
Do paid plans get a smarter Q?
No. Quantaible's commercial rule is Same Q. More capacity. Identify, Surround, Test, Connect, Consider, and Care remain the public Q actions across plans, with Retain separate and explicit. Plans may increase managed compute, online acquisition, cloud persistence and sync, collaboration, organisational controls, support, or deployment options, but do not unlock a better Q.
Does founding access include special subscription pricing?
No. Founding access describes participation in the controlled early pilot, not a permanent pricing entitlement. When paid billing opens, customers choose from the published pricing ladder then in force. Pilot participation and paid-plan pricing remain separate.
Does choosing a provider turn on web retrieval?
No. Processing control and source control are separate permissions. Quantaible Managed, Your provider, or supported Local determines how Q is powered; Local or Local + web determines what Q may retrieve. Web retrieval is off by default and requires explicit permission.
What law applies?
The intended governing law is New Zealand law. Mandatory rights in another jurisdiction may still apply where they cannot lawfully be excluded. The final accepted terms must identify the contracting operator and dispute forum clearly.
Paid-release gate
The final contract must be as inspectable as the product.
Before paid checkout or a binding paid account relies on these terms, the complete agreement must be reviewed against the actual service, Privacy & data contract, provider schedule, pricing contract, billing and entitlement flows, cancellation and recovery behaviour, data map, insurance position, and applicable New Zealand legal requirements. A mismatch keeps paid acceptance closed.
- Contracting legal entity, address, and formal contact are published.
- Effective version and affirmative acceptance are recorded.
- Pricing, renewal, taxes, refunds, cancellation, plan entitlements, and managed-capacity rules match checkout.
- Provider disclosures, subprocessors, credentials, compute modes, source scopes, costs, and fallbacks match runtime behaviour.
- Plan entitlements match Same Q · More capacity: Persistent Investigations and the public Q actions remain available across plans, with Retain separate and explicit.
- Export, deletion, suspension, and termination paths are tested end to end.
- New Zealand commercial, consumer, privacy, accessibility, and unfair-terms review is complete.
The rule
No silent transfer.No silent authority.
Your material remains distinguishable. Q's work remains a proposal. Paid commitments, provider access, retrieval permission, contractual changes, and final decisions require visible boundaries. Plans may change managed compute, online acquisition, cloud persistence and sync, collaboration, organisational controls, support, or deployment options around Q — not which Q a user receives or whether the core Persistent Investigation model is available. If the final terms and actual service cannot preserve those boundaries together, paid acceptance remains closed.