1. Information we handle

Depending on the features you use, NAPZ may handle:

• Account information: your email address, Firebase account identifier, verification status and account-scoped application preferences.
• Tournament information: tournament names and settings, team/player display names, gamer tags, Twitch names or URLs, scores, placements, brackets, timers, payment status or payment-related notes, administration notes and tournament history entered by a host.
• Local application information: settings, account-scoped cache data, diagnostic logs and local identifiers used to operate, recover and troubleshoot the application.
• Connected-service information: information needed for optional Google Drive and Twitch features, as described below.
• Support information: information you choose to provide when contacting us by email or Discord.

NAPZ does not currently process card or bank payments itself. A host may record a participant's payment status or related administrative notes inside a tournament.

2. How information is collected and used

Information is collected when you create or sign into an account, enter tournament information, enable an optional integration, publish a supported Live View, use the application, or contact support.

We use it to authenticate accounts; operate tournament setup and scoring; save, synchronize and recover tournament state; provide Remote Admin, Live View and caster features; maintain account preferences; diagnose faults; protect the service; and respond to support requests.

3. Firebase account and cloud services

NAPZ uses Google Firebase services for account authentication and supported cloud features. Authentication credentials are transmitted securely to Firebase for authentication; NAPZ does not store your plain-text account password.

Account-scoped tournament state, recovery/history information and supported public Live View information may be stored using Firebase services so NAPZ can provide those features across installations signed into the same NAPZ account.

4. Google Drive and Remote Admin

Google Drive integration is optional. When you connect it, NAPZ requests the Google Drive drive.file permission. This permission allows NAPZ to create new Google Drive files and access files created by, opened with, or otherwise specifically authorised for NAPZ. NAPZ does not request broad access to all files in your Google Drive.

NAPZ uses this access to create and manage NAPZ Remote Admin tournament files, synchronize permitted tournament administration and scoring changes, and reconnect the relevant NAPZ-created/authorised file when supported recovery requires it.

Information imported from an authorised Remote Admin file becomes part of the relevant NAPZ tournament state. Where cloud recovery/history is enabled for that tournament/account, the resulting tournament state may also be stored through NAPZ's Firebase-backed services.

Google OAuth credentials used by the Windows application are stored locally for the relevant NAPZ account using Windows Credential Manager. Disconnecting or disabling Google in NAPZ removes the local credential used by that Windows installation. You can also revoke NAPZ access from your Google Account.

NAPZ does not sell Google user data, does not use it for advertising, and does not use Google Drive access to read unrelated Drive content.

5. Twitch integration

Twitch functionality is optional. NAPZ uses an account-isolated Microsoft WebView2 browser profile for supported Twitch sign-in and caster workflows. Twitch cookies/browser storage are kept locally in that account's WebView2 profile. NAPZ may read local Twitch session indicators such as sign-in/login display information so the application can determine whether the Twitch session is available.

When Twitch is disabled or disconnected, NAPZ attempts to clear the locally cached Twitch authentication/session information for that NAPZ account. Twitch pages and streams are provided by Twitch and are also subject to Twitch's own terms and privacy practices.

6. Public Live View

If a tournament host publishes a supported Live View, selected tournament information can become publicly accessible through the Live View URL. This can include tournament/team/player display information, bracket or Match Point information, scores, placements and results that are included in the published view.

The host controls whether supported Live View information is published and is responsible for ensuring that information entered or published about participants is appropriate to make public.

7. Sharing and service providers

We do not sell personal information. Information may be processed or disclosed where reasonably necessary to provide the features you use, including through service providers such as Google/Firebase, Google Drive/Sheets, Twitch, Microsoft platform components, Cloudflare for website/network delivery, and Discord when you choose to use Discord support.

We may also disclose information where required by law, to protect users or the service, or in connection with a genuine business transfer where permitted by law.

8. Overseas processing

NAPZ is operated from Australia. Some third-party providers operate globally, so information may be processed or disclosed in Australia, the United States and other countries in which those providers or their subprocessors operate. Exact processing locations can vary according to the provider and service configuration.

9. Security and retention

We use reasonable technical measures appropriate to the service, including HTTPS for hosted services, authenticated account access, account-scoped storage, scoped Google OAuth access and Windows Credential Manager for supported local Google credentials.

Information is retained only as reasonably needed to provide account, tournament, recovery/history, support, security and legal functions. Local application data can remain on a device until removed by the relevant application/disconnect process, uninstall/cleanup process or manual deletion. Third-party providers may apply their own retention periods.

10. Your choices, access and correction

You can choose whether to enable optional Google Drive and Twitch integrations and whether to publish a supported Live View. You can revoke Google authorization through your Google Account and can clear supported local integration state through NAPZ.

To request access to, correction of, or deletion of personal information controlled by NAPZ, contact support@napztournaments.com. We may need to verify your identity before acting on a request. Some information may need to be retained where reasonably required for security, legal or legitimate record-keeping purposes.

11. Privacy questions and complaints

If you believe NAPZ has mishandled personal information, contact support@napztournaments.com with enough detail for us to investigate. We will review the issue and respond within a reasonable period. Where the Australian Privacy Act 1988 applies and you remain dissatisfied, you may also have a right to contact the Office of the Australian Information Commissioner.

12. Participant information and minors

Tournament hosts decide what participant information they enter into NAPZ. Hosts should not enter unnecessary sensitive personal information and are responsible for having an appropriate basis to use and publish participant information, including information relating to minors.

13. Website data

This public information website is designed as a static site and does not intentionally use advertising trackers. Hosting, DNS and security providers may process ordinary request/network information such as IP address, browser/user-agent information and timestamps as needed to deliver and protect the site.

14. Changes to this policy

We may update this policy when NAPZ features, integrations or legal requirements change. The effective date will be updated when a revised version is published.

15. Contact

Email: support@napztournaments.com
Support community: NAPZ Tournaments Discord