Mortuary Dispatch Network
Effective May 2026 · Subject to update before full commercial launch.
01
MDN provides software for coordinating pickup requests, dispatch, custody documentation, and related operational workflows for authorized organizations. This policy describes the categories of information we handle in connection with the service and how we handle them.
02
We collect information your organization provides when accounts are created, when users sign in, and when work is performed in the platform. This includes account profile fields, organization details, contact information, role assignments, device and session metadata, and audit-related metadata associated with platform activity.
03
We use information to operate and improve the service: to authenticate users, route pickup requests, coordinate dispatch, record custody and job activity, send operational notifications, support billing, monitor for abuse and errors, and improve reliability and security. We do not sell personal information.
04
Account and organization data is scoped to the organization that created it. Role-based access controls and organization isolation are applied so that users see information related to their own organization and the role they have been assigned within it.
05
Dispatch, job, and custody records — including statuses, signatures, timestamps, and location data captured during a pickup — are recorded to support operational coordination, recordkeeping, and audit needs. Custody events are append-only by design to preserve the integrity of the chain of custody.
06
Subscription and payment workflows may be handled through third-party payment processors. Card numbers and similar payment credentials are processed by those services in accordance with their own policies; MDN does not store full card numbers. Billing identifiers and high-level subscription state may be retained to operate the service.
07
We may send operational messages by email or SMS — including authentication codes, password resets, dispatch and job notifications, and administrative notices — using third-party providers. Recipients can manage their contact details through their account.
08
We use technical and organizational measures intended to protect information, including encryption in transit, access controls, audit logging, and least-privilege principles. No system can be guaranteed to be entirely secure, and users should safeguard their credentials and report suspected misuse promptly.
09
Operational records — including dispatch history, custody events, audit logs, and billing records — may be retained for as long as necessary to support compliance, audit, dispute resolution, or service integrity, and as otherwise required or permitted. Specific retention practices may evolve as the service matures.
10
MDN relies on third-party providers for hosting, database, monitoring, communications, payments, and similar infrastructure. Those providers handle data on our behalf in support of the service and are subject to their own terms and privacy practices.
11
Account holders can review and update their profile information through the platform. Some information is required to provide the service; removal of that information may affect access. Where additional choices apply by law, we will honor them as required.
12
For privacy questions, contact MDN through your account administrator or the official contact channel provided during onboarding.
13
This policy may be updated before full commercial launch. Material updates will be reflected on this page along with a revised effective date.
