BipTab Privacy Policy
Quiet Pulsar · support@quiet-pulsar.ru
Updated 7 October 2026
1. Data on your device
Medication names, doses, schedules, intake history, inventory, expiry dates, notes, treatment plans and their runs, your entered name and preferences are stored locally. No app account is required. The developer has no server collecting these records. Medication information is not sent to advertising or payment services. Android backup of app data is disabled.
2. Reminders and flashlight
Android notification and exact alarm permissions support reminders. Medication names and doses may appear in notifications, including on the lock screen according to your phone settings. Light signals are free and enabled by the user. During a reminder the flashlight blinks until the app home screen is opened or the signal is stopped; the manual preview blinks three times. Background signals depend on Android permissions and device support. Light signals do not record photos or videos. The separate Photograph package feature opens the camera only at your request. The photo and recognized text are processed on the phone and are not sent to a server or advertising SDK. The temporary photo is deleted after processing or cancellation. You confirm the name and enter the dose and schedule yourself.
3. Advertising
Yandex supplies advertising, which loads automatically in the free version. The app configures the SDK without consent to personalization (setUserConsent(false)); there is no separate advertising preference prompt. The SDK connects to Yandex servers and may process technical device data, IP address, ad interactions and advertising identifiers within SDK settings and device permissions. Location tracking is disabled. Non-personalized mode does not stop all technical data exchange. Medication information is not supplied for ad targeting. Premium disables ads.
Yandex policy: https://yandex.ru/legal/confidential/
SDK data information: https://ads.yandex.com/helpcenter/en/easy/integration/android/advanced-settings/security-privacy
4. Premium purchases in RuStore
RuStore processes subscriptions and renewals. The app receives product information, purchase status, transaction identifiers and subscription expiration to provide paid access. Card details are not stored by the app or sent to the developer. The payment service displays its applicable data terms. Medication names, doses, history and your entered name are not sent to RuStore. Purchase status verification needs an internet connection.
5. Export and deletion
You can export a JSON file to a location you choose. It contains medication and intake information, so choose its storage location carefully. Delete all my data removes local medications, history, treatment plans and settings. It does not remove exported files, records held by payment or advertising services, or cancel a subscription. Cancel renewal separately in RuStore → Profile → Subscriptions.
6. Support
If you email support@quiet-pulsar.ru, the developer receives your address and message to reply. Avoid including medical records, payment information or passwords unless necessary to describe a problem. Apart from verification codes and Premium service messages, the app does not send automatic emails. Diagnostic files for support are not sent automatically. Advertising SDK processing is described separately below.
7. Updates and contact
Updated policies are included with app updates. For questions about data or deleting support correspondence, contact support@quiet-pulsar.ru. Public developer name: Quiet Pulsar.
Premium payments and recovery through YooKassa
The BipTab server processes your verified email, random installation identifier, selected plan, order, payment amount and status, Premium period and accepted terms version. It stores verification hashes of installation tokens and one-time codes. Email is used for verification, recovery, electronic receipts and service messages.
YooKassa receives order data and email to process payment and issue a receipt. REG.RU sends one-time codes and service emails over an encrypted connection. This mechanism is not used for marketing emails. The BipTab server does not receive or store card details.
App-to-server communication uses HTTPS. Database access is restricted; email and payment records are not separately encrypted inside the database. Medications, doses, schedules, intake history and medical notes are not sent to the payment backend or YooKassa.
Deleting local app data does not delete server purchase records. Contact support@quiet-pulsar.ru about processing or deleting server data. Deletion of payment documents is subject to applicable record-retention requirements.
Premium account and deletion
In the Google Play version for Russia, your verified email identifies your Premium account. A random installation identifier and a token verifier link your device to the account. No account password is created. Access costs RUB 99 for one month or RUB 999 for one year. Auto-renewal is disabled.
Delete your Premium account through Profile → Premium → Manage Premium account, or without installing the app at https://www.quiet-pulsar.ru/biptab/delete-account. Deletion requires a separate email code and explicit confirmation of its consequences. Codes expire in 10 minutes and attempts are limited.
Confirmation removes the account email and profile, access tokens for all linked devices, installation links, recovery records, server entitlement and account service records from the active database. Old tokens stop working. Previously verified paid access remains locally on current devices until its expiry; it cannot be restored by email after reinstalling or on new devices. Creating another account with the same email does not recover the deleted purchase. Local medicines and reminders remain on the device.
When you delete your account, data needed to operate your Premium account are deleted or de-identified. Certain payment and fiscal transaction records are retained for the period required by Russian tax law — five years — solely to meet legal, tax and financial obligations. These records are not used for advertising, analytical profiling or restoring a deleted account. Deleted account data may temporarily remain in protected backups for no more than 30 days until scheduled rotation.
AppMetrica technical analytics
Yandex Mobile Ads includes AppMetrica for technical diagnostics and advertising statistics. Optional app analytics synchronization is disabled in the Google Play build. BipTab does not send AppMetrica your email, Premium account identifier, custom user profile, medicine names, doses, schedules, treatment plans, notes or reminder text. BipTab product counters remain on the device and are not sent to AppMetrica. Location tracking is disabled. BipTab does not report Premium purchases to AppMetrica.
How advertising analytics works
The embedded SDK may send Yandex device identifiers, system and SDK versions, advertising events, errors and performance information. BipTab does not link these data to your Premium account. Analytics without a BipTab account association are not necessarily anonymous: technical identifiers may still be personal data. Yandex AppMetrica processes these data under its service terms and Yandex privacy policy: https://yandex.ru/legal/metrica_termsofuse/ and https://yandex.ru/legal/confidential/. We do not set or promise a separate Yandex retention period. Deleting a Premium account does not automatically delete advertising SDK records held by Yandex. Contact support@quiet-pulsar.ru; the request procedure is also described at https://appmetrica.yandex.ru/docs/en/data-security/delete-data.
Server backups
The Premium server automatically creates encrypted database backups for disaster recovery. Access is limited to administrators and the encryption key is stored separately. Ordinary server backups expire automatically within 30 days while the cleanup service is operational. After account deletion, old account data may temporarily remain only in these protected snapshots until expiry. Backups are not used to restore an individual deleted account. Whole-service disaster recovery reapplies recorded deletions and invalidates old one-time codes. A minimal deletion journal contains only a random account identifier and deletion time, without email, and is kept for 35 days to cover older snapshots.
Technical record lifetimes
Verification codes expire after 10 minutes; expired records are cleaned hourly. A completion proof without email is retained for 24 hours to safely retry a deletion response. Rate-limit records older than 24 hours are removed at the next hourly cleanup. Unverified installations older than 30 days without a valid code are removed during cleanup. Verified device links, token verifiers and server entitlements are removed with the account. Dedicated BipTab operational logs are limited to 14 days and contain no app email, tokens, codes or medical information.
Financial records after deletion
Separate records contain only the amount, currency, plan, transaction dates and status, YooKassa payment identifier and available receipt information. An internal financial reference replaces the link to the deleted account; separated records contain no email, checkout links, tokens or medical data. Verified YooKassa notification records contain only the operation identifier, verification result and time, not the full notification payload. Five complete years are counted after the year of the last financial operation; expired records and their separate financial copies are automatically removed. The financial archive is not subject to the 30-day ordinary backup limit. Account deletion does not delete a receipt held by YooKassa and is not a refund. Contact support@quiet-pulsar.ru about financial documents.