Legal

CAN-SPAM Compliance

Effective date: 2026-04-29 · Version 1.0 · Sender: Ringdocket, a product of LIGHTHOUSE 27 LLC.

1. The four non-negotiables

Every email we send — marketing or transactional — contains:

1. Accurate, non-misleading From, Reply-To, and Subject fields. The From name is Ringdocket. The From address is a monitored mailbox at ringdocket.com. Subject lines describe the actual content.
2. Clear identification that the email is an advertisement when applicable. Transactional emails (account confirmations, receipts, password resets) are exempt from this requirement. Marketing emails (digest, impact report, Takedown Report reminders, Founding Flagger launch communications, product announcements) are commercial and are identified as such.
3. A physical postal address. See §2 below. This is a hard CAN-SPAM requirement — not optional, not conditional on email type. Every email, including transactional, carries this address.
4. A functioning opt-out mechanism. For marketing email, a one-click unsubscribe link that remains operational for at least 30 days after the email is sent. We use SendGrid's unsubscribe group feature so users can opt out of one category (for example, the weekly digest) without killing all email.

2. Physical address block

A physical postal address appears at the bottom of every Ringdocket email:

Ringdocket · LIGHTHOUSE 27 LLC
[PHYSICAL_ADDRESS]

3. "You received this email because…" block

Above the physical address block, every email explains why the recipient received it. We use the variant matched to the email type.

3.1 Weekly "Scam of the Week" digest

You received this email because you subscribed to the Ringdocket weekly
digest. We send one of these every Friday morning highlighting the most
reported scam campaign of the week.

Unsubscribe from the weekly digest: {{unsubscribe_url_group_digest}}
Manage all email preferences: https://ringdocket.com/account/email-preferences

3.2 Monthly personal impact report

You received this email because you have a Ringdocket paid subscription
and monthly impact reports are a benefit of your plan. This report
summarizes how your reporting activity contributed to the block list over
the past 30 days.

Unsubscribe from monthly impact reports: {{unsubscribe_url_group_impact}}
Manage all email preferences: https://ringdocket.com/account/email-preferences

3.3 Quarterly Takedown Report reminder

You received this email because your quarterly Ringdocket Takedown
Report is ready. This report shows the campaigns you helped flag and
the takedowns those reports contributed to.

Unsubscribe from quarterly Takedown Report notices: {{unsubscribe_url_group_takedown}}
Manage all email preferences: https://ringdocket.com/account/email-preferences

3.4 Transactional email

You received this email because of account activity on your Ringdocket
account. Transactional emails are not subject to marketing opt-out
because they are required to operate your account.

If you did not initiate this activity, please email [email protected]
immediately.

Manage marketing email preferences: https://ringdocket.com/account/email-preferences

3.5 Product announcement

You received this email because you created a Ringdocket account and
opted in to product announcements. These emails go out sparingly — we
won't pile on.

Unsubscribe from product announcements: {{unsubscribe_url_group_announcements}}
Manage all email preferences: https://ringdocket.com/account/email-preferences

4. Sender identification

Between the main email body and the "You received this email because…" block, every email carries:

Sent by Ringdocket, a product of LIGHTHOUSE 27 LLC.
Questions? Reply to this email or contact [email protected].

5. Full footer assembly (weekly digest example)

---
Sent by Ringdocket, a product of LIGHTHOUSE 27 LLC.
Questions? Reply to this email or contact [email protected].

You received this email because you subscribed to the Ringdocket weekly
digest. We send one of these every Friday morning highlighting the most
reported scam campaign of the week.

Unsubscribe from the weekly digest: {{unsubscribe_url_group_digest}}
Manage all email preferences: https://ringdocket.com/account/email-preferences

Ringdocket · LIGHTHOUSE 27 LLC
[PHYSICAL_ADDRESS]

6. What we never do

The following will create a CAN-SPAM violation, a deliverability problem, or both. None of them ship in any Ringdocket email:

• Misleading subject lines. No "Your refund is ready" when it isn't, no fake "RE:" prefixes, no subject lines that disguise marketing as personal mail. 15 U.S.C. §7704(a)(2).
• False From, To, or Reply-To fields. Ringdocket is always the identified sender. We never impersonate a user or a third party.
• Hidden unsubscribe links. The link is plainly visible — not behind an image, a CAPTCHA, or a multi-step flow. 15 U.S.C. §7704(a)(3).
• Login walls or confirmation emails to unsubscribe. Unsubscribe is processable from the email itself, in one click.
• Fees or required personal information to unsubscribe. No charges, no questionnaires.
• Sending marketing email more than 10 business days after an opt-out. SendGrid's unsubscribe group suppression handles this automatically.
• Selling, trading, or transferring the email addresses of users who opted out. Ever.
• Sending commercial email to addresses we did not collect with documented consent. No purchased lists. No scraped lists. No "we found you on LinkedIn" cold email from the product domain.
• Omitting the physical address block. See §2.
• Sending from a sender domain that is not authenticated with SPF, DKIM, and DMARC. Required for deliverability and to satisfy 2024 Google/Yahoo bulk-sender rules.
• Tracking pixels from non-HTTPS or third-party ad-tech vendors. SendGrid's first-party tracking is fine; advertising-style retargeting pixels are not.

7. Unsubscribe groups

Ringdocket maintains separate unsubscribe groups in SendGrid so a user who wants the weekly digest but not the monthly impact report (or vice versa) can opt out of one without losing the other. This is the best practice for preserving list health and reducing "mark as spam" rates.

Implementation notes for engineering: every marketing send sets the asm.group_id field to the matching group; SendGrid inserts the group-specific unsubscribe URL via the {{unsubscribe_url}} substitution tag. Transactional sends never set asm.group_id, so the marketing suppression list cannot block a password reset. We enable the List-Unsubscribe header (RFC 8058) and the List-Unsubscribe-Post: List-Unsubscribe=One-Click header on every marketing send.

8. Preference center

The "Manage all email preferences" link in every footer points to https://ringdocket.com/account/email-preferences, a logged-in page that shows the four marketing groups above with toggle switches. Users can opt out of any subset without affecting the others. A "turn off all marketing email" button is also provided.

9. Quick reference

10. Reporting a violation

If you received an email from Ringdocket that you believe violates CAN-SPAM — missing footer, broken unsubscribe, suspect content — email [email protected] with a copy of the message and the full headers. We treat these reports as P0 and investigate same-business-day.

End of CAN-SPAM compliance statement. For the full Privacy Policy see /privacy; for the Terms of Service see /terms.