Skip to content
Milly Lab
Sign up

Trust & legal

Security Overview

This document describes how Milly Lab protects data, what third parties receive, and where the current limits are. It is for customers evaluating Milly Lab and for anyone assessing it on a customer's behalf.

Last updated:

Milly Lab holds no security certification. This is a statement of practice, not an audit result. No claim of SOC 2, ISO 27001, HIPAA or GDPR compliance is made anywhere in this document, because none has been verified.


Authentication #

  • Sign-in is by email and password, or Google sign-in.
  • Passwords are stored as one-way hashes. Milly Lab cannot read your password.
  • Access tokens are valid 60 minutes; refresh tokens 30 days. The web app signs you out after 20 minutes without activity.
  • Tokens are held in browser storage: local storage, or session storage (cleared when the tab closes) if "Keep me signed in" is turned off at sign-in.

Two-factor authentication

Two-factor authentication is optional and is turned on in Profile → Security.

  • Authenticator codes. Once it is on, sign-in needs the password and a 6-digit code from any TOTP authenticator app. Turning it on or off requires the current password.
  • Recovery codes. One-time codes, shown once at setup, sign you in if the authenticator is lost.
  • Passkeys. With two-factor on, a passkey (Touch ID, Face ID, Windows Hello or a security key) can replace the code. The password is still required first.
  • Trusted browsers. "Remember this browser for 30 days" skips the code on that browser only. The password is still required. Trusted browsers can be revoked one by one or all at once.

Sign-in alerts and re-authentication

  • Every sign-in is recorded as a coarse device label (browser and operating system) with a shortened IP prefix. Recent sign-ins are listed in Profile → Security, and a sign-in from a new device triggers an email to the account owner.
  • Deleting the account requires a fresh re-authentication, so a stolen session cannot close the account.

Session revocation

Every token carries the account's revocation version. Signing out, changing a password, or resetting a password increments that version, and every token minted earlier stops working immediately — across all devices.

This matters because it means a stolen token has a bounded life that the user can end themselves. A password change is a genuine remedy, not a cosmetic one.

Deactivating an account takes effect at once: every authenticated request re-checks the account's active status.


Data isolation #

Every request resolves to an authenticated user, and every query for user-owned data is constrained to that user. Conversations, sessions, generated assets, usage records and workspace connections are scoped to their owner.

Team content is visible to team members by design. Anything shared into a team workspace is visible to everyone in it.


Encryption #

  • In transit — HTTPS to Milly Lab, and to every third-party provider.
  • Connected-workspace tokens — encrypted at rest with Fernet symmetric encryption, using a key held in the server environment rather than in the database.
  • Database and object storage at rest — provided by Railway and Cloudflare R2 respectively.

In production the application refuses to start unless the workspace-token encryption key is configured and valid — the encrypted-at-rest statement above does not depend on deployment configuration.


What third parties receive #

Milly Lab cannot answer a prompt without sending it to a model provider. What you submit — prompts, conversation history, attachments, and the contents of files read from a connected workspace — goes to the provider of the model you selected.

The complete list, with what each receives and where it processes, is the Subprocessor List.


Connected workspaces #

The highest-risk surface, and the one with the most deliberate design.

Permissions

ProviderScopeWhat it actually grants
GitHubrepoFull read/write to repository content. Not limited to the repository selected in Milly Lab — technically reaches every repository the account can access. Milly Lab confines itself to the selected repository in its own code.
Google Drivedrive.fileOnly files the user opens with Milly Lab and files Milly Lab creates. Enforced by Google, not by Milly Lab.

The GitHub position is disclosed plainly to users in the Connected Workspaces Guide and the Privacy Policy rather than glossed over.

The staged-write property

A run cannot modify a user's repository. Writes during a run go to a staging overlay attached to the session, never to the provider. Applying is a separate, explicit, user-initiated action.

This is the security boundary that matters most: a model that behaves unexpectedly — or that is manipulated by malicious content inside a repository it is reading — still cannot commit anything. The worst outcome is a bad proposal the user declines.

Supporting controls:

  • Path confinement. File paths are validated at the tool boundary and re-validated at apply time, and percent-encoded when sent to the provider. A path attempting to escape the selected repository is rejected.
  • Conflict detection. The version of each file when read is recorded. If it changed in the meantime, that file is reported as a conflict and left alone rather than overwritten.
  • Apply claiming. Concurrent applies are rejected, so a double-click cannot produce duplicate commits. The claim self-expires so a failure cannot wedge the session.
  • No apply mid-run. Applying while a run is still executing is refused.

Other controls #

  • Server-side URL validation on user-supplied reference image and video URLs, so Milly Lab cannot be induced to fetch internal network addresses.
  • Rate limiting on authentication and other sensitive endpoints.
  • Spend gating. Every billable operation passes a metering gate before a provider is called, so a runaway or hostile client cannot generate unbounded cost against Milly Lab's provider keys.
  • Administrative audit logging. Privileged console actions, including impersonation, are recorded.
  • No public API schema. The OpenAPI schema and the interactive API documentation are not served on the deployed hosts.

Reporting a vulnerability #

Report it through the Contacts page, and say that it is a security report. The team replies by email.

Please do not test against other users' accounts or data.


Known limitations, stated plainly #

An evaluator will find these anyway. They are listed here rather than discovered.

  1. No third-party security certification. No SOC 2, no ISO 27001, no penetration-test report.
  2. The GitHub OAuth scope is broader than the access Milly Lab uses. Described above.
  3. Account deletion keeps the billing ledger. Deleting an account erases it at once — conversations, memory, generated assets, connections and stored workspace tokens go, and every session ends — but payment and usage records stay for accounting, without the person's name or e-mail address.
  4. No data-retention schedule. Content is kept indefinitely; there is no automated deletion.
  5. The data export lists files instead of copying them. Settings → Data controls → Download my data returns one zip of JSON files with everything the account owns; uploaded files and generated media are listed with their links, not copied in. (Agents, skills and MCP server settings can also be exported from the Console.)
  6. Content sent to model providers cannot be recalled. Once transmitted it is governed by that provider's retention policy.
  7. Access tokens are held in browser storage, which is readable by JavaScript running on the page. The 60-minute lifetime, the 20-minute idle sign-out and revocation-on-logout limit the exposure.
  8. No formal incident-response plan is published.
  9. Single hosted region and a single web process. No documented disaster-recovery position.
  10. No SLA is offered.