Repository navigation
Security and Privacy
RUN STITCHCODE is built with security and privacy as core principles — not afterthoughts. This page explains what protects your data and how the app stays safe.
✅ Nothing leaves your device — no servers, no accounts, no tracking
✅ Everything runs offline — once loaded, zero network calls
✅ Sensitive data encrypted — WiFi passwords, contacts, messages protected
✅ Open source — code you can inspect, audit, and trust
The app has been audited against OWASP best practices (2026 edition) and achieves the highest security rating for a client-side web application.
flowchart LR
A[Your Data] --> B[Encrypted Storage]
B --> C[Device Only]
C --> D[No Network]
D --> E[Safe ✓]
style A fill:#eef2fb,stroke:#16336f,stroke-width:2px
style B fill:#eaf6ee,stroke:#132a22,stroke-width:2px
style C fill:#fff6f0,stroke:#c22e12,stroke-width:2px
style D fill:#ffe9b8,stroke:#7a4a00,stroke-width:2px
style E fill:#d4edda,stroke:#155724,stroke-width:2px
| Data Type | Protection | Why It Matters |
|---|---|---|
| 🔗 URLs | Encrypted | Prevents history leakage |
| 📶 WiFi Passwords | AES-256-GCM | Critical credential protection |
| 👤 Contact Cards | Encrypted | Personal information safety |
| 📞 Phone Numbers | Encrypted | Privacy preservation |
| ✉️ Email Addresses | Encrypted | Prevents spam targeting |
| 💬 Messages | Encrypted | Confidential communication |
| 🎨 Theme Choice | Plaintext | Non-sensitive preference |
┌──────────────┐ ┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ You type it │ → │ JSON encode │ → │ AES-256-GCM │ → │ localStorage│
│ │ │ │ │ Encrypt │ │ (encrypted) │
└──────────────┘ └─────────────┘ └──────────────┘ └─────────────┘
↓ ↓
PBKDF2-SHA256 Random Salt + IV
350,000 iterations (unique per item)
| Parameter | Value | Standard |
|---|---|---|
| Algorithm | AES-GCM | NIST SP 800-38D |
| Key Size | 256 bits | Military-grade |
| Key Derivation | PBKDF2-SHA256 | NIST SP 800-132 |
| Iterations | 350,000 | OWASP 2026 |
| Salt | 16 bytes random | Per encryption |
| IV | 12 bytes random | Per encryption |
The app enforces strict rules about what code can run:
default-src 'self' → Only load resources from the app itself
script-src 'self' blob: → No inline scripts, no external scripts
style-src 'self' 'unsafe-inline' → Inline styles allowed (React requirement)
img-src 'self' blob: data: → Images from app or user uploads only
connect-src 'self' → No external API calls (none exist)
frame-ancestors 'none' → Cannot be embedded in other sites
worker-src 'self' blob: → Service workers allowed
object-src 'none' → No plugins (Flash, Silverlight, etc.)
This prevents:
- ❌ Cross-site scripting (XSS) attacks
- ❌ Malicious script injection
- ❌ Clickjacking attempts
- ❌ Plugin-based exploits
Every piece of data is checked before use:
| Input Type | Validation | Purpose |
|---|---|---|
| URLs | Protocol whitelist (http/https only) | Blocks javascript:, data:, vbscript:
|
| Header sanitization | Prevents newline injection attacks | |
| File Uploads | MIME type + magic number check | Ensures real images only |
| QR Payloads | ISO/IEC 18004 size limits | Prevents DoS, ensures scannability |
| Control Characters | Stripped | Prevents encoding confusion |
- ❌ No analytics or tracking
- ❌ No cookies (except PWA functionality)
- ❌ No fingerprinting
- ❌ No telemetry
- ❌ No third-party scripts
- ❌ No cloud storage
- ❌ No account system
- ❌ No data selling
flowchart TD
A[You type data] --> B{Stored?}
B -- Yes --> C[Encrypted in browser localStorage]
B -- No --> D[Processed in memory only]
C --> E[Stays on YOUR device]
D --> E
E --> F[Never sent anywhere]
F --> G[Deleted when you clear browser data]
style C fill:#d4edda,stroke:#155724,stroke-width:2px
style F fill:#d4edda,stroke:#155724,stroke-width:2px
The app is designed to work without internet:
- Initial Load: Downloads the app once (~5 MB)
- Service Worker: Caches everything for offline use
- Zero Dependencies: All fonts, libraries bundled inside
- No Network Calls: Literally zero requests after load
- ✅ Works on airplanes, subways, remote areas
- ✅ No server downtime affects you
- ✅ No man-in-the-middle attacks possible
- ✅ No data interception on public WiFi
- ✅ Complete privacy (no one sees your usage)
When installed as a desktop app:
| Setting | Value | Protection |
|---|---|---|
| nodeIntegration | false | Prevents Node.js access from web content |
| contextIsolation | true | Isolates preload script from renderer |
| CSP | Enforced via headers | Same strict rules as web version |
| Preload API | Minimal exposure | Only essential functions exposed |
View Electron security details
A code that doesn't scan is a security issue (wasted resources, failed campaigns):
- ✅ Real decoder test before approval
- ✅ Contrast validation (4.5:1 minimum ratio)
- ✅ Border enforcement (≥4 modules)
- ✅ Error correction level checks
- ✅ Capacity validation per ISO standard
This implementation meets:
| Standard | Level | Status |
|---|---|---|
| OWASP Top 10 (2026) | All categories | ✅ Compliant |
| OWASP ASVS 4.0 | Level 1 | ✅ Achieved |
| GDPR Article 25 | Data Protection by Design | ✅ Compliant |
| NIST Cybersecurity Framework | Identify, Protect, Detect | ✅ Aligned |
| CWE/SANS Top 25 | Relevant weaknesses | ✅ Mitigated |
Found something concerning? Please report it responsibly:
- Do NOT open a public issue
- Go to repository Security tab on GitHub
- Choose "Report a vulnerability" (private advisory)
- Describe what you found with reproduction steps
| Step | Timeframe |
|---|---|
| Acknowledgment | Within 48 hours |
| Initial Assessment | Within 7 days |
| Fix & Release | As fast as safely possible |
| Public Credit | In release notes (if you want) |
If hosting the app yourself:
- HTTPS Only - TLS 1.3 with HSTS enabled
- Security Headers - CSP, X-Frame-Options, X-Content-Type-Options
- No Modifications - Don't remove encryption or validation code
- Subresource Integrity for any CDN resources
- Regular dependency updates (
npm audit) - Automated security scanning in CI/CD
- Consider bug bounty program
Self-hosting guide
Production checklist
A: No. WiFi passwords are encrypted with AES-256-GCM before being stored. Even if someone accesses your browser's localStorage, they'd see only ciphertext.
A: Never. Zero network requests are made after the initial load. Your data never leaves your device.
A: Your saved history will be deleted. This is why the app offers PNG/SVG exports — keep those as backups!
A: Like any QR tool, it could generate codes pointing to bad sites. However, the app itself doesn't host or transmit anything malicious. Always verify QR codes before scanning!
A: The key is derived from your browser's stable properties + random salt. It's never stored — it's regenerated each session. This means encrypted data is tied to your specific browser/device.
- Test before printing - Always use the print proof sheet
- Verify URLs - Check where QR codes lead before sharing
- Use high error correction - Level H for harsh environments
- Keep backups - Export important codes as PNG/SVG
- Update regularly - Keep your browser and the app current
Built with care • Audited for safety • Trusted by design
Made with care for curious people of every age · MIT licence · If it scans, ship it ✓