MogiuBack to mogiu.com

Legal

Cookie Notice

Last updated August 24, 2026

Everything Mogiu stores in your browser, and everything the third-party features embedded in our pages store in theirs. There are no analytics, advertising or session-recording trackers on this site.

01

In short

  • We set a small number of cookies that exist only to keep you signed in. Without them the app cannot work.
  • We use your browser’s local storage for your session token and interface preferences — language, layout, saved filters.
  • We run no analytics, advertising, attribution or session-replay software. Nothing on this site profiles you or follows you to other sites.
  • Two embedded third-party features set their own cookies: Google One Tap on the brand login page, and the Cal.com booking widget on our marketing page.
02

Cookies we set

CookiePurposeLifetime
business.session_tokenKeeps a brand user signed in. Set by our authentication server, HTTP-only, so scripts cannot read it.30 days
creator.session_tokenKeeps a creator signed in on mogiu.com/creator. HTTP-only.30 days

Both are strictly necessary: they are the session itself. On secure connections they carry the Secure prefix in their name. We set no other cookies of our own — no preference cookie, no analytics cookie, no advertising cookie.

03

Browser storage

Alongside cookies we use your browser’s local storage. It stays on your device and is never sent anywhere except where noted.

KeyWhat it holds
auth-tokenThe signed-in brand user’s session and access token. This is what authenticates each request to our API.
mogiu.langWhether you chose English or Chinese on the marketing page.
themeYour light or dark appearance preference.
layout-ui-stateInterface preferences inside the app — navigation collapsed, assistant panel open, panel width.
campaign-creator-saved-filtersFilter presets a brand user saved for their creator lists.
ai-chat-thread-id, ai-chat-thread-v3Which assistant conversation to reopen, and a local copy of its transcript so a page reload does not lose it.

Clearing site data in your browser removes all of these. Doing so signs you out and resets those preferences; nothing else is lost.

04

Third-party cookies on our pages

Google One Tap — brand login page only

The sign-in page for brands offers Google One Tap. Google’s script sets a g_state cookie recording that you dismissed the prompt, so it is not shown again immediately, and Google reads its own account cookies in its own context to know which account to offer. This runs only on the login page, and only Google can read those cookies. See Google’s privacy policy.

Cal.com — marketing page only

The Book a demo button on our marketing page loads Cal.com’s booking widget, which sets its own cookies in Cal.com’s context to run the booking flow. Anything you type into that widget — your name, email and booking notes — goes to Cal.com. See Cal.com’s privacy policy.

If you would rather neither of these loaded, block third-party scripts for this site in your browser or an extension. The rest of the site works without them; you would sign in with email instead of One Tap, and book a demo by emailing us.

05

Other requests your browser makes

Some resources load from other hosts without setting cookies. Those hosts still see your IP address and browser, as they must to serve the file. We send no referrer information with these requests.

  • Google Fonts — our typefaces load from fonts.googleapis.com and fonts.gstatic.com on every page.
  • Unsplash — a handful of stock portraits used in the illustration on our marketing page.
  • Media hosts — inside the app, creator avatars and post thumbnails load from our own storage and, in some cases, directly from the social platform’s image CDN. Opening a YouTube preview loads YouTube’s player, which sets YouTube’s cookies in that frame.
06

Controlling cookies

Every browser lets you view, block and delete cookies and site data, usually under Privacy settings. Because our own cookies are strictly necessary, blocking them signs you out and prevents you signing back in — but blocking third-party cookies, or blocking them for the two embeds above, does not stop the rest of the site working.

The cookies we set ourselves are strictly necessary and do not require consent. The two third-party embeds described above set their own cookies; if you are somewhere those require your consent and you would rather they did not load, block third-party scripts for this site — nothing else breaks. We run no analytics or advertising cookies at all, and if we ever add any we will ask for your consent first and update this page.

07

Contact

Questions about this notice go to hello@zalify.com. How we handle personal data more generally is set out in the Privacy Policy.