fix(emails): BCC scrape-alert recipients — never a shared cross-tenant To: line

[sweetmantech]

Summary

The "{artist} has new posts on Instagram" alert resolved every watcher of a social across all customer accounts into a single visible To: line — live evidence on the tracking issue shows a customer manager, an internal account, and a label contact (sam.palm@wmg.com) all mutually visible on one send. This PR hard-codes the privacy boundary: to is always our own from-address (Resend requires non-empty to), all recipients ride bcc.

Tracking issue: recoupable/chat#1855 (PR #1 of 6 — ships first and alone; nothing gates it).

What changed

• lib/apify/sendApifyWebhookEmail.ts: to: [RECOUP_FROM_EMAIL] + bcc: emails (the Resend wrapper already passes bcc through natively — no wrapper change).
• lib/apify/__tests__/sendApifyWebhookEmail.test.ts (new): asserts recipients land in bcc, and a guard-rail test that to/cc never contain more than our own address regardless of recipient count — so a future platform copy-paste can't reintroduce the leak.

Tests

RED→GREEN: 2 new assertions failed against the old implementation (to: emails), pass after (3/3). eslint clean.

🤖 Generated with Claude Code

---

Summary by cubic

Fixes a privacy leak in Instagram scrape-alert emails by moving all recipients to BCC and setting To to our own sender address. Prevents cross-tenant addresses from being visible to each other (recoupable/chat#1855).

• Bug Fixes
  • Update sendApifyWebhookEmail to use to: [RECOUP_FROM_EMAIL] and bcc: emails.
  • Add tests enforcing BCC-only recipients, to/cc limited to our address, and no send when recipient list is empty.

^{Written for commit f178c94. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api	Ready	Preview	Jul 6, 2026 9:54pm

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

@sweetmantech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 57f33e58-9270-429d-a92d-022bea08c7cd

📥 Commits

Reviewing files that changed from the base of the PR and between 7ed9338 and f178c94.

⛔ Files ignored due to path filters (1)

• lib/apify/__tests__/sendApifyWebhookEmail.test.ts is excluded by !**/*.test.*, !**/__tests__/** and included by lib/**

📒 Files selected for processing (1)

• lib/apify/sendApifyWebhookEmail.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/scrape-alert-bcc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

Architecture diagram

sequenceDiagram
    participant Caller as Apify Webhook
    participant Handler as sendApifyWebhookEmail
    participant Wrapper as sendEmailWithResend
    participant Resend as Resend API

    Note over Caller,Handler: Privacy boundary: watchers from different tenants

    Caller->>Handler: sendApifyWebhookEmail(profile, emails)

    alt emails is empty
        Handler-->>Caller: return null (no email sent)
    else emails non-empty
        Handler->>Handler: generate email body from profile

        Note over Handler: To: always our own address<br/>BCC: all recipients (cross-tenant safe)

        Handler->>Wrapper: sendEmailWithResend({ to: [RECOUP_FROM_EMAIL], bcc: emails, ... })

        Wrapper->>Resend: POST /emails (to=bcc set)
        Resend-->>Wrapper: success response
        Wrapper-->>Handler: result (e.g., { id })

        Handler-->>Caller: return result
    end

Loading

<sub>Auto-approved: Fixes email privacy by moving all recipients to BCC; adds tests for the new behavior. Small, isolated change with low risk.

Re-trigger cubic</sub>