AuraMind
Try Voice ↗

Security

Clear boundaries before broader automation.

AuraMind uses practical security and human-approval controls appropriate to each workflow. This page describes an approach, not a certification or a guarantee.

Access

Least necessary scope

Start with the minimum data, tool permissions and environments needed to reproduce or build the workflow.

Action

Human gates

Keep approval around financial, legal, safety-sensitive, identity-bearing or otherwise high-impact actions.

Evidence

Inspectability

Record the inputs, tool calls, outputs and decision state needed to investigate a failure without exposing unnecessary private data.

Public website

Current technical controls

  • HTTPS and transport security through the hosting platform
  • Content Security Policy, content-type, referrer and browser-permission headers
  • Microphone access is requested only when you start a voice session; camera and geolocation are disabled
  • Form honeypot and provider-side submission handling
  • No tracking cookies and no external analytics

Report an issue

Share the minimum needed to reproduce

Email contact@aura-mind.de with the affected URL, the observed behaviour, the impact and safe reproduction steps. Do not include active credentials, sensitive personal data or other users' data. AuraMind does not currently claim ISO, SOC 2 or any other security certification.