A narrower identity model
Many communication services begin with a phone number or public profile. Silent Key instead assigns a generated SK-ID after Google authentication. The goal is not anonymity from the service; the goal is to avoid using the phone number as the visible contact mechanism inside the app.
Temporary by default
New messages receive a seven-day expiry timestamp. The project also includes maintenance tools that delete expired records and repair conversation previews. The connection between participants remains even when the history becomes empty.
Moderation is part of the design
Users can block and report. Administrators can review reports and apply account or message actions. The project therefore describes itself as privacy-focused but not end-to-end encrypted.
Technology
The application is a static React-style web build hosted on Netlify. Firebase Authentication handles Google Sign-In, and Cloud Firestore stores profiles, SK-ID mappings, conversations, messages, reports, reviews, moderation information and the live announcement configuration.
Public documentation
This public site exists so users and search crawlers can understand the service without creating an account. Private routes are separated from public informational pages and do not load advertising scripts.
How the public documentation is written
Silent Key is an independent software project. Its public pages describe the product’s actual behavior, trade-offs and limits rather than publishing generic privacy slogans. Documentation is updated when the application changes, and it avoids claiming end-to-end encryption or guaranteed deletion.
The guides are written for users deciding whether the service fits an ordinary conversation. They are not legal, emergency or professional security advice.