top of page

Privacy policy

Privacy Policy

Last updated: 29 October 2026

1. Who is responsible for your personal data?

Media Moonlight is operated by XYZ Projects KLG, a Swiss general partnership, c/o Nils Meyer, Goldschrütifeld 14b, 6017 Ruswil, Switzerland, UID CHE-187.378.582 ("Media Moonlight", "we", "us").

We are responsible for the processing of personal data described in this Privacy Policy in connection with mediamoonlight.com and our services. To ask about privacy or to exercise your rights, contact info@mediamoonlight.com or write to the address above.

This Policy covers website visitors, guests who use our tools without an account, account holders, subscribers and people who contact us. It explains our processing under the Swiss Federal Act on Data Protection (FADP) and, where it applies, the EU General Data Protection Regulation (GDPR).

2. Personal data we process

We receive personal data directly from you, through your use of the Service, and from the providers involved in login, payments and delivering the Service.

Account information

Email address, name, login information, account identifier and settings. A telephone number only if you choose to provide one. If you log in with Google or Facebook, the account information that provider shares with us.

Purchases and subscriptions

Selected plans and token packs, subscription status, order and payment references, payment status, renewals, cancellations and refunds.

Tokens and usage

Your free-token allowance and its period, plan and top-up balances, token transactions, and a record of each request: tool, model, settings, token price, which balances paid, status and times. These records do not contain your prompt or files.

Prompts and pictures

Prompts, pictures you upload (reference and start images for the generators, photos for Upscale, Background Remover, Colorize and Vectorize), the settings you choose and the results. Pictures and prompts can contain personal data about you or other people.

Gallery information

Your creations with their prompt, settings and any reference image, pin status, creation date and the date until which each creation is kept.

Free-token and abuse-prevention data

A random device key stored in your browser, a visitor identifier issued by Wix, a keyed hash of the network part of your IP address, whether a CAPTCHA was passed, and for the sign-up bonus a keyed hash of your email address. See Section 3.

Technical information

IP address, device and browser information, access times, and error and security records processed by our providers when you use the website.

Communications

Messages you send to support, your contact details and the information needed to deal with your request.

Consent records

Your newsletter subscription and its confirmation or withdrawal.

Registration and social login

You can register with your email address, a password and your name, or log in with Google or Facebook. With social login, the provider shares the account information you allow during sign-in, and it processes information about your use of its login service under its own privacy terms. Accounts and passwords are managed by Wix; we cannot see your password.

3. Why we process data

We process personal data to:

  • provide accounts and tools and carry out your requests;

  • keep your creations in My Creations, including the prompt, settings and reference image, so that you can view, download and recreate them;

  • manage token balances, subscriptions, token packs and payments;

  • show your token history on the Token Usage page;

  • answer support requests and handle cancellation, refund and privacy requests.

We also process the information needed to protect accounts and systems, investigate technical failures, prevent fraud and abuse, keep legally required records and establish, exercise or defend legal claims. We use request records without prompts or files to estimate how long a request usually takes, which the progress bar on the tool pages shows.

Free tokens and abuse prevention

To give guests free tokens without an account, and to stop people from collecting them repeatedly, we work as follows:

Device key

When you first use free tokens, your browser receives a random device key, stored in your browser's local storage. It links your free tokens and guest creations to that browser.

Network hash

The device record also holds a keyed cryptographic hash of the network part of your IP address: the first three blocks of an IPv4 address, or the first four groups of an IPv6 address. We use it to count how many free allowances are started from one network per day and per week. We do not store your full IP address for this purpose.

Visitor identifier and CAPTCHA

The device record also holds the visitor identifier Wix issues to your browser, and whether you passed a CAPTCHA. A CAPTCHA may be requested when many allowances come from one network.

Sign-up bonus

For the one-time bonus, we store a keyed hash of your login email address, normalised so that variants of one address count as one, together with your account key and browser key. We do not grant the bonus to addresses of disposable-email services.

You need to provide the information marked as required to use an account, a paid service or a tool. Everything else is optional.

4. Legal bases where the GDPR applies

Where the GDPR applies, we rely on these legal bases:

Performance of a contract — Article 6(1)(b) GDPR

Providing the tools, your account, My Creations (including Recreate), tokens, orders and the Token Usage page relies on performance of a contract or steps you request before entering into one.

Legitimate interests — Article 6(1)(f) GDPR

Free-token limits, CAPTCHA, sign-up bonus checks, security, fraud prevention, fault analysis, run-time estimates and legal claims rely on our legitimate interests.

Legal obligation — Article 6(1)(c) GDPR

Accounting and other legal obligations rely on a legal obligation.

Consent — Article 6(1)(a) GDPR

The newsletter relies on your consent.

Our legitimate interests are running and securing the Service, keeping the free offer available to everyone, preventing misuse, fixing faults and protecting our legal rights. We do not rely on them where your interests or rights prevail.

5. Wix, Cloudflare, Stripe and other recipients

We use Wix (Wix.com Ltd., Israel) to run the website, member accounts and login, the checkout for plans and token packs (Wix Pricing Plans), the newsletter and our site settings. Wix processes this data on our behalf; see the Wix Privacy Policy and Wix's list of subprocessors. The CAPTCHA on the sign-up form, and any CAPTCHA for free tokens, is provided through Wix using Google reCAPTCHA, which processes device and interaction data to tell people from bots.

Payments are made through the Wix checkout and processed by Stripe, with the payment methods shown at checkout. Stripe receives the data needed to process the payment, prevent fraud and handle refunds and chargebacks. We see the order, its status and limited payment details in our Wix dashboard, not your full card number. Stripe has its own legal obligations and acts as an independent controller for some activities; see the Stripe Privacy Policy.

We use Cloudflare (Cloudflare, Inc., USA) to store and deliver your creations and to keep our token records:

Storage

Files are stored in Cloudflare R2: creations, reference images and pictures uploaded for processing. The storage is private and not publicly reachable. A file can be opened only through a short-lived link (valid for 15 minutes to one hour) that our system signs for you.

Database

Prompts, gallery entries, token balances and request records are kept in a Cloudflare D1 database and processed by Cloudflare Workers. Cloudflare also processes connection data, such as IP addresses, to deliver and protect the Service.

Encryption

Cloudflare encrypts stored data (AES-256), and all transfers use TLS. This is not end-to-end encryption: our system can read stored data in order to deliver it to you.

Our access

We do not look at your creations, prompts or uploads, and our administration tools do not display them. Only our administrators can access the storage systems, and only where necessary to run and secure the Service, fix faults, act on your request or meet legal obligations.

We also use Replicate and the AI providers behind its models (Section 6), and Microsoft for our support mailbox (Section 8). Each provider receives only what it needs for its task. We may disclose information where the law requires it, in response to valid requests from authorities, or where necessary to protect rights.

6. AI processing and training

When you use an AI tool, your prompt, any picture you add and your settings are sent to the AI model you selected to produce the result.

Replicate and the models we offer

We send requests through the API of Replicate (USA), using the model you select on the tool page. Replicate receives your prompt, your settings and, where you add a picture, a link to it. The link is signed and valid for one hour, and Replicate fetches the picture through it. For Colorize, the reduced picture is sent with the request itself. Replicate returns the result to our system, which stores it in your gallery.

Some models run on Replicate's own infrastructure. For others, Replicate passes the request on to the model's provider (for example Google, OpenAI or Runway), which then also processes it.

Google

Models offered:

Data sent, depending on the tool: prompts and settings; reference images (Nano Banana 2.1); start or reference images (Veo); photos to enlarge (Upscaler).

Black Forest Labs / FLUX Kontext

Models offered:

Data sent, depending on the tool: prompts, settings and reference images (FLUX 3); photos to restore and colourise.

OpenAI

Models offered:

Data sent, depending on the tool: prompts, settings and reference images.

Alibaba / Wan

Models offered:

Data sent, depending on the tool: prompts and settings; start images (Wan 3).

ByteDance

Model offered:

Data sent, depending on the tool: prompts, settings, start or reference images.

Runway

Model offered:

Data sent, depending on the tool: prompts, settings and start images.

Pruna AI

Models offered:

Data sent, depending on the tool: prompts, settings and start images (P-Video); photos to enlarge (P-Image Upscale).

Bria

Model offered:

Data sent: photos for background removal.

Recraft

Models offered:

Data sent, depending on the tool: prompts and settings for logos; pictures to convert into SVG.

Video results can include synthetic audio. Pictures of people, and the SVG files made from them, contain personal data; converting a picture does not anonymise it. See the Replicate Privacy Policy and Replicate's list of subprocessors.

How long Replicate keeps your request

According to Replicate's documentation, requests made through its API, together with their inputs, results and logs, are deleted automatically after one hour. We use only the API. Providers that receive a request from Replicate may keep data under their own terms.

Training by AI providers

We do not use your inputs or outputs to train AI models. The providers behind the models work under their own terms. The general terms of Black Forest Labs (FLUX API Terms) and Runway allow them to use inputs and outputs to improve their models; it is not confirmed whether this also applies to requests sent through Replicate. Recraft's developer terms exclude training Recraft models on results created through its API. For the other models we have no confirmation either way. If you do not want this, do not submit personal or confidential content.

Your gallery is private. We do not make your inputs or results public, share them with other users or use them in advertising without your separate permission. Our tools do not identify people or infer sensitive characteristics. Upload pictures of other people only where you are allowed to, and avoid sensitive or confidential content.

What we keep from your requests

Prompts and settings

Prompts and settings are kept with your creation for as long as the creation exists (Section 10). While a request is running, the prompt is also held in the request record. It is removed from that record when the request ends. A failed request keeps no prompt.

Reference and start images

Reference and start images (Image and Video generators) are kept with the creation so that you can recreate it. We keep the picture as it was sent to the model, reduced only if it was larger than the model accepts (up to 16 megapixels for images, 4 megapixels for video). The stored picture counts toward your pin space and is deleted with the creation. The upload copy used for sending is removed by a nightly clean-up within about two days.

Photos for Upscale, Background Remover and Vectorize

Photos for Upscale, Background Remover and Vectorize are kept in private storage only until the request has finished, at most about one day, and are then deleted. Only the result is kept, as a creation.

Photos for Colorize

Photos for Colorize are reduced in your browser and sent with the request. We do not store them; only the result is kept.

Picture metadata

Before a picture is uploaded, your browser removes the metadata that can show where, when and with what camera it was taken, such as the GPS location. This covers EXIF, XMP and IPTC in JPEG files, EXIF, text and time entries in PNG files, and EXIF and XMP in WEBP files. The picture itself is not changed. Upscale keeps only the orientation of a turned photo, so that it stays upright. Colorize redraws the picture, which removes its metadata as well.

7. Cookies and browser storage

Wix, our website platform, sets the cookies needed for sessions, login, security and the operation of the website; see Wix's information on cookies.

Our own site code stores the following in your browser's local or session storage:

  • the device key for your free tokens and guest creations (Section 3);

  • markers that the transfer of guest creations into your account, or the sign-up bonus, has been handled;

  • a copy of your token balance and of the tool prices, so that pages show them faster.

These are needed for the features you use. We currently use no analytics, advertising or other tracking technologies. If we add any, we will update this Policy beforehand and ask for your consent where the law requires it.

You can block or delete cookies and browser storage in your browser settings. The website may then not work fully, and deleting the site data removes the device key and with it your access to guest creations.

8. Newsletter and other communications

We use your contact details for messages needed to manage your account, purchases and requests. These are separate from promotional messages.

The newsletter is run through Wix, with signup in the footer of the website. The consent checkbox is not pre-ticked, and you confirm your subscription by email (double opt-in). We send the newsletter until you unsubscribe, which you can do through the link in every newsletter. Signing up for the newsletter is separate from accepting the Terms of Service or creating an account.

Support requests are handled by email at info@mediamoonlight.com. Our mailbox is hosted by Microsoft (Outlook). We process the information you include to answer and resolve your request, including any pictures or prompts you send us.

9. International transfers

Our providers process personal data in other countries:

Wix

United States, Ireland, Israel, South Korea, Taiwan and other countries (according to Wix).

Cloudflare

Its worldwide network, including the United States.

Replicate and the AI providers behind its models

United States.

Stripe

United States and other countries.

Google (login, reCAPTCHA), Meta (Facebook login), Microsoft (email)

United States and other countries.

Where a country does not offer an adequate level of data protection under Swiss or EU law, the transfer relies on the provider's certification under the Swiss-U.S. and EU-U.S. Data Privacy Framework, or on standard contractual clauses in the provider's data processing terms, with the adaptations Swiss law requires. You can ask us for a copy of these safeguards at info@mediamoonlight.com.

10. How long we keep data

We keep personal data only as long as needed for the purpose, our contract with you and our legal obligations, and then delete or anonymise it.

Creations (image, video and SVG files)

Stored in Cloudflare R2, private.

Guests: 7 days. Accounts without a running plan: 14 days. Accounts with a running plan: 90 days. The period is set when the creation is made. Pinned creations are kept until you unpin or delete them or delete your account.

Prompt and settings of a creation

Stored in Cloudflare D1 for as long as the creation.

Reference and start images

Stored in Cloudflare R2, next to the creation, for as long as the creation.

Upload copy of a reference or start image

Stored in Cloudflare R2, private, for up to about two days.

Photos for Upscale, Background Remover, Vectorize

Stored in Cloudflare R2, private, until the request has finished, at most about one day.

Request and token records (no prompts, no files) and ended plans

Stored in Cloudflare D1, under a pseudonymous account or device key.

Kept for 10 years as business records, then deleted automatically. A request whose creation you keep pinned stays as long as the creation, for Recreate.

Guest device record (free tokens)

Stored in Cloudflare D1.

Deleted 90 days after last use; if moved into an account, deleted 2 years after the move or its last use.

Network counters for free-token limits

Stored in Cloudflare D1 as a keyed hash.

Kept until the end of the day or week they count.

Sign-up bonus record (keyed hash of the email address, account and browser keys)

Stored in Cloudflare D1.

Kept for 2 years after the bonus, then deleted automatically.

Account, name, email, orders

Stored in Wix while the account exists, then as required for accounting.

Newsletter consent

Stored in Wix until you withdraw it, plus the proof of consent the law requires.

Support emails

Stored in Microsoft (Outlook) for 2 years after the request has been dealt with.

Database restore points

Stored in Cloudflare D1 for up to 30 days; deleted entries disappear completely after that.

Your browser keeps the items in its local storage until you clear them.

11. Deleting creations and your account

Single creations

You can delete a creation in My Creations. Its file, prompt and reference image are deleted immediately.

Your account

To delete your account, send a request to info@mediamoonlight.com from the email address of your account. We end any running plans, delete your account and confirm the deletion to you, at the latest within one month of your request.

When your account is deleted, an automatic process deletes everything in your storage: all creations, including pinned ones, their prompts and their reference images. Requests still running are stopped from storing anything. All token balances, including purchased top-up tokens, are forfeited. Your token and request records remain for accounting purposes under a pseudonymous key, without prompts or files, for the period in Section 10. Database restore points expire after 30 days. Download any files you want to keep before you send your request. Wix deletes your account data under its own procedures.

12. Security

We protect your data with technical and organisational measures suited to the risk, including:

  • private storage reachable only through short-lived signed links;

  • encryption of stored data by Cloudflare and TLS for all transfers;

  • access keys kept out of the website's code;

  • signed requests between the website and our storage system.

No online service can guarantee absolute security. Protect your login details and tell us promptly if you suspect unauthorised access to your account.

13. Your rights

Depending on the applicable law, you have the right to information about our processing and to access your personal data, to have inaccurate data corrected, to have data deleted or its processing restricted, to object to processing, and to receive your data in a portable format. You can download your creations from My Creations yourself.

Where processing is based on your consent, you can withdraw it at any time, with effect for the future. Where we rely on legitimate interests, you can object on grounds relating to your situation. You can object to direct marketing at any time.

Contact info@mediamoonlight.com to exercise your rights. We may ask for information to confirm your identity. We reply within the legal deadlines and explain any lawful limitation, for example where we must protect other people's rights or keep records required by law.

You can contact the Swiss Federal Data Protection and Information Commissioner (FDPIC). Where the GDPR applies, you can also complain to a data protection authority, in particular in the country where you live or work or where the alleged infringement took place. You do not need to contact us first.

14. Children and teenagers

The Service is intended for people aged 16 and over, with or without an account. We do not knowingly process personal data of children under 16. If we learn that an account or requests belong to a child under 16, we delete them. Users under the age of majority need their parent's or guardian's authorisation for purchases.

Parents or guardians who believe their child's data has been processed can contact us at info@mediamoonlight.com.

15. Automated decisions

We use automated checks that can refuse a request or a free benefit:

Prompt check

Every prompt is checked automatically, and prompts that sexualise minors are refused before anything is sent to a model. A refused request costs nothing.

Model safety filters

The AI models apply their own safety filters, which can refuse a request; its tokens are then returned.

Free-token limits

Free allowances are limited per network and week and may require a CAPTCHA. The sign-up bonus is not granted to disposable email addresses or to an address, account or browser that has received it before.

These checks have no legal or similarly significant effects on you; you can always use the Service with an account and purchased tokens. If you think a check refused you wrongly, contact info@mediamoonlight.com and a person will look at it.

16. Changes to this Policy

We may update this Policy when our services or the law change. The current version is always on our website with its date. Where the law requires it, we will inform you of changes in advance or ask for your consent.

bottom of page