Security Compliance Ledger

Privacy Policy

Last System Revision Matrix: July 2026

1. Information Collection Vectors

Our core system architecture captures distinct interaction sets to process service handshakes seamlessly across your devices:

  • Account Credentials & Identifiers: Email points, phone numbers, and profile details provided during account creation or via our Google OAuth single sign-on system.
  • Operational Log Tracks: Client-side context records including active IP routing positions, geographical matching parameters, user agent characteristics, and interaction history.
  • Localized Persistence Matrices: Temporary storage objects such as `user_token` values in LocalStorage, alongside IndexedDB tables to facilitate uninterrupted system access.

2. Third-Party Identity Federation (Google OAuth)

When choosing to bypass traditional forms via third-party social buttons, our platform intercepts an authorized access token to fetch your core directory details (specifically name and validated email address).

To maintain explicit control over your footprints, our components leverage security configurations that pass parameters through a clean `return_to_url` routine. This architecture ensures that sensitive session tokens and transient error flags are immediately removed from your browser's visible address bar once authentication concludes.

3. How We Utilize Collected Metrics

Captured user data is processed to manage live dashboard sessions, track user preferences across search layers, route geographical inquiries to appropriate neighborhood categories, and protect application frameworks from automated bot deployments or malicious attacks. We do not sell or trade user metrics to bulk advertising brokers.

4. Client-Controlled Cache Management

This PWA-enabled application preserves layout indices and classified summaries directly inside your browser cache. You maintain continuous, uninhibited authority to wipe these data layers at any time by clearing your browser's application cache, purging cookies, or resetting storage tables for this domain.

5. Structural Security Actions

All API transactions, user authorization requests, and payload dispatches are shielded using industry-standard SSL/TLS layer wrappers. While we use robust encryption schemes across all processing pathways, no digital data system can be guaranteed to be absolutely impervious to outside interception. We encourage you to safeguard your account passwords accordingly.