Privacy Policy

Planned integrations & new data uses

A Planned integration or feature listing does not grant access to your accounts or authorize a new use of your data. In-development source is not a released service. Before a new integration or data use is enabled, we will describe the data, purpose and relevant sharing, and obtain any required consent and provider permissions. Connecting one provider does not authorize access to another or supply visitor consent. Existing Google data-use, AI, retention and deletion disclosures continue to apply.

What we collect

Account and contact details you provide; connection credentials and resource identifiers; and account, campaign, creative, catalog, lead and performance information from supported services you explicitly connect through OAuth or another supported credential method.

We collect only what is needed for the workspace features you use. Public browsing can also involve technical information needed to deliver and secure the website; public learning access does not mean that no personal information is processed.

Children, learning access & eligibility

Public guides and learning material are available without the adult eligibility condition that applies to business operations. That access does not waive children’s privacy protections or authorize account registration, API credentials, subscriptions or connected-account actions.

Direct API credentials and live platform changes requested directly through the web interface or a direct API are reserved for people who are at least 18 and satisfy any higher applicable local or provider requirement. This direct-operation policy does not add a separate company-wide 18-year minimum to MCP use; applicable local and provider eligibility, lawful authority and child-data protections still apply. An external AI service’s age check does not establish eligibility for Ovaideu.

Age-eligibility records, server-side eligibility checks, parental-consent workflows and accounts designed for minors are planned and are not represented as live or verified. Until a supported lawful process is available, do not register a minor for an account or submit a minor’s personal information to ordinary account, AI or connected-service workflows. This does not prevent a child or guardian from contacting us to exercise privacy rights or report a safety concern. Required parental authorization and child-safety protections cannot be waived by accepting our Terms.

If you believe a child’s personal information has been provided without the required authorization, contact support@ovaideu.com. We will review the report and take the action required by applicable law, which may include restricting processing and arranging deletion. A lawful retention requirement, where it applies, is assessed separately; an abuse-prevention label does not automatically justify keeping a child’s data.

Planned eligibility information

The planned eligibility process is intended to record the applicable country or region, whether the relevant minimum age is met, the policy and notice version accepted, and the basis and date of an eligibility or parental-authorization assessment. Additional information will be requested only where necessary for the applicable verification process and disclosed before collection.

We do not claim that existing account records contain verified ages or verified parental consent. If an age-assurance or identity provider is introduced, we will describe its role, the information shared and applicable retention before using it. The intended design avoids retaining full identity documents or a precise date of birth where a minimum-age result is sufficient.

How we use it

To provide enabled account selection, reporting, diagnostics, campaign drafts and authorized operations for your assigned resources. An account connection, tool listing or local validation does not prove that a campaign change or conversion was accepted by a provider. Features in development are not represented as released services.

We do not sell your data.

Google & Meta data

Access is limited by the resources assigned to your workspace or client, your role, the current connected credentials and the provider’s actual permissions. Google API Services User Data Policy and Meta Platform Terms continue to apply. See our Google API Disclosure for Google scopes, purpose, storage, sharing, retention, deletion and Limited Use details.

Google features may use Google Ads, GA4, Search Console, Tag Manager, Business Profile, Merchant Center, OAuth profile and Calendar data only for the features you authorize. Calendar calendar.freebusy and calendar.events are requested when you connect or reconnect all Google services, or choose the Calendar booking or Google Meet connection. Connecting an individual Google service requests its own scopes and identity access. These Calendar permissions are used to check availability and create, update, or cancel Ovaideu booking events and Google Meet links. Meta features may use assigned ad account, Page, Instagram, campaign, creative, lead form, comment, catalog and conversion information where the operation is supported and permitted. Advanced Meta private replies, Instant Experience changes and Instagram partnership permissions remain unavailable while their authorization support is unfinished; this is separate from any provider review.

Individual connected-account access

Each person may use only the connected advertising, social, analytics, commerce, website or other provider resources they are individually authorized to access. Both their Ovaideu resource assignment and current upstream provider permission must allow the requested read or change. Connecting an account through one person does not make that person’s credentials available to colleagues.

Working for the same organization, sharing an email domain, paying for its subscription or holding an internal administrator role does not automatically permit access to another person’s connected accounts or data. A legitimately shared business resource requires separate authorization for each person; access to one resource does not grant access to the organization’s other resources.

These rules apply to every enabled dashboard and operation, including social publishing, API, MCP and other connected tools. A viewer may read only authorized information; a write requires the applicable current provider permission. Missing or uncertain provider authority is not permission to make a change.

Meta conversion credentials & removal

Meta conversion-credential and separate-token revocation workflows remain in development until live acceptance. Where a supported connection is enabled, Ovaideu may store a customer-controlled Meta system-user access token separately from the initiating user’s OAuth connection. The token is encrypted at rest, with bindings identifying the initiating user and workspace, current OAuth authorization, Meta business, ad account and pixel or dataset. A saved token or installation-asset match is not proof of conversion-event permission; unverified credentials cannot send conversion events.

Disconnect and account-deletion handling must separately reconcile removal of the applicable conversion token and OAuth access. Provider revocation is confirmed before the corresponding stored credential is removed; local unlinking alone does not prove provider revocation. Changed or shared credentials, uncertain authority or a provider failure may require retry or action through Meta’s controls. Minimal non-secret confirmation records may be retained to finish interrupted removal under the existing security and audit retention rules. Revocation of app access or a conversion token does not delete Meta accounts, business assets, system-user identities or administrators.

Conversion events & recipients

Where an enabled workflow accepts first-party conversion events, it may process an event name and time, purchase or lead value and currency, an order or CRM reference, destination account or dataset, consent state, click identifiers and analytics client or session identifiers. Conversion feedback records support normalized SHA-256 hashes of email, phone and name; the structured matching fields store these hashes rather than raw email or phone. Do not put raw contact or sensitive information in event notes. Hashes and click identifiers can still be personal data.

An authorized upload sends the eligible fields to the destination you select, such as Google Ads or GA4, or Meta’s assigned pixel or dataset, for conversion measurement. Google Data Manager, Meta Conversions API and expanded server-side tracking are in development and are not advertised as completed delivery workflows. A dry run validates local input; it does not transmit a conversion or prove attribution. Recording consent or queuing an event alone does not mean a provider accepted it.

Other platform destinations are not enabled merely because a planning record names them. Microsoft Advertising, Amazon Ads, Pinterest, LinkedIn Ads and ChatGPT Ads integrations remain Planned until their supported workflows and applicable provider access are accepted. Before additional data or a destination is enabled, its purpose, recipient and required permissions will be disclosed.

Customer journeys & analytics

When enabled for an explicitly assigned business and an operator-configured exact HTTPS website, Site Kit journey analytics records consented page paths, finite button intent, active time and filtered campaign/referrer information using random browser identifiers. Analytics requires an explicit analytics choice; regional or advertising defaults, wildcard origins and framed or opaque embeds do not enable this journey capability. Global Privacy Control and withdrawal stop future collection; withdrawal clears this tracker’s browser state, while existing legitimate history remains subject to the applicable retention and deletion process. No form contents, full query strings, IP address or browser fingerprint is collected by this journey path. A configured origin is not proof of website ownership. Provider conversion delivery and complete cross-platform attribution are separate workflows.

If you already use Microsoft Clarity on a configured website, a consented journey can also include the existing Clarity project, browser-user and session identifiers. Ovaideu reads these identifiers passively; this feature does not install Clarity or start a recording. The identifiers can provide a link to Clarity, but do not establish that a recording exists or that the viewer has access. Opening the link uses your own Clarity access. Withdrawal or a changed source assignment stops new capture and suppresses the link; retained identifiers remain subject to the applicable retention and deletion process. Authorized users can erase a selected session or the same browser visitor within its exact source and client. This removes journey observations, recording references and attribution links while preserving separate CRM, booking, payment and financial records. Minimal scoped hash selectors and withdrawn-consent hashes remain to prevent replay and finish an interrupted cleanup. Erasing journey history does not delete data held by Microsoft Clarity or another provider. Erasure also stops further collection under that existing consent grant; a fresh explicit consent choice is separate.

Unified customer-journey reporting across paid, organic, referral and direct traffic and supported ecommerce is Planned. Where available and authorized, it is intended to use consented first-party events and connected GA4 or Microsoft Clarity data. This listing does not mean a Clarity script, store integration or visitor profile has been enabled for your site.

Available data may include page or event activity, referrer and campaign information, device information, session identifiers and conversion outcomes. Collection and linkage are limited by consent, provider access and the supported site or store configuration. We do not promise that an advertising platform reveals each person’s ad views, identity or IP address, or that every visit can be matched. ChatGPT Ads reporting does not give advertisers access to people’s chats or memories. IndexNow submits page-update notifications to search engines; it is not visitor analytics.

Analytics and advertising choices must be respected, including withdrawal and opt-out requests. A report may be aggregated, incomplete or modeled, and attribution definitions and windows can differ between providers. Provider data may not be combined, exported or used for another network’s targeting where its terms prohibit that use.

Consent, data roles & choices

Connecting your provider account authorizes the permitted account operations; it is not consent from your website visitors or customers. Before collecting or uploading their information, your business must provide the relevant notice, have a lawful basis and obtain any consent required for analytics, advertising storage, ad user data or personalization. Server-side processing and hashing do not remove these requirements. Do not submit sensitive or prohibited information.

OIESU remains responsible for its obligations as the service operator. For account administration and security we determine the service purposes; when processing customer events under your documented instructions, the applicable data-processing arrangements and provider terms govern the parties’ roles. Accepting our Terms is not blanket consent to optional tracking or a new data use.

Where consent is withdrawn, stop the affected collection and future uploads and use the available deletion or suppression workflow for records already held. Changing a consent flag does not retroactively erase data a provider already received. You may request access, export, correction, deletion or raise a privacy concern through support@ovaideu.com; applicable objection, restriction and regulator-complaint rights are not waived.

Other advertising platforms

If enabled after acceptance, Microsoft Advertising, Amazon Ads, Pinterest, LinkedIn Ads and ChatGPT Ads use only the connected accounts or advertiser profiles and supported account settings, campaigns, creatives, audiences and reports needed for the requested feature. Provider API eligibility, application review where required, account permissions and operation-specific limits apply separately. Amazon Ads access does not grant Amazon seller or store API access.

Provider-specific data-use limits still apply. Pinterest campaign analytics may be retained only as permitted; other Pinterest API information is not a general-purpose stored customer database. Pinterest information must not be reused to target people on other advertising services. LinkedIn member data is not a source of unrestricted CRM prospects or cross-platform audiences. Connected-provider data is not used to train generalized AI models.

Amazon Ads data, exports and connected applications

Amazon Ads remains a planned integration while Ads API access and the applicable workflows await acceptance. If enabled, it uses only the authorized advertiser profiles and the supported account, campaign, creative, asset and report information needed for your requested feature. Amazon Ads approval does not authorize Amazon seller or store APIs.

The implemented Amazon report and export workflows can return results to the authorized browser, API or MCP application making the request. An external MCP or AI application that processes those results may receive Amazon data. Our separate AI workflow sends the prompt context you choose to your configured AI provider; choosing an AI provider is not permission to transfer restricted Amazon data. Marketing Stream supports delivery through a provider-verified destination, while setup of a new destination remains pending.

Amazon data-use restrictions apply to these paths and to information derived from Amazon data. Before Amazon-data sharing is enabled, the actual recipient, purpose, method and required Amazon permission must be established and disclosed. Workspace membership, user consent, a resource assignment or an encrypted connection does not itself establish that a recipient is permitted by Amazon. We do not represent these sharing paths, recipient approvals or cross-source combinations as accepted merely because the implementation exists.

AI & machine learning

Ovaideu does not use Google user data — or any connected Google Ads, Google Analytics (GA4), Search Console, Tag Manager, Business Profile, Merchant Center, Google Calendar, or Google Workspace data — to train, fine-tune or develop generalized AI or machine-learning models.

When AI features are used, connected Google data is processed only to produce the user-facing recommendation, report, diagnostic, draft, or workflow the user requested for that workspace. Third-party AI providers are not permitted to use Google user data from Ovaideu to train their generalized models.

Storage, sharing & security

Connection credentials are protected and used for the authorized connection, including transmission to the respective provider when required. Workspace and client boundaries, roles, resource assignments and current provider permissions restrict access. Credential values are not public tool results. Disconnect and revocation outcomes depend on the provider and must be checked rather than assumed.

Connected data is shared only as needed for the requested feature with its selected destination and necessary infrastructure, authentication, email, payment, monitoring, support or security service providers, or where legally required. AI requests may include the context you choose to send to your configured AI service only where that transfer is permitted. Provider restrictions and Google Limited Use requirements limit these transfers; selecting an AI service does not override them.

Connected-account contacts

Where you connect a third-party account (advertising, analytics, business profile, social, commerce or website), Ovaideu may store that account's administrator and user contact details — name, email, phone and role — as inert records, to operate your workspace, prevent abuse and provide continuity.

These contacts are never emailed or notified unless you, the workspace owner, explicitly enable notifications and add a specific contact to a send list. A cross-workspace record of connected-account and business identifiers is retained at the operator tier for abuse prevention and is accessible only to Ovaideu operators.

Google user data obtained this way is used only to operate your connected workspace, is never sold, and is never used for advertising — consistent with Google API Services User Data Policy (Limited Use) and Meta Platform Terms.

This describes permitted workspace purposes, not an unrestricted right to import every provider’s contacts. For a Planned advertising integration, contact collection and retention must satisfy that provider’s specific restrictions before the integration is enabled.

Support & administrative access

Designated Ovaideu platform owners and authorized support personnel may access customer account or workspace information only where necessary for an identified support request, account or feature verification, bug diagnosis or repair, authorized implementation work, service security, incident investigation or a legal obligation. This operational access is separate from ordinary customer membership and is not permission to browse customer data for unrelated purposes.

Personnel handling this information must protect its confidentiality, restrict access to the information and duration the task requires, and record administrative entry and actions through the applicable audit workflow. The existing temporary platform-owner entry into an Ovaideu subscriber workspace creates a workspace audit entry and has a limited session duration. More granular support-case grants, resource restrictions and automatic task-completion revocation remain planned until verified; this notice does not represent them as implemented.

Access to connected-provider information or a change to a connected account also requires the applicable provider permission and policy. Routine user-specific support or testing is not blanket authorization to read Google data. Where Google Limited Use applies, human access requires specific affirmative agreement to the data being viewed, a necessary security or legal purpose, or another exception permitted by that policy. General acceptance of these Terms does not provide that specific agreement. An operator may not use support access to make an otherwise unauthorized campaign, social post, budget, ownership or account-access change.

Support processing requires an applicable lawful basis and, where we process customer information on your behalf, the applicable documented instructions and data-processing terms. Where GDPR or UK GDPR applies, the basis may be necessary contract performance, a legal obligation or legitimate interests assessed against the affected person’s rights; required consent is obtained separately. This disclosure does not itself create a lawful basis or remove OIESU’s duties. Other applicable privacy laws and provider restrictions continue to apply.

Diagnostic information and copies must be minimized and kept only as long as necessary for the support task or a specific lawful security, audit, recovery or legal retention purpose, then deleted or returned under the applicable process. You may request access, correction, deletion or raise a support-access concern through support@ovaideu.com. We do not sell information accessed for support, use it for unrelated advertising or train generalized AI models with it. These restrictions also apply to support of white-label tenants.

Retention & abuse prevention

To operate the service and protect it from misuse, Ovaideu retains a limited set of account and business-identity data — your name, business name, email, phone number, website domain and the account identifiers of the providers you connect. We use this to run and support your workspace, to send occasional trial, subscription or promotional messages you can opt out of, and to detect and prevent fraud and abuse — including repeated free-trial abuse (for example, creating, deleting and re-creating accounts to obtain repeat trials), enforcing suspensions or blocks, and protecting the platform and other customers from spam, misuse or unlawful activity.

Where GDPR or UK GDPR applies, necessary security and fraud-prevention processing may rely on legitimate interests under Article 6(1)(f), subject to an assessment of necessity and your rights and freedoms. Continuing to retain data after a valid erasure request requires a specific lawful basis and satisfaction of any applicable erasure exception, such as a legal obligation or the establishment, exercise or defence of legal claims. GDPR Article 17(3) is not a blanket fraud-prevention exception. Other jurisdictions have their own requirements; we assess the applicable conditions and retention period rather than treating these Terms as permission to retain all data.

We keep only the minimal identifiers needed for suppression and abuse prevention, use them for no unrelated purpose, and never sell them. Any Google or Meta user data is handled under the Google API Services User Data Policy (Limited Use) and Meta Platform Terms, and is not used for these purposes beyond what those terms allow.

You can request deletion of your personal data at any time by emailing support@ovaideu.com or messaging us on WhatsApp at +91 98746 25135 (see also the Data Deletion page). On a valid request we delete your personal data unless a specific lawful basis and any applicable erasure conditions permit or require limited retention. A minimal suppression identifier, such as a hashed or truncated email, may be retained solely to enforce a prior block or prevent trial abuse only when necessary, for a documented permitted period and subject to those conditions. Fraud prevention alone is not a universal exception, and hashing does not automatically remove personal-data protections. Accepting our Terms does not waive your rights.

Account deletion & data retention

Workspace owners can request account deletion from Settings. We confirm the request with a one-time code sent to the account email. Once confirmed, the account enters a locked recovery state: you can reactivate it or explicitly confirm permanent deletion. A minimum 90-day recovery window applies to that account workflow, and reactivating resets it. Other users can request deletion of their own personal information through support; workspace ownership does not remove privacy rights.

Confirmation starts provider-access removal and data-purge handling. Revocation may be pending, fail, require a retry or need action in the provider’s settings; local unlinking does not prove that the provider grant or API key was revoked. Check the result and the Data Deletion instructions. A pending provider-removal step can delay the automated account purge; it does not waive or postpone a valid statutory erasure request, which can be made through support.

Fetched provider report caches have a seven-day inactivity retention policy and an active 100-day maximum fetched-age FIFO policy; these limits do not describe every account, event, audit or billing record. Separate legal retention and provider-specific limits may apply, and valid deletion requests are assessed separately. Any retained abuse-prevention identifier remains subject to the lawful-basis, necessity and permitted-period conditions explained above; hashing does not itself make it anonymous.

You can also temporarily pause your account instead of deleting it, and un-pause with access to the records still retained under the applicable retention rules.

Your choices

You can disconnect accounts, request export, pause your account, or request deletion at any time — see the Data Deletion page and the Anti-Fraud & Abuse Prevention Policy.