Account and Governance

Security and Data Handling

Security, privacy, and isolation are foundational to how DeplAI builds, runs, and stores applications. This guide explains how your projects, source code, and credentials are handled from a customer perspective.

Page

---

Build isolation and temporary environments

When DeplAI creates or updates an application:

Isolated execution: Application builds run in isolated temporary environments. Each build executes independently, preventing cross-tenant or cross-project data leakage.
Disposable build runtimes: Temporary build environments are disposable. Once a build completes or a preview is stopped, the execution runtime is decommissioned.
No production credentials: Application build environments do not receive or store production deployment credentials, cloud account root keys, or sensitive hosting secrets.

---

Source storage and durability

DeplAI cleanly separates temporary execution runtimes from permanent application records:

Independent source storage: Saved application source is stored separately from temporary build environments. When a preview container stops or is torn down, your code, version history, logs, and checks remain intact.
Version integrity: Each saved version represents an exact snapshot of your application at a specific milestone. You can browse, diff, or download code for any saved version at any time.
Project scoping: Generated code, saved versions, and conversation threads belong to your project and are accessible only to authorized accounts and organization members.

---

Data handling in previews

Demonstration data: When building applications that require records (such as orders, appointments, or user lists), DeplAI may generate sample demonstration data so you can test realistic screens immediately.
Separate from production data: Demonstration data exists strictly for preview and testing purposes within the temporary environment. It does not become production customer data. When you export your code and host the application, you connect your own live, production data stores.

---

Authentication and identity

User sign-in: DeplAI uses trusted identity providers (such as GitHub) for user authentication. Your password is never seen or handled by DeplAI.
Role-based access control: Organization memberships and permissions ensure that only designated team members can view, edit, or manage billing for a given project.
Session security: Dashboard access is protected through secure, encrypted session tokens.

---

Exporting and owning your code

Full exportability: You can download the complete source code for any saved application version at any time using Download code.
Clean codebases: Downloaded archives contain only the application source and configuration needed to run the project independently outside DeplAI, free of proprietary runtime agents or temporary build artifacts.

Account and Governance

Security and Data Handling

Page

---

Build isolation and temporary environments

When DeplAI creates or updates an application:

Isolated execution: Application builds run in isolated temporary environments. Each build executes independently, preventing cross-tenant or cross-project data leakage.
Disposable build runtimes: Temporary build environments are disposable. Once a build completes or a preview is stopped, the execution runtime is decommissioned.
No production credentials: Application build environments do not receive or store production deployment credentials, cloud account root keys, or sensitive hosting secrets.

---

Source storage and durability

DeplAI cleanly separates temporary execution runtimes from permanent application records:

Independent source storage: Saved application source is stored separately from temporary build environments. When a preview container stops or is torn down, your code, version history, logs, and checks remain intact.
Version integrity: Each saved version represents an exact snapshot of your application at a specific milestone. You can browse, diff, or download code for any saved version at any time.
Project scoping: Generated code, saved versions, and conversation threads belong to your project and are accessible only to authorized accounts and organization members.

---

Data handling in previews

Demonstration data: When building applications that require records (such as orders, appointments, or user lists), DeplAI may generate sample demonstration data so you can test realistic screens immediately.
Separate from production data: Demonstration data exists strictly for preview and testing purposes within the temporary environment. It does not become production customer data. When you export your code and host the application, you connect your own live, production data stores.

---

Authentication and identity

User sign-in: DeplAI uses trusted identity providers (such as GitHub) for user authentication. Your password is never seen or handled by DeplAI.
Role-based access control: Organization memberships and permissions ensure that only designated team members can view, edit, or manage billing for a given project.
Session security: Dashboard access is protected through secure, encrypted session tokens.

---

Exporting and owning your code

Full exportability: You can download the complete source code for any saved application version at any time using Download code.
Clean codebases: Downloaded archives contain only the application source and configuration needed to run the project independently outside DeplAI, free of proprietary runtime agents or temporary build artifacts.