Updated April 2026

Privacy
Philosophy

Not a policy. A position.

Ownership does not transfer on contact.
Custody is not title.

On Information and Ownership

Information about a person is an extension of that person. To collect it without necessity is not a neutral act — it is an appropriation. To retain it beyond purpose is not caution — it is possession without right. What a person generates about themselves originates with them, belongs to them, and does not become someone else's asset simply by passing through their systems. Ownership does not transfer on contact. Custody is not title.

Most of the digital economy is built on the opposite premise — that data flows freely until someone objects, shifting the entire burden of protection onto the person least positioned to carry it. We reject that entirely. The burden is on us to justify every piece of information we touch, and when we cannot justify it, we don't touch it. Occasionally, a specific and necessary function requires passing limited information to another custodian for a bounded purpose. When that happens, we name it, we limit it, and it goes no further.

We handle what belongs to others the way we would handle anything that was never ours to keep — carefully, minimally, and with a clear understanding that it goes back. We are custodians at best, and only briefly. Privacy is not a feature we offer. It is a condition we refuse to violate.

What We Collect and Why

We respect you enough not to want your information. Not what you browse, not what you buy, not what you do when you're not talking to us. None of it. We know what we need to do the job — your name, your contact, your engagement context — and that's the boundary. Anything beyond that isn't our business, literally.

Your Control

Before a contract is executed, anything you've shared with us is yours to delete entirely. Once an agreement is signed and an engagement begins, the information you voluntarily provided becomes part of a mutual business record. At that point it is no longer personal data held on your behalf — it is evidence of a commercial transaction between two parties.

“It is not personal data. It is not a profile. It is a receipt.”

We retain exactly three categories — executed agreements, delivery confirmations, and payment records — for six years from the close of an engagement. That window exists to protect the integrity of completed work on both sides. When it closes, those records are deleted permanently and without recovery.

Infrastructure and Third Parties

Your data is encrypted in your browser before it ever touches a server. By the time it moves, neither we nor any platform we use can read it in transit. It arrives encrypted and it stays that way.

Our site is served through Netlify. Data is stored in Supabase. Both platforms handle encrypted data only — they are infrastructure, not data processors in any meaningful sense, because what passes through them is unreadable to them by design. Netlify's privacy policy is available at netlify.com/privacy. Supabase's privacy policy is available at supabase.com/privacy.

Email notifications are delivered through Resend. Resend is used exclusively to notify you when something in your portal requires attention — a new message, document, or invoice. The notification contains nothing beyond your name, your email address, and the fact that an update exists. The content of that update never leaves your encrypted portal. Resend's privacy policy is available at resend.com/legal/privacy-policy.

Payment processing is handled by Stripe. When you transact with us, Stripe receives what is necessary to complete that transaction — nothing sourced from us beyond what the transaction itself requires. We do not pass behavioral data, engagement history, or anything beyond the transactional minimum. Stripe's privacy policy is available at stripe.com/privacy.

We are candid about something: these platforms operate under their own privacy policies, which we do not control and which may not reflect the same standards as our own. By engaging with our services, you extend a degree of trust to each of them. We have chosen each platform deliberately and with care, but we will not pretend their commitments are identical to ours. We encourage you to review their policies directly.

On Compliance

Regulators are welcome to review our practices. They'll find compliance — a byproduct, not a goal. We didn't build this around legal minimums. We built it around actually giving a damn, which turns out to be a considerably higher bar than the law has ever managed to set. If the rules happen to agree with us, that's the law's good fortune, not our achievement.

Security Practice
  • Our codebase is reviewed by automated agents on a recurring basis. Attack surface, dependency exposure, and security architecture are audited continuously — not as a one-time hardening exercise, but as an ongoing practice.
  • The standard we hold is that of a company considerably larger than we are. Small operation. Enterprise-grade review cycle.
  • The philosophy above describes our position on data. This is how we make sure the system enforces it.

What this means, in plain terms.

01

You own it

Data belongs to the person it describes — not to whoever processed it. We don't acquire rights to your information by handling it.

02

We take only what we need

Name, contact, engagement context. That's the boundary. Anything beyond that isn't a feature — it's overreach we're not interested in.

03

Control is yours — until it's shared

Before a contract is signed, anything you've shared is yours to delete entirely. Once an engagement begins, those records become mutual business evidence — retained for six years, then permanently deleted.

04

Four custodians. All bounded.

Netlify serves the site. Supabase stores data, encrypted. Resend delivers portal notifications — name, email, and the fact of an update, nothing more. Stripe processes payments. Each is named, scoped to infrastructure, and receives nothing behavioral. What passes through them is unreadable to them by design.

05

Compliance is a byproduct

We built this around actually giving a damn — which is a considerably higher bar than the law has ever managed to set. Regulators are welcome to check. They'll find we cleared their bar on the way to ours.

The Digital Economy

  • Collects freely, until you object
  • Retains indefinitely, just in case
  • Shares broadly, within policy fine print
  • Deletion requires a form, a wait, and faith
  • Compliance is the ceiling, not the floor

MEXICONNECT

  • Collects only what a specific function requires
  • Retains three named categories for six years, then permanently deletes
  • Four named custodians — all bounded, encrypted, scoped to infrastructure
  • Pre-contract: delete directly. Post-contract: mutual record, time-bounded.
  • Compliance is a byproduct of a higher standard

Privacy is not a feature we offer.
It is a condition we refuse to violate.

Work with us