Privacy
What NotiPrivYO knows about you
Nothing. That is not a slogan — there is no account with CyriLiNa.IT, no server of ours in the path, and no code in the app that sends anything anywhere except to the server you choose. This page says exactly what exists and where, so you can check it against the published source.
What CyriLiNa.IT collects
- Nothing. We operate no server that the app or your server talks to
- No account, no sign-up, no email address, no licence check
- No analytics, no advertising identifier, no crash reporting, no telemetry of any kind
- This website loads no fonts from a content network beyond Google Fonts, sets no cookies and runs no tracking script
📱 What stays on your phone
- An X25519 private key, generated on the device when it pairs. It never leaves the phone. It is what makes your notifications readable, and nothing else in the world can read them
- The address of your server, the name it gave itself, and the secret it issued to this phone
- Up to 200 messages that actually arrived, so you can read them again after dismissing a notification
- All of it encrypted at rest with
EncryptedSharedPreferences under a key held in the Android Keystore
- Unpair deletes every item above, and tells your server to forget the phone
🖥 What stays on your server
- Your administrator account, your channels, your sending keys as hashes, and the public key of each paired phone
- A copy of each message, encrypted with AES‑256‑GCM under a key file kept outside the database
- Your Firebase service-account file, encrypted the same way
- It is your machine. Deleting the data folder deletes all of it
☁ What Google can see
- Firebase Cloud Messaging carries the message. What it carries is a sealed box — ciphertext and an ephemeral public key, base64 encoded
- No title and no body are ever put in a Firebase notification payload. The notification you see is built on the phone after it opens the box
- Google can see that a message went to a device token, when, and how large it was. It cannot see what it said
- The Firebase project is yours, under your own Google account, subject to Google’s terms and not ours
- The app asks Firebase for a registration token and sends that token to your server. That is the only outbound call it makes that is not to your server
🔐 Permissions the app asks for
INTERNET — to reach your server and FirebasePOST_NOTIFICATIONS — to show a notification, which is the whole productCAMERA — only to scan the pairing QR code. Decoding happens on the device with a plain Java library; no image leaves the phone and no Google vision service is involved
🗑 Deleting your data
- On the phone: Server tab → Unpair this phone. Everything goes, and the server is told to remove the device
- On the server: Settings → Remove this server lists everything it put on the machine. Deleting the data folder deletes all of it
- There is nothing to request from us, because we hold nothing