gitwtfhub

wtf is phone-record-manager?

nextweb4/phone-record-manager — explained in plain English

Analysis updated 2026-05-18

164PythonAudience · generalComplexity · 2/5LicenseSetup · moderate

TL;DR

A Windows desktop app for tracking which accounts are tied to which phone number, useful when manually replacing a number across many services.

Mindmap

mindmap
  root((repo))
    What it does
      Tracks phone number bindings
      Manual replacement checklist
    Tech stack
      Python
      PySide6
      SQLite
    Use cases
      Track linked accounts
      Encrypted backups
    Audience
      Windows desktop users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Keep a record of which websites and apps are linked to each of your phone numbers.

REASON 2

Track a manual phone-number replacement across many accounts without missing one.

REASON 3

Back up your account list with password-protected encrypted exports.

REASON 4

Search and filter a large list of registrations by status or tag.

What's in the stack?

PythonPySide6SQLite

How it stacks up

nextweb4/phone-record-managerresonancegnatassess/lossless-scalingsilentfleetkk/ai-market-pulse
Stars164163163
LanguagePythonPythonPython
Setup difficultymoderateeasymoderate
Complexity2/52/53/5
Audiencegeneralgeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Windows only, running from source needs Python 3.12 with pinned, hash-verified packages.

Use freely for any purpose, including commercial use, under the MIT license.

Wtf does this do

Phone Record Manager is a desktop application for Windows that helps someone keep track of which phone numbers are linked to which website and app accounts, so they can manage the manual process of replacing a phone number across many accounts. It is built with Python, the PySide6 interface library, and a local SQLite database, and everything is stored on the user's own machine rather than in the cloud. The application does not automate logging into other services, submitting verification codes, or bypassing any security checks. Instead, it functions as a structured checklist: a user records each phone number, its current status such as active or being replaced, and a list of the websites and apps tied to it. When it is time to switch a number, the user creates a replacement task, and the application tracks each account that still needs to be manually updated, preventing accidental edits to accounts already involved in an active replacement. Other features include a master-password login using a standard password-hashing method, an idle-lock timer, light and dark themes, both Chinese and English interfaces, CSV import and export, and encrypted backups using a well-known Python encryption library. Restoring a backup checks the data's structure and internal rules before replacing anything, all inside a single database transaction so a failed restore cannot leave the data half-written. The README is direct about a security boundary: the master password only controls access through the application interface, it does not encrypt the underlying database file, so anyone with direct access to that file could still read its contents. The project targets Windows only, requires Python 3.12 to run from source, and ships prebuilt release packages including an installer, though the release is not code-signed. It is released under the MIT license.

Yoink these prompts

Prompt 1
Walk me through setting a master password and locking down this app on first launch.
Prompt 2
Explain how to start a replacement task and track it to completion.
Prompt 3
Show me how encrypted backup and restore work in this application.
Prompt 4
Explain the security boundary the README describes around the SQLite database.

Frequently asked questions

wtf is phone-record-manager?

A Windows desktop app for tracking which accounts are tied to which phone number, useful when manually replacing a number across many services.

What language is phone-record-manager written in?

Mainly Python. The stack also includes Python, PySide6, SQLite.

What license does phone-record-manager use?

Use freely for any purpose, including commercial use, under the MIT license.

How hard is phone-record-manager to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is phone-record-manager for?

Mainly general.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.