Try to write down every online account you've created in the past three years. Most people get to about fifteen and stall — then remember four more over the following week, usually because something arrived in their inbox.
That gap is the problem. You can't manage, cancel, or clean up something you can't enumerate. Every trial you started, every tool you tested for one project, every platform you joined out of curiosity is still holding an email address, a password, and whatever else you handed over.
The takeaway up front: keep a signup register — one entry per account, five fields, written at the moment you sign up rather than reconstructed later. The entry takes under a minute, and it converts "which accounts do I even have?" from an archaeology project into a list you can act on.
If you evaluate a lot of platforms — and if you work in content, marketing, or site ownership, you do — this is one of the highest-return small systems available.
Why reconstruction doesn't work
The usual advice is to audit periodically by searching your email for "welcome" and "confirm your account." It's better than nothing, and it's genuinely incomplete:
- Signups made with a different email address don't surface.
- Social logins ("Continue with Google") often leave no distinctive welcome mail, and the account exists under a provider you've forgotten you used.
- Confirmation mails get deleted, filtered, or lost to inbox cleanups — and older mail may be gone entirely, depending on your retention settings.
Reconstruction can only find what left a trace. A register records at the moment the trace is created, which is the only time you reliably have the full picture. It's the same principle behind beating save-and-forget with bookmarks: the metadata has to be captured at the point of action, because it doesn't survive in memory.
The five fields
Keep it small enough that you'll actually do it. Anything more than this gets abandoned within a month.
1. What it is, in your words. Not the product's tagline — your reason. "Screenshot tool for the client project." "Rewards site, testing for the roundup post." Three months later this is what tells you whether the account still has a purpose.
2. Which email and login method you used. Which address, and whether it was a password or a social login. This one field prevents most of the pain later, because it's the thing you can't work out from the outside.
3. What you gave it. Payment details? Identity verification? Access to another account via OAuth? Installed software or a browser extension? Phone number? A short note is enough. This is the field that determines how urgent cleanup is.
4. The exit route. The URL of the cancellation, account-deletion, or data-deletion page — found at signup time, when you're already on the site and not in a hurry. This is the field people skip and the one that saves the most time.
5. The date. Signup date, and trial end date if there is one.
Five fields, under a minute. Store it wherever you'll actually look — a spreadsheet, a note, or a dedicated collection in your bookmark manager with the details in each item's notes. The tool matters far less than the habit; what matters is that it's one place, and it's the place you already open.
Tagging the register
If your register lives in a bookmark manager, three tags do almost all the useful filtering:
paid— anything with billing attachedverified— anything you gave identity documents or a phone number totrial— anything with an end date you'll want to catch
The general tagging principles apply: a small vocabulary you'd actually type beats an elaborate scheme you won't maintain. Three tags you use are worth more than twelve you invent once.
Capture the exit before you need it
Field four deserves its own section, because it's the one that turns a register from a list into a tool.
The moment to find out how to leave a platform is the moment you join it — not because you expect a problem, but because you're already on the site, unhurried, and not yet emotionally invested. Ten minutes into signup you're browsing; six months later, when you want out, you're annoyed and the help centre has been reorganised.
So while you're there, locate and save:
- The cancellation or account-closure page, and whether closure is self-service or requires contacting support.
- The data deletion policy, if the platform publishes one separately from account closure. These are genuinely different things: closing an account doesn't automatically mean the data is deleted, and a platform that documents the distinction is being straight with you.
- The terms and privacy policy as they stood when you joined. Save the page, not just the link — policy pages get rewritten at the same URL, and the version you agreed to is worth having.
A published, findable deletion route is a real positive signal, and it's easy to check before you commit. Rewards and paid-task sites are a good category to see this in — TimeBucks, for example, publishes terms of service, a privacy policy, and a separate data deletion policy alongside its FAQ and contact page. That's the shape you want to find before you create an account, not after: a documented way in, and a documented way out.
The same visit is the right time to note the operational details you'd otherwise hunt for later — how payouts work if money moves in either direction, which payment methods are supported in your country, what verification is required and at what stage, and what the platform reserves the right to change unilaterally. Terms in that category typically retain broad discretion to modify or pause offers and to hold rewards during risk reviews; better read at signup than discovered at withdrawal.
Running the quarterly pass
Once a quarter, open the register and put every entry into one of four buckets:
Keep. Actively used. Move on.
Close. No longer needed. Use the exit route you already saved. Where a deletion route exists separately from account closure, use it — a closed account and deleted data aren't the same outcome.
Downgrade. Used occasionally, but paying for a tier you don't need. Often the largest recoverable cost in the whole list.
Decide later. Allowed once. If an entry lands here twice running, it's a Close — "later" is how registers turn back into piles.
Two habits make the pass fast: work top to bottom without second-guessing yourself, and do the closures immediately rather than making a second list — a to-do list of cancellations is just the original problem in a smaller font. The same discipline that keeps a link library usable applies here: the review only works if things actually leave.
What to do with the ones you can't close
Some accounts can't be deleted, or the process requires a support ticket you don't want to file today. Don't let those stall the pass. Instead: remove stored payment details, strip optional profile data to the minimum, turn off marketing email, and revoke any OAuth access the account has to your other services — check your Google, Apple, or Microsoft permission lists directly, since that's the authoritative view rather than the platform's. Then mark the entry dormant and revisit next quarter.
Starting from where you are
You don't have a register yet, and reconstructing three years of signups isn't realistic. Don't try. Do this instead:
- Start the register today, for new signups only. It becomes complete going forward, which is the part you can control.
- Add accounts opportunistically. Every time you log into something old, spend forty seconds adding it. Within a few months you'll have captured most of what you actively use.
- Do one targeted sweep of the two lists that carry real cost: your recurring charges (your card statement and your wallet's subscriptions page, both more reliable than memory) and your OAuth grants in your main identity provider. Between them they surface most of what matters.
Complete registers are built forward, not backward.
FAQ
Isn't this what a password manager does?
Partly, and if you use one it's a good foundation — it already knows where you have logins. What it doesn't record is why you signed up, what you handed over, or how to leave. Keep the register alongside it; the password manager holds credentials, the register holds context and the exit route.
Where should the register actually live?
Wherever you'll open it. A bookmark collection with notes works well because you're already in that tool daily and each entry can hold the exit-route link directly. A spreadsheet is equally fine. Avoid anything that requires a separate app you'd only launch for this purpose.
Is it safe to keep a list of my accounts?
Keep the register free of credentials — no passwords, no security answers, no payment details. It should be a list of what exists and how to leave, not a key to anything.
How often should I run the review?
Quarterly suits most people. If you trial a lot of tools, monthly is easier because each pass is shorter. The frequency matters less than the pass being short enough that you don't postpone it.
What if a platform won't delete my data when I ask?
Start with their documented process and keep a record of the request and the date. Depending on where you live, you may have a statutory right to erasure and a regulator to escalate to. This is exactly why saving the deletion policy at signup pays off — you'll have the version that was in force when you joined.
Next step
Open a blank note right now and add the last three platforms you signed up to, with the five fields. It'll take four minutes and you'll immediately notice which one you can't remember the login method for — that's the account the register exists for.
Then make it a rule: no signup without an entry. The habit costs a minute at the point where you're already filling in a form, and it turns every future cleanup into a list you can work through rather than a memory test. Start saving and organizing the links that matter at BookmarkingToday.
