Support feels measured, calm, and serious.

A product like DMS needs support that understands the weight of the decisions involved. Questions about trust, verifier setup, billing, and release workflows are handled carefully and clearly.

• Support email: dms@dms.criv.app
• Main topics: billing, verifier setup, release concerns, account access, product trust questions
• Future direction: dedicated incident/status communication and release-flow support processes

What DMS always protects

• Clarity over hype
• Trust signals that users can actually see
• Human confirmation before serious release actions
• Testing before activation
• Precise privacy claims instead of exaggerated ones

DMS is a strong fit when users need controlled release.

• You have instructions no one else knows
• You want human-confirmed release, not simple scheduled delivery
• You care about a locked-by-default private dashboard
• You want to test the workflow before trusting it

DMS is not the right answer for every problem.

• If you need a legal instrument rather than a release platform
• If you want fully automatic release with no human checks
• If you are unwilling to maintain good verifier and beneficiary details
• If you do not want the responsibility of protecting recovery instructions

The safest first move is still the free rehearsal.

The product proves itself before it asks for trust. Start with test mode, walk through the workflow, and decide whether DMS fits your use case after you have seen it behave.

Formal legal text is being prepared for review.

DMS is a secure release workflow for encrypted instructions, not a replacement for legal planning. Formal legal documents govern the service separately from the product overview on these pages.