Omniscio

Omniscio — Cookie Notice

Effective date: 2026-08-20 Last updated: 2026-11-08


Key terms at a glance

Plain-English summary — not a substitute for the full Cookie Notice. This box is a quick, friendly overview of the points people ask about most. It is not legal language and does not replace the numbered sections below, which are the Notice that actually applies. If anything here seems to differ from those sections, the full sections control.


1. About this notice

This Cookie Notice explains how Omniscio LLC ("Omniscio," "the Company," "we," "us," or "our"), a North Carolina limited liability company, uses cookies and similar technologies. It covers:

— together, the "Services." It supplements, and should be read with, our Privacy Policy. Where this notice and the Privacy Policy describe the same cookie, the descriptions are meant to be consistent.

2. What cookies and local storage are

Cookies are small text files placed on your computer or mobile device when you visit a website or use a connected app. They serve different purposes — for example, keeping you signed in, remembering your preferences, letting you move between pages efficiently, and helping the operator understand how a site is used.

Local storage and session storage are related browser technologies that let a site store data in your browser, similar to cookies but typically holding more data.

Session vs. persistent. A session cookie expires when you close your browser; a persistent cookie stays on your device until it expires or you delete it.

First-party vs. third-party. A first-party cookie is set by us (or by the App running on your own machine) and read only by us. A third-party cookie is set by an outside service loaded into a page — for example an analytics or advertising provider — and can be read by that outside party. As described below, the App itself sets only first-party, strictly-necessary cookies, while our marketing website loads Google Analytics (a third-party analytics tool).

3. The strictly-necessary cookies we set

We set three strictly-necessary cookies, on two different hosts: two on your own device, from the App's local server when you use the optional web-access feature (pairing a phone or browser to the App over your local network — the same surface as the mobile-web access above), and one on our share site, shares.omniscio.com. All three are first-party. Each is set only by the host named against it, and none of them is used for tracking, analytics or advertising.

On your device (the App's local server)

a) Sign-in cookie

b) Device-recognition cookie

On our share site

c) Share-link cookie (shares.omniscio.com)

Share pages also keep some choices in your browser's local storage on that site: your theme, your text size, your playback speed, and any selections you made on an interactive page. If you sign in with Google to comment on a share, Google sign-in keeps you signed in in that browser; that sign-in is shared with Google and with nobody else. None of this storage is used for tracking or advertising.

Because each is strictly necessary to deliver a feature you have chosen to use, all three are exempt from cookie-consent requirements. The two App cookies are set when you sign in to the web-access feature; __session is set only when you unlock a protected or view-limited link. We set no advertising or third-party tracking cookies on either host.

4. Cookie categories

Category Used? Description Details / who serves them
Strictly necessary / essential Yes Required to operate a feature you use; cannot be switched off. omniscio_web_token (persistent, up to 30 days) and omniscio_device_id (persistent, up to 400 days) — both first-party, set by the App's web-access feature (Section 3). On shares.omniscio.com, one first-party __session cookie (HttpOnly, Secure, SameSite=Lax, up to 24 hours, sent only to Share pages) holds signed passes for the Shares you open: share_unlock_… after you enter a Share's password (24 hours), share_view_… so one visit is counted once (6 hours), and share_ws_… after a workspace-only Share checks your sign-in (15 minutes; it carries your account id). It is not a tracking or advertising cookie and is never shared.
Analytics Yes — on our websites; analytics storage is off until the consent decision allows it, so no visitor has an analytics script or an analytics cookie until they press Accept Help us understand how our websites are used (page views, traffic sources, aggregate feature interest). Google Analytics, loaded directly (measurement id G-RRBM55YX1V) on the pages of omniscio.com and docs.omniscio.com, these legal pages included — except the help library (docs.omniscio.com/library/…), the /welcome page that opens after an App sign-in, and the account-email link page (/auth/action), which load no analytics. The gate that decides your choice loads on each of those pages, but the analytics script itself is fetched only while your choice permits analytics — so a visitor who has not answered downloads no analytics script and no analytics cookie is set. Google Consent Mode is set before the script is fetched, and Global Privacy Control always keeps analytics and ad storage denied. Once the script is fetched, Google sets its own third-party cookies (for example _ga, _ga_*) — only once you press Accept. Decline, the Do Not Sell or Share link, or Global Privacy Control turn Google Analytics off again; cookies it already set stay in your browser until they expire or you delete them (see Browser settings in Section 7). Not present on shares.omniscio.com or in the App.
Advertising / remarketing Yes — via Google Analytics ("Google signals") Used to build interest profiles or to show/measure ads across sites. Google Analytics ads-personalization ("Google signals") is enabled, so GA4 sets advertising/remarketing cookies via doubleclick.net and can use your activity for remarketing. Under California law this is a "share." Opt out with the "Do Not Sell or Share My Personal Information" link in our website footer, Global Privacy Control, or the controls in Section 7.
Advertising conversion measurement Yes — on our websites, only with advertising consent, and only while we run that platform's ads Tell an ad platform that a visitor who clicked its ad went on to download, sign up or buy, so we can see which ads work. Meta Pixel (connect.facebook.net, sets _fbp / _fbc and fr) and the Google Ads conversion tag (googleadservices.com, doubleclick.net) load only after you consent to advertising, and only while we run that platform's ads — neither loads from a download click without that consent. A first-party omniscio_attr cookie (30 days, shared across omniscio.com and docs.omniscio.com) is created only with advertising consent and holds the campaign tags (utm_*), the ad click ids (gclid, gbraid, wbraid, fbclid) and a random browser id. Without consent no such cookie is created, and on withdrawal the click ids, the browser id and the Meta cookies are deleted and never sent. Meta documents its fr cookie as being "used to deliver, measure and improve the relevancy of ads, with a lifespan of 90 days" (Meta Cookies Policy); it can only exist once the Meta Pixel has loaded, which needs your advertising consent and a configured Meta campaign. Neither platform is configured on our sites today, so no Meta Pixel and no Google Ads tag loads until we switch one on. Opt out with Decline, the Do Not Sell or Share link, or Global Privacy Control (Section 7).
Functional (preferences) Yes — local storage only, no cookies Remember preferences such as theme or language. amc-docs-theme on docs.omniscio.com keeps your light or dark choice (set to dark on your first visit). omniscio.launchOffer on omniscio.com records that you closed or joined the launch-offer popup, so it is not shown again. Both stay in your browser, are never sent to us or anyone else, and have no expiry; clearing your browser's site data removes them.
First-party measurement (local storage, no cookies) Only after you press Accept on the banner that names it Show you the same version of a page on every visit during an A/B test and count, on our own server, which version led to downloads and sign-ups (a download click records the version only, never the ID), and which page of our websites a download started from. omniscio-exp (the version you were shown) and amc-anon-id (a random anonymous visitor ID), kept in your browser's local storage on omniscio.com only after you press Accept, plus omniscio-consent-ab (a flag recording that Accept), omniscio-exp-seen (a marker so first views are counted once) and omniscio-ab-asked (a marker that we have already asked you about the visitor ID). Before you accept, an A/B test only keeps your version in session storage until you close the tab: no identifier is created and nothing is sent. Nothing is sent to any third party. Decline on the banner, the "Do Not Sell or Share" link, or Global Privacy Control deletes the ID, the stored version and the flag immediately (also if you change your choice in another tab; your analytics answer is shared by both sites, while the A/B version and ID stay in this browser on omniscio.com); with Global Privacy Control, Decline or the link on, you see the standard page. If you pressed Accept on the older banner, which did not mention the visitor ID, the banner asks once more about the ID alone; declining that question leaves your analytics choice as it was. After a Google/GitHub sign-in to the App, omniscio.com/welcome links the version to your new account once, only if you pressed Accept. Separately, omniscio-landing keeps the address of the first page of our websites you opened (for example omniscio.com/guides/…, never a query string or an identifier) in session storage until you close the tab, so a download click can say which page led to it; only after you press Accept is it also kept for 30 days in local storage as omniscio-landing-first, on that one site only. Decline, the "Do Not Sell or Share" link or Global Privacy Control deletes omniscio-landing-first on your next page load. Nothing is sent to us except with a download click, and nothing goes to any third party.
First-party download count (no cookies) Yes — not consent-gated Count which campaign, link or page led to a download, and later which downloads led to sign-ups. When you open our download page, your browser's session storage gets a random visit code (amc-download-code), which is also added to the Windows installer link; your first download click adds a random click id (amc-download-click-id). Both are cleared when you close the tab. That first click sends one beacon to our own server (shares.omniscio.com) carrying the visit code, the click id, the campaign tags (utm_source, utm_medium, utm_campaign), the referring page — of which we keep only its site address — and whether you gave advertising consent, whatever your choice; the ad click ids, browser ids, user-agent and page address ride along only with advertising consent. We keep each record for about 180 days. If you then sign in to the App on Windows within 30 days, the App reads the visit code from the installer's download note and links the campaign tags and the channel they point to (for example "Google Ads") to your new account, once, whatever your consent choice; only the report to an ad platform needs your advertising consent. No third party receives any of this.
Social media No Social login / sharing widgets. We do not embed social-media widgets that set third-party cookies.
Web fonts (no cookies) No outside provider Load the typefaces the pages are set in. None — we serve them ourselves. Every typeface on these pages is hosted on our own domains (omniscio.com and docs.omniscio.com), so your browser fetches the font files from us and no outside provider receives your IP address, browser user-agent, or the page you were on. No cookie is set and nothing is stored on your device. See Section 5.

5. Third-party recipients and international transfers

Our marketing website loads Google Analytics, so Google receives the information that tool collects (such as your IP address, the pages you view, and a randomly-generated analytics identifier) and processes it under Google's own terms as an independent third party. Google is a US-based provider that may process this data in the United States or other countries.

Meta and Google Ads (advertising consent only). When we run Meta or Google ad campaigns, a visitor with advertising consent (Section 7) who clicks a download link is reported to that platform from the browser (the Meta Pixel and the Google Ads conversion tag). If that visitor later creates an Omniscio account, our server may also send Meta Platforms, Inc. a "signup" and "purchase" event through Meta's Conversions API, carrying a one-way hash of your account id and email address, Meta's own _fbp / _fbc browser identifiers, your browser's user-agent, the page you downloaded from and — for a purchase — its US-dollar amount. Meta processes it under its own terms as an independent third party, in the United States and other countries. We keep a record of each report for 90 days, and if you withdraw advertising consent before a report is sent, it is cancelled. Nothing is sent for a visitor without advertising consent, or for an existing customer who simply re-downloads the App.

The App's omniscio_web_token and omniscio_device_id cookies are first-party and are shared with no third party. shares.omniscio.com loads no third-party cookie technology; its one first-party __session cookie (Section 4) is shared with no one. These legal pages carry the same consent-gated analytics as the rest of our websites, so Google receives nothing from them unless your choice permits analytics — for any visitor, only after they press Accept.

Web fonts. Every page on this site — including this notice, the Privacy Policy, and the Subprocessors page — is set in typefaces we host ourselves, on omniscio.com and docs.omniscio.com. Your browser fetches the font files from our own servers, so no outside provider receives your IP address, your browser's user-agent, or the page you were viewing, and those requests never leave our hosting. No cookie is set and nothing is stored on your device. Because the fonts come from the same origin as the page, blocking third-party requests leaves the pages fully readable.

6. Other technologies

7. How you can control cookies

Strictly-necessary cookies. The omniscio_web_token cookie is required to keep you signed in to the web-access feature; if you block it, that feature will not work. You can end the session by signing out and clear the cookie through your browser's settings. The omniscio_device_id cookie is persistent (up to 400 days) — clearing it through your browser's settings simply makes that browser look like a new device to the App the next time you pair it, and the App mints a fresh random id.

Browser settings. Most browsers let you see, manage, block, and delete cookies and clear local storage (usually under Settings → Privacy). Blocking cookies may mean you need to sign in to the web-access feature again.

Google Analytics opt-out. You can opt out of Google Analytics across all websites by installing Google's opt-out browser add-on at https://tools.google.com/dlpage/gaoptout, or by blocking analytics/third-party cookies in your browser.

"Do Not Sell or Share My Personal Information." Because we enable Google Analytics ads-personalization (a "share" under California law), we provide a "Do Not Sell or Share My Personal Information" link in our website footer. Clicking it opts your browser out of the analytics/advertising sharing: Google Analytics and the advertising tags are turned off for that browser, the stored ad click ids and Meta's cookies are deleted, and any not-yet-sent report to Meta is cancelled. Your choice is stored in your browser.

Opt-out preference signals (Global Privacy Control). We honor recognized browser opt-out signals such as Global Privacy Control (GPC) as a valid request to opt out of the sale or sharing of information collected through cookies — when we detect a GPC signal on our website, Google Analytics and the advertising tags stay off for that browser, exactly as with the link above. We do not sell your personal information for money.

Consent gate. Non-essential cookies (Google Analytics, the Meta Pixel, the Google Ads conversion tag, and the ad click ids in omniscio_attr) all follow one consent decision per visit, applied through Google Consent Mode before any tag loads:

Withdrawing consent later (Decline, the Do-Not-Sell link, or turning on GPC) deletes the stored ad click ids and Meta's cookies from your browser, asks our server to forget the ad details recorded with your earlier download clicks, and cancels any not-yet-sent report to Meta. Your choice is remembered in your browser — in local storage and in two first-party choice cookies, omniscio-consent and omniscio-optout (up to 400 days, shared by omniscio.com and docs.omniscio.com so one answer covers both sites; they hold only your choice) — and applies until you clear it.

8. Relationship to our Privacy Policy

For more about how we collect, use, and share information — including your privacy rights and how to exercise them — see our Privacy Policy, which is the controlling description of our data practices; this notice adds cookie-specific detail. (Note: the Privacy Policy's statement that the App sets no tracking cookies remains accurate; this notice discloses the separate use of Google Analytics on the marketing website.)

9. Changes to this notice

We may update this Cookie Notice from time to time — for example, if we add or remove a cookie or a web-surface technology. Material changes are indicated by the "Last updated" date above and, where appropriate, additional notice.

10. Contact

Questions about this Cookie Notice? Contact us at legal@omniscio.com, Omniscio LLC, 5301 Terminal St, Charlotte, NC 28208.