Privacy Policy

Recorded media stays local.

This policy describes the public 0.4.2 early prototype, including what is implemented locally and what is not connected to production services.

Effective 30 October 2026 · Not represented as legally reviewed

Current state: this website uses ordinary hosting/security logs and no advertising or product-analytics script. The packaged 0.4.2 prototype implements bounded local diagnostic/Usage Data queues and account-preference policy, but its telemetry destination is explicitly not configured. Sign-in is disabled pending provider registration and no recorded media is uploaded.

1. Who and what this covers

Willer Enterprises publishes Willer Clipper. This policy covers this website and the Willer Clipper Windows application. Full legal-operator and registration details are still being finalised and are not stated here. Privacy enquiries, access or correction requests, and complaints can be sent to [email protected].

2. Your clips and recordings

Recorded video, recorded application audio, microphone audio, thumbnails, originals and edited exports stay on your device. Willer Clipper does not upload that media to a Willer cloud clip library or social feed. You control whether to record, save, move, export or delete local media.

3. Website information

When you visit, the hosting and security layers may process IP address, request path, timestamps, browser/user-agent details, referral information, response status and security events to deliver and protect the site. Cloudflare may process this traffic as the DNS, proxy and security provider. This website currently has no advertising network, behavioural-advertising pixel or product analytics script. If advertising is introduced later, this policy and the site will be updated before ad scripts are enabled.

4. Required function and performance diagnostics

The 0.4.2 prototype implements a bounded local queue and allowlist for required diagnostic categories used to understand capture, encoding, export, update and repair reliability. These can include app version, feature success/failure, error category, performance timing, operating-system and hardware capability categories, and an installation or device identifier needed for reliability, security and support. Required diagnostics do not include the video or audio content of your clips.

The production transport is not configured, so the packaged prototype does not upload this queue to a Willer endpoint. The exact production event allowlist and retention schedule still require publication before public telemetry is enabled.

5. Optional WillerID-linked Usage Data

The prototype implements the local preference and queue policy for optional account-linked Usage Data, including an allowlist for captured game or application name, generated filenames, clip counts, resolution, frames per second, format metadata and related feature-use information. Sign-in is disabled pending provider registration, and production WillerID integration and telemetry upload are not configured or verified.

When production integration exists, turning it off will stop future optional collection, but one final batch already queued while the setting was on may still upload when the app next connects. Turning it off will not delete historic uploads. Historic information will remain subject to the applicable retention schedule and any access, correction or deletion options that are actually available; no immediate-deletion promise is made here.

6. WillerID and account data

The prototype contains a disabled profile affordance and account-policy foundations. Sign-in is disabled pending provider registration; settings/preset restoration and profile, device, session, support or potential licensing integration are not active. When implemented, account information can include identifiers, display/profile information, security and session records, connected device information, preferences, settings, presets and support correspondence. Signing in will not turn WillerID into cloud storage for recorded media.

7. Why information is used

  • deliver, protect and troubleshoot the website and application;
  • operate sign-in, settings/preset restoration, sessions and support;
  • measure function, performance and failures;
  • detect abuse, fraud or security problems;
  • meet legal obligations and handle complaints;
  • use optional linked Usage Data for product understanding when that preference is on.

8. Disclosure and overseas processing

Information may be disclosed within the Willer service responsible for the relevant function, to infrastructure and security providers such as Cloudflare, and to professional advisers or authorities where legally required. Willer Enterprises does not sell recorded media. Some website or service infrastructure may process information outside Australia. The final public-app provider and country list is not yet settled and must be published before production diagnostic or Usage Data collection starts.

9. Retention and security

Local media remains until you delete or move it, subject to local cache limits. Server-held information is retained only as needed for its stated purpose, security, support and legal obligations, but the product-specific retention periods are still being finalised. Reasonable technical and organisational safeguards are used; no internet-connected system can be guaranteed completely secure.

10. Your choices and requests

You can use local clipping without uploading recorded media. You can turn optional linked Usage Data off as described above. You may ask what personal information is held about you, request access or correction, or make a privacy complaint through [email protected]. Enough information may be requested to verify the account or request safely.

Contact Willer Enterprises first so the issue can be investigated. If an Australian privacy complaint is not resolved, information about escalating a complaint is available from the Office of the Australian Information Commissioner.

11. Changes

This policy will be updated when the product, advertising, providers, collection fields or retention practices change. Material changes will be presented through an appropriate website, app or account notice before they take effect where required.

This is an operational privacy disclosure for a public early prototype, not legal advice. Missing operator, provider-country and retention details are tracked production prerequisites rather than filled with invented information.