Oct 1, 2025

Oct 1, 2025

Disclaimer

Disclaimer

This document is a non-binding reference describing BridgTime/BRTM design intent and examples. It is not a public sale, solicitation, subscription, advertisement, or advice, and it does not guarantee listing, trading, liquidity, price, or returns. Features, timelines, partnerships, and token plans may change, be deferred, or not be executed without prior notice. BRTM is utility-only (feature access, operational bonding, governance input) and does not yield monetary benefits by mere holding. Even for private/pilot distributions, KYC/sanctions screening, contracts, transfer restrictions, and use limitations apply. Geofencing/access limits may be enforced per jurisdictional requirements. An RVA is verification metadata only and does not create rights/claims/collateral/income interests. Pre-payment/settlement and other financial transactions occur solely under off-chain agreements between licensed finance partners (LFPs) and their customers; BridgTime does not solicit, broker, arrange, advise, or custody. Nothing here is investment/legal/tax/accounting advice. To the maximum extent permitted by law, warranties are disclaimed and indirect/consequential damages are excluded.

Nature of this Document & Non-binding Status

This document compiles background, design intent, research directions, and illustrative scenarios regarding BridgTime and BRTM. It is not a contract, proposal, offer, guarantee, commitment, terms of service, privacy policy, or technical specification. Any functions, timelines, partnerships, figures, metrics, screens, code, and diagrams are plans/intent/examples only and are not guaranteed to be delivered. Nothing herein creates legal obligations or confers rights.

  1. No Public Offering or Solicitation; No Mass Marketing

    This is not an issuance, sale, subscription, solicitation, or advertisement of securities or financial products in any jurisdiction. It is not a public sale or mass distribution/marketing. If provision is necessary, materials may be shared only with eligible counterparties subject to KYC/sanctions screening and contractual restrictions.


  2. Laws, Regulations, and Jurisdiction

    Availability, scope, features, fees, and access to BridgTime/BRTM may vary or be restricted under applicable laws (financial/e-money/data protection/sanctions/export-control). In certain jurisdictions, token/activities may be regulated (e.g., Howey/MiCA/MAS/SFC/Thai SEC/FSC/VASP). In such cases, BridgTime may apply geofencing, access limits, or functional reductions.


  3. Sale Restrictions, Geofencing, and Eligibility

    BridgTime may implement geoblocking, feature restrictions, and allow/deny lists as permitted by law. Minors, sanctioned persons, and residents of prohibited jurisdictions cannot use the services. Access can be restricted if eligibility is not met; violations may result in denial/suspension of service.


  4. Not Investment, Securities, or Financial Advice

    Nothing herein is investment advice or a guarantee of returns, principal, dividends, interest, redemption, listing, distribution, liquidity, price stability, or trading opportunities. BridgTime does not provide financial/tax/accounting/legal/investment advice. Decisions must be made by readers in consultation with their own professionals.


  5. No Assurance of Listing, Liquidity, or Trading

    No exchange listing, maintenance, trading pairs, liquidity, price, volume, or spread is assured. Market-making or price stabilization is not promised. Any related plans may change or cease without notice.


  6. Caution on Forward-Looking Statements

    Words such as “aim/plan/seek/expect/may” indicate forward-looking statements that can differ materially. Items may change, be delayed, or withdrawn without notice due to market, technical, regulatory, partner, resource, security, or operational factors.


  7. Product/Technology Status

    Systems, APIs, oracles, smart contracts, risk engine, dashboard, subgraphs, SDKs, and security/ops may be in planning, design, research, alpha/beta, or testnet. Performance targets, SLA/SLO, throughput, latency, availability, and quality metrics are internal goals only. Screens, diagrams, code, interfaces, fields, and message formats are examples and may differ in reality.


  8. Data, Security, and Privacy

    Only minimal metadata (e.g., hash/grade/status/signature/timestamp) is intended for on-chain. Encryption, access controls, logging, audits, key management, pseudonymization, and cross-border controls do not guarantee error-free or incident-free operation. BridgTime is not liable for third-party cloud/KMS/HSM/storage/network/indexer/RPC/CDN/WAF outages or policy changes. Users must secure the legal basis, consent, and authority for data provision/processing.


  9. Third-Party Mentions and Dependencies

    Names of PGs, banks, ERP/POS vendors, indexers, chains, libraries, tools, standards, marketplaces, partners, or regulators are for illustration and do not imply affiliation, endorsement, approval, warranty, or sponsorship. Third-party terms, policies, pricing, availability, and security are owned and controlled by their respective parties.


  10. Smart-Contract & Network Risks

    Smart contracts may contain vulnerabilities, implementation defects, upgrade risks, misuse of privileges, or event delays/omissions. Risks exist across on/off-chain layers (e.g., L1/L2 congestion, gas volatility, reorgs, forks, censorship, consensus issues, bridge/sequencer/RPC incidents, MEV/front-running, subgraph delays). On-chain records are hard to amend; erroneous inputs/signatures/commits may be irreversible.


  11. Limited Effect of RVA (Non-Right-Creating)

    An RVA is only metadata about a verification fact. It does not constitute, transfer, or guarantee ownership, income, participation, collateral, or assignment rights in any underlying receivable, nor does it create legal rights or titles.


  12. BRTM: No Rights/Income; Utility-Only

    BRTM is designed solely for network feature access, operational bonding, and governance input. It grants no equity/debt/dividend/interest/revenue-share/redemption/priority/claim. Mere holding yields no income, dividends, interest, rebates, or rewards. Any amounts payable to operators are service fees for contractual/SLA performance, not consideration for token holding. Policies on price/liquidity/listing/demand/supply/rewards/discounts/credits/priority/distribution/vesting/lockups/mint/burn may change, be deferred, or halted without notice.


  13. Not a Financial Institution; No Custody/Brokerage

    BridgTime does not provide payment, custody, safekeeping, brokerage, lending, factoring, collective investment, advisory, trust, clearing, or settlement services. It does not solicit, broker, arrange, or advise on any financial product and does not custody funds or digital assets. Pre-funding/collections occur solely under off-chain contracts between LFPs and clients.


  14. Limits of Oracles/Verification/Grades/RVA Signals

    Oracle signatures, m-of-n consensus, risk scores/grades, and RVA issuance/updates/status are reference signals only and do not guarantee authenticity, recoverability, absence of fraud, legal effect, or financial outcomes of any transaction. Approvals/denials/limits/accounting/tax/regulatory reporting remain subject to each institution’s policies and judgments, and may vary with data/policy/model versions and timing.


  15. No Warranty of Outcomes or Benefits

    Any examples of lead-time reduction, higher automation, lower delinquency/fraud, improved forecast accuracy, cost savings, revenue/profit improvement, funding success, ROI, or productivity gains are illustrative only and not guaranteed. Adverse results may occur.


  16. User Responsibilities (Eligibility & Security)

    Access/integration/testing/deployment must be performed by duly authorized entities/professionals. Users are responsible for the security of their systems, data, keys, wallets, credentials, and access rights; losses due to compromise/misuse remain the user’s responsibility.


  17. Right to Change, Suspend, or Withdraw

    BridgTime may change, suspend, or withdraw products, policies, schedules, graphics, APIs, endpoints, fees, token plans, subgraphs, indexing, dashboards, sandboxes, and beta features without prior notice. Changes apply from the time of announcement.


  18. Warranty Disclaimer & Limitation of Liability

    This document and related materials are provided “AS IS” without express or implied warranties (including merchantability, fitness for a particular purpose, non-infringement). To the fullest extent permitted by law, BridgTime and its personnel/agents/partners are not liable for indirect, incidental, punitive, special, or consequential damages; lost profits/data/goodwill; replacement service costs; or opportunity costs. Liability for gross negligence or willful misconduct applies only as required by applicable law.


  19. Priority of Governing Documents & Interpretation

    If this disclaimer conflicts with terms, privacy policy, specific agreements, rules, notices, or product docs, those documents prevail. In case of translation discrepancies, BridgTime’s designated base-language document governs. Ambiguities are not construed against the drafter.


  20. Governing Law & Dispute Resolution

    (To be finalized.) Governing law and venue or arbitration clauses will be defined in separate terms or contracts. Except where mandatory consumer-protection laws apply, such provisions may be waived or excluded as permitted.


  21. No Duty to Update

    Except as required by law, BridgTime has no obligation to update this document regularly or to disclose non-public information.


  22. Official Contact Channels

    Legal notices, terms, privacy, security reports, rights claims, and regulatory/audit requests must be submitted via BridgTime’s designated official channels. General marketing/community posts, unofficial media, or third-party distributions are not legal notices.


  23. Non-Assurance on Development/Roadmap Execution

    BridgTime does not guarantee delivery, schedule, or performance of any development item (features, timelines, partnerships, token plans, APIs, SDKs, subgraphs, dashboards, gateways). Non-execution, change, or discontinuation does not constitute a claim for damages.


  24. Scope Limits of Governance

    Governance processes are limited to operational parameters and are unrelated to finance/revenue/dividends/price/listing/liquidity/market-making, and do not confer membership/equity/partnership status. Governance functions may be restricted or disabled if required by regulation.


  25. Marketing & Communications Notice

    Whitepapers, websites, social media, community posts, demos, and hackathons are not advertisements, solicitations, or offers. Past/example/simulated numbers or language do not imply or guarantee future performance. Terms like “partner,” “integration,” or “support” are for convenience and do not imply formal affiliation or approval.


  26. Tax, Accounting, and Disclosure Responsibilities

    Users are solely responsible for tax, accounting, and disclosure obligations arising from tokens or services. BridgTime does not provide tax/accounting advice; users must consult their own professionals.


Final Notice
All descriptions herein are general information about plans, intent, and examples. Nothing in this document guarantees delivery, success, timing, performance, or benefits. No legal liability or damages arise if items are not realized, are delayed, changed, or discontinued. Readers should reference this document only on the understanding that they have read and agreed to the entirety of this disclaimer.

Key questions under review

The items below are user questions that are being continuously refined during planning and testing.

My channels, PG, and ERP all differ. Will one upload automatically standardize into a single RVA? Which formats are supported?

What minimum materials qualify for partner review? How are exceptions or missing items handled?

Where and how is the blockchain record stored, and what about privacy and cost?

Which metrics inform a partner’s policy score, and what can I improve in advance?

Does global collaboration and multilingual support work well?

Key questions under review

The items below are user questions that are being continuously refined during planning and testing.

My channels, PG, and ERP all differ. Will one upload automatically standardize into a single RVA? Which formats are supported?

What minimum materials qualify for partner review? How are exceptions or missing items handled?

Where and how is the blockchain record stored, and what about privacy and cost?

Which metrics inform a partner’s policy score, and what can I improve in advance?

Does global collaboration and multilingual support work well?

Planning and research stage

BridgTime has not confirmed development or launch yet, and all content on this site is under planning. Scope and timeline may change or stop without notice. This site is for information only and is not investment advice. Approvals and payouts follow each partner’s policies and procedures.

Planning and research stage

BridgTime has not confirmed development or launch yet, and all content on this site is under planning. Scope and timeline may change or stop without notice. This site is for information only and is not investment advice. Approvals and payouts follow each partner’s policies and procedures.