What we send, who receives it, and how to stop it.

Who sends the mail

All email described here is sent by HonorLabs, the internal technology team of Honor Health Network, from addresses at the honorlabs.io domain. Every message identifies HonorLabs as the sender, states why the recipient is receiving it, and includes a working reply path to a monitored inbox.

What we send

Transactional and system notifications

Account and security messages generated by our internal applications — sign-in verification, password resets, permission changes, task assignments, and system alerts. Sent only to authenticated users of the tool that generated them, as a direct result of their own activity or an event in their account.

Operational messages to staff and agencies

Messages to employees, contractors, and agency staff of Honor Health Network about the systems they use — schedules, assignments, service changes, maintenance windows, and outages. Recipients receive these because of their working relationship with the network, not because of a public sign-up.

Automated reports and digests

Scheduled summaries, exports, and recurring digests delivered to internal users who requested them or whose role requires them. Each digest can be turned off by its recipient without affecting their account.

Announcements and newsletters

Periodic updates about our work, new tools, and changes worth knowing about. This is the only category we treat as promotional, and it is sent only to recipients who explicitly opted in. It always carries a one-click unsubscribe.

How people end up on a list

We use exactly three routes, and no others:

1. Account creation. A person is provisioned an account in one of our internal tools by their organization, and receives the transactional mail that account generates.
2. Working relationship. A person is an employee, contractor, or agency staff member of Honor Health Network and receives operational messages about the systems their work depends on.
3. Explicit opt-in. A person affirmatively subscribes to announcements or a recurring digest, through a form or a preference setting they controlled. We record the date and source of that opt-in.

Unsubscribing and preferences

• Every announcement, newsletter, and recurring digest includes a working unsubscribe link in the message and supports one-click unsubscribe via the List-Unsubscribe header.
• Unsubscribe requests are honored immediately and always within 10 days, as required by the CAN-SPAM Act. No confirmation step, login, or reply is required.
• Recipients can also unsubscribe or adjust their preferences by writing to support@honorlabs.io with the address to remove.
• Transactional and security messages tied to an active account — password resets, sign-in verification, critical service notices — cannot be unsubscribed while the account exists, because the account depends on them. Closing the account ends them.
• Suppression is permanent. An unsubscribed address is added to a suppression list and is not re-added to that mail stream by any later import or sync.

Bounces, complaints, and list hygiene

• Hard bounces are suppressed immediately and permanently. We do not retry a permanently failed address.
• Soft bounces are retried a limited number of times, then suppressed if delivery keeps failing.
• Spam complaints are treated as an immediate unsubscribe. The address is suppressed across the relevant mail stream and the complaint is reviewed.
• We monitor bounce and complaint rates continuously and hold them well below the thresholds set by our sending provider. If a rate rises, we pause the affected stream and find the cause before sending again.
• We process feedback loops and automated complaint reports from mailbox providers and act on them the same way.

Sending infrastructure and authentication

Our mail is sent through Amazon Simple Email Service (Amazon SES). The honorlabs.io domain is verified with our sending provider and authenticated with:

• SPF — published in DNS, authorizing our sending infrastructure.
• DKIM — every outbound message is cryptographically signed.
• DMARC — published with a reporting address so we see authentication failures and abuse of our domain.

We send from a dedicated domain we control, keep transactional and announcement traffic separated, and warm new sending volume gradually rather than in bursts.

Content standards

• Subject lines describe the actual contents of the message. We do not use deceptive subjects, headers, or sender names.
• Every message identifies HonorLabs and Honor Health Network as the sender.
• Commercial messages include a valid physical postal address and a clear unsubscribe mechanism.
• We do not send unsolicited commercial mail of any kind.

Data we keep about recipients

For each mail stream we retain the recipient address, the account or relationship it belongs to, the opt-in date and source where applicable, delivery and engagement events, and the suppression state. This data is used to deliver mail and to keep our lists clean. It is not sold, rented, or shared for anyone else's marketing. Our privacy policy covers this in full.

Reporting a problem

If you received mail from honorlabs.io that you did not expect, believe an address is being used without consent, or want to report abuse of our domain, write to support@honorlabs.io. Include the full message headers if you have them. We investigate every report and respond.