Privacy
This page describes what this website collects. It covers the marketing website only, not the Packmoat service. Packmoat is an early, private project run by its founder.
What we collect
If you fill in the request-access form, we store:
- your email address;
- your role (optional), your team size, and your answers about Azure Artifacts and npm;
- an internal label (5, 10 or 15) that the page assigns at random and does not display. It is a leftover from a pricing test we removed, and it means nothing to you;
- the site you came from (the referrer's address, without the page path) and the campaign tags in the link you followed (utm_source and utm_campaign), when your browser sends them;
- a random anonymous id (see below), used to limit abuse.
If your browser does not send a Do Not Track or Global Privacy Control signal, we also record anonymous usage events as you use the page: page view, reaching the setup or questions sections, clicking a request-access button (hero or footer), opening a question, starting and submitting the form. Each event carries the random anonymous id, the internal label, and a timestamp. An event does not contain your email address.
If your browser sends Do Not Track or Global Privacy Control, no usage events are sent and the referrer and campaign tags are not added to a form submission. The form still works. It sends a random id that exists only in memory for that page view; it is stored with your submission only so we can limit abuse.
The browser storage we use
We use your browser's local storage, not cookies. Exactly two values can be kept there:
- pm-anon: a random anonymous id. It is written only when your browser is not sending Do Not Track or Global Privacy Control.
- pm-price: the internal label described above (5, 10 or 15). No price is shown on the page. It is written only when your browser is not sending Do Not Track or Global Privacy Control.
If your browser sends Do Not Track or Global Privacy Control, we write nothing to local storage. The label and the id then exist only in memory for that page view. Clear your site data at any time to remove both values.
Notifications to us
When a request arrives we may send ourselves a short push message through a notification service. It contains only your team-size, Azure Artifacts and npm answers. It never contains your email address, your role or your anonymous id.
Why
We use form answers to decide whether to offer you early access and to reply to you by email. We use usage events to learn whether the page interests people, counted in aggregate. We do not use advertising tools or third-party analytics, and the page loads no third-party scripts, fonts or images.
Where it is stored, and who processes it
Form answers and events are stored in a Cloudflare D1 database. Cloudflare hosts this website and processes requests to it as our host. Packmoat does not store IP addresses, and the abuse limit is counted from the random anonymous id, not from addresses. Cloudflare sees network addresses as part of delivering the site, under its own terms. We do not sell or share your answers.
How long we keep it
We keep it until the founder deletes it or you ask us to delete it.
Ask for deletion
Write to the contact address from the email address you used, and we will delete your form submission. Your submission stores the random id that was used with it, so we also delete the usage events that carry that same id. Events from a browser that never submitted the form cannot be matched to a person, so we can delete them only if you send us the id from your browser's local storage (key pm-anon, if one was written).
This address is shown by JavaScript from one configuration file. If it does not appear, enable JavaScript.
The customer site (app.packmoat.com)
The sections above describe packmoat.com. Customers can also sign in to app.packmoat.com with their work Microsoft account. When you sign in there, Microsoft tells us your organisation's directory id, your user object id, your display name and the Packmoat role your organisation gave you. An encrypted session cookie in your browser holds these four values for at most 8 hours (or 30 minutes without activity), so the site knows who you are. We also keep, in our database for your organisation's Packmoat account, a member record with your directory id, object id, display name and when you were first and last seen, which the team page and tokens use. We also record which person owns each token, who created the organisation, and the display name and object id of whoever revoked a token, changed the auto-join setting or connected a feed. A log of account actions (tokens, auto-join, connecting a feed or having it withdrawn, starting a plan, opening billing management and sign-up) keeps the person's directory id, object id and display name; your role is not kept in our database, and we never receive your password. Our web server also keeps an access log for that site: your network address, the time and the page requested, with cookies and sign-in codes removed. The log is capped at about 60 MB and older parts are deleted after 90 days; while traffic is low, the newest part can hold entries for longer before it is replaced.
When an Admin or a developer checks the setup, Packmoat uses a short-lived Microsoft token to read feed settings in Azure DevOps. The token is used only during the check and is never stored. Packmoat's own feed access is also tested against your other feeds. We keep the check's result, including the display names of the person who ran it and of the feed's administrators.
For each package version your organisation's feed asks about, Packmoat keeps what it decided (shown or hidden), why, the publish date and cooldown it used, and when that decision was first and last made. It holds no token, name or network address. We keep it for 365 days after last use, and delete it with the rest of your organisation's data after cancellation.
When someone in your organisation downloads a package through Packmoat, we record the time, the package and version, what Packmoat decided and why, and the id of the token used. A token id leads to the person or automation the token was issued to. It holds no network address or user agent. We use it to tell you which tokens received a version that later turns out to be harmful. We keep it for 90 days. Separately, for each token we note the days (UTC) it was used, only the token id and the date, to count active developers. We keep that for 365 days. Both are deleted with the rest of your organisation's data after cancellation.
We use your organisation's directory id to find which Packmoat account you belong to, and your role to decide what you may see. Signing out removes the cookie. Each sign-in is checked by Microsoft and appears in your organisation's own Microsoft sign-in logs.
Who processes it: the customer site runs on a server we rent from DigitalOcean in New York, United States, which holds the access log and the account database. When an Admin starts a plan, Stripe, the merchant of record, collects payment details and the billing email on its own checkout page, under its own privacy policy (stripe.com/privacy). We send Stripe only your Packmoat account id; we keep Stripe's ids for your customer record and subscription, your plan and its status, and a card fingerprint (Stripe's code for a card, not the card number) so that each card gets one free trial. Microsoft handles the sign-in itself, under its own terms and your organisation's agreement with Microsoft.
Changes
We will update this page if what we collect changes.