Advanced Encryption Standard
AES
A symmetric encryption algorithm adopted by the U.S. government as the standard for encrypting sensitive information. AES-256 uses 256-bit keys, making it virtually unbreakable with current technology.
In THE WHEEL: We use AES-256-GCM to encrypt your personal documents and conversations at rest. Your data is encrypted before it's stored, and only you have the keys to decrypt it.
Bring Your Own Key
BYOK
A model where customers use their own API keys for external services rather than relying on a provider's shared access. BYOK gives organizations direct control, usage visibility, and cost management.
In THE WHEEL: (Coming soon) Bring your own API keys for external LLM providers like Anthropic or OpenAI. You get direct billing, full usage transparency, and can enforce your own rate limits and policies.
Ciphertext
Encrypted data that appears as scrambled, unreadable text. Ciphertext can only be converted back to plaintext (decrypted) using the correct encryption key.
In THE WHEEL: Your documents are stored as ciphertext in Google Cloud Storage. Even if someone accessed our storage buckets, they'd only find encrypted files that can't be read without your encryption keys.
Federal Information Processing Standard
FIPS
U.S. government standards for cryptographic modules. FIPS 140-2 Level 3 requires physical tamper-evidence and identity-based authentication for accessing cryptographic keys.
In THE WHEEL: Our HSMs are FIPS 140-2 Level 3 certified, meeting the same security standards used by government agencies and financial institutions.
Galois/Counter Mode
GCM
An authenticated encryption mode that provides both confidentiality and authenticity. GCM detects if encrypted data has been tampered with, preventing malicious modifications.
In THE WHEEL: AES-256-GCM ensures your encrypted documents haven't been tampered with. If anyone tries to modify your encrypted data, decryption will fail automatically.
HMAC-based Key Derivation Function
HKDF
A cryptographic function that derives multiple keys from a single master key. HKDF creates unique keys for different purposes without storing them separately.
In THE WHEEL: We use HKDF to derive purpose-specific keys from your private encryption key. For example, keys for encrypting metadata like file names and tags are derived using HKDF, ensuring each encryption purpose has its own cryptographically independent key.
Hardware Security Module
HSM
A physical computing device that safeguards and manages cryptographic keys. HSMs are tamper-resistant and provide a secure environment for key generation and encryption operations.
In THE WHEEL: Your private encryption key is protected by Google Cloud HSM (FIPS 140-2 Level 3 certified). Even our engineers cannot access this keyâit exists only in hardware-protected memory.
Key Management Service
KMS
A cloud service that manages cryptographic keys for applications. KMS handles key creation, rotation, and access control, removing the burden of manual key management.
In THE WHEEL: We use Google Cloud KMS to manage your entity-level encryption keys. Keys are automatically rotated, and all key operations are logged for security auditing.
Nonce
A "number used once"âa random value used in cryptographic operations to ensure the same data encrypted multiple times produces different outputs. Prevents pattern analysis attacks.
In THE WHEEL: Document content uses random nonces for each encryption, ensuring identical documents produce different encrypted outputs. This prevents attackers from detecting duplicate content.
Optimal Asymmetric Encryption Padding
OAEP
A padding scheme for RSA encryption that adds randomness and prevents certain cryptographic attacks. OAEP makes RSA encryption more secure against chosen-ciphertext attacks.
In THE WHEEL: RSA-OAEP ensures your encryption keys are protected with industry-standard padding, meeting NIST cryptographic recommendations.
Plaintext
Unencrypted, human-readable data. Plaintext can be read by anyone who accesses it without requiring decryption keys.
In THE WHEEL: Your documents are encrypted before storageâwe never store plaintext versions. Decryption to plaintext happens only in volatile memory during query processing, then memory is immediately wiped.
Rivest-Shamir-Adleman
RSA
A public-key cryptosystem used for secure data transmission. RSA uses two keys: a public key for encryption and a private key for decryption.
In THE WHEEL: RSA-OAEP-4096 is used in the cryptographic handshake between your device and the HSM during secure operations. The HSM holds the private key, ensuring keys can only be accessed through the hardware security module.
Salt
Random data added to inputs before hashing or encryption. Salts ensure that identical inputs produce unique outputs, preventing rainbow table attacks and pattern recognition.
In THE WHEEL: Salts are used in key derivation to ensure each entity's encryption keys are cryptographically unique, preventing any two entities from having identical key material.
Session Key
A temporary encryption key used for a single session or transaction. Session keys are generated on-demand and discarded after use, limiting exposure if compromised.
In THE WHEEL: When encrypting multiple documents at once, we generate a single session key from the HSM to encrypt the batchâreducing HSM calls while maintaining security. The session key is destroyed immediately after the batch completes.
Transport Layer Security
TLS
A cryptographic protocol that provides secure communication over a network. TLS 1.3 is the latest version, offering improved security and performance.
In THE WHEEL: All data in transit uses TLS 1.3 encryption. Your data is protected from the moment it leaves your device until it reaches our servers.