Shumse operates an independent, transparent global data platform. This policy outlines exactly how we manage telemetry to ensure maximum structural integrity and compliance with international tracking standards like GDPR and CCPA.
1. Information Architecture
When utilizing the Shumse terminals, we inherently collect standard HTTP routing data required to successfully transmit charts and numeric layouts to your device. This standard payload includes your generalized geographic IP (for localized rate delivery), your active browser-agent, and the timestamp of access.
2. Cookies & State Tracking
We deploy essential HTTP cookies strictly necessary to maintain your UI preferences (such as Light/Dark mode and preferred target nation).
Additionally, we may partner with third-party networks (e.g., Google AdSense or analytical pipelines) that deploy subsequent cookies to monitor ad-delivery metrics and traffic integrity. You maintain absolute control over these cookies via your native browser state settings.
3. Third-Party API Adjacency
As a global aggregator, our pipelines frequently interface with localized market APIs. It is critical to understand that navigating externally to cited sources inherently places you under their independent privacy frameworks. Shumse holds zero liability over third-party telemetry systems post-navigation.
4. Institutional Security
Our core PostgreSQL databases and NextJS routing layers strictly isolate backend data extraction processes from user identity vectors. We utilize secure socket layers (SSL) natively to prevent Man-in-the-Middle (MITM) interceptions.
Operational inquiries regarding this architecture can be securely routed to: [email protected]