Privacy Policy
Last Updated: May 23, 2026. At DataFuse, we are dedicated to protecting your data, code, and system credentials through advanced structural decoupling.
1. Introduction & Scope
DataFuse ("we", "us", "our") operates the developer integration network and platform located at datafuse.xyz. This Privacy Policy details our practices concerning data collection, usage, sharing, and retention when you access our services, utilize our CLI tools, integration compilers, and SDK components.
We design our platform under a strict "privacy-by-design" framework, striving to process the absolute minimum amount of personal identifiable information (PII) required to render our service.
2. Cryptographic Vault Decoupling
Architectural Isolation Commitment
Unlike traditional agentic frameworks that ingest your external API keys, service accounts, and database credentials directly into large language models (LLMs) or client-side stores, DataFuse utilizes a cryptographically decoupled architecture.
Your credentials are stored inside a secure isolated key-management vault. Credentials are never written to logs, never loaded into LLM prompts, and are injected exclusively at the ephemeral gateway proxy layer. We strip authorization headers before returning responses to client-side runtimes.
3. Data We Collect
We only collect data that is strictly necessary to run, monitor, and billing-verify the DataFuse services:
- Account Information: Name, Email, GitHub profile attributes (when using GitHub OAuth login), and Stripe payment reference identifiers.
- Developer Configurations: YAML configuration files, API endpoints definitions, and routing integration rules compiled in our workspace.
- Gateway Metadata: Non-sensitive invocation counts, token length counts, latency data, error rates, and API system identifiers (e.g., "Slack", "Salesforce").
- Application Logs: Technical error dumps and application crash stacks, completely stripped of customer data payloads and API secrets.
4. How We Use Data
DataFuse leverages collected data solely for the following functional purposes:
- To compile, authenticate, and securely execute your integration connections.
- To display usage statistics, billing tier reports, and performance charts in your console workspace.
- To maintain, patch, and optimize the gateway performance and response times.
- To prevent abuse, credential scanning, and unauthorized access to your account.
We will never sell, lease, or monetize your account details, usage logs, or integrations profiles to advertising systems or third-party brokers.
6. Technical Security Measures
We employ robust physical, administrative, and technical controls to safeguard customer workspaces:
- Encryption: All databases, vaults, and configurations are encrypted at rest with AES-256-GCM. Active network communication utilizes enforced TLS 1.3 tunnels.
- Access Control: Zero-Trust access model. We enforce multi-factor authentication (MFA) and granular IAM rules on all internal operations infrastructure.
- Vulnerability Management: Continuous dependency scanning, quarterly third-party external penetration testing, and real-time WAF filtering.
7. Your Rights (GDPR & CCPA)
Regardless of geographical location, DataFuse extends standard data control capabilities to all registered developers and teams:
- Right of Access: Request a export of all active profile logs and workspace data we hold.
- Right of Rectification: Edit or modify account emails and developer parameters directly through the dashboard.
- Right of Deletion ("Right to be Forgotten"): Instantly trigger total removal of credentials and account info.
- Non-Discrimination: We do not charge different rates or limit functionality if you select to exercise privacy choices.
8. Retention & Deletion
We store your account parameters and configurations for as long as your developer organization remains active on DataFuse.
Upon account termination or manual deletion, credentials inside our decoupled hardware vault are purged immediately (within seconds) from production memory. Associated diagnostic database parameters and account records are fully expunged within 30 business days, and from cold backups within a maximum of 90 days.
9. Changes & Contact
We may revise this Privacy Policy periodically to match compliance improvements or platform shifts. We will notify major updates to developers through their console dashboard alerts.
For questions regarding this policy, security vaults, or data processing agreements, contact our Data Protection Officer at: