STREAMREQUEST
Privacy notice
Information about the processing of personal data
Last updated: 8 November 2026
1. Controller, roles and contact
The controller for user accounts, agreement records and processing for the operator's own operational and security purposes is Luca Giuliano, trading as EliteKampfei Designs, Amthorstraße 42, 6020 Innsbruck, Austria.
For privacy enquiries and requests to exercise your rights, contact elitekampfeidesign@outlook.com.
The streamer receiving song requests decides how to receive, select and use them. Where StreamRequest processes this data on the streamer's instructions to provide the agreed functions, the operator acts as the streamer's processor.
This notice describes platform operation and data flows. It does not replace the individual streamer's privacy information concerning their own processing, particularly their use of data in livestreams or outside StreamRequest.
2. Website operation, hosting and technical logs
StreamRequest uses Cloudflare, Inc. to operate the application, D1 database and R2 file storage. Accessing the service requires processing technical connection data, which may include IP address, time, requested address, and browser and device information.
Technical requests and errors are logged for operation and troubleshooting. Processing serves service delivery, security, availability and fault resolution.
Workers Logs stored in the Cloudflare Workers dashboard are retained for up to seven days under the current plan. No additional export is currently configured for these logs. This period concerns Workers Logs, not all other processing performed by Cloudflare.
Processing for our own operational and security purposes relies on Article 6(1)(f) GDPR. Our legitimate interests are secure and reliable operation and detecting and preventing misuse. Where processing is necessary to deliver a contractual service you request, Article 6(1)(b) GDPR applies.
3. Account and authentication
Registration and account use involve processing the supplied name, email address, verification status, account identifier, and creation and modification times. Authentication uses Better Auth software and our database.
Password authentication involves a password verification value. Login sessions include an identifier, session token, expiry and other timestamps, and potentially IP address and browser user agent.
Technically necessary cookies support authentication and session recognition. Verification and account recovery also involve identifiers and tokens.
Processing is necessary to create, secure and provide your account under Article 6(1)(b) GDPR. Additional abuse prevention relies on Article 6(1)(f) GDPR.
Under the default configuration in use, login sessions are valid for seven days. Continued use may extend their validity. Seven days is therefore not a fixed retention period measured from the original login.
Email verification links are valid for one hour; password reset links for 15 minutes. Expired database records for login sessions and verification processes are cleaned up regularly. See section 11 for details.
4. Contracting party and DPA acceptance
When the Data Processing Agreement is accepted, we collect the supplied full name or company name of the contracting party. We also store the associated account and streamer profile, agreement version, checksum of the agreement text, agreement language and acceptance time.
These details support concluding and performing the agreement and documenting which version was accepted for which contracting party. The contracting party's name is not a public profile field. It is not automatically replaced by later changes to the public display name or future billing details.
Where you are personally a contracting party, necessary contract administration relies on Article 6(1)(b) GDPR. Processing representatives' details and necessary documentation relies on Article 6(1)(f) GDPR. Our legitimate interests are attributing and documenting the agreement and establishing, exercising and defending legal claims.
No additional IP addresses or browser identifiers are stored for this acceptance record. Such information may independently be processed in login sessions and technical logs.
Accepting the DPA is not consent to advertising, tracking or unrestricted additional processing. Retention of agreement records is explained in section 11.
5. Verification and recovery emails
We use Resend, a service of Plus Five Five, Inc., for verification and password reset emails. Resend receives the recipient address and message content, including the verification or recovery link.
Processing supports account verification, security and access recovery under Article 6(1)(b) GDPR and, where necessary, Article 6(1)(f) GDPR.
Resend states that service data is processed and stored in the United States. Selecting a European sending region does not mean data is stored exclusively in Europe. Its data processing addendum includes EU Standard Contractual Clauses.
Open and click tracking are disabled for the sending domain mail.streamrequest.app. Technical sending and delivery logs remain unaffected.
Resend states that email content and logs are retained for 30 days on the Free plan in use, with seven-day backup retention. Following termination of our Resend account, remaining customer data is deleted within 90 days under the provider's terms, subject to the exceptions in those terms. This concerns our account with the email provider, not deletion of an individual StreamRequest account.
Expiry of a verification or recovery link does not remove a delivered email from your mailbox. Cleaning our authentication database also does not remove delivery data stored by Resend.
6. Turnstile registration protection
Registration uses Cloudflare Turnstile to detect automated registrations and misuse. Cloudflare processes technical connection, browser and device signals and the verification result.
The check is integrated into registration. Abuse prevention relies on Article 6(1)(f) GDPR. Our legitimate interest is preventing automated account creation and attacks against the service.
Cloudflare provides further details in its separate Turnstile privacy notice.
7. Streamer profiles and music libraries
Streamers can provide a public display name, profile address, biography, avatar, banner and links to websites and social networks. These details are displayed publicly as part of the profile.
Personal MP3 libraries contain uploaded audio files and associated title, artist and administrative information. Files are stored in Cloudflare R2.
The requested profile and music management functions are provided as part of the agreed service. Where we act as controller, processing relies on Article 6(1)(b) GDPR. Where library content contains personal data processed on the streamer's behalf, the roles described in section 1 and the data processing arrangements apply.
Only enter information you wish to publish in public profile fields.
8. Song requests and submission limits
A song request includes artist, title, the supplied requester name, source, link or audio file, playback permission confirmation, and timing, status, queue and presence information. It is assigned to a streamer and stream session.
The receiving streamer can see the requester name in their protected dashboard. The public state and overlay APIs do not return that name field. Artist and song title remain publicly visible; do not put confidential information in those fields.
Requests are handled on behalf of the selected streamer. The streamer is responsible for their processing's legal basis and any required additional privacy information. StreamRequest processes commissioned request data according to the agreed instructions.
To limit open requests, an IP address is transformed into a pseudonymous identifier using a keyed hash function. The identifier is scoped to the streamer and stream session. The associated limit records do not store the IP address in plain text. This identifier is not anonymous data.
Where we process data for our own operational and abuse prevention security, we rely on Article 6(1)(f) GDPR. Our legitimate interest is protecting a fair and functional service. This is distinct from processing on the streamer's behalf.
Confirming playback permission is not general consent to unrestricted processing of personal data.
9. External YouTube and Suno players
YouTube and Suno can be allowed separately. In the dashboard, each player loads only after permission. Your browser then connects to the provider, potentially transmitting IP address, browser details and requested content information. Providers may use cookies or similar technologies and associate activity with an existing provider account.
YouTube uses its IFrame API and youtube-nocookie.com for the player. This does not prevent all data transfers to Google. Google Ireland Limited generally provides the service to users in the European Economic Area. The Suno embedded player is provided by Suno, Inc.
Optional embedding relies on your consent under Article 6(1)(a) GDPR. Where access to your device requires consent, the permission also covers that access.
Your choice is held only in application memory and resets on reload. You can withdraw permission in the external-player settings. The embedded player is then removed. Withdrawal does not retrieve information already transmitted; a loaded YouTube API script remains in the page until reload.
Playback of uploaded audio files does not require these permissions. External links take you to another website when you open them.
10. Browser storage
Authentication: Technically necessary cookies enable sign-in and session recognition. Section 3 explains session duration.
Volume and language: The player stores the chosen volume per streamer in localStorage. Sign-in and registration pages also store the selected language there. These entries have no expiry date and can be removed through your browser's website-data settings.
Registration draft: To resume profile setup after email verification, your email address, public display name, desired profile slug and language are temporarily stored in localStorage. A draft matching the account email is removed following successful setup or detection of an existing profile. If setup is not completed, the draft currently has no expiry date and remains until removed by the application or browser.
Verification page: The email address used for verification is also placed in the browser tab's sessionStorage. This storage is generally tied to the tab's session.
Passwords, CAPTCHA tokens, contracting party names and DPA acceptances are not stored in localStorage by this registration draft. DPA inputs are initially held in page memory; the acceptance record is stored on the server after successful submission.
Processing supports the registration and authentication flow you request under Article 6(1)(b) GDPR. Restoring selected operating preferences relies on Article 6(1)(f) GDPR; our legitimate interest is restoring your settings. This does not persist external-media permissions.
11. Retention and deletion
Song requests: Manually or automatically ending a stream session deletes its requests, requester names, sender identifiers and request history from the live database. Personal library tracks are not deleted by this process.
Automatic session ending: 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, an open session is ended by the background process, provided no valid player reservation exists. A player that remains reserved 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 this period.
Request audio files: Persistent deletion jobs are created together with database cleanup when a session ends. After a manual ending, file deletion is attempted immediately; after an automatic ending, it takes place during background processing. Outstanding jobs are retried regularly. After a failed file submission involving an attempted upload, a deletion job is also recorded where the database is available. Files still referenced by tracks are protected from deletion. Failures, backlogs and remaining references can delay deletion.
Ended stream sessions: Remaining session data, particularly start time, end time and status, is retained for troubleshooting for 30 days after the recorded end time. It then becomes eligible for automatic cleanup. Sessions still referenced by tracks are retained until those references are resolved. Active sessions are excluded.
Submission limits: Upload reservations are valid for up to ten minutes. After successful submission, the limit record provides a five-second cooldown. Expired records are removed during subsequent submissions and by background cleanup. Independently, the sender identifier stored in a song request remains until that request is deleted.
Authentication records: Expired login sessions and verification records are deleted from the live database by background cleanup. This does not delete your user account, its email address or password verification value.
Cleanup schedule: The background process is scheduled every five minutes and processes bounded batches. Backlogs, remaining references and technical failures may delay automatic session ending and actual deletion. The 24-hour period is an inactivity threshold, not a guaranteed maximum retention period. The schedule is not a guaranteed deletion deadline.
Accounts, profiles and personal libraries: These are retained for account use and provision of the corresponding functions. Ending a stream does not delete them. You can send deletion requests to the email address above.
DPA records: Records are retained for the duration of the commissioned use. When that use ends or deletion is requested, we assess which information remains necessary to document the completed processing, meet specific legal obligations, or establish, exercise or defend legal claims. Relevant criteria include the evidence's purpose, applicable limitation and retention periods, and ongoing proceedings. Information no longer required must be deleted. There is currently no automatic deletion routine for these records; review and deletion are manual. Ending a stream session does not remove a DPA record.
Workers Logs: Logs stored in the Cloudflare Workers dashboard are retained for up to seven days under the current plan.
Database recovery: Under the current plan, Cloudflare D1 Time Travel provides database states within a recovery window of up to 30 days. Data deleted from the live database may therefore remain in recoverable database states for up to 30 days. This feature covers database states, not audio files in R2.
Email provider: Retention of email content, delivery logs and backups at Resend follows the periods described in section 5. Those periods are independent of authentication-link validity and cleanup of our database.
Historical development backups: The reviewed separate local backup files have been deleted. The affected files were also removed from the reachable history of the private project repository; the original local Git copy was cleaned and the temporary cleanup copy deleted. This does not establish complete removal from GitHub's internal backups, cached views or other old copies. No specific deletion period has been confirmed for any such remaining copies. The D1 Time Travel 30-day period does not apply to them.
Browser storage: Local settings and registration drafts follow the criteria described in section 10. Deleting your server account does not automatically remove entries from your browser's localStorage.
12. Recipients and international processing
Recipients, to the extent required, include the selected streamer, infrastructure and email providers, and external-player providers after permission. Public profile details and displayed song information are accessible to visitors of the corresponding pages.
Contracting party names and DPA records are not displayed through public profile, state or overlay functions. They are processed internally for agreement administration and evidence. Necessary disclosure to authorised authorities or for legal proceedings remains possible subject to applicable law.
International providers may process data outside the European Economic Area, particularly in the United States. EU file storage alone does not mean all processing takes place exclusively within the EU.
Cloudflare and Resend provide, in particular, EU Standard Contractual Clauses for relevant international transfers in their data processing terms. Details of those safeguards are available through the terms linked above or on request. External-media providers describe their additional processing in their privacy notices.
13. Your rights
Subject to the applicable legal conditions, you have rights of access, rectification, erasure, restriction of processing and data portability.
Where processing relies on legitimate interests, you may object on grounds relating to your particular situation. You may withdraw consent at any time with future effect. Withdrawal does not affect the lawfulness of prior processing.
For processing for which we act as controller, send requests to elitekampfeidesign@outlook.com. Reasonable information to verify your identity or identify the relevant record may be necessary to prevent unauthorised disclosure.
The selected streamer is the controller for your song requests processed on their behalf. If you contact us, we help identify the relevant processing and forward your request to the responsible streamer where necessary.
You may complain to a data protection supervisory authority. In Austria, this is the Austrian Data Protection Authority.
14. Required information
Information required for registration, login and song requests is needed for the corresponding function. Without it, that function cannot be provided. Streamer profile setup also requires the specified contracting party details and acceptance of the released DPA version.
Viewers submitting a song request do not need to accept this DPA as streamer contracting parties. Additional profile information and external-player permissions are optional.
The reviewed functions do not use solely automated decisions producing legal or similarly significant effects. Automated security checks and submission limits serve technical abuse prevention.