Help and contact

Contact & Support

Use these safe troubleshooting steps while the service owner configures verified support, privacy, grievance, and security-reporting channels.

Last reviewed 17 November 2026

Official contact status

No verified public support email, postal address, grievance officer, privacy contact, or security-reporting channel is defined in this repository. To prevent phishing and misdirected personal data, this page does not invent one.

Production blocker: the owner must publish verified support, privacy/grievance, accessibility, and security contacts with response expectations.

Before requesting help

  • Check your connection and retry once; the API may take longer to respond after an idle period.
  • For sign-in trouble, use the password-reset flow or retry Google sign-in from the official site.
  • For a coding issue, record the problem URL, selected language, visible error, and approximate time. Do not include access tokens or private test data.
  • For missing profile or progress data, confirm you are signed into the intended account before changing anything.
  • Never send a password, OTP, refresh cookie, access token, or full authentication screenshot to support.

Requests that need dedicated handling

  • Account access and security incidents.
  • Privacy access, correction, export, deletion, consent, or grievance requests.
  • Accessibility barriers and accommodation requests.
  • Copyright or trademark notices with enough detail to identify the material and the claimant’s authority.
  • Responsible security reports. Do not test production accounts, data, or infrastructure without written authorization.