3.4 Security & Privacy Settings

Cryptic is designed to give users control over account access, cryptographic identity, wallet security, encrypted data, privacy preferences, and communication settings across supported product surfaces.

Security is not treated as a separate feature. It sits underneath the entire Cryptic stack: Mobile, Desktop, SDK infrastructure, wallet functionality, payment coordination, encrypted storage, and future agentic workflows.

Because Cryptic is built around cryptographic identity, user control is central. Account access, key security, recovery options, device protections, and approval flows all matter when communication, wallet actions, encrypted data, and payments exist inside one connected product environment.

Biometric Controls

Where supported, users may enable biometric authentication such as fingerprint or Face ID as an additional protection layer for sensitive operations.

Biometric controls may apply to actions such as:

• Opening the application

• Approving wallet actions

• Accessing sensitive account areas

• Confirming payment-related activity

• Unlocking secure communication or storage features

• Protecting Desktop or Mobile sessions where supported

Biometric controls help reduce friction while adding an additional device-level safeguard.

Key Management

Cryptic’s identity model is built around cryptographic keys.

Depending on product version and supported environments, users may be able to manage device access, account security settings, wallet import or creation, recovery options, and access controls.

Key management may include:

• Wallet creation or import

• Device authorization

• Account recovery settings

• Secure storage configuration

• Identity-related security controls

• Access permissions across Mobile and Desktop

• Future permissioning for agent-based workflows

The goal is to keep users in control of their identity, wallets, approvals, and sensitive cryptographic material.

Privacy Preferences

Cryptic gives users privacy controls across supported communication, account, and device settings.

Available privacy options may include:

• Notification settings

• Communication visibility preferences

• Message or communication retention settings where supported

• Contact and room-related preferences

• Device-level privacy settings

• Encrypted storage preferences

• Privacy controls for supported Desktop workflows

Privacy settings may vary depending on platform, product version, region, and enabled features.

Device Security

Cryptic uses platform-native secure storage and device-level protections where supported.

On Mobile, this may include operating system security features, biometric access controls, and secure storage for sensitive material.

On Desktop, this may include local storage controls, account import protections, encrypted notes, vault access, and product-specific security settings.

Users are encouraged to keep their device operating systems updated, protect their device login credentials, and enable supported security features wherever available.

Backup and Recovery

Backup and recovery are important parts of user control.

Where available, Cryptic may support encrypted backup and recovery flows designed to help users regain access while preserving control over sensitive cryptographic material.

Backup and recovery options may vary depending on:

• Product version

• Platform

• User setup

• Wallet configuration

• Enabled security features

• Supported recovery mechanisms

Users should treat recovery credentials, seed phrases, private keys, and backup materials with extreme care. Cryptic’s security model depends on users maintaining control over sensitive access material.

Desktop Security

Cryptic Desktop expands the user experience into a secure command layer for deeper workflows.

Depending on product version and enabled features, Desktop users may access wallet management, account import, encrypted notes, vault storage, confidential AI workflows, DeFi integrations, and local security settings.

Desktop security may include:

• Local account access controls

• Wallet import and management settings

• Encrypted notes access

• Vault and file storage controls

• Confidential workflow permissions

• Integration-specific settings

• Session and device-level protections

Because Desktop brings together communication, wallet actions, encrypted data, and financial workflows, users should treat Desktop access as a high-security environment.

SDK and Integration Security

For developers, partners, wallets, applications, and future agent frameworks, security depends on implementation.

SDK-based integrations may involve encrypted communication, cryptographic identity, key management, payment rails, encrypted data transfer, and permissioned workflows.

Developers and partners should review Cryptic SDK documentation, supported environments, deployment requirements, and security guidance before integrating Cryptic infrastructure into external products.

SDK security considerations may include:

• Identity generation and management

• Key handling

• Encrypted data transfer

• Access permissions

• Transport security

• Payment flow controls

• Agent-based permission models where applicable

• Application-specific security requirements

Agentic Permissions and Future Controls

As Cryptic expands toward human-to-agent and agent-to-agent workflows, permission controls become increasingly important.

Future agentic workflows may require users to approve what an agent can access, what data it can receive, what actions it can prepare, and whether any wallet or payment activity requires explicit confirmation.

Potential agentic security controls may include:

• User-approved permissions

• Encrypted data access controls

• Wallet-action approval flows

• Payment confirmation requirements

• Agent identity verification

• Human-in-the-loop execution controls

• Limits on what agents can read, prepare, or request

The principle is simple: agents may assist, but users remain in control.

Security and Privacy Summary

Security and privacy settings may vary between Mobile, Desktop, and SDK-based integrations depending on platform, product version, deployment model, and enabled features.

Across every surface, Cryptic is designed around the same foundation:

Cryptographic identity for secure access. User-controlled keys for sovereignty. Encrypted communication for privacy. Encrypted data transfer for sensitive workflows. Wallet security for value movement. Desktop controls for advanced workflows. SDK permissions for developers and integrations. Agentic controls for future AI-native coordination.

Cryptic’s security model is built to keep users, teams, wallets, applications, and future agents operating through secure cryptographic rails, with identity, permissions, privacy, and control at the center.