Workspace access
Workspace-based isolation and role-based access control keep access tied to the workspace that owns the work.
Your tools. Your data.
Protection built into the process.
Encrypted credentials, workspace access controls and activity you can review. Know how your connections and business data are handled.
Encrypted at rest.
Scoped to your workspace.
Your credentials stay protected through the connection lifecycle. Each process gets the access it needs when it runs.
For OAuth connections, sign in through the provider’s own page. Your password stays with the provider.
API keys and tokens are encrypted at rest using Google Cloud KMS and scoped to their workspace and configuration.
Secrets are decrypted in memory when a process needs them. Refresh tokens stay protected while fresh access tokens are supplied at runtime.
Keep your team’s connections, processes and history together in the workspace that owns them.
Workspace-based isolation and role-based access control keep access tied to the workspace that owns the work.
Review process runs and AI-assisted actions in your workspace history. See what executed and when it ran.
Choose which accounts to connect. Remove connected secrets and configurations from your workspace when you no longer need them.
Execution outputs, run history and account content have retention periods based on their purpose. The published policies explain retention and deletion.
Neudash has completed independent ESOF Shield verification at CASA Tier 3.
Read the verification detailsReview the published controls and data-handling terms for the tools and information you plan to connect.
OAuth tokens and API keys are encrypted at rest using Google Cloud KMS. Secrets are decrypted only in memory when a process needs them. Refresh tokens are not exposed to process code.
Data sent between you and Neudash uses HTTPS with TLS 1.3. Application databases are encrypted at rest by Google Cloud. The security policy explains the scope of these controls, including transfers within private networks. Read the security policy
Neudash uses workspace-based isolation and role-based access control. Secrets are bound to the workspace and configuration they belong to.
AI-assisted actions are recorded in workspace history so your team can review what happened. Run history also records process execution.
You can remove connected secrets and configurations from your workspace. Account closure and content deletion follow the retention periods and exceptions in the published privacy policy. Export any content you need before closing your account. Read the privacy policy
Contact Neudash with the tools you plan to connect and the data your process will handle. For vulnerability reports, follow the reporting instructions in the security policy. Contact Neudash
Tell us which tools you use and what data your process needs to handle.
Contact Neudash