Support

AR
Roadmap surface — not in MVP scopeRe-activates in Phase 5+ · RegAlign is currently available for controlled synthetic buyer validation. Named-customer pilot support terms are confirmed separately before activation.
Current support posture

Support terms should match the service actually in place.

RegAlign does not publish a generic response or resolution SLA before the relevant operating model has been evidenced. For any named customer or pilot, support hours, escalation, continuity and exit arrangements are agreed for that engagement and must match the capability in place at activation.

This is the current public contact route. Contact routing and monitoring are verified as part of named-customer activation; publication of an address does not by itself constitute a support SLA.

Availability

Demonstration and pilot are different stages

Controlled synthetic buyer validation

RegAlign may currently be demonstrated using controlled synthetic data. A named-customer pilot, real customer data or production reliance requires a separate activation decision and the applicable security, privacy, operational, support, commercial and customer-specific controls.

Operating principles

What must be in place for a named engagement

Current non-commitments

Not claimed unless separately evidenced and agreed

Customer-specific terms

Support, continuity and exit are part of activation

Before a named customer relies on RegAlign, the applicable agreement and activation record should define the support channel, severity and escalation model, operating coverage, incident communication, continuity and exit arrangements, known limitations and customer responsibilities. Those terms are not inferred from this public page.

Security and assurance information is provided through the appropriate controlled diligence route. See the Trust page for the current public posture.