EmailDesk is intended for legitimate business email. This policy explains permitted sending, prohibited behavior, recipient safeguards, and the evidence-led actions EmailDesk may take.
Reviewed: July 29, 2026Customers may use EmailDesk for ordinary business correspondence, customer support, account and service notifications, transactional application mail, permission-based marketing, internal operations, and approved custom-domain mailbox services.
The sender remains responsible for its legal basis, recipient permission, message accuracy, and any rules that apply to its industry or location.
Do not use EmailDesk for spam, phishing, malware, credential theft, impersonation, unlawful content, deceptive offers, harassment, evasion of another service's controls, or messages that conceal or falsify sender identity.
Do not send to purchased, scraped, harvested, rented, or transferred lists unless the sender can establish valid recipient permission and a lawful basis for that specific use.
Do not use transactional classifications, new sender identities, retry loops, URL shorteners, attachments, forwarding, or third-party integrations to bypass consent, suppression, quota, protection, or provider rules.
Use an accurate From name, an authorized and verified sender address, a working reply path where appropriate, and the DNS records required by the selected sending path.
SPF, DKIM, DMARC, or provider acceptance does not make unsafe or unwanted content acceptable and does not guarantee final delivery or inbox placement.
Marketing messages must include the configured unsubscribe behavior and must exclude recipients recorded as unsubscribed, bounced, or suppressed when those controls apply.
Customers should stop repeated delivery attempts when a permanent rejection, complaint, sender block, invalid address, or recipient opt-out provides evidence that another send is inappropriate.
EmailDesk may warn, watch, hold, quarantine, block, rate-limit, pause a sender or server, suspend sending, suspend a workspace, or require corrective work when current evidence supports that action.
A local block occurs before provider handoff. A provider can separately reject, defer, filter, or bounce mail under its own rules. EmailDesk records available evidence but does not promise that every abusive message will be detected.
Reports concerning EmailDesk service can be sent to abuse@emaildesk.bd. Include the relevant message headers, sender, recipient, date, and a short description when available.
Do not send account passwords, API keys, SMTP credentials, mailbox app passwords, or an unrelated mailbox export.