About

Email is the part of compliance nobody owns. We decided to own it.

PXCMail is built and operated by PacinfraX Corporation, headquartered in Irvine, California. We make email compliant for small regulated businesses — practices, firms and advisers that have the same obligations as a hospital or a bank and none of the staff.

Why we exist

Our founders spent two decades running email and security infrastructure for large organizations and watched small healthcare practices, accounting firms and law offices inherit the same rules with none of the tooling. The dental office down the street has a BAA, a Gmail account, a front desk that emails treatment plans all day, and no way of knowing whether any of it was encrypted. The two-partner CPA firm checked “yes, we have a WISP” on the PTIN renewal and hopes nobody asks. We think that is a solvable problem — and that solving it should not require a new app, a migration, or an IT department.

What we build

A compliance layer for the email you already use. Gateway sits in front of Google Workspace or Microsoft 365 and makes every outbound message compliant: encryption enforced, sensitive data detected before it leaves, an immutable archive, an audit trail your regulator can read. Hosted adds the mailbox for organizations that want everything from one vendor. An industry profile — healthcare, accounting and tax, legal and title, wealth — sets the agreement, the detection rules and the retention defaults at signup.

How we work

  • Assemble proven components; write as little new code as possible. We run on Amazon Web Services’ HIPAA-eligible mail and storage services and on open-source encryption and filtering software with long security track records. Our own code is the policy, the glue and the evidence — the smallest attack surface we can manage.
  • Publish the evidence. Every claim on this site links to the Trust Center. What is not done yet is marked as roadmap, with a date.
  • Make the safe path the default. Staff should not have to remember a toggle. Encryption and detection are automatic; the audit trail is a by-product of using email.
  • A human within fifteen minutes. Support is a product feature, not a cost center. DNS, connectors and migrations are done with you on a call.
  • Honest about limits. We do not give legal advice, we do not sell “HIPAA certification” (it does not exist), and we say plainly that compliance depends on your policies and people as well as our software.

What we promise

  • No AI reads your mail by default; we never train models on customer data.
  • No lock-in: standard protocols (IMAP, EWS, ActiveSync), full export in standard formats, a certificate of destruction when you leave.
  • Your data stays in the United States; only US-based staff can access message content, and every access is logged.
  • Published, flat pricing; no quotes, no annual surprises.
  • The agreement your regulator expects — Business Associate Agreement or Data Processing and Safeguards Addendum — signed before your first message.

The name

PXC stands for PacinfraX Compliance. Technically it is also what Gateway is: a protected exchange in front of your mail provider that makes every message compliant on the way out. Say it “P-X-C Mail”; write it PXCMail.

Company

Legal entity
PacinfraX Corporation
Headquarters
19900 MacArthur Boulevard, Suite 915, Irvine, California 92612, USA
Founded
2026
Teams
Engineering, security and tier-2 support in the United States; tier-1 support in Southeast Asia (configuration and metadata only, never message content)
Infrastructure
Amazon Web Services, US regions (us-east-1 primary, us-west-2 disaster recovery)
Leadership
Executive team and named Security Officer and Privacy Officer are published in the Trust Center at general availability
Contact
[email protected] · Contact page

Who writes and reviews what you read here

Every article on the blog and every regulation page in the Trust Center carries the name of the person who wrote it and is checked against the text of the rule before it is published. These are the people behind the bylines. The executive team and the named Security Officer and Privacy Officer are published in the Trust Center at general availability.

Elena Marsh
Compliance lead. Elena writes the regulation explainers and checks every article against the text of the rule before it is published. Before PacinfraX she ran privacy and security programs for outpatient clinics and a regional accounting firm.
Daniel Okafor
Product lead. Daniel runs product at PacinfraX and writes about what the product does and costs, including where competitors are better. He spent twelve years building email and archiving systems for large organizations.
Priya Raman
Security lead. Priya leads security at PacinfraX and handles incident response for customers. She writes about business email compromise, wire fraud and what examiners and carriers actually ask for.

Corrections: if an article misstates a rule, write to [email protected] with the citation. We fix it and note the change on the page.

Join us

We are a small team that likes email, security and healthcare more than is normal. Open roles →