Privacy

How AOZUMI handles your information.

Last updated: October 9, 2026

AOZUMI turns code into running apps and controls who can open them. This page explains what information that involves, where it goes, and what you can do about it. It describes the service during the beta and will change as the product does.

Your account and workspace

You sign in with GitHub. We ask GitHub only for your public profile and email address, and store:

• your GitHub user ID and username, display name, avatar URL, and email address if GitHub shares one;
• a sign-in session, stored as a hash of its token and valid for 30 days;
• your workspaces, their members and roles (owner, admin, builder, viewer), and pending invitations, which include the invitee's email and expire after 7 days;
• an audit log of actions in each workspace, such as deploys, access changes, key creation and CLI logins, with who did them and when;
• answers you give during onboarding, and support requests you send us, including any diagnostics you attach.

Your repositories and source code

Repository access goes through the AOZUMI GitHub App, and only for the accounts and repositories you choose when you install it. The App asks for read access to repository contents and metadata. Optional features, such as pull-request previews and preview status checks, may need extra GitHub permissions. GitHub asks the installation owner to approve those first.

When you deploy, AOZUMI downloads a snapshot (a tarball) of the chosen commit from GitHub and reviews it before building. Builds run on Amazon Web Services, in Lambda MicroVM builders and ECS/Fargate tasks. Source snapshots and build output are kept in private Amazon S3 buckets. We keep build artifacts so an app that went to sleep can wake without rebuilding, and so you can roll back to a recent release.

Builds, app runtimes, artifacts and databases currently run in AWS regions us-east-1 (N. Virginia, United States) and ap-south-1 (Mumbai, India).

Secrets and environment variables

• Secret values are encrypted with AES-GCM before we store them. After you save a secret, the console shows only its name.
• To run your app, we decrypt the values and hand them to its runtime. For container apps on AWS, that is through AWS Secrets Manager.
• Deployment logs shown in the console and to agents have known secret values redacted.
• Preview deployments get only their own environment's variables. Production secrets are never loaded into previews.

Deployed apps and their visitors

• Who can open an app. Each app is private (only people you approve), team (members of your workspace) or public. You can also invite people by email, approve access requests, or create share links. An access request stores the requester's email, name and a hash of their IP address. It expires after 7 days.
• Share links. A share link lasts 1 day, 1 week (the default) or 30 days, or never expires automatically if you choose that. You can revoke a link at any time. A share link gives access to that app only, not to your workspace or repository.
• Custom domains. If you connect your own domain, we register it with Cloudflare for SaaS, which routes its traffic and issues its TLS certificate.
• Edge cache. Static pages of public apps are cached in Cloudflare's data centres: HTML for about 30 seconds and fingerprinted files for up to a day. Responses from private and team apps are never stored in that shared cache.
• Usage metering. For each app and day we count requests, failed responses, response time, bytes in and out, runtime seconds and failed wakes. We use these totals for the usage and cost views, quotas and abuse prevention. They are not a record of individual visitors.
• Sleep. Server apps go to sleep when they have no traffic for a while, and wake on the next request.
• Health checks. If you turn them on, AOZUMI checks eligible public apps every five minutes and keeps a daily summary.

Your app's own data, and what it collects from its users, belongs to you. You are responsible for telling your users about it.

The CLI and agents

• aozumi login uses a browser approval flow. The CLI shows a code that is valid for 10 minutes. You check it in the browser and approve or deny it. The resulting key works in one workspace only, cannot be used as an agent key, and is revoked when you run aozumi logout.
• aozumi deploy uploads only your built output folder, never the repository. For a plain folder site, it publishes only web files and skips dotfiles, node_modules and key files.
• Agent keys connect AI agents to AOZUMI over MCP at /mcp. You create them in your profile. Each one is limited to one workspace, acts with your permissions, is stored as a hash, and can be revoked at any time.

The Foldy assistant

When you ask Foldy a question in the console, we send the question to OpenAI with a limited summary of your workspace. The summary can include app names, frameworks, deployment statuses, recent activity and the names (never the values) of required environment variables. We ask OpenAI not to store the request. Answers to repeated questions may be cached at Cloudflare for five minutes. Some suggestions, such as next steps, are generated without OpenAI.

Managed Postgres

If you add a managed Postgres database, it runs on a shared AOZUMI-operated Postgres host in AWS ap-south-1 (Mumbai). Its connection string is saved to your app as an encrypted secret. During the beta:

• Backups are taken every 6 hours. Every backup is kept for 48 hours, then one per day is kept for up to 7 days.
• Manual backups (up to 3) are kept for 14 days.
• When you delete a database, you can choose to keep a final backup for 14 days.
• Backups are stored in a private Amazon S3 bucket.

Analytics and cookies

On aozumi.dev, we use PostHog (United States) for product analytics. We send page views with the path and parameter names only (never their values), a small set of product events, and browser and device details. Automatic click capture is off. If session recordings are enabled, every form input is masked. PostHog stores its own identifier in your browser. We do not add analytics to the apps you deploy.

AOZUMI sets these cookies:

Who helps us run AOZUMI

We share information with these providers only as needed to run the service:

AOZUMI does not currently send email.

How long we keep information

• Sessions: 30 days. CLI login codes: 10 minutes. Invitations and access requests: 7 days unless they are accepted.
• Pull-request previews expire 7 days after the last update to the pull request, or when it closes.
• Files from older static releases are removed after 7 days, but the 5 newest releases and anything still live are kept for rollback.
• App task logs in AWS CloudWatch are set to expire after 14 days.
• Managed Postgres backups are kept for the periods listed above.
• Workspace records, such as apps, settings, the audit log and usage totals, are kept while the workspace exists.

Deleting your account

You can delete your account from your profile. Deleting it removes the hosting for apps in workspaces that only you belong to, then deletes those workspaces and your account record. If you are a member of someone else's workspace, or a workspace you own has other members, sort that out first. Records in other people's workspaces, such as audit entries showing your name, may remain. Backups and provider logs expire on their own schedules.

Your choices

You can revoke CLI and agent keys, remove the GitHub App or limit its repositories, change who can open each app, revoke share links, and delete apps, databases or your account. For any other request about your information, contact us. We may need to verify your identity before acting.

Contact

For privacy questions, email hello@aozumi.dev. See also our Terms.

Reporting a security issue

Email security@aozumi.dev. Our contact details are also published at /.well-known/security.txt.