Reports by choice
omapkg does not collect automatic usage telemetry. A crash report is sent only when you complete the opt-in form.
What a crash report contains
The submission contains the release ID, the crash summary you enter, a consent flag, and consent version privacy-v1. It is recorded without a name, account ID, IP address, device inventory, file paths, environment variables, or background telemetry.
What to leave out
Do not include personal details, home paths, access tokens, private URLs, or complete log files in a summary. Describe the release, action, and visible failure in your own words.
How reports are used
Maintainers review reports scoped to a published release. They may resolve a report or move a release back to dev when the release policy requires it. Reports are kept with the package history so that release decisions have context.
Feedback is separate
Signed-in release feedback is attached to your account and the release. It is separate from anonymous crash reporting; the crash form does not use your GitHub identity.