EmiStep Privacy Policy
Effective 15 October 2026 · Version 2026-10-15.1Operator and contact
EmiStep is operated by RELVO PROJECTS PRIVATE LIMITED, incorporated in India on 1 December 2025, CIN U74909KL2025PTC098789. Company mailing address recorded in the Certificate of Incorporation: Room No.17/153, Puzhambram, Gramam, Ponnani, Ponani, Ponnani, Malappuram - 679577, Kerala, India. Support, privacy and grievance requests: support@emistep.com. Responsible company contact: Muhammed Ansar AP, as designated in the company support/deletion documentation.
What we process
Phone number and Firebase account UID establish your account. You may enter loan labels, lender/reference text, categories, schedules, instalment amounts, self-recorded payments and reminder preferences. We store the accepted Terms and processing-notice versions/time. Firebase Authentication, App Check/Play Integrity and the web verification challenge process IP addresses, app/device identifiers, user-agent and security/attestation signals. We do not request contacts, SMS inbox, call logs, precise location, bank credentials or broad storage access.
Why, and which choices are optional
We process your phone/account identifiers for authentication and account management, and your entered records to provide the tracker and private cloud sync. Security signals prevent abuse. Loan entry is optional; information you choose to save is sent to the cloud. Notifications are optional and scheduled locally; denying permission does not stop record keeping. Export is optional and uses Android’s file picker. You can refuse phone-processing consent and decline the cloud service, or withdraw by requesting account deletion. Contractual Terms acceptance is a separate choice.
Google services and locations
Dedicated Google Firebase Authentication, Cloud Firestore, Cloud Functions, App Check and Hosting provide the service. Authentication processes phone numbers and related security information in the United States; Google also uses phone numbers for spam and abuse prevention across Google services. The account database and application functions use Mumbai, India. Hosting and attestation may use global infrastructure. We do not claim all data remains in India. The web deletion page uses Google’s phone-verification/reCAPTCHA flow. See https://firebase.google.com/support/privacy and https://policies.google.com/privacy.
Sharing and telemetry
We use service providers for these purposes and may disclose information where legally required. We do not sell loan records or add advertising, analytics or crash-reporting SDKs. Provider security/service logs still exist. There is no contact with lenders and no connection to Relvo CRM or another company app’s accounts. Local reminders do not transmit loan data through a push-notification service. Google authentication/attestation SDKs can exchange verification and installation signals.
Retention: live account records
Phone/Auth identity and cloud loan/payment records remain while the account is active. A verified deletion request creates a durable job. On successful completion it removes the account document, its acceptance record, any access entitlement and Firebase Auth user. Failures stay requested/processing and retry; completion is not claimed before these steps succeed. Deletion status/receipt records contain a UID, state and timestamps, not loan contents, and expire after seven days plus Firestore TTL processing delay.
Retention: logs and provider copies
Our default application/request log bucket retains entries for 30 days; we intentionally omit OTPs, tokens and loan contents from application logs. Google’s required administrative audit logs have provider-defined retention (normally 400 days). Firebase Authentication retains logged IP addresses for a few weeks and removes other authentication information from live/backup systems within 180 days after deletion is initiated. App Check token validity here is one hour; attestation-provider retention follows that provider’s terms. There is no configured account-database scheduled backup or point-in-time recovery. Underlying provider operational copies follow its contractual deletion lifecycle; we do not promise immediate erasure from every provider system.
Device storage, restore and exports
The app encrypts local account copies with Android Keystore. Android cloud backup and device-transfer backup are excluded by app configuration. Cloud records can be restored only by verifying the same existing account; an offline preview is not a cloud backup. After confirmed in-app deletion, the current cloud cache, matching preview records and local reminders are cleared. A remotely deleted account is denied server access; other devices clear account state when they next validate. Offline copies cannot be remotely erased while a device is disconnected: clear app storage or uninstall. Exported JSON files remain under your control. A newly created account after deletion has a different identity and cannot restore the deleted account’s records.
Security
We use HTTPS, encrypted device storage, Google storage protections, restricted backend access, phone verification and App Check on app data calls. The web erasure API accepts only recent verified phone identity; private random receipts reveal deletion status only. No system is risk-free. Never share OTPs, passwords or full financial records in support email.
Access, correction, erasure and grievances
Review/correct entries in the app, export your records, or delete your account in Profile or at https://emistep-relvo.web.app/delete-account.html. You do not need successful support-email delivery to submit verified deletion. For questions, access/correction requests or complaints contact support@emistep.com; the company contact handles privacy grievances. We may verify ownership proportionately. These notices do not limit statutory rights or access to an applicable authority.
Adults and changes
EmiStep is intended for adults aged 18+. We do not collect identity documents or KYC to use this tracker. Material processing changes will be described before requesting any additional consent needed. Current availability is India-first; broader distribution requires market review. Version 2026-10-15.1 is effective 15 October 2026.