MacOrb / Trust & transparency

Privacy

Last updated: September 18, 2026

What MacOrb holds

• Your GitHub user id and login, from signing in with GitHub.
• A signed sign-in cookie carrying your MacOrb user id and GitHub login. It is HttpOnly and expires after seven days. The MacOrb CLI can use the same token.
• Your encrypted Amp key, and your encrypted GitHub token if you store one. See Security for how they are protected.
• A record of each session: its state, instance and runner identifiers, the repository you named, timestamps, the lifetime you asked for, and why it ended.
• Measured Mac minutes, and operational logs carrying request and account identifiers and events such as “a credential was stored”. Logging is written to redact secret values.

How it is used and shared

MacOrb uses this to sign you in, start and stop Macs, run the Amp runner, clone the repository you named, show your usage, and troubleshoot the service. Cloudflare hosts the application and the database. Namespace runs the Mac. Amp authenticates and runs the agent. GitHub handles sign-in and repository access. Each receives what its part of the service needs, and no more.

MacOrb does not sell this information and does not use it for advertising.

Sign-in and repository access

GitHub sign-in asks only for public profile access (read:user). It identifies your MacOrb account. It does not authorize repository access and is never used to clone.

Cloning uses the separate GitHub token you choose to store. If you store no token, MacOrb clones nothing.

Cookies and page requests

There are two cookies: the sign-in cookie, and a short-lived cookie that protects the GitHub sign-in round trip. Neither is an advertising cookie, and these pages carry no third-party analytics.

The console loads its interaction script from Cloudflare's cdnjs service, so your browser makes a request there.

Deleting your account

The account page lets you sign out and delete your account. Deleting removes your stored Amp key and GitHub token and your account record.

Session and usage rows stay as operational history, because they are what MacOrb bills and audits against. How long they are kept is not yet decided. Deleting your MacOrb account does not revoke anything at Amp or GitHub, so revoke credentials there as well.

Signing out clears the cookie in that browser. The session token is stateless, so a copy already saved elsewhere, such as by the CLI, keeps working until it expires.

Your choices

You can sign out, stop a running Mac, replace or remove either stored credential, and delete your account. Stopping a Mac deletes nothing from MacOrb's records. Read Security before rotating a credential a running session is using.

Who holds your data

MacOrb is operated by Fathima Rinosha Abul Kalam, trading as FZMZ Labs, in the Netherlands, whose law governs these terms.

To ask a privacy question, or to ask for a copy of your data or its deletion, write to us. Never include keys, tokens or cookies in the message.

Support: support@macorb.dev.