Privacy Policy
Table of Contents
- 1 Scope and Who We Are
- 2 What We Collect — At a Glance
- 3 Guest or Account: How We Know It Is You
- 4 Your Account (Optional)
- 5 Information You Provide
- 6 Photos You Upload to the Catalogue
- 7 Your Garage
- 8 Favourites, Saved Searches, Likes and History
- 9 Regional Settings
- 10 Information Collected Automatically
- 11 Push Notifications and the Notification Centre
- 12 Advertising and Your Consent
- 13 Purchases and Premium
- 14 Vehicle Lookup by Plate or VIN
- 15 Car Recognition by Photo
- 16 Price Insight
- 17 Feature Availability, Testers and Gradual Rollout
- 18 Third-Party Services
- 19 Location Data
- 20 The Website and Cookies
- 21 Data Retention
- 22 Your Rights and Choices
- 23 Moderation and Enforcement
- 24 Children's Privacy
- 25 Security
- 26 International Users and Legal Bases
- 27 Changes to This Policy
- 28 Contact Us
- 29 Your Consent
This Privacy Policy applies to the Car Catalog app (the "Application") for Android and iOS, and to the website at carcatalog.app, both operated by the Car Catalog team (the "Service Provider", "we", "us"). The Application is an ad-supported service provided "AS IS".
This version replaces the policy dated October 18, 2026 and changes only section 20: the website now counts its visits with Cloudflare Web Analytics, which sets no cookies, and it no longer loads fonts or scripts from other servers. The October 18 version described what the Application does today: the garage, price insight, regional settings, likes and bookmarks, the notification centre and the full list of notifications we send (including promotional ones), the advertising formats and the consent we ask for, what the Application keeps on your phone, the operator notifications we receive through Telegram, and gradual feature rollout.
1. Scope and Who We Are
Car Catalog is a reference catalogue of car brands, models, generations and specifications, with automotive news, editorial collections and photographs contributed by users. Around it the Application offers a personal garage, favourites, saved searches, comparison, and — with Premium — a vehicle lookup by number plate or VIN, car recognition from a photo, an AI price estimate and offline copies.
An account is optional for most of the Application. Browsing the catalogue, the garage, favourites, uploads, reports and Premium all work without one, and we never ask for a password. If you choose to sign in with Google or Apple, we receive your name and email address from that provider so that your data can follow you to another phone — see section 4. Three features require an account because of what they do: the vehicle lookup, car recognition and price insight (sections 14–16). The only other time we ask who you are is a complaint about a photo, where the law requires us to know who is making the claim.
Every feature that processes data is described in its own section: which data, why, for how long, and what you can do about it.
2. What We Collect — At a Glance
The table below is a summary. Each row is explained in full in the section it points to.
| What | When | Why | Kept for |
|---|---|---|---|
| Installation and device identifiers Random, generated by the Application and by our server (§3) |
First launch | To keep your data without an account and to tell installations apart in statistics | Until you uninstall or ask us to delete them |
| Account (optional, §4) Name, email address and the sign-in provider's user id |
Only if you sign in with Google or Apple | To keep your data on every phone you sign in on | Until you delete the account; then wiped at once and the empty record removed after 30 days |
| Photos you upload (§6) Plus a note of which terms you accepted |
Only if you upload one | To review and publish them in the catalogue | Published: indefinitely. Rejected or withdrawn: files deleted 30 days after the decision |
| Your garage (§7) Your cars, their photo, diary, reminders |
Only if you add a car | To keep your service diary and send the reminders you set | Until you delete the car or the account |
| Reports, feedback and suggestions (§5) Name and email only for photo complaints |
Only if you send one | To investigate and answer | Indefinitely, as a moderation record; contact details removed on request |
| Favourites, saved searches, likes (§8) | As you use them | To show you what you saved | Until you remove them or delete the account |
| Catalogue pages you open (§8) | As you browse | Kept by our server as a viewing history (the latest 100), and on your phone as "Recently viewed" | Server: until you delete the account or ask us. Phone: until you clear it or uninstall |
| Regional settings (§9) Country, currency, unit system |
Only if you choose them | To show prices and measurements your way and to pick the market for price insight | Until you delete the account or ask us |
| Usage analytics (§10) Screens opened, actions taken, requests, errors |
Continuously | To find bugs and see which parts of the Application are used | Raw records: up to about 4 months. Daily activity: 400 days. Daily totals: indefinitely, without identifiers |
| IP address (§10) And an approximate country and city derived from it |
Every request | Abuse prevention, rate limiting, coarse regional statistics | Up to about 4 months |
| Push token and notification settings (§11) | Only if you enable notifications | To deliver the notifications you chose | Until you disable them or uninstall |
| Notification centre (§11) The notifications you were sent |
Whenever one is sent | To show them again in the Application | 90 days |
| Advertising consent (§12) | If your region requires a consent form | To decide what advertising and analytics are allowed | Kept by the Google consent SDK on your phone; our server records only "granted" or "denied" with each analytics record |
| Purchase records (§13) Store transaction identifiers, plan, status and dates — never your card details |
Only if you buy Premium | To switch the ads off and keep Premium working after a reinstall | While Premium is held by your device or account; anonymised afterwards and deleted after 3 years |
| Vehicle lookups (Premium, §14) The number plate or VIN you searched, the country, and what the registers answered |
Only if you search | To answer the search and keep your list of past searches | Your list: until you delete it or the account. Our log, with the plate or VIN masked: 90 days |
| Car recognition (Premium, §15) The photo you take or pick, what was recognised, and your feedback |
Only if you use it | To identify the car and keep your recognition history | Photo: 30 days, or until you delete it. The rest: unlinked from you after 30 days and kept as anonymous statistics |
| Price insight requests (Premium, §16) Which car, which country, which language, the outcome |
Only if you ask for a price | To count the daily limit and run the feature | Unlinked from you when you delete the account; the price answers themselves are not personal |
We do not sell your data, do not build advertising profiles of you ourselves, and do not send marketing email. Advertising is served by Google AdMob under its own policy and, where your region requires it, only with your consent — see section 12.
3. Guest or Account: How We Know It Is You
Three identifiers can be attached to what you do in the Application. None of them is your phone's serial number, IMEI, advertising ID or any hardware identifier, and none is shared with third parties for their own purposes.
- An installation identifier, a random value the Application generates on first launch and sends with every request. We use it only in statistics — to count installations, sessions and daily active users. Our server does not trust it for anything else.
- A device identifier and secret, generated by our server when the Application first registers. The identifier is sent with every request; the secret proves it is really your installation, is kept in your phone's secure storage, and is stored on our side only as a one-way hash. Everything you do as a guest — favourites, garage, uploads, reports, purchases — is tied to this identifier.
- Your account, if you sign in. From then on your data belongs to the account rather than to the device, and appears on every phone you sign in on.
Uninstalling and reinstalling the Application produces new identifiers. Guest data stored under the old ones is no longer reachable from your device — it stays on our server until deleted under section 21 or on request. With an account, signing in brings your account data back.
When you sign in on a phone for the first time, that phone's guest data — favourites, saved searches, reports, uploaded photos, garage cars, regional settings and Premium purchases — is moved into your account once. A phone can pass its guest data to one account only: if someone else already signed in on it, nothing is moved, and the Application tells you so.
4. Your Account (Optional)
You can sign in with Google (on Android and iOS) or with Sign in with Apple (on iOS). We receive from the provider, and keep:
- the provider's user identifier for you, which is how we recognise you next time;
- your email address, only if the provider confirms it is verified. If you choose Apple's Hide My Email, we receive a private relay address and do not treat it as your address — such an account has no email on file;
- your name and, from Google, your profile picture address, taken once when the account is created;
- the devices you are signed in on (device identifier, platform, model, app version) and when each sign-in started and was last active.
We never see your Google or Apple password. Signing in uses short-lived access tokens (15 minutes) and refresh tokens that the Application keeps in your phone's secure storage; on our side only a one-way hash of each refresh token is stored. A sign-in expires after 60 days without use and 180 days at most.
Accounts are never merged. If you sign in with a second provider whose verified, non-relay email address matches your existing account, that provider is added to the account; otherwise a separate account is created. You can add the second provider yourself from the account screen.
From the account screen you can see and end your sign-ins on other devices, sign out everywhere, and delete your account. Deletion is permanent and takes effect at once — see the Data Deletion page for exactly what is removed. To correct your name or receive a copy of your account data, write to us (section 22); our server keeps a complete export of an account for this purpose.
When a new account is created, our operator receives a notification saying only the provider (Google or Apple) and the platform — no name, email or identifier (section 18, Telegram).
Sign-in itself is provided by Apple and Google under their own privacy policies: Apple, Google.
5. Information You Provide
Several features let you send us something. All of them are optional, and none is needed to browse the catalogue.
Photos
A photo you upload to the catalogue is handled as described in section 6; a photo you send for car recognition as in section 15; a photo of your own car in the garage as in section 7. Photos are chosen through your phone's own picker, which needs no permission to your photo library. The camera is used only for car recognition (section 15).
Reports about content
You can report a user photo (from the photo feed or a car's gallery) or report an error on a generation page. A report records the reason you chose, any comment you wrote, which item it was about, and the device — and, if you are signed in, the account — that sent it.
Reports about photos require your name and email address. A complaint about a photo may be a copyright claim, and a copyright claim has to be answerable to a real person. If you are signed in, the Application fills these in from your account and lets you change them. Reports about catalogue data need no contact details.
Feedback
Profile → Support → Write to us sends a message with a subject you choose (bug, idea, missing car, thanks, other). A name and email address are optional; leave them if you want a reply. My requests shows the status of everything you sent and any reply from us.
Car suggestions
If car recognition cannot find a car in our catalogue, you can suggest it: make and model, optionally years and a comment. The suggestion is linked to your account and to that recognition's photo for as long as the photo is kept.
What our operator sees at once
When a report, feedback or suggestion is saved, our operator receives a notification through Telegram with the reason, the platform and app version, and the first 300 characters of what you wrote — never your name, email address or any identifier. See section 18.
6. Photos You Upload to the Catalogue
Location metadata is removed before anything leaves your phone, and again before anything is stored. Phone photos normally carry EXIF metadata including GPS coordinates, the camera serial number and the exact time of capture. The Application re-encodes the photo on your phone (at most 4096 pixels on the longest side, as a JPEG with a new file name), which discards that metadata; our server decodes and re-encodes it once more. It never reaches our storage and is never published. A photo of your own car cannot reveal where you keep it.
The rest of the process:
- Nothing is published automatically. Every upload arrives with the status "pending review" and is invisible to other users until a moderator approves it.
- You confirm the photo is yours to give. The Application shows you the upload terms and records which version you accepted, so it is always clear what you agreed to.
- Accepted formats are JPEG, PNG and WebP, at least 400×400 pixels and up to 10 MB. We store a fingerprint (a SHA-256 hash) of the processed image so the same photo is not reviewed twice from the same device. Uploads are limited to 20 an hour, 100 a day and 20 per generation for each device.
- You can withdraw a photo from My photos: with an account from any of your phones, as a guest from the phone that uploaded it. The Application also keeps a one-time management key for each upload in your phone's secure storage; we store only its hash.
- Approved photos are published in the catalogue alongside the car they show — in the photo feed, in the car's gallery and on the home screen — and are served through a content delivery network.
If a photo is rejected or you withdraw it
The image files are deleted from storage 30 days after the decision. The database record is deliberately kept, without the image, because it holds three things that must survive:
- the fingerprint, so a rejected photo cannot simply be uploaded again
- the reason for rejection, which is what you were told
- the moderation history, which is the case file if the photo was ever the subject of a complaint
This record contains no personal data beyond the device or account that uploaded it. It can be removed on request — see section 22. A photo we hid from the catalogue (rather than rejected) keeps its files until it is deleted.
7. Your Garage
The garage is a private place for your own cars. Nothing in it is published or shown to other users; our operator can see it when handling a support request. It works as a guest or with an account, and holds whatever you choose to enter:
- Cars — a nickname or the catalogue car it is, year, colour, engine and drivetrain details, VIN and number plate if you enter them, mileage, purchase date and price, currency, free-text notes, and the standard reminders you accept. Up to 20 active cars; archived cars keep their diary.
- A car's photo — re-encoded as JPEG with all metadata removed, up to 10 MB. It is not moderated and not published: the address is given only to you and to our operator, and the file lives under a long random name in our storage.
- Diary entries — services with parts, fuel, expenses, mileage readings, inspections, tyres and notes, with dates, amounts and currencies.
- Reminders — by date, by mileage or both, with the hour of day you want them (section 11).
- Recall notices — matched to your car's generation or modification from recall information we enter ourselves. Nothing about your car is sent anywhere to find them.
Statistics (costs, consumption, cost per kilometre) are computed from the diary. The reminder scheduler uses the time zone and reminder hour of your device — with an account, of the device you used most recently — so that a reminder arrives at the hour you chose.
Adding a car during the first-launch onboarding creates it in the same way. When you sign in for the first time on a phone, its guest cars move into your account. Deleting a car deletes its diary, reminders and photo; deleting your account deletes every car in it at once, including the photo files. A copy of the garage is kept on your phone so that it opens without a network; it is removed when you sign out choosing Erase from this phone or delete the account.
8. Favourites, Saved Searches, Likes and History
Some of this lives on our server, some only on your phone. The distinction matters for what follows you to another phone and for how you delete it.
On our server, under your device or account
- Favourites (bookmarks) — the brands, models and generations you saved, and when. The number of people who saved a car is shown on its page; who they are is not. Clearing favourites in Settings deletes them on our side too — with an account, on every phone.
- Saved searches — the filter values you saved, in a normalised form, up to 50 per owner. Since October 11, 2026 they belong to your account when you are signed in.
- Likes — the hearts you put on cars, on their pages and in the photo feed. Likes require an account. Counts are public; who liked is not.
- Viewing history — our server records which brand, model, generation and modification pages it served to you, with the time and a view count, keeping the latest 100. The Application does not read this list back: it exists so that your history can move into your account when you sign in and so that it can be included in a copy of your data. It is deleted with the account, or on request.
Only on your phone
- Recently viewed — the last 50 brands and cars you opened, kept by the Application itself. It does not follow you to another phone.
- Search history, the comparison tray and comparison history (the last 50 pairs) and the comparisons unlocked by a rewarded ad (section 12).
- Offline copies (Premium) — the generation pages and modification specifications you opened, with one main photo per generation, up to 200 generations, so that they open without a network.
- Settings — theme, language, notification prompts, counters that decide when an ad or a Premium offer is shown.
Each of these can be cleared in Settings → Data and storage, and all of them disappear when you uninstall. Signing out with Erase from this phone, or deleting your account, clears them too. We also count how many times each catalogue entry has been viewed; these counters are aggregated — they record that a brand was viewed, not who viewed it.
9. Regional Settings
In Settings → Region you can choose a country, a currency and a unit system. The currency converts catalogue prices, the units change how measurements are shown, and the country is the market used for price insight (section 16) and the default country for a plate lookup.
- Until you choose, nothing is stored: our server computes a default from the country your device reports (or, where our network edge provides it, the country of your connection) and sends it back without recording it.
- Once you choose, one record is kept — for your account if you are signed in, otherwise for your device. At your first sign-in on a phone, the phone's choice moves into the account unless the account already has one. The record is deleted at once when you delete the account.
- Exchange rates come from the public feeds of the European Central Bank and the National Bank of Ukraine. Fetching them involves no data about you.
The language you choose for the Application stays on your phone, but it is also sent to our server as your device's locale so that notifications arrive in that language.
10. Information Collected Automatically
Your device record
Alongside the device identifier (section 3) we store what your device reports when the Application starts: platform (iOS or Android), app version and build, operating system version, device model, language, country or region, and time zone, plus the push token if you enabled notifications and the time the device was last seen (updated at most hourly). These let us keep an old app version working, tell whether a bug affects one platform or both, send notifications in your language at the right local hour, and offer the right regional defaults.
Request log
Our server keeps a sample of the requests the Application makes — about one in ten of the successful ones, and every request that failed or was slow, because those are the ones worth fixing. A record holds the route that was called (as a template such as "brand detail", never a name or a plate you typed), the method, status and error code, how long it took, your platform, app version and build type, languages, the installation, device and account identifiers, your IP address with the approximate country and city derived from it, the user agent string, the session, and your advertising-consent answer (section 12).
Records are stored in monthly sets and a set is deleted once the whole month is older than 90 days — so a record lives between 90 days and about four months.
Usage events
The Application reports what you do in it as named events with short codes: a screen opened, a paywall shown, a plan selected, a car added to the garage, a notification opened, an ad shown or skipped, a search made, a consent answer given, and so on. Events carry codes only — never free text, names, plates, VINs or tokens — together with the platform, version, country, session, consent answer and the installation, device and account identifiers. They are kept in the same monthly sets as the request log. From them we compute daily totals per event, which are kept indefinitely without identifiers.
Activity and statistics
- Daily activity — one row per installation and day (platform, whether a debug build), kept for 400 days, from which we count daily, weekly and monthly active installations and sessions.
- Install cohorts — the day each installation was first seen, kept indefinitely so that retention can be computed.
- Catalogue view counters — how often each entry was viewed, per day for 400 days and in total indefinitely; aggregated, with no identifier.
- Server error log — one row per kind of error per day with a count, kept 30 days; email addresses, tokens, VINs, IP addresses and URL paths are removed before writing.
Firebase
The same usage events are also sent to Google Analytics for Firebase, with its own device-level identifiers. If the Application crashes, Firebase Crashlytics collects diagnostics — device type and OS version, app version, the time, the stack trace and the name of the last screen you opened. Firebase Performance Monitoring records app start, screen rendering and network request timings. Where your region requires a consent form (section 12), what Firebase may store follows your answer. These services are governed by Google's privacy policy.
IP address
Every request to our servers carries your IP address, as every internet request does. We use it for abuse prevention and rate limiting (for example, how many devices may be registered or reports sent from one address), and we store it with the request log, with an approximate country and city, for the period above. We do not store it on your device or account record.
11. Push Notifications and the Notification Centre
If you allow notifications, your device gives us a push token. On both platforms the token is issued by Google's Firebase Cloud Messaging (on iOS, the Application hands Apple's token to Firebase), so Google carries every notification to your device. We store the token against your device identifier.
What we send
Notifications are grouped into six categories, each with its own switch in Profile → Notifications. All are on by default.
| Category | What arrives |
|---|---|
| My photos and reports | The outcome of a photo you uploaded (approved, or rejected with the reason); the answer to a report you sent. |
| Garage reminders | A reminder whose date or mileage has come up; once a month, a nudge to update the mileage of a car with a mileage reminder; three days after you add a car without reminders, a suggestion to set some up. |
| Recalls | A recall notice matching a car in your garage. Sent immediately, even in quiet hours. |
| Saved cars | A daily digest of new photos of the cars you saved; a new generation of a brand or model you saved. |
| Editorial | The car of the day, at the hour of your local time we set; a new editorial collection. |
| Promotions | Messages from us about the Application and Premium, sent as campaigns by our operator; an automatic reminder if you have not opened the Application for 14 days (at most once a month); once, a suggestion to add a car if your garage is still empty a week after the first launch. |
Promotional notifications are limited to one a day and three a week, and respect quiet hours (22:00–09:00 in your device's time zone, when all notifications except recalls, the car of the day, garage reminders and the saved-cars digest wait until morning). A campaign may be addressed to a group of devices chosen by platform, language, whether they have Premium or a garage, which brands or models they saved, app version, how recently they were active and whether they are signed in — all computed on our server and never shared with advertisers. With an account, personal notifications go to every device you are signed in on.
A notification carries a title and text (which may name your car or your reminder, or give the reason a photo was rejected), a link into the Application and sometimes an image from our servers; this is what Firebase and Apple see in transit. Nothing else about you is sent with it.
Your controls
- Each category can be switched off; the switches and your reminder hour are stored per device on our server.
- The All notifications switch, or uninstalling, deletes the push token on our server. If you only block notifications in your phone's settings, the token stays until a delivery fails and the messaging service reports it dead.
- We do not send email, and we do not sell or share push tokens.
The notification centre
Every notification sent to you is also kept as a row in the notification centre — the bell in the Application — where it is shown for 30 days and marked read or opened. With an account, reading on one phone marks it read on your others. Rows are deleted after 90 days.
12. Advertising and Your Consent
The free version of the Application shows advertising served by Google AdMob: a banner at the bottom of brand, model, generation, news and collection pages; a full-screen ad occasionally after you close a brand, model or generation page; native ads laid out as posts in the user photo feed; and a rewarded video you may choose to watch to open one comparison without Premium (up to three a day). Premium removes all of it — no ad is even requested.
The consent we ask for
- European Economic Area, United Kingdom and Switzerland. Before any ad is requested, the Application shows Google's consent form (the User Messaging Platform). You can accept, refuse or choose purposes individually. You can change your answer at any time from Settings → Privacy settings.
- iOS. After the consent form, iOS asks whether the Application may track you (App Tracking Transparency). Refusing means ads are not personalised.
- United States. In states with an opt-out right, no form is shown at launch; Settings → Privacy settings lets you opt out of personalised advertising and of the sale or sharing of your information.
- Elsewhere no form is shown and ads may be personalised according to your device's advertising settings.
Your answer is stored on your phone by Google's consent SDK; we do not keep a copy of it. From it the Application derives three things: whether AdMob may request ads and personalise them; what Google Analytics for Firebase may store (its consent mode is set to "denied" until you answer); and the consent flag it sends with analytics to our server, which is recorded with each analytics record. We record the outcome of the form — the region, whether you granted, refused or partly granted, and whether it was shown at launch or reopened from Settings — as a usage event.
What advertising sees
AdMob collects data under Google's policy: your device's advertising identifier (the Android Advertising ID, or the IDFA on iOS if you allowed tracking), IP address, device and app information, and interactions with ads. We do not receive your advertising identifier and do not pass AdMob anything about you — not your account, your garage or your searches. Ads are not selected or endorsed by us. Our publisher identification is published at carcatalog.app/app-ads.txt.
You can also limit personalised advertising in your device settings.
Android: Settings → Google → Ads → Delete advertising ID or opt out of personalisation.
iOS: Settings → Privacy & Security → Tracking (disable), and Settings → Privacy & Security → Apple Advertising → turn off Personalised Ads.
How often the full-screen ad appears, when the Premium offer sheet is shown after ads, and which comparisons a rewarded ad unlocked are counted on your phone only.
13. Purchases and Premium
Premium removes advertising and unlocks comparison without limits, the vehicle lookup (section 14), car recognition (section 15), price insight (section 16) and offline copies. It is sold as an auto-renewing weekly or monthly subscription, or as a one-time lifetime purchase, through Google Play on Android and the App Store on iOS. The monthly plan currently comes with a free trial; introductory prices for the first week or month and win-back offers for former subscribers may also be shown. Prices are shown in the store in your local currency before you confirm.
Payment is handled entirely by Apple or Google. We never receive or store your card number, billing address or any other payment details. What we receive from the store, and keep on our server, is:
- the store's transaction and order identifiers and a service token that lets us ask the store about that purchase;
- which product, plan and offer you bought (regular, trial, introductory or win-back), its current status (active, cancelled, in a grace period, on hold, paused, expired, refunded), and the relevant dates;
- which store it came from and whether it was a test (sandbox) purchase;
- the notifications the store sends us about the purchase — renewals, cancellations, billing problems, refunds — so Premium switches on and off at the right moment.
A purchase is linked to the device that made it and, if you are signed in, to your account, so that it works on your other phones. A guest's purchase works on that phone; the first account to sign in there adopts it. If you sign in with a different account on a phone that holds a purchase, the Application may offer to transfer it — only with your confirmation, after which the previous owner loses it. A purchase can be held by one owner at a time; Restore purchases in Settings brings it back after a reinstall on the same store account.
Whether you qualify for a trial or a win-back offer is decided by the store from your store account's history. When the Application shows you an offer is decided by counters on your phone (launches, paywall closes); nothing about that is sent to us except the usage events of section 10. After a confirmed purchase, or when you have used the garage a few times, the Application may show your platform's standard "rate this app" prompt; whether it appears is up to the store.
Subscriptions renew automatically until cancelled. Cancelling, pausing, changing or refunding a purchase happens in your Google Play or App Store subscription settings — uninstalling the Application or deleting your data on our side does not cancel a subscription. Refunds are decided by the store under its rules; when a store refunds or revokes a purchase, Premium ends on our side too.
If our support team grants Premium manually — for example to compensate a problem — that is recorded with the reason, and it can be withdrawn the same way. We may also block Premium for an account or device that abuses it (section 23).
14. Vehicle Lookup by Plate or VIN
With Premium and a signed-in account you can look up a car by its number plate or its VIN (vehicle identification number) in a country you choose. Because a number plate can be personal data in some countries, we treat what you type as personal data throughout. Searches are limited per day (currently 20 per account); the Application shows the current limit.
Where the answer comes from
Our server asks free public open-data registers of the country you chose and, for a VIN, a few services that cover any car. Depending on the country these include the open data of the Ministry of Internal Affairs and of the National Police of Ukraine (data.gov.ua), the Israel Ministry of Transport (data.gov.il), the Netherlands' open vehicle data (RDW), the Czech vehicle register, the UK DVSA MOT history service, the US National Highway Traffic Safety Administration (VIN decoding and safety recalls) and the New York State DMV (data.ny.gov). The Application lists the sources behind each answer, and some sources or countries may be unavailable at times.
Only the plate or VIN leaves our server. The registers are asked by our server, not by your phone, so they never receive your name, email, account, device identifier or IP address. Where a service requires an access key, the key identifies our Application, not you. The Ukrainian registers are downloaded to our server in advance and searched there; a VIN may still be sent to the services that decode any VIN.
An answer describes the vehicle: make, model, year, colour, fuel and engine, inspections and mileage readings, registration events, open safety recalls, and whether it is listed as stolen or wanted. It does not contain the owner's name or address. About the owner, a Ukrainian registration event says only whether it was a private person or a company, and the region (oblast) — nothing more precise is kept even on our side.
What we keep
- Your list of searches. Each search that found a car is saved to your account: the plate or VIN, the country, the answer as it was, and when and how many times you searched it. Only you can see it, and only an account (not Premium) is needed to open it. You can delete one entry or the whole list in the Application; the latest 200 are kept and older ones are removed. Deleting your account deletes it at once, and a copy of your account data includes it.
- A log of attempts, masked. Every search is logged with the plate or VIN masked (for example AA****BB) — the full value cannot be recovered from it — along with the outcome, which registers answered and how long they took, your account and your device identifier. We use it to count the daily limit, prevent abuse and spot a register that has stopped answering. It is kept for 90 days. If you delete your account, the rows stay until they expire, without the link to you.
- Register answers, briefly reused. What a register said about a plate or VIN is stored for a limited time — 24 hours for a plate, 7 days for a register's view of a VIN, up to 180 days for what a VIN says about how the car was built, and a few hours for "not found" — so that searching the same car again does not ask the register again. These copies are not linked to who searched.
Accuracy and use
Registers can be incomplete or out of date, and an answer is only what they published. The lookup is for checking a car — before buying it, say — not for finding out about the people who owned it; the Terms of Service restrict it to lawful purposes.
15. Car Recognition by Photo
With Premium and a signed-in account you can take or pick a photo of a car, and the Application tells you its make, model and generation and finds it in the catalogue. The daily limit (currently 10 photos a day) and how long your history is kept (currently 30 days) are settings on our side that may change; the Application always shows the current values. The limit is counted per account and per device, and a day starts at midnight in your device's time zone.
How a photo is handled
- The camera. The Application opens the camera only when you tap the button to take a photo. On iOS it asks for permission to use the camera, and you can refuse. On Android the picture is taken by your phone's own camera app, which is given a one-time place to write the file; the Application does not request camera permission at all.
- On your phone. Before sending, the Application scales the photo down so that its longest side is at most 1600 pixels and re-encodes it.
- On our server. We first remove the photo's metadata (EXIF), including any GPS location. We then store the photo and a small thumbnail, and send the photo to an AI provider, which identifies the make, model and generation. Our server matches that answer to our catalogue.
- No plates, no people. The AI is instructed not to read out number plates or describe people, and our server removes any text that looks like a number plate from its answer.
Who receives the photo
Our server sends the photo to one or more of these AI providers, depending on our current configuration — a main model, with others as fallbacks: Google (the Gemini API, on its paid tier), OpenAI and Anthropic. A fourth provider, DeepInfra (the open-weight Qwen3-VL model), is configured as an alternative and is used only if we enable it. To compare quality, a share of photos may additionally be sent to a second model in the background; its answer is only recorded, never shown. They process the photo for us, as our processors. Only the photo and our instruction text leave our server — never your name, email address, or account or device identifiers. If we change providers, this list will be updated.
Your photo is not used to train AI models. Under their API terms these providers do not use our API traffic to train their models. They may keep it for a limited time to monitor for abuse, under their own policies. We never use a free tier that trains on the data sent to it.
What we keep
- Your recognition history. The photo and its thumbnail are kept for the retention period above, as your recognition history in the Application. With them we keep the result — what was recognised and the matching catalogue entries — your feedback if you give it (whether it was the right car, and the generation you chose), and technical details: the time, the model that answered, how long it took and what it cost us. The model's raw answer is removed after 90 days. Only an account (not Premium) is needed to open the history.
- Deleting an item. You can delete any item from your history at any time; its photo is deleted at once and the rest of the item is hidden from your history and anonymised on the usual schedule. Deleting an item does not give you back that day's attempt.
- After the retention period the photo is deleted, and the record is unlinked from your account and device and kept only as anonymous statistics.
- Our testers' photos. Photos taken by our own internal testers may be kept longer, in a set we use to evaluate recognition quality. Photos from anyone else are never added to it.
Suggesting a car we do not have
If the car is not in our catalogue, you can suggest it: the make and model, optionally the years and a comment, together with a link to that recognition's photo for as long as the photo is kept. A suggestion is linked to your account and is reviewed by our team; our operator is notified through Telegram with the make, model, years and the first 300 characters of your comment, without any identifier.
If you delete your account
Your recognition photos are deleted, and so are your suggestions. Your recognition history is removed with the account: until the emptied account record is removed, the history is kept, unlinked from you, only so that deleting and re-creating an account cannot reset the day's limit.
16. Price Insight
With Premium and a signed-in account you can ask what a modification sells for on the market of your country (section 9). An AI model with web search looks through car listing sites and answers with used-car prices by year, new-car prices where the car is still produced, a trend, a short summary in your language, and the sources it used.
What leaves our server
Our server sends the AI provider the brand, model and modification (or generation and fuel type when the search is widened), the country and currency of the market, the websites it should prefer or avoid, and the name of the language for the summary. Nothing about you is included — no name, email, account, device identifier or IP address. Depending on our configuration the request goes to OpenAI first and to Anthropic as a fallback; Perplexity is configured as a further alternative and used only if we enable it. The summary is written by an OpenAI model. These providers act as our processors and do not use our API traffic to train their models.
What we keep
- The answer itself is a snapshot for that modification and country, shared with everyone who asks about the same car in the same country for up to 7 days (24 hours if the listings were too few). Snapshots are not linked to anyone; older ones are kept so that a trend can be shown, and our operator can hide or delete them.
- Your request journal — for each request: when, which modification, which country and language, the outcome, and whether it counted against your daily limit. It is used to count the limit, prevent abuse and track our costs. A copy of your account data includes it. When you delete your account the journal is unlinked from you at once; the rows remain, tied to the device's daily window, so that deleting and re-creating an account cannot reset the limit.
The daily limit (currently none) and the other limits are settings on our side and may change; the Application shows the current values. Sources open in your browser under their own terms; we report only the website's domain when you open one.
17. Feature Availability, Testers and Gradual Rollout
Some features — car recognition, price insight and the vehicle lookup today — can be switched on gradually: for a share of installations, for certain platforms, countries, languages or app versions, or on a schedule. To decide, our server gives every account and device a stable place from 0 to 99, computed from its identifier, and compares it with the current percentage. Once a feature has been shown to you, that is recorded as a grant for your account and device so that it does not disappear when the share is lowered. Grants are removed when a deleted account is purged, and our operator may reset them.
We may also enable or disable a feature for specific accounts — our own testers, or a support case — and we look at how installations with and without a feature behave, as aggregate numbers. The Application asks our server which features apply to you at every start and after you sign in or out, and keeps the last answer on your phone.
18. Third-Party Services
These companies process data for us or receive it as described. Each acts under its own privacy policy for what it collects itself.
| Service | What for | What it receives |
|---|---|---|
| Google AdMob and the User Messaging Platform | Advertising in the free version; the consent form (§12) | Advertising identifier (with consent), IP address, device and app information, ad interactions, your consent choices |
| Google Firebase: Analytics, Crashlytics, Performance Monitoring, Cloud Messaging | Usage statistics, crash and performance diagnostics, delivery of push notifications (§10, §11) | Usage events and Firebase's own identifiers, crash reports, timings, the push token and the content of each notification |
| Google Play Services, Google Sign-In, Google Play Billing | Sign-in on Android and iOS, purchases on Android, in-app review and update prompts | What Google itself collects when you sign in or buy; we receive only what §4 and §13 list |
| Apple: Sign in with Apple, StoreKit, push delivery | Sign-in and purchases on iOS; carrying notifications to iPhones | What Apple itself collects; we receive only what §4 and §13 list |
| DigitalOcean | Hosting of our server and database (Frankfurt, Germany) and of all photos (Spaces object storage, Frankfurt), with its content delivery network | Everything stored on our side, as our hosting provider |
| Cloudflare | Protection and delivery of the website carcatalog.app, and its visit statistics — Cloudflare Web Analytics (§20) | The IP address and request details of visitors to the website |
| Telegram | Notifications to our operator: new account (provider and platform only), new report, feedback or car suggestion (reason, platform, version, the first 300 characters of your text), purchase and system events, aggregate daily statistics | The text excerpts above. Never a name, email address or identifier |
| OpenAI, Anthropic, Google (Gemini API); DeepInfra and Perplexity if enabled | Car recognition (§15) and price insight (§16), as our processors | Recognition: the photo and our instructions. Price insight: the car, the country, the currency and the summary language. Never anything about you |
| Public vehicle registers listed in §14 | Vehicle lookup | The plate or VIN searched, from our server |
| European Central Bank, National Bank of Ukraine | Exchange rates (§9) | Nothing about you |
| News publishers | Automotive news in the Application | A news item's cover image is loaded by your phone from the publisher's own server, which therefore sees your IP address; opening an article's source opens the publisher's website in your browser |
We do not send marketing or transactional email of any kind. The only email you may receive from us is a reply to a report, a request or a message you sent us first.
19. Location Data
The Application does not request location permission and does not access your device's GPS, precise location or background location — neither for features nor for advertising. On Android it declares only the internet, network state and notification permissions; on iOS it asks only for the camera (for car recognition) and for tracking (for advertising).
Three qualifications, stated plainly because they are the kind of thing a privacy policy should not bury:
- Approximate location from IP. Your IP address implies a rough country and city, and we store that with the request log for the period in section 10. This is country- and city-level at best — it is not your address and not a coordinate.
- Country from your device. The Application reports the country or region your phone is set to; we use it for regional defaults and for the market of price insight (section 9).
- Location in photos is removed, not read. A photo you upload, send for car recognition or add to your garage may contain GPS coordinates in its metadata. The Application and our server strip that metadata before storing anything and never record its contents. See sections 6, 7 and 15.
20. The Website and Cookies
The Application itself does not use cookies; the third-party services of section 18 may use cookies or similar technologies on your device under their own policies.
The website at carcatalog.app is a set of static pages that sets no cookies of its own. It is served through Cloudflare, which sees your IP address when a page loads and may set its own technical cookies to protect the site from abuse. Cloudflare also counts the website’s visits for us with Cloudflare Web Analytics: which pages were viewed, the referring site, and the country, browser and type of device of a visit. It works without cookies, stores nothing on your device and does not identify you or follow you across other websites; we see only aggregate figures. Fonts, images and scripts of the website come from carcatalog.app itself.
Links on the website to the App Store and Google Play carry a campaign label, so that the stores can tell us how many installations came from the website; the stores report these numbers to us in aggregate only, and open under their own terms.
21. Data Retention
| Data | Retention | Then |
|---|---|---|
| Request log and usage events | Monthly sets, deleted when the whole month is older than 90 days (90 days to about 4 months) | Deleted automatically |
| Daily activity per installation | 400 days | Deleted automatically |
| Daily totals and install cohorts | Indefinitely | Aggregate numbers without identifiers |
| Daily catalogue view counters | 400 days | Deleted automatically; only aggregate totals remain |
| Server error log | 30 days | Deleted automatically; written without personal data |
| Account profile and sign-ins | Until you delete the account | Name, email and sign-ins deleted at once; the empty account record is removed 30 days later |
| Device record | While the installation exists | Deleted on request |
| Favourites, saved searches, likes | Until you remove them | Deleted immediately; all deleted with the account |
| Viewing history on our server | The latest 100 entries, until you delete the account | Deleted with the account or on request |
| Garage (cars, diary, reminders, photo) | Until you delete the car or the account | Deleted immediately, photo files included |
| Regional settings | Until you delete the account or ask us | Deleted immediately |
| Published photos | Indefinitely, as part of the catalogue | Removed if you withdraw them |
| Rejected or withdrawn photo files | 30 days after the decision | Files deleted; the record is retained without the image |
| Reports, feedback, suggestions and moderation records | Indefinitely | Retained as an audit trail, unlinked from a deleted account; deleted on request where no legal claim depends on them |
| Push token and notification settings | Until you turn notifications off or uninstall | Deleted |
| Notification centre rows | 90 days | Deleted automatically |
| Purchase records | While Premium is held by a device or account; anonymised when the owner is deleted | Deleted 3 years after the purchase last granted anything — the window in which refunds and payment disputes can still arise |
| Store notifications about purchases | 180 days once processed | Deleted automatically; the few that could not be processed are kept for diagnosis |
| Your vehicle lookup list | Until you delete it or the account; the latest 200 searches | Deleted immediately |
| Vehicle lookup log (plate or VIN masked) | 90 days | Deleted automatically; kept without the account link if the account is deleted first |
| Reused register answers (not linked to anyone) | A few hours to 180 days, by type | Deleted automatically |
| Car recognition photos and thumbnails | The retention period shown in the Application (currently 30 days), or until you delete the item | Deleted; deleted at once if you delete the account |
| Car recognition history Result, your feedback, time, model, latency, cost | The same period, linked to your account and device; the model's raw answer 90 days | Unlinked and kept only as anonymous statistics; removed with the account if you delete it |
| Suggested cars | Until you delete the account | Deleted with the account |
| Price insight request journal | Linked to you until you delete the account | Unlinked at once; rows kept for the daily limit and our cost accounting |
| Price insight snapshots (not linked to anyone) | Kept as history | Operator may hide or delete them |
| Feature rollout grants | While the account or installation exists | Removed when a deleted account is purged, or reset by our operator |
| Copies for recovery | Short-lived | Copies of the database kept for recovery may retain data for a short time after it is deleted from the live system; they are not used to restore deleted data |
Anything collected by third-party services is subject to their own retention policies, which we do not control.
22. Your Rights and Choices
Much of this you can do yourself, in the Application, without asking us:
- Favourites — remove them one by one, or clear them in Settings; saved searches — delete them in the Application; likes — tap the heart again.
- Garage — edit, archive or delete any car, entry or reminder; remove a car's photo.
- Vehicle lookups and car recognitions — delete any item, or the whole list.
- Photos you uploaded — withdraw them in My photos.
- Notifications — switch off any category, or all of them; change the reminder hour.
- Advertising — change your consent in Settings → Privacy settings where offered, or limit personalisation in your device settings (section 12); or remove ads with Premium.
- Regional settings, language, theme — change them in Settings.
- Data on your phone — clear recently viewed, search history, comparisons, the image cache and offline copies in Settings → Data and storage.
- Your account — see your signed-in devices, end any sign-in, sign out everywhere, add a second sign-in provider, or delete the account, on the account screen.
- Stop all collection — uninstall the Application.
For anything else you have the right to ask us to:
- Access the data we hold about you, and receive a copy in a portable format. For an account, our server prepares a complete export (profile, sign-ins, devices, favourites, viewing history, likes, regional settings, garage, lookups, recognitions, suggestions and price insight requests) that we send you on request.
- Correct anything inaccurate — including the name on your account, which the Application does not yet let you edit.
- Delete your data — see the Data Deletion page for exactly how, what is removed and what is not.
- Restrict or object to processing, and withdraw consent where processing is based on it.
How to reach us. If you have an account, write to help.catalog.cars@gmail.com from the email address on the account, or use Profile → Support → Write to us in the Application. If you have not signed in, please use Write to us in the Application: a message sent from the Application is linked to your installation, which is the only way we can find a guest's data — the Application does not show you a device identifier, and an email from an address we do not know cannot be matched to an installation.
We answer requests within 30 days. You may also lodge a complaint with your data protection authority (section 26).
23. Moderation and Enforcement
Because users can upload photos, we moderate. Every upload is reviewed before it appears, and anyone can report content they think should not be there. Our content rules are set out in the Terms of Service.
If content is repeatedly rejected or a device or account is used abusively, we may:
- Suspend uploading for that device, temporarily or indefinitely, while leaving the rest of the Application working — including the ability to report content. A suspension attaches to the account you sign in with on that device and stays on the device after you sign out or delete the account.
- Block the device entirely in serious cases.
- Block the account, which signs it out everywhere, or block Premium for an account or device that abuses purchases.
We record who took the decision, why, and when it was lifted, so that a decision can be reviewed if you appeal it. Our operator can see, for a device or account, its uploads, reports, purchases, lookups (with the plate or VIN masked in the log), recognitions, garage and the request log of section 10, including IP addresses for as long as that log is kept. Appeals go to help.catalog.cars@gmail.com or Write to us in the Application.
24. Children's Privacy
The Application is not directed at children under 13, and we do not knowingly collect personal data from them. Signing in, uploading photos, keeping a garage and sending reports are intended for users aged 13 and over.
If you believe a child has provided us with personal information, contact us and we will remove it promptly.
25. Security
- All traffic between the Application and our servers is encrypted in transit (HTTPS).
- Device secrets, sign-in refresh tokens and photo management keys are stored on our side only as cryptographic hashes. We cannot read them back, which means they cannot be leaked in a readable form. On your phone they live in the system's secure storage (Keychain or Keystore).
- Photo metadata is stripped on your phone and again on receipt, so location data is never written to storage in the first place.
- Garage photos are stored under long random names that cannot be guessed; the address is shown only to you.
- Administrative access is authenticated separately, rate-limited and journaled; the server's own error log is scrubbed of personal data before it is written.
- The Application does not write personal data to its logs, and plates, VINs and email addresses never reach analytics or crash reports.
No system is perfectly secure, and we do not claim otherwise. If you find a vulnerability, please report it to help.catalog.cars@gmail.com rather than disclosing it publicly, and we will work with you on it.
26. International Users and Legal Bases
The Application is available worldwide. Our server, database and photo storage are located in the European Union (Frankfurt, Germany). If you use the Application from elsewhere, your data is transferred to and processed there. The AI providers used for car recognition and price insight (sections 15 and 16), Google, Apple and Telegram are based in the United States or elsewhere and may process the data they receive there, under their own safeguards.
Why we process your data, and on what basis
| Purpose | Basis (GDPR) |
|---|---|
| Running the Application: your identifiers, account, favourites, garage, reminders, uploads and their moderation, the notification centre, regional settings, offline copies | Performance of a contract (the Terms of Service) |
| Premium: verifying purchases, the vehicle lookup, car recognition, price insight | Performance of a contract |
| Push notifications you asked for (moderation outcomes, reminders, recalls, saved cars, editorial) | Performance of a contract and your settings; promotional notifications on our legitimate interest, with a switch to turn them off |
| Security, abuse prevention, rate limiting, the request log and IP addresses, moderation records, blocks and appeals | Legitimate interests in a safe, working service |
| Usage analytics, crash and performance diagnostics, gradual rollout of features | Legitimate interests in improving the Application; where a consent form is shown, your consent for what Google may store |
| Advertising and its personalisation | Your consent where the law requires it (section 12); otherwise legitimate interests in funding the free version |
| Answering reports, feedback and data requests | Legitimate interests and, for copyright complaints, legal obligations |
| Keeping moderation and purchase records after deletion | Legal obligations and the establishment and defence of legal claims |
European Economic Area, United Kingdom and Switzerland. You have the rights listed in section 22. Consent can be withdrawn at any time without affecting the lawfulness of processing before withdrawal. You may lodge a complaint with your local supervisory authority.
California and other US states. You have the right to know what is collected, to request deletion and correction, and to opt out of the sale or sharing of personal information and of targeted advertising. We do not sell personal information. Personalised advertising served by Google AdMob may count as "sharing" for cross-context behavioural advertising under California law; you can opt out in Settings → Privacy settings in the Application and in your device's advertising settings (section 12). We do not knowingly sell or share the personal information of anyone under 16.
Ukraine. Processing is carried out in accordance with the Law of Ukraine "On Personal Data Protection". You may exercise the rights it grants by contacting us at the address in section 28.
27. Changes to This Policy
We may update this Privacy Policy. The effective date at the top of this page always shows the current version, and material changes will be announced in the Application before they take effect. Continued use after a change takes effect constitutes acceptance of the revised policy.
Previous versions: October 18, 2026 and October 7, 2026.
28. Contact Us
Questions about this policy, requests about your data, or reports of a problem:
Car Catalog
help.catalog.cars@gmail.comIf your request is about your own data and you have not signed in, please send it from Profile → Support → Write to us in the Application so that we can find your installation (section 22).
29. Your Consent
By using the Application, you acknowledge this Privacy Policy and the processing described in it, including processing by the third-party services listed in section 18. Where the law requires your consent — for personalised advertising, and for notifications — it is asked for separately in the Application and can be withdrawn there.