Deliverability & consent

Email should arrive because you expect it.

CoHavn uses email for account and household activity—not bulk advertising. This page explains what we send and how we protect recipients and our sending reputation.

Last updated August 19, 2026

1. What CoHavn sends

CoHavn sends transactional and service-related email connected to a person’s account or a direct interaction with us. Examples include:

  • Email-address verification and account recovery.
  • Security and sign-in notices.
  • Household invitations initiated by a CoHavn user.
  • Service notifications enabled through a user’s preferences.
  • Replies or confirmations related to a direct inquiry.

CoHavn does not buy, rent, scrape, or trade email lists. We do not send third-party promotions or unsolicited bulk marketing.

2. How recipients are added

An address enters CoHavn’s email flow when a person provides it to create or manage an account, when a current user initiates a household invitation, or when someone contacts us directly. We do not import third-party prospect lists.

Account addresses must complete the verification steps required by the authentication flow before they are treated as verified. A household invite is tied to an action taken by a current user and is not permission for unrelated marketing.

3. Preferences and stopping messages

Optional app notifications can be managed through CoHavn’s settings as those controls become available for each feature. Messages necessary to secure or administer an active account—such as verification, recovery, or security notices—may not include an unsubscribe link because they are triggered by the recipient’s request or are required to operate the account safely.

If you receive a household invitation you did not expect, do not use its code or link. You can report it through our contact form.

4. Delivery and reputation controls

CoHavn sends application email through Amazon Simple Email Service (SES). Our sending setup uses domain authentication, including DKIM, SPF alignment, and DMARC policy records, and requires encrypted TLS connections where supported by the mail path.

SES account-level suppression is enabled for bounce and complaint feedback. Suppressed destinations are not repeatedly retried through ordinary sending flows. We review delivery health and will pause or narrow sending if bounce or complaint signals indicate a problem.

5. A controlled release approach

CoHavn is in a private beta. Email volume is expected to begin low and grow with verified accounts and real household activity. We will expand sending gradually, observe delivery results, and use the least amount of email needed to support the product.

6. Report an unexpected message

Use the CoHavn contact form and choose “Unexpected email or abuse.” Include the recipient address, the message subject, and when it arrived. Do not send passwords, verification codes, or full message headers containing sensitive data unless we specifically request a safe method.

We will use the report to investigate the recipient source, suppress further inappropriate mail when needed, and correct the underlying sending flow.