Privacy policy
Version 2026-09-21. Stationyx is a product of Wiens Corporation, 2133 Lawrenceville-Suwanee Rd, Suite 12-389, Suwanee, GA 30024.
Stationyx documents manufacturing lines, so most of what it holds is about equipment and process rather than about people. This page covers the part that is about people, and it names the actual records rather than describing categories in the abstract.
People who have an account
An account holder has an email address, held by Supabase Auth, which is how they sign in and how we reach them. Alongside it we keep their level in your organization and on each of your lines, and a contact card carrying their name, their company, their role and a short description.
We use it to let them in, to show colleagues who is who, to send the mail the product sends (an invitation, an approval request, a task or a flag), and to attribute changes in the activity trail. We do not use it for advertising, we do not sell it, and we set no advertising cookies.
Operators, who deliberately have no account
An operator is a contact card and nothing more. There is no account, no password and no sign-in: the card carries a name, a company, a role, a description and tags, and it identifies at the station with a PIN, a badge id, or both.
- PIN material never leaves the database. It lives in a table the browser cannot read, under a policy that admits only the service connection, and it is stored as a salted slow hash rather than the PIN. Nobody, including us, reads a PIN back out.
- An export records only that a PIN is set. A person's exported record carries the fact and never the value or the hash. A test searches a seeded export for the real hashes and salts and fails if any of them appears.
- Badge ids are not secrets. A badge is unique on a line when it is set, and it identifies rather than authenticates.
That is the whole point of the design: somebody can be on a line, be trained, run stations and appear in the run history without us holding an account for them.
The activity trail, and why deleting a person does not erase it
Stationyx records who changed what. Each entry carries the actor's email address written into the row at the moment of the change, rather than a link that gets resolved later.
That is deliberate. Deleting somebody's account ends their access and unlinks their contact card, and the record of what they did stays readable inside your organization, which is what makes the trail worth keeping at all. The trail is your organization's, not ours: your people read it in the product, and it goes when your organization goes. Deleting the organization erases the activity log along with everything else, because keeping actor emails and field-level differences after an erasure is exactly the residue an erasure must not leave.
Where it goes
Our security page carries the full list of third parties, generated from what the software actually calls. The ones that touch personal data:
- Supabase holds the database, the sign-in accounts and the uploaded files. Production is in the us-east-2 region, which is Ohio, in the United States.
- Resend sends the product's mail, so it receives the recipient's name, their address and the contents of the message.
- PostHog receives page views and in-app events tagged with organization and project id, and per-call token counts and cost for AI usage. Prompts and completions are deliberately not sent to it.
- Sentry receives stack traces and request metadata when something fails. Request bodies, cookies and authorization headers are stripped, and the user context is a user id and nothing else.
- Google Fonts serves the fonts for this site and the application, which means your browser sends Google your IP address and user agent before any Stationyx code runs.
- Google, through Vertex AI, receives the process text an AI suggestion is asked about. User accounts and email addresses are never part of that text.
PostHog and Sentry are active only where a key is configured for that deployment.
Visiting this website
The contact form and the "email me this sheet" button on the calculator post to a small service of ours that sends an email. What you type is what it receives: your name, your email address, your company and your message, or the figures you entered into the calculator. We use it to answer you.
How long we keep it
We keep your organization's data for as long as your organization exists. When an owner deletes it, access ends immediately and everything is destroyed thirty days later: every record in our database and every file in our storage.
Two honest limits. Rotated off-site backups still hold your organization until they age out of rotation, and our sub-processors keep their own logs under their own retention terms. The security page spells both out.
Your rights over it
- Get it. An owner exports the whole organization at any time, without asking us. It includes every record, every uploaded file and every released document.
- Correct it. People records are edited in the product by anyone at editor or above.
- Delete it. An owner deletes an organization, which starts the thirty-day window above. Deleting one person's account ends their access and unlinks their card while leaving the audit trail intact, as described above.
- Ask us. If you want something the product does not do for you, write to us and we will do it or tell you why we cannot.
Contact
Write to hello@stationyx.com. We answer within one business day.