Rovax
Legal

Acceptable Use & Anti-Spam Policy

The rules for using Rovax and agent email responsibly, and how to report abuse.

Last updated: October 27, 2026

Ler em português

This Acceptable Use & Anti-Spam Policy supplements the Terms of Service and the Privacy Policy of Rovax (TIMELY.AI TECNOLOGIA DA INFORMACAO LTDA., CNPJ 63.091.959/0001-08). It applies to all Users of the Platform and, in particular, to email sent and received by agents on the mail.rovax.io domain.

1. General principle

Rovax is an AI agent platform for businesses. Agent email exists for transactional, one-to-one (1:1) communication the User genuinely wants to carry out, never for bulk sending. The User is responsible for everything their agents send on their behalf.

2. How sending works

  • Each agent may have its own @mail.rovax.io address (the agent inbox), created by the account-owning User.
  • Sending happens only at the User's explicit request in a conversation, or in an automation the User configured. Agents do not start campaigns on their own.
  • Every send goes through automated review. Higher-risk sends (for example, with attachments or a modified Reply-To) require human approval, through an approval card, before they go out.
  • Expected use includes replies, sign-ups, confirmations and contact with people the User has indicated.

3. Prohibited uses

You may not use Rovax to:

  • send bulk marketing or unsolicited commercial email;
  • use purchased, rented, scraped or otherwise acquired lists with no legitimate relationship to the recipient;
  • conduct high-volume cold outreach;
  • engage in phishing, fraud, scams, or attempts to obtain credentials or financial data;
  • spoof the sender, headers or origin, or impersonate another person or organization;
  • send deceptive content, or use false subject lines or identification;
  • send messages to anyone who asked not to receive them, or circumvent suppressions by using another address, agent or account;
  • send unlawful content, malware, content that incites violence, hatred or exploitation, or that infringes third-party rights;
  • hide the sender's identity or remove opt-out mechanisms where required by law;
  • attempt to bypass the Platform's reviews, approvals, limits or controls.

4. Sender requirements

The User must:

  • send only to recipients with whom they have a legitimate relationship or who requested the communication, maintaining an adequate legal basis (LGPD and, where applicable, GDPR);
  • identify themselves clearly in messages and use subjects and content that accurately reflect the purpose of the message;
  • comply with the CAN-SPAM Act and other applicable electronic communications laws, including sender identification and an opt-out mechanism where required;
  • promptly honor opt-out requests.

5. Authentication, bounces, complaints and suppression

  • The mail.rovax.io domain is authenticated with DKIM, SPF and DMARC with a p=reject policy.
  • Inbound messages are scanned for spam and viruses.
  • Bounces and complaints are received through Amazon SNS and trigger automatic suppression of the recipient. A suppressed recipient receives no further sends.
  • Opt-out requests are honored. A recipient may reply to the message asking for removal, which the User must honor, or write to [email protected], and Rovax will suppress the address.

6. Limits, monitoring and enforcement

Rovax monitors abuse signals and sending health, including bounce and complaint rates. We may apply sending limits and may suspend or terminate the sending ability of accounts with elevated bounce or complaint rates or suspected abuse, and we may suspend or terminate the account under the Terms of Service. In case of serious violation or immediate risk, action may be taken without prior notice. Rovax may cooperate with infrastructure providers (such as AWS) and competent authorities.

7. Reporting abuse

If you received a message sent by a Rovax agent that violates this Policy, or you wish to stop receiving messages, write to [email protected] with the subject "Abuse" and, if possible, include the full message headers. We review reports and, when confirmed, suppress the recipient and take appropriate action against the responsible account.

8. Retention and privacy

Stored email content is retained for 90 (ninety) days and then automatically deleted, and data is scoped per company. See the Privacy Policy for details.

9. Changes

We may update this Policy. The current version and its last-updated date are always on this page.