What partscheduler.com and the PartScheduler app at app.partscheduler.com keep in your browser, what each item does and how long it lasts. “We” means PFM Design LLC, a Michigan limited liability company, doing business as PartScheduler.
The short version
The website sets no cookies. It counts visits through a service called Plausible, which uses none either, and you can switch that counting off below; the note of that choice is the only thing the website ever keeps in your browser. The app sets three cookies of its own and keeps a few settings in your browser. One cookie keeps you signed in, one remembers which machine a shop tablet shows, and one remembers which job you have open. Neither the website nor the app has advertising code. The app’s own code has no analytics, though the app does send error reports, and timings for a sample of page views, to Sentry, which sets no cookie. The app sets no cookies for any other company, but your browser does reach two other companies directly: Supabase, which stores the app’s files, and Google, whose map loads when someone opens a map or a company’s details on the shipping page. Either may set cookies of its own.
Cookies, browser storage and the cache
A cookie is a small piece of text a website asks your browser to keep. The browser sends it back to that website with its requests, which is how a site remembers that you signed in.
Browser storage means local storage and session storage. Both hold small values that a site’s own pages read and write, and the browser does not send them along with requests the way it sends cookies. Local storage lasts until it is cleared; session storage lasts until the tab closes.
The ordinary browser cache is neither, though every site relies on it. Your browser keeps copies of files it has downloaded (styling, fonts, images, the engine behind the app’s 3D part viewer) so the next visit loads faster. In the app, the cache can also hold photos and prints you have opened, under the browser’s own rules. We do not use it to recognize you, and we cannot read it.
The website: partscheduler.com
The website sets no cookies. It keeps nothing in session storage, and nothing in local storage unless you switch visit counting off, when one item remembers that you did. Every file it loads comes from partscheduler.com itself, so there is no other company’s content on it to set a cookie.
- plausible_ignore
- Remembers that you switched visit counting off. Local storage. Only the switch in the next section writes it, and only when you turn counting off; it holds the word “true” and nothing else. The name is Plausible’s, because Plausible’s own code checks for it before it sends anything. Lasts until you switch counting back on or clear your browser’s data for partscheduler.com.
We checked this in a browser on 13 October 2026. After we cycled the demo board, opened both of the home page’s tabs, read a blog post and switched counting off and on again, the browser held no cookies and nothing in session storage, local storage held plausible_ignore only while counting was off, and every file and request went to partscheduler.com. The Privacy page covers what the website loads and what the waiting list collects.
Counting visits to the website
The website counts visits so that we can see which pages and blog posts people read, how long they stay on each, how far down they scroll, which of the home page’s tabs they open and which site or ad sent them. Plausible, a company based in Estonia, does the counting for us. Its code is part of the website’s own files, and it uses no cookies and keeps nothing in your browser.
Your browser sends each count to partscheduler.com, and our host passes it on to Plausible, so your browser never contacts Plausible itself. Plausible reads your IP address to work out your country, region and city, and to make a code that counts you once for the day. It keeps neither your address nor the secret it mixes into that code; it deletes the secret every 24 hours, so a visit tomorrow cannot be matched to one today. We see totals. The Privacy page lists everything a count carries.
A browser that sends Global Privacy Control or Do Not Track is never counted. You can also switch counting off for the browser you are using now:
The app: app.partscheduler.com
The app sets three cookies. The list below adds a fourth, retired one, because the app still checks for it. All four are first-party: they belong to app.partscheduler.com, and your browser sends them back only to it. None of them holds your name, your email address or anything you typed. We checked this list against the app’s own code.
- ps_session
- Keeps you signed in. Holds a signed token with your account’s ID, an ID for this sign-in and a few details of it, such as when it began. The app signs it without encrypting it: anyone holding the cookie could read those IDs, but could not change them without the app noticing. Page scripts cannot read it (HttpOnly), it travels only over HTTPS (Secure), and other sites cannot make your browser send it in the background or when they post a form to the app (SameSite=Lax). Lasts 12 hours, which the app extends as long as you keep using it, though a sign-in ends after 7 days however active it is. On a shop-floor station, the login a floor computer shares, it is 30 days at a time and 90 at most. Signing out clears it.
- ps_machine_screen
- Remembers which machine’s screen a shop tablet opens to. Holds only that machine’s ID. The app sets it only when someone picks a machine for that device, and it has the same three protections as ps_session. Lasts 400 days, and stays after sign-out because it belongs to the tablet, not to whoever had signed in.
- ps_open_job
- Remembers which job you have open in the jobs list, so it stays expanded and current after you save a change to it. Holds only that job’s ID. The page’s own script writes it, which is why page scripts can read it; your browser sends it only to the jobs pages, and in every other way it has the same protections as ps_session. Lasts 15 minutes, renewed while you work in the list.
- ps_viewport_preview
- Retired. It held which screen layout an owner or admin was previewing, from a setting we removed in September 2026. It lasted one hour, and nothing has set it since then, so it has long expired. The app still checks for it: if a browser held one, an owner or admin would see that preview, with a banner, until they pressed Exit on the banner or signed out. Both clear it.
Browser storage in the app
The app keeps a few settings in your browser and reads them there; it never uploads them to us or anyone else. A remembered list simply reopens a page you already had open.
- ps-theme
- Light, dark, or follow the system. Local storage: it stays on that device until you change it or clear the browser’s data.
- ps:section:*, ps:pref:*
- Where you were in each section: the last list you had open there, with its filters and search, and your row and column choices on the jobs list. Session storage: gone when the tab closes, and the app wipes it when you sign out.
- ps_global_error_reload_at
- When the app last reloaded itself after a crash, so a screen nobody is watching cannot reload over and over. Session storage: gone when the tab closes.
Other companies
The website loads nothing from any other company, and its visit counts reach Plausible through our own server, as the section above explains. The services below are all the app’s.
Supabase (file storage)
Photos, prints and other files in the app travel straight between your browser and Supabase, the company that stores them, through short-lived links our server issues. Some arrive as soon as a page opens, such as the machine photos on the Operations board; others move when you open a PDF preview, download a file or upload one. Either way, Supabase’s servers see your IP address and browser details. A PDF preview also shows its file in a frame that Supabase serves. The app sets no cookie for any of this, but if Supabase’s servers set one of their own, it falls under Supabase’s privacy policy, not ours, and we cannot see or control it.
Google Maps
The map popup beside an address, and the company details panel on the shipping page, show a Google map. It loads from Google, in a frame, only when someone opens the popup or that panel, never on its own. Google then receives the address the map shows, your IP address and your browser’s details, and may set its own cookies, which fall under Google’s privacy policy, not ours. We cannot see or control those cookies.
Address suggestions, as you type an address, also come from Google, but by way of our server. Your browser does not contact Google for them, so Google sets nothing through them.
Stripe
Online subscription is not open yet. When a shop subscribes, it pays on a checkout page on Stripe’s own site, and any cookies on that page are Stripe’s, under Stripe’s privacy policy. Nothing from Stripe loads inside the app.
Sentry
When something goes wrong in the app, your browser sends an error report straight to Sentry, the service we use to find and fix faults. A sample of about one in ten page loads and moves between screens also sends timing data. Sentry’s code in the app sets no cookie and writes nothing to your browser’s storage. The Privacy page lists it with the other services we use.
On the website or in the app, a link that takes you to another site (a carrier’s tracking page from the app, or a policy this page links to) leaves us, and that site’s own cookies and policy apply there.
No advertising, and no tracking across sites
Neither the website nor the app has advertising, retargeting or social-media tracking code. The website’s visit counting cannot follow you to another site, or from one day to the next, and the app’s own code has no analytics at all. Apart from the Sentry reports above, the app’s code reports nothing about how people use it. We do not use any cookie or count to follow you to other sites, build a profile of you or show you ads.
Managing cookies
Your browser’s settings let you see, block and delete the cookies and stored data any site keeps. On partscheduler.com you will find nothing, unless you switched visit counting off and left plausible_ignore in local storage; deleting it switches counting back on. In the app:
- Without cookies on app.partscheduler.com, you cannot sign in. ps_session is the only way the app knows a request is yours, so deleting it signs you out.
- Clearing ps_machine_screen just resets that tablet: it stops opening to its machine’s screen until someone picks the machine again.
- Clearing anything else (ps_open_job, the theme, the session storage) loses a remembered view or setting, and nothing more.
Nothing asks you to accept cookies, on the website or in the app. The website sets none, and its visit counting uses none and has the switch above instead. The app’s cookies sign you in and remember choices someone made on that device; we do not use them for analytics or advertising. Other companies’ cookies are a separate matter, covered above: Google’s map may set some when someone opens it, and Supabase’s servers may when your browser fetches a file.
Do Not Track and Global Privacy Control
These browser signals ask a site not to track you across other sites, and not to sell your personal information or share it for advertising. We do none of those things, on the website or in the app. On the website, either signal also stops visit counting: a browser that sends one is never counted, whatever the switch above shows. The app counts no visits, so a signal has nothing of ours to switch off there. The Google map is different: it runs under Google’s own policy. The app loads it the same way whether or not your browser sends a signal, and what Google does with the signal is up to Google.
Changes
When what the website or the app keeps in your browser changes, we update this page, and the date at the top changes with it.
Contact
Ask about anything on this page with the Get in touch button.