Website analytics only. No product-side user records.

Peach uses standard website analytics only to understand traffic and performance. The product itself does not create accounts, collect or store IP addresses, or know who is using Peach. Purchases are handled privately by a third-party payment processor, and that buyer information is not passed into Peach product infrastructure. If you prefer, Peach also supports crypto payments as a more private checkout option.

Website analytics only

The Peach website uses generic, industry-standard analytics only to gauge traffic and measure site performance. That visibility is about how the website is doing, not about who is using Peach.

Used for aggregate traffic and performance measurement only.
Peach does not collect or store IP addresses.
Website analytics are not tied to product accounts because Peach has no product accounts.

No product identity layer

Peach does not create accounts, maintain user profiles, or keep a backend record of who is using the product. There is no Peach user database to correlate with analytics, licenses, or vaults.

No account creation is required to install or use Peach.
No hosted Peach vault service exists.
Peach has no idea which individual person is using a given installation.

Payments stay with the processor

Purchases are handled privately by a third-party payment processor. Licenses are generated and sent to your email there, and that purchaser information is not passed into Peach product infrastructure. Peach also supports crypto payments for people who prefer a more private checkout path.

Payment and checkout details stay with the payment processor.
Peach does not turn buyer records into product accounts because no product accounts exist.
License delivery does not create a Peach-side customer database.
If you want to reduce personal billing traceability, you can rotate and fund a wallet before paying with crypto.
A crypto payment still leaves an on-chain transaction record; Peach simply does not convert that payment into a product-side identity record.

Zero product infrastructure

Peach operates with effectively zero product infrastructure: no servers storing vaults, no account system, no user database, and nothing product-side to breach. Your vault stays local unless you explicitly export or sync it.

No central vault store exists.
No backend collects product telemetry.
No product-side record links vault usage to an email address, IP address, or named user.

In short: Peach can measure whether the website is healthy, but it does not run the kind of infrastructure that would let it identify product users, store vaults, or maintain a customer database behind the app.