{pufus} Data & Privacy
Terms of Service Workstation
Privacy Policy Effective: October 2026

Privacy Policy

We build Pufus on strict data minimization. We collect only what is required to authenticate your workstation, protect your repositories, enforce your script licenses, and keep our infrastructure secure.

Encrypted Repositories Your uploaded scripts are compressed and encrypted before storage.
Never Sold or Shared We never sell, rent, or broker your personal data, source code, or telemetry.
Instant Removal Deleting a file or project in your workstation removes it immediately.
01

Privacy Principles

This Privacy Policy describes how Pufus collects, uses, and safeguards information across our website, workstation dashboard, script delivery endpoints, proxy relays, and APIs.

Zero Data Monetization: Pufus is funded directly by our developers. We do not use advertising networks, and we never sell or share your scripts, endpoints, or user records with third parties.
02

Information We Collect

  • Account Credentials: Your username, email address, hashed password, two-factor authentication status, and OAuth profile identifier if you sign in with Google.
  • Billing Records: Transaction status, balance history, and plan tier. Payment card details are processed directly by Stripe and are never stored on Pufus servers.
  • Workspace Activity: Repository metadata, license key configurations, team member roles, and proxy relay settings.
03

Script Confidentiality & Storage

Scripts and modules uploaded to Pufus are compressed and encrypted prior to remote storage. When a client executes your loader URL, the script is processed in volatile memory to synthesize a protected build and is never exposed publicly in plaintext.

04

Security & Anti-Abuse Telemetry

To protect the platform against credential stuffing, multi-account abuse, unauthorized account sharing, and denial-of-service attacks, we collect device and browser signals, network IP addresses, and request rate metrics. These signals are used exclusively for platform security and compliance enforcement.

05

Licensing & Live Player Telemetry

When licensing is enabled on a repository, our runtime gateway processes session heartbeats containing the player's in-game user ID, username, place ID, and a one-way hashed hardware identifier (when HWID verification or lock is used). Active session data is held in temporary memory so repository owners can view live connected players and manage access slots, expiring automatically shortly after a player disconnects.

06

Data Retention & Deletion

Uploaded scripts and proxy configurations remain stored only while active in your workstation. When you delete a script or repository, it is removed from storage immediately. For permanently suspended accounts, repositories are retained for 15 days to allow local backup export (.zip), after which all associated files are permanently purged.