Cookies and storage

This page describes the current behavior of Meltiply’s landing site, documentation, and app. It is a factual explanation, not legal advice, a compliance certification, or a guarantee about any particular legal regime. The Privacy Policy describes other information the service processes.

Your choiceCopy Anchor Link

A cookie notice appears until you make a choice. You can accept or reject optional purposes, choose categories separately, and reopen Cookie settings later to change your choice. Optional purposes are denied unless a valid choice allows them.

On the public sites, Cookie settings stays in the footer. In the app, it is an inline action in workspace Settings and the sign-in/sign-up forms, not a floating pill. Within the docs, navigating between guides keeps the notice and any unsaved category choices open without replaying its entrance. Saving a choice shows a brief confirmation that fades out before closing; guide navigation does not restart that deadline. Returning keyboard focus to the control preserves your position on the page. Device-requested reduced motion applies to these transitions.

The choice is stored in the essential meltiply-consent cookie for 180 days. It records the versioned choice and its expiry, including when you reject optional purposes. On production Meltiply sites, the choice is shared across eligible meltiply.com subdomains; preview or other hostnames may require a separate choice. An invalid or expired record does not allow optional storage or tracking.

Rejecting or withdrawing optional consent keeps the essential choice record but removes known optional first-party data on the current origin where the browser allows it. Other Meltiply origins clean up their known optional data when you next visit or return focus to them. Browser controls can also clear site data. These controls do not promise deletion of HttpOnly cookies or data controlled by another service.

Essential storageCopy Anchor Link

Sign-in, session, and security mechanisms needed to authenticate accounts and protect the service remain active regardless of optional choices. The meltiply-consent cookie is also retained so the site can remember whether you accepted or rejected optional purposes. These essential records are not visitor analytics or advertising trackers.

Functional preferencesCopy Anchor Link

Functional storage is optional and is used for convenience and recovery preferences. It is written only after you allow the functional category. Known examples include:

• The meltiply-theme cookie, which keeps the selected light or dark theme available across eligible Meltiply sites for up to one year.
• Origin-local storage keys meltiply.theme, meltiply.low-motion, meltiply.language, meltiply.recent-navigation, and meltiply.devbox for theme, motion, language, recent navigation, and developer-tool preferences.
• Origin-local storage prefixes meltiply.composer.v1.*, meltiply.upload.v1.*, and meltiply.upload.create.v1.* for in-progress post and upload recovery data.

Without functional consent, theme, motion, and language controls still work, but their choices are not remembered for later visits. An explicit theme choice follows links between the landing page, docs, and app, including preview sites, without granting consent or writing optional storage on an unconsented destination. The destination applies that choice before its first paint and preserves it through hydration and an initial rejection of optional cookies. Device-requested color scheme and reduced motion do not require storage. Posts saved on the server and active uploads remain product functionality; only supplemental browser-local recovery is optional.

The local preferences do not have a fixed expiry; withdrawing functional consent removes the known keys and prefixes. The app’s essential sign-in and security storage is not removed by that cleanup.

Analytics and marketingCopy Anchor Link

Analytics means measurement of visits and use of Meltiply’s sites. Marketing means advertising, campaign attribution, or remarketing. No visitor-analytics or marketing trackers are currently installed on the landing site, documentation, or app. Choosing either category does not load a vendor, script, or SDK that is not present.

The performance analytics and comments shown in the app are product features based on reports from social platforms connected to your workspace. They are not measurement of visits to Meltiply’s public sites, and changing cookie consent does not turn off those features.

Cookies and equivalent technologiesCopy Anchor Link

Cookie choices also govern equivalent optional browser storage and non-cookie tracking used for the same purpose; a technology is not exempt merely because it is not a cookie. Meltiply does not currently add visitor-analytics or advertising integrations, and optional tracking must remain off unless the relevant category is explicitly allowed. Hosting infrastructure may separately process standard technical request records as described in the Privacy Policy.

For the current privacy disclosures, see the Privacy Policy.