Sharing the submission tracker may expose account email addresses
Source references: 3The template includes an “Account Email” field alongside each platform's status and public listing URL.
If the CSV is shared with contractors, published, or uploaded to a broad workspace, others could associate login emails with particular platform accounts for targeted phishing or account enumeration.
The tracker does centralize account email, submission status, and live URLs, and the output rules permit linking or including the CSV. If a populated tracker is shared publicly, it could expose an email address and campaign details. However, the source does not require publishing, uploading, or sharing the populated tracker and contains no real email. Exposure therefore depends on how the user stores and shares it. Users can keep account email out of shareable copies or treat the tracker as private.
This assessment concerns the code and conditions shown, not proof that harm has occurred.Directory,Tier,URL,Category,DR,Dofollow,Submission Date,Status,Live URL,Backlink Verified,Positioning Variant Used,Tags Used,Account Email,NotesProduct Hunt,1,https://producthunt.com/posts/new,Launch,91,Yes,,Draft,,,Startup,,,Hacker News (Show HN),1,https://news.ycombinator.com/submit,Launch,91,No,,Draft,,,Dev,,,Show 2 other places
Set up the tracker spreadsheet (`references/submission-tracker-template.csv`). Work left-to-right through it. 2–3 hours per batch is realistic.5. **Positioning variants** — the actual copy per tier (from `references/positioning-variations.md`)6. **PH 3-week prep timeline** — mapped to calendar dates if launch day known7. **Reviews 10-in-30 plan** — who to ask, when, how8. **Weekly targets** — directories submitted, reviews, DR movement9. **Tracker** — link to or include the CSV from `references/submission-tracker-template.csv`