on_death() is an experimental service with community-driven support. While we provide best-effort assistance, please understand the limitations of our support capabilities for this research project.

Support Channels

📧 Direct Support

Email Support:

  • Best for: Account issues, billing questions, privacy concerns
  • Response time: Best effort, typically 3-7 days
  • Availability: Limited due to experimental nature
  • Language: English only

Note: Due to the experimental nature of this service, email support is provided on a best-effort basis with no guaranteed response times.

Contact Information

🐛 Bug Reports

Found a bug or issue?

Create GitHub Issue

💡 Feature Requests

Have an idea for improvement?

Start Discussion

📧 All Support Inquiries

For all questions and issues (technical, billing, legal)

support@ondeath.dev

🔒 Privacy & GDPR

Data requests, GDPR rights, privacy concerns

privacy@ondeath.dev

📖 Documentation

Technical documentation?

man.ondeath.dev

Response Times

Expected Response Times

  • GitHub Issues: 1-3 days (community-driven)
  • GitHub Discussions: 1-2 days (community-driven)
  • Email Support: 3-7 days (best effort)
  • Security Issues: 24 hours acknowledgment
  • Privacy Requests: 30 days maximum (legal requirement)

Priority Guidelines

  • High Priority: Security vulnerabilities, service outages, GDPR data requests
  • Medium Priority: Account issues, billing problems
  • Low Priority: Feature requests, general questions

Note: This is experimental software with no SLA guarantees. All support is provided on a best-effort basis.

Before Contacting Support

Check These Resources First

Information to Include

When reporting issues, please provide:

  • Account ID: Your account identifier (if applicable)
  • Timestamp: When the issue occurred
  • Error Messages: Any error codes or messages
  • Steps to Reproduce: What actions led to the issue
  • Expected vs. Actual: What you expected vs. what happened
  • Browser/Client: Software version and environment details

Community Guidelines

For GitHub Issues and Discussions

  • Search First: Check for existing issues before creating new ones
  • Be Specific: Provide detailed descriptions and reproduction steps
  • Stay on Topic: Keep discussions focused and relevant
  • Be Respectful: Maintain professional and courteous communication
  • Follow Templates: Use provided issue templates when available

Code of Conduct

All community interactions are governed by our Code of Conduct. We expect all participants to be respectful, inclusive, and constructive in their communications.