DD Fake Podcast + Account Breach Response (Arseni, Mohammed) — January 12, 2026

Participants: Arseni, Mohammed Type: ops_call Approximate duration: 18 minutes Date logged: 2026-01-12 Notion: Not created from this environment

Action items

• Arseni — Tell David that iHouse will not grant or manage access for unverified third parties, especially from informal Gmail requests | Deadline: Jan 12 | Priority: urgent
• Mohammed — Document what was checked during the breach review and what access was exposed or stayed protected | Deadline: Jan 13 | Priority: urgent
• Ane — Learn the relevant account/system context so the team is not dependent on one person for future security incidents | Deadline: Jan 14 | Priority: normal

Topics covered

1. The "podcast" request turned out to be fake

The team realized David had been pushed toward a supposed podcast opportunity that was not legitimate. That confusion appears to have driven unsafe access requests and wasted time on non-billable coordination.

2. iHouse needs a harder security boundary around partner requests

Arseni was clear that the team should say no more often when unknown third parties ask for access or operational help through informal channels. The decision was to stop acting like David's investigator or security buffer for random people who have not been vetted.

3. Weekend cleanup consumed too much internal time

Mohammed described spending the weekend with additional team support checking systems and working through the consequences. The call effectively treated the incident as a process failure, not just a one-off annoyance.

Key quotes

— Arseni, re: boundary setting: "We just need to be careful and say more no."

— Arseni, re: unverified access requests: "We don't take this responsibility."

— Arseni, re: scope creep: "We are not David's private investigator."