Privacy Policy

Automatic Update Checks

A standard PLVS build checks for updates when the app starts and every 12 hours while it remains open. You can also start a check from Settings. The request retrieves the signed latest.json manifest from GitHub Releases. Preview builds compile the updater out.

The request does not contain audio, measurements, feedback, or a PLVS user identifier. Like any web request, GitHub receives network information such as your IP address and request headers and handles it under the GitHub Privacy Statement. PLVS does not keep a separate update-check history.

Newsletter Subscriptions

If you subscribe, PLVS collects the email address you enter, a random confirmation and unsubscribe token, your subscription status, and creation, confirmation, and unsubscribe timestamps. This data is used only to confirm the subscription, send PLVS release news, and process unsubscription.

Subscriber records are stored in a self-hosted SQLite database. Confirmation messages and newsletters are sent through Amazon Simple Email Service (Amazon SES), currently configured in the us-east-1 region. An unsubscribe request changes the record to “unsubscribed” so no further newsletter is sent; it does not automatically erase the record. Subscriber records remain until you request deletion.

Feedback

Feedback is sent only when you select Send. The request contains the text you wrote and, if supplied, your reply email. Diagnostics are off by default. If you select Attach Diagnostics, the request also contains the PLVS version, operating system, processor architecture, and the last 200 PLVS log lines. Home-directory paths are redacted before diagnostic logs leave the device. Log lines can still contain device labels, application events, and other paths, so review this choice before sending.

The receiving service adds the request origin and user-agent header to the email for troubleshooting. It uses the source IP temporarily to enforce a limit of five requests per minute. Application request logging is disabled, and request bodies are not written to the subscriber database.

Crash Reports

PLVS saves crash reports locally whether or not prompting is enabled. A report can contain a report and session identifier, creation time, crash type, PLVS version, operating system, processor architecture, error message, source location, stack or component stack, and the last 200 lines from the crashed session. Home-directory paths are redacted. You can inspect the exact request before sending it and optionally add a note and reply email. Logs and error details can contain device labels, application events, and other paths.

Nothing is sent until you select Send. After a successful send, or if you select Don’t Send, that local pending report is deleted. Later keeps it on the device. PLVS keeps at most the newest five local crash reports across the prompted and suppressed queues. Its local application log rotates at 2 MB and keeps up to three log files.

How Feedback and Crash Reports Are Handled

The self-hosted service at list.plvs.soundoer.com validates Feedback and Crash Report requests and sends them through Amazon SES to the PLVS maintainer’s mailbox. They are used to answer users, diagnose defects, and improve PLVS. They are not added to the newsletter database, used for advertising, or sold.

The service does not have an automated retention schedule for those mailbox copies; they remain until the maintainer deletes them or fulfills a deletion request. Amazon may process message data as the email provider. See the AWS Privacy Notice.

Website

The website is hosted on GitHub Pages. It does not set PLVS analytics or advertising cookies. The download section requests the latest public release metadata from the GitHub API. GitHub may process ordinary server and network data under its own privacy statement.

Deletion Requests and Contact

To request access to or deletion of a newsletter record, Feedback message, or Crash Report, email xichen@soundoer.com. Send the request from the same email address when one was provided. For a submission without an email address, include the approximate submission time and, for a Crash Report, its report identifier; otherwise it may not be possible to identify the message reliably.

The unsubscribe link in every newsletter stops future newsletter delivery. Contact the same address for privacy questions or to request full deletion of the retained subscriber record.

Changes to This Policy

Material changes will be published at this stable URL with a new effective date. The source for this page is versioned with PLVS so its statements can be checked against the shipped implementation.