Terms of Service

SilentAuth provides an online control plane for projects, registered agents, policies, approval requests, local proof workflows, signed receipts, and audit history.

You may use SilentAuth only if you can form a binding agreement and comply with these Terms, applicable laws, and any policies shown in the product or documentation.

You are responsible for your account, project API keys, connector credentials, gateway devices, local proof hardware, and any actions performed through your organization or projects.

Keep credentials secret, use strong authentication, rotate keys when needed, and promptly revoke agents or gateways that are compromised, retired, or no longer under your control.

SilentAuth does not execute your production actions. SilentAuth receives intent requests, evaluates policy, coordinates approval or proof, and issues receipt data that your agent, application, or gateway verifies before acting.

You are responsible for deciding which actions are protected, validating receipts before execution, handling denial or expiry safely, and ensuring your own systems do not bypass SilentAuth controls.

SilentAuth is currently offered as an Open Preview. Preview features may change, break, be limited, or be removed as the platform is hardened for production.

Do not rely on Open Preview for high-risk regulated workflows, emergency systems, irreversible financial transfers, or safety-critical automation unless you have a separate written agreement with SilentAuth.

You may not use SilentAuth to attack, disrupt, scan, overload, reverse engineer, or bypass the platform or any connected service. You may not submit unlawful, abusive, deceptive, or malicious workflows.

You may not use SilentAuth to authorize actions that violate another service's terms, compromise third-party systems, or process data you do not have permission to use.

You are responsible for the behavior of your agents, scripts, webhooks, connectors, local gateways, QR or NFC flows, VINAC-FM proof devices, and any downstream system that consumes a SilentAuth receipt.

Mock connector examples are for testing the approval loop. Real connector credentials should be configured only after you have reviewed the security model, logging behavior, and operational risks.

During Open Preview, SilentAuth is provided without a formal uptime commitment unless a separate written agreement says otherwise. We may limit, suspend, or modify access to protect the platform or other users.

Support is provided on a best-effort basis during preview. Contact us with security issues, account problems, or integration questions.

SilentAuth is provided as-is during Open Preview. To the fullest extent permitted by law, SilentAuth disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation.

To the fullest extent permitted by law, SilentAuth will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost data, business interruption, or unauthorized actions in your own systems.

We may update these Terms as the product evolves. If changes are material, we will take reasonable steps to notify users through the site, app, or email.

Continuing to use SilentAuth after updated Terms become effective means you accept the updated Terms.