About TreeChain AI & Glyphic Encryption

TreeChain AI is a proprietary encryption technology that operates as a second layer on top of standard AES-256-GCM encryption. Rather than relying solely on mathematical complexity that could be vulnerable to future quantum computing advances, TreeChain's polyglottal cipher takes AES-encrypted data and transforms it through a multi-dimensional mapping system that produces output as sequences of Unicode glyphs drawn from thousands of symbol sets — including alchemical notation, ancient mathematical symbols, astronomical signs, and writing systems from across human history.

The result is that what's actually stored in the database is not ciphertext in any traditional sense — it's streams of shapes and symbols (e.g., ⑨🜐🜟☥₮✍⁹☇ƀ❋❊Ŧ✞☐❼❇☋✈) that cannot be parsed, searched, indexed, or reverse-engineered by any known method, including quantum computing approaches. To recover the original data, an attacker would need to reverse the glyph cipher first, then break AES-256-GCM underneath — two completely independent cryptographic challenges.

Each encryption operation uses emotion-keyed cipher modes — named after philosophers (Aristotle, Plato, Socrates, Confucius, Kant, Descartes, Nietzsche, Spinoza) — that map to distinct cipher configurations, producing entirely different glyph patterns for the same input. This eliminates frequency analysis vulnerabilities completely.

Data Flow & Protection

Patient Intake Submission

When a patient submits a form on a practice's portal, the following security measures are applied automatically before the data is stored:

• Form data is validated and sanitized on the server
• PHI fields are individually encrypted with AES-256-GCM using a per-record DEK (Layer 1)
• The AES-encrypted output is transformed through TreeChain's glyph cipher (Layer 2) into quantum-proof symbolic strings
• Plaintext PHI is immediately purged from memory — only encrypted data is stored
• Display-safe glyph representations replace sensitive fields for dashboard viewing
• Searchable HMAC hashes are generated for lookup without exposing plaintext
• A full audit trail entry is created for HIPAA compliance

Data at Rest

Stored data is protected at three levels: AES-256-GCM envelope encryption, TreeChain glyph encryption, and AWS server-side encryption (SSE-S3). Even database administrators cannot read patient records — all PHI fields contain only encrypted glyph strings.

Data in Transit

All communications are secured with TLS 1.3. Practice portals enforce HTTPS with HSTS. API calls between services use encrypted channels with certificate validation. Patient form data is encrypted in the browser before transmission when supported.

Business Associate Agreement (BAA)

Dental Education, Inc. executes a Business Associate Agreement with every registered practice, establishing our obligations under HIPAA for the protection of PHI. Our BAA covers all services provided through the Intake.Dental platform, including:

• Digital patient intake forms and form submissions
• PDF generation and document storage
• Video consultations and teledentistry features
• Practice Management System (PMS) integration via Sikka AI
• Insurance verification services
• Email notifications and patient communications

We also maintain BAAs with all subcontractors in our service chain — AWS, Supabase, Sikka AI, and payment processors — ensuring end-to-end HIPAA compliance throughout the data processing pipeline.

Breach Notification

In the event of a confirmed security incident affecting PHI, Dental Education, Inc. will:

• Notify affected practices within 72 hours of discovery
• Provide a detailed incident report including scope, affected data, and timeline
• Cooperate with the practice's breach notification obligations under the HIPAA Breach Notification Rule
• Implement immediate remediation measures and document all corrective actions
• Provide ongoing status updates until the incident is fully resolved

Note: Due to our dual-layer encryption architecture, even in the event of unauthorized database access, patient PHI would remain encrypted and unreadable as glyph strings — which may qualify as a safe harbor under the HIPAA Breach Notification Rule's encryption exception (45 CFR § 164.402).

Third-Party Integrations & Compliance

Sikka AI — Practice Management System Integration

PMS integration is provided through Sikka Software Corporation, which maintains its own HIPAA compliance program and BAA. Sikka AI enables connectivity to 50+ dental PMS platforms. All PHI transmitted through the integration is covered under our BAA chain.

Insurance Verification

Real-time insurance eligibility verification is performed through HIPAA-compliant clearinghouse APIs using standard X12 EDI 270/271 transactions. Patient insurance data is transmitted securely and used solely for eligibility verification on the practice's behalf.

Video Consultations

HIPAA-compliant video infrastructure with end-to-end encrypted transmission. Video content is not recorded or stored by Intake.Dental unless explicitly configured by the practice. See our Terms and Conditions Section 11 for full teledentistry terms.

Contact

For security or compliance questions: