Platione Privacy Policy

1. Scope and responsibility

Platione Solutions Pvt Ltd operates the Platione marketplace and business services. This review draft describes accounts, public profiles, customer workspaces, CRM, communications, business transactions, digital-presence and support processing. PlatiHeal patient, clinical and research processing has a separate notice. Common infrastructure or a common account does not establish permission to combine those purposes.

We determine purposes for platform operation, security, account administration, billing and support. A customer may determine purposes for workforce, CRM or other records processed on its instructions. Actual activities, law and agreements determine each party’s responsibility. Customers must make their own relevant notices and instructions available; this policy does not settle every controller/processor relationship.

2. Data and sources

Data can include identity and contact details, organization and role memberships, public profiles, imported contacts, enquiries, quotations, orders, invoices, payment references, stock/accounting records, tasks, notes, communications and attachments. Authorized device features may involve contact, call-related, location or notification information. We should collect only what the selected service and lawful purpose require.

Information may come from you, your organization, transaction partners, enabled integrations or permitted public sources. Business contact details can still be personal data. Public availability or a CRM import does not establish unrestricted reuse, accuracy, consent or a right to disclose private information.

3. Purposes and sharing

Processing can support authentication, organization membership, marketplace discovery, requested transactions, customer workflows, delivery of requested communications, billing, fraud/security controls and support. Advertising, optional marketing, enrichment, workforce monitoring and materially different uses require separate assessment, notices and any required consent.

Authorized organization members and transaction counterparts receive the information needed for their role and transaction. Contracted hosting, communication, authentication, payment, analytics and other providers may process data for enabled services, subject to the applicable arrangements. We may respond to binding legal requirements and handle a business transfer with appropriate safeguards and notice. This is not permission to sell private workspace data or expose it indiscriminately.

4. Shared identity and confidential relationships

Shared marketplace profile records and organization-specific relationships are different layers. Accurate public or lawfully shareable identity fields may support matching and duplicate correction; private interactions, communications, notes, prices, pipeline, transactions and campaign information must remain within their authorized purpose and audience.

Neither first creation of a contact nor a shared account establishes unlimited ownership, publication rights or access to another organization’s information. A cross-product membership does not authorize healthcare-record access or health-data marketing. Report incorrect merges, disclosure or access rather than copying more data to work around the problem.

5. Optional analytics, cookies and device access

Cookies and local storage support authentication, security and saved preferences. Enabled usage/analytics tools can receive account identifiers, device/browser context, page/navigation and event information. Before adoption, review the actual SDKs, payloads, vendors and consent controls; do not put passwords, message bodies, contact lists, clinical information or payment secrets into analytics events.

Optional advertising and marketing need any required permission and a usable withdrawal mechanism. Device permission authorizes the specific device capability, not every downstream reuse. Customers enabling employee location, call-related or communication features must give the required notices, establish lawful authority and limit collection and access. Review device permissions and notification previews in system settings.

6. AI, research and integrations

AI and public-source research services may process prompts, documents and retrieved evidence for the requested function. Do not assume output is correct or that private customer data is automatically eligible for training, enrichment, sale or another customer’s benefit. Any private-data model processing needs an approved purpose, provider arrangement, authority and safeguards.

Third-party integrations receive the permissions and data necessary for their enabled function. Review and revoke connections where supported, and contact support where additional action is needed. Public company research is different from human-participant health research; this notice does not authorize clinical-to-research reuse, participant enrollment or research consent.

7. Security, hosting and incident handling

Access controls, transport protection and operational safeguards must match the deployment and data. No system is perfectly secure. This draft does not assert end-to-end encryption, a certified standard, universal GDPR/HIPAA compliance, India-only processing or a proven recovery time. Check actual regions, vendors, backups, permissions and incident procedures before publication.

We must assess and respond to suspected breaches and make notifications required by applicable law. Report a concern to the security contact without forwarding unnecessary sensitive files. Protect devices and credentials and promptly remove obsolete organization memberships.

8. Retention, exports and requests

Different account, transaction, tax, message, customer, security and backup records have different retention needs. Retain data for an identified purpose or legal duty, then use approved deletion or de-identification procedures. Do not promise a universal deletion period or immediate removal from every backup without an implemented schedule and process.

Contact privacy@platione.com for applicable access, correction, withdrawal, closure, export or deletion requests. We may proportionately verify identity and authority, including the organization’s role. Request handling must respect lawful retention, disputes and other people’s rights and the periods required by law. A closure request does not automatically cancel a transaction or erase another party’s lawful records.

9. Children, changes and complaints

The business account service is for adults legally capable of contracting. Do not create a child’s business account or upload a child’s sensitive information into general CRM tools as an alternative to an authorized healthcare/guardian workflow.

This draft has no approved effective date. Confirm the actual processing inventory, vendor/transfer list, retention and consent controls before adoption. Publish material changes and obtain additional consent where required; policy wording alone cannot authorize a new incompatible purpose. Use the company privacy/grievance contact below and retain the right to approach a competent authority.

Company and grievance contact

Platione Solutions Pvt Ltd
Office 4, Survey No 19/2 Sakhare Estate, Hinjawadi Wakad Rd, Hinjwadi, Pune, MH, India – 411057.

Privacy and grievance contact: Adv. Mrs. Usha Ghotankar.
Privacy: privacy@platione.com
Grievances: grievance@platione.com
Legal: legal@platione.com
Support: support@platione.com
Security: security@platione.com
Phone: +91-7083-888-888.

These are the existing Platione company contacts. Do not send passwords, OTPs or unnecessary sensitive documents by ordinary email.