Who this policy covers
This policy applies to the Keys Buddy website, download, account and licensing service, desktop application, and beta builds. Keys Buddy is the data controller for the information described here. Questions or requests can be sent to support@joshaquino.com.
This policy does not cover third-party websites or services that publish their own privacy notices.
Data we collect
We collect only the data needed to register, license, support, secure, and improve it:
- Account data: the email address you enter when downloading Keys Buddy or setting it up on a machine, the time you registered, one-way hashes of the machines registered to you, the application build and release channel, whether you opted in to product email and when, and any entitlement attached to your account if you later buy an add-on. Registration is required to use the application; the product-email opt-in is not, and is off unless you tick it.
- Invite and download records: the invite code used, the account associated with its redemption, the time of redemption, the terms version accepted, the requested build, operating system, and processor architecture, and the time a download link was issued. We use these records to enforce invite limits, support downloads, and monitor release access. A download-link record does not confirm that a transfer completed.
- Historic purchase data: where a paid early-access license was bought, the email address, order reference, product, price, currency, and purchase time. PayMongo processed those payments. Keys Buddy never received a full card number or security code.
- License data: license status, activation history, machine fingerprint, platform, device name, and application build. License keys are credentials and should not be shared.
- Beta enrollment and download data: the email address added to the approved tester list, whether that approval is active or removed, the email entered in the beta build, one-way hashes of that email and machine fingerprint in our records, the beta build identifier and release channel, the generated license, issue time and expiry, and a record that the approved email accepted the Beta Terms and acknowledged this Privacy Policy when downloading a build. The licensing service also stores the email on the beta license so support can identify the tester and recover the correct record.
- Support data: the messages and technical details you choose to send when asking for help.
- Website security data: ordinary request logs such as IP address, browser details, requested path, and time may be processed by our hosting and server providers.
- Product analytics: a pseudonymous install identifier, session identifier, event name, event time, application build, release channel, and platform.
Analytics and beta builds
Public releases send product analytics only after you enable analytics in the application. You can turn it off for future events in the application settings.
In a beta build, we compare the entered email with the approved tester list. If approved, we use the email and machine fingerprint supplied during enrollment to issue one email-associated, build-specific license and prevent repeated enrollment for the same beta. A new beta build identifier permits a new 30-day license. Removing an email blocks later issuance and online refresh. License processing is separate from product analytics: email addresses and license keys are not added to analytics events.
Some clearly identified beta builds require product analytics as a condition of participating in that beta. The beta invitation or download notice will identify the requirement and provide the beta terms and this policy before enrollment. If you do not agree, do not request a beta license or use that beta build. You can leave the beta and use a generally available build instead, subject to its own availability and license terms.
Product analytics do not include audio, MIDI content, filenames, rack names, email addresses, license keys, device names, SoundFont names, or plugin names.
Why we use data
We use data to register your account, issue and validate licenses, associate a beta key with the tester who requested it, reset beta access when a new build identifier is released, prevent repeated enrollment and abuse, operate and secure the service, answer support requests, diagnose crashes and reliability problems, understand feature usage, and improve beta and public releases. Where you have opted in, we also use your email address to tell you about new Keys Buddy releases, including any paid add-on. Because anyone can type an address into a download form, ticking that box only records a request to subscribe; we send one message asking you to confirm, and nothing else is sent unless you do. Leaving the box unticked on a later visit clears an unconfirmed request. We do not use it for anything else, we do not sell or rent it, and every message carries a one-click unsubscribe.
Depending on where you live, our legal basis may be performance of a contract, our legitimate interests in operating and improving a secure product, compliance with law, or your consent where consent is required. Product email about future paid releases always rests on your consent, which you can withdraw at any time without affecting your use of the application. Required beta analytics are treated as a disclosed condition of the optional beta program, not as consent that is bundled into unrelated use of the public product.
Retention and security
Product analytics events are retained for up to 180 days and the analytics store is capped at 50,000 events. Account records are kept while your account exists, so that support can identify your setup and a future paid add-on can be attached to it; ask us and we will delete them. A confirmed opt-in to product email is kept until you unsubscribe or ask us to remove it, together with the record that you gave it. An unconfirmed request is kept only until it is confirmed, cleared, or aged out. Historic purchase and paid-license records are kept while needed to provide that license, meet accounting or legal obligations, resolve disputes, and prevent fraud. Invite redemptions and download-link records are kept while needed to manage access, support downloads, and prevent abuse. Beta enrollment, download-acceptance, and beta-license records are kept while the beta program is active and afterward only as reasonably needed to support issued licenses, document the applicable terms, prevent repeated enrollment or abuse, resolve disputes, and meet legal obligations. Support correspondence and operational logs are kept only as long as reasonably needed for those purposes.
We use access controls, transport encryption, limited data collection, and operational safeguards designed to protect data. No internet service can guarantee absolute security.
Your choices and rights
You can withdraw the product-email opt-in at any time from the unsubscribe link in any such message or by writing to us, and doing so never affects your access to Keys Buddy. You may also ask to access, correct, delete, or receive a copy of personal data associated with you. You may also object to or request restriction of certain processing, withdraw consent where processing depends on consent, and complain to your local data protection authority. Rights vary by location and may be subject to legal exceptions.
Because product analytics use pseudonymous identifiers and exclude your email address, we may not be able to connect an analytics record to you without information from your installation. Send requests to support@joshaquino.com. We may need to verify your request.
International use and changes
Keys Buddy and its providers may process information in countries other than your own. Where required, appropriate transfer safeguards will be used.
Keys Buddy is not directed to children who cannot legally agree to these terms in their location. We may update this policy as the product or law changes. Material changes will be posted here and, when appropriate, shown in the application before they take effect.