Security & Privacy
Your data security and privacy are our top priorities. Learn how Flow API protects your information.
100% Client-Side
All processing in your browser
Zero Tracking
No cookies or analytics
No Data Storage
Nothing sent to servers
How It Works
Flow API is a 100% client-side application. This means all request parsing, visualization, and processing happens entirely in your browser using JavaScript. No data is ever sent to our servers.
✅ What this means for you:
- • Your API requests stay on your device
- • API keys and tokens never leave your browser
- • No server-side logs or database storage
- • Works offline after initial load
Verify Our Claims
Don't just take our word for it — verify our security yourself:
Open Browser DevTools
Press F12 or right-click → Inspect → Network tab
Paste a Request and Analyze
Watch the Network tab for any API calls
Confirm Zero Requests
You'll see no data sent to our servers during parsing
Security Best Practices
While Flow API is secure, we recommend these best practices:
⚠️ Use Test Credentials
When possible, use test/demo API keys instead of production keys
🔒 Redact Before Sharing
Remove sensitive tokens before taking screenshots or sharing links
🛡️ Self-Host for Maximum Security
Deploy your own instance on Vercel or Netlify for complete control
What We Don't Collect
No Request Data
Your API requests never reach our servers
No Personal Information
We don't track, store, or process any personal data
No Cookies or Analytics
No cookies, no Google Analytics, no third-party tracking
No Server-Side Logs
Only basic Vercel hosting logs (IP addresses, timestamps)
Local Storage Usage
Flow API uses your browser's localStorage to save your request history (optional feature). This data:
- •Stays on your device only
- •Never syncs to any server
- •Can be cleared anytime via browser settings
- •Is entirely optional (you can skip saving history)
Questions or Concerns?
If you have any security concerns or questions about how Flow API handles your data, please reach out:
Last updated: February 16, 2026