Security

If you believe you found a security issue, report it privately and share the minimum information needed to understand it.

Report a vulnerability

Email support@tinkerhowl.com. Use a concise subject line and do not send secrets or user data unless a secure transfer method is agreed first.

What to include

  • The affected page, app version, or component.
  • A concise description of the issue and its possible impact.
  • Minimal, non-destructive reproduction steps.
  • Your test environment and whether the issue remains reproducible.
  • A safe way to contact you if follow-up is needed.

What to avoid

  • Do not access, change, retain, or share another person’s data.
  • Do not degrade service, use social engineering, or test physical security.
  • Do not send passwords, tokens, private keys, health exports, photos, or backup files.
  • Do not publish exploit details before there has been a reasonable chance to investigate.

Scope and expectations

This page does not create a bug bounty, safe-harbor contract, payment promise, or guaranteed response time. Reporting terms may be revised as the publisher’s production systems change.

Website foundation

The site is static, has no form handler, account system, database, analytics, advertising, or third-party fonts. The site uses a restrictive meta Content Security Policy, a referrer policy, local assets, and no executable client script. Production hosting headers require their own configuration and verification; a meta policy must not be described as equivalent to a server header.