Privacy Policy

01 · SCOPE AND CONTROLLER

Who this policy covers

This policy applies to the Maanchitra Android relay application and its paired Docker-based web dashboard (together, “Maanchitra”), developed by Team-AwSM. Maanchitra is intended only for personnel who have lawful authority to submit and review telecom trace requests.

The organization that deploys the dashboard controls the operational records in that deployment and decides why and how they are processed. That organization is normally the data controller. Team-AwSM acts as the product developer and may not have access to a self-hosted deployment or its records.

This policy does not provide authority to locate a subscriber, access a telecom response or process NCRP information. Users and deploying organizations remain responsible for applicable law, authorization, carrier requirements and internal policy.

02 · DATA WE HANDLE

Information processed by Maanchitra

Important SMS and location limits

• The app does not request Android's SMS inbox permission and does not browse or upload SMS history.
• When a new SMS arrives, the receiver checks whether it matches an active carrier request. Matching acknowledgements or replies are stored and uploaded; unrelated messages are not stored by Maanchitra or sent to the portal.
• The app does not request GPS or Android location permission. Coordinates shown in Maanchitra are information returned by a TSP about the requested subscriber, not the physical location of the relay phone.
• A Super Administrator may use a quiet trace to reduce routine operational log noise. The request remains visible while it is processed and its result remains available to the Super Administrator, but the completed request is omitted from ordinary portal and relay history views. The Super Administrator can delete quiet test traces, including their SMS attempts, replies and map results. Relays purge the deleted requests on sync. A protected compliance audit record is still retained.
• The app does not collect contacts, call logs, microphone, camera, advertising ID or analytics profiles.

03 · ANDROID PERMISSIONS

Why the Android app requests access

04 · PURPOSES

How the information is used

Maanchitra uses the information described above to:

• register, authenticate and monitor an approved relay device;
• assign one request to one available relay, send the selected TSP command and track its result;
• correlate carrier acknowledgements and replies with the correct request;
• parse and display telecom status, cell and location information, request history, recurring trace schedules, blocked-number records and operational reports;
• protect access, enforce user roles, maintain audit history, diagnose failures and prevent duplicate or unauthorized dispatch.

Maanchitra does not use operational data for advertising, consumer profiling, marketing, data brokerage or sale.

05 · DATA SHARING

Who may receive information

Information is transmitted to the organization's configured self-hosted Maanchitra portal and, when an authorized request is sent, to the selected TSP through the mobile carrier's SMS network. Only the information needed to create and reconcile that request is included.

The dashboard uses OpenStreetMap map tiles. The tile provider receives standard web request information and the viewed map region. If an operator intentionally opens an external map link, the coordinates in that link are sent to the selected map provider, such as OpenStreetMap or Google Maps, under that provider's own privacy terms.

The deploying organization may disclose records to its authorized personnel, service providers, regulators or law-enforcement bodies where permitted or required by law. Team-AwSM does not sell Maanchitra operational data and the current Android relay does not include an advertising or analytics SDK.

06 · STORAGE AND SECURITY

How data is protected

The Android app stores its portal configuration and local job state on the device. The relay credential is protected with Android Keystore-backed encryption, Android backup is disabled and production portal connections must use HTTPS. The dashboard stores application data in the deploying organization's Docker volume and uses hashed passwords, role-based access, authenticated sessions, device credentials and audit records.

Deploying organizations must secure the phone, server, backups, domain, TLS termination and administrator access. No system can guarantee absolute security, but Maanchitra is designed to limit access to authorized users and the configured relay.

07 · RETENTION

How long information is kept

There is no single global retention period because each Maanchitra deployment is self-hosted. The deploying organization sets its operational, legal and backup retention schedule. Portal records remain until an authorized administrator clears them, resets operational data or applies the organization's retention process. Security logs and backups may remain for a limited additional period before rotation or deletion.

Local Android job and reply records remain on the relay device until cleared through available app controls, Android app storage is cleared or the app is uninstalled. Data should be retained only as long as needed for authorized operational, security, audit and legal purposes.

08 · CHOICES, ACCESS AND DELETION

Your controls

The Android relay does not offer public consumer accounts. Portal user IDs are provisioned and managed by the deploying organization's administrator. A relay operator can pause or stop processing, disconnect the device, revoke Android permissions, clear the app's storage or uninstall the app.

To request access, correction or deletion of portal account or operational data, contact the administrator or privacy contact for the organization operating the deployment. The organization will delete, anonymize or retain the information according to its legal authority and obligations. Copies in backups may remain until normal backup expiration.

If Team-AwSM operates the deployment directly, use the contact mechanism below and identify the relevant deployment, user ID and request. Do not include passwords, relay keys or sensitive case details in an initial inquiry.

09 · AUTHORIZED USE

Not for children or general consumer use

Maanchitra is not directed to children and is not designed for general consumer use. It is an access-controlled operational system for authorized adult personnel. The product does not knowingly solicit personal information from children.

10 · POLICY CHANGES

Updates to this notice

We may update this policy when Maanchitra's data practices, security controls, legal requirements or product features change. The “Last updated” date at the top identifies the current version. Material operational changes should also be communicated by the deploying organization through its normal user-notification process.

11 · CONTACT

Privacy questions and requests

For data held by another Maanchitra deployment, contact that deploying organization first; Team-AwSM may not possess or be able to retrieve its self-hosted records.