Agreement draft – not yet available for acceptance
Data Processing Agreement
Agreement governing personal data processed by StreamRequest on behalf of streamers.
Version: 2026-11-08-v2
This preview is provided for review. No agreement is concluded and no acceptance is recorded on this page.
1. Parties and scope
The processor is Luca Giuliano, trading as EliteKampfei Designs, Amthorstraße 42, 6020 Innsbruck, Austria. Contact for instructions, privacy requests and security incidents: elitekampfeidesign@outlook.com.
The controller is the individual or legal entity identified in the acceptance form for whose streamer profile StreamRequest is used. Anyone acting for another individual or organisation must be authorised to enter into this agreement.
This agreement covers the processing on behalf of the controller described in Annex 1. The annexes form part of the agreement.
2. Roles and responsibilities
The controller decides how to receive, select and use song requests addressed to them. The controller is responsible for the legal basis, required information for data subjects and the lawfulness of their instructions.
StreamRequest processes this data solely to provide the commissioned functions and on documented instructions. Using request data for advertising, personal profiling or personal analysis across multiple streamers is outside the scope of this processing.
The operator may act as a controller for its own purposes, including streamer account management, authentication and its own operational and abuse prevention security. Such processing is described in the privacy notice and is not made processor activity merely by this agreement.
Additional processing by the streamer outside StreamRequest, particularly in their livestream, remains within the streamer's responsibility.
3. Documented instructions
This agreement and actions initiated by the controller within the agreed functions constitute documented instructions. These include managing requests, playback, scheduling and ending a stream session.
By accepting this version, the controller also gives a standing instruction to automatically end inactive stream sessions and subsequently delete their song requests and request files under section 8 and Annex 2. Publishing this version alone does not constitute acceptance.
Further instructions may be sent to the processor's contact address. The sender's identity and authority may be verified before execution. An extension of the agreed service scope requires a separate agreement.
If the processor considers an instruction to infringe data protection law, it informs the controller without undue delay and suspends the affected processing pending clarification. Legally required processing is communicated to the controller beforehand unless the applicable law prohibits that notification.
4. Confidentiality and security
The processor limits access to persons who need it to perform the processing. Authorised persons are bound by confidentiality unless an appropriate statutory confidentiality obligation already applies. That obligation continues after their work ends.
Technical and organisational measures are described in Annex 2. They are reviewed and adjusted where necessary, taking account of risk, the state of the art and the processing scope. Changes must not reduce the agreed protection level.
The controller protects their credentials, signed-in devices and any confidential player access details. Suspected misuse must be reported without undue delay.
5. Assistance and personal data breaches
Taking account of the processing and information available, the processor assists the controller with data subject requests and with obligations concerning security, breach notifications and necessary data protection impact assessments, including prior consultations.
Data subject requests concerning commissioned processing are forwarded to the controller without undue delay. Substantive responses on the controller's behalf require instructions unless a legal obligation requires otherwise.
When the processor becomes aware of a personal data breach affecting commissioned data, it informs the controller without undue delay. Notification includes available information about its nature, scope, possible consequences, measures taken or proposed and a contact point. Missing information is provided subsequently without undue delay.
The processor documents the incident and supports containment and investigation. Decisions on notifying supervisory authorities and data subjects remain with the controller unless the processor has an independent legal obligation.
6. Sub-processors and international transfers
The controller gives general authorisation for the sub-processors and purposes described in Annex 3. The processor imposes data protection obligations corresponding to the relevant obligations of this agreement and remains responsible to the controller for their performance.
The processor notifies the controller by email at least 30 days before an intended addition or replacement. The controller may object within that period on substantiated data protection grounds. The new provider is not used for that controller's commissioned data pending resolution. If no suitable solution is available, the affected service may be terminated.
Transfers to third countries require compliance with Chapter V GDPR. On request, the processor provides information about the transfer mechanisms and necessary supplementary measures. Authorising a provider does not replace that assessment.
7. Evidence and audits
The processor provides information necessary to demonstrate compliance with this agreement and Article 28 GDPR. It allows and contributes to audits, including inspections, by the controller or an auditor appointed by the controller.
Audits are coordinated while protecting other customers' confidentiality and system security. Suitable existing evidence may be considered first but does not exclude necessary further audits. Ordinary notice periods must not prevent urgent audits prompted by concrete incidents.
8. Duration, return and deletion
This agreement applies from acceptance for the duration of the commissioned processing. Confidentiality, assistance and proper deletion obligations continue insofar as they remain to be fulfilled after the service ends.
Manually or automatically ending a stream session deletes its requests, including stored requester details, from the active database. Manual ending constitutes a deletion instruction; automatic ending follows the standing instruction given by accepting this version. The controller must request any required return of this data in good time before manual or automatic ending. Ending a session does not delete personal library tracks.
Session activity is updated when a session starts, when continuation is confirmed, and by confirmed heartbeats from a reserved player. After at least 24 hours without such an update, the background process ends the session if no valid player reservation exists. A reserved player keeps the session active through its heartbeats even while paused. Viewer visits or merely displaying the dashboard without such a heartbeat or confirmed continuation do not extend the period. The 24-hour period is an inactivity threshold; background intervals, backlogs and technical failures may delay actual ending and deletion.
At the end of the commissioned services, remaining commissioned data is returned or deleted at the controller's choice and remaining copies are deleted unless a legal retention obligation requires otherwise. Coordination and any necessary secure return take place through the processor's contact address.
Technical deletion procedures and backup periods are described in Annex 2. During any remaining backup period, data is not used for ordinary operations. Previously executed deletion instructions must be reapplied following restoration. Deletion is confirmed on request.
The agreement acceptance record is distinct and is administered by the operator as a controller. Its retention and deletion follow the applicable legal bases and the criteria described in the privacy notice.
9. Breach of agreement and acceptance
If the processor cannot comply with this agreement, it informs the controller without undue delay. The controller may require suspension of the affected processing pending remediation. Material or continuing breaches entitle the controller to terminate the affected commissioned processing.
The accepted text is documented by its version, checksum, language, acceptance time, the supplied full name or company name of the contracting party, and association with the account and streamer profile. Publishing a new text does not by itself constitute acceptance of that version.
In a conflict, this agreement's data protection obligations prevail over other agreements concerning the same processing. Mandatory law, data subject rights and supervisory authority powers remain unaffected.
Annex 1 – Processing description
Subject matter and purpose: Providing the personal request page, receiving and managing song requests, approval or rejection, presence confirmation, queues, playback and associated overlays, and managing supplied library files insofar as they contain personal data.
Processing operations: Collection, storage, organisation, display, retrieval, transmission to players and overlays used by the streamer, and deletion. Processing continues while the profile is used and until the agreed return and deletion procedures are complete.
Data subjects: Viewers and requesters, and individuals whose personal details the controller or a requester includes in submitted content.
Data types: Requester name or pseudonym, artist and title details, source links and any audio files, rights confirmations, timestamps, session associations, approval, playback and presence status, and technical identifiers. Where submission limits serve the commissioned function, this also includes pseudonymous sender identifiers scoped to a streamer and session.
Special categories of personal data and criminal offence data are not intended for the service. The controller must not deliberately use the functions to process such data. Unintentionally submitted content is addressed with the controller when discovered and removed where necessary.
Requester names are displayed in the protected dashboard; the reviewed public state and overlay interfaces do not return this field. Library content may be displayed or played through the playback and overlay functions used.
Annex 2 – Technical and organisational measures
Administrative access: Administration is performed by the operator. Their Cloudflare, GitHub and Resend accounts are protected by two-factor authentication. The development computer is protected by a Windows sign-in PIN. Additional administrative permissions are granted only where operationally necessary and revoked when no longer needed.
Access separation: Protected streamer functions use server-side authentication and ownership checks. Streamer data is separated through profile and session associations. This is application-level separation; a separate database for each streamer is not promised.
Transmission and secrets: The public application is provided over HTTPS. Access keys are managed as protected environment values. Database backups and local secret files do not belong in the source repository. Access to provider dashboards and keys is restricted to what is necessary.
Integrity: Related changes during profile setup and session ending use database transactions. Deletion jobs for request audio files are recorded durably together with database cleanup. Before deletion, the application checks whether a track still references the file. Failed deletions are retried.
Data minimisation: Submission limits use a pseudonymous identifier generated with a secret key and scoped to a streamer and session. Direct IP addresses are not stored in that limit table. Separate technical logs and login sessions may contain connection data.
Deletion: Requests from manually or automatically ended sessions are removed from the active database. Associated request audio files are removed immediately or through pending deletion jobs. Automatic ending follows the 24-hour inactivity rule in section 8. The ending reason and, where applicable, the acknowledgement time of the displayed notice are stored with the session. Remaining session data becomes eligible for cleanup 30 days after the recorded ending if no tracks still reference it. Ending a session does not affect personal library files.
Cleanup: Inactive stream sessions are automatically ended under section 8. Pending file deletions and expired login sessions, verification records and submission reservations are handled through bounded background runs. The schedule runs every five minutes; it guarantees neither ending exactly after 24 hours nor file deletion within five minutes. Errors, remaining references and larger backlogs may require further runs.
Backups and logs: The configured D1 Time Travel feature permits restoration of database states within up to 30 days. That backup period does not automatically apply to R2 files. Workers logs retained under the current plan are stored for up to seven days; no additional log export is currently configured.
Effectiveness and incidents: Changes to access protection, data access and deletion procedures are reviewed according to risk. Errors and security incidents are investigated and necessary measures documented. Provider backups do not replace application-level restoration checks.
Annex 3 – Providers and scope distinctions
Sub-processor: Cloudflare, Inc., United States, for application execution through Workers, the D1 database, R2 file storage and related technical logs. Cloudflare's data processing agreement and applicable sub-processor information also apply. Information: https://www.cloudflare.com/cloudflare-customer-dpa/ and https://www.cloudflare.com/privacypolicy/subprocessors/.
Processing locations: The R2 storage used is configured for EU jurisdiction. This does not promise that all Workers, D1, support or technical log processing takes place exclusively within the EU. Any international transfers are subject to Section 6.
Scope distinction: GitHub is used to manage application code and is not intended to store request data. Resend currently sends account verification and password emails as part of the operator's own account management; request lists and request MP3s are not transmitted for that purpose.
YouTube and Suno are integrated as external services when their players are used. Integration does not make them instruction-bound sub-processors of StreamRequest. Their integration, required information and the intended permission for external media must be considered separately.