Technical privacy notice updated November 8, 2026.
Your package stays in the browser
When you choose a .unitypackage, the browser reads it from your device. Decompression, parsing,
preview and export happen locally. The application does not upload the package, its models, textures,
materials, file paths or GUIDs to an extraction server.
Downloads
GLB files, ZIP archives, converted textures and diagnostic reports are created on your device and downloaded through the browser. If you choose a system file picker or disk-save prompt, your browser and operating system control the destination.
Downloaded diagnostic reports
A diagnostic report is created only when you press its download button. It may contain the package name, technical counts, file-type summaries, warnings, the currently selected asset path, application version and recent log messages. It does not contain model, texture, audio or archive binary payloads. The file remains on your device unless you choose to send it to support.
Automatic package-load error diagnostics
If reading, unpacking or preparing a package fails, the browser may send a small technical summary to this website. It contains only predefined error and file-format categories, the application build revision, broad size, duration and entry-count ranges, and a coarse browser family and desktop/mobile category. Sample-package errors are marked separately. It never includes package bytes, names, paths, GUIDs, raw error messages, stack traces, logs, full browser user agents, account details or persistent visitor identifiers. IP addresses are not stored in these diagnostic summaries; ordinary network requests and operational logs remain separate as explained below.
Matching error categories are counted together per day and retained for at most 30 days. Collection has request, group and storage limits (at most 100 MiB including the temporary storage copy). It is best-effort, does not interrupt local processing, and is disabled when the browser sends Global Privacy Control or Do Not Track. The full downloadable report described above is not sent automatically.
Website requests and operational logs
Loading the website necessarily sends normal web requests for HTML, JavaScript, CSS and images. The hosting infrastructure can receive routine connection information such as IP address, request time, requested URL, browser user agent and error status. This data is separate from the package being processed and is used for delivery, security and reliability.
Anonymous product analytics and cookies
We use Cloudflare Web Analytics to understand aggregate page visits and page-performance metrics. It does not access the contents of packages processed in the browser. Cloudflare states that Web Analytics does not use cookies or local storage for usage metrics and does not track individuals across websites.
If you close the language suggestion at the top of a page or pick a language in the menu, that choice is saved in your browser's local storage so the suggestion is not shown again. It is not sent to us.
While an export is running, the browser keeps a small marker in local storage with the export type, start time and progress count, never file names, so that an export cut short by a closed tab or a browser crash can be counted. The marker is removed when the export ends. When the Pro window is closed, the counters also note how long it was open and whether the email field or the currency was changed, never what was typed.
We also keep daily aggregate counters for product events such as choosing a package, completing local unpacking, opening a type of preview, opening a file in one of the VRM tools (which tool, and whether it opened, lacked avatar bones, was the wrong kind of file or failed), starting or completing an export, a safe error category, opening support, and the optional worked / something is wrong answer shown after a download, its selected issue category, whether missing textures were first noticed in the preview or after import, and clicks on the optional support-the-tool link (placement and export type). Size, duration and asset counts are recorded only as broad ranges. These counters do not contain package or asset names, paths, GUIDs, models, textures, logs, diagnostic contents, account identifiers or a persistent user/session ID.
To connect an export event with the page that introduced the current browser tab, the tab temporarily keeps only a coarse traffic-source category and a public landing-page path in session storage. This context is removed when the tab session ends and is not used to recognize a person or follow them across websites.
Optional return-visit measurement and app installation
Return-visit measurement is on by default. You can disable it at any time by unchecking the option in the website footer. This browser stores only the first measured visit date and the most recent measured visit date for this website, rounded to UTC calendar days. The marker expires after more than 90 days of inactivity and is replaced on your next measured visit. Where the optional Pro purchase is offered, the same option also keeps the last UTC calendar day on which this browser hit the free bulk-export limit, opened the Pro offer or started a checkout, so our counters can tell a first time from a repeat. Unchecking the option deletes these date markers; your preference remains on this device. There is no random visitor ID, cookie, fingerprint or cross-site tracking. Previously saved refusals are respected and are not replaced by this default.
The server receives only predefined categories: first observed or returning browser-day, a broad return-gap range and, for the Pro markers, whether it is the first time, again on the same day or again on a later day. The local dates are not transmitted. Counts are approximate: different devices, cleared storage, private browsing and simultaneous tabs can change the results. First observed does not mean a first-ever visitor. The converter works the same whether you enable this option or not.
We also count browser-reported app-installation events and page views in the installed app's standalone window, without a persistent identifier. These counts do not reveal who installed the app, do not include older installations, and are not supported by every browser. Our own product counters, return measurement and install counters are disabled when Global Privacy Control or Do Not Track is enabled. Cloudflare and ordinary hosting requests remain separate as described above. Aggregate product counters are retained for up to 400 days.
Sample package
If you press Try with a sample package, the browser downloads the public test fixture from this website. That request is an ordinary website download and does not expose any package from your device.
Third-party links
Guides may link to external documentation or communities. Opening those links is subject to the privacy practices of the external site.
Optional Pro purchase
Where the optional Pro purchase is offered, the email you enter is sent to this website to create a lava.top checkout, because lava.top requires a buyer email for the receipt. We pass it to lava.top and do not store the address itself. lava.top processes your email and the payment under its own terms and privacy policy; we never receive card or bank details.
So that you can restore Pro in another browser by email, we keep a keyed one-way hash of that email with the purchase. It matches only when the same address is typed again and cannot be turned back into the address without our server key. When you ask to restore Pro, the email you enter is used once to look up the purchase and, if there is one, to send a single-use link valid for 30 minutes through our email provider Resend, which processes the address under its own terms and privacy policy. We store only a hash of that link. Opening it gives the browser its own license code for the purchase. Restore requests are rate-limited per network and per address in memory for up to a day.
For each purchase we keep only a cryptographic hash of the generated license code, the keyed email hash described above, the lava.top contract id, the status (pending, paid or revoked), the invoice currency and amount, the coarse traffic-source category of the tab that started the checkout (for example search or direct) and timestamps. Unpaid checkouts are deleted after 48 hours; daily backups of this record are kept for 30 days. When a license is activated we also store, for up to 30 days, a salted one-way hash of the network it came from (the IPv4 address or the IPv6 /64 network), so unusually wide sharing of one code can be noticed; the address itself is not stored. Checkout and activation requests are also rate-limited per network in memory for up to a day.
The license code is saved in your browser's local storage together with a signed activation token; up to five recent unconfirmed checkout codes are kept there for up to 30 days so a payment can be confirmed later. To keep Pro working, the browser sends the code to this website at most about once a week. Local storage also keeps the free bulk-export counters (how many free bulk exports were used and when the last weekly one was used); they are not sent to us.
Our product counters for Pro are anonymous daily totals of predefined categories: for example that a paywall was shown or closed and at which step, a checkout was started, failed, sent to lava.top, created, paid or revoked (with currency and a broad time-to-pay range), a return from lava.top or a restore had a given result, or a free bulk export was used (and whether it was used after the weekly wait). They never contain license codes, emails, contract or payment ids, amounts or IP addresses.
Contacting support
If you contact support by email or Telegram, you choose what information to send. The relevant provider processes your account details and message under its own privacy terms. Support messages are used to answer the request, investigate reported problems and protect the service from abuse.
Privacy contact
Privacy and support requests can be sent to [email protected] or @blablakapr on Telegram.