Skip to content

Privacy Policy

How Melvu collects, uses and protects your personal data, and the rights you have under the GDPR.

Last updated


1. Who we are (data controller)

Melvu is operated by a sole trader trading as "Ultra", established in Portugal (the "operator", "we", "us"). We are the controller of the personal data described below.

  • Contact, privacy and Data Protection Officer (DPO): [email protected]
  • Postal address: on request - [email protected]
  • Governing law: Portugal / European Union (GDPR - Regulation (EU) 2016/679).

2. Data we collect

  • Account data - your email address and username, stored in our Supabase profiles table when you create an account.
  • Waitlist data (historical) - the product waitlist closed in September 2026 and collects nothing new. Records that remain hold your email address and, if you arrived through a valid creator link, that creator's normalized username.
  • Network data - our servers and infrastructure proxies necessarily receive your IP while handling a connection and may retain ordinary security/access logs under the operator's retention policy. Melvu monitoring never writes raw IPs to its application database or audit trail; a manual network ban persists only a server-keyed, non-reversible HMAC fingerprint.
  • Traffic statistics - our web server already logs each request it handles. We read those logs on our own server to count page views, downloads, countries and visitors. To count visitors, each IP address is turned into a one-way hash using a secret key held only in server memory and replaced when the server restarts, combined with the date, so the same visitor gets a different hash each day. The hash is kept only in server memory, for at most about 31 days, and is never written to disk or shown to anyone. No raw IP address is stored for statistics, and we use no analytics cookies and no third-party analytics service.
  • Billing data - when you subscribe or buy Lifetime, payment details are processed by Stripe. We receive limited metadata (payment identifiers and status, plan, card brand and last four digits, invoices) and record your checkout acknowledgements: the version of the Terms you accepted and when. Records for existing Founder's Edition purchases also contain your account identifier, email, numbered badge, checkout acknowledgements and purchase/refund history. We never see or store full card numbers.
  • Referral data - if you arrive through a partner link, the partner code and the time you arrived, kept in the melvu_ref cookie (see the Cookies Policy). When the referral is linked to your account, we record which partner referred you, when, and the payments that earn that partner a commission. Partners see only the dates and amounts of referred payments, never your name or email address.
  • Discord account link - if you link Discord from your account, your Discord user ID and the community-server role granted for your plan. You can unlink it at any time.
  • Image generation - when an agent in Melvu generates an image, the prompt and any reference images you supply, the generated image, and the credits it used.
  • Device and session data - for each device where the desktop app signs in to your account: a device identifier, platform, app version, and when it signed in and was last seen. You can review these devices and sign them out from your account dashboard.
  • Retired cloud-sync data - accounts that previously used the original app may still have end-to-end encrypted legacy blobs pending deletion. The operator does not hold the encryption keys and cannot read this content.
  • Melvu entitlement data - we check your account plan, plan expiry and, where applicable, Lifetime access, Team membership and the Team owner's current plan to decide whether you can use Melvu.
  • Melvu operational metadata - enrolled device identifiers and public keys, live process/session identifiers, app/platform/version/channel details, bounded aggregate run/tool/error/restart/latency counters, security nonces, installer-ticket redemption, configuration-lease and activation/failure receipts, and timestamps. Operational endpoints do not receive your prompts, chats, file paths, source files, URLs, keystrokes, screenshots or other local workspace content.

3. Why we use it and legal bases (Art. 6 GDPR)

  • Providing the account and the service - performance of our contract with you (Art. 6(1)(b)).
  • Processing payments and managing subscriptions and Lifetime purchases - performance of contract (Art. 6(1)(b)) and our legal obligations, e.g. tax/accounting (Art. 6(1)(c)).
  • Sending transactional email (confirmations, password resets, billing notices) - performance of contract (Art. 6(1)(b)).
  • Abuse prevention, security, rate-limiting and privacy-safe operational monitoring - our legitimate interests in keeping the service reliable and secure (Art. 6(1)(f)).
  • Traffic statistics from our own server logs - our legitimate interest in operating the site and understanding how it is used (Art. 6(1)(f)).
  • Referral attribution and the referral discount, including the melvu_ref cookie - our legitimate interest in crediting partners and giving you the discount their link offers (Art. 6(1)(f)).
  • Showing and signing out the devices signed in to your account - performance of contract (Art. 6(1)(b)) and our legitimate interest in keeping your account secure (Art. 6(1)(f)).
  • Product news and promotions - your consent (Art. 6(1)(a)), given as a separate optional choice and confirmed by email. You can unsubscribe at any time.
  • Historical waitlist records and their creator attribution - kept from before the waitlist closed, on the basis of our legitimate interest in honoring creator referral agreements (Art. 6(1)(f)); nothing new is added.
  • Linking your Discord account and granting your plan's role - performance of contract (Art. 6(1)(b)), at your request.
  • Generating images you ask for - performance of contract (Art. 6(1)(b)).
  • Retaining legacy encrypted cloud-sync blobs until deletion - your prior consent (Art. 6(1)(a)); we cannot read them.
  • Authorizing Melvu and securely delivering installers and device configuration - performance of our contract (Art. 6(1)(b)) and our legitimate interests in preventing unauthorized access and replay attacks (Art. 6(1)(f)).

Where we rely on legitimate interests, you can object at any time (Art. 21 GDPR) by emailing us.

4. Processors and sub-processors

We share the minimum data necessary with the following processors, each bound by a data-processing agreement:

  • Stripe - payment processing, Stripe Checkout, the Stripe billing portal and subscription billing.
  • Supabase - authentication and database hosting (account/profile data).
  • Resend - delivery of account emails, and promotional emails for confirmed subscribers. We record your subscription choices, consent timestamps and delivery status. Email open and click tracking are disabled.
  • Cloudflare, Inc. (USA) – DNS, content delivery and DDoS protection for melvu.app. All web requests pass through Cloudflare, which processes your IP address, request details and approximate country to deliver and protect the site, and may set strictly necessary security cookies such as __cf_bm. Transfers rely on the EU–US Data Privacy Framework and Standard Contractual Clauses.
  • Discord Inc. (USA) - when you link your Discord account, we receive your Discord user ID and give that account the community-server role for your plan.
  • Image generation - prompts, reference images and generated images are processed by Melvu Image Studio (hosted on Supabase) and the AI image model provider it calls to create the image. Images are generated on request and returned to your app.
  • YouTube (Google LLC, USA) - the Streamers page loads nothing from YouTube until you click Watch live. The player then loads from youtube-nocookie.com, and Google processes your IP address and device data under its own privacy policy.
  • Hetzner Online GmbH (Germany) - hosting of the website and its backend in the EU.

5. Retention

  • Account and profile data - kept while your account is active, and deleted shortly after you delete your account.
  • Historical waitlist data, including creator attribution - kept only as long as needed for the access requests made before the waitlist closed. Unsubscribing stops the relevant emails; minimal consent and suppression records remain to respect your choice. You can request removal of your waitlist data. Completed website email jobs are removed after 30 days when the queue next changes.
  • Web server access logs - kept for up to 14 days, then rotated out.
  • Daily visitor hashes - kept only in server memory, for at most about 31 days, and never written to disk.
  • Keyed IP fingerprints - active network bans expire within 30 days; related security records are kept only while needed for abuse investigation and the audit trail.
  • Referral cookie - up to 30 days in your browser, or until the referral is linked to your account, when it is deleted. Referral attribution and commission records - kept while needed to pay and account for partner commission, and for the period required by tax and accounting law.
  • Device records - kept while your account exists and deleted with it. Signing a device out ends its access immediately.
  • Live Melvu session metadata and aggregate counters - removed on disconnect or after the bounded two-minute presence window; local counters reset when the desktop process restarts.
  • Billing records and invoices - kept for the period required by Portuguese/EU tax and accounting law, even after account deletion.
  • Legacy cloud-sync blobs - retained only until account deletion or an erasure request, then permanently removed.
  • Melvu device and operational records - kept while needed to provide and secure the service, investigate failures and protect the audit trail; device access ends automatically when the qualifying plan, Lifetime access or Team entitlement ends.

6. International transfers

Some processors may store or process data outside the European Economic Area. Where that happens, transfers are protected by appropriate safeguards under the GDPR, such as the European Commission's Standard Contractual Clauses or an adequacy decision.

7. Your rights

Under the GDPR you have the right to access, rectify, erase, restrict and port your data, to object to processing, and to withdraw consent at any time. To exercise any of these, email us at [email protected].

  • Erasure (right to be forgotten) - you can delete your account yourself, directly in the dashboard, using the account deletion flow, which asks for your current password. This removes your account and associated profile data.
  • Legacy cloud-sync deletion - delete your account in the dashboard or contact us to erase any retained encrypted blobs; once deleted they cannot be recovered.
  • You also have the right to lodge a complaint with your supervisory authority - in Portugal, the Comissão Nacional de Proteção de Dados (CNPD).

8. Cookies and local storage

The site uses the storage needed to keep you signed in (Supabase auth/session tokens), minimal preference and session storage, and, only when you arrive through a partner link, the first-party melvu_ref cookie. Cloudflare may set its strictly necessary __cf_bm security cookie. It uses no analytics or advertising cookies. See the Cookies Policy for details.

9. Changes and contact

We may update this policy from time to time; material changes will be reflected by the date above. Questions or requests: [email protected].