Privacy policy for WildBit Viewer and WildBit Slide Show Remote

Last Updated 11 October 2025

WildBit Viewer collects diagnostig data only when an unexpected issue occurs, such as a crash or exception. This data helps identify and resolve software problems and includes:

Application:

1. Start Date
2. Name
3. Version Number
4. Parameters
5. Compilation Date
6. Up Time

Exception:

7. Date
8. Address
9. Module Name
10. Module Version
11. Type
12. Message
13. ID
14. Count
15. Status
16. Note
17. Send

Active Controls:

18. Window Class
19. Window Text
20. Control Class
21. Control Text

Computer:

22. Total Memory
23. Processor
24. Display Mode
25. Display DPI
26. Video Card

Operating System:

27. Type
28. Build
29. Update
30. Non-Unicode Language
31. Charset/ACP

Steps to reproduce:

32. Text

• WildBit Viewer does not automatically transmit any personal data or information. If a crash or exception occurs, the program prompts the user to send a bug report via email. Before sending, user can review, edit, or delete any part of the data. Submission is entirely voluntary and based on informed user consent. Some diagnostic data may include file paths that reflect user-specific folder names; These are visible to the user before sending.
• Some older versions of WildBit Viewer may collect additional system metrics beyond those listed above. These may include, but are not limited to: Free Memory, Disk Space, System Up Time, Printer Information or other environment-specific details. The exact data collected may vary depending on the version and configuration.
• WildBit Slide Show Remote does not collect or transmit any data.
• For more information about WildBit Viewer or WildBit Slide Show Remote please contact via email.

Privacy Policy for Blog

This blog is hosted on Google’s Blogger platform and protected by Google reCAPTCHA. As a result, the Google Privacy Policy and Terms of Service apply.

Visitors may leave comments on blog posts using Google’s comment system. When doing so, they may provide their name, email address, or Google account information. This data is processed by Google and used solely for displaying and moderating comments. It is not shared with third parties by the blog owner without consent.

This blog does not set cookies on initial page load. However, cookies may be set automatically by Google services when users view blog posts, interact with the comment section, log in via Google, or respond to Google’s own cookie banner. These cookies are managed by Google and may include: NID, 1P_JAR, AEC, and CONSENT. Their behavior is subject to Google’s consent mechanism and privacy practices.

This site displays an informational consent banner regarding blog usage. It does not control cookie behavior, which is managed by Google. Clicking “Accept” stores your consent locally and hides the banner. Clicking “Reject” dismisses the banner without granting cookie consent. No redirection occurs, and users may continue browsing the blog with limited functionality depending on Google’s cookie settings.

Some third-party services may still set cookies independently based on their own consent mechanisms. These are outside the control of this blog and governed by their respective privacy policies.