Your buddy. Your boundaries.

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, and keeps a short list of your Emblas (name, web address, app version, last seen) so you can open them. Your Embla’s workspace reaches it through its own Cloudflare Tunnel: your Embla checks your session on every request, and chats and files are loaded from it only while you have the page open. Like the rest of this site, that traffic passes through Cloudflare’s network. Your browser remembers small view preferences, such as the last page you opened. No payment processing or software downloads are offered. Fonts and product assets are served with the site.

Google sign-in.

If you sign in with Google, Google shares your email address and basic profile information (name and profile picture) with us through the openid, email, and profile scopes. We use this data only to create and secure your Emberbuddy account. It is stored by our authentication provider (Supabase) and is never sold. It is shared only with Supabase as needed to operate sign-in, and with Google as part of the OAuth flow. To review or delete your account data, contact us through the Support page.

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.