TreaxuresPilot contact
Legal

Terms of Service

Draft — pending legal review. This document has not yet been reviewed by Indian-jurisdiction counsel and is not in effect. Content is subject to change before publication.

Terms of Service

Status: Draft — not effective

Last reviewed for product accuracy: 2026-07-19 Operator: Treaxures, operated by ESPR Creative Lab Private Limited, Aizawl, Mizoram, India

These draft terms describe the intended Aizawl field-guide product. They are not ready for user acceptance and do not replace a creator, organisation, partner, seller, provider, payout, or pilot agreement.

1. Access and eligibility

Public Aizawl catalogue pages may be browsed without an account. An account is required for features that need saved state, private content, completion, reviews, Passport records, creator/partner authority, or transactions.

The minimum age, guardian-consent flow, paid-feature eligibility, and organisation/partner authority requirements are a release gate pending counsel and store review. Do not enable production acceptance with placeholder ages.

Users must protect their credentials, provide accurate account information, and notify support@treaxures.com of suspected unauthorised access. Accounts may not be used to evade enforcement, fabricate activity, manipulate reviews, impersonate a contributor or partner, or interfere with the service.

2. Field-guide scope and safety

Treaxures provides contextual field-guide information. Route, access, weather, transport, cultural, and safety details can change. Review dates, sources, limitations, and current bulletins should be checked before and during a journey.

Treaxures is not an emergency service and does not guarantee that a route is safe or accessible for every person or condition. Users remain responsible for following current law, local instructions, closures, property boundaries, sacred-space guidance, traffic rules, and advice from appropriate emergency or medical services.

The final terms must contain counsel-approved warranties, disclaimers, liability limits, insurance position, force-majeure treatment, and dispute terms. The placeholder liability language from earlier drafts has been removed.

3. Content, sources, media, and reviews

A user or workspace submitting text, routes, sources, media, translations, reports, reviews, or other content must have authority to do so and must not:

  • infringe another person's intellectual-property, privacy, publicity, cultural, confidentiality, or data-protection rights;
  • invent or materially misrepresent a person, quotation, source, place, community, partner, price, review, route, safety condition, or right;
  • expose sensitive locations or personal data without an approved basis;
  • submit unlawful, abusive, deceptive, malicious, or unsafe material;
  • manipulate completed-experience eligibility, sentiment, moderation, or commercial disclosure.

Publishing requires the applicable source, local-context, rights, route/field, safety/access, commercial, and copy review. Review applies to an exact revision and scope; it is not a blanket endorsement of its author.

A public review may be submitted only after the corresponding eligible completed journey or booking. Treaxures may moderate, withhold, correct, or remove content and may offer an appeal or correction workflow.

The content licence, contributor-credit obligations, moral-rights treatment, media uses, AI-assistance rules, takedown process, and survival after account deletion must be set out in the counsel-approved creator/organisation agreement and final terms. No broad placeholder licence should be relied on.

4. Creator, organisation, and partner workspaces

Creator Studio is invitation-only and role-scoped. A creator may propose a partner and editorial relationship but cannot claim partner authority, accept terms, set payout details, or activate commerce for that partner.

Contributors keep scoped credit independent of account ownership. Organisations, partners, sellers, providers, reviewers, and staff must act within their granted authority. Material changes can invalidate review or require a new immutable revision.

Compensation, expenses, commission, ownership, licence, disclosure, correction, cancellation, tax, payout, and takedown terms are contract-specific. Treaxures does not promise a universal creator tier, fixed revenue percentage, fixed fund allocation, default price, or payout schedule in these terms.

5. Commercial features

A paid guide, real-world service, offer, booking, product handoff, or other commercial capability may be used only when it is operationally enabled and its required legal/payment review is complete.

Before confirmation, the experience must identify the seller or provider, fulfilment owner, price, taxes and fees, any contractually applicable allocation, commercial relationship, current availability, cancellation/refund terms, and support or grievance contact.

An outbound affiliate handoff must offer the reviewed disclosure and a clean seller link. Enabling attribution does not prove a sale or contribution. Commission is recognised only from reconciled provider evidence.

Orders, bookings, redemptions, refunds, disputes, settlements, and payouts are server-authoritative and auditable. The exact receipt and accepted terms govern the transaction. Refund timelines, statutory rights, taxes, KYC, invoices, payout eligibility, and seller obligations must be approved for each operating model; the old generic refund and fixed-price promises have been removed.

Digital collectibles, public rewards, flight/hotel booking, generic marketplace checkout, and carbon-offset commerce are not part of the Aizawl public launch.

6. Impact Passport and public sharing

The Impact Passport is private by default. Records identify whether their source is a completion, transaction, confirmation, observation, or estimate. They do not create public authority or an entitlement to preferential treatment.

Users may share only the fields offered in the visibility controls. Treaxures may update or reverse a record when its source transaction, confirmation, or release changes while preserving the audit history required by the approved retention policy.

7. Enforcement, suspension, and service changes

Treaxures may restrict a capability, pause a release or transaction, remove content, or suspend an account when needed for safety, rights, fraud, abuse, legal process, partner offboarding, or policy enforcement. A reason, appeal route, and notice should be provided where appropriate and lawful.

Private preview access is revocable and does not authorise public sharing. Features compiled into an app are not promised to be operational.

8. Privacy, deletion, and support

The draft Privacy Policy and Data Deletion page describe the intended product workflows. They are not effective until approved alongside these terms.

Support: support@treaxures.com

Legal notices: legal@treaxures.com Creator and organisation pilots: creators@treaxures.com

9. Required legal completion

Before these terms become effective, counsel must approve at least: entity and address disclosures; acceptance and versioning; age/guardian controls; consumer and e-commerce obligations; seller/provider responsibilities; IP and cultural rights; moderation and appeals; payment/refund/payout language; tax and KYC; warranties and liability; governing law and disputes; notices and response periods; termination; survival; and change notification.

The production release must bind acceptance to the exact immutable approved version.