SETSimple. Easy. Transactions.SET Consults · a member of SET Enterprises

PUBLIC LEGAL / TERMS OF SERVICE

Use the dashboard.
Keep server access bounded.

These Terms govern Set-Ledger, operated by SET Enterprises, LLC, including implementation reviews, onramp link maintenance, client workspaces, and signed operational records. Stripe provides checkout and eligible crypto purchases; Privy provides customer wallet authentication.

Last updated: September 10, 2026 · Service reviews, maintenance, and protected client operations

Controlling boundary: command records are audit entries only. They do not authorize or cause financial activity, provider activity, regulated decisions, or external communications.

1. Acceptance and eligibility

By accessing or using Set-Ledger, you agree to these Terms and acknowledge the Privacy Policy. The informational dashboard is public. Server records, secrets, protected history, and archive retrieval are not public. Do not share hook secrets, access tokens, sessions, or exported logs.

2. Service scope

The $495 implementation review provides a written implementation plan. The optional $195 USD monthly retainer covers maintenance of a working onramp link. The retainer renews monthly until canceled through the Stripe billing portal; cancellation takes effect at the end of the current paid period. Crypto purchase principal and provider transaction fees are separate from SET service fees.

Set-Ledger receives properly signed webhook records, automatically activates paid retainer workspaces, records required operator follow-up, and retains bounded operational records. Implementation reviews use operator approval. Legacy decisioning, simulation, underwriting, and financial-reasoning routes remain retired.

Provider configuration and link availability do not guarantee customer eligibility, wallet funding, settlement, or uninterrupted third-party service. Customer authentication, consent, and provider verification remain required.

3. User authority and responsibility

You may use the Console only for a lawful, authorized operational purpose. You are responsible for the accuracy, authority, and legality of records you submit and for keeping webhook sources and credentials under your control. A successful receipt means only that an audit record was accepted; it is not approval, settlement, execution, authorization, or proof that an external action occurred.

4. Data restrictions and acceptable use

Submit only minimized operational metadata necessary for the retirement record. You must not submit:

  • live payment credentials, account or routing numbers, government identifiers, authentication secrets, or private keys;
  • customer files, nonpublic personal information, biometric data, identity documents, raw transaction descriptions, or SAR information;
  • malware, unlawful content, instructions to bypass controls, or material you lack authority to retain; or
  • commands represented as executed when they were only recorded.

Search engines, AI discovery services, accessibility tools, and other automated agents may crawl, index, quote, and summarize publicly available pages in accordance with robots.txt. This permission does not extend to protected interfaces, API routes, stored records, credentials, personal data, or attempts to evade access controls. You may not probe, overload, reverse engineer, or attempt unauthorized access to the Console or its storage. Set-Ledger does not automatically remove or substitute sensitive-looking fields. Accepted payload content is stored without field-level redaction within the size limit and may later appear in archived logs. This makes payload minimization a condition of use.

5. Hosting, Stripe, and third-party services

The Console depends on its hosting and storage providers, whose terms and privacy notices may also apply. Stripe is not the operator of the Console, and the Console is not a Stripe Connect Platform, Connected Account dashboard, payment interface, or substitute for Stripe’s agreements.

If you separately enroll in or use Stripe Connect, that activity is governed by the applicable Stripe Connected Account Agreement, the incorporated Stripe agreements, your agreement with the relevant platform provider, and applicable law. Stripe’s processing of personal data is described in the Stripe Privacy Policy. These links do not establish sponsorship, approval, integration, or authorization.

6. Security, suspension, and termination

We may suspend or revoke access, reject a hook, or preserve records when reasonably necessary to protect the Console, comply with law, investigate an incident, enforce these Terms, or maintain the retirement boundary. Retirement or deletion schedules may be paused when preservation is legally required or necessary for a documented security incident. You must promptly report suspected unauthorized access through an authorized internal channel.

7. Disclaimers and limitation

To the fullest extent permitted by law, the Console is provided “as is” and “as available,” without warranties of uninterrupted availability, completeness, fitness for a particular purpose, noninfringement, or regulatory sufficiency. No system is perfectly secure, and an audit record may be incomplete, delayed, duplicated, or unavailable.

To the fullest extent permitted by law, SET Enterprises, LLC and persons associated with the retired project are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, lost data, business interruption, provider action, financial loss, or reliance on a receipt as proof of execution. These limitations do not apply where prohibited by law.

8. Changes, governing law, and contact

We may update these Terms when the Console, retention model, vendors, or law changes. The updated date will identify the current version. Missouri law governs these Terms, without regard to conflict-of-law principles, subject to non-waivable rights. If a provision is unenforceable, the remaining provisions continue.

Questions, incident notices, and legal notices must be sent to the project owner through an authorized internal SET Enterprises channel. Do not use webhook or command payloads as a notice channel.