0x0BB570E30f0b3C5D909C08e3316Dade9C1Dc7fE0 no Workflow action — test tiny rail only
Explorer ↗Draft v0 — pending securities-counsel confirmation. Defaults are best-effort, not legal advice.
Effective 2026-04-29 · last copy review 2026-06-10 · still Draft v0 — a real legal pass is pending and this page says so honestly.
Workflow is open-source software under MIT. Public goal content is CC0-1.0. Current Workflow settlement testing uses test tiny on Base Sepolia. The real currency reference is Destiny (tiny), and real-token integration is deferred.
Concept-layer public; instance-layer private; never training data. The shape of your workflow (which nodes, what edges, what state schema) is public — that's the commons. The contents you process (your documents, your prompts, your fills) stay on your machine or in owner-only storage. We do not train models on your data and never will.
Per-piece visibility is judged by your chatbot per request, not by us. The chatbot proposes; you confirm. No cached consent.
You may export or delete your data at any time. The /account page (Phase 2) provides a 30-day grace-window deletion flow per CCPA / GDPR Article 17.
Cookies / analytics: we plan to use Plausible (privacy-friendly, no PII, no third-party trackers). No advertising cookies, no cross-site tracking pixels.
Minimum age. Workflow is not directed at children. You must be at least 18 years old to use the service or hold a wallet connection. Wallet features are not live today; the age self-declaration described here pre-positions the obligation for if and when wallet-connect opens. You self-declare your age at wallet-connect; misrepresentation is grounds for termination. We do not knowingly collect data from minors; if you believe we have, contact [email protected].
By using Workflow (the website, the MCP gateway at tinyassets.io/mcp, or the daemon tray), you agree to these terms. If you do not agree, do not use the service.
The service is not available in jurisdictions comprehensively sanctioned by OFAC (currently: Cuba, Iran, North Korea, Russia/Crimea, Syria) or where local law prohibits transacting in utility tokens (currently: People's Republic of China). Wallet features are not live today; the screening described here pre-positions the obligation for if and when wallet-connect opens. We screen wallet connections via Wallet-connect screening (Chainalysis or TRM at MCP gateway). Self-declared geo-attestation at first paid-market action.. By using the service you represent that you are not a resident of, or accessing from, a blocked jurisdiction.
You retain all rights to data you process through Workflow. By publishing a node, branch, or goal to the public goal set, you license that artifact under CC0-1.0, irrevocably. Private workflows stay private — see Privacy above.
We provide the platform "as is". We do not guarantee uptime, output quality, or specific economic outcomes. Where the platform routes your work to a daemon-host, the host runs your work according to the protocol; we are not the host.
We may suspend or terminate accounts that violate these terms. You may stop using the service at any time and delete your account.
This section separates token identity from current Workflow integration. The real currency reference is Destiny (tiny); the current Workflow rail is test tiny on Base Sepolia.
Under the SEC's April 2026 interpretive release on crypto-asset categorization (the "Project Crypto" framework), digital assets are classified into five categories: digital commodities, digital collectibles, digital tools, payment stablecoins, and digital securities. If real Workflow settlement opens, Destiny (tiny) is intended to function as a digital tool and/or digital commodity for paid-market participation, deriving value from the programmatic operation of the protocol.
tiny is also intended to qualify under the "mature blockchain system" carve-out contemplated by the Digital Asset Market Clarity Act (H.R. 3633) once the Workflow protocol meets the decentralization and functional-use criteria established by the Act in its final form.
test tiny rail until real integration opens.test tiny on Base Sepolia for roadmap testing and settlement simulation.tiny payouts, staking, DAO votes, or treasury flows in current Workflow surfaces.The real Destiny (tiny) token exists on the chains below. They are shown reference-only: Workflow takes no action on them today and settles solely on the Base Sepolia test tiny rail. Verify any address yourself on its block explorer before trusting a copy of it.
0x0BB570E30f0b3C5D909C08e3316Dade9C1Dc7fE0 no Workflow action — test tiny rail only
Explorer ↗0x92a242f94db176082Df4D386B366f4217ab7fAFd no Workflow action — test tiny rail only
Explorer ↗0x839108AaecB749e8F33cc68bb6D6323F61206322 legacy address; no Workflow action
Explorer ↗Canonical surfaces only: the site is tinyassets.io, the MCP URL is tinyassets.io/mcp, the repo is github.com/Jonnyton/Workflow. Anything else is not us.
This site does not constitute an offer or solicitation to sell securities. Existing tiny contracts are reference-only for Workflow today; no new offering is being made through this site. Any future real-token settlement must open as an explicit roadmap phase.
Tier-1 chatbot users (browse, run free-tier daemons) do not require KYC. Tier-2 daemon hosts are subject to identity verification at a cumulative lifetime paid-market threshold of USD 1,000 via a third-party KYC provider (Sumsub, Persona, or Onfido). Treasury operations involve full KYC. Wallet features are not live today; the screening described here pre-positions the obligation for if and when wallet-connect opens. Wallet connections are screened against the OFAC sanctions list in real time.
Real-token payouts are disabled at v0. If real Destiny (tiny) payouts later open, you are responsible for the tax treatment of any token received, spent, or disposed of in your jurisdiction. We are not a tax advisor. Consult a qualified tax professional.
Use of Destiny (tiny), test tiny, and the Workflow platform involves risks. Read these carefully.
tiny holdings once real integration exists.tiny, require KYC, or prohibit certain uses in certain jurisdictions.tiny. Trading volume on any specific venue may be thin or zero.tinyassets.io, the canonical MCP URL is tinyassets.io/mcp, the canonical repo is github.com/Jonnyton/Workflow. Anything else is not us.If you believe content on the public goals surface or wiki infringes your copyright, send a DMCA takedown notice to [email protected] including: identification of the work, identification of the infringing material with URL, your contact info, statement of good-faith belief, statement under penalty of perjury, and your physical or electronic signature.
Counter-notices follow standard 17 U.S.C. § 512 procedure. Designated DMCA agent registration with the U.S. Copyright Office is in progress.
Governing law. These terms are governed by State of Delaware, USA (without regard to conflict-of-laws).
Dispute resolution. JAMS binding arbitration in Delaware, individual claims only (class-action waiver), small-claims-court carve-out preserved. By using the service you waive your right to participate in a class action; mass-arbitration coordination is also prohibited. You retain the right to bring an individual claim in small-claims court.
Injunctive relief. Either party may seek injunctive relief in State and federal courts located in Delaware for IP infringement, breach of confidentiality, or platform-abuse claims that arbitration cannot timely address.
Liability cap. Lesser of (a) fees paid to us in the 12 months preceding the claim, or (b) USD 100. We disclaim consequential, indirect, special, and punitive damages. We do not exclude liability that cannot be excluded by law (e.g. willful misconduct, gross negligence in some jurisdictions; consumer-protection statutes in some US states and EU member states).
Indemnification. You will indemnify us for misuse of the service, IP infringement in your content, sanctions-law violations, and false geo-attestations. We will indemnify you for IP infringement of the platform code within the scope of the MIT license, capped at the liability limit above.
Force majeure. Neither party is liable for delay or failure caused by events beyond reasonable control: Blockchain-network events (chain reorgs, RPC outages, gas spikes >5x baseline, hard forks); Cyberattacks affecting the gateway, MCP, or daemon hosts; Regulatory action that prohibits continued operation; Infrastructure-provider outages (Cloudflare, Supabase, Fly.io, GitHub); Acts of God, war, civil unrest, pandemics. We may suspend performance for up to 30 days; longer suspensions trigger pro-rated refund of any prepaid fees.
Severability + entire agreement. If any provision is unenforceable, the rest survives. These terms are the entire agreement between you and us regarding the service.
General: [email protected]
Security: [email protected]
Legal: [email protected]
DMCA agent: [email protected]
Response SLA per CONTRIBUTING.md — 48h first response, 5 calendar days for full review.