In a network built on cryptography, data privacy is not a feature; it is the foundation. Evantics is committed to collecting only the absolute minimum telemetry required to keep the system operational. This document outlines how your data is tracked, stored, and protected.
When you interface with the Evantics network, we collect:
Tech Stack & Identity: To maintain secure authorization across the network, cookies are used via Google Firebase specifically for identity confirmation and session management.
Local State Tracking: To enforce the system rules without constantly pinging our backend servers, Evantics utilizes local browser storage. localStorage is used exclusively to keep track of the Architect's puzzle thresholds (the crack limits) to prevent platform manipulation and brute-force attempts. Tampering with this local data triggers an automatic system lockout. By using the platform, you consent to this localized telemetry.
Our database architecture is intentionally blind to the secrets you share. When an Architect inputs a Master Payload and Decryption Answers into the Studio, the text is immediately scrambled using SHA-256 and AES encryption locally in the browser. What gets uploaded to our Firestore database is an unreadable hash. We cannot read your passwords, nor can we read the hidden rewards you encrypt.
Evantics relies on heavily vetted third-party nodes to ensure uptime and security:
You reserve the right to vanish. If you wish to permanently delete your UID and scrub your profile from the Evantics network, you may initiate a deletion request through your System Profile. Note: Nodes deployed by Architects may remain active on the network even after the creator's account is purged, to preserve the integrity of ongoing puzzles.