This policy covers cookies on websites and services operated by Butterfly Effect and its affiliates, including Manus
Butterfly Effect Pte. Ltd. says it operates the Manus platform at manus.im. The policy explains how and when it uses cookies and similar technologies on the websites and services that Butterfly Effect and its corporate affiliates operate, together called the "Sites". The document shows a "Last Updated" date of September 12, 2026 and does not give a separate effective date or mention a successor version.
Supporting quotations
Last Updated: September 12, 2026
Butterfly Effect Pte. Ltd. ("Butterfly Effect", "we", "us", or "our") operates the Manus platform (manus.im).
This Cookie Policy explains how and when we use cookies and similar technologies on the websites and services operated by Butterfly Effect and its corporate affiliates (collectively, the "Sites").
Qualifications & exceptions
Reaches websites and services operated by Butterfly Effect and its corporate affiliates, not only manus.im.
Not stated here
The corporate affiliates are not named in this document.
The document states no region, user group or product limit.
The policy defines "Sites" but later also uses "Services", which it does not define.
Capitalised terms not defined here take their meaning from the separate Privacy Policy
The policy says capitalised terms it does not define have the meanings given in Butterfly Effect's Privacy Policy, which it says also has more detail on data collection and use. The Privacy Policy is a separate document that this analysis does not include, so what it says about cookie data is not described here.
Supporting quotations
Capitalised terms not defined in this policy have the meanings set forth in our Privacy Policy, which also includes additional details about our data collection and use practices.
Qualifications & exceptions
Applies only to capitalised terms this policy leaves undefined.
Not stated here
The text of the Privacy Policy is not part of this source; its additional details and definitions are unknown here.
Session cookies last until the browser closes; persistent cookies stay until deleted or expired
The policy describes cookies as small text files placed on a device to store information, and as used to store and receive identifiers and other information on computers, phones and other devices. It says session-based cookies last only while the browser is open and are deleted automatically when it closes. Persistent cookies remain on the device until the user or the browser deletes them, or until they expire.
Supporting quotations
Cookies are small text files placed on your device to store information.
Session-based cookies last only while your browser is open and are automatically deleted when you close it.
Persistent cookies remain on your device until you or your browser delete them, or until they expire.
Qualifications & exceptions
Session-based and persistent cookies are described as two types; the type of each listed cookie is not marked except by its TTL entry.
Not stated here
Which listed cookies are session-based is not stated; only one table entry (the hCaptcha _iidt cookie) lists its TTL as "Session".
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.
Cookies help show signed-in users the right information and personalise their experience
The policy lists authentication as a purpose of cookies. If the user is signed in to the Services, cookies help Butterfly Effect show the right information and personalise the experience.
Supporting quotations
We use cookies for the following purposes:
Authentication: If you are signed in to the Services, cookies help us show you the right information and personalise your experience.
Qualifications & exceptions
Applies when the user is signed in to the Services.
Not stated here
"Services" is not defined in this document, so which products are covered is not stated.
Security & Safeguards · Company practice
Cookies enable security features and help detect malicious activity
The policy lists security as a purpose of cookies. Butterfly Effect uses cookies to enable and support security features and to detect malicious activity.
Supporting quotations
Security: We use cookies to enable and support security features and to detect malicious activity.
Not stated here
The policy does not say what data these cookies collect or how detection works.
Use & Processing · Company practice
Cookies remember language and communication preferences and can support forms, features, insights and customised content
The policy lists preferences, features and services as a purpose. Cookies remember which language the user prefers and the user's communication preferences. They can also help the user fill out forms more easily and provide the user with features, insights and customised content.
Supporting quotations
Cookies remember which language you prefer and what your communication preferences are. They can also help you fill out forms more easily and provide you with features, insights, and customised content.
Qualifications & exceptions
Form help, features, insights and customised content are described as things cookies "can" do, not as something every cookie does.
Not stated here
The policy does not say what "insights" or "customised content" are based on, or whether they rely on browsing or usage data.
Use & Processing · Company practice
Cookies measure site performance, count visits and traffic sources, and support product research
The policy lists performance and analytics as a purpose. Cookies help Butterfly Effect understand how well the Sites and Services perform, and it also uses them to understand, improve and research its products, features and services. The Appendix's Analytics Cookies description says these cookies allow it to count visits and traffic sources so it can measure and improve the site's performance, understand how visitors interact with the site, and identify areas for improvement.
Supporting quotations
Performance and Analytics: Cookies help us understand how well our Sites and Services perform. We also use cookies to understand, improve, and research our products, features, and services
Analytics Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors interact with our site and allow us to measure traffic and identify areas for improvement.
Qualifications & exceptions
The Appendix description speaks of "our site" and visitors; the purpose list also reaches products, features and services.
Not stated here
The policy does not describe what visitor data analytics cookies collect beyond counting visits and traffic sources, or how the third-party analytics providers named in the table use it.
Cookies are also used to create logs and record access from different devices
Within the performance and analytics purpose, the policy says Butterfly Effect also uses cookies to create logs and to record when a user accesses the Sites and Services from different devices.
Supporting quotations
including to create logs and record when you access our Sites and Services from different devices.
Qualifications & exceptions
Stated as part of the performance and analytics purpose.
Not stated here
The policy does not say how access from different devices is matched to one user, what the logs contain or how long they are kept.
Advertising cookies and similar technologies target ads, limit repeated ads and attribute conversions
The policy lists advertising and personalisation as a purpose. These cookies and similar technologies help deliver more relevant advertisements, prevent the same ad from being shown repeatedly and improve campaign effectiveness. They may store or reference advertising click identifiers to attribute conversions and optimise performance.
Supporting quotations
These cookies and similar technologies help deliver more relevant advertisements, prevent the same ad from being shown repeatedly, and improve campaign effectiveness.
They may store or reference advertising click identifiers to attribute conversions and optimise performance.
Qualifications & exceptions
Click identifiers are something these cookies "may" store or reference, not a stated certainty.
Not stated here
This block does not say what data is shared with advertising providers or what the advertisements are based on.
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.
Listed lifetimes of third-party cookies are provider defaults at publication and may vary
For cookies set by third-party services, the durations in the Cookie Table reflect each provider's default settings at the time of publication and may vary. For the most current information the policy tells users to refer to each provider's own cookie policy.
Supporting quotations
Where cookies are set by third-party services, the durations listed below reflect the provider's default settings at the time of publication and may vary. For the most current information, please refer to each provider's own cookie policy.
Qualifications & exceptions
Applies to cookies set by third-party services, not to those the table lists with source "Manus".
Not stated here
The providers' own cookie policies are not supplied here, and the policy does not say which durations differ.
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 · User right or choice
Cookie settings are reachable from a footer "Manage Cookies" link or account settings, where available
As one of the options for managing preferences "where applicable", the policy points to cookie settings. Where available, a user can reach cookie preferences through the "Manage Cookies" link in the footer of the Manus website or through account settings.
Supporting quotations
You can manage your preferences through one of the following options where applicable:
Where available, you can access cookie preferences via the "Manage Cookies" link in the footer of our website or through your account settings.
Qualifications & exceptions
Offered "where applicable" and "where available".
Not stated here
The policy does not say where the setting is unavailable or which cookies it can change.
Use & Processing · User right or choice
Users can opt out of targeted advertising through the "Ads about Manus" setting, where available
Where available, a user can opt out of targeted advertising at any time through the "Ads about Manus" setting in account settings. Depending on location, the setting may also be reached through a "Your Privacy Choices" link in the website footer.
Supporting quotations
Where available, you can opt out of targeted advertising at any time through this setting in your account settings.
Depending on your location, this setting may also be accessible via the "Your Privacy Choices" link in our website footer.
Qualifications & exceptions
Offered "where available".
The footer link depends on the user's location.
Not stated here
The policy does not say whether the opt-out stops the advertising cookies in the Cookie Table from being set or only changes ad targeting.
The policy does not say which locations get the footer link.
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.
Account & Service Control · Restriction or exception
Changing cookie or advertising preferences may affect availability or functionality of the Services
The policy warns that changes to a user's cookie or advertising preferences may affect the availability or functionality of the Services.
Supporting quotations
Please note that changes to your cookie or advertising preferences may affect the availability or functionality of the Services.
Qualifications & exceptions
Stated as something that "may" happen.
Not stated here
The policy does not say which features are affected by which preference.
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
contrast (model-proposed): Amplitude sets two Functional cookies for feature rollout assignments and to prevent duplicate configuration events — The policy says cookies listed as "Strictly Necessary" cannot be disabled, and places the first Cookie Table under that heading. That table includes Amplitude feature-rollout cookies that its own Sub-Type column calls Functional, so which listed third-party cookies are covered by "cannot be disabled" is not clear from the text. The policy does not resolve this.
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".
Manus sets cookies that record a successful login and keep sign-in sessions, lasting 90 to 365 days
The table lists these Manus cookies for sign-in and sessions: login_success (indicates a successful login event, 365 days), oauth_session (maintains the OAuth authentication session, 90 days) and session_id (unique identifier for the user's active session, 90 days). It also lists manus_help_center_token, described as an authentication token for accessing the Manus Help Center (365 days), which the table labels Functional.
Supporting quotations
2 login_success Manus Authentication Indicates a successful login event 365 days
5 oauth_session Manus Authentication Maintains the OAuth authentication session 90 days
6 session_id Manus Authentication Unique identifier for the user's active session 90 days
25 manus_help_center_token Manus Functional Authentication token for accessing the Manus Help Center 365 days
Qualifications & exceptions
Source is Manus for all four rows.
Sub-type is Authentication for the first three and Functional for manus_help_center_token.
Not stated here
The policy does not explain how the 90-day or 365-day lifetimes relate to its earlier description of session-based cookies, which last only while the browser is open.
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
Manus sets client_id_v2, a unique client identifier for the user's browser, for 365 days
The table lists client_id_v2 (source Manus, sub-type Functional) as a unique client identifier, version 2, for the user's browser, with a TTL of 365 days.
Supporting quotations
20 client_id_v2 Manus Functional Unique client identifier (version 2) for the user's browser 365 days
Qualifications & exceptions
Source is Manus; listed as Functional; TTL 365 days.
Not stated here
The policy does not say what the identifier is used for or whether it is linked to an account or shared with other parties.
Use & Processing · Company practice
Manus cookies store language, theme, interface state and input-box drafts for 365 days
Five Manus cookies, each Functional with a 365-day TTL, store preferences and interface state: locale (preferred language or locale), manus-theme (selected UI theme, for example light or dark), session_list_unpinned (the unpinned state of the session list), persist:root (root key for persisted application state) and input_box_draft_list (draft content from the input box, for session persistence). A sixth, sessionsSize, stores the number of active sessions.
Supporting quotations
1 locale Manus Functional Stores the user's preferred language/locale setting 365 days
3 manus-theme Manus Functional Stores the user's selected UI theme (e.g., light/dark mode) 365 days
4 session_list_unpinned Manus Functional Tracks the unpinned state of the session list in the UI 365 days
14 persist:root Manus Functional Root key for persisted application state (Redux/state management) 365 days
17 input_box_draft_list Manus Functional Stores draft content from the input box for session persistence 365 days
13 sessionsSize Manus Functional Stores the number of active sessions 365 days
Qualifications & exceptions
Source is Manus; sub-type Functional; TTL 365 days.
Not stated here
The policy does not say how much of the draft input is held in input_box_draft_list or where it is stored beyond the cookie.
Use & Processing · Company practice
Manus cookies record which dialogs, guides, notifications and onboarding steps a user has seen, for 365 days
Ten Manus cookies, each Functional with a 365-day TTL, record interface and onboarding state: task_finished (whether a specific task has been completed), spaceDeploymentGuideLastShowSession (the last session in which the Space deployment guide was shown), showed_daily_free_credit_dialog (whether the daily free credit dialog was displayed), showedSharePopover (whether the share popover was displayed), latestNotificationId (the most recent notification viewed), invitation_code_max_used (whether the invitation code usage limit has been reached), first_entry (triggers the required first-time onboarding flow to enable core service functionality), credit_animate_time (the timestamp of the last credit animation display), activity_entry_flag (prevents repeated display of feature-specific onboarding dialogs) and cm_done (flags completion of a specific configuration or onboarding step).
Supporting quotations
8 task_finished Manus Functional Flags whether a specific task has been completed 365 days
10 spaceDeploymentGuideLastShowSession Manus Functional Tracks the last session in which the Space deployment guide was shown 365 days
11 showed_daily_free_credit_dialog Manus Functional Flags whether the daily free credit dialog has been displayed 365 days
12 showedSharePopover Manus Functional Flags whether the share popover has been displayed 365 days
15 latestNotificationId Manus Functional Stores the ID of the most recent notification viewed 365 days
16 invitation_code_max_used Manus Functional Tracks whether the invitation code usage limit has been reached 365 days
18 first_entry Manus Functional Triggers the required first-time onboarding flow to enable core service functionality 365 days
19 credit_animate_time Manus Functional Stores the timestamp of the last credit animation display 365 days
24 activity_entry_flag Manus Functional Prevents repeated display of feature-specific onboarding dialogs 365 days
26 cm_done Manus Functional Flags completion of a specific configuration or onboarding step 365 days
Qualifications & exceptions
Source is Manus; sub-type Functional; TTL 365 days.
Not stated here
The policy does not say what "specific" task or configuration step task_finished and cm_done refer to.
Use & Processing · Company practice
Manus cookies keep homepage layout, Japanese-locale routing and login-page presentation consistent for 365 days
Three Manus cookies, each Functional with a 365-day TTL, support page presentation: homepage_version (ensures a consistent homepage layout across the user's browsing session), ja_home_entry (tracks the entry point for Japanese-locale homepage routing) and login_page_experiment (maintains consistent login page presentation to prevent user confusion during authentication).
Supporting quotations
27 homepage_version Manus Functional Ensures a consistent homepage layout across the user's browsing session 365 days
28 ja_home_entry Manus Functional Tracks the entry point for Japanese-locale homepage routing 365 days
29 login_page_experiment Manus Functional Maintains consistent login page presentation to prevent user confusion during authentication 365 days
Qualifications & exceptions
Source is Manus; sub-type Functional; TTL 365 days.
Not stated here
The policy does not describe what experiments or variants these cookies relate to beyond the descriptions given.
Security & Safeguards · Company practice
hCaptcha sets a device identifier and a visitor identifier token used for bot detection and verification
The table lists two cookies from hCaptcha with sub-type Security: _iidt, a device identifier used by hCaptcha for bot detection (TTL Session), and _vid_t, a visitor identifier token used by hCaptcha for verification (TTL 365 days).
Supporting quotations
31 _iidt hCaptcha Security Device identifier used by hCaptcha for bot detection Session
32 _vid_t hCaptcha Security Visitor identifier token used by hCaptcha for verification 365 days
Qualifications & exceptions
Source is hCaptcha, not Manus.
_iidt is listed as Session; _vid_t as 365 days.
Under the policy's own note, durations for third-party cookies are provider defaults at publication and may vary.
Not stated here
hCaptcha's own handling of these identifiers is not described in this policy, and hCaptcha's policy is not supplied.
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
contrast (model-proposed): 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" cannot be disabled, and places the first Cookie Table under that heading. That table includes Amplitude feature-rollout cookies that its own Sub-Type column calls Functional, so which listed third-party cookies are covered by "cannot be disabled" is not clear from the text. The policy does not resolve this.
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".
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.
Tapfiliate sets tap_vid to identify affiliate referrals and track conversions for 90 days
The second table, under the Analytics Cookies heading, lists tap_vid from Tapfiliate, described as affiliate referral identification and conversion tracking, with a TTL of 90 days.
Supporting quotations
39 tap_vid Tapfiliate Affiliate referral identification and conversion tracking 90 days
Qualifications & exceptions
Source is Tapfiliate, not Manus; durations for third-party cookies are provider defaults at publication and may vary.
Not stated here
The policy does not describe the affiliate program or who receives referral and conversion data.
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.
Linking & Identification · Company practice
The Vector SiteID Pixel uses device fingerprint information to match visitors to an identity graph; it has no cookie TTL
The table lists the Vector SiteID Pixel from Vector as a web pixel that uses device fingerprint information to determine whether a website visitor matches Vector's pre-existing, privacy-sourced business-contact identity graph. Its TTL is "N/A — web pixel", and the entry adds that Vector states its site de-anonymization service does not rely on third-party cookies.
Supporting quotations
A web pixel that uses device fingerprint information to determine whether a website visitor matches Vector’s pre-existing, privacy-sourced business-contact identity graph.
N/A — web pixel; Vector states that its site de-anonymization service does not rely on third-party cookies.
Qualifications & exceptions
The statement about third-party cookies is attributed to Vector ("Vector states"), not made by Manus.
The match is against Vector's own identity graph, described as pre-existing and privacy-sourced.
Not stated here
The policy does not say what visitor data is sent to Vector, or what Manus receives or does with the match result.
The policy does not say whether the cookie settings, the advertising opt-out or the Global Privacy Control signal apply to this pixel.
The policy does not say what "privacy-sourced" means or which visitors are matched.
Data Access & Collection · Restriction or exception
The consent tools apply only to cookies set on the Sites, not to cookies set by third-party websites visited afterwards
The policy says 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. It says those cookies are governed by the third party's own policies and that its consent tools apply only to cookies set on the Sites.
Supporting quotations
Cookies on third-party websites (outside our control)
When you leave our Sites (for example, to complete a survey or a payment), you may visit third-party websites that set their own cookies.
Our consent tools apply only to cookies set on our Sites.
Qualifications & exceptions
Limited to cookies set on the Sites; cookies set on third-party websites after leaving the Sites are excluded.
Not stated here
The policy does not say which tools "our consent tools" covers, for example whether it means cookie settings, the advertising opt-out or the Global Privacy Control signal.