Datenschutzerklaerung

1. Core principles

We try to keep data handling simple: collect less, keep it only when it is operationally necessary, and avoid unnecessary tracking.

We do not use the contact form to store IP addresses, browser fingerprints, or user-agent strings. For feedback, we keep the message itself and, if you are signed in, your account identity and email so we can respond.

2. Data we may keep

Depending on how you use the service, we may store account details such as username, email address, subscription status, payment references, download history, generated jobs, and support messages.

We keep this data to run the service, prevent broken account states, investigate billing or host issues, and provide access to paid features you already purchased.

3. Data we avoid collecting

We do not claim a zero-data system, because that would be false for an account and payment product. But we do try to avoid invasive collection.

We do not intentionally build behavioral advertising profiles from your use of the premium service, and we do not keep extra contact-form metadata just because it is easy to collect.

4. Security approach

We treat account, payment, and support data as operationally sensitive. Access should stay limited to service administration and problem resolution.

No internet-connected system can honestly promise perfect security forever, but the operating goal is straightforward: keep less data, expose less data, and avoid creating extra sensitive records that do not help run the product.

5. Payments and third parties

Payments may involve third-party processors such as PayPal or banking rails. Those providers handle part of the payment flow under their own policies.

We may keep payment identifiers, status, payer email, amount, currency, and processor response data when needed to activate service, verify transactions, handle disputes, or review refunds.

6. Retention

We do not want to retain records longer than necessary, but some records may remain for accounting integrity, abuse review, support history, legal obligations, or system consistency.

If a retention period is not obvious from the feature itself, the practical rule is this: if the record is no longer useful or necessary, it should not stay around just by default.

7. Account deletion

If you want to leave, you can delete your account directly from this page. This action removes your login account and signs you out immediately.

Some transactional or system-linked records may remain where deletion would break payment history, support continuity, or database integrity, but your direct account access will be removed.

8. Contact

For privacy questions, billing issues, or account concerns, use the contact form at /premium/contact.