PrivacyUpdated 13 November 2026

Privacy.
What reaches us.

Most of pacxio runs on your machine and never reaches us. This page says what does, why, and for how long.

A1
Website cookies
None
B1
Analytics
None
A2
Your files
Local by default
B2
Cloud files
Deleted after 30 days
Overview

Who we are

pacxio (“we”, “us”) makes the pacxio packaging tools and runs pacxio.dev. This policy covers the website, the pacxio software you install, and the cloud features it can call.

Overview

In short

  • No trackingThe website sets no cookies and runs no analytics or ad scripts. Signing in to the cloud features sets one sign-in cookie on api.pacxio.dev, used for nothing else.
  • Local firstDielines, 3D previews and the workbench run on your computer. We don't receive those files.
  • Cloud on requestFiles reach our server only when you use a cloud feature, and only the files that feature needs.
  • Short retentionCloud job files are deleted 30 days after your last use of that job.
  • Never soldWe don't sell your data or use your designs to train AI models.
What we handle

This website

The website is served by Cloudflare, which processes your IP address and request details to deliver and protect the pages. We don't keep our own access logs for the website.

Your language choice is saved in your browser's local storage so it stays the same across pages and visits. It is not sent to us or used for tracking. You can change it in the language menu or clear it in your browser settings.

The fonts are served from this site. The 3D viewer loads from jsDelivr, which receives your IP address and browser details when your browser fetches the file, under its own privacy policy.

The structure library runs in your browser. The generator sends the structure, sizes, board and options you pick to our server (api.pacxio.dev), which draws the dieline and works out the fold. These requests aren't linked to an account; like other requests to the server they appear in its access logs, kept for 14 days. Downloading the dieline files needs an account (see below). The files are made when you ask for them and aren't kept on the server.

What we handle

The software

The pacxio package installs from PyPI, and setup downloads the open-source Source Han Sans fonts from jsDelivr or GitHub. Those services see your IP address when you download.

Once installed, the dieline engine, 3D preview, workbench and MCP server run on your machine. The workbench listens only on 127.0.0.1. The software sends no usage statistics or crash reports to us.

Your coding agent (for example Claude Code or Codex) reads your prompts and project files under its own provider's terms. We don't receive what you send to your agent.

What we handle

AI images

Concept images and print artwork can be generated by an image service you choose: your agent's built-in image tool or an API key you set up. Prompts and reference images go from your machine straight to that service, under its terms. They don't pass through us, and we never see your API keys.

What we handle

Cloud features

Some steps run on our server: layout and typesetting on the dieline, turning concept flats into vectors, full preflight and separations, and building the factory file pack. When you use one, your agent uploads what that step needs: the job file, your text, artwork, logos, fonts you added, and the concept flats.

We use these files only to produce the result you asked for and to fix problems with that job. Staff look at a job only when you ask for help with it or to investigate abuse.

Job files and results are deleted 30 days after your last use of that job, or sooner if you ask. Our cloud server is in the United States, so your files may be processed outside your country. Files travel over HTTPS and are stored on a server that only we administer.

The cloud server (api.pacxio.dev) keeps standard access logs (IP address, time, request and browser type) for 14 days to keep the service running and secure.

Cloud features need an account. We keep your email address (you sign in with a code we email you), a sign-in cookie for the account pages, and the computers you connect with pacxio login (named after the computer, for example "pacxio CLI on maker-mbp", so you can tell them apart and disconnect them). Sign-in emails are sent by Resend.

To run and improve the service we keep usage records: which cloud steps you ran, when, how long they took, whether they succeeded and any error message; the days you signed in on the website; and your dieline downloads from the generator (structure, board, file format and time). The generator also counts how often each structure is generated per day, without your IP address or account.

Deleting your account on the account page deletes your email address, sign-ins, connected computers and cloud job files. Your usage records are kept only without your account ID or email address, as anonymous statistics.

If we add payments, we'll use a payment provider for card details and update this page before that starts.

Your choices

Sharing

We share data only with providers that help us run the service (hosting: Hostinger; network and website delivery: Cloudflare; sign-in email: Resend), under contracts that limit them to that work, or when the law requires it. We don't sell or rent personal data.

Your choices

Your rights

You can ask us for a copy of the data we hold about you, to correct it, or to delete it, wherever you live. Depending on your location (for example under the GDPR or California law) you may have further rights, including objecting to processing and complaining to your data protection authority.

pacxio is a professional tool and isn't meant for children under 16.

Your choices

Changes

We'll post any change here and update the date above. If a change affects how we use files you've already sent, we'll say so before it applies. Last updated 13 November 2026.