Privacy

Privacy Policy

How SilentAuth handles account data, project configuration, approval events, signed receipt metadata, and local proof information during Open Preview.

Last updated: June 18, 2026

This page is written for the SilentAuth Open Preview. It should be reviewed by counsel before broad commercial launch or enterprise contracting.

What We Collect

SilentAuth collects the account information needed to create and operate your account, such as name, email address, organization details, authentication events, and support messages.

When you use the platform, SilentAuth stores project configuration, registered agent metadata, policy settings, approval requests, receipt metadata, audit events, gateway status, webhook configuration, and related operational logs.

For VINAC-FM and other local proof workflows, SilentAuth is designed to store proof metadata such as nonce, expiry, proof tier, gateway identity, and result status. Raw audio should remain local to the gateway and is not intended to be stored by the cloud platform.

How We Use Information

We use platform data to authenticate users, operate projects, route approval requests, issue and verify receipts, show audit history, send account and approval notifications, provide support, and improve platform reliability.

We may use aggregated operational data to understand feature usage, detect abuse, diagnose failures, prioritize product work, and protect the service from spam or automated misuse.

How We Share Information

SilentAuth does not sell personal information. We share information with service providers only as needed to run the platform, such as authentication, database, hosting, email delivery, monitoring, and support systems.

We may disclose information if required by law, to protect the rights and safety of SilentAuth or others, or in connection with a merger, financing, acquisition, or similar business transaction.

Security

SilentAuth is built around scoped projects, audit trails, signed receipts, short expiry windows, and separation between the cloud control plane and local proof gateways.

No online service can guarantee absolute security. You are responsible for protecting your account credentials, project API keys, gateway devices, and any connector secrets you configure.

Data Retention

We retain account, project, audit, and receipt data for as long as needed to provide the service, satisfy legal obligations, resolve disputes, enforce agreements, and preserve security logs.

You may request account deletion or data export by contacting us. Some audit records may be retained where required for security, fraud prevention, legal compliance, or legitimate business records.

Your Choices

You can update account information in the app, rotate project API keys, pause or revoke registered agents, disable webhooks, and remove gateway registrations when they are no longer needed.

You can unsubscribe from non-essential communications. Transactional emails such as password reset, account security, approval, receipt, and support messages may still be sent where needed to operate the service.

Open Preview

SilentAuth is currently in Open Preview. Features, data models, retention defaults, and infrastructure may change as the platform moves toward production readiness.

If you plan to use SilentAuth with regulated data, high-risk production workflows, or enterprise compliance requirements, contact us first so the appropriate security and legal review can happen before launch.

Questions

For privacy, security, or account questions, contact the SilentAuth team.

Contact SilentAuth