Security

Embarko runs other people's code. That shapes everything on this page: the platform has to keep your app's data safe from everyone else, keep every other app's code away from yours, and keep the deploy path from becoming a way in. For the legal commitments behind these controls, see our Terms, Privacy Policy, and DPA.

Isolation between apps

• Every app runs in its own isolated environment, with its own filesystem and its own persistent volume.
• An app can reach its own storage under DATA_DIR and nothing else. It has no path to another customer's app, data, or secrets.
• Resource ceilings per app keep one workload from starving the others, and a crashing app restarts without touching its neighbours.

Encryption and secrets

• All traffic is served over HTTPS, on *.app.embarko.ai and on connected custom domains, with certificates issued and renewed for you.
• Data is encrypted in transit, and encrypted at rest by our storage provider.
• Environment variables and app secrets are encrypted at rest under a separate key, and are exposed only to your own app's runtime.
• Access to production infrastructure is limited to the people who need it, and is logged.

Deploy tokens and accounts

• Tokens are company-scoped. A deploy token authenticates as a company, so a deploy lands under that company's apps no matter who or what ran it.
• Tokens are stored hashed and are individually revocable, so a leaked one can be rotated without disturbing the rest. Revoke it and every subsequent deploy with it fails with unauthorized.
• There is no password to breach. Sign-in is a one-time code sent to your email or phone and verified by our authentication provider.
• App names are unique platform-wide, so nobody else can publish onto a subdomain you already hold.

The deploy path

• Deploys go to ship.embarko.ai over HTTPS and require a valid token before any build begins.
• Uploaded source is checked before we build it. Patterns we know cannot work — an app calling window.storage, for instance — are rejected up front with 422 rather than half-built.
• Builds run in a throwaway environment, separate from the environment your app eventually runs in.
• Every deploy is recorded — which token, which version, what the build did — so an unexpected deploy is traceable.

Your app's own security

We secure the platform; your app's own behaviour is still yours. Embarko can give you HTTPS, isolation, backups, and a login building block, but it cannot make your app check authorisation correctly or stop it from leaking its own data. Treat the app your agent generated as code you are responsible for, and keep anything you cannot afford to lose in source control.

Backups and deletion

• Automatic backups are included from the Creator plan up; see pricing for what each plan covers.
• Backup frequency and how far back you can restore: [schedule and retention].
• Deleting an app permanently removes its instance, its stored data, and its backups. So does deleting the company that owns it.
• Closing an account deletes its apps and their data within [deletion window].

Cookies and analytics

• Our cookies exist for sign-in sessions and for the analytics described below. We do not run advertising cookies.
• Our marketing pages and console load Google Tag Manager for product analytics — page views and coarse device and location data.
• The analytics we show you about your live app use coarse request metadata; we do not hand raw visitor IP addresses to app owners.

Infrastructure and sub-processors

Embarko is built on third-party infrastructure for compute, storage, authentication, email, and payments. The current list, with purposes, locations, and our change-notification commitment, is maintained in the DPA.

Reporting a vulnerability

Email security@embarko.ai with what you found and how to reproduce it. We will acknowledge your report within [acknowledgement window] and keep you posted while we investigate. While you are testing, please stay within your own apps and account — do not access anyone else's data, and do not degrade the service for others. [state whether a bug bounty is offered].

Security reviews

Running a vendor assessment? Email hello@embarko.ai and we will work through your questionnaire. Current certifications and audit reports: [e.g. SOC 2 status, or "none yet"].