Privacy Policy for WallpAi

Effective date: 7 September 2026

Previous version: 25 December 2023

1. Overview

This policy covers the WallpAi Android application (com.wallpai) and the site at wallpai.ovh. It describes what we collect, why, who else sees it, and how to get rid of it.

WallpAi is run by one person. There is no advertising network beyond Google AdMob, nothing is sold, and there is no analytics product other than the Google ones named below.

2. What we collect

a. If you use the app as a guest

You can use WallpAi without giving us an email address. A guest account stores a generated identifier and your generation credit balance. That is all of it.

b. If you register

your email address and a password, which is stored only as a one-way hash and cannot be read back;
a username you choose;
if you sign in with Google: the identifier and email address Google gives us, and your default Google profile image. We do not receive your Google password.

c. What you create

The prompts you type, including negative prompts, and the guidance setting. These are stored with the wallpaper they produced and are sent to the image-generation service that makes it (see section 4).
The wallpapers you generate and save, and whether you marked each one public or private.
Your favourites, and any reports you file.
A profile picture and banner, if you upload them.

d. Automatically

What	Why	Can you turn it off?
Crash reports (Firebase Crashlytics) — the error, a stack trace, device model and Android version	To find and fix the crash	On by default. It is how a crash gets fixed at all.
Usage events (Firebase Analytics) — which screens are opened, whether a generation succeeded, how long it took, the category chosen, the length of a prompt	To see what is broken and what is used	Off unless you agree. Collection starts disabled on every launch and is enabled only from the consent choices the app asks for the first time you open it.
Advertising identifier and ad interaction (Google AdMob)	To show the banner and the rewarded video that pays for the app	Personalised advertising is governed by the consent form on first launch, and you can reset or withdraw it from your Android settings.
Server request logs — the route called, the response code, timing, and the app version	To keep the service running and diagnose failures	No, but see below.

The request log never records the content of a request. Not the body, not header values, not query-string values — so passwords, reset links, email addresses and prompts do not appear in it.

Your prompt text is never sent to Firebase. Analytics events carry the number of characters, never the words.

3. What we do with it

Sign you in and keep you signed in.
Generate the wallpaper you asked for, and store it so you can find it again.
Show public wallpapers in the shared gallery.
Count and top up your generation credits.
Show advertisements, which is what pays for the generation.
Send you account email: verification, and password resets.
Investigate abuse of the reporting and moderation system.

We do not sell your data, and we do not use your prompts or your wallpapers to train any model of our own.

4. Who else sees it

Service	What reaches them
The image generator (currently Replicate)	Your prompt, negative prompt and generation settings. Not your name, email address or account identifier.
Google Cloud Storage	The wallpapers you generate, and your profile picture and banner.
Google AdMob	Advertising identifier and ad interactions.
Google Firebase	Crash reports, and usage events if you agreed to them.
Google Sign-In	Only if you choose it, and only to sign you in.
Gmail (SMTP)	Your email address, to deliver account mail.

We may also disclose information where the law requires it.

5. What other users can see

Public wallpapers — the image, its title, its prompt and the username of whoever made it. If you would rather your prompt were not readable, save the wallpaper as private.
Your username.
Not your email address, and not your password.
Profile pictures and banners are not shown to other users in the app, but they are stored on public web addresses, so anybody who has the address can open the image. Do not upload something you would not be willing to have seen. (The 2023 version of this policy called them private without qualification. That was not accurate about how they are stored, and this corrects it.)

6. Keeping it, and deleting it

We keep your account and its contents until you delete them. Full instructions, and exactly what is and is not removed, are on the Delete your account page. In short: deleting the account removes your profile, your wallpapers, your favourites, your credits and your uploaded images immediately. Reports you filed about other people's wallpapers are kept with your identity removed, because they are moderation records about somebody else's content, and a database backup taken beforehand holds the account until that backup expires in the normal rotation.

A guest account cannot be recovered. It exists on one device, and signing out of it or reinstalling the app loses its wallpapers and credits permanently. Register with an email address if you want them to survive.

To ask what we hold about you, or to have it corrected, email us at the address in section 9.

7. Children

WallpAi is not directed at children under 13, and we do not knowingly collect anything from them. If you believe a child has created an account, email us and we will remove it.

8. Security

Passwords are stored hashed and cannot be read back. Traffic to the API is encrypted in transit, the database is not reachable from the internet, and an account can only be modified or deleted by whoever is signed in to it. No system is perfectly secure and we cannot promise otherwise.

9. Changes, and contact

When this policy changes, the effective date above changes with it. Questions, requests and complaints: wallpai.contact@gmail.com.