TRUST FUELS PROGRESSAndhra Pradesh & Telangana · India

SSF website & mobile apps

Privacy policy

Privacy policy for SSF Consumer, SSF Lead, SSF Collection and this website.

Last updated: 12 October 2026

1. Scope & operator

This privacy policy explains how SRI SATYA FINANCE CORPORATION, operating as Sri Satya Finance (“SSF”, “we”, “us”), handles information through SSF Consumer, SSF Lead, SSF Collection and the website srisatyafinance.com. It covers information about authorised staff, customers, borrowers, guarantors and other people whose records are handled through these apps.

SRI SATYA FINANCE CORPORATION
D No. 44-15-24, Bypass Road, near DMH School, Annapurnampeta,
Rajamahendravaram – 533101, Andhra Pradesh, India

Email: [email protected]
Phone: +91 88866 73333

SSF provides finance exclusively for purchasing vehicles. It does not offer personal cash loans, payday loans or loans against already-owned vehicles. SSF Lead and SSF Collection are tools for authorised staff handling vehicle-purchase finance applications and existing accounts; they do not provide public borrower registration or personal cash-loan applications. Customer information may be entered by authorised staff or retrieved from SSF’s systems. Device permission from a staff member does not replace any notice or consent required from the customer whose information is entered.

2. Apps covered

SSF Lead

SSF Lead supports customer registration, document uploads, vehicle-purchase finance lead management, loan application preparation and application tracking.

SSF Collection

SSF Collection supports servicing existing vehicle-purchase finance accounts, instalment collections, receipts, cash deposits, expenses, follow-up notes, loan closure and authorised vehicle seizure, release and sale workflows.

SSF Consumer

SSF Consumer gives existing customers access to vehicle-purchase finance accounts, including accounts where they are guarantors. It supports viewing loan details, instalment schedules, dues, transaction history and receipts, submitting complaints, requesting phone or address changes, and receiving account notifications. It does not provide new loan applications or process EMI payments inside the app. Where payment-information features are available, they display SSF payment details or QR codes for use in an external payment application.

3. Information handled

The information used depends on the app, the task, the record and the user’s authorised access. Not every field is required for every transaction.

CategoryInformation and use
Consumer authentication and preferencesMobile number and country code, one-time passwords submitted for verification, authentication token, selected language, Firebase Cloud Messaging registration token and device platform used for account access and notifications.
Consumer account informationExisting customer profile and identifiers, contact and address information, profile image and identity or bank information where present in SSF records; borrower and guarantor relationships; vehicle details; loan terms, schedules, balances, dues, charges, payment references, transaction history and receipts retrieved from SSF’s backend. Some information is retrieved as part of an account response even when not displayed on every screen.
Consumer requestsNew phone number, verification codes, requested address details, complaint description, issue category, urgency, associated loan reference, status and staff responses, used to verify and handle your requests.
Staff accountsLogin identifiers and passwords submitted for authentication; staff profile and role information; authentication tokens and an app MPIN used for account access.
Customer and related-person recordsNames, phone numbers, email, date of birth, gender, addresses, photographs, family or reference information, education and income information used for customer and loan records.
Identity informationAadhaar and, where entered or present in records, PAN, passport, voter ID, driving licence, ration card, GST, CIN and CKYC identifiers, together with supporting images.
Bank and vehicle informationLead app records can include bank account number, holder name, account type, bank, branch and IFSC; vehicle ownership, make, variant, registration, engine and chassis information and associated amounts.
Loan and operational recordsLoan applications, amounts, interest and instalment terms, balances, dues, charges, payments, receipts, cash deposits, expenses, notes, reminders, closure and repossession records.
ImagesPhotographs or images deliberately captured or selected for customer profiles, documents, notes or transaction evidence and uploaded to SSF’s backend.
LocationSSF Collection obtains the staff device’s current location during selected user-initiated activities and includes latitude and longitude with the corresponding record.
Technical informationNetwork connection information needed to communicate with the service, app version information, and printer names or addresses used for Bluetooth connections. Hosting infrastructure processes IP addresses and request metadata when serving requests.

4. Purposes & device permissions

Information is used to authenticate staff, maintain customer and vehicle records, prepare and track loan applications, administer loans, record payments and field activities, generate receipts, handle follow-ups and provide support.

Consumer login, requests and notifications

SSF Consumer uses your phone number and OTP to authenticate access to existing accounts. On Android, optional SMS Retriever autofill supplies a matching verification code; it does not provide general SMS-inbox access. You can enter the OTP manually. Phone-change requests use OTP verification; address-change and complaint requests are sent to SSF for processing.

Consumer uses Firebase Cloud Messaging to receive account reminders and confirmations, including notification content and related loan references. Its registration token and device platform are sent to SSF to route messages. You can decline or disable notification permission in device settings and continue signing in. In-app notification records are also retrieved from SSF. Control lock-screen notification visibility through your device settings.

The Consumer features described here do not collect device location or provide camera, microphone, contact-list or photo-library scanning. Profile images and documents already held in SSF’s records may be retrieved from the backend. The current complaint form submits text and does not provide an attachment-upload picker.

Location — SSF Collection

Location is requested while using selected features, including instalment collection, cash-deposit recording, field notes, vehicle seizure and release. Coordinates are sent with those operational records to identify where the action was recorded. Some receipt-printing flows also request current location. This policy covers foreground, action-based location access: the release does not request background-location permission or provide continuous background location tracking. SSF Lead does not collect device location through the features covered here.

Users can decline or revoke location permission in device settings. Collection features that require a location cannot complete without it. Turning off permission stops new location access but does not delete coordinates already submitted.

Camera and photos

Camera and image-selection features let staff deliberately capture or choose images for upload. Declining the relevant access prevents that input method. These features do not scan the phone’s entire photo library or record audio.

Bluetooth and telephone

Collection uses Bluetooth device discovery and connection to print receipts on a selected compatible printer. Receipt content is transmitted to that printer. Calling features open or use the phone dialling functionality for a selected customer number. The features covered here do not read the device’s address book, SMS inbox or call history.

Consumer downloads, sharing and external services

Consumer can generate and save receipt PDFs and, where available, payment QR images. Android 10 and later use system storage APIs for these downloads; older Android versions may request storage-write access. This is for saving selected files, not browsing your existing files. If you choose to share a receipt or QR slip, the file is passed to the application or recipient you select through the system share sheet. Saved and shared receipts may contain personal and financial information.

Consumer support buttons open the phone dialler or WhatsApp. QR payment information is used outside Consumer; the selected payment provider’s privacy practices apply. Consumer does not collect a UPI PIN or payment-card credentials to process a payment.

Transactional messages

Some Collection transactions include a request for the backend to send an SMS notification. This is separate from reading SMS messages on the staff device.

5. Transmission & sharing

App records and uploaded images are transmitted over HTTPS to SSF’s backend services hosted on Railway. Information is processed by those services and accessed through authorised operational accounts. Client-side role checks control some app features; access to backend records also depends on SSF’s server configuration.

Consumer uses Google Firebase Cloud Messaging for push delivery. Google processes the messaging registration identifiers and technical information needed to provide that service; notification payloads can include account-related content and loan references. OTP delivery also involves the backend’s messaging provider. Consumer’s Google Fonts integration may retrieve fonts from external font services. Information can be handled by infrastructure providers supporting the backend and, where transactional SMS is sent, the messaging delivery service. This policy does not describe unrelated advertising or marketing integrations.

If a staff member selects “Open in Maps” for a saved Collection note, its coordinates are passed to Google Maps in an external application or browser. Google’s terms and privacy practices apply to that service. Receipt printing sends the chosen receipt to the selected printer. Google Fonts and PDF font-loading features may contact external font services to retrieve fonts.

For information about the providers involved in a specific record or transaction, contact SSF. Customer and finance records should not be shared outside authorised finance operations without an appropriate basis.

6. Storage, retention & security

SSF Lead and SSF Collection store an authentication token and MPIN in the device’s app storage to support subsequent access. Logging out clears the local authentication database. Selected images and generated receipts may also create device files; clearing an authentication session does not establish deletion of every device file or server record.

SSF Consumer stores its authentication token and selected language locally. Logging out removes the local login token; it does not delete SSF’s customer, loan, complaint, contact-change or notification records, revoke every server-side device registration, or remove receipts and QR files saved or shared outside the app. You can delete downloaded files using your device’s file controls and disable notifications in device settings. Ask SSF to remove app access or associated notification registration.

Retention depends on the record’s purpose, account or loan status, applicable recordkeeping obligations, and any unresolved transaction, audit or dispute. Customer, identity, vehicle, loan and payment records may remain necessary after staff access is removed or a loan closes. Coordinates attached to an operational record are part of that record. Contact SSF for the retention and deletion treatment of a particular record; this policy does not specify a universal retention period.

HTTPS protects data transmission to the configured backend. Authentication and app permission checks restrict functionality. This policy does not claim end-to-end encryption or encryption of all device or server storage. Protect the staff device and credentials, and log out when access is no longer required. No system can guarantee absolute security.

7. Access, correction & deletion requests

To request access, correction, account removal, data deletion or information about consent withdrawal, email [email protected] with the subject “SSF privacy request”. State the app, your relationship to the record, the request and a contact method. SSF may need to verify identity and authority before acting on a request. Do not include passwords, one-time codes or complete identity documents in the initial email.

Authorised staff can also contact their SSF administrator about removal of staff access. Account removal and deletion of customer or finance records are separate matters. Applicable recordkeeping requirements, an outstanding loan or a dispute may limit deletion. Ask SSF which records can be deleted and which must be retained.

The apps covered here do not provide an in-app account-deletion workflow. Uninstalling an app or logging out does not delete backend records or cancel a loan obligation. See account & data requests for contact instructions.

8. Website information

This website has no sign-in, enquiry form, payment processing, advertising scripts or analytics scripts. Fonts and brand images are served with the site. It does not set application cookies or use browser storage. Hosting infrastructure processes technical connection information, including IP addresses and request metadata, to deliver the website. Email and telephone links open the relevant services on your device; their providers’ practices apply.

9. Intended users

SSF Lead and SSF Collection are intended for authorised finance personnel. SSF Consumer is intended for existing SSF customers accessing their finance records. These apps are not intended for children to use independently and do not provide public registration for new loan applications. If you believe a child’s information has been entered incorrectly or without appropriate authority, contact SSF for review.

10. Updates & privacy contact

This policy was updated on 12 October 2026. Changes to app features or information handling may require an updated policy. The latest version is published on this page.

For privacy questions, complaints or requests, contact:

SRI SATYA FINANCE CORPORATION
D No. 44-15-24, Bypass Road, near DMH School, Annapurnampeta,
Rajamahendravaram – 533101, Andhra Pradesh, India

Email: [email protected]
Phone: +91 88866 73333