Security and trust

Financial clarity without financial control.

Dinty is designed to explain provider-reported money movement through read-only, purpose-limited evidence. Dinty does not move money or gain authority to alter financial transactions.

What Dinty reads

Approved evidence required for the explanation

  • Supported orders, payments, and refunds
  • Supported payouts and settlement entries
  • Provider-reported fees and corrections
  • Dispute evidence where accessible
  • Capability, coverage, and freshness state

What Dinty never does

Initiate or alter a financial transaction

  • Create or change an order
  • Capture, void, or refund a payment
  • Submit dispute evidence
  • Change payout configuration
  • Initiate bank or accounting transactions

Trust architecture

The controls behind an explainable answer.

Dinty's backend is built around explicit authority, minimized evidence, immutable revisions, and fail-closed conclusions.

Workspace isolation

Every tenant-owned read, write, task, event, export, cache key, and stored artifact is scoped to an explicitly validated authority root. Provider identifiers never grant access.

Purpose-limited collection

Dinty imports only fields registered for an approved product purpose. Unknown provider fields are not silently stored, and raw unsanitized response bodies are not product data.

Protected credentials

Connector secrets are designed for encrypted storage, narrow runtime use, rotation, revocation, and complete audit. Secret values are never product-display fields.

Immutable evidence and lineage

Corrections append new revisions instead of rewriting history. Dinty conclusions retain the exact source, semantic, projector, and policy versions that support them.

Audited sensitive access

Scoped support access, exports, integration changes, privacy actions, and failed attempts are designed to produce durable, bounded audit evidence without exposing secrets or unnecessary personal data.

Retention with explicit holds

Visible history, provider correction windows, technical evidence floors, privacy restrictions, open cases, exports, and legal holds are resolved deliberately rather than by a single blanket duration.

Honest product status

Trust also means not claiming readiness before it is proven.

This site is a pre-launch product preview. Production connections and customer-visible financial conclusions remain closed until deployment, credential, live-provider, reconciliation, and pilot gates have passed.