Terms

1. Who agrees

Customers buy the service. Users ask their team for help.

templ.fun Ltd runs Templ. It is a BVI Limited Company, company number 2191511. It registered on 28 October 2025. Its registered and mailing address is Quijano Chambers, P.O. Box 3159, Road Town, British Virgin Islands.

“Templ”, “we” and “us” mean templ.fun Ltd. “Customer” means the organization that runs a support workspace. Its manager, team and registered AI agents act for it. “User” means someone who asks that team for help through Templ.

These terms apply when you use Templ or sign an order form. You must be legally able to agree. A Customer representative must have authority to bind that Customer. Customers must supervise their authorized users. Customers must not design support for children without an agreed scope and required safeguards.

Customers owe the service fees. Users owe Templ no resolved-case fee for asking for support. A user's purchases from a protocol follow that protocol's separate terms. A privacy notice does not create consent to optional data use.

2. The service

Templ provides support software. Extra work needs an agreed scope.

Templ provides a wallet-connected support widget, a private team inbox and AI tools. Features depend on the workspace's settings and enabled release gates. A workspace flag can enable a feature for that workspace. It never grants extra data access or removes a safety check. A disabled feature is not a promised service.

A signed order form can set custom prices, service scope and service levels. The Safety rules form part of these terms. The DPA governs Customer Personal Data processing. The Privacy Policy explains other data uses.

Mandatory transfer clauses control any conflict within their scope. The DPA controls conflicts about Customer Personal Data. A signed order form controls its stated commercial changes. These terms control other matters. Summaries explain the clauses. The full clauses control.

3. Your duties

Customers run their support service. Users must share data lawfully.

Customers choose their notices, team, instructions, sources and integrations. They need the rights and lawful basis to provide that material. They must show clear privacy information before collecting user data. They remain responsible for their protocol, products and promises.

Customers must check answers where errors could cause harm. Wallet sign-in proves wallet control at that time. It does not prove a person's name or company authority.

Users must share only data they may lawfully share. Do not send another person's private data without authority. Never send a private key, recovery phrase, password or other secret. Use your own case. Do not seek access to another user's case.

Keep your wallet, device and session secure. Tell your manager or Templ about suspected misuse. A shared device can expose data you may read. Templ cannot restore your private key.

4. Team access

Managers grant team access. An order form alone grants none.

Users read their own cases. Team access follows current roles and permissions. Newly authorized team members may read retained history within their permission. User exports exclude internal notes.

Payment, billing rights, token ownership and display names grant no case access. Ordinary case assignment grants no access either. Specialists have limited access through qualifying follow-ups or mentions. Templ checks current access for private reads, writes, searches, exports, files and events.

Done-for-you support requires a signed order form. It states the tasks, coverage, escalation rules, price and any service levels. Templ staff act as the Customer's processor under its instructions. They enter its inbox only after its manager grants them explicit team access. Their role limits what they may do. The manager can revoke that access.

An order form, payment or operator role never opens a Customer inbox. Templ staff must follow lawful Customer instructions and the agreed scope. They cannot approve financial actions for the Customer or its users.

Self-serve software does not include free human services. Setup, installation, operating work and managed AI have separate quoted fees. Templ quotes service fees separately before work starts. These services are not free or included with a top-up. Self-serve install with one prompt is the product. Managed AI builds an agent on your docs and rules. Templ hosts it and updates it monthly. A service fee adds nothing to the prepaid case balance.

5. AI answers

AI can answer or draft. People must check important answers.

A workspace can allow AI answers, AI drafts only or AI off for a case. An agent cannot send user-facing answers in drafts-only mode. It cannot read or act on an AI-off case through the agent interface. An agent cannot change its own case mode. A person who sends a draft takes responsibility for that reply.

AI can produce wrong, incomplete, biased or outdated answers. It can invent facts and sources. Templ does not guarantee accuracy, unique output or rights the law does not recognize. Customers must check their sources, drafts and permitted AI actions.

A user may ask for a person on their own case. The request hands the case to the team. It adds no charge or permission. It does not promise an immediate reply.

Support provides information, not financial, investment, legal or tax advice. Check important instructions with the team before acting. Enabled managed AI may send relevant case material to its model provider under the DPA.

6. Public prices

Team-handled cases cost $8 each. They cost $4 after 100 billed team-handled cases in a UTC month.

An AI-only case costs $0.99. AI-only means the case resolved without a human staff reply. This rate applies to registered team agents and Templ's managed AI. A human staff reply makes the case team-handled, even if AI also replied.

The first 3 eligible final team-handled cases are free. AI-only cases bill from the first case. They use no free case and never advance the team-handled price step. The free start applies once per billing owner and once per app domain. It does not renew each month. Accounts under the same owner's control share this rule.

Each billed team-handled case takes its monthly price step when its charge becomes final. The cheaper step does not change earlier charges. Free and grant cases use no paid price step.

The public software offer has no seat, subscription, platform or minimum fee. The fee for a case your team resolves is a software fee. Separate services and applicable taxes may cost extra.

A signed order form may set custom prices for that workspace. It states its prices, scope and term. The public offer invites custom terms above 3,000 billable cases each month.

Custom pricing for bigger teams. Talk to us.

7. Billable cases

A case bills only after a person replied or a registered AI agent answered. It also needs a qualifying Templ step and final resolution under the pricing rule.

A user message opens a case. A message within 7 days of resolution reopens that case. A later message opens a new case. Only a user message opens a case.

The team can mark a case resolved. The user can confirm “Yes” or “Solved”. A person's reply or registered AI answer must come first. Automatic greetings and replies that only hand off to a person do not count.

A team resolution becomes final after 7 days without a reopen. A user's new message or “not solved” answer cancels it before then. A user's “solved” answer becomes final after 24 hours. Their new message or “not solved” answer cancels it during that time. A spam mark before finality excludes the charge.

Each case can have only 1 charge. Resolving a cancelled case again uses that same charge. A final charge keeps its case class and price after reopening. A cancelled charge uses current case facts and prices at its next billable resolution. Templ's managed AI needs the user's Yes before finalization. Managed AI billing stays closed until its own required checks pass. One canonical user bills once within the 24-hour duplicate window. A guest who links their wallet remains the same user.

Spam, qualifying duplicates, Templ checks, team previews and permitted install previews do not bill. Up to 10 listed test accounts may create 50 excluded test cases in 30 days. Excluded cases use no free case. Abandoned cases do not bill because time passes. Improvement copies never create or change a charge.

8. Stablecoin payments

You pay for resolved cases by prepaid stablecoin balance. Pay only through the instructions shown in your authenticated app.

Payments use the stablecoins and networks shown in the app. Supported tokens include USDC and USDT where official on configured EVM networks and Solana. Payments are direct stablecoin transfers. The app shows the enabled network, amount, recipient and payment request.

Pay to the address shown in the app. Create the request in your authenticated Plan view. Use the proven paying wallet named there. Check the token, network, address and amount before sending. Gas and wallet fees are separate. Chat cannot change payment instructions or start a payment or signature.

Templ credits only a verified transfer matched to its payment request. It checks the asset, network, payer, recipient, amount and finality. A receipt credits once. A payment memo is not required for credit. A wallet signature, screenshot or return page adds no balance. A payment method stays closed until its required checks and configuration pass.

An unmatched transfer needs operator review before credit. Talk to us with its public transaction reference and payment request. Do not send credentials. Wrong-network, wrong-token and wrong-address transfers may be lost. Templ cannot promise recovery or automatic credit.

Custom-deal invoices use payment requests tied to signed order forms. The same scanners verify their transfers. These requests earn no bonus credit.

Blockchain transfers are generally final and irreversible. A refund needs a separate payment. It cannot erase the original transfer. Stablecoins can lose value or become restricted by their issuer. Templ does not guarantee their market price or redemption.

The app records paid service credit in USD for the verified amount received. Standard top-ups are $100 to $10,000, in whole dollars. The eligible amount left after clearing debt earns 10% bonus credit from $2,000. It earns 20% at $10,000. The bonus percentages do not add together.

Eligible team-handled cases use free cases first. Reviewed grants and prepaid balance follow for both case classes. Grants follow their case count and end date. Bonus and grant credit cannot be withdrawn, transferred or refunded. Top-ups never renew automatically.

Reviewed founding credit covers 100 resolved cases. It ends when used or 90 days after it starts. Each billing owner can receive it once. Templ may approve reviewed pilot credit with an end date. Each pilot grant states its case limit and ends when used or on that date. List prices apply from day one. Credits never change the public price.

Payments buy Templ services. Templ receives them as its own funds. Your balance is service credit. It is not custody, a bank deposit or an investment. Templ does not hold your private keys or control your wallet.

A positive balance pays the whole next case, even if it becomes negative. A workspace with a verified top-up or a reviewed grant keeps working below zero. Templ contacts its managers. Only an audited operator can suspend it. Billing suspension refuses new cases. Open cases stay readable and answerable unless another lawful restriction applies. Their charges continue.

A workspace that never added balance and never held a grant pauses at -$20. The pause stops new cases and team or AI replies. Managers can still read, export and add balance. A verified top-up must restore a non-negative balance to restart support. An audited operator can also restart it. Balance alerts never cap spending or stop service.

9. Billing disputes

Dispute an error within 30 days. Refunds cover eligible unused paid balance.

A billing manager may dispute a final charge within 30 days. Reasons include spam, tests, duplicates and an unresolved case. Use the charge reference and a short reason. Do not send the user's private case as billing evidence.

Automatic dispute credits have a limit each UTC month. The limit uses final charges from the last 30 days. It is the larger of 2 charges or 5% of those charges. Each case class has the same limit, using only that class's final charges. Automatic credits must fit both the total limit and their class limit. Earlier automatic credits without a recorded class count against both class limits. Further disputes need operator review. Billing access grants no raw case access. Review uses charge metadata and any lawfully available de-identified copy.

On account closure, you may request a refund of eligible unused paid balance. Refunds cover paid top-ups younger than 365 days. Templ subtracts valid charges waiting to become final. Refunds return to the paying address on the same network. Bonus and grant credit are never refunded.

Final service fees are not refundable unless a billing correction, signed agreement or mandatory law requires a remedy. An order form can state other remedies. Legal checks may delay or prohibit a return. Templ cannot return assets it never received.

A price increase takes effect only after 30 days' notice. A lower price applies at once. A charge keeps the price table in force when it became provisional. A fixed order-form price follows that form. These rules do not remove mandatory rights.

10. Content rights

You keep your content. Templ uses it for agreed and lawful purposes.

Customers and users keep their rights in submitted content. They grant Templ the rights needed to host, process and deliver it. These rights cover the service, lawful security review and required legal duties. Separate data uses follow the Privacy Policy and DPA. This contract alone does not create a lawful basis for optional use.

Templ owns its software, design and documentation. Customers may use the service during their agreement. Users may use the support features their Customer enables.

Each party must protect the other's confidential business information with reasonable care. Use it only to perform this agreement. Share it only with people who need it and owe confidentiality duties. This excludes independently developed material and information lawfully received or already public without breach.

A party may disclose information when law requires it. Give notice where lawful. Limit disclosure to the required scope. Customer Personal Data also follows the DPA. Confidentiality duties continue while the information remains confidential.

11. Data use

Customers control support data. Templ's separate uses need their own lawful basis.

The Customer is the controller of user support data. Templ is its processor for support, including agreed done-for-you work. Templ is a controller for its account, billing, security, legal-intake and analytics data.

The improvement-copy feature has separate rules in Privacy and the DPA. It stays gated. The rules remove detected wallet addresses, transaction hashes, emails, handles and names. A de-identified copy may still be personal data. Templ needs lawful grounds, notices and transfer safeguards before using it. Account acceptance cannot replace required consent.

Improvement copies never create or change a charge. Billing counts your team's resolves and your users' “solved” answers. Templ gives 30 days' notice before copies could ever affect billing. You must tell your users about these copies. The DPA notice gives text you can use.

Eligible copies help improve answers, check resolution rules and review disputed charges. They last at most 730 days. They may outlive normal case deletion. A user's privacy request or objection removes them sooner. Workspace deletion removes them too. Legal holds never extend their retention. Templ sends no improvement rows to model providers and trains no model on them.

No product setting excludes a workspace from the enabled copy rule. A signed custom contract can do so. Want a contract without this? Talk to us. The copy store grants no access to raw private cases.

Resolved, abandoned and spam cases normally expire 365 days after their last message. Cleanup runs through service activity and scheduled work. Expired data can remain until cleanup runs. Open cases remain until closed or validly deleted. Archive does not change retention. A documented legal hold can preserve raw service data.

At service end, return or deletion follows the DPA. Export important records before access ends. User exports exclude internal notes. A domain change or deployment shutdown does not delete stored data.

Private cases are access-controlled. They are not end-to-end encrypted. Templ applies the DPA's security measures and responds to incidents. The Privacy Policy explains account records, provider logs and deletion limits.

12. Lawful use

Use Templ for lawful support. Do not harm people or bypass security.

Do not use Templ for fraud, phishing, harassment, exploitation, malware or unlawful content. Do not unlawfully disclose personal data. Never ask for private keys, recovery phrases or other secrets. Do not use chat to start wallet signing, approvals or transactions. Questions about past public transactions remain allowed.

Do not bypass user isolation, permissions, revocation, rate limits or feature gates. Do not impersonate a person, organization or authority. Do not use stolen credentials. Do not manipulate free cases, duplicates, grants or resolved-case billing.

Follow sanctions and export laws that apply to you or Templ. Do not act for a prohibited person when law bars that service. The Safety rules explain the applicable scope.

Templ may protect against attacks and unauthorized access. It may restrict service for verified breaches, unpaid fees or applicable legal duties. Content enforcement and disclosures follow the Safety review process. A report alone grants no access and causes no automatic restriction.

Where lawful and practical, Templ explains the reason and allows time to fix a breach. Urgent security or legal duties may require immediate action. You may appeal a platform decision through Safety.

13. Service limits

Keep your own important records. Either party can end service under these rules.

The service has message, storage, request, search, file and provider limits. It is not a permanent archive. Standard limits promise no measured throughput or unlimited use. Only an order form can set a service-level agreement.

Templ may maintain or change the service with reasonable notice where practical. It will not remove a fixed order-form commitment without agreement or a lawful remedy. External wallets, blockchains and providers can interrupt their services.

A Customer may request closure at any time. An order form controls its term, renewal and early exit. Templ may end self-serve service with 30 days' notice. It may end it sooner for an uncorrected material breach, active security threat or legal requirement.

Ending access does not cancel valid fees, agreed remedies, confidentiality or data duties. Templ follows the DPA for return, deletion and lawful preservation. Ending access does not erase public blockchain records.

14. Warranties

Templ provides support information. It does not guarantee protocol or blockchain outcomes.

Templ will use reasonable care and skill to provide the agreed service. Subject to mandatory law, other warranties are excluded. Templ promises no uninterrupted service, error-free AI or particular support result.

Read-only transaction checks may be incomplete or wrong. They are not audits, endorsements or proof that funds are safe. Templ provides no custody, exchange, brokerage or transaction-signing service. It provides no financial, investment, legal or tax advice.

Wallet sign-in uses an authentication message. That signature proves wallet control for its stated session. It authorizes no transfer or token approval. Chat never starts signing or submits transactions.

Public blockchain data can reveal addresses, amounts and transaction history. Others may copy it or link it to people. Templ cannot change or delete that history. Protocols and wallets have their own terms.

15. Liability limits

Contract claims have limits. Mandatory rights remain available.

To the extent lawful, neither party owes the other damages for indirect or consequential loss. This includes lost profits, revenue, business opportunities and expected savings. This exclusion does not remove direct data-restoration costs caused by a DPA breach.

For Customer claims, each party's ordinary aggregate liability has a cap. It is the greater of US$1,000 or the affected service's fees over the preceding 12 months. Those fees include amounts paid or payable. The period ends at the first event giving rise to the claim.

Confidentiality breaches, data-protection breaches and section 16 indemnities have a higher combined cap. It is the greater of US$10,000 or twice those fees. This includes ordinary claims. The caps do not add together.

A user's direct claim against Templ has an aggregate cap of US$1,000 where lawful. Users owe no Customer fees or business indemnities.

No exclusion or cap covers fraud, fraudulent misrepresentation, willful misconduct or gross negligence. None limits death or personal injury from negligence where law forbids it. None limits liability that applicable law prohibits limiting. Customer fee obligations remain payable.

These terms preserve data subjects' statutory compensation and mandatory transfer-clause rights. They preserve regulator remedies and mandatory consumer rights. Caps apply only between the contracting parties where lawful.

16. Business indemnities

Each business covers defined claims caused by its own responsibilities.

The Customer must defend Templ against third-party claims caused by unlawful Customer content or instructions. This includes infringement by Customer-supplied material. The Customer pays resulting court awards and approved settlements. This excludes loss caused by Templ's breach or misconduct.

Templ must defend the Customer against third-party claims that authorized use of Templ software infringes intellectual property rights. Templ pays resulting court awards and approved settlements. This excludes Customer material, AI output, unauthorized changes and combinations that caused the claim. It excludes continued use after a lawful notice to stop infringement.

Templ may obtain rights, replace the affected feature or change it to avoid infringement. Otherwise, it may end that feature. Any refund or other remedy follows mandatory law and the applicable signed agreement.

The protected party must give prompt notice and reasonable help. The defending party controls the defense. It cannot admit the other's fault or impose non-monetary duties without consent. Consent must not be unreasonably withheld. Section 15 applies where lawful. Users give no business indemnity.

17. Governing law

BVI law governs. Mandatory court and complaint rights remain available.

British Virgin Islands law governs this agreement, excluding its conflict-of-laws rules. Competent British Virgin Islands courts have exclusive jurisdiction for Customer contract disputes. Venue is Road Town, subject to the court's rules.

First send a written dispute notice with the facts and requested remedy. The parties will try to resolve it for 30 days. This does not delay urgent court relief or statutory deadlines.

Mandatory consumer law, regulator jurisdiction and data-subject rights remain available. Transfer clauses keep their required governing law, courts and complaint rights. Users retain any mandatory right to sue in their home courts.

18. Changes and contact

Templ dates changes. Use its widget first when you need help.

Templ publishes dated terms and gives Customers 30 days' notice of material changes. Immediate changes may address mandatory law or urgent security issues. Templ explains them as soon as lawful and practical. Price changes follow section 9.

Changes apply to future use. They do not rewrite fixed order forms or expand processing instructions without required agreement. You may stop using an affected service before a rejected material change takes effect. Closure rules still apply.

Neither party may transfer this agreement without reasonable consent. A business transfer may occur if its successor assumes all duties. It must preserve data rights and required notices. A transfer grants no new use of personal data.

If a clause is unenforceable, the rest remains effective. A failure to enforce a right is not a waiver. These terms and applicable order forms form the service agreement. Mandatory data-subject beneficiaries keep their rights.

Talk to us for Templ support and billing help. Use Legal notices for legal-page questions and formal notices. Formal legal and contract notices may also go to legal@usetempl.com. Use Privacy requests for data requests. These requests may also go to privacy@usetempl.com. Written notices may use our mailing address above. Use Safety for its legal reports, urgent reports and appeals.