The rules the platform actually enforces

TRVUE is a launch platform. Verified companies run campaigns for products, locations and communities; supporters contribute money and receive utility, access and membership benefits, sometimes as a token issued by the company.

TRVUE operates the platform. It does not operate the campaigns. The company running a campaign is responsible for delivering what it promised, and it — not TRVUE — issues any token supporters receive.

TRVUE reviews a campaign before it goes live and records what was checked. Review is an evidence check against stated information, and the record of it is public on the campaign page.

An account needs an email address, a display name, and a password of at least ten characters containing a letter and a digit. You may add an authenticator app or a passkey; both are optional and both can be removed.

You are responsible for what happens under your account. A password reset ends every existing session on it, and sessions expire seven days after they are created.

Everything an account stores is enumerated field by field in the Privacy notice.

A campaign is created by a company that already exists on TRVUE. You submit a title, a tagline, a description, a three-part story, a funding goal, a duration, milestones, support tiers and token details. Everything you submit is your content and your representation — TRVUE publishes it, it does not author it.

The platform enforces these bounds on every campaign:

• $1,000minimum funding goal
• $100,000,000maximum funding goal
• 7–90campaign duration, in days
• $1minimum single contribution
• $1,000,000maximum single contribution
• 180days to claim tokens before the unclaimed balance can be swept

A campaign can only be edited while it is a draft or in review, and any saved edit returns it to review. Once a campaign is live its terms are fixed for the people who already supported it.

Every campaign passes through the same states. A founder can never move a campaign into the live state — only a TRVUE admin approval does that.

Approval requires the company to be verified, and — for a campaign connected to an existing token — a live on-chain check that a contract exists at the stated address. Approval restarts the campaign clock, so time spent in review never eats into the campaign.

Funded and ended are derived from the deadline and the amount raised rather than stored, so a campaign cannot be marked funded by anything other than actually reaching its goal in time.

You can support a campaign only while it is live. The amount must be at least $1 and at most $1,000,000, within any bounds the campaign itself sets. Tiers award a stated number of tokens; a custom amount earns tokens pro rata against the highest tier at or below it, and an amount below the first tier earns none.

When payments are configured, contributing opens a Stripe Checkout session and your contribution is recorded as pending. It becomes paid only when Stripe's signed webhook confirms the payment — nothing you or the company can send will mark a contribution paid. Only paid contributions count toward the goal. What this costs is set out under Fees.

A tier slot is reserved when the contribution is created, before the payment round trip, so a tier cannot be oversold while a payment is in flight.

If a campaign reaches its goal by the deadline it completes as funded. Contributions are kept and the company may publish a token distribution.

If a campaign does not reach its goal by the deadline, no tokens are distributed and every paid contribution is refunded in full through Stripe. Refunds are for the whole payment; no partial amount is ever sent.

If a company cancels a campaign, every paid contribution is refunded before the cancellation takes effect. If any refund fails the cancellation does not complete and the campaign stays cancellable, so a cancellation can never strand a paid contribution.

Settlement is refused outright when payment credentials are missing, rather than silently marking a campaign settled.

The token belongs to the company, not to TRVUE. TRVUE never holds a supporter's tokens at any point.

After a campaign is funded, supporters register a payout address. The company then freezes the allocation into a Merkle root, deploys a claim contract, and funds it with exactly the allocated total. Publication happens once: a published root is final, because supporters hold proofs against it.

Allocations match on the payout address, not on your account. A supporter who has registered no address at the moment the root is frozen is left out of it, and those tokens stay in the company's reserve.

Claiming stays open for 180 days from publication. After that anyone may sweep the remaining balance to a destination fixed when the contract was deployed. A claim costs network gas, paid by whoever submits it.

TRVUE removes or refuses campaigns and content that:

• present a token as a financial instrument, or promise a return
• misstate who the company is, who runs it, or what it has built
• describe a product the company has no intention of delivering
• infringe someone else's trademark, copyright, or other rights
• are unlawful where the campaign is offered, or target people who may not lawfully take part

The first of these is enforced automatically at submission: campaign text containing equity · shares · dividends · guaranteed returns · APY · ROI is rejected, and the founder is asked to describe utility, access and membership instead.

TRVUE can suspend a company. A suspension requires a written reason, which is recorded with the reviewer's name and a hash of the evidence and shown to that company's members and to TRVUE admins. It is deliberately kept out of the public record and out of the API.

A suspension is written as a revoked verification record, not as a deletion. The earlier record remains, so a company's history shows what was checked, when, and when it was withdrawn.

A suspended company's campaigns lose their verified company check and their Trust Score falls accordingly. Scores are recomputed by the engine and are never manually editable.

The TRVUE API serves campaign, company and compliance data. Access is by API key; keys are issued out of band by the operator and shown once at issuance. Rate limits are 30, 120 or 600 requests per minute depending on the key's tier.

Do not use the API to republish TRVUE verification records as your own assessment, to present a Trust Score as an endorsement, or to build a service implying that TRVUE approved something. Verification records are evidence, and their meaning is the meaning this document gives them.

Endpoints, authentication and error codes are documented under API documentation.

Nothing on TRVUE is investment, legal, tax or financial advice, and nothing on it is a recommendation to support a campaign or to acquire a token.

TRVUE provides the platform as it is. Campaign outcomes, product delivery, token value and company conduct are outside TRVUE's control, and verification does not move that risk onto TRVUE.

This page states no limitation of liability, no warranty disclaimer in the legal sense, no indemnity and no dispute-resolution clause. Those are the parts of a contract only counsel can draft, and inventing them here would be worse than leaving them out.

This description changes when the platform changes. The date in the notice above is the date it was last reconciled against the code, and it is the only claim this page makes about its own currency.

You can stop using TRVUE at any time, and TRVUE can suspend an account or a company under the section above. Neither this page nor the code defines a notice period, a deletion deadline on account closure, or what happens to a live campaign when its founder's account closes.

These questions are open. The code has no answer to them, so this page does not pretend to:

• Which entity contracts with users, where it is established, and which law and courts govern the relationship.
• Whether collecting money against future utility makes TRVUE a payment intermediary, and what licensing that implies in each market.
• Whether a campaign token is a security, a voucher, or something else under each jurisdiction's tests, and whether TRVUE distributing it changes the answer.
• A binding refund window, any consumer right of withdrawal, and how the two interact with a campaign cancelled mid-flight.
• Limitation of liability, warranties, indemnities, and the dispute-resolution route.
• An appeals process for suspension, with a response window and an independent reviewer.

The per-country eligibility rules the platform can enforce today are described under Compliance architecture — which is configuration, not legal advice, and carries the same warning.