# Privacy Policy Draft privacy policy for Meltiply — what data the service processes, why, and who it is shared with. > **Draft — not yet in effect.** This policy has not been approved by Meltiply's owner or reviewed by legal counsel. It describes honestly what Meltiply processes today and why. Elements a final policy normally contains — the operating entity and controller identity, a privacy contact route, retention schedules, and jurisdiction-specific rights procedures — are identified in the text and will be completed before this document takes effect. ## Scope This policy is intended to cover the **Meltiply application** — the signed-in service for planning, composing, scheduling, and publishing social media content across connected channels, with backend synchronization for post performance and audience interactions — and, where relevant, this **public documentation site**. It does not cover third parties that have their own privacy policies — the social platforms you connect (currently TikTok, YouTube, Instagram, Facebook, and Threads), our payment provider **Polar**, or any site we do not operate. Their own policies govern information they receive. ## Who is responsible for your information The entity operating Meltiply — the controller of the information described here — has not yet been publicly identified. Rather than guess, this draft leaves that fact open; the operating entity's legal name and contact details will be stated when this policy takes effect. ## Information we process **Account information.** When you sign up we collect your name, email address, and a password credential, along with the verification records used to confirm your email and manage sign-in. **Session and technical data.** To keep you signed in and protect the service, we process technical session data such as your IP address and browser information. **Workspace information.** The workspaces you belong to, their names, your role in each, and the Brand Profiles grouping channels, media, and posts inside a workspace. **Connected platform data.** When you connect a social account, the platform shares the account identity you authorized — such as its display name and avatar — and the permissions you granted. Meltiply keeps the authorization needed to act on your behalf and tracks each connection's status and granted scopes so expired or revoked access surfaces clearly. **Your content.** Media you upload (files, titles, descriptions, tags, and properties like dimensions and duration), the posts you compose (captions, hashtags, and platform-specific options such as titles and visibility levels), and your scheduling choices. **Synced platform content.** For posts published through Meltiply we sync reported performance analytics — views, likes, comments, shares, reach, impressions, watch time — and the audience comments on those posts, including each comment author's name, avatar, and text, via backend platform synchronization. **Usage data.** How much your workspace uploads, publishes, stores, and requests during each usage period, so plan limits can be applied and monitored against plan quotas (see [Billing](/docs/billing)). **Billing data.** Your workspace's plan, subscription status, and renewal or cancellation dates, along with a reference to your customer record at our payment provider. Payment details go to **Polar**'s hosted checkout and billing portal under Polar's own privacy policy — Meltiply does not store your card number. **Operational records.** Records the service needs to run reliably — scheduled and delivered work, notifications from platforms and the payment provider, and abuse-prevention activity. ## Where information comes from Most information enters Meltiply directly from you (sign-up details, uploads, composed posts, settings), from platforms you connect (authorized account identities, synced analytics and comments), from Polar (subscription status), or is generated by the service itself (usage counters, connection statuses, operational records). ## How we use information - **Provide the service** — upload and store media, schedule and publish posts to your chosen platforms, sync analytics and comments, and deliver transactional emails such as sign-in and verification messages. - **Authenticate and secure accounts** — sign-in, sessions, and abuse prevention. - **Apply plan limits and billing** — measure period usage against plan limits and manage subscriptions through our payment provider. - **Operate and improve reliability** — monitor scheduled work and delivery so publishing completes and failures surface clearly. - **Meet legal obligations** — and enforce the [Terms of Service](/docs/terms). This draft describes the purposes the product serves today; product analytics based on social-platform reports and comments are backend capabilities, not visitor tracking. No visitor-measurement or advertising trackers are currently installed on public Meltiply sites. ## Public posts and private workspaces Publishing a post sends its content to the platform you selected, where it becomes content on that platform — visible according to the audience and privacy options you chose, and governed by the platform's own policies. Once delivered, it is outside Meltiply's control: changing or removing it happens on the platform itself, not inside Meltiply. Everything else in your workspace — drafts, media attachments, scheduled and queued posts, synced analytics and comments, billing state — is private to its members and is not published or publicly indexed by Meltiply. ## When we share information - **Social platforms you connect.** Publishing a post sends that content to the platform you selected; syncing retrieves analytics and comments from it. Each platform's own privacy policy applies to data it receives or provides. - **Polar**, our payment provider, processes subscription payments under its own privacy policy. - **Service providers** that help run the service — cloud infrastructure, database hosting, media storage, and transactional email delivery — process information on our behalf; provider terms will be described in the final version once verified. - **Legal and safety.** We may disclose information where required by law or where we believe it is necessary to protect the service, its users, or others. We have not yet adopted formal commitments about the sale of personal information or sharing data with third parties for their own marketing, so this draft states none. ## This documentation site The site you are reading is public and does not require a Meltiply account or sign-in. Its pages, its built-in search index, and any downloadable copies of the documentation are publicly accessible — treat anything published here as public. The public landing site and documentation do not add visitor analytics or advertising integrations, and the app does not add visitor measurement or advertising trackers. Optional visitor tracking and equivalent technologies are not used before explicit category consent. Hosting infrastructure may separately produce standard technical request records, which this draft does not describe. See [Cookies and storage](/docs/cookies) for current behavior. ## Device storage and cookies The app and public sites use essential sign-in, session, and security mechanisms, which remain active regardless of optional choices. The essential consent record remembers whether optional purposes were accepted or rejected. Optional functional preferences and recovery data are stored only after functional consent. There is no in-product control to reopen saved choices; browser site-data controls can reset the consent record. See [Cookies and storage](/docs/cookies) for the categories, known browser-storage keys, cleanup behavior, and retention periods. ## Retention and deletion We keep information for as long as your account and workspace need it to provide the service. The final version of this policy will set out formal retention periods for each category; this draft does not invent them. What the product does today: - Most workspace items remain until you remove them. Deleting a media asset or a draft is **permanent** — the confirmation dialogs state it cannot be undone, and there is no recovery path. - Deleting a Brand Profile removes the profile with the channels, assets, and posts it owns, and scheduled work on those channels stops. The backend retains soft-deleted Brand Profiles for 7 days before permanent purge; backend restore operations recover profile records, but its channels stay disconnected and its cancelled posts are not revived. An explicit deletion through the app is permanent and cannot be undone. - Disconnecting a channel on the [Channels](/docs/channels) page stops its scheduled and queued posts and ends Meltiply's use of that connection for publishing and syncing. It deletes nothing in Meltiply and does not revoke the authorization on the platform's side — revoke that in the platform's own settings; you can reconnect anytime. - None of these actions — deleting content, disconnecting a channel, or ending an account — removes content already published to a platform. Published posts cannot be deleted from inside Meltiply; remove them on the platform itself. ## Your choices and controls - **Disconnect channels** — remove a platform's connection from your workspace on the [Channels](/docs/channels) page; you can also revoke Meltiply's access on the platform itself. - **Manage content** — delete media assets, drafts, and Brand Profiles in the app; each confirmation describes consequences that can be permanent. - **Cookies and local storage** — choose optional purposes in the initial consent prompt; use browser site-data controls to reset a saved choice. [Cookies and storage](/docs/cookies) explains the known browser storage and reset behavior. Theme and reduced-motion controls remain available in the sidebar footer. - **Billing** — paid subscriptions are managed through Polar's hosted billing portal; plan limits and quotas are described in [Billing](/docs/billing). - **Profile and account data** — the app does not yet offer self-service controls for editing account profile data or requesting account deletion, and no in-product request route exists yet. Request handling will be described in the final version of this policy. ## Regional rights Depending on where you live, privacy laws may grant rights over your personal information — access, correction, deletion, export, or objection to certain processing. Which rights apply is jurisdiction-dependent: this draft claims compliance with no specific regime and grants no universal set of rights. No privacy request route or response procedure has been published yet, and no guaranteed response timeframe exists; how to exercise your rights will be described before this policy takes effect. ## International processing We have not yet documented where information is processed and hosted or which legal safeguards apply to cross-border transfers; the final version will state them once confirmed rather than guess. ## Children's privacy Meltiply is intended for people legally able to form a binding contract and is not directed at children. No specific minimum age is asserted; the threshold varies by jurisdiction and will be set in the final version. ## Security We use technical and organizational measures appropriate to the service — including access controls and protected storage for connected-platform authorizations — and work to protect data against loss and unauthorized access. This draft does not describe specific mechanisms or claim certifications. No method of transmission or storage is completely secure. ## Changes to this policy We may update this policy as the product and legal review progress; material changes will be posted on this page. How users will be notified will be decided before the policy takes effect. ## Contact The public Meltiply website is [meltiply.com](https://meltiply.com). A dedicated privacy contact route has not yet been established; it will be published with the final version of this policy. ## Related - [Terms of Service](/docs/terms) — the draft terms governing use of Meltiply. - [Channels](/docs/channels) — connecting, reconnecting, and disconnecting platform accounts. - [Billing](/docs/billing) — how plan limits and payments work.