1. Information Ingestion
We collect system-minimum metadata required for protocol stability. This includes cryptographic identities and operational logs telemetry.
- Account Credentials (SHA-512 Encrypted)
- API Authentication Tokens
- Transport Layer Telemetry
2. Cryptographic Security
Inslash utilizes enterprise-grade Argon2id and SHA-512 hashing vectors. Every fragment of sensitive data is isolated within an immutable Passport string, featuring unique per-user salts and optional hardware-security peppering.
3. Data Sovereignty
Your data is strictly confined to the Inslash ecosystem. We enforce a zero-sharing policy with third-party analytical or advertising networks. Decryption is mathematically impossible by design.
4. Operational Persistence
Metadata remains cached as long as the account remains active in the registry. Terminal account deletion triggers a total cryptographic purge of all associated identities within 72 hours.
5. Protocol Adjustments
We reserve the right to upgrade this protocol as security standards evolve. Significant shifts in cryptography will be broadcast via system-wide notifications.