Privacy Policy

This Privacy Policy page is a placeholder pending legal review and business approval. It is not a final legal policy.

What Indian buyers typically ask about privacy

• What customer and shipment-related information is processed
• Who can access operational records inside the platform
• How long records may be retained for operations and accounting
• How access for former staff should be controlled
• What to request before go-live for counsel review

Use Contact to request the approved privacy materials when available, and keep product evaluation focused on operational fit through demos and documented commercial terms.

Important: this page remains a placeholder pending legal review and business approval. Nothing here should be treated as a final, binding legal policy. Indian buyers and partners should request the approved policy documents during commercial discussion and before go-live.

In the Indian courier software market, privacy, terms, refund, and data handling expectations matter because customer teams process shipment details, contact information, franchise commercial data, and operational exceptions every day. Clear written policies help owners, finance teams, and compliance reviewers understand responsibilities before software commitment.

Anjova’s public website currently separates marketing and product explanation from final legal instruments. That separation is intentional. Product pages explain operational value. Legal pages must eventually publish counsel-reviewed language that matches actual contracting, hosting, support, and data-handling practices.

Indian courier networks often ask practical questions during evaluation: who can access booking data, how long records are retained for operational and accounting needs, what happens if a project is paused, how refunds or credits are handled for setup or subscription fees, and what customer responsibilities exist for user access control.

Until approved policies are published, use Contact and Book Demo channels to request clarification on commercial terms, implementation scope, support expectations, and data handling practices relevant to your deployment model.

Buyers should also align internal stakeholders early. Operations cares about access and workflow continuity. Finance cares about invoices, refunds, and outstanding commercial clarity. IT or vendor management cares about data location assumptions, access control, and incident communication. Legal or advisory reviewers care about contract language and policy completeness.

For franchise and multi-branch networks in India, policy clarity becomes more important because multiple legal entities or commercial parties may share a platform. Permission boundaries inside the product and contractual boundaries outside the product should be discussed together during onboarding planning.

Anjova encourages Indian customers to document open questions in writing before signing. Policy placeholders are not a substitute for negotiated commercial terms, statements of work, or counsel-reviewed agreements.

As approved content becomes available, these pages will be updated to replace educational guidance with final policy text. Until then, treat every statement on this page as informational context for evaluation, not as enforceable legal wording.

Courier software deployments in India also involve practical records that finance and customer support rely on: AWB histories, status events, wallet movements, credit decisions, and outstanding notes. Future approved data and privacy policies should address how such operational records are handled in line with business process and applicable law as determined by counsel.

Customers should maintain their own access hygiene: strong credentials, role-based user assignment, timely deactivation of former staff, and careful handling of exported reports. Platform controls and customer operating discipline must work together.

If your organisation requires vendor security questionnaires, data processing summaries, or contractual annexes, raise those requirements during commercial discussion so Anjova can respond with accurate, approved materials rather than informal assumptions.

This expanded explanation exists so Indian market evaluation teams have enough reading material to align internal expectations while final legal pages are prepared. For product depth, continue with Product, Features, Pricing, Solutions, Integrations, and FAQ pages.

Always prefer written commercial confirmation over verbal assumptions about refunds, implementation scope, integration effort, support coverage, and data handling. Clear documentation reduces dispute risk for both courier networks and software vendors.

Anjova’s goal is operational honesty: publish final policies only after review, keep placeholders clearly labelled, and give buyers enough India-market context to ask the right diligence questions now.

Additional diligence note 1 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 2 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 3 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 4 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 5 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 6 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 7 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.

Additional diligence note 8 for Indian courier buyers: request counsel-reviewed policy documents, confirm commercial terms in writing, and validate operational data-handling expectations against your franchise, branch, finance, and support workflows before go-live. Placeholder pages help orientation only; approved contracts and policies govern the relationship once issued.