Privacy / Your information

Privacy Policy

What PanelWatcher receives, why we use it, and how it supports your workspace and connected infrastructure.

Effective date:

Operating name: PanelWatcher.

Operating location: Tennessee, United States.

Information you provide

When you use PanelWatcher, we receive the information needed to set up and operate your account and organization.

  • Account information: your name, email address, profile information and authentication records.
  • Workspace and team information: organization name, membership, roles, invitation email addresses and configuration choices.
  • Support communications: tickets, replies and attachments you choose to send.
  • Billing records: payment-provider customer and subscription identifiers, plan, billing status, invoice or transaction information and billing-period dates.

Please avoid including passwords, API keys or payment details in support messages or attachments.

Connected infrastructure

With your authorization, PanelWatcher retrieves information from your Pterodactyl Application API. This includes nodes, servers, locations, allocations, resource limits and capacity information. Infrastructure records can include names, identifiers, hostnames and network addresses.

We store synchronized infrastructure data, capacity configuration, monitoring samples and alert history to provide dashboards, historical views and notifications. The integration reads infrastructure information; it does not control game servers.

Accounts and authentication

PanelWatcher supports email and password sign-in, and Google or GitHub sign-in where enabled. Password authentication uses stored password hashes. When you choose an external sign-in provider, we receive the account information needed to identify you, such as your name, email address and provider identifier.

Authentication records can include sessions, IP addresses and browser information. These support sign-in, access controls and account security.

Payment processing

Stripe and PayPal process payment information through their own services when that provider is available at checkout. PanelWatcher receives billing identifiers, subscription state and invoice or transaction details needed to manage your organization’s plan. PanelWatcher does not store raw payment-card numbers.

The payment providers handle information under their own policies: Stripe Privacy Policy and PayPal Privacy Statement.

Uses and communications

We use information to operate the service, authenticate accounts, apply workspace permissions, monitor connected infrastructure, provide alerts, manage billing, investigate security or abuse, and respond to support requests.

Service communications include verification emails, team invitations, configured alert notifications and support-related messages. Discord, email and generic webhook destinations receive notification information according to your workspace configuration and plan. You are responsible for choosing appropriate recipients and destinations.

Cookies and sessions

The authenticated application uses authentication and session cookies for sign-in and necessary application functionality. Site preferences may also be stored in your browser. Blocking necessary cookies can prevent sign-in or other application features from working.

External sign-in and payment services may use their own cookies when you visit them. Their policies describe those practices.

Service providers and access

Operating PanelWatcher involves infrastructure hosting, storage, email delivery, authentication and payment services. These providers receive information needed for their functions. Your chosen notification services receive the content sent to them.

Workspace members can access information according to their role. Authorized platform operators may access service records to operate the application, handle support and investigate problems. Information may also be disclosed where required by applicable legal obligations.

Retention

History available in the application depends on your plan. Monitoring samples are subject to the service’s storage-retention process; a longer plan history window does not recover records already expired from storage.

A downgrade can restrict access to infrastructure details and features without immediately deleting synchronized data or saved configuration. Support records and attachments have separate retention processes, and backup copies may remain until their retention cycle completes.

Account and service records may be retained as needed for operation, security, billing, support or legal obligations. Cancellation of a paid subscription is not an account-deletion request. Contact us about account or privacy requests rather than assuming a specific automatic deletion date.

Safeguards

Safeguards include server-side credential handling, encryption of stored Pterodactyl API credentials and notification secrets, organization-scoped access controls and role checks. No service or security measure can guarantee absolute security.

Our Security page explains the read-only integration and related boundaries.

Questions and privacy requests

For questions about your information, account access or a privacy request, use [email protected]. Existing customers can submit a ticket through PanelWatcher Support. We may need to verify your identity and authority over the account or workspace before acting on a request.

Policy updates

We may update this policy as the service or its practices change. The effective date identifies this version. Review the policy when making decisions about the information you connect or provide.