Data Transparency
Exactly what Dobermann collects, what it doesn't, and how it all works.
What We Collect
| Data | Example | Purpose |
|---|---|---|
| API call count | 42 |
Dashboard stats |
| Batch run count | 3 |
Dashboard stats, free tier limits |
| Records processed | 1,200 |
Dashboard stats |
| Execution time | 8,450ms |
Dashboard stats |
| Environment base URL | https://api.example.com |
Environment licence validation |
| Extension version | 1.5.0 |
Compatibility & support |
| VS Code version | 1.96.0 |
Compatibility |
| OS platform | win32 |
Compatibility |
| Feature usage flags | {"pagination": true} |
Product development |
What We Never Collect
None of the following ever leaves your machine:
- Request or response bodies
- Auth tokens or credentials
- CSV, JSON, or Excel file contents
- API endpoint paths, headers, or query parameters
- Individual record data
- Error message content (only success/failure counts)
How It Works
- Counters are aggregated locally, per environment, per day
- Flushed to the server every 5 minutes
- The server identifies you via
auth.uid()— no user ID is sent from the client - Row-Level Security: you can only ever see your own data
- View your stats on your Account dashboard
Your API Data Stays Local
- Requests, responses, and logs are saved as plain JSON in
.active8/results/ - Credentials are stored in your OS-level credential manager (Keychain / Windows Credential Manager)
- Nothing leaves your machine
Need Zero Telemetry?
Available by arrangement — contact hello@dbmn.io.
For the full legal privacy policy, see our Privacy Policy.