Privacy policy.

Information we handle

When you visit meluvya.com

You can read the website and blog without creating an account or uploading a photo. The site does not currently provide a photo-upload form. Its store buttons display a coming-soon message.

GitHub Pages hosts this website and can process technical request information, such as your IP address, browser information and requested pages, to deliver and protect the site. We have not added advertising pixels or visitor analytics cookies to the website. We use Google Search Console reports to understand how the site appears in search; these reports do not give us your photo library.

When you use the app

• Photos and creation choices. The photo you select for cloud generation, the effect or template you choose, and the generated result. A selected photo may include faces or other personal information visible in the image.
• A device-based identity. The current app uses guest access rather than requiring a new sign-in. A credential stored on your device connects you to your private collection; the service stores a hashed credential and an internal owner identifier.
• Job and service records. Request identifiers, timestamps, processing status, limited error information and usage records help return results, avoid duplicate jobs, apply service limits and troubleshoot failures.
• Purchase records, when purchases are available. Apple handles App Store checkout. The subscription system uses transaction identifiers, subscription status and credit records to verify purchases and restore entitlements. Meluvya does not receive your full payment-card details from that checkout.

How AI photo creation works

Cloud generation requires sending the selected photo to Meluvya’s backend on Cloudflare. The backend sends the photo and the instructions needed for the selected effect or template to Google Gemini. Where a template uses a reference image, that reference accompanies the request. The generated result returns to the backend for the app to retrieve.

Cloud generation is different from a device-only edit. The app also includes editor operations that run on the device. Review the app’s photo-upload notice before starting a cloud creation, and only submit photos you have permission to use.

Google’s handling of API input and output depends on the applicable service terms and account configuration. This draft does not promise zero provider retention or that submitted content is never used to improve models. The active Gemini data-use terms must be confirmed and stated here before the final policy is issued.

Service providers

Different providers support different parts of Meluvya. Reading this website does not itself send your personal photos to an AI provider.

• Cloudflare

  Hosts the app’s API, private photo storage, database and processing queue.

  Cloudflare privacy policy
• Google Gemini

  Processes the selected photo and creation instructions to produce an AI result.

  Gemini API data-use terms
• Apple

  Provides App Store purchases and subscription verification when those features are enabled.

  Apple privacy policy
• GitHub

  Hosts meluvya.com and delivers its public pages and images.

  GitHub privacy statement
• Supabase — legacy access

  Remains part of administrator authentication and compatibility with older signed-in app sessions. New guest installations do not use Supabase sign-in.

  Supabase privacy policy

Provider processing may take place outside your country. The operator’s location, applicable legal bases and international-transfer safeguards must be completed for the final release. Linked provider policies explain their services; they do not replace Meluvya’s own responsibilities.

Storage and deletion

Uploaded source photos: the documented backend deletes the temporary source after processing. A scheduled cleanup and a one-day storage lifecycle provide a backstop. Storage lifecycle cleanup is asynchronous, so this is not a promise that every copy disappears at an exact 24-hour deadline.

Generated results: the documented app service keeps results until the owner deletes them. Deleting a result removes its stored photo objects, while minimal job records can remain for ownership, duplicate-request protection and usage limits. The final policy must specify retention for those remaining records, purchase records and any provider logs or backups.

Copies on your device or elsewhere: cached images, exports saved to your photo library, and copies shared with other services are separate from the backend result. Deleting one copy does not necessarily delete the others. Removing the app is not a confirmed way to delete server-side data.

The current guest collection is tied to its device credential and does not automatically sync to a new device. Restoring a purchase restores its credit entitlement, not another device’s private photo collection.

Your choices and privacy rights

• Choose which photo to use and review the upload notice before cloud generation.
• Manage camera and photo permissions in your device settings. Changing permissions does not retroactively delete a photo already uploaded.
• Use the app’s photo-deletion controls for saved results, and manage exported or shared copies separately.
• Manage an App Store subscription through Apple. Cancelling a subscription and deleting photo data are separate actions.

Depending on the law that applies to you, you may have rights to access, correct, delete or receive a copy of your personal information, restrict or object to processing, withdraw consent where it is relied on, or complain to a data-protection authority. The final notice will identify the operator and provide a working way to make these requests.

Do not send passwords, device credentials or payment-card details in a privacy request. The contact fields below are not yet populated, so this draft is not a working request channel.

Age eligibility and updates

The app’s final age eligibility and related controls must be confirmed before release. Google’s current Gemini API terms restrict use in services directed toward, or likely to be accessed by, people under 18. This draft does not assert that Meluvya has already implemented age verification.

We will revise this page as the app’s release configuration and privacy details are finalized. The date above records the latest draft update; it is not an effective date for a completed policy.