Local-first.
Clear about connections.

The Android application

WizeStream does not require a WizeStream account and does not include advertising, analytics or tracking SDKs. Subscriptions, playlists, supported profile data and history are held locally or exported to a destination you choose.

This is a data-storage and feature-choice model, not a claim of network anonymity. Media services and network providers can receive normal connection information while you stream. Incognito pauses supported activity recording; it is not a VPN.

Optional services remain choices

Update checks contact GitHub when enabled or requested. SponsorBlock, DeArrow and dislike features contact their community providers when used. Live Radio and Live TV browse external directories and connect to the selected stream source.

SponsorBlock contributions require a separate opt-in and use a persistent private contribution ID. Submissions and votes can become public. The contribution identity is excluded from normal WizeStream backups and Device Sync; it should not be posted in a report.

Voice search delegates to an installed recognition provider. Although WizeStream requests offline recognition, the provider determines whether it can work locally. On-device comment translation has different requirements and no WizeStream cloud fallback.

Sync, casting and deliberate sharing

Device Sync exchanges supported records through encrypted peer-to-peer connections after one-time QR pairing. Search history is excluded unless enabled on both devices. Downloaded media files are not transferred.

Casting and configured home-audio handoff send selected media information to your chosen receiver or server, which may then request the source media itself. A personal backup or imported playlist can also contain private information even though the app has no cloud account.

Reports you can review

WizeStream does not automatically upload crash reports. Its reporting flow lets you review and edit information before copying it or sending it through an email app or GitHub.

Reports can include URLs, service/language details, versions, exceptions and your own text. Remove passwords, authentication cookies, private links and personal database contents before posting to a public project.

This website

The documentation website uses static pages; the optional community reviews page uses PHP and MySQL. Neither includes analytics scripts, advertising scripts, tracking cookies, third-party fonts or embedded social-media widgets. Documentation search and comparison filters run inside your browser without sending their input to a search or analytics service.

If you explicitly choose a light or dark appearance, the website can store only that preference locally as wizestream-site-theme. You can remove it in your browser’s site-data settings. Ordinary access still reveals connection information to the hosting and network providers; their logging practices depend on the final hosting configuration.

The direct-download route records only aggregate ARM and x86_64 request counts. It does not store IP addresses, user agents, referrers, cookies or device identifiers. HEAD, prefetch and resumed range requests are excluded. Public download badges combine that website total with public GitHub release-asset counts and public IzzyOnDroid aggregate statistics.

Images and interface assets are served with the website. External GitHub, IzzyOnDroid, competitor and project-reference links are contacted when you follow them, rather than being loaded as third-party widgets. Those destinations have their own policies.

Optional community reviews

The separate community review page asks for a rating, written feedback, consent, and optional nickname and app version. It requires no account or email. Every submission waits for moderation; only published reviews count toward the public rating.

The PHP service stores a hash of your private deletion key, not the key itself. Temporary HMAC-derived address buckets in MySQL enforce shared abuse limits across PHP workers. Identifiers change each UTC hour, expire at the next UTC hour and are removed on the next request or hourly cleanup. They are not attached to a review. Raw addresses, user agents and device IDs are not stored by this service.

Pending reviews expire after 30 days and are cleaned up on the next request or scheduled cleanup. Published reviews stay until the author or moderator removes them. Deletion removes the live record; hosting logs, database logs and backups follow the operator’s actual configuration. The service does not guarantee one review per person or verified installations.

Useful controls and references

• Review history, Incognito, optional community features and selected network settings in the app.
• Keep private backups and contribution/review management secrets out of public issues.
• Use the privacy and networking guide for proxies, Invidious media-host trust and individual feature boundaries.
• Read the repository privacy policy for the app’s canonical published policy.

This overview was reviewed on 13 November 2026 against the development snapshot. Newly merged behavior may be newer than an installed stable build or an older policy section; the linked source and feature guides provide that context.