MRM-Roc MailingPermission-based SaaS

Contact

Reach M-Roc for pilot and compliance requests.

Use these routes for pilot inquiries, privacy requests, abuse reports and operational support. Dedicated support mailboxes must be activated before paid beta.

Last updated: 2026-06-11 EDT

Current public contact route

During the private pilot setup, public inquiries should start from the M-Roc public landing page contact area.

Request types

  • Privacy request: access, correction, opposition, deletion review or unsubscribe issue.
  • Abuse report: suspected spam, misleading sender, list-source dispute or complaint.
  • Pilot support: account, import, campaign approval, suppression or audit question.
  • Provider incident: bounce spike, complaint spike, provider warning or unexpected dispatch job.

Before first live send

M-Roc must activate and monitor dedicated operational aliases for support, privacy and abuse requests before opening real provider dispatch for pilot customers.

Supportactivation target

support@digimonstre.com

Pilot operator questions, account support, imports and campaign workflow issues.

Monitoring owner: Support/operator

Privacyactivation target

privacy@digimonstre.com

Data access, correction, opposition, deletion review and unsubscribe disputes.

Monitoring owner: Founder/compliance

Abuseactivation target

abuse@digimonstre.com

Spam complaints, suspicious sender behavior, list-source disputes and provider review.

Monitoring owner: Abuse/operator

These aliases must receive an external test message and have a named monitoring owner before `MVP_SUPPORT_MAILBOXES_ACTIVE` can be set to true.