CODE_OF_CONDUCT.md

Rama main · réplica de lectura del repositorio original.

# Community code of conduct

WHOOP Personal MCP welcomes constructive participation from people of different
backgrounds and experience levels. Keep discussion focused on the software,
evidence, and the one-owner personal-wellness scope.

## Expected behavior

- Be respectful, specific, and patient.
- Critique ideas and code, not people.
- Protect privacy: use synthetic fixtures and redact credentials and wellness
  data.
- State uncertainty, especially for security, privacy, health, and legal topics.
- Respect the read-only, provider-neutral, non-medical project boundaries.
- Accept maintainer decisions about scope without harassment; forks remain
  available under the MIT License.

## Unacceptable behavior

- Harassment, threats, discrimination, sexualized conduct, or personal attacks.
- Publishing another person's private information or wellness data.
- Pressuring someone to disclose credentials, medical information, or identity.
- Knowingly presenting the project as medical advice, clinical clearance,
  officially endorsed by a named provider, or suitable for multiple people.
- Exploiting or publicly disclosing a vulnerability before a reasonable private
  reporting opportunity.
- Spam, coordinated disruption, or repeated bad-faith argument.

## Scope and enforcement

This applies in repository issues, pull requests, discussions, reviews, and
other spaces represented as project community channels. Maintainers may edit or
remove contributions, lock threads, reject changes, or temporarily/permanently
restrict participation when behavior undermines a safe and productive project.

For a confidential conduct concern, use the repository's
[private reporting form](https://github.com/josealvaradoa/whoop-personal-mcp/security/advisories/new)
and begin the title with `Code of Conduct report`. This reuses GitHub's private
advisory channel because the project does not publish a separate conduct
mailbox; it does not characterize the concern as a software vulnerability. Do
not post personal details in a public issue. For a security vulnerability, use
the separate instructions in [SECURITY.md](SECURITY.md).

There is no guaranteed response time or formal appeal process. Enforcement
decisions should be proportionate, documented when appropriate, and protect
reporters from retaliation. The project cannot provide emergency services or
investigate conduct outside its community spaces.