Digital Identity Management

Requirements

1. Members must conduct a full digital footprint audit at least once per year, covering data broker records, breach database entries, social media, and publicly searchable filings.
2. A tiered email architecture must be maintained at all times: a private primary address for trusted personal contact only, a professional address for business correspondence, a service address for account registrations, and disposable aliases for any service not explicitly trusted.
3. Every account must use a unique, randomly generated password stored in a reputable password manager. Password reuse across any two accounts is prohibited without exception.
4. App permissions on all devices must be reviewed quarterly. Location, microphone, and camera access must be restricted to applications that functionally require them. Permissions granted during setup are not to be treated as permanent.
5. Accounts that have been inactive for more than twelve months must be deleted. Where a platform does not offer account deletion, the account must be stripped of accurate personal information and the associated email address replaced with a disposable alias.
6. All email addresses in active use must be checked against known breach databases at least annually. Any address confirmed in a data breach must not be used as the primary contact for financial, professional, or sensitive accounts.

The Aggregation Problem

Each piece of information you share online appears inconsequential in isolation. A name on a forum. A phone number on a registration form. A tagged photograph. A business registration. Individually, none of these cause concern. Aggregated, they build a profile detailed enough to impersonate you convincingly, target you specifically, or compromise the institutions and individuals around you.

High-net-worth individuals, executives, and founders are not targeted because attackers are technically sophisticated. They are targeted because the potential return justifies effort that would not be applied to an ordinary individual. The attack surface for someone with significant assets or institutional access is different in kind, not just degree. Standard consumer security practices are not designed for that environment.

Conducting the Audit

Begin by searching your full name, email addresses, and phone numbers across the major data broker aggregators. What you find will likely surprise you. The primary sources of exposure to address:

• Data brokers — Spokeo, Whitepages, BeenVerified, Intelius, and similar services compile publicly available records and sell them commercially. Most provide an opt-out or removal mechanism, though records re-accumulate over time and removal must be repeated. Paid services that automate ongoing removal requests are worth considering for anyone with significant exposure.
• Public records — Property ownership, court records, company directorships, and electoral rolls are searchable in most jurisdictions. Where possible, use a registered agent, nominee director, or legal entity for filings that would otherwise list your home address or personal details directly.
• Social media — Historical posts, tagged photographs, listed affiliations, and geolocation data remain indexed long after you have forgotten them. Conduct a full audit across every platform on which you have ever had a presence. Remove what you can. Restrict visibility on what you cannot remove.
• Breach databases — Services such as Have I Been Pwned catalogue credentials and personal data from known breaches. Every email address you use should be checked. An address that appears in a breach should be rotated out of sensitive accounts immediately, as the associated password — however old — may be in active use by attackers against other services where you have reused it.

Email Architecture

Using a single email address for all purposes is the most common and most consequential failure in digital identity management. A breach of any single service exposes your primary contact, your password reset path, and your identity simultaneously. The required tiered architecture eliminates this single point of failure:

• Primary address — Known only to people you trust personally. Never used for registrations, newsletters, or commercial services of any kind. Treat it as you would a private phone number: given out rarely and only when there is genuine need.
• Professional address — Used for business correspondence. Listed publicly where your role requires it. Assume that anything sent to or from this address may eventually be seen by parties beyond the intended recipient.
• Service address — Used for account registrations, software trials, subscriptions, and any commercial service. A breach of a service using this address does not compromise your primary or professional contact.
• Disposable aliases — For any registration you do not trust, any one-off interaction, or any service you are not confident will handle your data well. Tools such as SimpleLogin or Apple's Hide My Email generate unique forwarding aliases that route to your inbox and can be deactivated individually when they receive spam or when you no longer need them.

Account Hygiene

Most people hold dozens of active accounts they no longer use. Each one is a potential breach vector — a stored password, a linked email address, a saved payment method. The annual account audit is not optional: it is the mechanism by which exposure is kept bounded rather than allowed to accumulate indefinitely.

When reviewing app permissions, the default posture is denial. An application does not receive location access because it asked for it during installation. It receives it only if you have reviewed why it needs it and concluded that the function genuinely requires it. This applies with particular force to microphone and camera permissions, which are rarely necessary and frequently over-requested.