Privacy, in plain language
Tailtint is made so that the main creative work stays on your device. When you choose a pet photo for the card maker or filters, the browser opens and edits that photo locally. We do not upload it to Tailtint, store it, inspect it, or use it to train anything. The exported PNG is made in your browser too. If you close or refresh the page, the working photo is gone from the tool unless your browser has kept it in normal local memory.
What we measure
We do not use cookies, ad pixels, or a fingerprinting script. We send a small event beacon when a page opens, a tool opens, a photo is loaded, an export is requested, an install is accepted, or the portrait link is clicked. Those beacons carry only the event name, page path, tool name where relevant, and selected template where relevant. They never carry image data, pet names, typed messages, or the contents of your card.
Like most web servers, our server logs record IP addresses and the pages requested. These logs help us keep the service working and understand whether the card maker is useful. They are not used to build advertising profiles. The service worker may cache the app shell, locally included fonts, and libraries on your device so the editor can work offline; this is browser storage for the app, not an account on our server.
Portrait orders are separate
If you choose the paid AI-assisted, hand-checked portrait option, you leave Tailtint for Fiverr. Your order, reference photos, messages, payment, and delivery there are covered by Fiverr’s terms and privacy practices. The Tailtint card maker does not receive those files. We say this clearly because “photos processed on your device” applies to the free browser tools, not to a portrait order you voluntarily place with an external marketplace.
Questions about this policy can be sent through pivlu.com. This page describes the current simple service: no accounts, no cookies, browser-local photo editing, a small anonymous measurement beacon, and ordinary server request logs.