Can I use SilentWall to communicate across devices?
Yes. SilentWall enables asynchronous private communication across devices by allowing access to the same named wall using a single key, where each wall is an independent encrypted space readable and writable only by devices that know both the wall name and the key, with all encryption and decryption happening locally in your browser.
How many walls can I create?
Unlimited. SilentWall allows you to create as many independent walls as you want. Each wall is cryptographically isolated and does not affect others.
How large can a single note be?
A single note in SilentWall can contain up to 350,000 characters in one entry. This allows long-form writing, source code, research drafts, or structured technical content within a single encrypted record.
How does SilentWall prevent accidental data overlap between users?
SilentWall uses two-layer isolation:
- Wall Name — defines where the data lives
- Encryption Key — defines who can read it
Even if two users accidentally choose the same key, different wall names always produce different cryptographic keys and separate storage paths.
This prevents global collisions and unintended data exposure.
Can the server access or read my notes?
No. All notes are encrypted entirely on the client side using cryptographic keys derived locally from the wall name and the passphrase before any transmission occurs.
The server stores only encrypted data (ciphertext) and never has access to decryption keys, wall names, or plaintext content.
Are Exported files (.silentwall) encrypted?
Yes. Exported files always contain encrypted data only and never store plaintext in the file itself.
Exports are encrypted client-side using AES-256-GCM with a cryptographic key derived locally from both the wall name and the passphrase.
An exported file is a static, encrypted snapshot of selected notes. It does not represent a live wall and does not enable synchronization.
Export exists to provide a fully independent, encrypted snapshot for offline access, long-term archiving, air-gapped environments, or personal backups outside the network.
An exported file does not rely on SilentWall servers, accounts, sessions, or connectivity. It can be stored, moved, duplicated, or archived indefinitely without any network access.
Plaintext becomes readable only after successful decryption using the same wall name and passphrase that were used at export time. Any device — present or future — that provides both correctly can decrypt the contents, including SilentWall or any compatible AES-256-GCM decryptor that applies the same key derivation logic.
Without the correct wall name, passphrase, and key derivation process, the exported file remains cryptographically unreadable.
What happens if I lose my encryption key?
Your data cannot be recovered. There is no recovery mechanism, backdoor, reset, or administrative override. The encryption key is the sole access to your data.
Is SilentWall truly zero-knowledge?
Yes. SilentWall is a strict zero-knowledge system by design. All encryption and decryption occur exclusively inside your browser’s memory (RAM).
Encryption keys are derived locally from the combination of the wall name and the passphrase, and are never transmitted, stored, cached, or persisted in any form.
Each wall is an independent cryptographic space. Even if the same passphrase is reused, different wall names always produce different derived keys and completely isolated encrypted data.
SilentWall never receives plaintext content, derived keys, wall names, identities, or recovery material. The service cannot read, reconstruct, correlate, or recover user data under any circumstance.
When the session ends, the page is refreshed, or the browser becomes inactive, all cryptographic material is immediately cleared from memory.
Is my data tied to a device or account?
No. SilentWall does not bind data to devices, accounts, or identities.
All notes and messages are bound to a specific wall, and encrypted using a key derived locally from the wall name and the passphrase.
Any device that provides the same wall name and passphrase can access and contribute to that encrypted space.
If either the wall name or the passphrase is incorrect or unknown, the data remains completely unreadable and cannot be inferred, reconstructed, or partially accessed in any form.
Why does SilentWall automatically log out users? (Anti-Logout)
For strict security, encryption keys and derived keys are never stored in browser cache, LocalStorage, or SessionStorage. All cryptographic material exists only in volatile browser memory (RAM).
If the page is refreshed or closed, the encryption key is immediately cleared from memory and the user is returned to the lock screen.
This design enforces true client-side zero-knowledge operation by ensuring that no persistent session, background access, or long-lived key storage can exist.
What happens if SilentWall is left idle or inactive?
SilentWall does not maintain persistent login sessions. All encryption keys and derived keys exist only in volatile browser memory (RAM).
If the app is left idle without interaction, backgrounded, the device is locked, the browser is suspended, or the system reclaims memory, SilentWall automatically clears all cryptographic material and performs an automatic logout.
The user is immediately returned to the lock screen, and access can only be restored by re-entering the correct wall name and passphrase.
This behavior is intentional and ensures that no silent recovery, background access, or unattended exposure of encrypted content is possible.
Are my IP addresses logged?
No. SilentWall does not log, store, or associate IP addresses with notes, walls, encryption keys, identities, or any user activity. IP addresses are not linked to content, wall names, or encrypted data and are never used for analytics, behavioral profiling, tracking, or correlation. Like all internet services, connection metadata such as IP addresses may be processed temporarily for routing and operational security, but this information is not stored persistently, not associated with user identity, and cannot be used to track or identify users.
