Venari
Find deals

LEGAL & TRUST

Cookie, Analytics & Advertising Consent Policy

Effective Date: September 21, 2026 Last Updated: September 21, 2026

This Cookie, Analytics & Advertising Consent Policy explains how Venari, a product operated by The Viral Marketer, LLC, uses cookies, browser storage, analytics technologies, advertising pixels, server-side conversion measurement, and similar technologies on our public websites and customer-acquisition flows.

It should be read together with our Privacy Policy.

1. Our Approach

We use a privacy-first consent model.

Our rules are:

  • technologies necessary to operate/secure the requested service may operate without optional advertising consent where permitted by law;
  • optional Analytics defaults OFF;
  • optional Advertising & Audience Measurement defaults OFF;
  • advertising tracking is limited to the public marketing/customer-acquisition funnel;
  • advertising tracking does not operate inside private Venari workflows; and
  • declining optional analytics/advertising does not prevent use of Venari.

2. Cookies and Similar Technologies

Cookies are small pieces of data stored by a website or related service on your browser/device.

We may also use:

  • browser/session storage;
  • advertising pixels;
  • conversion tags;
  • server-side conversion APIs;
  • campaign identifiers;
  • browser/device identifiers;
  • analytics scripts; and
  • similar measurement technologies.

Some operate in the browser. Others, such as server-side conversion APIs, may send an event from our server to an advertising/measurement provider.

Consent rules apply according to the purpose of the processing, not merely whether a traditional cookie is used.

3. Consent Categories

A. Strictly Necessary

Always active where genuinely necessary to provide the requested service.

This may support authentication, account security, fraud prevention, temporary signup state, session maintenance, privacy-choice storage, payment/checkout functionality, reliability, and other essential functions.

Strictly Necessary technologies are not used for cross-site behavioral advertising.

B. Analytics

Optional — default OFF until granted.

Analytics may help us understand public-page visits, campaign attribution, signup funnel performance, aggregate website usage, and technical performance.

Analytics is not intended to collect contents of Saved Searches, Acquisition Inbox, private Marketplace analyses, Inventory, VMS results, Deep Analysis, or other authenticated resale-operation activity.

C. Advertising & Audience Measurement

Optional — default OFF until granted.

Potential uses include:

  • Meta Pixel;
  • Meta Conversions API;
  • Google Ads conversion measurement;
  • other comparable advertising services;
  • conversion attribution;
  • campaign optimization;
  • customer-list audiences;
  • Custom Audiences;
  • Lookalike/similar audiences; and
  • measurement of signup, trial, or subscription conversion.

This may involve advertising/campaign identifiers, page/conversion event, browser/device information, IP address where technically transmitted, advertising cookies/identifiers, and normalized or hashed email where the applicable consent exists.

Hashing an email does not make it anonymous.

4. Marketing Email Is Separate

Consent to cookies, Analytics, or Advertising does not subscribe you to promotional email.

Marketing communications are governed by a separate preference.

Necessary account, billing, security, Support, verification, password-reset, privacy-request, and customer-enabled Monitoring communications are separate from promotional marketing.

5. Your Choices

The consent interface should provide clear choices equivalent to:

  • Accept All Optional
  • Reject All Optional
  • Manage Preferences

Preferences should separately display:

  • Strictly Necessary — Always Active
  • Analytics — On / Off
  • Advertising & Audience Measurement — On / Off

Marketing email is controlled separately.

Rejecting optional technologies must be as straightforward as accepting them.

6. Default State

Before you make a choice:

Strictly Necessary = ON
Analytics = OFF
Advertising & Audience Measurement = OFF

Optional advertising/analytics tags must not send ordinary optional tracking data before the applicable consent is granted.

For Google services, applicable consent states should initialize as:

analytics_storage = denied
ad_storage = denied
ad_user_data = denied
ad_personalization = denied

7. Basic Blocking Consent Mode

For initial launch, Venari uses a conservative blocking model.

When Analytics consent is denied:

do not load/send optional Analytics measurement.

When Advertising & Audience Measurement consent is denied:

do not send optional advertising events or customer identifiers.

A future move to advanced cookieless measurement requires a deliberate privacy review and policy update.

8. Where Advertising Tracking May Operate

Optional analytics/advertising may operate in the public customer-acquisition funnel, including:

  • public landing pages;
  • pricing;
  • marketing pages;
  • signup;
  • trial-start flow;
  • checkout/conversion flow; and
  • confirmation of signup/trial/subscription conversion.

Advertising tracking should stop at that boundary.

9. Where Advertising Tracking Must Not Operate

Advertising/audience tracking must not operate inside private product surfaces such as:

  • Acquisition Inbox;
  • Saved Searches;
  • Monitoring results;
  • individual opportunities;
  • Marketplace analysis results;
  • Deep Analysis;
  • Value My Stuff inputs/results after the acquisition funnel;
  • Inventory;
  • resale outcomes;
  • customer economic dashboards;
  • private Support content;
  • Privacy Request content; or
  • Admin.

Advertising providers must not routinely receive Saved Search keywords, products being sourced, seller asking prices, Buy Under values, profit estimates, acquisition prices, sale prices, Inventory holdings, VMS photos, analysis evidence, or Marketplace seller information.

10. Permitted Conversion Events

Subject to Advertising & Audience Measurement consent, the acquisition funnel may send a small allowlist such as:

PAGE_VIEW_PUBLIC
SIGNUP_STARTED
SIGNUP_COMPLETED
TRIAL_STARTED
SUBSCRIPTION_ACTIVATED

Equivalent provider names may be mapped internally.

Not permitted as advertising events:

Saved Search contents
listing/product being sourced
Marketplace listing ID
seller identity
Buy Under
Expected Sale
Quick Sale
profit
ROI
Inventory item
acquisition price
sale price
VMS content
VMS photo
Deep result
opportunity identity

11. Meta Conversions API

Venari may use Meta's server-side Conversions API.

Server-side processing does not bypass consent.

Before sending an optional Meta conversion event, backend logic must verify valid Advertising & Audience Measurement consent.

Conceptually:

Advertising consent = YES
+ approved acquisition event
→ Meta CAPI event may be sent

Advertising consent = NO
→ no optional Meta CAPI event

The browser declining a Pixel must not be circumvented by silently transmitting the same optional event server-side.

12. Customer Lists, Custom Audiences, and Lookalikes

If you separately consent to Advertising & Audience Measurement, we may use limited first-party information such as email to create/update advertising audiences with providers such as Meta.

This may include customer-list audiences, Custom Audiences, exclusion/suppression audiences, Lookalike/similar audiences, and conversion matching.

Where appropriate, information may be normalized and cryptographically hashed before transmission.

Hashing is a security/data-handling measure and does not make the information anonymous.

Access to Venari is not conditioned on consenting to customer-list/Lookalike use.

13. Advertising Audience Data We Will Not Upload

The customer-audience program should initially be limited to identifiers and high-level conversion status needed for advertising.

Do not upload Saved Search contents, search radius, products being sourced, Marketplace listing IDs, specific opportunity history, Inventory, acquisition prices, sale prices, realized profit, ROI, VMS content, uploaded product photos, seller information, or private Support conversations for audience creation.

14. Withdrawal of Consent

You may change optional consent preferences.

When Advertising & Audience Measurement consent is withdrawn:

  • future optional Pixel activity stops;
  • future optional server-side advertising transmissions stop;
  • future customer-list/audience uploads stop; and
  • where supported and reasonably available, we remove or suppress your identifier from customer-list advertising audiences created through that consent.

Withdrawal is prospective and may not erase measurements lawfully processed before withdrawal where retention is independently permitted.

15. Consent Records

We may retain a minimal record showing your choice.

A consent record may include:

  • consent-policy/version identifier;
  • each consent category;
  • granted/denied status;
  • timestamp;
  • method/source;
  • account identifier where signed in; and
  • whether a recognized browser privacy signal was present.

We use these records to honor your choice, demonstrate consent where required, avoid repeatedly asking for the same choice, and process later withdrawal.

16. Global Privacy Control and Browser Signals

Where applicable law requires recognition of Global Privacy Control (GPC) or a comparable legally valid opt-out signal, we will honor it.

For launch architecture, a valid GPC signal should treat the browser/device as opted out of optional advertising sharing/targeted-advertising processing.

GPC does not by itself require disabling ordinary first-party Analytics under this V1 policy unless future law/policy requires it.

17. Browser Controls

Your browser may allow you to block/delete cookies, clear local storage, block third-party tracking, enable privacy signals, or restrict JavaScript.

Using those controls may affect website functionality.

18. Third-Party Provider Controls

Advertising or analytics providers may offer their own privacy controls.

Those controls are separate from Venari's preference system.

Changing an external provider's setting does not necessarily update Venari's stored preference, and changing Venari's preference does not necessarily modify every independent setting held by another company.

19. Canadian Visitors

Our launch architecture treats Analytics and Advertising as optional choices rather than a condition of using Venari.

20. U.S. Visitors

Some U.S. laws provide additional rights concerning targeted advertising, sale, or sharing when applicable thresholds are met.

We intend to maintain a common privacy-preference architecture rather than waiting until every threshold is triggered.

21. Changes to This Policy

We may update this policy as technologies, providers, or legal obligations change.

If we materially expand optional tracking/advertising uses, we will update the policy and obtain new consent where required.

An earlier consent to one materially narrower purpose is not permission for an unrelated expanded advertising use.

22. Contact

The Viral Marketer, LLC Attn: Privacy Officer 1321 Upland Dr, Unit 1713 Houston, Texas 77043 United States

Privacy Officer: Jalal Ibrahimi Email: privacy@theviralmarketer.com

V1.1 IMPLEMENTATION AMENDMENTS

The following rules are authoritative and form part of this policy package.

Personal information must never be placed in analytics URLs

Do not intentionally place email, account ID, customer name, Saved Search, customer-specific listing title, Inventory information, VMS content, or another personal/customer identifier in URL query strings, page-path analytics dimensions, UTM values generated from authenticated activity, or intentionally constructed referrer values.

Analytics/advertising events should use bounded allowlisted event names.

Meta Advanced Matching

Meta automatic/manual Advanced Matching must remain disabled unless:

  1. Advertising & Audience Measurement consent is ON;
  2. the identifier is specifically approved;
  3. the use is described in the current Privacy/Cookie policy; and
  4. server-side and browser-side controls enforce the same consent.

A frontend-disabled Pixel does not authorize server-side identity transmission.

Google enhanced conversions and customer match

The equivalent rule applies to Google Enhanced Conversions, Customer Match, audience uploads, or another identifier-enrichment feature.

No identity enrichment without approved Advertising & Audience Measurement consent.

Global scope

The consent manager must control every marketing tag loaded by first-party code, tag manager, advertising SDK, analytics SDK, server-side conversion service, or later marketing integration.

Adding a tag through a tag manager does not exempt it from this consent policy.