# Developer contact email is verified

- **Pattern:** `ab-001357` (`extension-store-readiness.review-prep.developer-contact`)
- **Severity:** info
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-001357
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-001357)

## Why it matters

Chrome Web Store requires a monitored developer contact so users and the review team can report issues, abuse, and policy violations. An invalid or placeholder email (like `dev@example.com`) means user complaints go nowhere — the store's dispute escalation process routes through developer contact, and unresponsive developers are flagged for suspension. A real contact email is also how Chrome notifies you of impending policy violations before they become removals, making it a practical early-warning mechanism.

## Severity rationale

Info because a missing or placeholder contact email blocks user feedback and policy violation notifications but does not directly affect extension functionality or immediate submission.

## Remediation

Add a real, monitored contact email to your README and store listing. Avoid `@example.com` or role addresses you don't check daily.

```json
{
  "homepage_url": "https://yoursite.com"
}
```

In `README.md`:
```markdown
## Support

For bug reports or questions: support@yourdomain.com

We respond within 2 business days.
```

Use an address on a domain you own, not a Gmail alias — it signals legitimacy to reviewers. Set up email forwarding if needed so support requests reach you regardless of which inbox you monitor.

## Detection

- **ID:** `developer-contact`
- **Severity:** `info`
- **What to look for:** Count every contact email reference across the manifest, README, and documentation. Verify the email format is valid (contains `@` and a domain). If possible, verify it's a real, monitored email (not a placeholder like `dev@example.com`).
- **Pass criteria:** At least 1 valid contact email is provided in the manifest, README, or store listing, and appears to be real (not obviously a placeholder like dev@example.com). Quote the actual email found.
- **Fail criteria:** 0 contact emails found, or the email format is invalid.
- **Skip (N/A) when:** Never — contact information is required by Chrome Web Store.
- **Detail on fail:** `"No contact email provided in documentation"` or `"Email is 'dev@example.com' (appears to be placeholder)"`.
- **Remediation:** Add a contact email to your manifest or README:

  ```json
  {
    "homepage_url": "https://yoursite.com"
  }
  ```

  And document it in your README:

  ```markdown
  ## Support

  For questions, bug reports, or feedback, contact: support@yourdomain.com
  ```

## External references

- external chrome-cws-developer-contact — https://developer.chrome.com/docs/webstore/program-policies/developer-agreement/

Taxons: regulatory-conformance

HTML version: https://auditbuffet.com/patterns/ab-001357