Legal · Privacy
This privacy policy describes how Stream handles information when you visit streamproin.com. The site is a static editorial publication. We collect as little as practical and do not sell personal data.
What we collect
Server logs may record IP address, user agent, referrer and requested URL for security and operational purposes. These logs are retained for a limited period and are not used for advertising profiles.
If you email the desk, we process the content of your message and your email address in order to respond. We do not add email correspondents to marketing lists.
Cookies and local storage
The site does not set advertising cookies. Essential functional storage may be used by the browser for accessibility preferences. Third-party embeds, if any, are disclosed at the point of use.
Sponsored routes
When you follow a sponsored route, you leave Stream and are subject to the destination's own privacy policy. Sponsored routes are clearly labelled and use a first-party redirect.
Third parties
We do not sell personal data. Infrastructure providers that host the site may process server logs under their own terms. We do not use third-party advertising networks on editorial pages.
Your rights
Depending on your jurisdiction, you may have rights to access, correct or delete personal data we hold about you. Contact the desk at [email protected] to exercise those rights. We will respond within a reasonable period.
Children
The site is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe we have done so, contact the desk and we will delete the data.
Changes
We may update this policy. The last-updated date at the top of the page will change when we do. Material changes will be noted in the edition masthead for at least one edition cycle.
Contact
Privacy questions: [email protected]
Server logs in more detail
When you visit the site, the web server may record the time of the request, the requested URL, your IP address, your user agent string and the referrer URL. These logs are used for security monitoring, abuse prevention and operational debugging. They are not used to build advertising profiles and they are not sold.
Log retention is limited. Logs older than the operational window are deleted or rotated. The exact retention window may vary with infrastructure changes; the principle is minimum necessary retention.
Email correspondence
If you email corrections@, tips@ or desk@ addresses, we process the content of your message and your email address in order to respond. We may retain the correspondence for a reasonable period to handle follow-ups and to keep a record of corrections. We do not add email correspondents to marketing lists and we do not sell email addresses.
Sponsored-route handoff
When you follow a sponsored route, you leave Stream via a first-party redirect and arrive at a third-party destination. That destination has its own privacy policy. Stream does not control what the destination collects. Sponsored routes are clearly labelled so you can choose whether to follow them.
International visitors
The site is reachable globally. Infrastructure providers may process server logs in the region where the servers are located. If you are in a jurisdiction with specific data-protection rights, contact the desk to exercise those rights. We will respond within a reasonable period and in line with applicable law.
Security
We take reasonable technical and organisational measures to protect the limited data we process. No method of transmission or storage is perfectly secure. If you believe there has been a security incident affecting your data, contact the desk immediately.
What we do not collect
We do not run advertising cookies. We do not build cross-site advertising profiles. We do not sell personal data. We do not require an account to read editorial content. We do not collect payment card data on this site. We do not run on-site wagering forms.
If a future feature requires additional collection, we will update this policy and note the change in the edition masthead before the feature goes live.
Legal bases and retention principles
Server logs are processed for legitimate operational and security interests. Email correspondence is processed to respond to your request. Retention follows a minimum-necessary principle: logs rotate, correspondence is kept only as long as needed for follow-up and correction records.
If you ask us to delete correspondence that is not required for a public correction record, we will do so within a reasonable period unless a legal obligation requires retention.
Do-not-track and similar signals
Because the site does not run advertising tracking, there is no advertising profile to honour with a do-not-track signal. Essential server logs may still be recorded for security. If you use browser tools to block third-party content, the editorial pages should continue to function.
Contact for privacy requests
Privacy requests go to [email protected]. Include enough detail for us to locate the data you mean. We will respond within a reasonable period and in line with applicable law in your jurisdiction.
Practical examples
Example: you open the homepage. The server may log your IP and user agent. No account is created. No advertising cookie is set by Stream.
Example: you email a correction. We read the email, act on the correction if valid, and keep the thread long enough to handle follow-up. We do not add you to a newsletter.
Example: you tap the sponsored sticky bar. You leave via /Login/playnow to a partner destination under that destination's policy.
Example: you block third-party scripts in your browser. Editorial HTML/CSS/JS on Stream should still render because the site is static and self-contained.
Requests we expect
Access requests: ask what personal data we hold about you. We will explain server logs and any email threads. Deletion requests: we will delete email threads not required for a public correction record, subject to law. Correction requests about personal data in email: we will correct our records.
We may need to verify that the request comes from the right person. Do not send sensitive government ID unless we ask for a specific minimal proof.
We respond within a reasonable period. Complex requests may take longer; we will say so.
There is no automated decision-making with legal effects on this static editorial site.
Policy maintenance
This policy is reviewed when infrastructure changes, when new collection begins, or at least annually. Material changes get an edition masthead note.
If a provision conflicts with mandatory local law, local law wins for residents of that jurisdiction to the extent required.
Questions: [email protected].
Related documents: terms of use and responsible-play policy.
Infrastructure and processors
The site is hosted on infrastructure that may process connection metadata to deliver pages securely. Those processors act on our instructions for hosting, security and availability. They are not granted a right to sell visitor data harvested from Stream editorial traffic.
If a CDN or edge cache is introduced later, cache logs may include URL paths and approximate geography derived from IP. That processing remains operational. It is not advertising profiling. Material infrastructure changes that alter collection will be reflected in this policy with a new last-updated stamp.
We do not run third-party advertising networks on editorial chapters. We do not drop marketing pixels for retargeting. Sponsored routes leave Stream via a first-party path; after the hop, the destination’s policy applies.
Communications preferences
Stream does not operate a marketing email list from the public contact forms. Writing to corrections@, tips@ or desk@ starts a correspondence thread, not a newsletter subscription. If that ever changes, consent will be collected explicitly and this policy will be updated before any list is built.
Transactional replies about corrections may reference the public stamp on the affected chapter. Those replies are part of the corrections record, not marketing.
Retention schedule in plain language
Server logs: short operational window, then rotation or deletion. Email correspondence: retained while a correction or tip remains active, then reduced to the minimum needed for a public correction archive when one exists. Public correction stamps on chapters may remain indefinitely as part of the editorial record because they protect readers.
If you request deletion of an email thread that underpins a public correction, we may keep a redacted operational note that the correction occurred while removing your address and message body, unless law requires a fuller record.
Security incidents
If we become aware of a security incident that affects personal data we hold, we will assess impact and notify affected individuals and regulators when required by applicable law. Report suspected incidents to [email protected] with enough detail to investigate.
Do not send passwords, payment card numbers or government ID unsolicited. The desk will not ask for payment card data by email.
Cross-border access
Because the site is reachable globally, visitors may connect from many jurisdictions. Infrastructure may be located in one or more regions. Where cross-border transfer rules apply, we rely on appropriate contractual and technical measures used by the hosting stack. Questions about transfer safeguards can be sent to desk@.
Children and age-gated products
Editorial chapters are written for a general audience interested in competitive esports. Sponsored routes may lead to products with their own age gates. Stream’s responsible-play chapter states the age boundary for wagering products referenced via labelled sponsored surfaces. That boundary is editorial policy; technical age verification on partner destinations is controlled by those destinations.
We do not knowingly collect personal data from children under 13. If you believe we have, contact desk@ and we will delete it.
How to read this policy with other documents
Read this privacy policy together with the terms of use and the responsible-play policy. Privacy explains data handling. Terms explain acceptable use. Responsible play explains coverage limits and age boundary language. If the three conflict on a privacy point, this policy controls for data handling questions.
