Security at Aura Manager
A practical overview of how Aura handles creative work, uploads, memory, and support.
Our security promise
Aura is built so creators can bring rough ideas, scripts, lyrics, images, audio, PDFs, and project notes into one workspace. We keep the promise simple: your account context should stay tied to your account, support access should be intentional, and public claims should match what the product actually does.
Account-scoped memory
Aura uses saved notes, preferences, ratings, and Pro tool context inside the user's own account. It is not designed to share one user's creative history with another user.
Protected sign-in
Aura uses managed authentication and session cookies so users can sign in without storing a password inside Aura Manager.
Private creative context
Prompts, uploads, notes, and generated outputs are used to provide the requested workspace experience, including chat, PDFs, storyboards, and creative planning.
Limited support access
Feedback and support requests should include only the context needed to solve the issue. Human support can review submitted support messages and screenshots when the user chooses to send them.
Safe product behavior
Aura should refuse harmful requests and avoid instructions that enable violence, abuse, fraud, malware, or other unsafe behavior.
Operational safeguards
We use platform controls, environment variables, server-side checks, usage limits, and audit-friendly workflows to reduce accidental exposure and abuse.
What users can control
- Save or delete notes they no longer want in their workspace.
- Start a new chat when they want to reset a conversation.
- Choose what references to attach before asking Aura to analyze them.
- Send feedback or request human support when product help is needed.