Privacy Policy
How Introlic handles identity payloads, token query parameters, and mathematical search records under a zero-surveillance model.
Zero Surveillance Mandate
Legacy tech stacks have turned the web into an ad-driven profiling mechanism. Introlic operates under a strict Zero Surveillance Mandate.
We do not embed third-party tracking pixels (e.g. Meta pixel, Google Analytics, or other ad trackers) on our domain. We do not construct user profiling graphs, and we do not monetize your queries, search history, or personal data.
Minimal Data Sharding
We only store data that is mathematically necessary to execute platform operations:
- Authentication Shards: Your username, email address, password hash, and metadata (role, status) required to access the admin decks.
- Operational Telemetry: Log attempts and security event logs to protect our infrastructure from automated attacks.
- Submission Metadata: Data you explicitly transmit through our contact channels, project forge, or recruitment portals.
Search Index Processing
Our search indexing is built on mathematical retrieval models. Queries processed by the Introlic search nodes are computed strictly in-memory.
We do not associate query strings with authenticated user accounts. We do not sell or lease search queries to third-party data aggregators.
Cryptographic Security & JWT
All data transactions between your client browser and Introlic nodes are secured using Transport Layer Security (TLS).
User sessions are signed cryptographically using JSON Web Token (JWT) payloads with HMAC SHA-256 algorithms. This ensures that session data cannot be manipulated by intermediate proxies.
Account Cleansing Protocols
You retain complete ownership over your digital footprint. If you choose to terminate your node account, you may request database cleansing.
Once verified, all user record rows in primary databases will be purged. Backups are cleared in standard rotation cycles.