SECURITY · PRIVACY · RESPONSIBLE AUTOMATION
Security and privacy for your dental operations.
This Trust Center describes the security architecture and infrastructure providers behind DentalXpand, the dental operations and billing platform from Xpand Technology LLC. It also explains what your organization needs to confirm before connecting a practice.
Overview published: October 8, 2026. This is not an evidence-review date.
Documents for your security review
Tell us which deployment, controls and agreements you need to assess. We will confirm the available documents, their scope and any access requirements. Do not send patient data or credentials.
Request security documents · Read our Privacy Policy
Provider assurance
Scope: Railway hosting and Supabase data services; provider reports cover their assessed services.
Status: Provider information is linked below. Confirm the current report period and service scope with the provider.
Evidence date: Current report periods are not supplied on this page.
Document owner: The relevant infrastructure provider.
Review provider sourcesDentalXpand application controls
Scope: Access, encryption, session locking, administrator authentication and external security testing described below.
Status: Public architecture overview. Request deployment-specific evidence; an independent DentalXpand SOC 2 Type II examination remains on the roadmap.
Evidence date: Deployed-control test dates and penetration-test scope/date are not publicly supplied here.
Review contact: Xpand Technology LLC — support@dentalxpand.io.
Review access controlsBAA and data-processing terms
Scope: Applicable services, PHI workflows and the proposed deployment.
Status: Arrange the applicable BAA before enabling PHI workflows. Request the DPA and confirm the terms that apply to your deployment; this page does not establish that an agreement has been executed.
Evidence date: Agreement versions and execution dates require confirmation.
Review contact: Xpand Technology LLC — support@dentalxpand.io.
Review healthcare prerequisitesData lifecycle and connected providers
Scope: Retention, deletion, exports and providers enabled for your setup.
Status: Public Privacy Policy and Terms are available. Request the current provider/subprocessor list and deployment-specific retention arrangements.
Evidence date: Provider-list and retention-review dates require confirmation.
Review contact: Xpand Technology LLC — contact@dentalxpand.io.
Review privacy and retentionInfrastructure with independent provider assurance
DentalXpand runs on Railway’s managed application infrastructure, with Supabase supporting its core database and data services. Our Railway application services and Supabase database are hosted in North American regions. Both providers publish SOC 2 Type II compliance information covering their assessed services.
Railway
Application hosting infrastructure. Review Railway’s compliance information and request its current assurance documents through its Trust Center.
Supabase
Database and data-service infrastructure. Supabase publishes its security practices and the scope of its annual SOC 2 assessment.
Our security foundation combines independently assessed infrastructure providers with DentalXpand’s application-level access controls, encryption and security testing. Provider SOC 2 reports cover their respective services. An independent SOC 2 Type II examination is part of DentalXpand’s security roadmap. We plan to pursue this assessment and publish an update here upon completion.
Separate website and application domains
Our public website, dentalxpand.io, and application, xpand.dental, use separate domains. This creates a browser-level boundary: one domain cannot set cookies for the other, and browser same-origin rules restrict access between them. It helps limit some cross-site risks, while infrastructure, access controls, integrations and ongoing risk management determine the service’s broader protection.
Read MDN’s explanation of the same-origin policy.
Layered data protection
- Encryption at rest: Supabase states that customer data on its platform is encrypted at rest with AES-256. DentalXpand’s PMS credential and imported source-snapshot components additionally use AES-256-GCM encryption.
- Transport protection: HTTPS and TLS protect supported connections. Protocol support and configuration depend on the endpoint and connected provider.
- Protected integration credentials: Sensitive connection settings are handled through restricted backend paths rather than ordinary browser-facing settings.
During setup, we review where data travels, which integrations are enabled and how the deployment is configured. A provider’s encryption statement does not cover every downstream export or customer-managed device.
Access scoped to your organization and practice
DentalXpand’s access architecture combines authenticated users, role and permission checks, organization and practice scoping, PostgreSQL row-level security policies and private-file access policies. These controls are designed to limit access to the workspace and actions a user is authorized to use.
Two-factor authentication is required for every administrator account, including users newly assigned an administrator role. Protected platform-administration functions also include elevated authorization checks. Administrative audit records help support investigation and accountability for covered actions.
- Inactive sessions automatically lock after 30 minutes.
- After three incorrect password attempts, sign-in is blocked until the user resets their password through the Forgot Password flow.
Training, support and billing staff receive access according to their assigned roles. These staff members are not granted direct administrative access to production servers, databases or source-code repositories. They cannot sign in as clients or directly change client passwords; they can send invitations or password-reset links to the client’s registered email address.
Customer administrators should check permissions when roles change and remove access when people leave. They should also confirm who can manage integrations, exports and sensitive workflows.
Confirm the healthcare-data setup before connecting
Xpand Technology LLC signs Business Associate Agreements for applicable services. Contact support@dentalxpand.io to arrange the required agreement before enabling workflows involving PHI.
Before protected health information (PHI) enters a workflow, confirm the authorized use, applicable Business Associate Agreement (BAA), selected services and required safeguards. Hosting-provider compliance alone does not establish that a particular deployment is ready to receive PHI.
- Confirm each connection’s provider, purpose, data categories and permitted actions.
- Use approved secure setup channels for credentials and patient information.
- Review AI and document-extraction outputs before material healthcare, payment or employment decisions, as described in our Terms.
Keep patient data out of public forms. Do not send PHI, passwords, API keys or financial-account details through our website inquiry form or ordinary email.
Your data, privacy choices and retention
Customers control the records they place in their workspace and the users, integrations and workflows they authorize. Our Privacy Policy explains information use, connected services, AI-assisted features and rights requests.
Retention, deletion and export arrangements depend on the applicable agreement, data type, customer configuration and legal obligations. Removing an integration does not automatically erase records already received by another service.
Official HIPAA guidance for your evaluation
Use these U.S. Department of Health and Human Services resources when reviewing your organization’s responsibilities and the proposed deployment.
- HIPAA Security Rule overview — administrative, physical and technical safeguards for electronic protected health information.
- HIPAA risk analysis guidance — identifying and assessing risks to electronic protected health information.
- Business associates and BAAs — business-associate roles and agreement responsibilities.
- HIPAA and cloud computing — cloud-provider responsibilities, BAAs and shared safeguards.
These resources explain general requirements. Linking to them does not imply government endorsement or certify DentalXpand’s compliance.
Have a security question?
DentalXpand has engaged external security-testing firms for penetration testing. An assessment applies to the systems and scope tested at that time.
Send your business security questions or procurement requirements to support@dentalxpand.io. Tell us which controls and provider documents you need to review, and the deployment you are considering for your practice, billing company or DSO.
To report a suspected vulnerability, use the same address with the subject “Security report.” Start with a brief description and affected feature; request a secure channel before sharing sensitive evidence.
For privacy questions or rights requests, contact contact@dentalxpand.io.
This overview supports your evaluation. Your executed agreement, BAA, DPA and applicable service terms govern the commitments for your deployment.