MAXPKG
Sign in
Privacy

Privacy Policy

Last updated: July 24, 2026

maxpkg collects the information needed to run a package registry: accounts, developer profiles, package pages, uploaded files, reviews, moderation records, and basic operational data.

1. Data we collect

Depending on how you use maxpkg, we may store:

  • Account details such as email address, display name, avatar, login provider, and account dates.
  • Developer profile details such as publisher name, logo, bio, website, GitHub, support link, and contact email.
  • Package data such as name, slug, description, license, tags, category, GUID, versions, changelog, and compatibility.
  • Uploaded files such as package covers, SVG icons, screenshots, and MZP package files.
  • Reviews, ratings, review replies, reports, and moderation notes.
  • Download/install events and basic technical request information used for security and service health.

2. How we use data

We use this data to authenticate users, show public package pages, let developers manage releases, process uploads, moderate content, calculate ratings, count downloads, diagnose service problems, and protect the platform from abuse.

3. Uploaded files

Package files and images are stored so maxpkg can display package pages and provide downloads. Public package assets such as covers and screenshots may be visible to anyone. MZP files may be downloaded through package pages, runtime APIs, or moderation tools depending on package status and permissions.

Do not upload private client files, secrets, credentials, license keys, or anything you are not allowed to share.

4. Runtime and API requests

The MaxPkg Manager runtime may request catalog data, package details, screenshots, changelogs, updates, and downloads from maxpkg. These requests help the manager show packages inside 3ds Max and install selected tools.

We may record basic operational data such as timestamps, package ids, version ids, client versions, and general request metadata to keep downloads reliable and understand package usage.

5. Service providers

maxpkg uses infrastructure providers to operate the service, including authentication, database, file storage, CDN, hosting, email delivery, and monitoring. These providers process data only as needed to run maxpkg.

6. Data sharing

We do not sell personal data. Public profile information, package metadata, screenshots, ratings, reviews, and developer replies may be shown publicly as part of the marketplace.

We may disclose information if required by law, to investigate abuse, to respond to security issues, or to protect users and the service.

7. Retention

We keep data as long as needed for accounts, package availability, moderation history, security, backups, and operational records. Published package data may need to remain available even if a developer account changes, especially when users depend on the package.

8. Your choices

You can update account and developer profile information from the website. Some public package information can be edited from the Developer Dashboard.

Account deletion is available for accounts without developer packages. Accounts with published developer packages may require manual support review so public package pages and user workflows are not broken unexpectedly.

9. Security

We use access controls, server-side checks, moderation tools, and private server keys for sensitive actions. No system is perfect, but maxpkg is designed so users and developers do not need direct access to private infrastructure credentials.

10. Contact

Privacy questions or account requests can be sent to support.maxpkg@gmail.com.