Privacy & data handling

What we collect

• • Account identifiers (email, organization name)
• • Usage metadata (tool runs, timestamps, status)
• • Operational logs for debugging, reliability, and security

Tool data & execution

Tool inputs and outputs are processed only for the duration of execution. By default, Dwizi does not persist tool payloads or execution results.

Execution metadata (such as timestamps, status, and runtime identifiers) may be logged for reliability, debugging, and abuse prevention.

What we don’t do

• • We don’t sell or monetize user data.
• • We don’t train AI models on your code, inputs, or outputs.
• • We don’t inspect tool payloads except when required for security or abuse prevention.
• • We don’t share customer data with third parties for advertising or profiling.

Data isolation

Each organization’s data is logically isolated. Tools, execution metadata, and access tokens are scoped per organization and cannot be accessed across organizational boundaries.

Data retention

We retain operational logs for a limited period to keep the platform reliable and secure. You can request deletion of your account data at any time.

Our role

Dwizi operates as infrastructure. You control what code runs, what data is processed, and who can access it. Dwizi does not act on your behalf beyond executing tools as configured.

Contact

Questions? Contact us.