Terms of Service

Terms for using decide.

These terms cover the public website, Decision API, reference applications, API keys, billing links, documentation, and support workflows.

Last updated: May 23, 2026 (UTC)

API access terms Privacy Security Trust packet
Scope Website, Decision API, docs, reference applications, and support workflows.
Customer role Own downstream actions, API-key custody, data inputs, and human review.
Output limits Decision outputs are operational records, not professional advice.
Precedence Signed agreements control where they conflict with public terms.

Agreement and order of control

By using decide.fyi or related services, you agree to these Terms. If you use decide on behalf of a company, you confirm you have authority to do so.

If a signed order form, master services agreement, data processing addendum, enterprise agreement, or other written agreement applies, that written agreement controls where it conflicts with these public Terms.

Service scope

  • decide provides deterministic decisioning infrastructure, including the Decision API, Decision Record v1 outputs, replay surfaces, reference applications, docs, status pages, and trust/security resources.
  • Reference applications demonstrate source-backed checks for refund, cancellation, return, and trial workflows. They are proof surfaces and compatibility endpoints, not legal advice or vendor-authoritative systems.
  • Paid API plans add production API keys, quotas, usage metering, replay visibility, and support boundaries as described in pricing pages, API access terms, or a signed agreement.

Accounts, API keys, and access

  • You are responsible for account access, API key custody, and downstream systems that call decide.
  • Production API keys must be kept server-side and must not be exposed in browsers, client apps, public repositories, or shared screenshots.
  • We may limit, suspend, rotate, or revoke access to protect the service, enforce plan limits, address abuse, or comply with law.
  • You must provide accurate contact and billing information when requesting or purchasing API access.

Customer responsibilities

  • You decide what actions your product, agent, queue, CRM, billing system, or workflow takes after receiving a verdict.
  • You are responsible for validating integrations, monitoring behavior, storing records appropriately, and applying human review where your workflow requires it.
  • Do not submit unnecessary personal data, regulated data, secrets, credentials, or content you are not authorized to process.
  • Do not use decide to violate law, bypass security controls, overload the service, reverse engineer protected systems, or make unsupported compliance claims.

Decision outputs and advice limits

Decision outputs are operational records tied to configured context and guardrails. They are not financial, legal, medical, employment, or professional advice.

Reference policy outputs depend on public source materials, configured rules, declared inputs, and current runtime state. They may be incomplete, outdated, or inapplicable to a specific customer, region, purchase channel, enterprise contract, promotion, or exception.

Billing and cancellation

  • Self-serve payments are processed through Stripe or the checkout provider shown at purchase.
  • Commercial terms for API access kickoff, production API plans, cancellation, refunds, credits, and support boundaries are listed at API access terms, unless a written agreement says otherwise.
  • Pricing, plan limits, and included features may change prospectively. Changes do not override an active signed order during its stated term unless that order allows it.

Decision lifecycle artifacts

  • Decision Records, execution receipts, Outcome Records, policy intelligence, exported packets, and verification responses are operational evidence artifacts produced from submitted inputs and configured runtime state.
  • Customers decide how those artifacts are used in internal approvals, audits, disputes, support workflows, and downstream systems.
  • Verification proves hash and signature consistency for the artifact being checked; it does not independently validate the truth of customer-provided facts or third-party system state.

Availability and changes

  • Public sandbox, docs, reference applications, and preview surfaces are provided on a best-effort basis.
  • Status and readiness pages are operational snapshots, not contractual uptime commitments.
  • Contractual uptime, retention, support, custom security terms, or compliance addenda require a paid tier or written agreement that says so.
  • We may update, suspend, replace, or discontinue features as the product evolves.

Security and compliance claims

We do not claim SOC 2, ISO 27001, HIPAA, or regulated-industry suitability unless explicitly published in the relevant artifact or agreed in writing. Current security posture is described at Security.

Intellectual property and feedback

decide, the website, API design, docs, examples, and related service materials are owned by decide or its licensors. You may use docs and examples to integrate with the service, but you may not copy branding or service materials in a misleading way.

If you send feedback, suggestions, or requests, we may use them to improve the service without owing compensation, unless a written agreement says otherwise.

Privacy

The Privacy Policy explains how decide handles account data, API request data, logs, local browser data, payments, source alerts, and support workflows.

Contact and changes

We may update these Terms as the product, pricing, infrastructure, or legal requirements change. The updated date above shows the latest public revision.

Questions: support@decide.fyi.

Related pages: Privacy, API access terms, Security, and Trust.