Mobile App Privacy Policy

JPRAXC INFYNEX PRIVATE LIMITED (CIN: U62011UP2026PTC252552) publishes this notice for the apps below. It supplements our Privacy Policy, which explains website forms, sales, licensing, ERP deployments, service providers and privacy requests.

Apps covered

• JPX School ERP: the school office app for administrators and authorised ERP users. It provides app screens for the records, forms, fee collection, approvals, settings and reports the account’s ERP role allows, office ConnectX conversations and verification of school documents. It connects to the school’s ERP; the current dedicated app does not open its school tasks in an embedded browser.
• JPX Parent: access to the student information, documents and conversations a school releases to an authorised parent or guardian.
• JPX Staff: staff records and the school workflows permitted for that account, including assigned teaching and communication work.
• JPX Mail: access to one or more business mailboxes, messages, attachments, contacts, drafts and delivery status.
• JPX Partner: partner sign-in, customer and order work sent to the configured JPRAXC Sales service.
• Legacy JPX School ERP / Universal: a mobile workspace that opens the school’s ERP through an embedded browser, with its own browser storage and device-unlock behaviour.

These apps do not all use the same sign-in, storage or notification mechanism. Available functions depend on the app version, platform, connected service and account permissions. Features depend on the installed build and server rollout; a source update does not establish that every device has that build. The legacy Universal app is not one of the five current dedicated apps.

Who handles your records

A school controls the student and staff records it makes available through its ERP and portals, including account access, publication, corrections and retention. Parent, Staff and School ERP connect to the school service identified during setup. The school’s hosting and support arrangements determine which authorised service providers may also process those records.

The organisation administering a business mailbox controls its mailbox account and employment-related access. The mail service processes messages and related records to provide email. JPRAXC handles partner, sales and licensing information needed for its own service relationship. It is therefore not accurate to say that JPRAXC can never receive any information from these apps.

Information used

School discovery and sign-in

Parent, Staff and School ERP use the Organisation ID with JPRAXC’s school-verification service to find the correct school connection. The service receives the Organisation ID, app type and normal client and network information. The verified app then connects to the school’s ERP for the authorised account.

The current Parent app asks for the child’s admission number, date of birth and the father’s mobile number recorded by the school. Older Parent sign-in deployments may use an Aadhaar-related matching field. These identifiers are not secret passwords or proof of guardian authority, and this is not represented as UIDAI authentication. The school must verify guardian linkage and the lawful necessity of any identifier. Ask the school for a non-Aadhaar access arrangement; if access is blocked, contact JPRAXC through direct reporting. Do not send Aadhaar through support email. Staff use school-issued account credentials.

Mail sign-in sends the email address and password to the selected mail service, with mail.jpraxc.com as the default service address. Partner sign-in connects to its configured Sales service. School ERP signs in to the school’s ERP with the ERP Login ID and password, the ERP’s security question and, where the account has one, the second sign-in step; the app does not store the password. Sessions and account references let the apps make later authorised requests.

Records shown or entered

Parent and Staff may receive the profile, photograph, date of birth, address, guardian contacts and other demographic or identity fields the school releases, including masked identity numbers where provided. Depending on account permissions, records can also include attendance, marks, diary entries, notices, fees and receipts, transport, staff details, leave, payroll and salary slips.

ConnectX uses the conversations, participants, text and selected attachments sent through the school workspace. The current Parent and Staff attachment flow accepts supported image formats and PDFs. Staff actions such as attendance, diary updates, marks or class communications are sent to the school service when the relevant permission is enabled.

Business Email processes mailbox identities, message senders and recipients, content, attachments, drafts, folder and message state, the mail service’s contact directory and delivery information. Sending an email shares its content with the recipients and delivery systems involved.

Partner requests may include an organisation name, customer contact name, email, telephone, billing address, GSTIN and requested product details. The order flow asks the partner to confirm customer authority. Those records are sent to the configured Sales service for the requested business process.

School ERP reads and changes the school registers, records and conversations the account’s ERP role allows. These can include admission and student information, guardian contacts, health records, staff and payroll information, attendance, marks, fees and receipts, transport and other enabled school tasks. Forms, photographs, selected documents and imports are sent to the school when submitted. Scanning an issued document reads its barcode or QR code on the phone and sends the decoded reference to the school for verification; the scanner image is not uploaded. Manual reference entry is also available.

School ERP ConnectX carries text, selected pictures and supported documents, voice notes, conversation participants and message status. A voice note is recorded after you start recording and ends when you stop; it is prepared as an attachment and sent when you choose to send it. A broadcast goes to the selected families or staff in their private conversations after confirmation. The school’s support conversation shares information you send with the authorised JPRAXC support team.

Technical and connection data

The apps and connected services use session tokens, app roles and versions, generated device or installation references where implemented, request timing, errors and connection state to authenticate access, refresh records and diagnose problems. A server handling a request also receives network information such as its source IP address and client headers.

Background notifications

FCM-enabled Parent, Staff, School ERP, Business Email and Partner builds can register a Firebase Cloud Messaging device token with the relevant authenticated school, mailbox or Sales account. Google processes registration identifiers and notification/data payloads for delivery; servers use account/device bindings to route alerts. Older builds may use polling or connection-based refresh instead. Notification titles or previews can appear on the lock screen; use device privacy controls on shared phones. Firebase Analytics or Crashlytics use is not implied by FCM. Permission, connection quality, Android power controls, provider availability and server workers affect delivery: instant or closed-app delivery is not guaranteed.

Disable alerts through app/device notification settings. Sign-out or permission changes do not erase school, mailbox or order records or recall already delivered alerts. On a lost or offline phone, request account/session revocation from the administrator rather than relying only on local settings.

In JPX School ERP, the control is More › Push notifications. Push delivery uses a generic school-update alert; the app loads school details after authorised access. This does not imply advertising analytics or crash-reporting collection. Declining notifications leaves your ERP account and unrelated tasks available.

What can stay on the device

The apps retain information needed to reopen an account, remember settings and display recent records. Storage differs by app:

• Parent and Staff: saved school and linked-account details, session tokens and app-lock state use secure storage. Appearance preferences and cached portal snapshots also use local application preferences. Those snapshots may include profile and school records released to the account.
• Business Email: account addresses, display names, server addresses and tokens use secure account storage. Server and theme preferences, the last address and cached account information also use local preferences. Files opened or attached may have local copies.
• Partner: the app keeps the session and local lock state needed for access to the configured Sales service.
• JPX School ERP: the verified school connection and remembered ERP sign-in, plus local settings such as appearance, App PIN, biometric preferences, sign-out preference and the name and school displayed on the lock page. The ERP password is not stored by the app. The remembered sign-in uses the phone’s secure account storage; ordinary display preferences use app settings. Selected attachments, voice recordings, downloaded documents and exports can have temporary app copies. Files saved or shared outside the app can remain there after account removal.
• Legacy School ERP / Universal: the embedded browser can keep cookies and web storage for the school workspace, in addition to the saved school selection.

Secure storage and ordinary application preferences are different mechanisms; this notice does not describe every cached record as encrypted or hardware-protected. Documents opened from Parent or Staff may be saved to temporary app storage before another application opens them. Downloads, exports or files you deliberately save or share may remain outside the app’s own storage.

Permissions and local app lock

• Network access: connects to the school, mail, Sales or JPRAXC service used by the app.
• Files and photographs: selecting an attachment or profile photo uses the relevant device picker. Taking a new profile photo can open the device’s camera flow. The selected file or photo is then available to the app and, when submitted, the connected service. Current Parent, Staff and School ERP Android builds do not request broad media-library access.
• Notifications — all five dedicated apps where enabled: requested as needed by the platform to display alerts; declining stops display but does not cancel the account. Token registration and lock-screen controls are explained above.
• Camera and microphone — enabled School ERP, Parent and Staff Live Classes: used when you choose to publish audio/video. Other authorised participants receive it; a permitted recording can capture it. Refusal prevents that participation mode, not permission to use unrelated data.
• Camera — School ERP document verification: used only while the scanner is open, to read a document’s barcode or QR code; the picture is not uploaded, and a reference can be typed instead.
• Microphone — ConnectX voice notes: used only while you record a voice note, which is sent to the conversation you choose.
• Location — relevant Staff/transport workflows only: used for the selected attendance or transport task when supported and enabled; check the feature notice before granting access. It is not a blanket requirement for reading notices or email.
• Screen capture — School ERP Live Classes on Android: Share screen asks for the phone’s confirmation before the screen is shared with authorised class participants. Other apps, notifications or records visible on that screen can also be exposed. Use Stop sharing or Leave class to stop. Screen capture is not used for ordinary ERP browsing.
• Nearby-device audio access, where requested: routes Live Classes audio through a connected Bluetooth headset. It is not a request to read contacts or unrelated personal files.
• Biometric or device unlock: where enabled, the app asks the operating system to authenticate you. The app receives the authentication result, not your fingerprint image or face template.

JPX School ERP, Parent and Staff require a four-digit App PIN after first sign-in and offer optional supported-device fingerprint or face unlock. In School ERP, More › App security opens its settings page; App PIN › Change opens a popup to enter and confirm the new PIN. Cancelling or a failed save keeps the previous PIN. The page also controls Fingerprint or face unlock, Open fingerprint automatically and Ask before signing out. Business Email and Partner also provide local PIN or biometric options. The legacy School ERP / Universal workspace has its own device-unlock behaviour.

A local PIN or biometric check controls access on that device. It does not change the school, mailbox or Sales account permissions and is not a substitute for protecting the device itself. Declining an optional permission can prevent that particular action without granting the app broader access to your device.

Connections and recipients

Information goes to the service needed for the action: the school’s ERP for school work; JPRAXC for school verification, relevant account services and support messages you send; the configured mail service and chosen recipients for email; and the JPRAXC business service for Partner activity. Hosting and maintenance providers may process records under the arrangement for that service. Google processes registration information and alert payloads needed for enabled push notifications.

Enabled SMS, WhatsApp or payment workflows can also involve their selected providers. The main policy describes provider categories and configured integrations. Choosing an external browser, document viewer, payment checkout or sharing target makes the relevant information available to that service under its own practices.

ConnectX access follows the participants and the school’s permissions. A class-teacher conversation and an office conversation can have different authorised readers. Do not assume that a message is visible to every member of staff or that it can only be read on the phone that sent it.

Live Classes, where purchased and enabled

The school determines class access, teacher/guardian roles and recording authority. Participant identity, room membership, connection metadata and audio/video are processed to run the class; other authorised participants can see or hear shared content. Screen sharing can expose other windows, so share only what is intended. The interface must notify participants when recording is active. Transport protection is not a promise of end-to-end encryption.

The normal administrator download window is designed to end 24 hours after the actual class end. Download expiry, media deletion, metadata, backups, deletion retries, legal holds and school-downloaded copies are distinct; see the recording retention notice and the school’s activation schedule. Schools that have not enabled the add-on do not receive live-class participation through these apps.

Children’s records

Parent access is intended for an authorised parent or guardian. School and staff accounts are administered by the institution. The school is responsible for the authority, notices and permissions required to collect and release a child’s information. A guardian seeking a correction, access change or deletion should contact the school first; JPRAXC can assist within its role in providing the service.

Signing out, local removal and retention

JPX School ERP: Sign out locks the remembered account behind its App PIN; it does not remove the remembered sign-in. More › Remove from this phone removes that sign-in and its App PIN and attempts to end the phone’s school access. If the school is unreachable, local removal still takes effect and school-side access follows its normal expiry or administrator revocation. The school’s ERP records are not deleted. Forgot App PIN? requires ERP sign-in again before setting a new PIN.

Parent and Staff: the header’s Sign out locks the remembered account. Remove this account from the phone removes the selected account and its related cache and attempts to revoke that phone’s access; other linked accounts can remain. Change school clears the school binding and linked sessions. These actions do not guarantee that files saved or shared outside the app have been erased.

Business Email and Partner: sign-out or account removal changes local access; it does not by itself delete the mailbox, sent messages, orders or organisation records held on the server.

Legacy School ERP / Universal: its change-school flow clears saved school details and the embedded browser’s cookies and web storage. Files saved outside that browser storage may remain. This is separate from the current dedicated JPX School ERP app.

Device settings let you clear app data or uninstall the app. Files already saved or shared outside its private storage may require separate removal. If a phone is lost or remains offline, ask the account administrator to review or revoke access as well as securing the device.

Server records, audits and backups follow the organisation’s rules, service agreement and applicable legal requirements. There is no universal retention period or app button that deletes every related server record. To request account or data deletion, contact the responsible school, mailbox administrator or JPRAXC support as appropriate. We may need to verify identity and explain records that must be retained.

Request account or data deletion

• Parent/Staff: ask the school to remove guardian/staff access and assess the related records. School retention duties may prevent deletion of attendance, fees or statutory records. For a problem with JPRAXC processing or reaching the school, contact us directly.
• JPX School ERP: ERP accounts are issued and managed by the school. Ask its administrator to remove ERP account access and assess related records. Remove from this phone removes local access; it is not a request to delete school records, audits or backups. You may also use the direct privacy request form or JPRAXC support below.
• Business Email: ask the domain/mailbox administrator about mailbox closure and export. A recipient’s received copy is not deleted when the sender closes an account.
• Partner: request account closure from JPRAXC support; open orders, earned payouts, tax records and dispute evidence are assessed separately.

The direct privacy request form is available without signing in or a prior ticket. Include the app name and a minimal account reference, not passwords or identity documents. We verify authority before changing records and explain retained categories. Uninstalling is not an account-deletion request. Available in-app controls and the applicable store listing should be checked for the installed release.

Security

The apps use authenticated sessions, platform storage and local access controls appropriate to their respective implementations. Online school, mail and Sales connections use the configured service endpoints; network and hosting protections also depend on the deployment. Keep the app and device current, review linked accounts, and protect files opened in other applications.

Changes

The date above identifies this revision. App versions and connected services can change; material changes to the practices described here will be reflected in an updated notice. This notice does not replace the organisation’s own privacy notice or limit rights available under applicable law.

Governing law and jurisdiction

Subject to applicable law, any dispute, claim or legal proceeding arising out of or in connection with the website, products, services or agreements of JPRAXC INFYNEX PRIVATE LIMITED shall be subject to the exclusive jurisdiction of the competent courts in Kushinagar, Uttar Pradesh, India.

This clause does not restrict any non-waivable right to seek relief before a consumer commission, regulator or other forum whose jurisdiction is prescribed by applicable law. See Governing law and disputes in the Terms of Service.

Contact

For information held by JPRAXC, account-removal requests or privacy concerns, email support@jpraxc.com with the subject “App privacy request”. Include the app name and enough account or organisation information to locate the issue. For school records or an employer-managed mailbox, that administrator normally determines the request; you may still contact JPRAXC directly without first obtaining a support decision.

JPRAXC INFYNEX PRIVATE LIMITED
Registered office:
C/O Jay Prakash Chaurasia
Bherahritola, Dudhi
Bansgaon, Padrauna, Kushinagar
Uttar Pradesh PIN - 274302, India
Corporate / Business office:
Ward No 12, Dudahi
Kushinagar, Uttar Pradesh
PIN - 274302, India

Step-by-step instructions: JPX School ERP app guides and Mobile app terms.

Support: +91 9792908836.