Coroov BYOA Terms (Bring Your Own AWS)

Last updated: August 5, 2026

These BYOA Terms (the “BYOA Addendum”) govern your use of Coroov in a Bring Your Own AWS (“BYOA”) configuration, where Coroov connects to and operates within Amazon Web Services infrastructure that you own and control. This Addendum supplements and is incorporated into the Coroov Terms of Service (the “Agreement”) and the Privacy Policy. Capitalized terms not defined here have the meaning given in the Agreement. For BYOA matters, if this Addendum conflicts with the Agreement, this Addendum controls.

1. Definitions

“AWS” means Amazon Web Services. “SES” means Amazon Simple Email Service. “IAM Role” means the AWS Identity and Access Management role you authorize Coroov to assume, scoped by a unique “External ID.” “Customer Data” means data you send, store, or process through Coroov, including contacts, message content, and campaign data. “Operational Metadata” is described in Section 8.

2. Scope and Relationship to the Agreement

These BYOA Terms apply whenever Coroov is connected to customer-controlled AWS infrastructure. They supplement, and do not replace, the Agreement. Except as expressly modified here for BYOA, all terms of the Agreement — including limitation of liability, warranties, governing law, and dispute resolution — continue to apply.

3. Your AWS Account and Responsibilities

You are solely responsible for your AWS account and everything within it, including: (a) account ownership, credentials, and billing; (b) IAM users, roles, and permissions; (c) network, encryption, and security configuration; (d) resource and quota management, including Amazon SES sending limits, production-access (sandbox) status, and domain or dedicated-IP configuration; and (e) your own legal and regulatory compliance within your environment. You are responsible for keeping AWS credentials secure and for the acts of anyone you permit to access your account.

4. Coroov Access and Least Privilege

To provide the BYOA service, Coroov assumes a customer-authorized IAM Role scoped by an External ID, and uses it only to perform setup, verification, sending, monitoring, and related operations you request through the service. You are responsible for reviewing and limiting the permissions you grant, and you may narrow or revoke that access at any time. Coroov will not use your AWS access to provide services to any other customer and will use it solely to operate the service for you.

5. AWS Costs and Billing Separation

BYOA means you pay AWS directly for all AWS usage, including SES sending, data transfer, storage, and any other AWS charges. Coroov subscription and credit charges are separate and are billed by Coroov. Coroov is not responsible for AWS charges of any kind, including unexpected, elevated, or fraudulent charges in your account. You are responsible for monitoring your AWS spend and configuring your own budgets, alerts, and limits.

6. Sending, Deliverability, and Sender Responsibilities

In a BYOA configuration, you are the sender of record. You are responsible for the content of your messages; for having a lawful basis and appropriate consent to contact your recipients; for honoring unsubscribe requests and suppression lists; and for complying with all applicable laws governing electronic communications and data (which may include, for example, the CAN-SPAM Act, GDPR, and CASL). Coroov provides tooling such as unsubscribe handling, suppression, and DKIM/authentication support, but does not guarantee inbox placement, deliverability, or sender reputation, which depend on your practices and third-party systems.

7. Acceptable Use

You must not use Coroov or your connected AWS infrastructure to send unsolicited bulk email (spam) or unlawful, deceptive, infringing, or harmful content, and you must comply with the AWS Acceptable Use Policy and the Amazon SES terms. Coroov may investigate suspected violations and act as described in Section 12 and the Agreement.

8. BYOA Operational Metadata

To operate and support the service, Coroov stores operational metadata about your BYOA connection, such as the IAM Role ARN, AWS account ID, region, CloudFormation stack name, connection status, configuration flags, and operational logs. This metadata is used for service operation, support, security, and troubleshooting, and is handled in accordance with the Privacy Policy.

9. Data Processing and Privacy

With respect to Customer Data, you act as the data controller and Coroov acts as a processor operating on your behalf and on your instructions, as further described in the Privacy Policy and any applicable data processing terms. Customer Data that resides in your AWS infrastructure remains under your control. Each party will comply with the data protection obligations that apply to it.

10. Security

Coroov applies technical and organizational measures to protect access to your environment, including scoping access with an External ID and safeguarding stored credentials and secrets. You are responsible for security on the AWS side, including enabling MFA, maintaining IAM hygiene, and configuring network and encryption controls. You will promptly notify Coroov of any suspected compromise affecting the BYOA connection.

11. Service Dependencies and Availability

The BYOA service depends on AWS and other third-party systems that Coroov does not control. Coroov is not responsible or liable for AWS outages, throttling, SES suspension or policy changes, or other third-party actions. Changes to your AWS permissions or configuration may interrupt or disable the service until corrected. Any service levels are as stated in the Agreement; nothing here creates an availability guarantee beyond it.

12. Suspension and Termination

Coroov may suspend or terminate the BYOA connection or your access where reasonably necessary to address a security risk, suspected abuse or unlawful use, non-payment, or a violation of the AWS or SES terms, consistent with the Agreement. On termination of BYOA, you should revoke the IAM Role and External ID. Customer Data stored in your AWS infrastructure remains with you; Coroov will delete or return Operational Metadata in accordance with the Privacy Policy and its retention practices.

13. Warranties and Disclaimers

Except as expressly stated in the Agreement, the BYOA service is provided “AS IS” and “AS AVAILABLE.” Coroov disclaims all warranties to the fullest extent permitted by law, including any warranty of deliverability, uninterrupted or error-free operation, or the performance or availability of AWS or other third-party services.

14. Limitation of Liability

The limitations and exclusions of liability in the Agreement apply to these BYOA Terms. Without limiting them, Coroov is not liable for AWS charges, for the acts, outages, or decisions of AWS or other third parties, or for loss arising from your AWS configuration, credentials, or the content you send.

15. Indemnification

To the extent set out in the Agreement, you will defend, indemnify, and hold harmless Coroov from claims, damages, and costs arising out of (a) the content you send, (b) your AWS account, credentials, or configuration, and (c) your violation of applicable law or of any third-party terms, including the AWS and SES terms.

16. Changes to These Terms

Coroov may update these BYOA Terms from time to time. For material changes, Coroov will provide reasonable notice through the service or by email. Your continued use of the BYOA service after the changes take effect constitutes acceptance.

17. Contact

For BYOA support or questions about these terms, contact support@coroov.com.