PstEnroll
Sign UpBook a Demo
Book a DemoSign Up

Legal · PostEnroll

Information Security

Last updated July 8, 2026

Privacy PolicyTerms of ServiceTCPA ComplianceSecurity

PostEnroll handles data that matters: Medicare members’ names, phone numbers, plan details, call recordings, and transcripts. This page describes our security program the way we run it — what is in place today, and what is in progress. We would rather tell you the truth than impress you.

Architecture and data flow

Member data lives in an agency-isolated database. Every table is protected by row-level security, and application queries are scoped to the owning agency — a three-layer isolation model (middleware authorization, query scoping, and database-level row security as the backstop). Voice calls run through our voice AI subprocessor under a signed Business Associate Agreement; recordings and transcripts are attached to the call record and visible only to the owning agency.

In place today

  • Encryption in transit: TLS on every connection — browser to app, app to database, and between our services and subprocessors.
  • Encryption at rest: disk-level encryption across our database and hosting infrastructure.
  • Tenant isolation: row-level security enabled on all tables; agency-scoped access enforced at three layers.
  • Authentication and access: managed authentication with JWT-based sessions and role-based access controls — platform, agency, and team-member scopes.
  • Least-privilege access: privileged database credentials are confined to the backend and never exposed to browsers; administrative endpoints require authenticated administrator sessions.
  • Compliance rails in code: calling-time gates, four-layer do-not-call enforcement, text-message opt-out handling, and recording-disclosure requirements for all-party-consent states (see our TCPA Compliance page).
  • Observability without leakage: error monitoring is scrubbed of personal information before events leave our systems.
  • Emergency controls: platform-wide kill switch and per-agency pause for all outbound activity.
  • Secure development: schema changes ship as reviewed migrations, and secrets live in environment configuration — never in source code.

HIPAA & BAA

We do not accept real member PHI onto the platform before a Business Associate Agreement is executed with your agency. Until then, onboarding and testing run on demo and synthetic data only.

Where PostEnroll processes PHI on an agency’s behalf, we act as a business associate under HIPAA and the executed BAA governs that processing. The current state of our BAA chain, stated plainly: our voice AI runtime BAA is signed; BAAs with our database, telephony, and AI-processing subprocessors are in procurement; and our customer-facing BAA template is with counsel. Request the current BAA status or template at legal@postenroll.ai.

We will not describe ourselves as HIPAA compliant until that chain is complete.

In progress

We maintain a roadmap of security enhancements beyond the controls above. Agencies in evaluation can request our current security roadmap and trust packet at security@postenroll.ai.

Responsible disclosure

If you believe you’ve found a vulnerability, email security@postenroll.ai. We commit to acknowledging reports within 2 business days, and we will not pursue action against good-faith research.

Subprocessors

A current list of our subprocessors — including which handle PHI and their BAA status — is available to customers and prospects under evaluation on request: privacy@postenroll.ai. The same address accepts subscriptions to subprocessor-change notifications.

Contact

Security questionnaires and diligence requests: security@postenroll.ai.

PstEnroll
  • Privacy Policy
  • Terms of Service
  • TCPA Compliance
  • Security
  • hello@postenroll.ai
© 2026 PostEnroll · All rights reservedBuilt in the United States