Support
Find self-service help and prepare a useful, privacy-safe problem report.
Start in Troubleshooting, where each workflow has checks for common failures and stable reason codes.
Before asking for help
- Identify the action that failed and its visible outcome.
- Retry once only when the failure appears temporary.
- Record the exact reason code and approximate time with time zone.
- Confirm whether the same public URL works in a signed-out private browser window.
- Note the environment, browser, extension version, and affected reading list or device.
Use the complete problem report checklist so the issue can be reproduced without exposing account secrets.
Contact and service status
During the private beta, use the support channel supplied with your account invitation or extension release. A public support address and service-status page are not yet linked from the product. They will be documented here before public store distribution.
Do not guess an address or send sensitive information to an unverified contact.
Product feedback
For feature requests, describe the outcome you are trying to achieve, the current workflow, and why the existing behavior does not meet it. Include screenshots only after following the screenshot privacy checklist.