Privacy policy
Hannes Software builds desktop applications that do local work. We do not use a centralized user account system for our products.
1. Desktop activity
The products process data, such as network packets, video files, or audio stems, on your local machine unless explicitly stated otherwise. We do not collect analytics on what files you open, what IP addresses you scan, or the internal contents of your workspace.
2. License activation
When you purchase a license, Paddle collects your billing details as the payment provider. We receive the email address, name, and product tier needed to generate a license key. During activation, the application sends the license key and a hardware-derived identifier to our server so we can bind the seat. This identifier cannot read your files or track your browser history.
3. Support communication
If you use the contact form or send us an email, we keep that correspondence to solve the issue. If you send a packet capture, report, screenshot, or media file for troubleshooting, it is used only for that support case unless you give permission to keep it as a test fixture.
4. Website analytics
This website does not load optional Google advertising services unless you explicitly allow them. If AdSense is enabled, our site limits it to editorial blog and help routes; Google may process page, device, cookie, and ad-interaction data to select, deliver, and report ads. Google Ads may also receive ad-click identifiers, Community Free download events, and completed purchase events for campaign measurement. Regulated European regions require a Google-certified consent platform. We do not sell traffic data.
How Google handles business data5. Payments and fulfillment
Paid product checkout is handled by Paddle or another listed payment provider. The provider is responsible for card, tax, invoice, fraud, and regional payment processing. Hannes Software receives only the transaction details needed to issue the product license, answer purchase questions, and keep a durable fulfillment record.
6. Support files and diagnostic material
Some support cases require evidence such as packet captures, screenshots, logs, media snippets, clinic workflow examples, or exported reports. Send the smallest sanitized sample that still demonstrates the problem. We do not use support attachments for model training, advertising profiles, or public examples unless you give separate written permission.
7. Retention and deletion
License fulfillment records are kept while the license may need recovery, transfer, refund review, or abuse prevention. Support correspondence is kept long enough to resolve the case and recognize repeat issues. If you need deletion or correction of contact records, write from the same email address so we can verify ownership before changing records.
8. Service providers
The site may rely on hosting, DNS, payment, email, and basic infrastructure providers. Those providers process limited operational data so the website, downloads, license activation, email delivery, and purchase fulfillment can work. Product files opened inside the desktop applications remain local unless you deliberately send them to support.
Contact support
To ask about privacy records, license fulfillment, or support history, email contact support.