At a glance
Cookies we set
- __Host-mr_session — Main Revenue sign-in session. Secure, HTTP-only, same-site. Lasts 12 hours and ends after 30 minutes of inactivity.
- __Host-mai_admin — a signed session for Main staff on the internal admin pages. Never set for customers or visitors.
- Consumer tools: no cookies. Sign-in uses Firebase Authentication, which keeps your session in your browser’s IndexedDB (or localStorage when IndexedDB is unavailable), not in a cookie.
Browser storage: Main AI consumer tools
- Your sign-in session (Firebase Authentication, IndexedDB or localStorage).
- Documents you open, their extracted text and their analyses, so they are there after a refresh. When you sign out, Main AI clears the documents and analyses it stored in that browser for your account. If you use the tools without signing in, this stays until you clear your browser storage.
- Interface preferences: theme, layout, dismissed tips and feature settings.
- mainai_share_name — on shared-report pages, the display name you typed for comments.
- mainai.session.v1 — a random id kept in the tab’s session storage, used only to count usage steps (below). It is not tied to your account and disappears when the tab closes.
- mainai.attrib.v1 — on the free checker pages only, and only when the link you arrived on named a checker or carried a campaign or partner code: that code and the referring page, so a later sign-up can be credited to the right page. No name, email or document content.
Browser storage: Main Revenue
- Your last-used organization and staff-workspace state in the application.
- Your answers on /start, kept in that browser tab while you fill the form (never your password).
- An order reference so you can finish checkout, and an Ask Main conversation id for the tab.
Usage counts without cookies
Both products count page views and a few product steps in our own database, without a cookie and without a third party. A usage record holds the step name, the page path (no query string), the random tab id above, whether you were signed in or on a paid plan, the document type if known, and the checker or campaign code and referring page from the link you arrived on. It never holds your IP address, browser details, name, email address, file name or document text. Main Revenue keeps the same kind of counts, with your organization for steps inside its application, and deletes them with the organization’s data. The counts are shown to Main staff as daily totals to see where people get stuck.
You can turn the consumer-tool counts off for this browser. The switch below sets one flag in your browser’s storage and nothing else; clearing site data resets it.
Third parties
- Stripe sets cookies on its own checkout and billing pages (checkout.stripe.com). Those pages are Stripe’s, under Stripe’s cookie policy; card details are entered there and never reach Main.
- Google handles “Continue with Google” sign-in on its own pages, under Google’s policies. Firebase Authentication (also Google) is called to sign you in and refresh your session.
- The consumer dashboard loads one open-source document-rendering library from the jsDelivr CDN. Loading a file from a CDN sends your IP address to that CDN, as any web request does; it sets no cookies on mainai.live.
- No advertising, analytics or social-media script from any third party loads on any page of mainai.live.
Service worker cache
The consumer tools register a service worker that caches static files (scripts, styles, icons) for speed and offline use. It stores no personal data and no documents.
Questions and requests
Questions about cookies or storage: mainaihelp@gmail.com, or by mail to Main AI LLC, PO Box 3, Brooklyn, NY 11218. To delete your data, see the data deletion page. The privacy policies (consumer tools, Main Revenue) describe what we collect beyond the browser.

