Security is part of membership, not an upsell

Transport and access

• Modern TLS is required for member-facing mail protocols and web access.
• Authentication attempts are rate-limited and logged for abuse review.
• Member credentials are stored using industry-standard salted hashing; plaintext passwords are never retained in correspondence.
• Session timeouts apply to the member web portal after a period of inactivity.

Data handling

MyPrivate does not monetize member correspondence through advertising profiles or third-party data brokers. Operational staff access is limited to what is required for service delivery, abuse response, and lawful requests processed according to our privacy policy.

• Message content is not used to train external models or sold to marketing platforms.
• Backups are encrypted and retained according to member policy schedules communicated at provisioning.
• Custom domain members receive domain verification requirements before mail flow is enabled.

Infrastructure posture

• Routine patching and vulnerability review are performed on a fixed maintenance calendar.
• Member traffic is segregated from unrelated public web properties where feasible.
• Incident response procedures include member notification when credentials or availability may be affected.

Member responsibilities

Security is shared. Members agree to use strong unique passwords, protect recovery information, and report suspected compromise promptly. Accounts involved in abuse, bulk unsolicited mail, or policy violations may be suspended pending review.

What we do not claim

MyPrivate is a managed correspondence service, not a consumer anonymity product. We do not publish marketing-grade “military encryption” language. Members requiring specialized legal or regulatory certifications should discuss requirements during the invitation review process.