import Link from "next/link"; import { Band, CtaBand, PageHead, SiteNav, body, h2, h3, kicker } from "@/components/site"; /* Google Play requires a publicly reachable page that explains how to delete an account and what happens to the data — reachable without signing in, which is why it lives on the marketing site rather than inside the app. */ export const metadata = { title: "Delete your account", description: "How to delete a ThreadCount account or just some of its data, what goes with it, and what is kept.", alternates: { canonical: "/delete-account" }, }; const KEPT = [ ["Nothing, once the facility goes", "Deleting the last account deletes the facility outright. There is no archive copy and no soft-delete flag — the rows are gone from the database."], ["Your name on past records, if colleagues remain", "If someone else still runs the facility, only your login is deleted. Issues, stocktakes and slips you recorded keep the name they were stamped with, because a stock record nobody signed isn’t an audit trail."], ["Backups you downloaded", "A backup file you exported before deleting stays on your own computer. Delete it yourself if you don’t want it."], ["Encrypted server backups, briefly", "Routine server backups roll off on their own schedule. Nothing is restored from them except to recover the whole server after a failure."], ]; const STEPS = [ ["Sign in at threadcount.tech", "Use the account you want to delete. Deletion is done by the account holder — there is no form to fill in and nobody to email."], ["Open Settings, then the Account tab", "It’s the last section on that tab, under your profile, password and users."], ["Read which of the two cases you’re in", "The page tells you whether you’re the last person who can sign in. If you are, download a backup first — the link is right there."], ["Confirm", "Enter your password. If deleting takes the facility with it, you also type the facility name exactly. Then it’s done immediately."], ]; const PARTIAL: [string, string][] = [ ["Remove one person from the staff register", "Settings isn’t needed — open the staff member on the Staff Register and delete them. Their name stays on garments already issued, because a stock record nobody signed isn’t an audit trail."], ["Wipe the activity, keep the setup", "Deletes every issue, return, order, delivery, pickup, stocktake, approval and photo, and resets stock adjustments. The catalogue, staff register, suppliers and departments stay, so the room can carry on from a clean ledger."], ["Start fresh", "Deletes everything the facility has entered — catalogue, barcodes, staff, departments and all history — and leaves only the logins and the facility’s own settings. It’s the reset for a room that wants to begin again without losing its accounts."], ["Export first, if you want a copy", "Settings › Data offers a complete JSON backup before you delete anything. It downloads to your own device and we keep no copy of it."], ]; export default function DeleteAccount() { return ( <>

How to do it

    {STEPS.map(([t, b], i) => (
  1. {String(i + 1).padStart(2, "0")} {t}{b}
    2. ))}

Can't sign in? Use the contact form from the email address on the account and say which facility it belongs to.

If you use the staff app

Ask the linen room — it takes effect immediately

The steps above are for a linen-room coordinator. If you are a staff member who signs in to ThreadCount Staff to see your own uniform, your account works differently, because the record it attaches to belongs to the linen room rather than to you.

Ask your uniform coordinator to remove your access. There is a button on your staff record that does exactly that: it deletes your sign-in, and it ends every session you have open straight away. You can be given a fresh code later if you change your mind.

Your register entry and issue history stay behind, because the facility needs them for its own stock and financial records — the same way your employer keeps a record of any equipment issued to you. Deleting those is the facility's decision, not something one sign-in controls.

If you would rather not ask your coordinator, or you want a copy of what is held about you first, write to privacy@threadcount.tech and we will route it through your facility's privacy process.

The two cases

What gets deleted depends on whether anyone else is left

Other people can still sign in

Only your login is deleted. The facility, its catalogue, staff register, stock and history all stay, because they belong to the linen room rather than to you. Your name stays on what you recorded.

You are the last one

Deleting your account deletes the whole facility: every user, the catalogue and barcodes, the staff register, every issue, return, order, delivery, stocktake, photo and signature. It happens immediately, it cannot be undone, and support cannot get it back. Download a backup first if any of it matters.

Without closing your account

Deleting some data, but not all of it

You don't have to delete your account to remove data. An administrator can do any of these from Settings › Data, and keep working afterwards:

    {PARTIAL.map(([t, b], i) => (
  1. {String(i + 1).padStart(2, "0")} {t}{b}
    2. ))}

All of these happen immediately and can't be undone. None of them touches your login, so you stay signed in and the facility keeps running.

What is kept, and for how long

{KEPT.map(([t, b]) => (
{t}

{b}

))}

More detail on how data is held is in the privacy policy and{" "} data security pages.

); } const wrapNarrow: React.CSSProperties = { maxWidth: 860 };