Privacy policy
Last updated: 3 September 2026. Product: Recevly (Android / iOS). API host: https://recevly.cloud.
This policy describes what the Recevly backend stores, why, and how long. It matches the production API used by the mobile app. Client-side Google Analytics, Crashlytics, and Firebase Cloud Messaging on the phone are listed because the app declares them in Play Data safety.
Who we are
Recevly is a smart-lock companion app. The API at https://recevly.cloud is hosted on a Hostinger VPS (KVM). Authentication emails are sent by this API over SMTP.
Data we store on the server
- Account. User id, email address, whether the email is verified, verification time, account creation time.
- Sessions. Access tokens are short-lived JWTs signed by this API. Refresh tokens are stored as hashes. Logout and account deletion revoke them. We also store a timestamp used to reject access tokens after logout or deletion.
- Locks. Lock id, who first registered the lock, creation time, last time the lock device contacted the API.
- Lock names and sharing. Per-user display name for a lock, and which user ids may use that lock.
- Access codes (lock OTPs). Codes, expiry, use counts, permanent-code flag. Codes are encrypted at rest. Authorized app users with lock access (and the lock device with a device key) can still read codes so the current app and firmware keep working.
- Push tokens. Firebase Cloud Messaging registration tokens and platform (
android/ios) so the lock can notify you.
We do not store your device contacts, precise location, or payment details. We do not run our own analytics pipeline on the API.
Data on the phone (Play Data safety)
The Recevly app may use Firebase Analytics, Crashlytics, and FCM. Those SDKs are operated by Google and are not processed by this API except that we store FCM tokens you register and send lock notifications through Firebase. Crash and analytics events stay in Google's Firebase project for the app.
Why we process this data
- Sign in with email one-time codes.
- Register and share physical locks.
- Create, list, verify, and delete lock access codes.
- Notify you of lock events.
- Delete your account when you ask.
Legal bases: performing the contract (providing the lock service) and, where required, legitimate interest in securing the service (rate limits, abuse prevention).
Retention
- Account and lock sharing. Until you delete the account (in the app or on the delete-account page).
- Expired or used lock OTPs. Removed after at most the configured retention window (currently hours set by
OTP_RETENTION_HOURS; production default is 48–168 hours). - Push tokens. Until you log out, register a new session (tokens for that user are cleared on login), or delete the account. Invalid FCM tokens are dropped after Google reports them unregistered.
- Auth OTPs. Short-lived, one-time, stored as hashes in our database until they expire or are used (about 10 minutes).
- Deleted accounts. We keep only a non-PII tombstone of the former user id so the same session cannot recreate the profile. Email is not kept.
Subprocessors
- Hostinger. — VPS hosting for the API, PostgreSQL, and TLS termination. May process IP addresses in operational logs per Hostinger's terms.
- Google LLC (Firebase). — Cloud Messaging for lock notifications. The mobile app may also use Firebase Analytics and Crashlytics on-device.
This API does not use Firebase Analytics or Crashlytics on the server.
Security
- The API is HTTPS only (TLS). These pages do not load mixed HTTP content.
- Access tokens are short-lived JWTs. Refresh tokens are rotated; reuse is rejected. Logout revokes sessions server-side.
- Production logs are filtered so access tokens, refresh tokens, lock OTPs, and email addresses are not written in plaintext.
- Secrets (database URL, JWT signing key, SMTP password, device key, encryption material) are provided via environment variables, not the git repository.
Your rights
- Delete. In the app: overflow menu → Delete account. On the web: https://recevly.cloud/delete-account. You confirm with a code sent to your email. Deletion is permanent.
- Access / export. Signed-in clients can call
GET /auth/me/exportto download a JSON copy of the data we store for that account.
Children
Recevly is not directed at children under 13 (or the age required in your country). We do not knowingly store children's accounts.
Physical lock limitation
Today the phone may still send access codes to the lock over the local network in plaintext on port 80, and discovery uses an unauthenticated UDP broadcast. That local protocol is a known gap. The hosted API hashes/encrypts codes at rest and authorizes lock OTP routes. See the project README for the firmware migration plan. This does not change what we store on the server.
Changes
If we change what we store, we will update this page. The hosted URL for Play Console is https://recevly.cloud/privacy.