Skip to content

Acceptable Use Policy

Effective Date: September 15, 2026

This Acceptable Use Policy ("AUP") sets the rules for using the sevk.io hosted email platform, including its dashboard, API, SMTP, and inbound email services. It forms part of our Terms of Service with SEZ YAZILIM DANIŞMANLIK TİCARET LİMİTED ŞİRKETİ ("sevk", "we", "us"). You are responsible for activity under your account, including email sent on behalf of your clients and anyone you authorize to use the Service.

1. Permission-Based Email

Marketing emails, newsletters, and promotional broadcasts may only be sent to recipients who have explicitly opted in to receive that type of email from the business identified as the sender. Consent to hear from one business does not authorize unrelated businesses to contact the same recipient.

  • Do not use purchased, rented, scraped, harvested, or automatically generated address lists, including lists supplied by a broker or lead-generation service.
  • Do not send unsolicited bulk email or cold outreach to people who have not opted in. A publicly listed email address or a business relationship alone is not marketing permission.
  • Keep records showing when, where, and how each recipient gave consent, what they agreed to receive, and which business they agreed to hear from. You must provide relevant evidence when we request it.
  • Importing a list from another provider does not remove your responsibility to establish consent and preserve its unsubscribe and suppression records.

2. Transactional Email

Transactional emails must relate to a recipient's request, account, transaction, or an existing service you provide to them, and have a valid legal basis. Examples include requested password resets, receipts, and necessary account notifications. Do not label promotional campaigns as transactional to bypass consent requirements, marketing opt-outs, or sending restrictions. A marketing opt-out does not itself prevent a necessary, lawful transactional message, but delivery and abuse suppressions must still be respected.

3. Unsubscribe Requests and List Hygiene

  • Every marketing email must include a clear, working unsubscribe link. Do not require a login, payment, or unnecessary personal information to unsubscribe.
  • Honor opt-outs promptly and stop further marketing to that recipient. Do not override their choice, re-import them as subscribed, or move them to another project or account to continue sending.
  • Preserve the unsubscribe links and headers provided by the Service. Do not remove, hide, or interfere with them.
  • Stop sending to addresses that hard-bounce or report your messages as spam. Keep your lists current and do not bypass suppression controls or repeatedly retry permanently failed addresses.

4. Sender Identity and Authentication

Send only from domains you own or are authorized to use, and complete the domain verification and email authentication required by the Service. Maintain the required DNS records and use accurate sender names, From and Reply-To addresses, subject lines, and business contact details. Do not impersonate another person or organization, forge headers, disguise the origin of a message, or use misleading links. Domain verification does not establish recipient consent.

5. Prohibited Content and Activity

You must not send, upload, knowingly host, or facilitate the following through the Service:

  • Phishing, credential theft, malware, ransomware, or harmful attachments and links, including simulated phishing campaigns through our email delivery service.
  • Fraud, scams, pyramid schemes, deceptive offers, or other unlawful activity.
  • Threats, harassment, incitement to violence or terrorism, or child sexual exploitation or abuse.
  • Content that infringes intellectual property, privacy, or other rights, including unauthorized disclosure of personal or confidential information.
  • Unauthorized access, denial-of-service activity, email bombing, or attempts to disrupt the Service or third-party systems.
  • Attempts to evade quotas, domain checks, suppression lists, account restrictions, or abuse enforcement by rotating identities, credentials, projects, or accounts.

6. Sending Quality and Enforcement

You must monitor delivery failures, complaints, and opt-outs, address their causes, and stay within the sending limits assigned to your account. A sending quota is a technical limit, not permission to send unwanted email.

We may investigate suspected violations using relevant delivery metrics, abuse reports, and account activity. We may request consent records, information about list sources and your business, sample messages, or corrective action. You must cooperate with these requests and provide accurate information.

Where your activity violates this policy or creates a delivery, security, legal, or reputational risk, we may reject messages, reduce sending limits, pause sending, or suspend or terminate access, including without prior notice where necessary. High bounce or complaint rates can trigger action even if your messages otherwise appear to meet these rules. Reinstatement may require evidence that the cause has been corrected. Data handling and refunds remain governed by the Terms of Service, DPA, and Refund Policy.

7. Applicable Laws and Provider Rules

You are responsible for complying with the privacy, electronic communications, advertising, and other laws that apply to you and your recipients. A legal basis for processing an address does not remove this policy's marketing opt-in requirements. Our Privacy Policy and DPA describe the parties' data protection responsibilities.

This policy applies to all email sent through sevk. You must also comply with the applicable delivery provider terms linked on our Subprocessors page.

8. Report Abuse

To report suspected spam, phishing, or other misuse of sevk, email support@sevk.io or use our contact form. Include the sender address, date, message ID or relevant email headers, and a brief description of the issue so we can investigate. Do not include passwords or API keys.

9. Changes to This Policy

We may update this policy as the Service, abuse risks, or applicable requirements change. The effective date is shown above. Material changes will be communicated as described in our Terms of Service.