Milled Legal

Security Overview

Last updated: September 18, 2026

This page describes the technical and organizational measures Milled (Full Stack LLC) uses to protect customer data. It is incorporated into our Data Processing Agreement as Annex II.

Scope

Milled is a search engine and archive of publicly distributed marketing emails. Customer Data is limited to authorized-user account details and the content users create in the Service (private lists, collections, notes, saved searches). Milled does not ingest customer databases, end-user data, or payment-card data; payments are processed by Paddle, our Merchant of Record.

Access control

  • System-level production access (servers, databases, infrastructure consoles) is limited to the founder.
  • Customer-support staff use role-based application admin access with tiered permission levels, below system level. Admin actions are recorded in an audit log.
  • Administrative access to infrastructure providers, source control, DNS and edge services, and billing requires multi-factor authentication, with hardware security keys where the provider supports them.
  • Credentials are stored in a password manager; application secrets are stored as encrypted application credentials and Kubernetes secrets.
  • Operator access to production hosts runs over a private overlay network. No SSH is exposed to the public internet.

Customer authentication

  • Sign-in is by Google account or an emailed magic link. Passwords, where used, are hashed with bcrypt.
  • Sessions can be revoked by Milled on request. Seats are individual; credential sharing is prohibited.
  • SAML single sign-on, SCIM provisioning, and in-app two-factor authentication are not currently offered. Google sign-in inherits the customer's Google Workspace multi-factor policy.

Encryption

  • All traffic is encrypted in transit with TLS 1.2 or higher at the edge and between the edge and origin.
  • Data at rest is encrypted by the hosting providers for the database and object storage.

Infrastructure

  • Milled runs on infrastructure in the United States (Cloudflare, Amazon Web Services, PlanetScale, netcup), with some background processing in the European Union (Hetzner). The current vendor list is on the Subprocessors page.
  • Production, staging, and development environments are separated. Production data is not used in development except through read-only, access-logged tooling.

Change management

  • All code changes go through pull requests with automated tests and review before merge. Deploys are automated and can be rolled back.
  • Dependencies are monitored for known vulnerabilities.

Monitoring and incident response

  • Application errors and infrastructure metrics are monitored with on-call paging. Infrastructure monitoring receives no customer data.
  • Security incidents affecting customer personal data are reported to the customer's notice address within 72 hours of Milled becoming aware.
  • Bot and abuse traffic is controlled at the edge and in the application.

Backup and resilience

  • Database: continuous backups with point-in-time recovery.
  • Object storage is replicated; search indexes are backed up separately.
  • Database backups run every 12 hours and are retained for up to 31 days, with point-in-time recovery inside that window. Deleted customer content is removed from live systems on deletion and expires from backups within that window.

Retention and deletion

  • Customer content is deleted on request or within 60 days after a subscription ends.
  • Account deletion requests are handled through [email protected] within 45 days.

Personnel and certifications

  • Milled is founder-operated. Contractors with access to support tooling are bound by confidentiality terms.
  • Milled does not hold SOC 2 or ISO 27001 certification.

Reporting a vulnerability

Email [email protected]. See also our Subprocessors list and Privacy Policy.