Terms of Service
These draft terms describe the expected commercial and operational boundaries for early TxnShield users. They are written for launch review and should be replaced or approved by counsel before broad rollout.
Service
TxnShield provides a control plane and runtime integration surface for evaluating sensitive application transactions, recording decisions, managing policies, and operating related alerts, webhooks, and billing controls.
TxnShield complements authentication and authorization. Customers remain responsible for their application permissions, user experience, production rollout decisions, and final enforcement behavior inside their own systems.
Accounts and Access
Customers are responsible for maintaining accurate account information, securing user credentials, assigning appropriate organization roles, and promptly removing access for users who no longer need it.
Secret keys must be stored only in trusted server-side systems. Customers are responsible for rotating keys after suspected exposure or personnel changes.
Acceptable Use
Customers may not use TxnShield to attack, disrupt, reverse engineer, overload, or probe the service beyond ordinary integration testing. Attempts to bypass rate limits, abuse public forms, or submit malicious payloads may be blocked.
Customers should avoid sending unnecessary raw secrets, full payment details, or sensitive personal data in request summaries. TxnShield is designed to store security-relevant transaction evidence, not complete customer records.
Plans and Billing
Plan limits are enforced by TxnShield entitlements and usage rules. Stripe may be used for checkout, invoices, payment collection, and subscription lifecycle events.
If billing becomes past due, canceled, unpaid, incomplete, or a trial expires, premium mutations may be restricted while existing data remains available where practical.
Availability and Changes
TxnShield is an early-launch product. Features, limits, documentation, and service behavior may change as the product matures. Material changes should be communicated through product surfaces, documentation, or direct customer contact where appropriate.