Trust and security
We take the security of your data seriously. Here's how we protect it.
Local execution
Weavori runs on your machine or in your CI environment. Your source data is never uploaded to external servers. Generation, sampling, and export all happen locally.
Encryption at rest and in transit
All connections to Weavori services use TLS 1.3. Authentication tokens are encrypted at rest using industry-standard algorithms. Access entitlements are cryptographically signed for tamper resistance.
Minimal data collection
We collect only what's necessary: account credentials (email, auth provider ID), plan status, and basic usage metrics. No database contents, no query patterns, no sampled rows.
Third-party infrastructure
We use Supabase for authentication and database, Paddle for payment processing, and Vercel/Render for hosting. Each provider follows industry-standard security practices and compliance certifications.
Code signing and releases
All releases are built via GitHub Actions with signed commits. Binaries are published through private GitHub Releases. Checksums are verified during installation.
Vulnerability disclosure
If you discover a security vulnerability in Weavori, please email us directly at security@weavori.com. We ask that you give us reasonable time to respond before disclosing the issue publicly. We will acknowledge receipt within 48 hours and work toward a resolution.