KMS-backed encryption
Every password, API key, and access token is encrypted using envelope encryption backed by Google Cloud KMS.
Security
How Neudash protects credentials and business data
Secrets stay encrypted at rest, are decrypted only when a workflow needs them, and activity stays tied to the workspace that owns it.
Protect credentials, limit retained data, and keep activity reviewable.
Neudash decrypts secrets only in memory when a workflow needs them and keeps access scoped to the workspace and configuration that own them.
It is built to move data between systems, not warehouse more of it than needed. Neudash has completed ESOF Shield verification at CASA Tier 3.
At a glance
What this product is for
Neudash protects credentials and business data by encrypting secrets at rest with Google Cloud KMS, decrypting them only in memory when a workflow needs them, scoping access to the workspace and configuration that own them, and keeping activity reviewable in workspace history. Neudash is built to move data between systems, not warehouse more of it than needed.
Best for
Teams moving sensitive customer, finance, or operational data between systems and needing clear workspace-level control.
Why teams switch
Secrets encrypted at rest, runtime-only access, workspace-scoped controls, reviewable history, published retention windows, and ESOF Shield verification at CASA Tier 3.
Review next
Features
How connected credentials are handled
When you connect an account to Neudash, the credential stays encrypted at rest, scoped to the workspace and configuration that own it, and decrypted only when a workflow needs it.
Provider-controlled sign-in
OAuth sign-in happens through the provider’s own flow. Passwords are entered with the provider, not into Neudash.
Fresh tokens at runtime
Refresh tokens stay protected. Workflows receive fresh access tokens only when the API call needs them.
Security
Connection, access, and review controls
You choose what connects where, and you can review, pause, or disconnect anything at any time. Public-facing workflows deserve an extra review pass because their output is visible outside your workspace.
Workspace-scoped access
Workspace-based isolation and role-based access control keep credentials tied to the workspace and configuration that own them.
Run history stays reviewable
Run history lets your team review what executed, when it ran, and what changed.
Source systems keep the records
Neudash moves data between systems and keeps the minimum data needed to run the workflow.
AI-assisted work stays visible
AI-assisted actions are recorded in workspace history so your team can review what happened.
Retention and removal
Connected secrets and configurations
Each connection is added by someone in your workspace, and connected secrets and configurations can be removed at any time.
Retention and deletion windows
If you delete your account, account content is deleted within 60 days, purged from active systems within 30 days, and removed from backups within 90 days according to the retention policy.
Public-facing workflow review
Public-facing workflows deserve an extra review pass because their output is visible outside your workspace.
Review next
Published policies and a route for workflow-specific questions.
Read the security policy
Use the published policy for the current control set, verification details, and retention guidance.
Read policyRead the privacy policy
Review the privacy policy when the question turns to data handling, retention, and deletion timelines.
Read policyAsk a workflow-specific question
Use the contact page when your review depends on a specific workflow, integration, or data-handling path.
Contact NeudashFAQ
How does Neudash protect my credentials?
All OAuth tokens and API keys are encrypted at rest using Google Cloud KMS. Refresh tokens are never exposed to process code. When your automation needs to call an API, Neudash injects a fresh access token at runtime without revealing the underlying credentials.
How is AI-assisted work controlled in Neudash?
Neudash follows a least-data approach. Connected credentials stay encrypted at rest, secrets are decrypted only in memory when needed, and AI-assisted actions are recorded in your workspace history so your team can review what happened.
How is access separated between workspaces?
Neudash uses workspace-based isolation with role-based access control. Secrets are cryptographically bound to the workspace and configuration they belong to, and they are only decrypted at the moment an automation needs them.
How can I remove my data from Neudash?
You can delete connected secrets and configurations from your workspace at any time. If you delete your account, account content is deleted within 60 days. Deleted data is purged from active systems within 30 days and from backups within 90 days according to the retention policy.
Where can I review policies or ask a specific security question?
Review the security policy and privacy policy for the published controls and retention details, then use the contact page if you need an answer about your specific workflow or data-handling setup.