Privacy policy
Effective October 17, 2026. Contact the developer operating under the name Bitter Softworks at davilapps@gmail.com.
The backend operates with limited availability while the updated app awaits release qualification. It is not a monitored emergency-response service. No guarantee of connectivity, delivery, rescue or continuous operation is made.
Information on your phone
Trusted-contact names, phone numbers, optional email addresses, preferences and alert history use encrypted app-private storage. Android backups are disabled. We do not read your address book, SMS inbox or call history. Chosen contact information and alert content are passed to the messaging services you use.
Location and private tracking
After your separate agreement and Android permission, the app collects precise location only during an alert you activate, including when the app is closed or not in use. Ending the alert stops new collection. With relay enrollment, a pseudonymous device identity, alert/session details, timestamps and location points are transmitted over HTTPS. Location is encrypted at rest; the relay operator can decrypt it to serve authorized viewers. This is not end-to-end encryption.
People with the private viewer link can view the alert and available trail and can copy or forward it. The viewer makes no automatic phone call or notification and does not dispatch help. Opening a Maps link sends those coordinates to your maps provider.
Gmail and SMS
Gmail connection is optional and requests only permission to send email from your selected account. No inbox-reading permission, password or full-mailbox access is requested. Google processes the sender, chosen recipients, content and any location/viewer link. Google access tokens stay in memory and are not sent to our relay. Pending email is encrypted on the phone. Google user data is not sold or used for advertising.
Our use and transfer of Google user data follows the Google API Services User Data Policy, including its Limited Use requirements.
SMS and manual email open the user's messaging application; the user must tap Send. Connected Gmail can submit automatic alerts. Submission/acceptance does not prove delivery or reading. Disconnecting requests Google access revocation and cancels pending sends but cannot recall submitted messages. Review access in your Google Account if offline revocation could not complete.
Optional minute email reminders
Updated builds offer a separate switch, off by default, for future alerts only. While the phone's finite tracking window remains active, reminders attempt a follow-up at least one minute after the previous accepted email. Android scheduling, connectivity and Gmail can delay or prevent sending. The app never sends a burst of missed reminders on reconnection. Up to 60 follow-up messages, including first-location/viewer-link follow-ups, may be created per alert. End, tracking expiry, disconnection or an unresolved email failure prevents further reminders; turning the switch off cancels unsent minute reminders. Already submitted email cannot be recalled. A self-test remains one message.
An encrypted local rolling-24-hour ledger limits all app email to 100 possible submission attempts and 400 recipient attempts, counting retries and uncertain submissions conservatively. These are local app safeguards, not guarantees of provider quota availability or global project cost. Other email activity and Gmail limits can block sending sooner. Tracking and manual contact options are separate from these email limits. The phone stores only bounded timestamps/counts for this ledger, not Gmail tokens or inbox contents. Uncertain sends are not automatically repeated as definitely unsent. Tell trusted contacts about reminders and obtain their agreement before enabling them.
Advertising and purchases
This private build uses Google's official test ad identifiers only. Ads remain off until privacy checks permit requests, and privacy choices are available in More. Google Mobile Ads may process IP-derived approximate location, identifiers, interactions and diagnostics. We do not provide precise alert locations, contact lists or Gmail data to the ad SDK.
Production purchases are disabled in the private pilot. When qualified and enabled, Google Play handles billing. The app sends its purchase token and pseudonymous device identity to our verifier to establish subscription access. We do not receive card details. Our relay uses Google/Firebase infrastructure. Firebase Analytics has not been integrated into the current app.
App accounts and allowance records
The updated app uses email/password app sign-in handled by Firebase Authentication with Identity Platform. Use an app-specific password, never your Gmail password. Firebase receives the app email/password to create or authenticate the account and can send verification/password-reset messages when requested. The phone stores an encrypted refresh session; passwords are not saved by the app or sent to our relay. The relay verifies a Firebase identity token and stores an opaque account identifier, not the email/password or raw Firebase token. Existing registered older versions keep their original tracking route during the transition; newly registered phones use the account-based route.
The account ledger retains a minimal demo-use marker, device/alert identifiers and cutoff so another alert, month, reinstall or second device using the same account cannot obtain another demo. Verified subscription lease deadlines may be stored with the account; raw purchase tokens are not stored in this ledger. Account/allowance records do not automatically expire with seven-day location history and are removed through account deletion. Different new accounts remain an abuse risk. A phone/account connection must be rechecked online within 24 hours before a new tracking start and after reboot. Public rollout and paid-plan qualification remain unfinished; this update has not been submitted for Google Play review.
Phone registration and admission controls
Updated builds can register a phone after verified app sign-in without an operator code. The phone creates a signing key in Android Keystore and proves possession of it. The relay stores the public key and pseudonymous account association; the private key and Firebase token are not stored on our server. Registration alone does not start tracking, grant a second demo or move protection away from another phone. Moving protection requires fresh app-password confirmation and ended active alerts.
Initial self-service intake is capped at 100 new phone registrations per UTC calendar month across the service and five per app account, with additional request limits. A retry with an already registered key does not consume another slot. When intake is full or closed, new setup is unavailable; registered phones are not disabled by that admission control. The account retains only its registration month/count, removed with account deletion. A separate aggregate counter contains no user identifier and expires seven days after the month ends, subject to asynchronous database TTL. These controls reduce abuse but are not proof of a unique person, a guarantee against new-account abuse or a hard spending cap.
Account deletion processing
In updated builds, More → App account → Delete app account & data asks you to confirm with your current app password. Google authenticates that password; our relay receives the identity token, never the password. End active tracking first. Deletion revokes account tracking access and removes associated sessions, locations, viewer records, device registrations, the Firebase app-authentication account and the allowance ledger before reporting completion. Only the authenticated account's records are selected, not another account's data on a previously shared phone. It does not delete your Google account or cancel a Google Play subscription.
Cleanup is bounded and may require Continue account deletion after a connection interruption or a large history. A pending cleanup record stores an encrypted Firebase user identifier and limited progress metadata, with a 30-day renewable expiry; the phone stores an encrypted continuation receipt. Completed cleanup removes that user identifier and keeps a minimal retry/abuse-prevention receipt for seven days. A revoked registration temporarily needed for another account's retained legacy history can remain for up to seven days. Database TTL deletion is asynchronous. Short-lived rate/replay records expire separately. If a pending receipt expires or you cannot continue, use the support deletion request below. A pending request is not represented as complete.
Completion clears contacts, history, pending location and email records, app sign-in and relay registration on the requesting phone, and requests Gmail revocation. If Google revocation cannot be confirmed, remove the app's access in Google Account settings. Other phones' local data is not remotely erased; end alerts and clear those phones separately. Sent messages and provider audit/billing records remain subject to their own retention rules.
Usage and family-view limits
For the planned paid plan, the account ledger also stores a protected-phone identifier, UTC calendar-month usage and reserved tracking time. These records prevent a phone move, new alert or refreshed purchase from resetting the allowance. Unused reserved time is returned when End reaches the server; delayed delivery can reduce that return. Sessions store up to three short-lived hashed browser-slot identifiers and activity deadlines to enforce simultaneous viewing limits. Viewer cookies remain private credentials. See the subscription terms for time limits and resets. Purchases are not active.
Plan and usage records
The account ledger also stores the verified plan identifier and absolute monthly used/reserved tracking time; sessions retain their granted tier, point ceiling and cutoff. These records enforce paid allowances and prevent a refresh, plan change or repeated End from creating extra time. Raw Play purchase tokens are not retained in this ledger. Plan/usage records are removed through app-account deletion, not location-history expiry.
Retention
Remote session access expires no later than seven days after session creation. Database TTL cleanup is asynchronous and is not instant physical deletion. Ended viewer links can remain accessible for up to two hours, within their original expiry. Local history stays until you delete it or clear app data.
Pending initial mail expires after 24 hours when processed; minute reminders expire after at most two minutes or the remaining tracking window, whichever is shorter. Local mail metadata is bounded to 100 rows; completed rows can be evicted earlier and seven-day rows are pruned on enqueue, not by a guaranteed deletion timer. Rolling-day email counters are pruned on submission; disconnect does not reset them. Account deletion clears the requesting phone's email records and counters. Native location queues are bounded. Device registration remains until a verified removal request is handled. Security replay/rate/tombstone records use bounded expiry. Recipients and providers may retain sent messages under their own policies.
Deletion and choices
Request deletion of remote app data or an app account, even if the app is no longer installed.
Delete individual contacts in Contacts, or use More → Delete saved contacts and history. That action does not erase native pending outboxes or remote records, disconnect Gmail, remove an app account or cancel subscriptions. Clearing app storage or uninstalling can discard unsent updates and enrollment. End an active alert first.
Email davilapps@gmail.com and specify the app account and phone relay data you want removed. We verify ownership before acting; do not send passwords, codes, coordinates or private viewer links. Consumer account/deletion handling is still being qualified; this is not instant self-service deletion. This request does not cancel Google Play billing or erase messages held by recipients.
Location permissions can be changed in Android Settings. App sign-out and optional Gmail disconnection are separate actions in More. Review Gmail access in Google Account permissions and manage/cancel subscriptions separately in Google Play. App-account deletion does not delete your Google/Gmail account.
Audience, safety and updates
The current pilot is intended for adults, including people seeking help with independent living. Do not use it for covert monitoring. It provides no automatic fall detection, diagnosis, medical/police dispatch or guaranteed rescue. We update this notice when data practices change, and obtain new consent where required. Contact support for privacy questions or requests.