Review-only public record

Privacy policy review

This public review record separates facts visible in the current Mutjir source from privacy and legal decisions that still need authorized approval.

What the current source supports

These statements describe the repository reviewed on the date above. They are evidence inputs, not a complete disclosure of production behavior.

Mutjir Mobile is a permissioned business workspace. It signs in an existing tenant-admin or employee account and does not currently create those accounts in the mobile app.
Authenticated requests carry account, tenant, branch, session, and resource identifiers to the configured Mutjir API so the server can authorize access and return workspace data.
Depending on role and enabled features, workspace data can include employee or admin profile details, products and inventory, customer and supplier records, sales and other financial operations, tasks, reminders, support messages, and free-form business content.
The current native configuration requests camera access for barcode scanning, disables microphone recording for that camera integration, and blocks legacy Android storage permissions. Final archive and bundle inspection is still required.

A compliant policy must describe actual production processing, not infer it from a client repository.

The approved developer and legal entity, controller or business contact, address, and countries or regions of availability are not confirmed in the release records.
The complete production data inventory, purposes, required or optional fields, sharing, server and infrastructure logs, backups, retention periods, and deletion or anonymization behavior have not been approved.
Production subprocessors, hosting locations, international-transfer safeguards, security statements, and legally supported user rights have not been documented for publication.
The exact iOS archive, Android app bundle, embedded SDK privacy manifests, backend behavior, and store privacy or Data safety answers still need evidence-based review.

This route can become a policy only after an authorized privacy owner replaces the review record with approved, versioned language.

Name the approved legal entity and monitored privacy contact without relying on placeholder company details.
Reconcile every disclosure with the final signed binary, production API, logs, retention schedule, backups, vendors, and data flows.
Explain collection, use, sharing, retention, deletion, consent withdrawal, and applicable rights in language the responsible owner has approved.
Match the App Store privacy answers, Google Play Data safety form, in-app wording, support workflow, and deletion decision before configuring a live URL.

These primary sources explain the review gate. They do not approve Mutjir’s missing product or legal decisions.

The contact page is for questions only. It is not represented as an approved privacy-rights request workflow.