Skip to main content

MeshStream Privacy Notice

Effective date: October 11, 2026

This Privacy Notice explains how MeshStream collects, uses, retains, shares, and protects information when you register, use the console, integrate an SDK, run a demo, or contact support. MeshStream is a brand and service provided by an individual operator; it is not currently a registered company, corporation, or separate legal entity. The operator, formal service-notice address, governing law, and dispute forum are identified in the current version of this Notice, the applicable order, or a legal notice. This Notice is written for the developer or business customer. If you use MeshStream to process information about your own viewers, you remain responsible for your end-user privacy notice, lawful basis, notices, and consents.

1. Information we handle​

Account and contact information​

We may handle your email address, password hash, verification status, selected region, account status, sign-in events, and security audit records. We do not store your plaintext password.

Application and configuration data​

This may include application names, key identifiers, playback domains, region policies, tracker and fallback settings, allowlists, and console actions. Secret key material should never appear in public code, client logs, or media URLs.

SDK and device signals​

During playback, the SDK may report SDK version, platform, operating system, browser or player type, an anonymous device or session identifier, app version, network type, approximate region, peer capability, connection state, and error reason. These signals support routing, compatibility, diagnostics, abuse prevention, and security.

Playback and usage data​

We may handle application and session IDs, stable content IDs, media protocol, segment outcomes, P2P download bytes, CDN fallback bytes, hit status, authorization result, latency, failure, and downgrade reason. We generally do not need to store media bodies. Logs may be retained when needed for security, support, dispute handling, or legal obligations.

Orders and support​

We may handle plans, quotas, order status, invoices, support tickets, feedback, and troubleshooting material you choose to provide. Where online payments are not enabled, MeshStream does not store full card or payment-account details.

2. How we use information​

We use information to create and protect accounts, send verification and service messages, operate P2P routing and CDN fallback, calculate quotas, provide console analytics, detect abuse and key theft, troubleshoot incidents, improve the Services, and meet legal or regulatory obligations.

We do not sell customer media, origin credentials, or business data. We do not use customer content to build unrelated advertising profiles.

3. P2P privacy boundary​

P2P requires participating devices to exchange limited network metadata needed for connection and segment delivery, such as temporary peer identifiers, connection state, and segment requests. The SDK must not send origin authorization headers, origin passwords, private tokens, or other sensitive request headers to peers. Origin requests remain on your CDN, origin, or controlled fallback path.

We use anonymous or short-lived identifiers where practical and retain connection records only for routing, security, analytics, and support needs. You must explain P2P connections, network metadata, local caching, and analytics to your viewers when required and obtain any required consent.

4. Cookies and local storage​

The console may use cookies, local storage, or similar technologies for sign-in state, language, theme, and security tokens. These essential technologies are required for the service to work and are not used for advertising. The SDK may use local cache for temporary segments, session state, and performance information. Clearing these values may sign you out, invalidate cache, or affect playback.

If Google Analytics is enabled on the developer site, the Google tag loads under Consent Mode with analytics storage denied by default. Until you allow analytics in the Cookie preferences dialog, it does not set or read analytics cookies, although cookieless measurement signals may be sent to Google. Cookie-based analytics is enabled only after you give permission and helps us understand page usage and improve documentation and product navigation. You can reject analytics on first visit or reopen Cookie preferences from the Legal section of the footer to withdraw consent. Google may process measurement data in accordance with its own terms and privacy policy.

5. Providers and international transfers​

We may use carefully selected providers for infrastructure, email, logging, monitoring, cloud storage, support, and security. Providers may access only the information needed for their service and must follow confidentiality and security obligations.

Your selected region may involve cross-region routing, disaster recovery, or support processing. Where information is transferred across borders, MeshStream will use safeguards required by applicable law, such as contractual commitments, access controls, encryption, and data minimization. We disclose information to authorities only when legally required or necessary to protect people, the Services, or legal rights.

6. Retention​

We retain information for as long as needed for the purpose collected, account administration, security, usage and settlement records, dispute handling, backups, and legal obligations. When retention is no longer required, we delete, anonymize, or securely isolate the information.

7. Your choices and rights​

Depending on applicable law, you may request access, correction, deletion, restriction, objection, withdrawal of consent, or a portable copy of personal information. We may verify your identity before responding. Deletion may be limited by security, accounting, dispute, or legal retention duties.

Contact support@meshstream.net for a request or privacy question. If you believe we have not handled a request properly, you may contact the data protection authority available in your jurisdiction.

8. Security and incident response​

We use password hashing, encryption in transit, credential separation, least-privilege access, audit logs, rate limits, backups, and security monitoring. No online service can guarantee absolute security. You are responsible for protecting your account, keys, origin credentials, and access devices.

If an incident may affect your information, we will take reasonable corrective steps and provide notice when required by law or reasonably necessary.

9. Children​

The Services are intended for developers and organizations, not children. If you believe a child provided personal information without appropriate authorization, contact support@meshstream.net.

10. Updates and contact​

We may update this Notice for service, legal, or security changes. We will publish the new effective date and provide additional notice for material changes where required.

Privacy requests, data-subject rights, security incidents, and other privacy questions: support@meshstream.net

Singapore region and personal data protection​

If the Console or an order identifies Singapore as enabled, account, tenant, application configuration, order, quota, usage, and security-audit data for customers selecting Singapore are intended to be processed and stored by the Singapore control plane. Limited information may still be handled by restricted providers in other locations when necessary for global access, resilience, email delivery, payments, monitoring, or support. An unlisted region is not a commitment about data location or availability.

For personal data subject to Singapore's Personal Data Protection Act (PDPA), we will meet applicable requirements for collection, use, disclosure, protection, retention, and disposal, using access controls, encryption, minimization, audit controls, and vendor management. Cross-border transfers are limited to what is necessary for the Services, legal obligations, or security, with safeguards required by applicable law.

If you use MeshStream to process information about your viewers, customers, or other individuals, you generally determine the purposes and legal basis, provide required notices, obtain required consents, and respond to individual requests. MeshStream processes that information on your documented instructions. If we become aware of a security incident that may affect personal data, we will notify affected customers and reasonably cooperate with investigation, remediation, and legally required notifications.

Regional data locations, provider lists, retention periods, and privacy contacts may change with the service architecture; the current information is provided in this Notice, the Console, applicable orders, and legal notices.