Cookie Policy

Manus · agreement dated September 12, 2026 · Official agreement

Read the agreement

7 of 37 cards in Use & Processing

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.
Also annotated in the same passage (2)

Use & Processing · Company practice

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.

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.

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.