Privacy and Data Handling Notice

How ArtifactPilot handles local scans, support bundles, license activation, website analytics, optional advertising cookies, payments, and subscriptions.

ArtifactPilot Privacy and Data Handling Notice
Effective Date: June 17, 2026
Document Version: 1.4
Publisher: NH Media LLC

This notice explains how ArtifactPilot is designed to handle data. It supplements the ArtifactPilot End User License Agreement and any checkout, subscription, merchant-of-record, or licensing-provider terms that apply to your purchase.

1. Local-first design

ArtifactPilot scans and analyzes developer workspaces locally on your computer. The app does not need to upload your source code, file contents, scan results, cleanup candidate lists, cleanup manifests, or personal files to NH Media LLC to perform local scanning and cleanup.

2. Local files created by ArtifactPilot

ArtifactPilot may create local settings, trial records, activity logs, crash logs, CSV reports, JSON cleanup manifests, support bundles, license records, and configuration files in your user profile. These files help you review scans, cleanup previews, completed cleanup actions, app status, and support information.

3. Trial and license activation

ArtifactPilot may store a local trial start date, trial expiration date, license key record, activation instance ID, subscription/license status, activation limit, activation usage, product/variant information, masked license information, and validation timestamps.

Some builds require online license activation or validation. During activation, validation, refresh, or deactivation, ArtifactPilot may transmit information necessary to validate a license, such as license key, product identifier, variant identifier, app version, activation instance name or ID, activation status, validation timestamp, and a pseudonymous machine identifier.

To enforce activation limits, ArtifactPilot may generate a pseudonymous machine identifier from local device and operating-system attributes such as hostname, platform information, machine architecture, and operating-system username. Current builds use a one-way cryptographic hash before using the identifier for activation. The standard activation identifier is the hashed identifier, not the raw source values, and the identifier is not created by scanning your source code, project file contents, cleanup candidates, or personal files.

Current direct-subscription builds use Lemon Squeezy's License API for activation, validation, refresh, and deactivation. ArtifactPilot may receive license metadata from Lemon Squeezy or another licensing provider, such as customer email, customer name, order ID, product ID, variant ID, plan name, license status, activation limit, activation usage, and subscription/license status. ArtifactPilot uses this information to validate that a license belongs to ArtifactPilot and to display local license status.

4. Payments and subscriptions

ArtifactPilot does not process payment-card information locally. Payment-card data, billing addresses, taxes, refunds, chargebacks, receipts, customer portals, subscription records, and license delivery are handled by the Checkout Provider when you purchase through that provider. The current checkout and merchant-of-record provider is Lemon Squeezy unless your checkout page, receipt, or written agreement identifies a different provider.

5. Support bundles

If you choose to export a support bundle, the bundle may include app/system metadata, settings, masked license status, recent activity log entries, crash log text if present, and recent cleanup manifests. It is not intended to include project file contents, source code, .env files, .git folders, cleanup target contents, or raw license keys.

Support bundles, scan reports, logs, and manifests may still include local file paths, usernames, project names, client names, technology stacks, or internal folder structure. Review them before sending if paths are sensitive.

6. Desktop app telemetry

Current ArtifactPilot desktop builds do not send background product telemetry. Update checks and license activation/validation may contact configured servers only for those specific functions.

7. Website analytics and optional advertising cookies

ArtifactPilot.com may use Cloudflare Web Analytics to understand aggregate page views, referrers, and site performance. This helps NH Media LLC understand whether the website, download page, pricing page, and documentation are working for visitors. Cloudflare Web Analytics is intended for aggregate website measurement and does not require analytics cookies from ArtifactPilot.com.

ArtifactPilot.com may also use Google Ads tags to understand whether advertising traffic leads to key page visits, such as the Download page or Pricing page. These optional advertising cookies or ad-click identifiers are off unless you choose to accept optional cookies on the website. ArtifactPilot configures Google Consent Mode defaults so optional Google Ads storage is denied unless you accept optional cookies. You can reopen this choice using the Cookie settings link in the website footer.

Website analytics and optional advertising cookies are used for website/ad performance and do not provide NH Media LLC with your source code, project file contents, scan results, cleanup candidate lists, cleanup manifests, or personal files from the ArtifactPilot desktop app.

8. Customer portal and order recovery

Lemon Squeezy or another Checkout Provider may provide a customer portal, order page, receipt email, or license-key recovery process. Those services are governed by the provider's terms and privacy policy.

9. Contact

For privacy questions, contact NH Media LLC through the contact method listed on artifactpilot.com, the app, your purchase receipt, or the documentation. The current primary support address is [email protected].