Privacy Policy
Watch Register v1.x · Published by Aveneg Technologies, LLC
The short version
This application does not collect your data, because it cannot. There is no
server for it to send data to. Nothing you enter — watches, values, serial
numbers, photographs, documents, your passphrase — ever leaves the device it
is installed on. This is not a policy choice we could reverse later; it is
enforced by the application's Content Security Policy, which disables
fetch, XMLHttpRequest, WebSocket and every other network primitive at
the engine level. See the Security Overview for the technical detail.
Everything below exists to cover the few places data can touch someone other than you: buying the software, and asking us for help.
1. What the application itself collects
Nothing. No analytics, no telemetry, no crash reporting, no usage tracking, no update checks, no device fingerprinting, no advertising identifiers. The application makes no network requests of any kind, ever, under any circumstances. We do not know how many people use Watch Register, what watches are in anyone's collection, or whether you opened the app today.
Your register — including photographs and attached documents — is encrypted on your own device with a passphrase only you hold. We do not have a copy of it, a backup of it, or a way to decrypt it. If you lose your passphrase and your recovery key, we cannot recover your data, because we never had access to it in the first place.
2. If you purchase a licence
If Watch Register is distributed as a paid product, purchases are handled by a third-party Merchant of Record (for example Paddle or Lemon Squeezy), not by Aveneg Technologies, LLC directly. That processor collects what it needs to complete the transaction and comply with tax law — typically your name, email address, and payment details — under its own privacy policy, which governs that data. Aveneg Technologies, LLC receives confirmation that a purchase occurred and a licence was issued; we do not receive or store your full payment details. Contact the processor directly regarding data it holds about your purchase.
3. If you contact us
Email (bug reports, feature requests, a commercial licence question, or a security report) is received and retained like any other business correspondence, for as long as needed to respond and keep a reasonable record. We do not use it for marketing, and we do not sell, rent, or share it with anyone.
If you send a screenshot, log excerpt, or exported file to help diagnose a problem, that content is only ever what you chose to send — the application has no mechanism to transmit anything on its own. Delete anything sensitive from a file before sending it if you are not comfortable including it in an email.
4. What we cannot access, even if asked
Because your register is encrypted with a key derived from your own passphrase, and that key never leaves your device, there is no mechanism by which Aveneg Technologies, LLC could produce your data in response to a subpoena, a support request, or anything else. We are not holding it in escrow; we simply do not have it. This is the same design described in the Terms of Service and the Security Overview as "zero-knowledge" — the company literally does not know what is in your collection.
5. Children's privacy
Watch Register is not directed at children and is not intended for use by anyone under 18. We do not knowingly collect information from children, consistent with Section 1 above — we do not knowingly collect information from anyone.
6. Changes to this policy
If this policy changes, the version distributed with your installed build governs your use of that build, consistent with the Terms of Service. Material changes will be reflected in a new version of the application.
7. Contact
Questions about this policy, or about data held by a payment processor, purchasing platform, or support correspondence: privacy@watchregister.app.
Watch Register · watchregister.app · published by Aveneg Technologies, LLC. This policy describes the application's own conduct; it does not extend the privacy practices of any third-party payment processor.