Trust
Security and data boundaries should be understandable.
This page explains what the public website handles, the principles governing product data, and the controls that must be in place before approved patient-linked information enters the environment.
PLENTI does not claim certifications, audits, vendor designations, or production controls that have not been completed, granted, and verified.
Last updated: September 9, 2026
The public website
What this website currently handles.
This section describes the public PLENTI marketing website and Express Interest form. It does not describe every future product-data workflow.
- Business-contact information submitted through the Express Interest form.
- Practice-context information entered into the form.
- Limited technical information required to operate, secure, monitor, and diagnose the website.
- Encrypted transmission of form submissions through HTTPS.
- Storage of submissions in an access-restricted record.
- Internal access limited to people responsible for reviewing and responding to design-partner inquiries.
- Necessary service-provider processing required to host the site, store submissions, transmit notifications, or protect the service.
The public website is intended for business-contact and practice-context information—not patient information or clinical records.
Clear boundaries
What this website is not intended to do.
- It does not request or intentionally collect patient information or protected health information through the public form.
- It does not connect the public marketing website to a practice's clinical system or medical record.
- It does not provide a portal for uploading patient files or clinical records.
- It does not sell Express Interest submissions to advertisers.
- It does not use submitted inquiry information to claim customer results.
- It does not represent website visitors or inquiry submitters as PLENTI customers.
- It does not claim security certifications, independent audits, partnerships, or vendor designations that have not been completed or granted.
Please note
Do not submit patient information, protected health information, patient-identifiable information, clinical records, account credentials, source-system exports, or other sensitive practice data through this website or by ordinary email.
This boundary applies to the public marketing website and ordinary email. Future contracted product workflows may involve approved patient-linked information only after the applicable legal, vendor, security, access, and operating gates are satisfied.
Product data principles
The control framework PLENTI is designed and being validated to follow.
The following principles describe the intended product-data control framework. They do not mean that every production control has already been completed, independently tested, or audited.
Principle 01
Purpose-limited data
Principle 02
Customer control of raw source data
Principle 03
Read-only and least-privilege access
Principle 04
Practice-level separation
Principle 05
Traceability and visible exceptions
Principle 06
Human responsibility
These are governing design and operating principles. Current implementation status varies by control and must be stated separately.
Cloud infrastructure
Provider controls are one layer of the security model.
PLENTI uses third-party cloud and software infrastructure as part of its product environment. Provider assurance reports and security programs are evaluated as part of vendor diligence, but provider controls do not replace PLENTI’s responsibility for its own application, data, access, configuration, monitoring, and operating procedures.
Security in a cloud environment is a shared responsibility. A cloud provider is responsible for the security of the underlying infrastructure it operates. PLENTI remains responsible for the security and operation of its application environment, including customer data, identities, permissions, application configuration, encryption choices, monitoring, logging, incident procedures, vendor governance, and workforce responsibilities within its control.
PLENTI’s own SOC 2 readiness remains a staged objective. PLENTI does not currently claim that it has completed an independent SOC 2 examination unless and until that examination has been completed and the resulting report supports the claim.
Before patient-linked information
Contracts, permissions, vendors, and controls must be approved first.
PLENTI should not receive patient-linked information merely because a technical connection is available. The legal, operational, vendor, access, and security path must be approved before that information enters the environment.
- Executed design-partner, pilot, or customer agreement
- Business Associate Agreement or other appropriate data terms where required
- Data-processing and security terms appropriate to the engagement
- Written source-system authorization and an approved access method
- Defined minimum dataset and approved data-flow map
- Confirmed customer authority and named customer data contact
- Review of relevant hosting, database, AI, email, monitoring, integration, and other subprocessors
- Appropriate downstream agreements where required
- Read-only or least-privilege access wherever supported
- Practice-level separation and role-based access appropriate to the data scope
- Credential-control and access-revocation procedures
- Logging and monitoring appropriate to the environment
- Backup and recovery procedures appropriate to the service
- Security risk analysis
- Incident-response and notification procedures
- Workforce access, confidentiality, and training requirements
A signed BAA alone does not make an environment ready. Contracting, vendor eligibility, access design, technical controls, operating procedures, and workforce responsibilities must work together.
Patient-linked information would be accepted only through an approved contracted workflow after the applicable readiness requirements have been satisfied. The public website and ordinary email are not approved channels for that information.
Controlled decision path
Separate the source, the calculation, the explanation, and the decision.
A four-stage sequence in order: approved source information, then governed calculations, then AI-guided explanation, then human-led decision.
Stage 01
Approved source information
PLENTI uses information authorized for the agreed operating purpose and preserves where material source information came from.
Stage 02
Governed calculations
KPI, financial, scenario, and practice-value calculations follow approved deterministic logic, assumptions, and review rules rather than unrestricted language-model output.
Stage 03
AI-guided explanation
AI may organize, prioritize, de-duplicate, summarize, and explain approved findings, subject to traceability, confidence, limitations, and review.
Stage 04
Human-led decision
The physician owner and practice manager determine what action to take. Material value interpretation, unusual outputs, and low-confidence findings require appropriate human judgment.
AI-guided explanation. Deterministic calculations. Human-led decisions.
- AI does not independently create source data.
- AI does not independently calculate EBITDA or invent valuation conclusions.
- Material calculations should remain traceable to source information, formulas, assumptions, periods, and review status.
- PLENTI does not autonomously execute clinical, employment, payment, or transaction decisions.
Data use and learning
Customer data rights and reusable learning require clear permission.
A practice’s raw source data remains customer-owned. PLENTI uses that information only under the applicable agreement and approved purpose.
Any use of implementation evidence for de-identified learning, evaluation, playbooks, or benchmarking must be governed by the applicable agreement, approved purpose, de-identification and aggregation standards, minimum cohort thresholds, provenance, and protections against cross-customer disclosure.
PLENTI will not use customer information for an unstated purpose merely because the information is technically accessible.
- No identifiable customer information should be exposed to another customer.
- Benchmarking should not be represented as available until a sufficient permissioned cohort and appropriate comparison standard exist.
- De-identification is not the same as merely removing a practice name.
- Product improvement, evaluation, model use, retention, deletion, export, withdrawal, and historical-treatment rights should be defined contractually.
- Public case studies, customer names, testimonials, or named outcomes require separate permission.
Vendor and integration assurance
Pursue the strongest relevant designation for priority production connectors.
For priority production connectors, PLENTI intends to pursue the strongest relevant designation available in each vendor ecosystem—such as certified integration, marketplace listing, or technology-partner status—where such a program exists and materially improves secure access, data reliability, technical support, onboarding, or customer trust.
No certification, marketplace listing, technology-partner relationship, preferred-vendor status, endorsement, or formal partnership is claimed unless it has been granted, documented, and approved for public use.
- EHR and practice-management systems
- Reliable access to approved scheduling, encounter, patient-flow, and revenue-cycle information.
- Clearinghouse and revenue-cycle systems
- Reliable access to claims, remittance, denial, reimbursement, and collection information.
- Accounting and financial systems
- Traceable operating, income-statement, expense, cash, and financial-period information.
- Payroll and workforce systems
- Approved staffing, labor-cost, role-mix, capacity, and workforce information.
- Voice, communication, marketing, and referral systems
- Approved evidence concerning inquiry response, call intent, follow-up, referrals, and patient-conversion pathways.
The connector strategy is problem-led rather than logo-led. PLENTI should pursue a vendor relationship because it improves the approved customer use case—not simply to accumulate badges.
A vendor designation may support access, reliability, support, or customer confidence. It does not by itself certify PLENTI’s full security, privacy, data-governance, or compliance program.
Current status
State what is operating, what remains in validation, and what is not yet claimed.
Current public-website practices
- Business-contact and practice-context collection through the Express Interest form
- HTTPS transmission of website submissions
- Access-restricted inquiry records
- Limited internal access for inquiry review and response
- No intended collection of patient information through the public site
- No sale of inquiry submissions to advertisers
These statements describe the public website, not the complete PLENTI product environment.
Product controls in validation or readiness work
- Approved live-data access paths
- Source-to-KPI traceability
- Reconciliation and visible exceptions
- Practice-level separation
- Role-based access
- Credential and revocation controls
- Logging and monitoring
- Backup and recovery
- Vendor and subprocessor governance
- Incident-response readiness
- Repeatable customer implementation
- Security documentation and diligence processes
- SOC 2 readiness planning
Status varies by control. Inclusion in this column does not mean the control is production-proven.
Not claimed unless verified
- Commercial MVP completion
- Production readiness at scale
- PLENTI SOC 2 examination or report
- HIPAA certification
- HITRUST certification
- Independent security audit completion
- Guaranteed security
- Zero possibility of an incident
- Universal encryption claims not supported by configuration evidence
- A vendor designation that has not been granted
- A partnership or endorsement that has not been documented
- Broad compliance claims exceeding the reviewed service scope
Security is an operating discipline—not a one-time badge. PLENTI will update this page as material controls, reviews, agreements, and verified evidence advance.
Customer diligence
Security responsibilities should be confirmed before approved data access.
Before approved live-practice data access, the parties will confirm the applicable agreement, data boundaries, access method, customer and PLENTI responsibilities, relevant vendors, and supporting security documentation.
More detailed security, architecture, subprocessor, access-control, data-flow, and incident-response information may be provided through an appropriate diligence process, subject to confidentiality, availability, and the current evidence stage.
The availability of a document does not itself prove that every described control has been fully implemented or independently tested. Customer-facing documentation must remain consistent with the actual environment.
Questions
Questions about privacy, security, or data handling?
Contact PLENTI at info@plentisolutions.com for questions about website privacy, security, data handling, or the design-partner diligence process.
Do not send patient information, protected health information, patient-identifiable information, clinical records, source-system exports, passwords, access tokens, API keys, or other sensitive information by ordinary email.