Privacy Policy

This Privacy Policy covers the LIAFI Android app (com.liafi.agent) and liafi.in. The app and website are independently developed and operated by Sagar Singh Kushwaha, their sole owner and developer. This policy explains which data is kept on your phone, which data is sent to our service or other providers, and your choices. It applies to both direct-download and Google Play distributions; permission differences are identified below.

Google account · Local files · Auto SMS · Drive backup · Retention · Request deletion

1. Google sign-in and app access

Google supplies your verified account identifier, email address and display name. We use these to authenticate your account, determine trial and paid access, match website purchases and provide support. We do not receive your Google password.

The app sends an app device identifier, installation identifier, phone model and app version. Our service stores account/trial/paid dates, active-phone bindings, session-credential hashes and protected short-lived authentication retry records. These support one active phone, the single eligible 30-day account trial, transfers, security and access verification. Trials and paid access have a limited offline verification window of up to seven days, never beyond signed access expiry. Historical licence records may be retained for payment reconciliation and support. Licence-key activation, validation and recovery are no longer supported.

2. Profile, client documents and other local records

After you sign in, LIAFI asks you to create your agent profile before using the app. Your name, mobile number, agency code, branch code, agency start year and club type are saved to your LIAFI account so they can be restored when you reinstall or change phones and so LIAFI can support you. New forms request agency code instead of age; previously supplied ages remain stored for compatibility. Your profile photo stays on your phone and in your optional backup. Staff assigned to your saved branch can see your profile name, mobile number, agency code, agency start year and club type.

Your agent profile, client folder names and policy numbers, scans/PDFs, E-cards, competition records, My Khata ledger and reminder history, BMI records and SMS settings/logs are stored on your phone. Apart from the account/profile details and separately described shared features, LIAFI's account servers do not receive these local records or document contents through ordinary use. Optional encrypted backup and user-initiated sharing are separate actions described below.

Camera access is used for scanning. Selected photos, files and PDFs are imported when you choose them. Document processing and BMI calculations take place on-device. The BMI calculator is an informational calculation, not medical diagnosis or treatment. The My Group Insurance Calculator tile displays fixed benefit amounts based on profile details; it does not sell, issue, arrange or underwrite insurance, determine a claim, or promise that a user is eligible for cover. Confirm actual benefits with the relevant provider or administrator. LIAFI does not provide personalized financial or insurance advice. If you open a Mediclaim/WhatsApp service or download an E-card link, that provider receives the request, link details and normal network information; WhatsApp or the provider handles any details you send there. LIAFI does not read your WhatsApp chats. Exporting or sharing gives the selected files to the app or recipient you choose.

Saving a client requires a name and valid phone number. If you allow Contacts access, LIAFI checks the entered number locally to avoid creating another phone contact for a number already saved. The lookup does not import or upload your address book to LIAFI servers. You can instead choose a phone contact with Android's picker. New phone contacts are created through Android's contact editor; this is on by default and can be disabled in App settings. Declining lookup access does not silently create a contact. Client details you save are stored locally and may be included in your optional encrypted Drive backup.

3. Optional Auto SMS and phone permissions

Auto SMS is off unless you enable it and grant the required access. It reads recent call-log entries, including numbers, caller names when available, call type, duration and time, plus relevant phone/SIM information. It uses that information on-device to decide whether to send your configured follow-up from your own SIM. Android/carrier delivery information and the recipient/message details are kept in the local sending log. Carrier charges can apply.

The app requests permission to send SMS; it does not request permission to read your SMS inbox or receive incoming SMS/MMS. LIAFI account servers do not receive your call history or SMS message contents. These records may be included in your optional encrypted Drive backup.

Contacts access is requested separately for the client-save lookup described above in both distributions. Google Play's Auto SMS setup does not request Contacts access; direct-download builds may offer optional Contacts lookup for caller names. You can decline optional access. Notification and battery/background settings help show and maintain automation; they do not grant SMS access. Stop Auto SMS from its screen or ongoing notification, or revoke phone/SMS permissions in Android settings. Battery settings and your phone manufacturer can affect reliability.

My Khata payment reminders

My Khata records money you paid for clients and their repayments; it does not verify LIC premium status. After you confirm the message and the scope of current and future paid-for Khata clients, optional reminders apply to that scope except clients you exclude. They use those clients' mobile numbers, current overdue balances, your chosen message and your profile name. These details and reminder history stay on your phone and in your optional encrypted Drive backup. LIAFI's account service verifies account access and the active phone; it does not receive the ledger, reminder recipients, balances or message contents for dispatch.

Payment reminders are off by default and separate from follow-ups after calls. Google Play builds prepare reminders for you to review and send in your messaging app. Supported direct builds can send from a SIM you select after you confirm the message and recipients and grant SMS and phone/SIM access. No SMS-inbox or call-log access is requested for payment reminders. Carrier charges may apply, and your carrier and intended recipient process the SMS.

Reminders begin after an expected repayment date, target 9 AM India time, and may catch up between 9 AM and 6 PM when Android allows. There are at most three sent or explicitly confirmed reminders per client, at least three days apart. Full repayment stops further reminders; partial repayments reduce the overdue amount. Pause a client or disable payment reminders from My Khata or App settings. Sending does not prove delivery, and an SMS already handed to the carrier cannot be recalled. Restoring a backup preserves history but disables reminders until you reconfirm recipients and the sending SIM.

4. Optional encrypted Google Drive backup

Drive authorization is requested separately for app-created Drive files and private application data, using the same Google account. You may decline it and use the app without backup. Backups can contain local documents, profile information, settings and SMS logs.

New backups use an AES-256 key generated on the phone. A recovery key is stored in your Google Drive private app-data folder, allowing the same Google account to restore without a routine backup password. Google authorization protects access to that folder. It is hidden from the usual Drive interface; this is not a claim that Google cannot access data it hosts. LIAFI servers do not receive your backup contents or recovery key.

Current backups coordinate their encrypted files, checksums and versions through your Google Drive. Older installations may retain server-side backup references and use a one-time legacy handoff when upgrading. LIAFI's account service still verifies access and the active phone. Older password-protected backups may require the original password once. Keep your Google account secure. Old backup generations may contain files deleted locally until cleanup completes. Revoking Drive permission does not delete existing backups, and deleting recovery data can make backups unreadable.

5. Website purchases and support

For a website purchase we collect your name, mobile number, email, LIC agency code, LIC branch code and selected fee. We keep order/payment identifiers, amounts, status and account entitlement records for settlement, renewal, support, accounting and fraud prevention. Website payments are processed by Razorpay; we do not receive your card number, UPI PIN, banking password or bank credentials. See Razorpay's privacy policy.

Your branch code links the purchase to your LIC branch. The staff member LIAFI registers for that branch can see the name, mobile number, agency code, amount and date of purchases made with their branch code, and can send announcements to accounts of that branch through the app. Branch staff cannot see your email, payment identifiers, documents or other branches' purchases. Staff contact and bank details given to LIAFI for administration are visible only to the LIAFI administrator.

When you contact support, we receive the information you send and use it to respond, verify ownership and handle your request. Please do not send client documents, passwords, OTPs, tokens or recovery keys.

Branch staff may publish an organization contact directory for their branch, containing a designated person's name, designation and mobile number. Staff are asked to add only contacts approved for sharing. Authenticated users with current app access see only the directory matching their saved branch code. These directory records are kept on LIAFI's server and loaded into app memory when viewed; they are not added to phone contacts or personal Drive backups. Branch staff can correct or remove entries. Contact your branch staff or LIAFI support about a directory entry.

Push notifications

LIAFI uses Firebase Cloud Messaging to deliver announcements and competition updates. After sign-in, Google processes a per-installation identifier, a push registration token and technical connection information. Our server links the token to your LIAFI account and active phone to select the correct branch. Push messages contain update identifiers; the app retrieves authorized content from LIAFI. Client documents, call logs and SMS contents are not sent through FCM. Notification display is controlled by Android permissions. We remove stale server registrations after 45 days without renewal; signing out or moving to another phone prevents that session from receiving new targeted pushes. Firebase Analytics and release Crashlytics collection are not enabled by this messaging integration.

6. Cookies, hosting and diagnostics

The website uses a language cookie, a customer sign-in/session cookie and a separate administrator session cookie. These support language preferences, authentication and request security. Our website does not add advertising or third-party analytics cookies. Razorpay may use its own cookies during checkout. Hosting and network services process normal connection/request information such as IP addresses and request times for delivery, security and troubleshooting.

The app's Google ML Kit barcode-scanning SDK can send device/app information, per-installation identifiers, performance/usage metrics, API configuration, feature/input-output size and error events to Google for diagnostics and usage analytics over HTTPS. This SDK information is separate from document backup. See Google's ML Kit data disclosure and Google's privacy policy. The current Play build includes no advertising SDK or Firebase Crashlytics collection.

7. Sharing and security

We do not sell or rent personal data. Data is processed by Google for authentication, optional Drive storage and SDK diagnostics; our hosting providers for account services; Razorpay for payments; your chosen recipient/application when you share; and link/service providers when you use their services. We may disclose necessary information to meet a legal obligation or address fraud/security incidents. Providers can process data in countries where they operate.

HTTPS protects network transport. Android Keystore protects stored account credentials, and optional backups are encrypted before upload. Access to administrative records is restricted. No security measure guarantees absolute protection; protect your phone and Google account.

8. Retention, deletion and your choices

Local records remain until you remove them or clear app storage; signing out does not erase them. Account/access records are kept to operate the service until deletion is requested or they are no longer required. For verified deletion requests we arrange removal of account/profile data, sessions, device bindings and backup-reference metadata that do not have a documented retention basis. Payment/accounting records may need retention under applicable law, and limited records may be needed for security, unresolved disputes or trial-abuse prevention. We explain retained categories, reasons and applicable periods when handling your request rather than promising that every record is immediately removed.

You can request deletion of your LIAFI account and associated data at liafi.in/account-deletion, without reinstalling the app. You may also ask for access, correction or deletion of particular data by emailing contact@sanganixai.com. We verify ownership, explain the completion timetable and respond to the request. Account deletion does not automatically erase copies on your phone, your own Google Drive or files already shared with recipients. The deletion page explains those separate copies and recovery-key precautions.

You can revoke app permissions in Android settings and Google account settings. This does not retrospectively remove existing files or payment records. Contact us for help with an inaccessible account, a privacy concern or a grievance.

9. Adult users and policy changes

LIAFI is intended for adult insurance agents and is not directed at children under 18. If a child has provided personal information, contact us. We update the date above when this policy changes and provide an appropriate notice for material changes.

10. Developer, privacy and grievance contact

Sagar Singh Kushwaha — LIAFI developer and privacy contact
Email: contact@sanganixai.com
Phone: +91 70499 26442
Postal address: Jaysingpura, Jainabad, Madhya Pradesh, India