Privacy Policy
1. Introduction
Kramank ("Kramank", "we", "us", or "our") operates MODAL, a library and coaching management software platform designed to help libraries and coaching institutions manage their day-to-day activities.
This Privacy Policy explains how MODAL collects, uses, stores, accesses, shares, retains, and deletes personal information through its available services.
The Policy applies to library owners, administrators, authorized staff, students whose records are entered into MODAL, and other individuals whose personal information is processed through the platform.
MODAL currently provides owner and staff mobile applications. The web administration panel, website-based management features, RFID attendance hardware, and other future services may be introduced separately. Their data practices will be disclosed or this Policy will be updated as applicable before those features are introduced.
We aim to handle personal information responsibly and in accordance with applicable laws of India.
2. Information We Collect
The information collected depends on the features used and the records entered by the library or its authorized users.
2.1 Library Owner and Library Information
We may collect and process:
- Owner's name and mobile number.
- Library or institution name and address.
- Owner account credentials and account identifiers.
- Owner profile photograph and basic personal details.
- Signature and payment QR code.
- Aadhaar information and other personal documents, where provided.
- Subscription plan, subscription status, and related payment records.
- Library configuration information, such as total seats, shifts, timings, and other management settings.
2.2 Staff Information
Information entered or maintained by a library may include:
- Staff name, contact details, and role or designation.
- Login credentials and account information.
- Profile photograph.
- Signature and payment QR code.
- Up to two personal documents, such as Aadhaar or other identity documents, including front and back images where applicable.
- Permissions, attendance records, and other operational information maintained by the library.
2.3 Student and Guardian Information
Authorized library owners and staff may enter and maintain student records, including:
- Student name, photograph, contact number, and email address.
- Gender, date of birth, caste information, and address.
- Guardian name and contact details.
- Aadhaar information and other identity documents.
- Enrollment number, course or class, and examination preparation details.
- Assigned shift, timing, seat, and locker information.
- Fee plans, discounts, amounts due, payments recorded by the library, and receipt information.
- Up to two personal documents, including front and back images where applicable.
The Aadhaar, caste, date-of-birth, guardian, and other optional fields described above are not required to complete student admission in the current workflow.
The information actually entered into MODAL depends on the library's requirements and the fields used by its authorized staff.
2.4 Fees and Financial Records
MODAL may process library-maintained financial records such as:
- Fee plans and monthly fees.
- Discounts, outstanding dues, and amounts received.
- Payment dates and payment method names.
- Receipt numbers and remarks.
- Staff names associated with fee entries.
- Records required for receipts, fee reminders, reports, and transaction history.
MODAL does not directly collect student fees through a student payment flow at present. The payment method recorded against a student's fee entry identifies the method recorded by the library.
2.5 Attendance and RFID Information
MODAL may process:
- Attendance dates and manually recorded attendance status.
- Check-in and check-out timestamps.
- Multiple visits during a day.
- Calculated study duration and related attendance summaries.
- Staff attendance and working-hour records.
- Seat, shift, and timing information associated with attendance.
- RFID card identifiers and device-related attendance information when RFID features are enabled.
RFID attendance hardware is currently under development. Any additional data collected through that hardware will be disclosed as the feature is introduced.
2.6 Photographs, Documents, and Files
Depending on the available feature, users may capture or select photographs from their device, including student and staff profile photographs.
MODAL may also process uploaded identity documents, support-request screenshots, and receipt PDFs.
Uploaded files are stored on the secure private server used by MODAL.
2.7 Technical and Device Information
We may collect or process technical information such as:
- IP address and login timestamps.
- Device UUID and device identification information.
- Android device model, operating-system version, and app version.
- API request logs and diagnostic information.
- Device location information, where permission is granted.
- Device or application information required for authentication, security, troubleshooting, and device management.
The exact contents and retention periods of technical logs depend on the implementation and must be verified before publication.
3. How We Collect Information
Information may be collected:
- Directly from library owners during account registration.
- From owners and authorized staff when they create or update records.
- Through the mobile applications and connected backend services.
- From attendance events and device integrations when enabled.
- Through device permissions granted by the user.
- Through support interactions, diagnostic logs, and technical operations.
- Through subscription payment providers when a subscription payment is initiated.
At present, MODAL does not provide a student application through which students independently manage or edit their records. Student information is managed by the library's owner and authorized staff through the available MODAL application.
4. Purposes for Which Information Is Used
We use information for the purposes described below.
4.1 Account and Library Management
To create and maintain accounts, identify authorized users, configure libraries, manage staff permissions, and provide the management features requested by the library.
4.2 Student and Staff Management
To maintain admission records, profile information, identity details supplied by the library, seat allocations, shifts, timings, and other operational records.
4.3 Fee Management
To generate receipts, calculate dues, maintain fee histories, support reminders, and provide income and fee-related reports.
4.4 Attendance and Operations
To record manual attendance, calculate study duration, produce attendance reports, support occupancy-related features, and maintain staff attendance and working-hour records.
4.5 Identification and Emergency Reference
Libraries may use the optional personal details and documents entered into MODAL for identification and emergency-reference purposes. MODAL does not represent that it independently verifies every identity document uploaded by a library.
4.6 Security and Device Management
To authenticate users, identify devices, maintain login records, investigate suspicious activity, prevent misuse, troubleshoot technical problems, and manage device-related functionality.
4.7 Institution Location
MODAL may request device location permission when the application starts and when it is opened. This location is used for the institution's location-related information and is not used to verify student attendance.
The precision of location information may depend on the permission granted by the user. Location access is not required for the application to operate according to the current implementation.
4.8 Support and Service Improvement
To investigate reported problems, maintain service reliability, diagnose errors, respond to support requests, and improve the operation and usability of MODAL.
5. Location and Device Permissions
MODAL may request device location access to support institution-location functionality.
The application may receive approximate or precise location information depending on the permission granted and the device's operating system.
Users may deny location permission. Denying this permission does not prevent the application from operating.
Camera and photo-library permissions may be requested to capture or select profile photographs and other supported attachments.
We will not describe a permission as optional or required beyond what the actual application behavior supports.
6. Access to Personal Information
6.1 Library Owners and Authorized Staff
A library owner may access records associated with their own library, subject to the features available in MODAL.
Authorized staff may access records according to the permissions assigned by the owner. Owners can configure staff permissions according to their operational requirements.
Other libraries are not authorized to access a library's records through the intended business-level access controls.
6.2 Kramank Technical and Support Access
Authorized Kramank technical or support personnel may access relevant records when reasonably necessary for troubleshooting, technical maintenance, backup operations, security investigation, or support.
Such access is intended to be limited to authorized personnel and legitimate operational purposes.
7. File Access and Storage
Photographs, identity documents, and receipts are stored on the secure private server used by MODAL.
File links may be used to retrieve these resources through authenticated API access. Access to files is intended to be restricted to authorized users and appropriate permissions.
8. Payments and Subscription Information
Kramank offers paid MODAL subscriptions. Subscription payments may be made through available online payment methods, including UPI, cards, and wallets, or manually in cash where supported.
Online payment processing may involve a payment gateway or other payment service provider.
MODAL does not store customer's card or bank details. Payment providers may separately process the information needed to complete a transaction under their own terms and privacy practices.
MODAL also stores library-maintained student fee records for management purposes. These records are distinct from subscription payments made to Kramank.
9. WhatsApp, SMS, and Notifications
MODAL provides communication-related functionality involving WhatsApp, SMS, and notifications.
In MODAL, WhatsApp and SMS actions use the relevant applications available on the user's device and their official application interfaces to open a communication or message.
When a user initiates a communication, the selected messaging application or service may process the recipient's contact information, message content, attachments, and related technical information under its own terms and privacy policy.
MODAL's current communication flow should not be interpreted as a statement that Kramank independently sends all WhatsApp or SMS messages through its own external messaging API.
10. Third-Party Services and Data Sharing
We may use service providers necessary to operate MODAL, including hosting, database, infrastructure, and payment-processing services.
Our current system operates on a secure private server, utilizing a centralized API and a dedicated database.
MODAL does not share customer records with external development contractors and does not use personal data for advertising or sell it to data brokers.
Information may also be disclosed where reasonably necessary to investigate security incidents, protect the service, comply with applicable law, or respond to a lawful request from an authorized authority.
11. Marketing and Other Uses
At present, MODAL personal data is not used for advertising, marketing profiles, or data-broker sales.
Kramank may introduce other products or services under the broader Kramank Group in the future. Any future use of personal data for additional marketing purposes will be reviewed against applicable legal requirements, appropriate notices, consent requirements where applicable, and user choices.
This Policy does not grant unrestricted permission to use student, guardian, staff, or owner records for unrelated marketing.
If our practices materially change, we will update this Policy and provide any additional notice or obtain any consent required by applicable law.
12. Children's Personal Data
Libraries using MODAL may maintain records relating to students under 18 years of age.
The library's owner and authorized staff are responsible for managing admissions and following the institution's applicable procedures for informing parents or guardians and obtaining permissions where required.
Kramank recognizes that children's personal data requires particular care. The fact that a library manages the admission process does not remove any legal obligations that may apply to Kramank or another party processing the data.
13. Aadhaar and Other Identity Documents
Libraries may enter Aadhaar information and upload other identity documents where they consider these details necessary for their records.
These fields are optional in the current admission workflow. A student admission can be completed without filling them in.
MODAL does not claim that it independently authenticates or verifies the identity documents uploaded by users.
The necessity, access, use, retention, and deletion of identity information must be handled carefully and in accordance with applicable law.
14. Data Retention
For active accounts, information is currently retained for ongoing service use. This retention as long-term or indefinite while the account remains active.
When a subscription expires, account information may be soft-deleted or made unavailable through the active service while being preserved to allow the library to resume operations if it renews later.
The current implementation also allows library owners to export supported records in PDF or Excel formats before closing or discontinuing an account, where those export functions are available.
Soft deletion does not necessarily mean that the information has been permanently erased from databases, uploaded files, backups, or other copies.
We will retain information only for periods supported by the applicable service purpose and legal requirements, and will establish appropriate deletion procedures where information is no longer required.
15. Access, Correction, Copy, and Deletion Requests
Individuals who want to access, correct, or obtain a copy of their information should ordinarily contact the library owner or authorized staff responsible for the relevant records.
A library owner or authorized staff member may be able to correct or delete records within the permissions available in MODAL.
Where a request concerns information processed directly by Kramank, or where a person cannot reasonably resolve a privacy concern through the library, the person may contact Kramank through the contact details provided below.
We may need to verify the identity of the requester and their authority to act for another person before disclosing or changing personal information.
Requests will be handled according to applicable law, including any applicable requirements concerning access, correction, erasure, consent withdrawal, and grievance redressal.
16. Account Deletion and Subscription Closure
Subscription expiry and account deletion are different processes.
Subscription expiry may result in access restrictions or soft deletion so that the library's data can be restored if it renews later.
A request to permanently delete an account or personal data must be assessed separately. Where deletion is required, it should cover the relevant associated information, subject to any lawful retention requirements.
Users may contact Kramank to initiate a privacy or deletion request.
17. Data Security
The current system utilizes HTTPS/TLS to protect data transmitted between the application and the server, along with password hashing, user authentication, and restricted access to server backups.
We aim to protect information through appropriate technical and organizational measures suited to the data processed and the services provided.
No electronic service can guarantee absolute security.
18. Security Incidents and Data Breaches
If we identify a suspected or confirmed security incident involving personal data, we will assess the incident, restrict unauthorized access where appropriate, investigate relevant logs, secure affected systems, and take reasonable steps to contain and address the incident.
Where required by applicable law, we will notify affected individuals and relevant authorities within the applicable time limits.
19. International Processing
MODAL currently serves customers in India.
The exact physical hosting location and the regions used by all infrastructure and service providers have not yet been confirmed. As a result, this Policy does not make an unconditional claim that all data is stored exclusively in India.
20. Privacy Complaints and Contact
For privacy questions, data-related requests, or complaints, please contact:
- Representative: Anurag Tiwari
- Support Contact: +91 95808 15767 (Call, WhatsApp or SMS)
- Primary Website: https://modal.kramank.in
- Secondary Website: https://modalapp.in
- Platform: Kramank Solutions
- Product / Service: MODAL — Library & Coaching Management Software
- Office Address: Rajendra Nagar, Orai, 285001, India
At present, privacy requests and complaints are handled by the representative. A dedicated privacy email and formal support contact may be introduced in the future.
We will handle requests in accordance with the applicable legal requirements and the procedures established for the service.
21. Changes to This Policy
Kramank may update this Privacy Policy to reflect changes in the service, data collection practices, technology, business operations, or applicable law.
Authorized Kramank personnel may publish updates. The revised Policy will identify its effective or last-updated date.
Users should periodically review this page to stay informed about how their information is handled.
22. Additional Information
This Policy describes the practices currently reported by Kramank and is intended to explain how MODAL handles personal information.
It does not replace any additional notices, consent processes, data-processing agreements, or contractual arrangements that may be required for particular customers, features, or legal obligations.