Privacy Policy

This Privacy Policy explains how OmniCommerce Solutions Pte Ltd ("we", "us") collects, uses, shares, and protects personal data when you use OmniCommerce (the "Service"). We are based in Singapore. Our handling of personal data is governed by Singapore’s Personal Data Protection Act 2012 (PDPA) and other applicable law.

We may collect account details (name and email), authentication identifiers, usage data, marketplace integration metadata, product catalog data, order data, fulfillment data, billing-related records, and technical logs required to operate, secure, and improve the Service.

When merchants connect marketplace or commerce integrations, this can include customer personal data contained in orders—such as names, emails, phone numbers, shipping addresses, order identifiers, order totals, and line items—but only where needed for merchant-requested order, fulfillment, inventory, support, reporting, or synchronization workflows.

When you choose to connect an email provider, we also access mailbox data as described in Section 7 (Google / Gmail) and Section 9 (Microsoft Outlook).

We use data to provide and improve user-facing product features, authenticate users, process marketplace operations, import and synchronize products and orders, support fulfillment workflows, power optional assistant/email features you enable, send service notifications, and monitor platform reliability and security.

We do not use merchant customer personal data for advertising, resale, or unrelated profiling. Use of Google user data is further limited as described in Sections 7 and 8. Use of Microsoft Outlook / Microsoft Graph data is described in Section 9.

We share information only with trusted service providers and infrastructure needed to operate the Service (for example hosting, storage, email delivery, observability, and AI model providers used solely to power features you request), with marketplaces and integrations you connect, or when required by law.

We do not sell personal data. We do not transfer or sell Google or Microsoft mailbox user data to data brokers, advertisers, or information resellers. Transfers of Google user data are limited as described in Sections 7 and 8. Transfers of Microsoft Outlook data are limited as described in Section 9.

We retain personal data for as long as needed to provide the Service, meet legal obligations, resolve disputes, and enforce agreements. Marketplace protected customer fields are minimized by default, redacted when a supported marketplace sends a valid erasure request, and periodically redacted from retained Shopify order records after 18 months unless a longer period is legally required.

When the original purpose is no longer served and retention is no longer necessary for a legal or business purpose, we delete the personal data or remove the means of associating it with an individual.

Retention and deletion practices for Google user data (including Gmail connection tokens and related data) are described in Section 7. Practices for Microsoft Outlook connections are described in Section 9.

We apply reasonable technical and organizational safeguards to protect data, including encryption in transit (HTTPS/TLS), access controls scoped to authenticated users and their organizations, encrypted storage of OAuth refresh and access tokens for connected email accounts, and least-privilege operational practices. However, no system is completely secure.

Additional protections specific to Google user data are described in Section 7. Protections for Microsoft Outlook connections are described in Section 9.

This section applies when you connect a Google account to OmniCommerce (for example via Account → Email → Connect Gmail). Connecting Google is optional. We access Google user data only after you grant permission through Google's OAuth consent screen, and only for the scopes you approve.

Data access (what we access). Depending on the scopes granted, we may access: your Google account email address and basic identity needed to label the connection; Gmail mailbox data such as message and thread identifiers, headers (for example From, To, Cc, Subject, Date), labels, and message bodies and attachments when you or your authorized workflows read, search, or open mail; and Gmail draft and send capabilities so the Service can create drafts or send messages from your connected mailbox when you request those actions. We currently request mail-related scopes only (including gmail.readonly and gmail.compose, plus openid/email for account identity). We do not request Google Calendar scopes at this time. We may process both raw mailbox content and limited derived or aggregated signals needed to operate features (for example search results, thread summaries produced for you, or delivery status for a send you initiated).

Data use (how we use it). We use Google user data solely to provide or improve user-facing features of the Service that you enable, including: listing, searching, and reading mail in your connected mailbox; drafting and sending email on your behalf when you request it; optional assistant/AI features that help you understand or act on your own mailbox content; and reliable connection maintenance (token refresh, webhook/push notifications for new mail where configured, and troubleshooting). We do not use Google user data for targeted advertising, credit eligibility or lending decisions, or any purpose unrelated to providing or improving these features.

Data transfer (who we share it with). Google user data is not sold. We may process it using subprocessors that help us deliver the Service—such as cloud hosting and storage providers, application infrastructure, and AI model API providers—only as needed to perform the user-facing features described above (for example generating a draft reply you requested). We do not transfer Google user data to third parties for their independent advertising, data-brokerage, or model-training purposes. We may disclose data if required by law or to protect the rights, safety, and security of users and the Service.

Data protection (how we secure it). OAuth access and refresh tokens for Google connections are encrypted at rest. Access to connected mailboxes is limited to the signed-in user who connected the account (connections are user-owned, not shared organization-wide by default) and to backend systems required to fulfill your requests. We use industry-standard transport security and operational access controls. We encourage you to disconnect Google access when it is no longer needed.

Data retention and deletion. We retain Google OAuth tokens and connection metadata for as long as the connection remains active so we can continue providing the connected-email features. Message content retrieved from Gmail is processed to fulfill your requests and is not used to build advertising profiles. Operational logs may retain limited technical metadata for security and reliability for a limited period. You can disconnect Gmail at any time in Account → Email, which deletes the stored connection and associated OAuth tokens for that account. You may also revoke OmniCommerce's access in your Google Account security settings (Third-party access). For additional deletion or privacy requests regarding Google user data, contact sales@omnicommerce.sg. We will respond in accordance with applicable law and our technical ability to identify and delete retained data.

Our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular: (a) we use Google user data only to provide or improve user-facing features that are prominent in the Service; (b) we do not transfer Google user data to third parties except as necessary to provide or improve those features, for security, or as required by law; (c) we do not use or transfer Google user data for serving advertisements, including retargeting, personalized, or interest-based advertising; (d) we do not allow humans to read Google user data unless you give us affirmative consent for specific messages, it is necessary for security or legal compliance, or the data has been aggregated and anonymized; and (e) we do not sell Google user data.

AI and machine learning. When optional assistant or AI features process Gmail content, that processing is only to provide personalized, user-facing features for the requesting user (for example summarizing a thread or drafting a reply). We do not use raw or derived Google Workspace / Gmail user data to develop, improve, or train generalized or non-personalized AI/ML models. We do not transfer Google Workspace / Gmail user data to third-party AI services for those services to train their models; any AI provider processing is limited to generating the feature output you requested, subject to our agreements with those providers.

The use of raw or derived user data received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.

This section applies when you connect a Microsoft account or Microsoft 365 / Outlook mailbox to OmniCommerce (for example via Account → Email → Connect Outlook). Connecting Microsoft is optional. We access Microsoft user data only after you grant permission through Microsoft's OAuth consent experience, and only for the permissions (scopes) you approve.

Data access (what we access). Depending on the permissions granted, we may access: your Microsoft account profile and primary email address (for example via openid, profile, email, and User.Read) needed to identify and label the connection; Outlook / Microsoft 365 mailbox data via Microsoft Graph such as message identifiers, conversation identifiers, headers (for example From, To, Cc, Subject, Date), folders, and message bodies and attachments when you or your authorized workflows read, search, or open mail (Mail.Read and, where granted, Mail.ReadWrite); and send capabilities so the Service can create drafts or send messages from your connected mailbox when you request those actions (Mail.Send and related write permissions). We use offline_access so we can refresh tokens and keep the connection working without repeated sign-in. We currently request mail-related Graph permissions only. We do not request Microsoft Calendar permissions (for example Calendars.ReadWrite) at this time. We may process both raw mailbox content and limited derived or aggregated signals needed to operate features (for example search results, thread summaries produced for you, or delivery status for a send you initiated).

Data use (how we use it). We use Microsoft Outlook / Graph user data solely to provide or improve user-facing features of the Service that you enable, including: listing, searching, and reading mail in your connected mailbox; drafting and sending email on your behalf when you request it; optional assistant/AI features that help you understand or act on your own mailbox content; and reliable connection maintenance (token refresh, change notifications/webhooks for new mail where configured, and troubleshooting). We do not use Microsoft mailbox data for targeted advertising, credit eligibility or lending decisions, or any purpose unrelated to providing or improving these features.

Data transfer (who we share it with). Microsoft user data accessed through Graph is not sold. We may process it using subprocessors that help us deliver the Service—such as cloud hosting and storage providers, application infrastructure, and AI model API providers—only as needed to perform the user-facing features described above (for example generating a draft reply you requested). We do not transfer Microsoft mailbox data to third parties for their independent advertising, data-brokerage, or model-training purposes. We may disclose data if required by law or to protect the rights, safety, and security of users and the Service. Microsoft’s processing of data in its own services remains subject to Microsoft’s terms and privacy statements.

Data protection (how we secure it). OAuth access and refresh tokens for Microsoft Outlook connections are encrypted at rest. Access to connected mailboxes is limited to the signed-in user who connected the account (connections are user-owned, not shared organization-wide by default) and to backend systems required to fulfill your requests. We use industry-standard transport security and operational access controls. We encourage you to disconnect Microsoft access when it is no longer needed.

Data retention and deletion. We retain Microsoft OAuth tokens and connection metadata for as long as the connection remains active so we can continue providing the connected-email features. Message content retrieved from Outlook is processed to fulfill your requests and is not used to build advertising profiles. Operational logs may retain limited technical metadata for security and reliability for a limited period. You can disconnect Outlook at any time in Account → Email, which deletes the stored connection and associated OAuth tokens for that account. You may also revoke OmniCommerce's access in your Microsoft account or Microsoft 365 admin consent settings. For additional deletion or privacy requests regarding Microsoft user data, contact sales@omnicommerce.sg. We will respond in accordance with applicable law and our technical ability to identify and delete retained data.

AI and machine learning. When optional assistant or AI features process Outlook mailbox content, that processing is only to provide personalized, user-facing features for the requesting user (for example summarizing a thread or drafting a reply). We do not use raw or derived Microsoft mailbox data to develop, improve, or train generalized or non-personalized AI/ML models. We do not transfer Microsoft mailbox data to third-party AI services for those services to train their models; any AI provider processing is limited to generating the feature output you requested, subject to our agreements with those providers.

Our use of Microsoft APIs and data obtained through them is intended to comply with applicable Microsoft API Terms of Use, the Microsoft Services Agreement, and related Microsoft developer policies for the permissions we request.

When you connect WhatsApp Business through Meta, we may process business and WhatsApp Business Account identifiers and names, business phone numbers and phone number identifiers, catalog identifiers and product data, access tokens and connection metadata. When you enable messaging, inbox, or assistant features, we may also process customer names and phone numbers, message content, attachments or media references, conversation history, message identifiers, timestamps, delivery statuses, and messaging preferences needed for those features.

We use this data to provide the WhatsApp features you enable, including connecting your business account, synchronizing your catalog, receiving and sending messages, supporting customer conversations, and providing requested assistant features. We do not sell this data or use customer conversations for unrelated advertising or profiling.

Data is shared with Meta and service providers only as needed to operate the enabled features, or as required by law. Access is limited to authorized users in your organization and backend systems needed to fulfill your requests. Connection tokens are encrypted at rest and data is transmitted over HTTPS/TLS.

We retain this data only as needed to provide the Service and meet the retention purposes in Section 5. You can request disconnection and deletion of WhatsApp or Meta data held by OmniCommerce by contacting sales@omnicommerce.sg; the Data Deletion Instructions page explains the request process, our response target, and retention exceptions. Revoking access through Meta stops authorized access but does not itself delete data already held by us. Data held independently by Meta, WhatsApp, merchants, or message recipients remains subject to their own policies.

Depending on applicable law, you may have rights to access, correct, delete, or restrict processing of your personal data. For Google-connected accounts, you can disconnect the integration in the Service or revoke access in your Google Account. For Microsoft Outlook–connected accounts, you can disconnect the integration in the Service or revoke access in your Microsoft account / organization admin settings. To exercise privacy rights, contact sales@omnicommerce.sg.

Our providers may process data in Singapore, the United States and other countries where they operate. Overseas processing and remote access are subject to the PDPA’s Transfer Limitation Obligation; using a Singapore-based service does not mean that all processing stays in Singapore.

Before transferring personal data overseas, our policy is to assess the recipient, purpose, locations and safeguards, and ensure protection comparable to the PDPA through legally enforceable obligations, such as appropriate contractual terms, or another basis permitted by Singapore law. Transfers must be limited to the data needed for the service, with reasonable security and access restrictions. A provider’s location alone does not establish adequate protection. Contact us for information about safeguards applicable to your data.

Public product search, product details and comparison do not require an OmniCommerce account or an OAuth connection. They return public merchant catalog information, recorded prices and inventory, variants and stored product enrichment. These tools do not expose private seller costs, customer orders or payment records, and do not provide checkout.

We process submitted search criteria and product identifiers to answer requests, together with limited network and operational metadata needed to deliver, rate-limit and secure the service. We do not intentionally collect sensitive personal data through these tools. Reading the public tools does not invoke an AI model; stored enrichment may have been prepared through separate merchant-enabled features. The agent host, such as Meta/Muse, receives tool results and handles its own user conversations under its own policies.

Infrastructure providers include Amazon Web Services for application hosting, database storage and runtime logs, Cloudflare for edge delivery and security, and Sentry for scrubbed error diagnostics. Application hosting is in Singapore; Sentry’s configured ingestion region is the United States, and edge delivery may process request metadata in other locations. Runtime application logs are configured for seven-day retention. Separate security and audit records may be retained for 24 months, and incident records for three years, where needed for their purpose. Legal holds may require longer retention. Deletion and anonymisation follow Section 5 and our Data Deletion Instructions; deleting data held by OmniCommerce does not delete copies independently held by the agent host or other parties.

Requests for non-public personal data are referred to our privacy contact for review of the requester’s identity, authority, applicable law and scope. We require a valid legal basis for disclosure, limit it to what is necessary, and seek clarification or appropriate legal advice where a request is unclear, excessive or disputed. Informal requests do not by themselves authorize disclosure.

We document the decision and apply any lawful preservation requirement. We comply with disclosure obligations under applicable Singapore law and other laws that apply to us. We do not notify individuals of a disclosure where the law prohibits notification; any notice in other cases is subject to applicable law and the circumstances. Privacy and legal requests should be sent to sales@omnicommerce.sg.

The OmniCommerce Chrome extension uses your signed-in account and selected workspace to provide assistant chat. Browser tools work on a tab you explicitly share. When you ask the assistant to inspect that tab, the extension can send its hostname, page title, visible text, and descriptions of visible controls to OmniCommerce. If you approve a browser plan, the extension uses the approved actions and any text needed to carry them out. Images and screenshots you attach are uploaded when you send your message. If you start a voice session and grant microphone permission, the service processes microphone audio and may save the conversation transcript.

We use this information to provide the assistant features you request, with service providers such as hosting, storage, and AI providers as described in Section 4. Chat messages, uploaded attachments, and browser tool results can be retained as part of your workspace conversation under Section 5. The extension stores some preferences and related-chat associations in your Chrome profile. Stopping browser access ends tab sharing. To request deletion of data already sent to the service, follow our Data Deletion Instructions or contact sales@omnicommerce.sg.

We may update this policy periodically. Material changes will be reflected by the effective date above. Continued use of the Service after an update constitutes acceptance of the revised policy where permitted by law.

For privacy-related requests, including access, correction, withdrawal of consent or deletion requests, contact our privacy contact at sales@omnicommerce.sg. This includes questions about Google, Microsoft, WhatsApp, Meta and public connector data.