Legal
Acceptable Use Policy
RouteWrk lets your workflows send email on your behalf. This policy sets out how that capability may and may not be used, and what happens when it's misused.
Contents
This Acceptable Use Policy ("Policy") applies to all use of RouteWrk's email-sending and workflow-automation capabilities, and is incorporated by reference into our Terms of Service. It exists to protect recipients from unwanted email and to protect RouteWrk's ability to deliver mail reliably for every customer. Violating this Policy is a violation of the Terms.
1. Scope
This Policy governs any email sent through a RouteWrk workflow, whether triggered manually, by an incoming ticket, or by an automation node, regardless of the mailbox (Gmail or Outlook/Microsoft 365) used to send it. It also governs use of workflow nodes that make outbound requests to systems outside RouteWrk.
2. Mandatory email controls
Every email RouteWrk sends on your behalf automatically includes:
A report-abuse link, on every outbound email without exception
An unsubscribe link on bulk sends, with RFC 8058 one-click unsubscribe headers so mailbox providers can honor it automatically
These elements cannot be removed, hidden, or disabled through workflow configuration, custom templates, or any other setting. This is enforced at the platform level, not left to customer discretion.
3. Suppression & bulk-send detection
Suppression list
Once a recipient unsubscribes or reports abuse, RouteWrk automatically blocks all future sends to that address for that organization. This is enforced platform-wide and cannot be overridden by workflow configuration.
Bulk-send detection
When a workflow node's sends to distinct recipients cross a threshold within a rolling window, RouteWrk automatically escalates the visible unsubscribe footer on those sends. This exists specifically to catch marketing-style blasts sent through workflow automation rather than through a dedicated marketing tool, and applies regardless of how the workflow is configured.
4. Prohibited uses
Regardless of workflow configuration, you may not use RouteWrk to:
Send to purchased, scraped, or rented contact lists
Send to recipients who have not opted in or do not have an existing relationship with you
Send phishing email or otherwise misrepresent the identity of the sender
Distribute malware or abuse email attachments in any way
Use any workflow node, including the http_request node, to attack, scan, or probe third-party systems
5. Automated systems & the http_request node
The http_request workflow node lets your workflows call external services. It is guarded server-side against server-side request forgery (SSRF), but that guard is a technical safeguard, not permission: using this node, or any other RouteWrk feature, to attack, scan, overload, or gain unauthorized access to third-party systems is prohibited regardless of whether the underlying request is technically blocked.
6. Reporting abuse
Every RouteWrk email includes a report-abuse link. Clicking it logs the report and immediately suppresses future sends to that address for the sending organization. This happens automatically, without waiting on human review.
We don't yet have a dedicated trust & safety team reviewing every report on a fixed timeline, so we can't commit to a specific human response time. Suppression itself is instant and automatic for every report.
7. Enforcement
Per-recipient suppression is automatic and immediate, as described above. Beyond that:
Repeated violations by a single workflow or user can result in suspension of that workflow's or user's send privileges
Org-wide or severe violations can result in suspension or termination of the account, per our Terms of Service
8. Changes to this policy
We may update this Policy as our email and automation capabilities evolve. We'll give at least 14 days' notice of material changes by email, consistent with our Privacy Policy.
9. Contact
Questions about this Policy, or to report abuse outside of the in-email link, contact us through our contact form.