This Privacy Policy describes how the mobile app Lisvaro, developed by Luis Suñol Mateo (acform), handles information. It refers only to the Lisvaro app; the other acform apps have their own policy, and the acform.es website has its own. The conditions of use of the app are a separate document: the terms and conditions of use.
This is the most important point in this document, and almost everything that follows derives from it. The items you save, their prices and the whole history live in the local database of your own device. They are not uploaded to any server of ours, there is no user account, no sign-up, no login and no synchronisation between devices. The developer holds no copy of your data and cannot access it. Copies of yours may exist off the phone —the one Android makes in your own Google account and any you save by hand—, and they are explained in point 7. There is a single connection to a server of ours, and it carries none of the above: in order to query eBay listings, the app asks it for a temporary permission. That request carries neither which products you watch, nor your target prices, nor your history. It is explained in points 4 and 5.
The only information the user provides are the addresses (URLs) of the product pages they choose to watch, together with what they want watched on them: a target price, a discount percentage or simply that the product comes back on sale. If the page offers several versions of the product, also which one is followed. That information is stored on the device and is not sent anywhere. An address can also be saved without watching it, in the Wishlist: it keeps whatever the page published the day you saved it and is never consulted again, so while it sits there it generates no request to the shop at all.
To find out a product's price, the app downloads that product's page. That request is made directly by your phone, from your own Internet connection. There is no intermediate server of ours. We want this to be clear because it has a consequence you should know about:
LisvaroApp/1.0 (+https://acform.es/bot), which says who it is and links to a page explaining it. It sends no identifier of yours, no installation number, and nothing that would allow your device to be recognised between two requests. Some shops publish their prices through an interface meant for programs (an «API») instead of requiring the page to be read. Today that is the case with eBay. For eBay listings the app does not download the page: it asks eBay's interface server, api.ebay.com, for the figure. It is cleaner for both sides —a few pieces of data travel instead of a whole page, with its advertising and its images— but it is worth knowing how it differs from the above:
ebay.es —or from any of eBay's other marketplaces— and the request goes to api.ebay.com. It is the same company, but it is a different server, and we tell you because it is not visible. Reading eBay listings requires a permission granted by eBay, and that permission is requested from a server of ours at acform.es instead of being kept inside the app. It is safer for everyone: that way the credential does not travel in the installation file, where anyone could extract it.
Some shops do not publish the price in the page's code: their JavaScript writes it after loading. For those —and only for those, after the normal route has been tried— the app opens the page in the operating system's own browser (the WebView component that Android already has installed), reads the price and closes it. No window is opened and you are not interrupted.
This has consequences you should know about, and they are the same as if you opened that page yourself:
The site's robots.txt file is always requested on behalf of LisvaroApp, including when the page is going to be loaded by the browser, so that the exclusion any shop can request works on both routes.
Everything that follows is stored in the local database on your phone and nowhere else.
For each product you add: the name, the page address, the shop's domain, the currency, the image address if the page publishes one, the chosen variant if the listing has several, your target price or percentage, the checking frequency, the date it was added, the category you have put it in, which of the two lists it is on —tracking, Wishlist or both—, whether you have pinned it to the top and the position you have left it in. And a few technical items: its identifier at the shop if the price comes from an official interface, the second image address when the page publishes two, and how many checks in a row have failed, which is what decides when to try again.
For each price reading: the price, the currency, the availability and the date. If the page publishes a struck-through or previous price, that is stored too, so the discount can be calculated.
When a check fails, the reason for the last failure and a technical detail are also stored —for example “the shop did not respond” or “the price was not found on the page”— so that we can explain to you what happened.
Of each alert you set up: what kind it is —price, percentage or back on sale—, the figure you set, what the discount is calculated against, whether it is active and the date it last fired. That date exists so as not to repeat the same alert to you every day while the condition keeps being met, and it is deleted with the alert.
For each listing, what the shop publishes openly about the product is stored as well: its description, if it publishes one, and its average rating together with the number of opinions behind it. It is there so that you can recognise a listing months after saving it —above all in the Wishlist, where the name alone is not enough—, it is refreshed along with the shop and it is not used for anything automatic. No other page content is stored: neither the written reviews, nor the comments, nor the rest of the text.
In Settings you can write how you prefer the app to address you. It is used only to greet you at the top of your list.
Each listing takes a note of yours, written with the pencil on the listing itself. It is there to help you recognise a product whose published name means nothing to you: the shop calls it “House on Calle Altozano” and you think of it as “the one in Fuensanta with a garden”.
Android may include the app's data in the backup you have set up in your Google account, just as it does with every other app. That copy is yours and goes to your Drive: we do not see it, we do not receive it and we cannot access it. If you would rather it did not happen, you can turn it off in Android's backup settings.
In Settings you can save a file with everything the app stores about you —your products, their history, your alerts, your categories, your notes and the technical log of point 9— and choose where to put it: your Drive, this phone or wherever you prefer. The app does not enter your Drive and does not ask you for any account: it simply hands the file to Android's picker and you decide.
That file is yours and is not encrypted, so that you can open it or take it wherever you want. If you leave it in a shared place, anyone with access to that place will be able to see which products you follow.
It does not carry your settings —neither the name you may have written, nor the switches, nor the purchase—. Restoring a backup replaces your products and their history, and nothing else.
The app stores the address of the image that the page itself declares, not the image as part of your data. Display is switched off by default and you can turn it on or off whenever you like from the app's Settings.
The app keeps an internal technical log of what it does: when it has checked, which products it reviewed, how long it took and what failed. You can read all of it in Settings › App log.
The alerts —both price-drop alerts and alerts that a product is back on sale— are local notifications, generated by your own device when the condition you set is met. No push notification service is used, neither Firebase Cloud Messaging nor any equivalent external service. No server knows which products you watch or when you have been alerted.
So that there is no doubt whatsoever, Lisvaro does not collect, does not transmit and does not share:
The app contains no advertising and includes no analytics or tracking SDK that records your activity.
This refers to the app. The shop pages that the app reads have their own analytics, which act when the page loads —just as if you opened it yourself— and over which we have no control.
As all the data resides solely on your device, you have complete control over it:
Lisvaro is not specifically aimed at minors and does not knowingly collect data from them. Since the app collects no personal data from any user, no differentiated processing is carried out on the basis of age.
The General Data Protection Regulation (GDPR) grants you the rights of access, rectification, erasure, restriction, portability and objection. Since the developer does not receive, does not store and does not process any personal data of yours, these rights are guaranteed by default: you exercise them directly from your device, by deleting the data or uninstalling the app. If you would nonetheless like to contact the data controller, you may do so through the contact form or at the address given at the foot of this document.
If you are responsible for a shop or a website and want to know exactly what the app does when it reads a page, or you want to exclude your domain, the full information is on the acform.es/bot page.
This policy may be updated to reflect changes in the app or in applicable legislation. The version in force is always the one published at this address, and the date of the last update appears at the foot.
Last updated: 25 August 2026
Data controller: Luis Suñol Mateo (acform). For any question regarding this policy, including the exercise of your rights, use the contact form or write to lisvaro [at] acform.es (written this way on purpose, to hinder automated address harvesting).