← Back to Trei apps Dekhbhal · Android App

Privacy Policy

Effective Date: November 1, 2026  ·  Last Updated: November 1, 2026

Trei ("we", "us", "the developer") built Dekhbhal: Senior Citizen Phone as an Android app with two halves. One runs on an elderly parent's phone and becomes its home screen. The other runs on an adult family member's own phone and sets that home screen up remotely. This policy explains exactly what moves between the two, and what never does.

The short version. Dekhbhal is not a tracking app. A family member changes our app's settings on the parent's phone – their contact tiles, the apps on their home screen, their medicines, how strict the call shield is. In return the parent's phone reports only four things, which the parent agrees to on their own screen before anything is sent at all: that the Help button was pressed (with a location only if they separately allowed it), whether a medicine was taken or missed, the battery level and last-seen time, and a daily count of unknown calls the shield stopped. That is the entire list. The parent's phone shows a notification saying sharing is on for as long as the app runs, and the parent can stop it themselves at any time.

What Dekhbhal can never show the family Who the parent called or who called them, any phone number that called, what they wrote or received, which apps they opened or for how long, anything on their screen, and where they are at any moment other than a single Help press they made themselves. None of this is collected, so none of it can be shown, exported or recovered.

What the Parent Agrees To

Before the parent's phone sends anything, it shows a consent screen in large Hindi type listing what will be shared, and waits for them to accept. Pairing does not complete without it. Declining leaves the phone unpaired and nothing is sent.

  • Help presses. When the parent presses the big red Help button and lets the five-second countdown finish, every paired family member is alerted, with the time.
  • Medicines. Whether a dose was taken, and how many minutes late, or that it was missed. The medicine's name travels with it, because that is what the family set.
  • Battery and last seen. The battery percentage, whether it is charging, and the minute the phone last checked in – about every thirty minutes, and whenever the app is opened or the phone restarts.
  • A daily count of stopped calls. A running total only, for example "3 unknown calls stopped today". No number, no time, no caller ever leaves the phone.
  • Which apps can be put on the home screen. On pairing, and when the installed apps change, the phone reports the names and package ids of apps that can be launched, so the family can choose which six appear. Which apps the parent actually opens, and for how long, is never read or reported.

Location

Location is optional and is asked for on its own setup step, which can be skipped. When it is granted, Dekhbhal takes one position fix, at the moment the parent presses Help, and attaches it to that alert as a Google Maps link the family can open.

There is no background location, no location worker and no location history. Dekhbhal does not request ACCESS_BACKGROUND_LOCATION. Between Help presses the app never asks the phone where it is. A Help press with no location granted still alerts the family; it simply carries no map link.

The Parent's Contacts Never Leave the Phone

The call shield has to know whether a ringing number belongs to someone the parent knows. To do that it reads the phone's own contacts, with the READ_CONTACTS permission the parent grants during setup.

That reading happens inside the call-screening callback, on the phone, while a call is ringing. The answer is a yes or no about one number. No contact name, no contact number and no contact list is stored by us or sent anywhere, ever – not to our servers, not to the family member's phone. The permission step can be skipped, and the shield still works from the lists the family set.

What the Family Member's Side Collects

  • A Google account. The family member signs in with Google, so their name and email address identify the account. The parent's phone signs in anonymously and has no email address.
  • What they type about their parent. The parent's name, the relation word they chose, an optional photo, the parent's phone number, the contact tiles (name, number, optional photo), medicines (name, dose note, times, days), the call shield level and its allowed numbers, and which number the Help button should call. All of this is typed by the family member and sent to the parent's phone, because it is the setup.
  • Alerts and events that the parent's phone reported, as listed above, kept so the dashboard and the alert feed can show them. They are deleted automatically after 90 days.

Medicine names and dose notes can name a condition, so they are treated as sensitive: they are visible only to the paired family members and the parent's own phone, and are never used for advertising or shared with anyone.

Analytics and Error Reports

Dekhbhal sends our own analytics endpoint a fixed set of event names – a role was chosen, a pairing succeeded or failed and why, a permission was granted or skipped, a setup was saved, a reminder was shown, a dose was taken or missed, a call was screened, Help was pressed – along with a device identifier and the app version. The call-screening event carries the shield's level and no number, no time and no caller. These answer whether people can set the app up and whether they keep using it. They are never sold and never used for advertising.

Permissions and Why We Need Them

  • Home app (launcher) role – Dekhbhal is the parent's home screen. This is granted on the parent's phone only, and can be changed back from Android settings at any time.
  • Call-screening role – the scam shield. It lets Android hand us a ringing call so we can decide whether it rings. Dekhbhal does not request READ_CALL_LOG or read the call log.
  • READ_CONTACTS – the shield's allow-list only, read on the phone and never uploaded. See above.
  • CALL_PHONE and ANSWER_PHONE_CALLS – a contact tile and the Help button place a call through the phone's own dialer, and the Help screen offers a button to end it.
  • SCHEDULE_EXACT_ALARM – a medicine reminder has to arrive at the time it was set for. If the step is skipped, reminders still work but may drift, and the family is warned.
  • USE_FULL_SCREEN_INTENT and POST_NOTIFICATIONS – the reminder has to be readable on a locked phone, and the sharing notice has to be visible.
  • Location – optional, one fix on a Help press. See above.
  • INTERNET and RECEIVE_BOOT_COMPLETED – to reach our server and to rebuild the medicine alarms after a restart.

Dekhbhal does not request or use READ_SMS, SEND_SMS, RECEIVE_SMS, READ_CALL_LOG, ACCESS_BACKGROUND_LOCATION, QUERY_ALL_PACKAGES, the microphone, the camera, usage-access or any accessibility service.

The Parent Stays in Control

From the parent's own settings screen, behind a four-digit sharing PIN, the parent can stop sharing entirely. The family member is told that it happened. Nothing further is sent from that phone, and the family can no longer change its setup. The phone keeps working as an ordinary phone.

Deleting Your Data

  • From the app. The family member's settings screen has "Delete my data", which removes the family, every parent paired to it, their setups, events and alerts, and the sign-in account itself.
  • By unpairing. Either side can unpair, which removes the data for that pairing.
  • By email. Write to contact@trei.dev and we will delete it.
  • Automatically. Events and alerts are deleted after 90 days regardless.

Security, Storage and Third Parties

Everything the app sends travels over HTTPS and every request carries a signed Firebase identity token; each route checks that the caller is either the paired phone or a member of that parent's family. Pair codes are single-use, expire in fifteen minutes, are rate limited and are never written to logs in plain text. Data is held on our own servers in a database used by Dekhbhal alone.

Dekhbhal uses Google Firebase for sign-in and for push messages (Firebase Privacy). It contains no advertising, no advertising SDK, no payments and no subscription SDK.

Who Dekhbhal Is For

Dekhbhal is for adults: an adult family member setting up a phone for an adult parent, with that parent's agreement. It is not directed at children, and we do not knowingly collect data from anyone under 18.

Changes to This Policy

We may update this policy when features change. Updates are posted here with a new "Last Updated" date.

Contact

Trei
Email: contact@trei.dev
Phone: +91 85500 77767
Website: trei.dev  ·  Contact form