Menu

We are a San Diego based AI-first company. Our silicon to python full-stack expertise enables us to provide elegant and cost-effective solutions to businesses.

Our first product is secure email. Secure mail is regular email protected by open standards. The message is sent through commonly used email apps and protocols, while S/MIME certificates prove who sent it and encrypt the content so only the intended recipient can read it.

Outlook

Outlook showing a digitally signed and encrypted secure email message
Displays the message as digitally signed and encrypted by the sender.

iPhone Mail

iPhone Mail showing verified sender and lock icons on an encrypted message
Shows the verified sender badge and lock icon directly beside the address.

MacBook Mail

MacBook Mail showing security details for a signed and encrypted email
Labels the message security as signed and encrypted in the native reading view.

Encrypted content

The lock tells the recipient that the message body and attachments were encrypted for their certificate.

Verified identity

The signature badge confirms the sender address and shows the message was not altered after it was sent.

No special app

Patients and staff use Apple Mail, Outlook, and other standards-based clients instead of logging into a separate portal.

How secure email works

FAQ

Two setup paths, one interoperable S/MIME email standard.

Security Architecture: Website-based email setup (HIPAA mail)

During website setup, Pervasieve creates a unique S/MIME key pair and certificate for each mailbox. The private key and certificate are packaged in a password-protected PKCS#12 file. Apple devices receive it inside the signed configuration profile; Outlook Classic users receive a temporary certificate-download link and see the passcode separately during setup.

Only the public certificate is published to the LDAP directory. Senders use that public certificate to encrypt mail. The recipient's installed private key decrypts incoming mail and creates digital signatures. TLS protects mail while it is moving between systems; S/MIME protects message content and attachments end to end.

Email headers and routing metadata are not encrypted by S/MIME. HIPAA compliance also depends on each organization's policies, access controls, training, and operating procedures.
Diagram showing server key generation, protected certificate delivery, public certificate publication to LDAP, and encrypted S/MIME exchange
Website setup: protected private-key delivery and public-certificate discovery.

Security Architecture: App-based email

The Pervasieve app requests a short-lived enrollment challenge. Apple's SCEP framework generates the S/MIME key pair on the device and sends only a certificate-signing request to Pervasieve. The certificate authority signs the public key and returns the certificate to the device.

The S/MIME private key remains in the Apple keychain and is never uploaded to Pervasieve. The public certificate is published to LDAP so other standards-based mail clients can find it, encrypt messages for the user, and verify that user's digital signatures.

The app also uses a separate device-bound signing key to authenticate sensitive account actions. That key is not the S/MIME email key.
Diagram showing an Apple device generating its private key locally, requesting a signed certificate, and publishing only the public certificate to LDAP
App setup: on-device key generation with SCEP certificate enrollment.

Standards-based access

Devices and Platforms

iOS 15+

Pervasieve app and Apple Mail setup.

macOS

Native S/MIME support in Apple Mail.

Outlook Classic on Windows

Manual mailbox and S/MIME certificate setup.

Thunderbird on Android

Support planned

Pervasieve integration and minimum Thunderbird/Android versions are still being validated.

Reliable delivery, additional protection

Email Service

We continually evaluate commercial and open-source email solutions and select a foundation for secure, reliable email that offers strong performance and high availability.

Pervasieve layers identity, certificate discovery, S/MIME signing, and end-to-end encryption on top of the underlying email service. If you have an existing email provider that you would like Pervasieve to work with, let's talk.

Our commitment

Privacy Policy

Pervasieve is an independent company. Our revenue comes from subscriptions, not from selling or monetizing your data. We do not sell personal information or share it outside Pervasieve except for the limited information required by service providers to deliver the service.

  • Apple: Your subscription status may be visible to Apple when a subscription is purchased or managed through the App Store.
  • Email delivery: Pervasieve uses email infrastructure providers to deliver messages. Your email address and message destination are processed as needed for delivery.
  • Message contents: When S/MIME encryption is enabled, message contents and attachments are encrypted for the intended recipient and are not readable by Pervasieve or the underlying email service. If encryption is deliberately disabled, that protection does not apply.