Privacy

What we store

• Account data: Email, and an optional name from Settings, GitHub, or Google. An optional GitHub or Google link, with the email that provider shares. Session tokens. The email each login code is sent to. Emails you invite to a project.
• Optional MFA (TOTP) enrollment metadata when you enable two-factor authentication.
• Folder, guest and server tokens (hashed), labels, expiry, and last use.
• Project metadata: project, context, and variable names, context protection, machine labels and public keys.
• Value ciphertext, context keys sealed to public keys, and your private key in separately encrypted copies: one wrapped with your Vault password and, if you set up a recovery code, one wrapped with that code. We do not store Vault passwords, recovery codes or readable values.
• Backup records: label, value count, and date. The backup file itself stays with you. A restore opens it in your browser or CLI and uploads names and ciphertext.
• Activity and security events: actions such as project created, variable set, CLI command used (command name and counts), login, and access request approve or deny. Metadata only, never values.
• Network metadata: IP address, country, and user agent on browser sessions, tokens, and security events. IP address and user agent when a guest project is created. Country on activity events. The IP of a server token read refused by its allowlist, on that activity event. The project owner sees it in Activity. The country your account signed up from. The user agent of each remembered browser. The name of each passkey. It starts as the browser and system it was added on, and you can rename it. The IP or CIDR allowlist you set on a server token.

What we never store

• Your Vault password.
• Your recovery code.
• Readable values.
• Values in emails or webhook payloads (names and metadata only).
• The command line after getmyenv run -- (your app command).

Runtime

Values are set as environment variables before your process starts. That works for any language that reads the environment (for example Node, Python, Ruby, Rust, Go, PHP, Java, .NET, and shell).

Why we store it

To run the product: authenticate you, deliver ciphertext to authorized clients, show your activity, and understand which CLI commands are used so we can improve the product. Access and security events also support account safety.

Site analytics

On production marketing pages (home, docs, guides, about, brand, privacy, terms, contact, changelog), we load Google Tag Manager (container GTM-KNRWPCJX), which can run Google Analytics 4 (measurement ID G-566S2Z04B0). We use this to understand traffic: pages viewed, referrals, and rough geography.

The dashboard, sign-in, CLI sign-in, and claim pages do not load it. Claim codes and session IDs are removed from reported URLs.

What may be collected includes:

• Page URL and path, referrer, and similar navigation data.
• Device and browser information.
• Approximate location derived from IP address.
• Measurement events Google Analytics provides for site usage.

Google processes this data under Google's terms for Tag Manager and Analytics. We do not sell it.

Cookies

First-party cookies and related browser storage we use. On getmyenv.com the sign-in cookies carry the __Host- prefix (for example __Host-getmyenv_session).

• getmyenv_session - signed-in session (HttpOnly). Up to 14 days. It ends after 3 days without use.
• getmyenv_mfa_pending - short-lived cookie while MFA verification is in progress (HttpOnly).
• getmyenv_admin_session - parked admin session during support access (HttpOnly).
• getmyenv_device - remembers this browser so it can skip the email login code for 30 days (HttpOnly). Set only when you check Remember this browser. MFA still applies when enabled.
• getmyenv_oauth_state / getmyenv_oauth_verifier / getmyenv_oauth_trust - GitHub and Google sign-in checks and your trust choice (about 10 minutes).
• getmyenv_auth_hint - short-lived, readable hint of the last signed-in email after OAuth (cleared when the dashboard loads).

This browser can also store the last email you signed in with in local storage on your device.

Google may set its own cookies or similar storage for Tag Manager and Analytics measurement.

Retention and deletion

Account and project data stay while your account exists. Deleting your account removes the projects you own, their ciphertext, backup records, webhooks, and activity, also for members you shared them with. You leave projects shared with you, and your copies of their keys are removed. Security events are kept, unlinked from the account. The deletion event records your email.

Guest (unclaimed) projects: an AI or human can create a project without an account. A guest project stays active while the CLI uses it. After 30 days without use, or 180 days after it was created, values can't change. For 30 more days, run still works and it can still be claimed. Unclaimed projects may be deleted after that. Deletion is permanent. Run npx getmyenv claim to keep the project.

Browser sessions expire on the schedule above. Tokens last up to 1 year unless you revoke them sooner. Tokens for getmyenv staff accounts last 8 hours.

Analytics retention follows the settings in our Google Analytics property.

Your choices

You can limit analytics with browser controls or extensions that block tracking scripts. Privacy or security questions: Contact or [email protected].