Effective date: 21 October 2026.
One policy for every version of the app — iOS, Android and Windows. Where they behave differently, it is said so.
Livery Lab collects neither your work nor your name and email: no livery contents, no images you placed in them. Signing in is optional; if you choose to sign in with Apple or Google, we receive your name and email — see "Account". There is no advertising.
What the app does send is usage statistics and crash reports: which actions were taken, from which country, region and city (worked out from the IP address), and whether the app crashed. No livery names, no file names and no images go there. What is sent is described in "Usage statistics and crash reports" below.
The one exception is a link for a friend, and only when you make one yourself: then a turntable of your car as images and the livery's captions go to our server, so that your friend can see them in a browser. Details are in "Link for a friend".
The second exception is the livery cloud (part of Pro), again only when you tap for it: a livery you put into the cloud yourself is kept on our server under your account so that you can open it on another device. Details are in "Livery cloud and Pro".
Everything you do in the app stays on your device:
The developer has no access to these files: the files themselves never leave the device unless you put a livery into the cloud yourself. Car models are downloaded from our server; what goes back from your device is the usage statistics and crash reports described below and, when you tap for it, the turntable for a link for a friend. Not one livery file, layer or model is among them.
On iOS the files live in the app's documents folder: you can see them in the Files app, and they go into your device backup if you have one enabled.
On Android the files live in the app's internal storage. Other apps cannot see them, and they do not go into a backup: app data backup is turned off (allowBackup="false").
Deleting the app deletes all of these files with it.
The app goes online in six places, and only these:
1. The model catalog — reads the list of cars and downloads the one you picked. No liveries and no images are sent there. As with any website, the host sees your IP address while the file is downloading — the file could not reach you otherwise. 2. Usage statistics — sends the events listed below. 3. Remote settings — the app asks whether it is time to update. The request carries an anonymous installation number, the app and system versions and the device language — the server cannot answer without them. No name and none of your files are among them. 4. A link for a friend — only when you tap "Share a link" or "Delete link". What exactly is sent is described in the next section. 5. Account — only when you sign in, sign out or delete it; see "Account". 6. Livery cloud and Pro — only when you are signed in and open the cloud or the Pro window; see "Livery cloud and Pro".
The app makes no other network requests — not when parsing a model, not while painting, not when building the archive. The Windows version goes online differently — see “Windows version”.
On Android everything above works the same way, the model catalog included. The app requests two permissions, and both exist purely for the network: internet access and network state. It asks for no camera, no microphone, no location (the statistics server works out the country and city from the IP address — see "Usage statistics and crash reports"), no contacts and no photo library — you pick the model and the images through the system file picker, which needs none. The permission list on the app's Google Play page consists of those two — you can check.
"Share a link" makes a page where a friend, without the app, sees your car in its livery and can turn it around. Nothing is sent until you tap that button yourself.
What is sent. A turntable — 48 images of your car from all sides plus a cover, made by the app — and captions for the page: the livery and car names, the game, the number, and the team and driver names if you entered them. Livery files, layers, the car model and the original decal images are not sent. If your livery carries your own photo as a decal, it shows on the turntable just as it does on the body.
Where it is stored. On our server liverylab.uz, which runs on Cloudflare (a processor acting on our behalf): the turntable is kept in Cloudflare R2 storage.
Who can see it. Anyone who has the link. The page is closed to search engines, but the address can be forwarded — do not share what you do not want to show.
How to delete it. With "Delete link" in the app: the turntable and the captions are erased at once, and the old address only shows "This livery was removed". The deletion key is kept in the app on your device; if the app is gone, email us at the address below with the link and we will delete it by hand.
Reports. The page has a "Report" button. A report keeps only its time and the reason, if one was given — not the address or the device of the person reporting. Links that break the rules or someone's rights are taken down.
A link is not tied to your account, even if you are signed in: no name or email goes to the page or the links server. Like any website, the server sees the IP address of whoever uploads a turntable or opens the page — only for the duration of the request and to allow no more than five links a minute from one address; we do not store it. Everything travels over HTTPS.
Signing in is optional: you can paint, build the archive and put a livery into the game without an account. You may sign in if you wish — with Apple or Google, using the "Account" button in the garage. The account carries the livery cloud and the Pro subscription — continuing liveries on other devices.
What we receive. The name and email address that Apple or Google provides, the sign-in method and the account number assigned by Firebase. Apple lets you hide your email — then we only see Apple's relay address. No password, no liveries and no files go into the account.
Where it is kept. In Google Firebase Authentication (a processor acting on our behalf). The device keeps a sign-in key so you do not have to sign in every time; on a computer it is kept together with the name and email, in the app's folder.
On a computer sign-in happens in the browser: the app opens a sign-in page at auth.liverylab.uz, and the page hands the sign-in key back to the app on the same computer (address 127.0.0.1). The browser does not remember the sign-in itself.
The account is not tied to links for a friend or to crash reports. It is tied to the usage statistics only by a pseudonymous number, described in "Usage statistics and crash reports"; your name, your email and the Firebase account number itself do not go there. No selling, no advertising.
The cloud is optional and only for signed-in users: a livery goes there only when you tap "To cloud" or "Upload a livery" yourself, and only the one you picked.
What is sent. The livery file as it is: layers and masks, the cover, the livery name, team and driver names, the number; the images placed on it as decals; a description of the car — its name, its number in our catalog, the game. Along with it go the time the livery was changed and the kind of device (iPhone, Android or computer). The car model is not sent: each device takes it from the catalog or from its own game.
Where it is kept and who sees it. On our server liverylab.uz (Cloudflare, a processor acting on our behalf), in Cloudflare R2 storage, under your account number. Only you can see and download it — by signing in with the same account. The cloud has no link and is not open to anyone else. Everything travels over HTTPS. The cloud holds up to 200 liveries, each up to 64 MB.
How to delete. With "Delete" in the cloud window — the livery is erased from the server at once. Deleting your account erases the whole cloud.
Pro. The server keeps, under your account, whether you have a Pro subscription: where it was bought (App Store or Google Play), which product, until when it is valid and the original purchase number. To check a purchase, the server asks Apple or Google about it. We never see or receive payment details — card, address, amount.
In the app: "Account" in the garage → "Delete Account" → confirm by signing in once more. The account is deleted from Firebase immediately and for good; the livery cloud and the subscription record are erased from our server along with it. For Sign in with Apple, the permission granted to the app is revoked as well. Deleting the account does not cancel a subscription — it is cancelled where it was bought, in the App Store or Google Play. Liveries on the device stay.
If the app is already gone, email us at the address below from the address you signed in with — we will delete the account manually within 30 days.
The app counts what is done in it, and never what you painted. The statistics run in the iOS app from the App Store, in the Android app installed from Google Play, and in the installed Windows program. Developer builds, simulators, emulators and automated checks send nothing.
Which events. Which car was downloaded from the catalog: its catalog number, name, brand, class and game — this is public catalog data, not yours. For a car taken from the game's files, the name of its folder in the game. Importing a model of your own — only the file format. The same public car details also go with later events about that car — opening, exporting, the cloud: for a catalog car, its catalog name, brand, class and game; for a car from the game's files, the folder name; for a model of your own, the game and the ACC model name if the app guessed it, otherwise the mark "own". For a decal, where it came from is sent — a ready-made element (with its number in our library), text, recent, photo or file — but not the image or the text itself. Opening and closing a livery — how many seconds the work took, how many layers and decals were added, how many times you undid something and which tools you worked with. Exporting to the game or to an archive, sharing, a link for a friend and the livery cloud — whether it worked, how many seconds it took and how many megabytes it weighs. Signing in, signing out, deleting the account, the Pro window and a purchase — the step and the result. If an action failed, the kind of reason is sent — "no network", "no room" — not its text: the text can contain a path to your file.
What else is known about you. Sent with the events: the language in which you see the app, the number of cars and liveries in your garage, whether you are signed in and with what (Google or Apple), and whether you have your own paid Pro subscription and which — monthly or yearly. The free Pro that is currently open to everyone does not count as a subscription. In addition, Amplitude receives what it receives about any app: the device model, the system and app versions, the language and the mobile carrier; the Windows program sends the system name and version, its own version and the language.
Location — from the IP address. The IP address travels with the event, and Amplitude uses it to work out the country, region and city, approximately, as any website can. There is no precise location: the app does not ask for location permission and does not read GPS, latitude and longitude are not collected, and the advertising region is turned off.
Device number and account number. To tell one device from another, the installation is given a pseudonymous number. If you signed in with Google or Apple, the events carry one more pseudonymous number, calculated from the number of your Firebase account. It is the same on all your devices, so Amplitude can see that an iPhone, an Android phone and a computer belong to one person. No name or email can be seen behind this number in Amplitude, and the Firebase number itself does not go there. After you sign out, new events no longer carry this number, while those sent earlier stay as they were; when you delete your account, the device number is replaced with a new one and new events are not tied to the earlier history.
What never leaves:
A crash report contains what such a report usually contains: where in the code the app crashed, the device model, the system version, free memory and disk space. A short marker about the last major action is attached — "editor opened", for example. There is no account number in a report.
Processors: Amplitude (statistics) and Google Firebase Crashlytics (crashes and remote settings). The processors act on our behalf; data is neither sold nor shared for advertising, and you are not tracked across other companies' apps: the app does not read the device advertising number and does not ask for tracking permission. Everything travels over an encrypted connection (HTTPS).
The desktop program paints the same way as the phone app and keeps everything on your computer too: the library, liveries and decal pictures live in %APPDATA%\Livery Lab. Uninstalling the program leaves that folder alone — it is your work; you can delete it by hand.
Usage statistics in the installed program are the same as on phones: the same events, the location from the IP address and the pseudonymous account number after you sign in — all described in "Usage statistics and crash reports". The program sends them to Amplitude itself; Firebase Crashlytics is not used in the Windows version. The device number is random and is written to the settings file in the %APPDATA%\Livery Lab folder; uninstalling the program leaves that folder alone, so the number survives a reinstall until you delete the folder. A program launched by the developer from source code, and automated checks, send nothing.
Update check. On launch and once a day the program reads a file with the latest version number from liverylab.uz. The request carries the program and Windows versions in its header, like any program does — no installation number and no name. If you click “Update”, the program downloads the installer from the same place, checks its checksum and installs it over the old version.
Crash reports go to our own server liverylab.uz (Cloudflare, acting on our behalf), with no third-party services. A report contains the program, Windows and Java versions, the graphics card and driver name, the place in the code where the program crashed and the last lines of its log. File and folder paths — which contain your Windows user name and the names of liveries and pictures — are replaced with “<path>” before anything is sent. A report is tied neither to an account nor to a device, and the server does not store your IP address. Reports are kept for 90 days and then deleted automatically.
Otherwise the program goes online in the same places as the phone app: the model catalog, the link for a friend, sign-in and the livery cloud, if you sign in. The program does not sell the Pro subscription — it is bought in the phone app with the same account.
we take a link down after a report.
deleted automatically.
and serve only to understand what is used and what breaks.
The account, if you signed in, is kept until you delete it — see "How to delete your account". The livery cloud and the subscription record are kept until you delete them yourself or together with the account.
There is no name and no email in the statistics. If you have never signed in, they are not tied to an account either, so we cannot find the records of a particular person in them. After you sign in, the events carry a pseudonymous account number: after you sign out, new events no longer carry it, while those sent earlier stay as they were, and deleting the account leaves new events not tied to the device's earlier history; the events already sent stay in Amplitude — without a name or email. To stop anything leaving the phone, delete the app. On Android the installation number is deleted with it, and a new installation gets a new number unrelated to the old one. On iPhone the device number is the system's vendor identifier (IDFV): it stays the same as long as at least one other app from the same developer is installed on the phone, and a new one appears only when none is left. On a computer the number lives in the %APPDATA%\Livery Lab folder — delete it, and a new installation starts with a new number too. Any question about your data can be sent to the email below.
When you build an archive and choose where to send it, the file is handed over by the system in the way you picked: AirDrop, Files, email, a messenger. That is your action and your choice of recipient — the app only hands the file to the system.
You send a link for a friend yourself in the same way: the app puts the address into the system share sheet or copies it, and you decide who gets it.
Painting, building the archive and putting a livery into the game are free in every version. The only paid part is the Pro subscription (livery cloud, transfer between devices, the league grid), and until payments launch, Pro is free for everyone.
Once the subscription opens, it is bought in the App Store or Google Play: the store handles the payment, and the app never sees or stores payment details. The app passes the purchase confirmation to our server so that the subscription works on all your devices — what is kept is described in "Livery cloud and Pro". A subscription is cancelled in the store; deleting your account does not cancel it.
Without signing in, the app receives no name and no email from anyone, children included; they appear only if someone signs in with Apple or Google. The usage statistics and crash reports described above contain neither a name nor an email: they know the approximate location from the IP address, and a pseudonymous account number appears in them only after signing in. A link-for-a-friend page shows only what was entered into the livery — if a child makes a link, a parent should know it can be deleted in the app.
If this policy changes, a new effective date will appear here.
Questions about this policy: nasriddinov.islom.19@gmail.com