Privacy Policy

1. Who this covers

OmniCommand ("the Service") is operated by Omni Media Consulting (OPC) Pvt. Ltd., E-2/11, 2nd Floor, Malviya Nagar, New Delhi 110017, India ("we," "us"). This Privacy Policy explains how we collect, use, store, and share information when you use the Service. It covers account holders and workspace members, and people who request access to the Service. Where you connect a client's advertising or analytics account, you are responsible for having the authority to do so; the data from that account is processed on your instructions as described here.

2. What we collect

Account information. Name, email address, workspace and portfolio names, role and membership records, and your settings and preferences. You sign in with Google; we never store passwords.

Plan and usage records. The plan your account holds, its limits, and who assigned it and when. Each time an AI feature is used, we record who used it (name and email address), the feature, the AI model, and its measured cost, and we keep daily totals per person. We use these records to measure your plan's AI allowance, show you how much of it is used, and support and bill your account.

Connected-platform data. When you authorize a connection via OAuth, we receive access tokens (stored encrypted) and retrieve the data the platform's API returns within the access you granted: advertising performance data (campaigns, spend, impressions, clicks, conversions, quality and delivery metrics) from Meta Ads and Google Ads; site and app analytics (sessions, events, channels, geography, landing pages) from Google Analytics 4; and search performance (queries, pages, impressions, clicks) from Google Search Console; and from additional platforms as we add support for them, such as LinkedIn Ads and LinkedIn Lead Gen Forms (when supported). We do not receive your platform passwords. OmniCommand only reads this data and never changes anything in your accounts: we do not create, edit, pause, publish, or delete campaigns, ad sets, ads, budgets, bids, targeting, or creatives. We use this data to provide reporting, analysis, and recommendations to your workspace, and otherwise only as this policy describes. You can disconnect a platform at any time; Section 8 describes what happens to the data already collected.

Google Ads change history. From Google Ads we also receive the account's history of changes (what changed, when, and the previous and new values), including the email address Google reports for the person who made each change. We show it in the change history to your workspace's members, and we never send it to AI models.

Lead uploads. When you import a lead file, we keep each lead's date, campaign, keyword and search term, conversion, status, device, location, and audience fields (age group, gender, income group), with its tracking parameters and ad click identifiers. We do not store names, email addresses, phone numbers, or notes from the file, and we do not keep the file itself: it is read and then discarded. For this data you are the controller and we process it on your behalf, to attribute and analyze your leads: we use these fields, including each lead's status, to report lead volume and quality to your workspace, and otherwise only as this policy describes. Lead data is never enriched from third-party sources and never used for advertising. Lead information from connected platforms is not supported today; if we add it (such as LinkedIn Lead Gen Forms, when supported), we will update this policy before it is offered.

Notes you write. Progress notes, snooze notes, and dismissal notes you add to recommendations and findings. They are visible to everyone in your workspace who can see that recommendation or finding, progress notes show who wrote them, and notes are never sent to AI models.

Requests for access. If you request early access on our website, or try to sign in before your access is approved, we store your name, email address, company, and company website, and any note you add. We use them to review your request and to contact you about access and the Service's launch. We keep a request until you ask us to delete it (see Section 8).

Usage and technical data. Log data (requests, timestamps, IP addresses), device and browser information, and product usage events (which features are used), used for security, debugging, and improving the Service. Application telemetry is collected without request or response bodies.

Support communications. Tickets, replies, and the ticket history you create.

3. How we use it

To provide the Service: retrieving and storing your connected data, computing metrics and findings, generating summaries and recommendations, producing reports, and measuring plan and AI usage. To send Service emails: invitations to join a workspace (including to people who do not yet have an account), one-time codes that confirm a deletion, notices when a workspace or portfolio deletion is requested, scheduled, canceled, or declined, or a portfolio is moved to trash or restored, notices of invitations sent, accepted, or declined, onboarding completion, report publication notices, alerts when a connected source needs reconnecting, notices when AI allowance usage reaches 80% and 100%, replies to your support requests, and, if you requested access, the email telling you it was approved. Source reconnection alerts and AI allowance notices can be turned off in Settings; the others are needed to operate the Service. To secure and improve the Service: monitoring, debugging, abuse prevention, and product analytics. To communicate with you about the Service. We do not sell personal data, and we do not use your data for third-party advertising.

4. AI processing

Some features send data to AI models to generate narrative text (summaries, explanations, recommendation wording). When you use Ask Omni, your question is sent to the AI model with the data needed to answer it. Numerical figures are computed by our own software, not by AI models. Before AI-written text is shown, our software checks every number in it against your data; we keep a log of each check, including the sentence that was checked and any number that failed and why, to measure and improve the check. AI inference is performed in the United States by our AI infrastructure provider(s) under agreements that restrict use of your data to providing the service to us and prohibit training their general-purpose models on it.

5. Where your data lives

Application and database hosting: Microsoft Azure, Central India region. Certain supporting services: Azure, East US. AI inference: United States (Section 4). Email delivery: Microsoft Azure. Website and product analytics: Google Analytics (Section 11). By using the Service you consent to processing in these regions; we will notify you through the Service of material changes.

6. Aggregated and anonymized data

We may derive aggregated, anonymized statistics from Service usage and connected-platform data: statistics that do not identify you, your company, your clients, or any individual and cannot reasonably be re-identified. We use them to build benchmarks, improve our analytics, and publish general insights. Individual-level or identifiable data is never included in benchmarks shown to other customers.

We share data only with: subprocessors that host and operate the Service (cloud hosting, email delivery, AI inference), bound by data-protection agreements; your own workspace, whose members see data according to their role, and reports you publish are visible to the members you publish to; analytics and advertising measurement providers (Google Analytics, and on our website any advertising measurement you allow), as described in Section 11; authorities, where legally required, in which case we will notify you unless prohibited; and a successor entity in a merger or acquisition, under this policy's protections. We never share your data with other customers except as anonymized aggregates (Section 6), and we never sell your data.

8. Retention and deletion

Connected-platform data, findings, and reports are retained while your workspace is active so the Service can show history and trends, and so are a workspace's change history, lead uploads, notes, usage records, and AI number-check log. Deleting a workspace permanently removes its data from the live Service: the deletion cascades through all stored records of that workspace; anonymized identifiers may be retained in tombstone records to keep references consistent, and residual copies may persist in encrypted backups for up to 35 days before being overwritten. Disconnecting a platform stops new collection; already-collected data remains until you delete it or the workspace. A request for access is kept until you ask us to delete it at support@omnicommand.ai, and it is also deleted if you later delete an OmniCommand account under the same email address. Account records needed for legal or accounting obligations may be retained as required by law. Acceptance records (which Terms/Policy version you accepted and when) are retained as evidence of consent.

9. Security

Access tokens are stored encrypted. Access to production systems is restricted and logged. Traffic is encrypted in transit (TLS). Role-based access controls govern what workspace members can see and do, and administrative actions are logged. No system is perfectly secure; we will notify affected users of a personal-data breach as required by applicable law.

10. Your rights

Depending on your jurisdiction (including under India's Digital Personal Data Protection Act and, where applicable, the GDPR for European users), you may have rights to access, correct, export, or delete personal data, and to withdraw consent. Workspace deletion and platform disconnection are available directly in the product, and step-by-step deletion instructions are at omnicommand.ai/legal/data-deletion; for other requests, contact support@omnicommand.ai. If you believe we have not resolved a concern, you may complain to your local data-protection authority.

11. Cookies and similar technologies

Strictly necessary cookies. The Service uses cookies for sign-in sessions and security. These are always on.

Analytics. Our website (omnicommand.ai) and the Service (app.omnicommand.ai) use Google Tag Manager, which loads Google Analytics 4, to measure how our sites are used: pages viewed, how visitors arrive, and which features are used. Google Analytics sets cookies on the omnicommand.ai domain so that a visit to our website and a later sign-in to the Service can be counted as one journey. When you are signed in, we send Google Analytics an identifier derived from your account with a one-way function; it is never your email address or your name. Google Analytics is provided by Google.

Advertising measurement. Our website may also run advertising measurement tags loaded through Google Tag Manager. They run only with the "Ok" choice. The Service (app.omnicommand.ai) never runs advertising tags.

Your choice. A banner on our website and in the Service offers three choices. Ok allows analytics and advertising measurement cookies. Essential only allows analytics cookies but not advertising measurement. Reject turns off both; Google may still receive basic signals without cookies (for example, that a page loaded), which it uses only in aggregate. Until you choose, analytics and advertising measurement are on. Your choice is stored in a cookie on the omnicommand.ai domain, applies to both sites, and lasts 180 days. You can change it at any time from "Cookie settings" on our website or in the Service.

12. Children

The Service is for business use by adults. We do not knowingly collect personal data from anyone under 18.

13. Changes to this policy

Each version carries an identifier and effective date. Material changes will be presented in the Service; where consent is the legal basis, we will seek renewed acknowledgment, and the version you acknowledged is recorded.

14. Contact

Saurav Chhabra (Grievance Officer), Omni Media Consulting (OPC) Pvt. Ltd., E-2/11, 2nd Floor, Malviya Nagar, New Delhi 110017, India, support@omnicommand.ai.

Version PRIV-2026-10-23-v1.5 · Effective October 23, 2026