1. Controller

Patrick Mohr
Karl-Leibersperger-Weg 3
76707 Hambrücken
Germany

Email: info@viewpulse.de

2. Principles of data processing

ViewPulse processes personal data only as far as necessary to operate the website, Twitch login, Twitch bot, dashboard, panel and community features. This includes technical delivery, account assignment, progress calculation, abuse prevention and error analysis.

Personal data is not sold. ViewPulse does not use external advertising, marketing or tracking services.

3. Hosting and technical security

ViewPulse is operated on a server provided by Webtropia. When the website and technical interfaces are accessed, server-side access data may be processed, including:

• IP address
• Date and time of access
• Requested pages, files and interfaces
• HTTP method and status code
• Browser type, browser version and operating system
• Referrer information where technically transmitted

This processing is used to provide the website, analyze errors, secure the system and prevent misuse.

Legal basis: Art. 6 para. 1 lit. f GDPR

The security statistics maintained by ViewPulse and their deletion schedule are described in section 10. Separate logs kept by the web server, a reverse proxy or the hosting provider are distinct from these statistics. Their configuration and retention are not controlled by deletion within ViewPulse.

4. Twitch login and Twitch permissions

ViewPulse uses Twitch OAuth for login, account assignment and bot permissions. You are redirected to Twitch and sign in there. ViewPulse only receives the data and permissions required for the selected function.

Depending on the login, the following data may be processed:

• Twitch ID
• Twitch login name and display name
• Profile image URL
• Granted Twitch permissions, for example channel:bot
• Session data for login

For the bot account, OAuth data may additionally be stored so the bot can send Twitch chat messages and perform chat-related bot functions.

Twitch's own data processing is governed by the Twitch Privacy Notice.

Legal basis: Art. 6 para. 1 lit. b GDPR for login and use of the service, and Art. 6 para. 1 lit. f GDPR for technical security and abuse prevention.

5. Cookies and session data

ViewPulse uses technically necessary session cookies so login, session management and protected areas such as the dashboard can function. These cookies are not used for advertising, external tracking or user profiles.

Language selection may be stored in a technically simple cookie so the selected website language remains active.

Legal basis: Art. 6 para. 1 lit. b GDPR and Art. 6 para. 1 lit. f GDPR. Where information is stored on or read from your device, this is done for technically necessary purposes under § 25 para. 2 TDDDG.

6. Streamer data in the dashboard

If you use ViewPulse as a streamer, data required for administration and operation of your ViewPulse system is processed. This includes:

• Permanent Twitch ID to recognize the same channel after a name change
• Twitch login name of the streamer
• Account creation time
• Plan information such as Free or Pro
• Bot permission status and notice status
• Live status of the stream
• Times of bot activation, last detected live streams, live checks and any required inactivity review
• Streamer settings such as XP values, watchtime intervals, level limits, streak milestones and bot language
• Blocklists for bots and users

A new bot activation includes checking your total Twitch follower count. No follower lists are imported for this purpose, and the checked total is not permanently stored in a separate ViewPulse database field. After an extended streaming break, the bot slot may be released without automatically deleting existing progress.

Purpose: dashboard delivery, bot control, level system configuration and abuse prevention.

7. Viewer data, chatbot and progress system

ViewPulse processes viewer data so XP, levels, ranks, watchtime, streaks and status commands work in the respective Twitch channel. This may include:

• Twitch username in the respective channel
• Twitch ID if the identity was shared or linked through Twitch
• Twitch opaque ID in the panel where transmitted by Twitch
• XP, level, prestige and season points
• Watch streak, last streak dates and redeemed streak rewards
• Timestamps of last activity, last message, last XP grant and last watchtime grant
• Status values such as AFK or Lurk

The bot evaluates chat activity to operate the progress system. In the regular data model, ViewPulse does not store complete chat logs. Temporary console output may occur for troubleshooting.

8. Forum, comments and wishes

If you submit a comment, wish, idea or problem in the ViewPulse forum, ViewPulse stores your Twitch login name, display name, selected category, title, content, status and submission time.

Forum posts are publicly visible so other users can understand ideas and ViewPulse can collect feedback more effectively. Please do not post confidential data, tokens, private contact details or other sensitive information.

Legal basis: Art. 6 para. 1 lit. b GDPR and Art. 6 para. 1 lit. f GDPR.

9. Twitch panel and extension API

The ViewPulse panel regularly requests data from the ViewPulse API so viewers can see their progress directly inside the Twitch panel. Depending on Twitch sharing and panel state, this may include:

• Twitch channel ID
• Twitch user ID if the viewer shared their identity
• Twitch opaque ID if no direct identity was shared
• Panel views and technical API responses
• Linked ViewPulse progress data such as level, XP, rank, streak and status

The panel is designed for regular updates to reduce server load and avoid unnecessary data processing.

10. Internal statistics and Control Center

Service and usage overview

ViewPulse maintains its own server-side daily statistics to investigate technical faults and understand how its features are used. These include:

• Aggregated requests to ViewPulse pages and interfaces by path, HTTP method, status code and day
• Aggregated response times, including total, average and longest response time
• Aggregated bot command usage by streamer, command and day
• Aggregated streamer metrics such as dashboard views, panel polls and login events

Request counts are not a reliable count of individual people. Repeated API polls, search engines and other automated requests may be included.

Security statistics containing IP addresses and browser identifiers

To recognize unusual request volumes, automated requests, sign-in problems and technical errors, ViewPulse also processes the full transmitted IP address and the browser-supplied identifier (User-Agent, truncated to no more than 180 characters). This identifier may contain information about the browser, operating system and sometimes device type; it is not reliable evidence of the actual device used.

Separate daily counts and the time of the last recorded request are stored for IP addresses and browser identifiers. These values are not anonymized. They are not used to create advertising profiles or deliberately linked with Twitch profiles.

The statistics concern requests within ViewPulse, not your general browsing history or visits to other websites. Query parameters, passwords, OAuth codes, tokens, cookie contents and form submissions are not included in these statistics. No additional tracking cookies or browser fingerprinting techniques are used for this analysis.

Purpose limitation: IP addresses and browser identifiers are evaluated for troubleshooting, abuse detection and service availability, not for personalized advertising or personal audience profiles. The other aggregated feature counts also help improve ViewPulse.

Retention of security statistics: Daily entries containing IP addresses or browser identifiers become due for deletion seven days after the last request recorded in that daily entry. ViewPulse cleans up these entries at startup and hourly while running; an overdue cleanup is also performed before Control Center statistics are evaluated. The check interval can delay actual deletion by up to one hour. Following an interruption, cleanup is performed when the service resumes. This period does not automatically apply to separate server logs or backups.

Access and recipients: Control Center statistics are restricted to authorized administrators and are not public. Security statistics are not sent to Twitch, advertising networks or external analytics services. Necessary technical access by the hosting provider and legally required disclosures remain possible; see section 12.

Legal basis and legitimate interests: Art. 6 para. 1 lit. f GDPR; the interests pursued are protection against abusive requests and a reliable service. This basis requires the processing to be necessary and proportionate and your competing interests not to override those interests. It does not authorize unlimited data collection.

Right to object: You may object to processing based on Art. 6 para. 1 lit. f GDPR on grounds relating to your particular situation. We will then examine whether compelling legitimate grounds justify continued processing. Send privacy requests to info@viewpulse.de.

11. Database, backups and security

ViewPulse stores the data required for the service in a database. The system is designed for PostgreSQL. Backups may be created to secure operation and may contain personal data. They are used only for recovery, troubleshooting and operational security.

Access to database, backups and Control Center is restricted to authorized administrators. Credentials, tokens and configuration files must not be made publicly available.

12. Sharing with third parties

Personal data is not sold and is generally not shared with third parties unless this is necessary for operating ViewPulse, you knowingly use a function or a legal obligation exists.

• Webtropia as hosting provider
• Twitch for login, OAuth, bot functions, chat, panel and API requests

The hosting provider may access stored data to the extent necessary to provide the technical service. Internal security statistics are not supplied for external providers' own advertising purposes. Using a hosting provider therefore does not mean that all technical disclosure is excluded.

If payment functions for paid plans are added later, this privacy policy will be updated with the relevant payment provider.

13. Storage period and deletion

Personal data is stored only as long as required for the respective purposes or as long as legal obligations require longer storage.

The active IP/User-Agent security statistics follow the seven-day deletion rule described in section 10. This does not require deleting a Twitch account or signing out of ViewPulse. Backups must be kept separate from active use and deleted when their recovery purpose no longer applies. If data is restored from a backup, overdue cleanup must be performed again.

If a streamer account is deleted, the related ViewPulse data is deleted from the database according to the current technical state, unless legal retention obligations prevent this. Technical residual data may remain in short-term server logs or backups for a limited time.

14. Your rights

Under the GDPR you have in particular the following rights:

• Right of access under Art. 15 GDPR
• Right to rectification under Art. 16 GDPR
• Right to erasure under Art. 17 GDPR
• Right to restriction of processing under Art. 18 GDPR
• Right to data portability under Art. 20 GDPR
• Right to object under Art. 21 GDPR
• Right to lodge a complaint with a data protection authority

If processing is based on consent, you can withdraw that consent at any time with effect for the future.

15. Privacy requests

For privacy questions or requests for access, correction, deletion, restriction or objection, contact:

Email: info@viewpulse.de

To prevent data from being disclosed or deleted for unauthorized persons, an appropriate identity check may be required.

16. Minors

ViewPulse is primarily aimed at streamers and community managers. It does not offer content specifically targeted at children. Use as a streamer requires that the registering person is authorized to manage a Twitch stream or community.

17. Automated decisions

No automated decision-making with legal or similarly significant effect takes place. Automatic calculations of XP, levels, ranks, streaks or AFK/Lurk status serve only ViewPulse functionality within the respective stream.

18. Status of this privacy policy

Status: October 22, 2026

This privacy policy will be updated if technical functions, legal requirements or the type of data processing at ViewPulse change.