Skip to content


Security.

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.

Your connected account

Protected credentials

Encrypted at rest.
Scoped to your workspace.

Access at runtimeReviewable history
How a connection supports your process.

From sign-in
to execution.

Your credentials stay protected through the connection lifecycle. Each process gets the access it needs when it runs.

  1. Connect your account

    For OAuth connections, sign in through the provider’s own page. Your password stays with the provider.

  2. Keep credentials encrypted

    API keys and tokens are encrypted at rest using Google Cloud KMS and scoped to their workspace and configuration.

  3. Use access only when needed

    Secrets are decrypted in memory when a process needs them. Refresh tokens stay protected while fresh access tokens are supplied at runtime.

Control access.
See the activity.

Keep your team’s connections, processes and history together in the workspace that owns them.

Workspace access

Workspace-based isolation and role-based access control keep access tied to the workspace that owns the work.

Reviewable activity

Review process runs and AI-assisted actions in your workspace history. See what executed and when it ran.

Connection control

Choose which accounts to connect. Remove connected secrets and configurations from your workspace when you no longer need them.

Defined retention

Execution outputs, run history and account content have retention periods based on their purpose. The published policies explain retention and deletion.

Independently verified.

Neudash has completed independent ESOF Shield verification at CASA Tier 3.

Read the verification details
ESOF Shield Verified and Secured

The details,
in writing.

Review the published controls and data-handling terms for the tools and information you plan to connect.

Frequently asked questions

How are my credentials protected?

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.

Is my data encrypted in transit?

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

How is access separated between workspaces?

Neudash uses workspace-based isolation and role-based access control. Secrets are bound to the workspace and configuration they belong to.

Can I review work carried out by AI?

AI-assisted actions are recorded in workspace history so your team can review what happened. Run history also records process execution.

How can I remove my data?

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

Who can answer a security question about my workflow?

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

Let’s talk about
your requirements.

Tell us which tools you use and what data your process needs to handle.

Contact Neudash