Our Commitment to Security & Privacy
SnappySnag accelerates issue discovery in mobile apps while maintaining a zero-compromise architecture designed to safeguard user privacy and proprietary code.
1. Automatic PII Redaction
During Flutter widget tree traversal, password inputs (obscureText: true) and sensitive fields are masked on-device prior to transmission.
2. Zero AI Model Training
Screenshots, widget trees, and user tickets are never used to train public or proprietary AI models. Data is strictly utilized for inference and code synthesis.
3. Complete Encryption at Transit & Rest
All client-server communications enforce TLS 1.3. Stored database records and raw screenshots are encrypted at rest with AES-256.
4. Open Client SDK Architecture
The client-side Flutter SDK executes transparently without hidden background tracking or obfuscated endpoints. All payloads follow public schemas.
Technical Safeguards & Architecture
Database-level Row Level Security (RLS) is strictly enforced across all PostgreSQL tables. Users are cryptographically prohibited from querying rows belonging to unjoined projects.
API requests originating from unauthorized bundle identifiers or package names are rejected at the edge (403 Forbidden), mitigating risk if client keys are extracted.
When a user triggers account or project deletion, all associated feedback records, comments, and storage blobs are purged immediately and permanently from production servers.
Payment details are processed entirely via Stripe (PCI-DSS Service Provider Level 1). Credit card numbers never touch or reside on SnappySnag servers.
We welcome security researchers and developers to report potential vulnerabilities. If you discover a security concern, please contact our security team directly.