Privacy Policy — Szept

Last updated: 2026-07-25 · Developer: SP8MB · Contact: brzoza@inter1.pl

Szept is an end-to-end encrypted messenger. We design it to collect the absolute minimum of data. We show no ads, use no analytics or tracking, and do not sell or share data with third parties.

What data we process

Phone number — as the account identifier (given at registration, verified with an SMS code).
Public cryptographic keys of your device — needed so others can encrypt to you.
Minimal routing metadata — whom to deliver an encrypted message to, and a temporary queue while you are offline.
Optional push notification token (if you enable it) — to wake the app; it carries only a signal, no content.

What we do NOT process

Conversation content — messages, voice/video calls and attachments are end-to-end encrypted; the server sees only ciphertext and has no keys to read it.
Your phone book — contact names are matched locally on the device and are not sent to the server.
Ads, advertising identifiers, location, analytics, profiling.

Data on the device

Keys, conversation history, contacts and sessions are encrypted on the phone's storage with a hardware-backed key (Android Keystore). You can enable an app lock (biometrics/PIN) and screenshot protection.

Retention and deletion

Encrypted offline messages and attachments are stored on the server temporarily (until delivery, with a limited lifetime) and then deleted. You can delete your account by contacting the server administrator; deletion removes public keys, the queue and related metadata.

App permissions

The app asks for access to the microphone and camera (voice/video calls), contacts (showing names — locally), notifications and background activity (keeping the encrypted connection alive and receiving calls). Each permission serves only the operation of the app.

Children

The app is not directed at children under 13.

Contact

Privacy questions: brzoza@inter1.pl.

← Home