Privacy & control
Your buddy. Your boundaries.
A personal agent needs more than useful tools. It needs a clear relationship with your files, your accounts, and you.
Your Embla
Approved local files
Agent workspace
Your model provider
Cloud reasoning
Provider data policies apply
Back to you
Review the work
Approve sensitive actions
Our design principles
Local ownership.
Honest about the cloud.
Files are planned to stay on your device by default. When your agent uses a cloud model, relevant context leaves the device to be processed by that provider. Local storage does not mean every part of a task happens locally.
Access should be intentional.
You should be able to choose folders, limit tools and integrations, review activity, and pause work. Sending, purchasing, deleting, publishing, and changing security settings need understandable approval boundaries.
Secrets need their own protection.
Secure credential storage, isolated tools, signed updates, and recovery are part of the engineering plan. These are design requirements; we do not claim they have been implemented or independently verified.
What this website does today.
This website uses Supabase for authentication and account security. The earlier test dashboard, device relay, software downloads, and stored device/provider records have been retired. No agent, device control, analytics, or payment processing is currently offered by the site. Fonts and product assets are served with the site.
Before launch.
A complete privacy notice will need to describe the actual services, data flows, retention, providers, and account rights before customer data is collected. This page describes the current product approach.
A little space for what’s next
An idea taking shape.
A place to begin.
Embla is in development. Account access and security settings are available today.
View your account