Omniconvert Commander Insights — Product Privacy Notice

Effective Date: November 10, 2026
Version: 1.2
Data Controller: Omniconvert SRL, 14 Vasile Stroescu Street, Bucharest 021374, Romania
Contact: privacy@omniconvert.com

This notice supplements the main Omniconvert Privacy Policy. It describes how Omniconvert Commander Insights ("Omniconvert Commander", "the Service") specifically processes data from your connected analytics integrations. It also covers the Adstein extension for Google Chrome ("Adstein — Save ads", section 2.10). Adstein is a product of Omniconvert and runs on the same platform as Omniconvert Commander. Where this notice is silent, the main Omniconvert Privacy Policy applies.

1. What Is Omniconvert Commander Insights?

Omniconvert Commander Insights is an AI-powered analytics intelligence product that connects to your existing analytics platforms (e.g., Google Analytics 4, Omniconvert Commander, ad platforms), detects anomalies and patterns across those sources, and generates actionable insights and A/B test hypotheses.

Omniconvert Commander is a business-to-business (B2B) service. We process data on behalf of businesses (agencies, e-commerce brands) and do not directly collect data from their end customers. All data described in this notice belongs to you, the subscribing business.

Adstein is a separate Omniconvert product for brands. Its Chrome extension saves ads to a brand's Inspiration Library in Adstein (lab.agentadstein.com). Adstein data is stored with Omniconvert Commander data on the same infrastructure. Section 2.10 describes the extension. Where a section of this notice names Omniconvert Commander, it applies to Adstein in the same way unless section 2.10 says otherwise.

2. Data We Access from Your Integrations

When you connect an integration to Omniconvert Commander, we access only the data necessary to detect anomalies and generate insights. We never use your data to train our AI models or share it with third parties for their own purposes.

2.1 Google Analytics 4 (GA4)

Data accessed (legal basis: contract performance):

Traffic metrics — sessions, users, pageviews, bounce rate, engagement rate
Conversion data — conversion rates, funnel steps, goal completions, eCommerce transactions
Revenue data — revenue, average order value, transaction volume
Audience data — device type, channel, geographic region (country/region level only), new vs. returning
Product performance — product views, add-to-cart rate, product revenue
Site speed — Core Web Vitals, LCP, CLS, FID

We do NOT access: Individual user identifiers, IP addresses, precise geographic coordinates, or personally identifiable visitor data.

Google API Services Disclosure: Omniconvert Commander uses Google Analytics Data API to access your GA4 property data. Your use of this integration is subject to Google's Terms of Service. Omniconvert Commander's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

We use GA4 data only to operate Omniconvert Commander (anomaly detection, insight generation, correlation analysis).
We do not sell or use GA4 data for advertising.
We do not allow humans to read your GA4 data unless you explicitly request support or it is required for security/legal obligations, and only after obtaining your consent.
You can revoke Omniconvert Commander's access to your GA4 property at any time via your Google Account permissions page.

Retention: GA4 query results used for analysis are not stored raw. Only derived insights (anomaly descriptions, scores, recommendations) are stored in Omniconvert Commander. When you disconnect your GA4 integration, no further data is queried. Historical insights remain available until you delete them.

2.2 Omniconvert Commander

Data accessed (legal basis: contract performance):

Customer segments — RFM segment distribution (Champions, Loyal, At Risk, etc.) — aggregate counts only
Lifetime value — average CLV per segment, CLV trends
Purchase behavior — purchase frequency, recency distributions, repeat purchase rates (aggregated)
Retention metrics — churn indicators, segment migration rates
NPS data — NPS score, promoter/detractor ratios (aggregate)

We do NOT access: Individual customer email addresses, names, order histories, or any data that identifies specific end-customers.

Retention: Aggregated segment metrics used in analysis are not stored raw. Only derived insights are retained. On integration disconnect, no further data is queried.

2.3 CROBenchmark

Data accessed (legal basis: contract performance):

Audit scores — overall CRO score, category scores
Criteria status — pass/fail/partial status per audit criterion
Industry benchmarks — anonymous industry median metrics for comparison

Retention: Audit scores are stored to enable trend analysis and recurring opportunity detection. Data is deleted within 30 days of integration disconnect.

2.4 BrandFeel.ai

Data accessed (legal basis: contract performance):

Sentiment scores — overall sentiment score, sentiment trends
Topic analysis — aggregated review topics and theme distributions
Issue tracking — reported issue types and frequencies

We do NOT access: Individual review text, reviewer names, or any data that identifies specific reviewers.

Retention: Aggregated sentiment metrics are not stored raw. Only derived insights are retained.

2.5 Meta Ads (Ad Intelligence Module)

Own advertising data via Meta Marketing API (legal basis: contract performance):

Ad performance — CTR, CPA, ROAS, impressions, spend, conversions
Creative data — your own ad creative (images, video, copy) for performance correlation
Campaign structure — campaign names, ad set configurations

Competitor ad data via Meta Ad Library — public data (legal basis: legitimate interests):

Public competitor ads — ad creative, messaging, duration active, impression range (publicly disclosed by Meta)

This data is publicly available in Meta's Ad Library and is accessed programmatically to inform your ad intelligence briefs. We only collect ads for competitors you explicitly specify.

2.6 Google Ads (Ad Intelligence Module)

Own advertising data via Google Ads API (legal basis: contract performance):

Ad performance — CTR, CPA, ROAS, quality score, spend, conversions
Creative data — your own ad copy, extensions, responsive search ad assets

Competitor ad data via DataForSEO API — public data (legal basis: legitimate interests):

Public competitor search ads — visible ad copy from public search results

2.7 TikTok Ads (Ad Intelligence Module)

Own advertising data via TikTok Marketing API (legal basis: contract performance):

Ad performance — CTR, CPA, ROAS, video play rate, spend, conversions
Creative data — your own video ad thumbnails and copy

Competitor/trending ad data via TikTok Creative Center — public data (legal basis: legitimate interests):

Public trending ads — top-performing ad patterns publicly featured by TikTok

2.8 Gorgias (Ad Intelligence Module)

Data accessed (legal basis: contract performance):

Support ticket themes — categories of customer issues, topic frequencies (extracted by AI — see §3)
CSAT scores — customer satisfaction scores (aggregate)

PII in Support Tickets: Gorgias tickets may contain customer names, email addresses, and order details. Before any ticket content is processed by our AI or stored, it is automatically anonymized: customer names, email addresses, order numbers, phone numbers, and other direct identifiers are replaced with generic placeholders using pattern detection. Only anonymized, thematic content is processed and stored.

Retention: Anonymized extracted themes are retained for up to 90 days to enable trend analysis. Raw ticket content is never stored by Omniconvert Commander.

2.9 Omniconvert Commander Chrome Extension (Inspiration Library)

The Omniconvert Commander extension for Google Chrome ("Commander — Save ads") saves ads to your store’s Inspiration Library in Omniconvert Commander. It works on the Meta Ad Library, on the Facebook feed, on the Instagram feed, Reels and Stories, on YouTube video, Shorts and search pages and, when Omniconvert Commander turns TikTok saving on, on TikTok. You install it and connect it to one store yourself.

The extension sends nothing to Omniconvert Commander until you connect it. Before you connect it, it can already read ad data on Meta Ad Library, Facebook, Instagram and YouTube pages to place its Save buttons. That data stays in your browser. The extension reads nothing on TikTok until it is connected and Omniconvert Commander has turned TikTok saving on.

Sites and permissions (Chrome asks once, when you install the extension):

Sites — https://api.commander.omniconvert.com (the Omniconvert Commander API), https://www.facebook.com, https://www.instagram.com, https://www.tiktok.com and https://www.youtube.com. The extension also runs on the Meta Ad Library (facebook.com/ads/library) and the TikTok Ad Library (library.tiktok.com/ads). It does not run on Messenger or Instagram Direct. It asks for no other site and has no optional permission.
Chrome permissions — "storage" (to keep the connection in your browser), "activeTab" (to read the address of the tab you open the popup on, and the ads on it when you click the extension icon or press its shortcut) and "scripting" (to add the Save buttons to these sites and read their ad data). The extension does not ask for the "tabs" permission.
Omniconvert Commander pages — only pages on commander.omniconvert.com and nexus.omniconvert.com can send the extension a message. Such a page can ask whether the extension is installed and connected, give it a one-time connect code, and tell it to disconnect when you log out. The extension answers with its version, whether it is connected and the connection’s ID. It answers no other site.
Turning it off on a site — Chrome grants these sites at install, so the Save buttons work with no further click. To turn the Save buttons off on a site, remove that site from the extension’s site access in Chrome’s extension settings. The extension then removes its scripts from that site.

Connection data (legal basis: contract performance):

Connect code — a one-time code that Omniconvert Commander creates while you are signed in. It works once and is valid for 10 minutes. It works only with the Commander extension. We store only a hash of it.
Access token — when the code is exchanged, Omniconvert Commander issues a token to the extension. The extension keeps it in Chrome’s extension storage on your computer and sends it only to Omniconvert Commander. Only the extension’s background worker reads it. The popup and the scripts on web pages never receive it. Omniconvert Commander stores a hash of the token and its first 12 characters, never the full token. The token expires after 30 days without use.
Connection record — the Omniconvert Commander user who connected, the store, the browser name, the browser’s user agent string (at most 500 characters), when the connection was made, last used and ended, and why it ended. Settings → Browser extension lists the live connections of your store.
Kept in your browser — Chrome’s local extension storage holds the access token, the connection’s ID, the store’s ID and name, the Omniconvert Commander address and the address of its saved-ads page, and the connect date. It also holds why the last connection ended, the last Omniconvert Commander address used and the one that handed over the token, the Shopify store name you last typed in the popup or on the extension’s setup page, and the popup’s light or dark theme. Nothing is kept in Chrome’s sync storage. When you choose Save to Omniconvert Commander or Open in Ad Library on a Facebook or Instagram ad, a short hand-off record goes to Chrome’s session storage: the ad’s ID, where it shows, whether to save it or only open it, the ID of the Ad Library tab it opens (and, when a Save button on the page started it, the ID of that page’s tab), and the times. It never holds the token. It is valid for two minutes. The extension deletes it when the Ad Library page finishes the hand-off, drops expired records each time it writes a new one, and keeps at most five. Chrome deletes them when the browser closes.

What the extension reads on each site (legal basis: legitimate interests). The extension reads the ad data that each page has already loaded, inside your browser. To place its Save buttons, it marks each ad in the page with a small attribute that holds the ad’s ID (for a YouTube search ad, its place among the search ads) and, on Facebook and Instagram, a second attribute that holds where it shows. It passes the ad’s own page data between its scripts through the page. The site’s own scripts can see these marks. They never hold your token. Unless this section, the saved-status check or the saved ads below say an item is sent, it stays in your browser.

Meta Ad Library — the extension reads each ad card and the ad data the page has already loaded, to show a Save button under each ad. It makes no extra request to Meta.
Facebook (feed) and Instagram (feed, Reels and Stories) — on each page and as you scroll, with no click, the extension checks the page’s own ad data for the posts on your screen. It keeps only each ad’s ID and where it shows (the Facebook feed, or the Instagram feed, Reels or Stories), to put a Save button on that ad. When you click the extension icon or press its shortcut, it also reads, for at most five ads on your screen, each ad’s ID, the advertiser’s name and the link to the ad’s own picture, and lists them in the popup with their pictures. It copies no posts that are not ads, no comments, no messages, no profile pictures and no names of people who reacted. These items stay in your browser, with one exception: when you choose Save to Omniconvert Commander or Open in Ad Library, the ad’s ID goes to facebook.com in the Ad Library link, and the ad opens in the Meta Ad Library. After Save to Omniconvert Commander, if the extension is connected and your plan includes the Inspiration Library, the extension saves the ad there with no second click. Open in Ad Library saves nothing. The page that opens is an ordinary Ad Library page, so the saved-status check below applies to it. No Facebook or Instagram feed page sends ad IDs to Omniconvert Commander.
YouTube (video, Shorts and search pages) — on every YouTube video, Shorts and search page you open, the extension reads the ads the page holds and shows a Save button on each. For each ad it reads the video ID (none for a search ad), the channel name (for a search ad, the name or web address the ad shows) and, when the page shows one, the channel ID, the headline, text and button text and, for a search ad only, the address of the ad’s picture. For a video ad, it builds the picture address from the video ID. A search ad has no video ID, so the extension makes an ID for it from a one-way fingerprint of the ad’s name, headline and text. When you click the extension icon or press its shortcut, it lists up to five of these ads in the popup. It copies no click address, no tracking ping, no "About this ad" data, no search query and nothing about the video you are watching.
TikTok (only when Omniconvert Commander turns TikTok saving on) — Chrome grants access to tiktok.com at install, but the extension reads nothing on TikTok until it is connected and Omniconvert Commander has turned TikTok saving on. Then, on TikTok Ad Library pages, it reads the ad data the page has already loaded, to show a Save button under each ad. On your TikTok For You page, if your plan includes the Inspiration Library, it reads the posts on your screen as you scroll, and again when you click the extension icon, press its shortcut or click a Save button. One read keeps at most five ads. For each ad it keeps the ad’s ID, the advertiser’s business name, the ad’s text, its button text and the link to its cover image. It keeps nothing from posts that are not ads. It copies no posting accounts, no comments, no likes, no messages, no videos, and not the reasons TikTok gives for showing you an ad. When you choose Find it in the TikTok Ad Library in the popup, the ad’s ID goes to library.tiktok.com in the link.
Your tabs — when you open the popup, the extension reads the address of the current tab, on any site, to show the right view or to open Omniconvert Commander in the matching Shopify store. Chrome also gives the extension the addresses of open tabs on the sites above, so it can start its scripts in tabs that are already open, and it reads the address of the tab a Save button is on, to check where the button’s message comes from. These addresses stay in your browser.

Saved-status check (legal basis: legitimate interests): while the extension is connected, a page of the Meta Ad Library, YouTube or (when TikTok saving is on) TikTok sends Omniconvert Commander the IDs of the ads the extension read on it. Omniconvert Commander uses them only to show whether your store already saved each ad. For each saved ad, the answer carries the first name of the teammate who saved it, the date, the folder, and the note with the first name of its author, so the Save button and the popup can show them (for example "Saved by Ana"). The extension receives first names only, never an email address. Omniconvert Commander does not store the IDs it is asked about. The log entry for this check records only how many IDs were asked about, how many were saved and how many cannot be saved, with your store and user IDs.

Saved ads (legal basis: legitimate interests — public data from the Meta Ad Library, and ads shown to you on Facebook, Instagram, YouTube and TikTok, saved only when you click Save to Omniconvert Commander):

Ad content from the Meta Ad Library (this includes ads you save from Facebook and Instagram, which the extension saves through the Meta Ad Library) — the advertiser’s name, page ID, profile picture link and page categories; the ad text, headline, caption, link description, call to action and landing page; the ad’s display format; the pictures and videos; every card of a carousel, with its own text and link; Meta’s count of the ad’s versions and their group ID; the dates, the platforms and the status on the day you saved it; and the ad’s Ad Library address.
Ad content from YouTube — the ad’s ID (its video ID or, for a search ad, the fingerprint ID described above), the channel’s name and, when the page shows one, its ID, the headline, text and button text, the address of the ad’s picture, and the address of the ad’s own YouTube page (a watch or Shorts page built from the ad’s video ID, or the YouTube results page for a search ad). It is never the address of the page you were on, and never your search.
Ad content from TikTok (when TikTok saving is on) — the ad’s ID, the advertiser’s business name, the text, the button text, the cover image link and the address of the TikTok page it came from (For You, or the ad’s TikTok Ad Library page) and, from the TikTok Ad Library, also the advertiser’s business ID, the dates the ad ran, TikTok’s own reach range, its landing page and the links to its video and images.
Media copy — after a save from the Meta Ad Library, Omniconvert Commander copies up to 10 of the ad’s files (pictures, videos and video cover images) from Meta’s servers to our object storage (section 4). The saved ad then keeps its media after Meta’s links expire. A save from YouTube or TikTok copies no picture and no video. Omniconvert Commander keeps only the links and shows the pictures from the platform’s own servers.
Who saved it, folders and notes — who saved the ad and when, the folder it is in, and the note you write. You can also create a folder from the Save button on a Meta Ad Library page. The name you type is kept in your store’s folder list, and the extension reads your store’s folder names to show that list. Members of your store see saves, folders and notes in Omniconvert Commander and in the extension. A note or a folder name is free text, so we recommend you do not write personal data about other people in it.

Diagnostic counts (legal basis: legitimate interests): while the extension is connected and your plan includes the Inspiration Library, a Meta Ad Library page (and a TikTok Ad Library page, when TikTok saving is on) reports which library it is, how many ad cards the extension found, how many it could not read, and the extension’s version number. The report holds no ad, no page address and no token. Omniconvert Commander records it, with your store and connection IDs, in its service logs only.

Request logs (legal basis: legitimate interests): like any web service, our servers log each request the extension makes: the time, the request type and address, the result, the browser’s user agent and your user ID. The log entries for connecting, saving, looking up saved ads and the diagnostic counts also carry your store ID. To stop abuse, our servers count requests per IP address for a short time: one minute for the connect step and 15 minutes for the other requests the extension makes.

Pictures from other servers: the popup and the Save button’s folder box show ad pictures, the pictures of recent saves and your store’s logo. Ad pictures load from the servers that host them (Meta, YouTube, Google and TikTok). Pictures of saves whose media we copied load from Omniconvert Commander. Your store’s logo loads from wherever your organization’s logo file is hosted. Your browser requests these pictures as it does for any web page, so those servers see your IP address and browser type. The extension does not copy these pictures.

We do NOT access: your Facebook, Instagram, TikTok, YouTube, Shopify or Omniconvert Commander password; the cookies or login sessions of these sites; any page of a site other than those named above, apart from the address of the tab you open the popup on; or your browsing history. The extension keeps no list of the pages you visit and sends none to us.

No analytics, no other recipients: the extension contains no analytics or advertising code and sends data only to Omniconvert Commander. Apart from the pictures described above, the only other requests it causes are pages you open yourself with a button: the Ad Library page of an ad you chose to save or open, the Meta Ad Library home page, the TikTok Ad Library page of a TikTok ad (when TikTok saving is on), your Omniconvert Commander pages and your Shopify admin. When you first install the extension, it also opens its own welcome page, which makes no request. Saving an ad starts no AI processing. Saved ads go to no third party other than our hosting sub-processor, and service logs and error reports go to our monitoring sub-processors (section 4). If a member of your store creates a share link for a saved ad, anyone with that link can see the ad. If you later use a saved ad in an AI feature, section 3 applies. We do not sell data from the extension and do not use it for advertising.

Chrome Web Store Limited Use: our use of information received from the extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Retention: a save and its note stay until you remove the save. Removing a save deletes the save, its folder placement and its note. It does not delete the saved ad content, its copied media, or the record of which Omniconvert Commander user saved the ad and when. A folder stays until you delete it. Deleting a folder moves its saves to Unfiled. We keep connection records and the hashed connect codes after a connection ends. Settings → Browser extension shows only live connections. A connection ends when you click Disconnect, revoke it in Settings → Browser extension, log out of Omniconvert Commander in the browser that holds the extension, lose access to the store, have your account deactivated or its sign-in reset, connect the browser to another store, or leave it unused for 30 days. Uninstalling the extension deletes the token and everything else the extension keeps in your browser. Closing a store in Omniconvert Commander archives it and keeps its data. To have your data deleted, email privacy@omniconvert.com; section 6 describes deletion on account termination.

Your controls: click Disconnect in the extension, or revoke your own connected browsers in Settings → Browser extension. Organization owners and admins can revoke any browser of the store. To delete a save, click Remove in the folder box under the ad on a Meta Ad Library page, or remove the save in Omniconvert Commander. Remove a site from the extension’s site access in Chrome to turn the Save buttons off on that site.

2.10 Adstein Chrome Extension (Inspiration Library)

The Adstein extension for Google Chrome ("Adstein — Save ads") saves ads to your brand’s Inspiration Library in Adstein. It works on the Meta Ad Library, on the Facebook feed, on the Instagram feed, Reels and Stories, on YouTube video, Shorts and search pages and, when Adstein turns TikTok saving on, on TikTok. You install it and connect it to one brand yourself. The extension’s popup labels the brand as a store.

The extension sends nothing to Adstein until you connect it. Before you connect it, it can already read ad data on Meta Ad Library, Facebook, Instagram and YouTube pages to place its Save buttons. That data stays in your browser. The extension reads nothing on TikTok until it is connected and Adstein has turned TikTok saving on.

Sites and permissions (Chrome asks once, when you install the extension):

Sites — https://lab.agentadstein.com (Adstein and its API), https://www.facebook.com, https://www.instagram.com, https://www.tiktok.com and https://www.youtube.com. The extension also runs on the Meta Ad Library (facebook.com/ads/library) and the TikTok Ad Library (library.tiktok.com/ads). It does not run on Messenger or Instagram Direct. It asks for no other site and has no optional permission.
Chrome permissions — "storage" (to keep the connection in your browser), "activeTab" (to read the address of the tab you open the popup on, and the ads on it when you click the extension icon or press its shortcut) and "scripting" (to add the Save buttons to these sites and read their ad data). The extension does not ask for the "tabs" permission.
Adstein pages — only pages on lab.agentadstein.com can send the extension a message. Such a page can ask whether the extension is installed and connected, give it a one-time connect code, and tell it to disconnect when you log out. The extension answers with its version, whether it is connected and the connection’s ID. It answers no other site.
Turning it off on a site — Chrome grants these sites at install, so the Save buttons work with no further click. To turn the Save buttons off on a site, remove that site from the extension’s site access in Chrome’s extension settings. The extension then removes its scripts from that site.

Connection data (legal basis: contract performance):

Connect code — a one-time code that Adstein creates while you are signed in. It works once and is valid for 10 minutes. It works only with the Adstein extension. We store only a hash of it.
Access token — when the code is exchanged, Adstein issues a token to the extension. The extension keeps it in Chrome’s extension storage on your computer and sends it only to Adstein. Only the extension’s background worker reads it. The popup and the scripts on web pages never receive it. Adstein stores a hash of the token and its first 12 characters, never the full token. The token expires after 30 days without use.
Connection record — the Adstein user who connected, the brand, the browser name, the browser’s user agent string (at most 500 characters), when the connection was made, last used and ended, and why it ended. Settings → Browser extension lists the live connections of your brand.
Kept in your browser — Chrome’s local extension storage holds the access token, the connection’s ID, the brand’s ID and name, the Adstein address and the address of its saved-ads page, and the connect date. It also holds why the last connection ended, the last Adstein address used and the one that handed over the token, and the popup’s light or dark theme. Nothing is kept in Chrome’s sync storage. When you choose Save to Adstein or Open in Ad Library on a Facebook or Instagram ad, a short hand-off record goes to Chrome’s session storage: the ad’s ID, where it shows, whether to save it or only open it, the ID of the Ad Library tab it opens (and, when a Save button on the page started it, the ID of that page’s tab), and the times. It never holds the token. It is valid for two minutes. The extension deletes it when the Ad Library page finishes the hand-off, drops expired records each time it writes a new one, and keeps at most five. Chrome deletes them when the browser closes.

Meta Ad Library — the extension reads each ad card and the ad data the page has already loaded, to show a Save button under each ad. It makes no extra request to Meta.
Facebook (feed) and Instagram (feed, Reels and Stories) — on each page and as you scroll, with no click, the extension checks the page’s own ad data for the posts on your screen. It keeps only each ad’s ID and where it shows (the Facebook feed, or the Instagram feed, Reels or Stories), to put a Save button on that ad. When you click the extension icon or press its shortcut, it also reads, for at most five ads on your screen, each ad’s ID, the advertiser’s name and the link to the ad’s own picture, and lists them in the popup with their pictures. It copies no posts that are not ads, no comments, no messages, no profile pictures and no names of people who reacted. These items stay in your browser, with one exception: when you choose Save to Adstein or Open in Ad Library, the ad’s ID goes to facebook.com in the Ad Library link, and the ad opens in the Meta Ad Library. After Save to Adstein, if the extension is connected and your plan includes the Inspiration Library, the extension saves the ad there with no second click. Open in Ad Library saves nothing. The page that opens is an ordinary Ad Library page, so the saved-status check below applies to it. No Facebook or Instagram feed page sends ad IDs to Adstein.
YouTube (video, Shorts and search pages) — on every YouTube video, Shorts and search page you open, the extension reads the ads the page holds and shows a Save button on each. For each ad it reads the video ID (none for a search ad), the channel name (for a search ad, the name or web address the ad shows) and, when the page shows one, the channel ID, the headline, text and button text and, for a search ad only, the address of the ad’s picture. For a video ad, it builds the picture address from the video ID. A search ad has no video ID, so the extension makes an ID for it from a one-way fingerprint of the ad’s name, headline and text. When you click the extension icon or press its shortcut, it lists up to five of these ads in the popup. It copies no click address, no tracking ping, no "About this ad" data, no search query and nothing about the video you are watching.
TikTok (only when Adstein turns TikTok saving on) — Chrome grants access to tiktok.com at install, but the extension reads nothing on TikTok until it is connected and Adstein has turned TikTok saving on. Then, on TikTok Ad Library pages, it reads the ad data the page has already loaded, to show a Save button under each ad. On your TikTok For You page, if your plan includes the Inspiration Library, it reads the posts on your screen as you scroll, and again when you click the extension icon, press its shortcut or click a Save button. One read keeps at most five ads. For each ad it keeps the ad’s ID, the advertiser’s business name, the ad’s text, its button text and the link to its cover image. It keeps nothing from posts that are not ads. It copies no posting accounts, no comments, no likes, no messages, no videos, and not the reasons TikTok gives for showing you an ad. When you choose Find it in the TikTok Ad Library in the popup, the ad’s ID goes to library.tiktok.com in the link.
Your tabs — when you open the popup, the extension reads the address of the current tab, on any site, to show the right view. Chrome also gives the extension the addresses of open tabs on the sites above, so it can start its scripts in tabs that are already open, and it reads the address of the tab a Save button is on, to check where the button’s message comes from. These addresses stay in your browser.

Saved-status check (legal basis: legitimate interests): while the extension is connected, a page of the Meta Ad Library, YouTube or (when TikTok saving is on) TikTok sends Adstein the IDs of the ads the extension read on it. Adstein uses them only to show whether your brand already saved each ad. For each saved ad, the answer carries the first name of the teammate who saved it, the date, the folder, and the note with the first name of its author, so the Save button and the popup can show them (for example "Saved by Ana"). The extension receives first names only, never an email address. Adstein does not store the IDs it is asked about. The log entry for this check records only how many IDs were asked about, how many were saved and how many cannot be saved, with your brand and user IDs.

Ad content from the Meta Ad Library (this includes ads you save from Facebook and Instagram, which the extension saves through the Meta Ad Library) — the advertiser’s name, page ID, profile picture link and page categories; the ad text, headline, caption, link description, call to action and landing page; the ad’s display format; the pictures and videos; every card of a carousel, with its own text and link; Meta’s count of the ad’s versions and their group ID; the dates, the platforms and the status on the day you saved it; and the ad’s Ad Library address.
Ad content from YouTube — the ad’s ID (its video ID or, for a search ad, the fingerprint ID described above), the channel’s name and, when the page shows one, its ID, the headline, text and button text, the address of the ad’s picture, and the address of the ad’s own YouTube page (a watch or Shorts page built from the ad’s video ID, or the YouTube results page for a search ad). It is never the address of the page you were on, and never your search.
Ad content from TikTok (when TikTok saving is on) — the ad’s ID, the advertiser’s business name, the text, the button text, the cover image link and the address of the TikTok page it came from (For You, or the ad’s TikTok Ad Library page) and, from the TikTok Ad Library, also the advertiser’s business ID, the dates the ad ran, TikTok’s own reach range, its landing page and the links to its video and images.
Media copy — after a save from the Meta Ad Library, Adstein copies up to 10 of the ad’s files (pictures, videos and video cover images) from Meta’s servers to our object storage (DigitalOcean Spaces in Amsterdam, EU). The saved ad then keeps its media after Meta’s links expire. A save from YouTube or TikTok copies no picture and no video. Adstein keeps only the links and shows the pictures from the platform’s own servers.
Who saved it, folders and notes — who saved the ad and when, the folder it is in, and the note you write. You can also create a folder from the Save button on a Meta Ad Library page. The name you type is kept in your brand’s folder list, and the extension reads your brand’s folder names to show that list. Members of your brand see saves, folders and notes in Adstein and in the extension. A note or a folder name is free text, so we recommend you do not write personal data about other people in it.

Diagnostic counts (legal basis: legitimate interests): while the extension is connected and your plan includes the Inspiration Library, a Meta Ad Library page (and a TikTok Ad Library page, when TikTok saving is on) reports which library it is, how many ad cards the extension found, how many it could not read, and the extension’s version number. The report holds no ad, no page address and no token. Adstein records it, with your brand and connection IDs, in its service logs only.

Request logs (legal basis: legitimate interests): like any web service, our servers log each request the extension makes: the time, the request type and address, the result, the browser’s user agent and your user ID. The log entries for connecting, saving, looking up saved ads and the diagnostic counts also carry your brand ID. To stop abuse, our servers count requests per IP address for a short time: one minute for the connect step and 15 minutes for the other requests the extension makes.

Pictures from other servers: the popup and the Save button’s folder box show ad pictures, the pictures of recent saves and your brand’s logo. Ad pictures load from the servers that host them (Meta, YouTube, Google and TikTok). Pictures of saves whose media we copied load from Adstein. Your brand’s logo loads from wherever your organization’s logo file is hosted. Your browser requests these pictures as it does for any web page, so those servers see your IP address and browser type. The extension does not copy these pictures.

We do NOT access: your Facebook, Instagram, TikTok, YouTube or Adstein password; the cookies or login sessions of these sites; any page of a site other than those named above, apart from the address of the tab you open the popup on; or your browsing history. The extension keeps no list of the pages you visit and sends none to us.

No analytics, no other recipients: the extension contains no analytics or advertising code and sends data only to Adstein. Apart from the pictures described above, the only other requests it causes are pages you open yourself with a button: the Ad Library page of an ad you chose to save or open, the Meta Ad Library home page, the TikTok Ad Library page of a TikTok ad (when TikTok saving is on) and your Adstein pages. When you first install the extension, it also opens its own welcome page, which makes no request. Saving an ad starts no AI processing. Saved ads go to no third party other than our hosting provider, DigitalOcean. Service logs go to New Relic and error reports go to Sentry, our monitoring providers. If a member of your brand creates a share link for a saved ad, anyone with that link can see the ad. We do not sell data from the extension and do not use it for advertising.

Chrome Web Store Limited Use: our use of information received from the extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Retention: a save and its note stay until you remove the save. Removing a save deletes the save, its folder placement and its note. It does not delete the saved ad content, its copied media, or the record of which Adstein user saved the ad and when. A folder stays until you delete it. Deleting a folder moves its saves to Unfiled. We keep connection records and the hashed connect codes after a connection ends. Settings → Browser extension shows only live connections. A connection ends when you click Disconnect, revoke it in Settings → Browser extension, log out of Adstein in the browser that holds the extension, lose access to the brand, have your account deactivated or its sign-in reset, connect the browser to another brand, or leave it unused for 30 days. Uninstalling the extension deletes the token and everything else the extension keeps in your browser. Closing a brand in Adstein archives it and keeps its data. To have your data deleted, email privacy@omniconvert.com. We delete it within 30 days of a verified request, except where the law requires us to keep it.

Your controls: click Disconnect in the extension, or revoke your own connected browsers in Settings → Browser extension. Organization owners and admins can revoke any browser of the brand. To delete a save, click Remove in the folder box under the ad on a Meta Ad Library page, or remove the save in Adstein. Remove a site from the extension’s site access in Chrome to turn the Save buttons off on that site.

3. How Artificial Intelligence Processes Your Data

Omniconvert Commander uses a multi-agent AI system (built on LangGraph) to analyze your connected data and generate insights. Here is exactly how AI is used:

3.1 What AI Does

Detects statistically significant anomalies in your metrics
Correlates patterns across multiple data sources
Generates natural-language descriptions of insights (headlines, summaries, root cause analyses)
Creates A/B test hypotheses and recommendations
Decomposes ad creatives into structured components (hook, body, offer, CTA) for the Ad Intelligence module
Synthesizes competitive intelligence from your ad data and competitor public ads

3.2 Anonymization Before AI Processing

Before any data is sent to an external AI model, it is anonymized. Specifically:

Customer names, email addresses, phone numbers, and order IDs are removed from support ticket data
Individual user identifiers are not included in AI prompts
Prompts contain only aggregated metrics, percentages, and anonymized thematic content

External AI providers used to process your anonymized data:

Anthropic (Claude) — text insight generation, ad copy analysis, brief creation; receives anonymized metrics, ad copy text, thematic summaries
Google (Gemini) — video ad analysis; receives anonymized video content for structural analysis
OpenAI — ad image generation, ad copy generation; receives brief specifications and style directives (no customer data)
fal.ai (Flux, Kling) — image and video generation; receives creative briefs (no customer data)
Runway ML — video generation; receives creative briefs (no customer data)

3.3 No AI Training on Your Data

Your data is never used to train AI models — neither by Omniconvert nor by our AI sub-processors. All AI sub-processor contracts include explicit prohibitions on using customer data for model training.

3.4 No Automated Decisions with Legal Effects

Omniconvert Commander does not make automated decisions that produce legal effects or similarly significant impacts on any individual. All AI-generated insights are recommendations for your review and action.

4. Sub-Processors

We use the following sub-processors to deliver the Omniconvert Commander service. All sub-processors have been assessed for GDPR compliance and have signed Data Processing Agreements with Omniconvert.

Anthropic, PBC (USA) — LLM inference (insight generation, ad analysis) — Privacy Policy
Google LLC (USA) — Gemini LLM inference (video analysis) — Google DPA
OpenAI, LLC (USA) — GPT image generation, ad copy generation — Privacy Policy
fal.ai (USA) — Flux image generation, Kling video generation — fal.ai DPA
Runway AI, Inc. (USA) — Runway ML video generation — Privacy Policy
DigitalOcean, LLC (USA and EU) — cloud infrastructure: application servers in New York (USA); database hosting (PostgreSQL) and object storage (Spaces) in Amsterdam (EU), for generated creatives and the media of ads saved from the Meta Ad Library with the Omniconvert Commander and Adstein Chrome extensions — DigitalOcean DPA
New Relic, Inc. (EU region) — service logs and performance monitoring — New Relic DPA
Functional Software, Inc. (Sentry) (USA) — error reports — Sentry DPA

International Transfers: AI sub-processors and Sentry are based in the USA, and our application servers run in DigitalOcean’s New York region (USA). Data transfers to these processors are governed by Standard Contractual Clauses (SCCs) adopted by the European Commission, which provide equivalent protection to EU data protection law.

Sub-Processor Changes: We will notify you at least 30 days before adding or replacing any sub-processor that processes your data. You may object within this period; if the objection cannot be resolved, you may terminate your Omniconvert Commander subscription.

5. Agency Multi-Property Model

If you use Omniconvert Commander as an agency managing multiple client properties:

Data isolation: Each client property's data is strictly isolated. Users assigned to Property A cannot access data from Property B, even within the same agency account.
Access control: You control which team members can access each property.
Client responsibility: As an agency, you are responsible for having a lawful basis to connect your clients' analytics accounts to Omniconvert Commander and for informing your clients about this processing.
Property deletion: When you remove a property from Omniconvert Commander, all derived insights for that property are deleted within 30 days. No further data from that property is queried.

6. Data Retention

AI-generated insights and recommendations — until you delete them, or 12 months after last activity on the property
Analysis run metadata (no raw data) — 90 days
Ad intelligence briefs — until you delete them, or 12 months after generation
Gorgias anonymized ticket themes — 90 days
HITL review queue entries — 30 days after resolution
Insight feedback (your own feedback) — 24 months
Integration credentials (encrypted) — until you disconnect the integration
Chrome extension connect codes (Omniconvert Commander and Adstein) — stored as a hash and kept after use; single use; valid for 10 minutes
Chrome extension connections (Omniconvert Commander and Adstein) — kept after the connection ends (Settings → Browser extension shows only live connections); the access token expires after 30 days without use
Ads saved with the Omniconvert Commander or Adstein Chrome extension — a save and its note until you remove the save; a folder until you delete it (its saves move to Unfiled); the saved ad content, the copied media of Meta Ad Library saves and the record of who saved the ad and when are kept after a removal
Adstein brands — closing a brand in Adstein archives it and keeps its data; to have it deleted, email privacy@omniconvert.com. We delete it within 30 days of a verified request, except where the law requires us to keep it.

On Account Termination: All data associated with your Omniconvert Commander account is deleted within 30 days of account closure, except where retention is required by law.

7. Security

Encryption at rest — all stored data is encrypted using AES-256
Encryption in transit — all API communication uses TLS 1.2 or higher
Credential security — integration API keys and OAuth tokens are stored encrypted using pgcrypto; keys are never logged
Access control — role-based access with property-level isolation
Anonymization — PII in support ticket data is automatically stripped before AI processing and storage
ISO 27001 — Omniconvert is ISO 27001 certified
Audit logging — all access to integration credentials and data is logged

8. Your Rights

As a subscriber (data controller for your own analytics data), you have the following rights regarding the data Omniconvert Commander processes on your behalf:

Access — view all insights and data in your Omniconvert Commander dashboard at any time
Deletion — delete individual insights via the dashboard, or request full account deletion by emailing privacy@omniconvert.com
Portability — export your insights as CSV or PDF from the dashboard
Disconnection — disconnect any integration at any time from Settings → Integrations; disconnect the Chrome extension from its popup, or revoke your own connected browsers in Settings → Browser extension (organization owners and admins can revoke any browser of the store); remove a site from the extension’s site access in Chrome to turn its Save buttons off on that site; for Adstein, disconnect the extension from its popup, or revoke your own connected browsers in Adstein under Settings → Browser extension (organization owners and admins can revoke any browser of the brand)
Correction — update your account information via Settings
Objection — if you object to a processing activity, contact privacy@omniconvert.com; we will assess and respond within 30 days

9. Contact

Data Controller: Omniconvert SRL 14 Vasile Stroescu Street Bucharest 021374, Romania Email: privacy@omniconvert.com General: contact@omniconvert.com

For data protection inquiries related to Omniconvert Commander or Adstein: privacy@omniconvert.com

10. Changes to This Notice

We will notify you via email and in-app notification at least 14 days before making material changes to this privacy notice. The current version is always available at https://www.omniconvert.com/privacy-policy-commander/.

———

Google User Data

Omniconvert Commander Insights ("Omniconvert Commander", "we", "our") integrates with Google APIs to provide eCommerce performance intelligence on behalf of merchants who explicitly authorize the connection through Google's OAuth consent screen. This section describes how Omniconvert Commander accesses, uses, stores, shares, retains, and deletes Google user data, and supplements the rest of this Privacy Policy. Omniconvert Commander's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data Accessed

When a merchant connects a Google account to Omniconvert Commander, we request only the OAuth scopes strictly required to deliver the connected feature. The data we access is limited to:

Google account identity (sign-in only) — openid, email, profile. We use this solely to identify the authenticating user, link the connection to the correct Omniconvert Commander workspace, and display the user's name and email in the Omniconvert Commander UI.
Google Analytics 4 (read-only) — https://www.googleapis.com/auth/analytics.readonly. We read aggregated GA4 reporting data (sessions, users, conversions, revenue, traffic source dimensions, e-commerce events, and related metrics) for the GA4 properties the merchant explicitly selects during onboarding. We do not access GA4 admin settings, edit GA4 configuration, or read user-level identifiers from GA4.
Google Ads (read-only, where enabled) — https://www.googleapis.com/auth/adwords (read-only usage). We read campaign, ad group, ad, keyword, and performance metrics (impressions, clicks, cost, conversions, ROAS) for the ad accounts the merchant links. We do not create, edit, pause, or delete campaigns unless the merchant explicitly opts into a managed-optimization feature and re-consents to write scopes at that time.

We do not request access to Gmail, Google Drive, Google Calendar, Google Contacts, YouTube content, Google Photos, or any other Google service outside the scopes listed above. This concerns access through your Google account. Sections 2.9 and 2.10 describe how the Omniconvert Commander and Adstein Chrome extensions read ads on the YouTube pages you open.

Data Usage

Omniconvert Commander uses Google user data exclusively to provide and improve the user-facing features the merchant signed up for. Specifically, we use Google data to:

Authenticate the user and maintain their session in Omniconvert Commander.
Detect anomalies in eCommerce performance (traffic, conversions, revenue, paid media efficiency) using deterministic statistical methods (z-score, percentage thresholds, trend analysis).
Correlate signals across GA4, Google Ads, Shopify, and other sources the merchant has connected, to surface likely root causes of performance changes.
Generate written narratives, recommendations, and A/B test hypotheses for the merchant. When generative AI (large language models) is used to produce these narratives, the prompt is constructed from aggregated, de-identified metrics only; we do not send raw user-level data, individual session data, or personally identifying information from Google to any LLM provider.
Display dashboards, reports, and insight cards inside the Omniconvert Commander app to the merchant who connected the account.

Omniconvert Commander's use of Google user data complies with the Google API Services User Data Policy's Limited Use requirements:

We do not use Google user data to serve advertisements.
We do not sell Google user data.
We do not allow humans to read Google user data, except (a) with the merchant's explicit consent for a specific support request, (b) where required for security investigations or to comply with applicable law, or (c) where the data has been aggregated and anonymized and is used for internal operations in line with Google's policy.
We do not use Google user data to train, fine-tune, or improve generalized or non-personalized AI/ML models.

Data Sharing

Omniconvert Commander does not sell, rent, or trade Google user data. We share Google user data only in the following limited circumstances:

With the merchant who authorized the connection — Authorized users within the merchant's Omniconvert Commander workspace can view dashboards and reports derived from the connected Google data.
With trusted sub-processors that operate the Omniconvert Commander service — strictly for the purpose of running our infrastructure under written data protection agreements:
- Cloud hosting and managed databases (DigitalOcean: application servers in New York, USA; database and object storage in Amsterdam, EU).
- Application monitoring, logging, and error tracking providers.
- LLM providers used for narrative generation. Only aggregated, anonymized metrics are sent; raw Google user data, identifiers, or PII are never transmitted to LLM providers.
For legal reasons — when we have a good-faith belief that disclosure is required to comply with applicable law, regulation, legal process, or enforceable governmental request, or to protect the rights, property, or safety of Omniconvert, our users, or the public.
In a corporate transaction — in the event of a merger, acquisition, reorganization, or sale of assets, in which case the acquiring entity will be bound by this Privacy Policy or will notify users of any material change.

We do not share Google user data with advertising networks, data brokers, or analytics providers for cross-site tracking purposes.

Data Storage & Protection

We take the following measures to protect Google user data:

Encryption in transit — All communication between the merchant's browser, Omniconvert Commander servers, and Google APIs is encrypted using TLS 1.2 or higher.
Encryption at rest — OAuth refresh tokens, access tokens, and any cached Google data are encrypted at rest using industry-standard symmetric encryption (AES-256) with keys managed by our cloud provider's key management service.
Tenant isolation — Google data is logically partitioned per merchant workspace; queries are scoped by workspace identifier at the application layer, and no cross-tenant data access is permitted.
Access controls — Production access to systems holding Google user data is restricted to a small number of authorized engineers, requires multi-factor authentication, and is audited.
Network controls — Production databases are not publicly accessible; access is limited to the application's private network.
Secrets management — Google client secrets and signing keys are stored in a dedicated secrets manager and are not committed to source control.
Vendor due diligence — Sub-processors that may handle Google user data are reviewed for security posture and bound by data protection agreements.
Incident response — We maintain an incident response process. In the event of a confirmed data breach affecting Google user data, we will notify affected merchants and the relevant authorities in accordance with applicable law.

No system is perfectly secure. While we use commercially reasonable safeguards, we cannot guarantee absolute security.

Data Retention & Deletion

OAuth tokens are retained for as long as the merchant's Google connection is active. When a merchant disconnects Google in Omniconvert Commander, or revokes Omniconvert Commander's access from their Google Account permissions page, we revoke the token with Google and delete it from our systems within 30 days.
Cached Google reporting data (GA4 metrics, Google Ads performance data) is retained only as long as it is needed to power dashboards and historical comparisons inside Omniconvert Commander, and in any case no longer than 24 months. Aggregated, de-identified statistics derived from this data may be retained longer for product analytics and benchmarking.
Account closure — When a merchant closes their Omniconvert Commander workspace, all Google user data associated with that workspace, including OAuth tokens and cached reporting data, is deleted from our production systems within 30 days, and from encrypted backups within 90 days.
User-initiated deletion — A merchant can request immediate deletion of all Google user data we hold about their workspace at any time by:
1. Disconnecting Google inside the Omniconvert Commander app (Settings → Integrations → Google → Disconnect), which triggers automated deletion, or
2. Emailing privacy@omniconvert.com with the subject "Omniconvert Commander — Google Data Deletion Request". We will confirm and complete deletion within 30 days.
Revoking access at Google — At any time, a user may revoke Omniconvert Commander's access to their Google account at https://myaccount.google.com/permissions. Revocation will sever Omniconvert Commander's ability to read further data; previously cached data will be deleted following the process above.

For any questions about how Omniconvert Commander handles Google user data, contact us at privacy@omniconvert.com.

———

Meta (Facebook & Instagram) User Data

Omniconvert Commander Insights integrates with Meta's Marketing API to provide ad performance intelligence and, where the merchant explicitly opts in, automated optimization for Meta Ads campaigns. Our use of data received from Meta complies with Meta's Platform Terms and Developer Policies.

Data Accessed

When a merchant connects their Meta Business account to Omniconvert Commander, we request only the permissions strictly required for the connected feature set:

email, public_profile — to identify the authenticating user.
business_management — to enumerate the Business Manager accounts the user administers, so the merchant can pick which one to connect.
ads_read — to read campaign structure, creatives, audiences, placements, and performance metrics (impressions, clicks, spend, conversions, ROAS, attribution data) for the ad accounts the merchant selects.
ads_management — required only when the merchant opts into managed-optimization features (e.g., automated budget reallocation, auto pause/start rules). Omniconvert Commander only writes changes that the merchant has explicitly configured in advance via Omniconvert Commander's rules engine; we never make ad changes outside the merchant's stated intent.
pages_read_engagement, pages_show_list — where the merchant connects a Facebook Page for ad attribution and creative analysis.
instagram_basic — where the merchant connects an Instagram Business account linked to ads they wish to analyze.

We do not request access to private messages, friend lists, or any user data outside the scopes listed above. This concerns access through your Meta account. Sections 2.9 and 2.10 describe how the Omniconvert Commander and Adstein Chrome extensions read ads on the Facebook and Instagram pages you open.

Data Usage

We use Meta data to:

Detect anomalies and trends in paid social performance.
Correlate Meta ad performance with site analytics, revenue, and other connected sources.
Generate written narratives, recommendations, and creative-level insights inside the Omniconvert Commander app. Only aggregated, de-identified metrics are sent to LLM providers; raw Meta data, user identifiers, or PII are never transmitted to LLMs.
Where the merchant has explicitly opted in, execute pre-configured optimization actions (e.g., pause an ad set when CPA exceeds a threshold the merchant defined).

We do not use Meta data for advertising targeting outside the merchant's own ad accounts, do not sell Meta data, and do not use Meta data to train generalized AI/ML models.

Data Sharing

We share Meta data only with the merchant's authorized workspace users and with the same limited set of sub-processors described in the "Google User Data → Data Sharing" section above (cloud hosting, monitoring, and aggregated-metrics-only LLM providers), all under written data protection agreements. We do not share Meta data with advertising networks or data brokers.

Data Storage & Protection

Meta access tokens, page tokens, and any cached Meta data are encrypted at rest (AES-256), encrypted in transit (TLS 1.2+), logically isolated per merchant workspace, and protected by the access controls, network controls, and incident-response process described in the "Google User Data → Data Storage & Protection" section above.

Data Retention & Deletion

Meta access tokens are retained for as long as the connection is active and deleted within 30 days of disconnection.
Cached Meta reporting data is retained for up to 24 months to power historical comparisons inside Omniconvert Commander.
A merchant can disconnect Meta from Omniconvert Commander at any time (Settings → Integrations → Meta → Disconnect), which triggers automated deletion of tokens and cached data.
A user can revoke Omniconvert Commander's access from their Facebook account at https://www.facebook.com/settings?tab=business_tools.

For any questions about how Omniconvert Commander handles Meta user data, contact us at privacy@omniconvert.com.