Privacy Policy

1. Who we are

Hackwhiz is a personal project and a platform for content and experiments. For data questions, write to [email protected], Telegram or Discord.

2. What data we collect

• Account data. Username, email, password (hashed), profile settings.
• Uploaded content. Audio files, images, and other content you submit for processing or posting.
• Usage and technical data. Basic server logs, timestamps, device and browser info, IP address for security.
• Cookies and auth tokens. Technical cookies for sessions, security (for example, CSRF), and login persistence.
• Support communications. Messages and requests you send to us.

3. How we use data

• Provide account access, authentication, and abuse prevention.
• Maintain, troubleshoot, and improve the site and services.
• Communicate about service changes or support.

4. Cookies

We use only necessary cookies for site functionality and authentication. We do not set analytics or advertising cookies at the moment.

• sessionid / access_token: store your active session for login.
• csrftoken: protection against cross-site requests.

You can accept all cookies or keep only necessary ones via the banner and the cookie settings button in the footer.

5. Who we share data with

We do not sell your data. We share it only with service providers needed to operate the service (hosting, email), for security, or when required by law.

6. Data retention

Data is stored as long as needed for the service to operate and to meet legal obligations. You can request deletion of your account and content by contacting support.

7. Your rights

• Get a copy of your data and correct it.
• Request correction or deletion of your information if permitted by law.
• Withdraw consent for optional cookies (when they appear).

8. PhysicsLNZ service

The following applies specifically to the PhysicsLNZ physics simulation service:

Data collection

• Project data: name, simulation parameters, world settings, and preview images you create.
• Privacy settings: your choice of public or private visibility for each project.
• Interaction data: likes and engagement with other users' public projects.
• Account linkage: your user ID and username from the auth service to identify project ownership.

Data handling and storage

• Public projects are visible to all users; private projects are visible only to you.
• Project data and preview images are stored on our servers for the duration of your use of the service.
• You can delete your projects at any time, which removes all associated data including preview images.
• Simulation data is stored locally in your browser and synced to our servers only when you explicitly save a project.

Third-party sharing

• Public projects may be viewed and liked by other users of the platform.
• We do not share your project data with third parties for commercial purposes.

9. Wyverno service

The following applies specifically to the Wyverno audio processing service:

Data collection and billing

• Payments are processed by Paddle; we receive transaction status, plan, and contact email to manage subscriptions.

Audio processing and data storage

Wyverno processes audio files strictly as an audio signal (for example, EQ curves, dynamics, and noise reduction) for sound design and music production.

• Processes uploaded audio by extracting technical signal parameters (equalization, dynamics, noise floor) and applying them to target recordings.
• Does NOT extract, model, or store vocal identity, voiceprints, or any biometric information.
• Does NOT perform speaker recognition, voice profiling, or any form of biometric analysis.
• It does not use your audio data for model training.
• It does not use your audio data for external analytics.
• It does not share your audio data with third parties (except infrastructure providers required for storage/processing as part of operating the service, and only to the extent necessary to provide functionality).
• Your audio data remains private and is accessible only to you in your account.

Wyverno Studio: what data is stored in projects

Wyverno Studio allows you to save projects so you can return to them, edit them, and re-export results. To do this, we store the following data (privately for your account):

• Project audio files. Uploaded audio files, reference files, as well as generated/exported files (for example, processed clip renders and final mixdowns). These files may be stored on disk or in object storage depending on the service operating mode.
• Audio metadata. Duration, sample rate, channel count, original filename, technical metadata, and waveform/peak data for displaying on the timeline.
• Project metadata. Name, description, creation/update timestamps, archive status, BPM, project duration, master volume settings, and other project UI parameters.
• Project structure (timeline). Tracks, clips, timeline positions, durations and offsets, gain, fades, panning, and other playback/editing parameters.
• Effect chains and processing settings. Selected models, enabled effects (effect chain), and your saved processing settings for tracks/renders.
• Generated parameters and derived data. Parameters the service predicts/generates during processing (for example, EQ/dynamics parameters), as well as your saved adjustments to those parameters.
• Cache and intermediate artifacts for functionality. Temporary or cached previews/renders and internal identifiers (for example, render hashes) to speed up reprocessing. They are used only to operate Studio (preview, reopening, export) and are not used for model training or external analytics.

Retention and deletion (Wyverno Studio)

• Projects and related data are stored until you delete them (or as needed to provide the service at your request, for example, saving a project).
• You can delete uploaded files, output results, and/or entire projects through the Studio interface; after deletion, we remove the corresponding records and files from our storage to the extent technically possible.
• Some temporary files created during processing (previews, intermediate results) may be retained for a period of time for performance and stability, but their purpose is only to provide Studio functionality.

Refund policy

We provide a 14-day refund period starting from the first purchase or subscription start. If you are not satisfied with the service, you can request a refund within the first 14 days.

Refunds may be issued provided the request is made within this 14-day period. We reserve the right to review refund requests in cases of excessive or abusive use of the service to prevent fraud or abuse.

After the 14-day period, payments are generally non-refundable, except in cases of duplicate charges, billing errors, or technical issues preventing service access.

To request a refund, please contact our support team with your account details and a brief description of the issue. Approved refunds will be processed, where possible, through the original payment method.

10. Contacts

Privacy inquiries: [email protected], Telegram or Discord. You can also leave information about a problem via the link to the problems page.