Security Policy
How Connect and Konnect protect credentials, access and spend, and how to report a flaw.
Effective: August 1, 2026 | Last updated: August 1, 2026
support@dashapi.ai1. Overview
Connect sits between your agents and many third-party providers, so it holds credentials and decides what a key may do. This policy describes the controls we build into Connect and run in Konnect. The company-wide Security Overview covers the wider organization.
2. Credential isolation
Provider credentials are stored encrypted and injected on the server when a call runs. They are never sent to your agent, shown again in the portal after entry, or written to logs. Rotating a credential creates a new version without exposing the old one.
3. Access and grants
- Browsing the catalog grants nothing. Each API key receives only the connections and resources you assign.
- Write, destructive and spend actions require an approval bound to that specific action.
- Owners and billing managers are separated. Billing roles require multi-factor authentication.
- Keys can be named, rotated and revoked at any time.
4. Spending controls
Calls draw on a prepaid balance and are refused at zero. Concurrent calls cannot overspend it. You can set daily and monthly limits per connection, so a runaway agent hits a ceiling instead of your budget.
5. Cache separation
Public-data answers can come from a cache shared across customers. Answers obtained with your own provider keys never enter it. They are cached for your organization only, and private resources such as exclusion lists and bulk jobs stay owned by the creating organization.
6. Audit records
Every execution is recorded in an append-only audit trail: who called, which operation, which provider answered and what it cost. Retrieval of audit records is restricted.
7. Rate and abuse protection
Per-provider rate and concurrency limits are enforced in the database, so a burst across workers cannot exhaust a supplier's quota. Each application also has a request throttle at the edge.
8. Writes and uncertain outcomes
If a timeout may have occurred after a provider acted, Connect records an uncertain outcome and reconciles it. It does not blindly retry a write.
9. Open source
The Connect engine is open source, so you can read how credentials, routing and billing are handled and review changes in the repository.
10. Incident response
We investigate suspected incidents promptly, contain them, and notify affected customers without undue delay and as the law requires.
11. Reporting a vulnerability
Email support@dashapi.ai with the details and steps to reproduce. Please give us reasonable time to fix the issue before disclosing it, and do not access data that is not yours or degrade the service while testing. We will acknowledge your report and keep you updated.
12. Your side of the responsibility
- Keep API keys out of repositories and client-side code.
- Give each key the narrowest access it needs and set spending limits.
- Revoke keys you no longer use or think are exposed.
- If you self-host Connect, you secure your own deployment, database and secrets.
13. What we do not claim yet
We do not claim a third-party security certification for Konnect at this time. Hosting regions across North America, Europe, Asia and Latin America are being rolled out, and choosing a region for your data is not yet available. The public MCP adapter is built but not switched on until its authorization model is settled. Many provider operations have been tested against fixtures, with live verification continuing.