UnifyDesk
In developmentTake a tour

LEGAL · REVIEW DRAFT — NOT EFFECTIVE

Privacy Policy

Prepared 12 October 2026 · Awaiting legal and operational approval

Proposed notice for India Early Access covering the UnifyDesk website, application and customer-authorized integrations. All disclosures require final operational and legal approval.

Provider identity and requests

UnifyDesk is being established as an Indian sole proprietorship. Before publication, insert the exact legal proprietor identity and verifiable legal correspondence address from approved business records.

Privacy and grievance requests: support@unifydesk.in (business-supplied address; inbox receipt and handling must be verified before publication). Verified postal address: [CONFIRM BUSINESS NOTICE ADDRESS]. The legal address remains an unresolved release blocker.

Information handled

We may process names, work email addresses, login and session records, workspace membership, role assignments, subscription details, technical diagnostics and support requests.

Customer-controlled data can include imported contacts and phone numbers, opt-in/opt-out records, message headers (including To/CC/BCC), subjects and bodies, attachments, campaign audience and delivery status, WhatsApp metadata and advertising account data.

Our role and customer responsibility

We operate account, security, website, service and billing workflows for UnifyDesk. Business customers choose whose contact, message and campaign data to submit and which providers to connect; those customers remain responsible for appropriate permissions, required notices and lawful outreach.

Different processing activities may have different legal roles. The roles and instructions for business-customer content must be finalized in the Terms and a customer Data Processing Addendum.

Google, Microsoft, Zoho and Meta integrations

The reviewed backend supports Gmail, Microsoft and Zoho inbox connections and Meta/WhatsApp and advertising integrations. Where authorized, it can synchronize email bodies, recipients, message metadata and attachment references, send messages and maintain provider connection state. Some attachments are streamed from the provider; other objects may use configured media storage.

Default code scopes include Gmail gmail.modify; Microsoft Mail.ReadWrite and Mail.Send; and ZohoMail.messages.ALL. Production scopes and all data transfers need verification.

Google API information must be handled under the Google API Services User Data Policy and applicable Limited Use requirements. UnifyDesk must audit these purposes and flows before submitting Google app verification.

Why information is used

We use information to authenticate users, enable requested workplace features, deliver communications through selected providers, manage contacts and consent, process legitimate billing, operate support, monitor security and investigate misuse.

Storing a contact does not itself establish consent to receive marketing. The backend includes channel-specific preference and suppression logic.

Disclosure to vendors

Depending on which services are enabled, information may be shared with customer-authorized Google, Microsoft, Zoho and Meta integrations; messaging providers; configured hosting/object storage; payment processing; and website analytics.

The exact legal vendor entities, environments, data locations and international transfers are not confirmed; review the Subprocessors inventory before publishing.

Analytics and cookies

The current marketing-site code loads optional Google Analytics only after a visitor explicitly allows analytics. The site stores the visitor's choice locally and provides a Cookie settings control in the footer. Deployed tracking, cookies, geographic access and consent behavior must still be checked before approval.

Security and retention

The reviewed code has role/company permission models, stored encrypted provider credential payloads, authorized attachment access, and deletion-processing services. This is not a certification that each control is deployed or independently audited.

Account and workspace deletion are staged; the code includes a configurable default 30-day delayed purge, but this is not a universal retention promise. Notification records, imports, media, backups, security logs and financial records may have other timelines or exceptions. Some deleted contacts retain protected suppression fingerprints.

Rights, complaints and changes

Requests should be authenticated and may need to be directed to the business customer controlling the recipient information. Publish an actual working email or public request form before approval; do not require a public data subject to create an account solely to ask for deletion.

A final notice must explain rights and grievance procedures under applicable Indian law according to its current phased commencement schedule. Requests may be sent to support@unifydesk.in, subject to mailbox and workflow verification. The final notice needs a real effective date.

Related documents