Cookie Policy

Manus · agreement dated September 12, 2026 · Official agreement

Read the agreement

18 of 37 cards in Data Access & Collection

Data Access & Collection · Context

"Cookies" here also means browser or device data, device identifiers and other software, including a listed web pixel

The policy says other technologies serve purposes similar to cookies, including data stored on the web browser or device, identifiers associated with the device, and other software, and it calls all of these "cookies" in this policy. The Cookie Table accordingly includes a web pixel, the Vector SiteID Pixel, which the table describes as using device fingerprint information and which has no cookie lifetime (TTL "N/A").

Supporting quotations

Other technologies, including data stored on your web browser or device, identifiers associated with your device, and other software, serve similar purposes.
In this policy, we refer to all of these technologies collectively as "cookies."
A web pixel that uses device fingerprint information

Qualifications & exceptions

  • Other technologies count under the label "cookies" because they "serve similar purposes" to cookies.

Not stated here

  • The policy does not say whether its preference options (cookie settings, advertising opt-out, Global Privacy Control) apply to non-cookie technologies such as the listed web pixel.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

Third-party cookies on the Sites are listed in the Cookie Table, which may change; cookies on other sites are outside it

The policy points to the Cookie Table for the third-party cookies used on the Sites. Butterfly Effect says it does its best to keep the table up to date but that the number and names of cookies, pixels and other technologies may change from time to time. The policy adds that when a user leaves the Sites (for example to complete a survey or a payment), the third-party websites visited may set their own cookies. Those cookies are governed by the third party's own policies, not this one, and are not in the Cookie Table.

Supporting quotations

What third-party cookies does Butterfly Effect use?
We do our best to keep this table up to date; however, the number and names of cookies, pixels, and other technologies may change from time to time.
Cookies on third-party websites (outside our control)
Those cookies are governed by the third party's own policies, not ours, and are not listed in our Cookie Table.

Qualifications & exceptions

  • Table kept up to date on a best-efforts basis only ("We do our best").
  • Cookies set on third-party websites a user visits after leaving the Sites are excluded from the table and from this policy.

Not stated here

  • The policy does not say how users are told when the table changes.
  • The survey and payment providers given as examples are not named.
Also annotated in the same passage (1)

Data Access & Collection · User right or choice

Cookie choices depend on applicable law; where law requires, prior consent is sought and non-essential cookies start off

The policy says that, depending on applicable law, a user may be able to choose which cookies are used. Where required by law, Butterfly Effect obtains the user's prior consent before setting non-essential cookies, and these cookies are turned off by default.

Supporting quotations

Depending on applicable law, you may be able to choose which cookies are used when using our Services.
Where required by law, we obtain your prior consent before setting non-essential cookies, and these cookies are turned off by default.

Qualifications & exceptions

  • Choice is available only "depending on applicable law" ("may be able").
  • Prior consent and the off-by-default setting apply "where required by law".

Not stated here

  • The policy does not say which locations or laws trigger prior consent.
  • The policy does not say how non-essential cookies are treated where law does not require consent.
  • Only "Strictly Necessary" is labelled in the policy; "non-essential" is not defined.

Data Access & Collection · Company commitment

The Global Privacy Control signal is honored where required by applicable law

Butterfly Effect says it honors the Global Privacy Control (GPC) signal where required by applicable law, listed as an opt-out preference signal option.

Supporting quotations

Opt-out preference signals: We honor the Global Privacy Control (GPC) signal where required by applicable law.

Qualifications & exceptions

  • Honored only "where required by applicable law".

Not stated here

  • The policy does not say where law requires this, or whether the signal is honored where law does not require it.

Data Access & Collection · Restriction or exception

Strictly Necessary cookies cannot be switched off in its systems; blocking them in a browser breaks parts of the site

The policy says cookies listed as "Strictly Necessary" are required for the Services to function and cannot be disabled. Under the Strictly Necessary Cookies heading in the Appendix it adds that these cookies are necessary for the website to function and cannot be switched off in Butterfly Effect's systems, and are usually only set in response to actions the user takes that amount to a request for services, such as setting privacy preferences, logging in or filling in forms. A user can set the browser to block or alert about these cookies, but doing so will cause some parts of the site not to work.

Supporting quotations

Cookies listed as "Strictly Necessary" are required for the Services to function and cannot be disabled.
Strictly Necessary Cookies
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions you take that amount to a request for services, such as setting your privacy preferences, logging in, or filling in forms.
You can set your browser to block or alert you about these cookies, but doing so will cause some parts of the site not to work.

Qualifications & exceptions

  • "Usually" only: the policy does not say these cookies are set only in response to user actions.
  • Browser blocking is possible but breaks parts of the site.

Not stated here

  • The policy does not itself say which rows of the Cookie Table are Strictly Necessary beyond placing the table under this heading.

Cross-references

Also annotated in the same passage (2)

Data Access & Collection · Context

The first Cookie Table, under Strictly Necessary, lists 36 cookies with source, sub-type, description and TTL

After the Strictly Necessary Cookies heading and its paragraph, the Appendix's first table lists 36 numbered cookies with columns for name, source, sub-type, description and TTL. Thirty are shown with source Manus; the others come from hCaptcha, Amplitude, Intercom and Iterable. The sub-types shown are Authentication, Security and Functional. No row carries "Strictly Necessary" as its sub-type, so the policy marks that status only through the table's position under the heading; it does not say which individual rows cannot be disabled.

Supporting quotations

Cookie Name Source Sub-Type Description TTL

Qualifications & exceptions

  • The Strictly Necessary status is indicated only by the heading and paragraph that precede the table; the table's own Sub-Type column uses Authentication, Security and Functional.

Not stated here

  • The policy does not say whether the rows from third-party sources (hCaptcha, Amplitude, Intercom, Iterable) are all among the cookies that "cannot be disabled".

Cross-references

Data Access & Collection · Company practice

Manus cookies store profile, subscription, usage, add-on, configuration and Facebook/Meta login data for 365 days

Six Manus cookies, each listed with a 365-day TTL and sub-type Functional, hold account-related information: usage_info (usage-related information for the user's session), subscriptions (the user's subscription status or plan details), bizAddonList (the list of business add-ons enabled for the user), UserService.userInfo (user profile information for the session), UserService.userClientConfig (user client configuration settings) and fb_userinfo (user information obtained via Facebook/Meta OAuth login).

Supporting quotations

7 usage_info Manus Functional Stores usage-related information for the user's session 365 days
9 subscriptions Manus Functional Stores the user's subscription status or plan details 365 days
21 bizAddonList Manus Functional Stores the list of business add-ons enabled for the user 365 days
22 UserService.userInfo Manus Functional Stores user profile information for the session 365 days
23 UserService.userClientConfig Manus Functional Stores user client configuration settings 365 days
30 fb_userinfo Manus Functional Stores user information obtained via Facebook/Meta OAuth login 365 days

Qualifications & exceptions

  • Source is Manus for all six rows; TTL 365 days; sub-type Functional.
  • fb_userinfo applies to users who sign in with Facebook/Meta OAuth.

Not stated here

  • The policy does not say which profile, usage or Facebook/Meta fields these cookies hold.

Data Access & Collection · Company practice

Amplitude sets two Functional cookies for feature rollout assignments and to prevent duplicate configuration events

The first table lists two cookies from Amplitude with sub-type Functional and a 365-day TTL: EXP_#### (stores feature rollout assignments so the user receives a stable, compatible version of site functionality) and EXP_sent_v2_#### (prevents duplicate delivery of feature configuration events). The #### in the names is a placeholder in the source. Amplitude also appears with analytics cookies in the second table.

Supporting quotations

33 EXP_#### Amplitude Functional Stores feature rollout assignments to ensure the user receives a stable, compatible version of site functionality 365 days
34 EXP_sent_v2_#### Amplitude Functional Prevents duplicate delivery of feature configuration events 365 days

Qualifications & exceptions

  • Source is Amplitude, not Manus; listed in the table that follows the Strictly Necessary heading.
  • Durations for third-party cookies are provider defaults at publication and may vary.

Not stated here

  • The policy does not say what data, if any, these cookies send to Amplitude, or whether they are among the cookies that "cannot be disabled".

Cross-references

Data Access & Collection · Company practice

Intercom sets cookies for in-app messaging and support chat; Iterable identifies the user for transactional messages

The first table lists Intercom cookies named "(various)" for in-app messaging and customer support chat, and iterableEndUserId from Iterable, which identifies the user for delivery of transactional service communications such as account notifications and security alerts. Both are labelled Functional with a 365-day TTL.

Supporting quotations

35 (various) Intercom Functional Cookies set by Intercom for in-app messaging and customer support chat 365 days
36 iterableEndUserId Iterable Functional Identifies the user for delivery of transactional service communications (e.g., account notifications, security alerts) 365 days

Qualifications & exceptions

  • Source is Intercom and Iterable, not Manus.
  • The Iterable description names transactional service communications, with account notifications and security alerts as examples.
  • Durations for third-party cookies are provider defaults at publication and may vary.

Not stated here

  • The Intercom cookie names are not listed ("(various)").
  • The policy does not say whether Iterable's identifier is used for anything beyond transactional service communications, or whether these cookies are among those that "cannot be disabled".

Cross-references

Data Access & Collection · Company practice

Amplitude analytics cookies track user interactions for 365 days and marketing campaign attribution for 90 days

Under the Analytics Cookies heading, the policy says analytics cookies count visits and traffic sources and show how visitors interact with the site. The second table lists two Amplitude cookies: AMP_#### (an analytics cookie for tracking user interactions, where #### is a dynamic project or API key, 365 days) and AMP_MKTG_#### (a marketing analytics cookie for campaign attribution, with the same placeholder, 90 days).

Supporting quotations

Analytics Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
37 AMP_#### Amplitude Amplitude analytics cookie for tracking user interactions (#### = dynamic project/API key) 365 days
38 AMP_MKTG_#### Amplitude Amplitude marketing analytics cookie for campaign attribution (#### = dynamic project/API key) 90 days

Qualifications & exceptions

  • Source is Amplitude, not Manus.
  • Durations for third-party cookies are provider defaults at publication and may vary.

Not stated here

  • The policy does not say what is recorded about "user interactions" or which campaigns are attributed.
Also annotated in the same passage (1)

Data Access & Collection · Context

The Advertising Cookies table lists 12 entries from ad, attribution and identity providers

The Advertising Cookies section has no description paragraph of its own, unlike the Analytics Cookies section; the general description of advertising cookies is in the purposes list earlier in the policy. Its table lists twelve numbered entries (numbers 40 to 51) with source, description and TTL, from Google Ads, Bing Ads, Meta Ads, TikTok Ads, Naver Ads, Adjust, Apple Search Ads and Vector.

Supporting quotations

Advertising Cookies

Qualifications & exceptions

  • Entries come from third-party sources; the policy says third-party durations are provider defaults at publication and may vary.

Not stated here

  • The section does not say whether these entries are the "non-essential" cookies for which the policy says prior consent is obtained where required by law.

Data Access & Collection · Company practice

Google Ads and Bing Ads cookies track ad conversions and efficiency, lasting 90 or 390 days

The table lists four entries from Google Ads and Bing Ads. Google Ads: _gcl_au (conversion tracking and ad efficiency, 90 days) and the click identifiers gclid, gbraid and wbraid (same description, 90 days). Bing Ads: _uetvid (stores a unique visitor identifier for cross-session ad conversion tracking, 390 days) and msclkid (conversion tracking and ad efficiency, 90 days).

Supporting quotations

40 _gcl_au Google Ads Conversion tracking and ad efficiency 90 days
41 _uetvid Bing Ads Stores a unique visitor identifier for cross-session ad conversion tracking 390 days
47 gclid, gbraid, wbraid Google Ads Conversion tracking and ad efficiency 90 days
48 msclkid Bing Ads Conversion tracking and ad efficiency 90 days

Qualifications & exceptions

  • Sources are Google Ads and Bing Ads, not Manus.
  • Durations for third-party cookies are provider defaults at publication and may vary.

Not stated here

  • The policy does not say what data Google or Microsoft receive or how they use it.

Data Access & Collection · Company practice

Meta Ads and TikTok Ads cookies support ad targeting, real-time bidding and conversion tracking

The table lists three entries. Meta Ads: _fbp (advertisement targeting and real-time bidding, 90 days) and fbclid (conversion tracking and ad efficiency, 90 days). TikTok Ads: _ttp (visitor identification for TikTok ad conversion tracking, 390 days). _fbp is the only entry in the advertising table whose description mentions targeting and real-time bidding.

Supporting quotations

42 _fbp Meta Ads Advertisement targeting and real-time bidding 90 days
49 fbclid Meta Ads Conversion tracking and ad efficiency 90 days
43 _ttp TikTok Ads Visitor identification for TikTok ad conversion tracking 390 days

Qualifications & exceptions

  • Sources are Meta Ads and TikTok Ads, not Manus.
  • Durations for third-party cookies are provider defaults at publication and may vary.

Not stated here

  • The policy does not say what data is used for targeting or bidding, or what Meta or TikTok receive.

Data Access & Collection · Company practice

Naver Ads, Adjust and Apple Search Ads entries identify visitors or measure ad clicks and conversions

The table lists four entries. Naver Ads: NVADID (visitor identification for Naver ad conversion tracking, 180 days) and NaPm (ad efficiency, 30 days). Adjust: adjust_web_uuid (visitor identification for mobile attribution and conversion tracking, 365 days). Apple Search Ads: Private Click Measurement, described as a browser-level API for measuring ad clicks and conversions (365 days).

Supporting quotations

44 NVADID Naver Ads Visitor identification for Naver ad conversion tracking 180 days
50 NaPm Naver Ads Ad efficiency 30 days
45 adjust_web_uuid Adjust Visitor identification for mobile attribution and conversion tracking 365 days
46 Private Click Measurement Apple Search Ads Browser-level API for measuring ad clicks and conversions 365 days

Qualifications & exceptions

  • Sources are Naver Ads, Adjust and Apple Search Ads, not Manus.
  • Durations for third-party cookies are provider defaults at publication and may vary.
  • The Apple entry is described as a browser-level API rather than a cookie, and is listed in the table with a 365-day TTL.

Not stated here

  • The policy does not say what data these providers receive or how they use it.