Acceptable Use Policy for MailFleet Email Campaign Software

Purpose of this Acceptable Use Policy

MailFleet gives operators direct control over email campaigns from a desktop application: templates, SMTP and API provider profiles, proxy routing, SpamAssassin checks, sending capacity scoring, webhooks, and detailed local logs. That power must be exercised responsibly.

This Acceptable Use Policy sets the rules for what you may and may not do with MailFleet. It protects recipients, mailbox providers, our brand, and legitimate customers who depend on sustainable deliverability. It works alongside our Anti-Spam Policy, Terms of Service, Privacy Policy, and Security documentation — each document covers a different angle of compliance and operations.

By installing, licensing, or using MailFleet, you agree to follow this AUP. If you cannot meet these standards, do not use the software.

Who and what this policy covers

This policy applies to all MailFleet license holders, trial users, website visitors submitting inquiries, and anyone who configures MailFleet on behalf of an organization or client. It covers the desktop application, updates, documentation, free diagnostic tools on mailfleet.app, license validation, and support interactions.

MailFleet is client software. You connect it to email infrastructure you control or are authorized to use. We do not send mail on your behalf, host your lists in the cloud, or operate a shared SMTP pool. Your providers' acceptable use terms apply in parallel with MailFleet rules.

This document is not legal advice. Laws vary by jurisdiction, industry, and recipient type. Consult qualified counsel for obligations specific to your business. This AUP states MailFleet minimum expectations and industry-recognized boundaries for professional email software.

• Applies to all MailFleet installations on Windows, macOS, and Linux.
• Covers marketing, newsletter, operational bulk, and client-managed campaigns sent through MailFleet.
• Includes use of mailfleet.app tools, docs, and contact channels related to MailFleet.
• Does not replace stricter contractual terms you accept with clients, employers, or providers.

Permitted use of MailFleet

MailFleet is designed for teams that send email through their own providers under their own brands with appropriate permission from recipients. Permitted use includes permission-based marketing, newsletters, product announcements to opted-in audiences, client campaigns where you have documented authority and compliance oversight, and operational mail that your counsel recognizes as lawful in relevant jurisdictions.

You may use MailFleet features — including provider profiles, template management, SpamAssassin pre-checks, capacity scoring, campaign logs, reports, and webhooks — to prepare, execute, monitor, and audit campaigns responsibly. Testing with small volumes to real inboxes you control or that belong to consenting testers is permitted when it supports deliverability preparation, not deception.

Agencies may use MailFleet for multiple clients when each engagement includes clear list ownership, consent documentation, suppression handling, and contractual assignment of compliance duties. Internal IT and operations teams may use MailFleet for approved organizational communications that meet policy and law.

• Permission-based campaigns with documented consent or another lawful basis.
• Client work where contracts define compliance responsibilities and list provenance.
• Deliverability testing with authorized recipients and honest content.
• Operational workflows: logs, exports, webhooks, and reporting for legitimate business needs.
• Connecting to SMTP and API providers you are authorized to use.

Prohibited conduct

The following activities are prohibited when using MailFleet, regardless of jurisdiction or intent. They harm recipients, damage shared email infrastructure, and violate the purpose for which MailFleet was built.

You may not send unsolicited bulk email (spam), use purchased or scraped lists, harvest addresses from websites or directories, run dictionary attacks, or message recipients who have unsubscribed or complained without a lawful exception your counsel documents. You may not phish, distribute malware, promote illegal goods or services, harass, threaten, or facilitate fraud.

Deceptive practices are forbidden: forged headers, hidden or misleading sender identity, subject lines designed to trick recipients, impersonation of brands or individuals, and content that misrepresents affiliation with MailFleet, Secuno LLC, or third parties. Attempts to evade abuse controls, law enforcement requests, court orders, or provider suspensions are prohibited.

• Unsolicited bulk email or campaigns without permission or lawful basis.
• Purchased, rented-without-consent, scraped, or harvested address lists.
• Phishing, credential theft, malware, ransomware, or exploit delivery.
• Harassment, threats, hate speech, or content violating criminal or civil law.
• Deceptive sender identity, forged routing, or misleading subject lines.
• Circumventing provider blocks, spam filters, or MailFleet enforcement actions.
• Sending on behalf of third parties without authority and compliance oversight.

Email compliance and the Anti-Spam Policy

Email-specific compliance requirements — including consent documentation, list hygiene, unsubscribe handling, SPF/DKIM/DMARC alignment, complaint management, and regulatory references — are detailed in our Anti-Spam Policy. That policy is incorporated by reference into this AUP. If your sending practices violate the Anti-Spam Policy, you violate this AUP as well.

Operators must comply with CAN-SPAM (United States), GDPR and ePrivacy (EU/UK), CASL (Canada), and all anti-spam and data protection laws applicable to recipients and your business. MailFleet provides controls that support responsible sending; it does not automate legal compliance or guarantee inbox placement.

When enterprise procurement teams evaluate MailFleet, they should review both this AUP and the Anti-Spam Policy together with the Security page and Privacy Policy for a complete picture of vendor expectations and product architecture.

• Read and follow the MailFleet Anti-Spam Policy for email-specific rules.
• Maintain suppression lists for unsubscribes, complaints, and hard bounces.
• Honor opt-out requests promptly; faster than regulatory minimums is recommended.
• Authenticate sending domains and monitor reputation before scaling volume.

SMTP, API, and third-party provider rules

MailFleet connects to SMTP relays and HTTP APIs operated by third parties — including cloud email services, transactional providers, and self-hosted mail servers. Each provider publishes acceptable use terms, rate limits, and abuse policies. You must comply with those terms in addition to MailFleet rules.

You may not use MailFleet to exceed provider quotas through deceptive rotation, credential sharing that violates provider contracts, or deliberate misrepresentation of message type (for example, labeling marketing mail as purely transactional to bypass rules). If a provider suspends your account, do not use MailFleet to continue the prohibited activity through alternate paths without resolving the underlying violation.

API keys, SMTP credentials, and webhook signing secrets must be stored securely on devices running MailFleet. Rotate credentials when staff depart, clients offboard, or compromise is suspected. You are responsible for activity performed with credentials configured in your installation.

Acceptable use of proxy and routing features

MailFleet supports proxy profiles — including master proxy assignment, campaign-specific routing, and managed network profile selection across approved endpoints — for legitimate operational needs. Examples include agency workflows with client-approved egress paths, network separation required by internal IT, and structured testing through designated gateways.

Proxy features are not licensed for abuse. You may not use proxies to hide unsolicited mail, evade IP or domain reputation consequences, bypass provider suspensions, or obscure true sending context from recipients or investigators. Using proxies to defeat spam filters or law enforcement oversight violates this AUP.

Document why each proxy profile exists, which clients or environments it serves, and who approved its use. When routing errors appear in campaign logs, investigate before increasing volume.

• Permitted: approved client routing, IT-mandated gateways, structured operational separation.
• Prohibited: filter evasion, concealment of abuse, rotation to dodge provider enforcement.
• You supply proxy infrastructure; MailFleet does not provide proxy servers.
• See proxy management documentation and the Anti-Spam Policy for related guidance.

Software license integrity and technical restrictions

Your MailFleet license grants limited rights to use the desktop application per the Terms of Service. You may not reverse engineer, decompile, or modify the software to remove compliance controls, bypass license validation, or redistribute the application except as expressly permitted in writing.

You may not use MailFleet to develop tools whose primary purpose is spam, list harvesting, filter evasion, or credential theft. You may not scrape mailfleet.app, overload support channels with automated requests, or attempt unauthorized access to MailFleet systems, license servers, or other users' data.

Security researchers who discover vulnerabilities should report them responsibly through our contact page with type "security." Do not exploit issues against production systems or customer devices without authorization.

Content and messaging standards

Message content must be honest and lawful. Marketing mail should clearly identify the sender, relate to the permission the recipient granted, and include required physical address and unsubscribe mechanisms where regulations apply. Do not disguise advertisements as personal messages, fake replies, or urgent security alerts unless they are genuine security communications from your organization.

Attachments and links must not deliver malware, unwanted software, or deceptive landing pages. Affiliate promotions, financial offers, and health claims face heightened scrutiny from mailbox providers and regulators — ensure you have appropriate permissions, disclosures, and legal review.

MailFleet SpamAssassin checks help identify content signals associated with spam; passing a check does not certify legal compliance or inbox placement. Use human review for sensitive campaigns.

Volume, rate limits, and infrastructure respect

Responsible operators ramp volume gradually, monitor bounce and complaint rates, and pause campaigns when signals degrade. MailFleet sending capacity scoring helps estimate safe throughput; ignoring sustained warnings and blasting at rates your providers cannot support violates both provider terms and this AUP.

Do not use MailFleet to degrade third-party infrastructure through deliberate mail bombs, list bombing, or coordinated harassment campaigns. Do not target individuals or organizations with high-frequency unwanted messages.

If webhooks or automations trigger external systems, ensure failures do not loop into runaway send volume. Design idempotent handlers and circuit breakers for production integrations.

Agency, consultant, and multi-client responsibilities

If you manage campaigns for clients using MailFleet, you remain responsible for ensuring each client's lists, content, and practices meet this AUP and applicable law — even when the client supplies the data. Contracts should define who maintains consent records, handles complaints, and pays for remediation when issues arise.

Separate client data logically: distinct provider profiles, suppression practices, templates, and reporting where possible. During client offboarding, export or delete data per agreement and remove credentials from MailFleet profiles.

Do not use one client's permission to market another client's offers without explicit consent. Cross-client list merging is a frequent source of compliance failures and is prohibited without documented authorization.

• Document client authority to send on their behalf.
• Include AUP and anti-spam obligations in contracts and SOWs.
• Maintain per-client suppressions and complaint handling paths.
• Enterprise procurement support: contact us via mailfleet.app/contact.

Data handling and workstation security

Campaign lists, templates, logs, and provider credentials are stored locally on devices running MailFleet by default. You are responsible for securing those workstations: disk encryption, access controls, backups, patch management, and physical security appropriate to the sensitivity of your data.

License validation communicates with MailFleet services using encrypted connections; campaign content is not uploaded to MailFleet servers for normal operation. When you export reports or configure webhooks, protect data in transit and at receiving endpoints.

Personal data in lists must be processed according to applicable privacy law and our Privacy Policy. Do not collect or use sensitive categories of data in campaigns unless you have a lawful basis and appropriate safeguards.

Website, tools, and support channel use

The mailfleet.app website, free diagnostic tools, documentation, and contact forms must be used lawfully. Do not submit false abuse reports, spam our contact forms, scrape content at disruptive rates, or use tools to probe third-party infrastructure without authorization.

Support inquiries should be truthful and relevant. Do not request assistance with activities that violate this AUP. We may decline support for accounts or licenses under investigation for abuse.

Monitoring, investigation, and enforcement

We may investigate suspected violations using abuse reports, provider referrals, technical signals, and information you provide during support. Enforcement is proportionate to severity and history: informal warnings, required remediation plans, temporary license suspension, permanent termination, and cooperation with providers or lawful authorities when appropriate.

Egregious or repeated violations — including phishing, malware distribution, large-scale unsolicited mail, or deliberate deception — may result in immediate suspension without prior warning. Good-faith operators who promptly remediate root causes are treated differently from intentional abusers.

If you believe enforcement action was taken in error, contact us with consent records, suppression evidence, and corrective steps. We review appeals in good faith but are not obligated to restore access when risk to recipients or infrastructure remains.

• Report abuse to [email protected] with headers, timestamps, and samples when available.
• We may suspend licenses pending investigation.
• Termination does not limit other remedies available under the Terms of Service or law.
• Continued use after suspension or termination may violate computer fraud and access laws.

How to report violations

If you receive unwanted or abusive mail sent using MailFleet, or observe conduct that violates this AUP, report it to [email protected]. Include full message headers (if available), sending domain, approximate date and time, and a description of the violation. Reports with .eml samples or header text are processed faster.

For security vulnerabilities, use the contact form with inquiry type "security." For general legal or privacy questions, use the paths published on mailfleet.app/contact.

We do not disclose private investigation details to reporters, but we take credible abuse reports seriously and prioritize cases involving phishing, malware, and clear unsolicited bulk mail.

Relationship to other MailFleet policies

This Acceptable Use Policy should be read together with the Anti-Spam Policy, Terms of Service, Privacy Policy, Security documentation, and product documentation. Together they form the compliance framework for MailFleet products and services. If marketing materials conflict with these policies, the published policies control for conduct and compliance questions.

• Anti-Spam Policy — consent, list hygiene, authentication, and email-specific compliance.
• Terms of Service — license grant, billing, refunds, liability, and termination.
• Privacy Policy — data collection on the website, support, licensing, and local app data.
• Security & trust documentation — architecture, data handling, and enterprise review support.
• Documentation — operational guides for responsible sending and feature configuration.

Policy updates and contact information

We may update this Acceptable Use Policy as laws, provider expectations, product capabilities, or enforcement experience evolve. Material changes appear on this page with an updated modification date. Continued use of MailFleet after updates constitutes acceptance of the revised policy where permitted by law.

Secuno LLC operates MailFleet from 30 N Gould Street, Sheridan, Wyoming, USA 82801. Phone: +1 (315) 961-7074. General inquiries: [email protected].

For enterprise procurement, security questionnaires, or compliance alignment with sales scripts, contact us through mailfleet.app/contact. We answer with accurate documentation — we do not claim certifications or controls we have not implemented.

Summary

MailFleet exists so professional teams can run permission-based email campaigns with clarity, control, and accountability. This Acceptable Use Policy draws a clear line: legitimate business communication through your own providers is welcome; spam, deception, and infrastructure abuse are not.

Document consent. Send honest content. Respect provider rules. Secure your workstations. Use proxies and automation only for approved operational purposes. Stop sending when signals go wrong. Report abuse when you see it.

Questions about this policy: mailfleet.app/contact. Abuse reports: [email protected].