Public paid beta

Privacy Policy

How Metricanic handles information for the public paid beta website, application panel, tracking infrastructure, billing flows, integrations, and related services.

Effective date
May 1, 2026
Last updated
May 1, 2026

Scope and Contact

BushWell Inc. operates Metricanic as a public paid beta for business users. Metricanic is offered as a public paid beta. Beta features may change, have limited support or SLA commitments, and may be unavailable or incomplete. No production-grade SLA applies unless separately agreed in writing. Some integrations or advanced features may require configuration, approval, or plan eligibility.

Privacy requests may be sent to [email protected]. Support and legal notices may be sent to [email protected].

Roles

Metricanic acts as a controller or business for information it uses to operate its own service, including account creation, authentication, tenant administration, billing, support, product security, abuse prevention, legal compliance, and website or panel analytics where enabled.

Metricanic generally acts as a processor or service provider for customer campaign, tracking, attribution, event, routing, reporting, postback, and integration data that customers submit to, configure in, or collect through Metricanic.

For visitor tracking data, the customer is usually the controller or business. The customer is responsible for its own lawful basis, privacy notices, cookie notices, consent, opt-outs, and ad platform obligations.

Metricanic provides tools for tracking, attribution, routing, reporting, postbacks, and integrations. Metricanic does not determine customer campaign purposes, audiences, offers, legal bases, consent requirements, or whether a visitor may lawfully be tracked.

Information Metricanic Collects

  • Account and authentication data, such as email address, account identifiers, login/session metadata, and security metadata.
  • Billing and subscription metadata, including billing identifiers, checkout metadata, invoice metadata, billing status, usage, and plan limit data.
  • Support, diagnostic, audit, request, security, abuse-prevention, and account communication data.
  • Website and panel analytics and advertising measurement where implemented, subject to applicable consent requirements.

Customer Tracking and Campaign Data

When customers deploy Metricanic tracking, campaign links, scripts, cookies, redirects, postbacks, direct tracking, APIs, imports, exports, Google Ads conversion uploads, or related integrations, Metricanic may process visitor, click, visit, event, conversion, cost, revenue, and campaign data on behalf of that customer.

  • Customer-configured identifiers and source-specific campaign identifiers.
  • Visitor and request metadata, which may include network, device, browser, approximate location, referrer, and security signals.
  • Campaign, attribution, event, conversion, cost, revenue, value, and reporting data.

Customer Responsibilities

Customers, not Metricanic, determine their campaigns, audiences, offers, landing pages, traffic sources, redirects, postbacks, integrations, tracking domains, cookies and scripts deployment, whether and how visitors are tracked, legal bases, consent flows, opt-outs, privacy notices, and ad platform compliance.

Customers are solely responsible for their use of Metricanic, including lawful collection and use of Customer Data, required privacy notices, cookie notices, consents, opt-outs, Do Not Sell or Share handling where applicable, campaign-specific GDPR, ePrivacy, PECR, CPRA, PIPEDA, Quebec Law 25, traffic source, affiliate network, publisher, advertiser, app store, and Google Ads obligations, lander, offer, funnel, and content legality, and the accuracy and legality of data submitted to Metricanic.

Metricanic does not provide legal, privacy, advertising compliance, platform compliance, tax, or regulatory advice. Customers must obtain their own professional advice.

  • Provide required privacy notices and cookie notices.
  • Obtain and record required consent for cookies, tracking, analytics, advertising, profiling, attribution, and similar technologies.
  • Honor opt-outs, withdrawal of consent, Do Not Sell or Share requests, and similar privacy choices where applicable.
  • Comply with applicable traffic source, ad platform, affiliate network, publisher, advertiser, app store, and partner rules.
  • Avoid sending regulated sensitive data to Metricanic unless Metricanic separately approves that use case in writing.

Integrations

If a customer connects Google Ads, Metricanic may process account authorization, advertising account identifiers, and conversion upload data when the integration is enabled. Customers are responsible for ensuring conversion uploads and consent handling comply with Google Ads policies and applicable law.

If a customer connects an OpenAI or ChatGPT MCP integration, the connection may expose limited workspace data needed for the customer-enabled integration. The MCP connection is designed to limit access to customer-enabled workspace data and exclude sensitive operational data, secrets, and write access.

How Metricanic Uses Information

  • Provide, operate, maintain, and improve the public paid beta service.
  • Authenticate users, protect accounts, process billing, administer plans, and enforce subscription limits.
  • Provide tracking, attribution, reporting, routing, postbacks, and enabled integrations.
  • Monitor reliability, debug issues, prevent abuse, and respond to support requests.
  • Comply with legal, tax, accounting, security, and recordkeeping obligations.

Sharing and Disclosure

  • Service providers and subprocessors used to operate the service.
  • Payment processors, identity providers, infrastructure providers, analytics providers, and integration providers where applicable.
  • Customers, when processing customer-controlled tracking data.
  • Authorities or third parties when required by law or needed to protect rights, safety, security, or service integrity.
  • Successors in connection with a merger, acquisition, financing, reorganization, or sale of assets.

Retention, Deletion, and Security

Metricanic retains information as long as needed to provide the service, administer subscriptions, maintain security, provide support, comply with legal obligations, resolve disputes, enforce agreements, and operate the public paid beta.

Deletion is request-based unless a specific product workflow states otherwise. Deletion may be limited by legal retention, security, fraud-prevention, audit, billing, tax, accounting, backup, log, provider, or customer-instruction requirements.

Metricanic uses technical and organizational measures intended to protect information, including encryption in transit, access controls, operational safeguards, and managed provider security controls. No service can guarantee absolute security.

Privacy Rights and Requests

Requests may include access, export, deletion, correction, opt-out, Do Not Sell or Share, and integration revocation. Send requests to [email protected] or [email protected], or use the Privacy Choices and Data Deletion pages.

If a request concerns customer-controlled visitor tracking data, Metricanic may route the request to the relevant customer or act on that customer's instruction because the customer is usually the controller or business for that data.