Last updated: April 10, 2026
Geo Portal is built for a public, location-based platform with accounts, creator monetization, messaging, and real-time communication. Security is integral to protecting users, payments, and content. This page summarizes our practices at a high level. It is not an exhaustive contract or guarantee; see our Terms of Service for limitations of liability.
We use HTTPS (TLS) for connections between your browser and our services where standard deployments are configured correctly. Always check for the padlock in your browser and avoid entering credentials on untrusted networks without a VPN.
Card and bank payment details for subscriptions, vault purchases, creator payouts, and similar flows are handled by certified payment processors (for example Stripe). We typically receive tokens and transaction metadata—not your full card number. PCI DSS obligations for card data rest primarily with those processors and their integration patterns.
We apply reasonable administrative and technical measures appropriate to our stage of service: access controls for production systems, dependency and security updates as practicable, logging and monitoring for operational and abuse-detection purposes, and rate limiting on sensitive APIs where implemented.
Messages, portal media, and call signaling pass through our systems and/or third-party providers (for example real-time video). You should treat highly sensitive information with care; no online service can promise absolute confidentiality against all threats.
If you believe you have found a security vulnerability in Geo Portal, please report it responsibly to the operator of this deployment with enough detail to reproduce the issue. Avoid accessing or exfiltrating user data beyond what is necessary to demonstrate the flaw. We appreciate coordinated disclosure and will work to address valid reports in line with our capacity.
For what data we collect and why, see our Privacy Policy and Cookie Policy.