Lead illustration: A visual metaphor for visible files and less visible data trails. The scene does not represent measured proportions. AI-generated illustration / The Steward.
The files we save are only part of our digital lives. Traces, predictions and shared records call for care suited to the power we actually have.
Suppose you open a family photograph on your phone. You see a birthday cake, a crowded table, someone caught halfway through a laugh. The picture is easy to recognize as something worth keeping.
Now consider what sits around it. Depending on the camera and its settings, the file may carry a location. A shared album may give other people access. The people pictured may have different wishes about where it appears. Years later, someone may inherit the image without knowing a single name.
One photograph already asks more of its keeper than finding enough storage.
Part 1 introduced stewardship as a responsibility accompanying our interests in data. We can regard information as our property while recognizing duties to people represented in it, affected by its use, or eventually entrusted with its care. The fiduciary comparison is an ethical analogy here, not a claim that every reader holds a formal legal office.
What, then, belongs in our field of attention? The answer includes the data we create, control, or access, plus information made about us that we may influence without controlling. Those relationships call for different kinds of care.
Start with what you meant to keep
Photographs, letters, spreadsheets, recordings and emails are the obvious beginning. We usually know why we made them, even if the reason has faded by the time we find the folder again.
Their familiar appearance can conceal competing interests. A letter belongs in your archive, but its writer may have expected a private audience. A shared work document can be visible to you without being yours to circulate. Access gives you an opportunity to handle information; it does not settle whether copying, publishing or keeping it indefinitely is appropriate.
Preservation and restraint belong together. A useful family archive needs names and context. A useful working folder may need fewer obsolete copies. Deciding what should survive also means deciding who should be able to see it.
The records made around you
Other records arise while we are doing something else. Searches, purchases and interactions with services can leave behavioral traces. Exactly what is collected, where it is stored and how long it remains depend on the service, device, account and settings. An account history is one part of that picture.
Google’s search-history guidance illustrates the distinctions. It describes controls for saved account activity, while noting that a browser may retain a separate history. It also explains that deletion starts a process and that certain data may be retained longer for limited business or legal purposes. A switch can be useful without being a universal eraser.
Information can then be turned into an inference: a conclusion drawn from other records. Google explains that its advertising categories use activity to estimate which audiences a person belongs to. An estimate can be wrong. Researching a purchase for somebody else does not necessarily describe your own circumstances.
Some derived records carry greater consequences. The US Consumer Financial Protection Bureau describes a credit score as a prediction based on credit-report information; scores can differ with the model, data source and calculation date. A score is produced through choices about records and methods, not detached from human decisions simply because a computer calculates it.
We cannot sensibly call all these records our private filing cabinet. We may be able to inspect an account history or change an advertising preference while having little visibility into another organization’s systems. Stewardship includes noticing that boundary. It cannot make an individual responsible for every use others make of information about them.
What travels with the contents
Metadata is information describing other information: a photograph’s location, a document’s creation date, or the time and participants associated with a communication. The envelope around a letter is a helpful comparison, provided we do not mistake the outside for something harmless.
Apple’s photo-metadata guidance offers a concrete example. With the relevant camera location permission enabled, location coordinates are embedded in photos and videos. Recipients may be able to read them. Apple also describes ways to inspect the information and omit location when sharing through Photos.
Context can expose something sensitive without revealing the contents. It can also mislead. Imagine a call log containing a medical practice’s number: it does not tell us whether the caller was a patient, a relative, an employee or someone asking directions. Concern about privacy should make us more careful about such records, including the conclusions we draw from them.
The practical question is what accompanies the item we intend to share. Looking at the image itself may answer only half of it.

When the household produces the record
A connected doorbell, speaker or thermostat adds another complication. One person buys and configures the device; other people encounter it. A visitor does not choose the household’s account settings.
Here, precision matters. A microphone’s presence does not by itself establish continuous cloud recording. Detection, recording, transmission and retention are separate questions. Google’s Home and Nest privacy documentation describes different treatment by device and feature: some processing happens on the device, while enabled camera services can send and retain recordings. Configuration and service arrangements matter.
The person managing the household’s equipment should therefore ask what a particular feature does, who can access its records and whether its coverage is appropriate. A conversation with housemates, a less intrusive camera position or a review of recording settings may be more useful than a general promise to take privacy seriously. Visitors deserve consideration too.
Providers carry substantial responsibility of their own: for intelligible choices, appropriate safeguards and the uses they make of the data. Buying a device does not give a household control over the company behind it. Duties should be proportionate to actual power.

The next keeper needs a way in
Some records arrive through inheritance: scanned correspondence, an old computer, an archive assembled by a relative. Receiving the material does not tell us who should read every part of it. A collection can preserve a life while also containing confidences about people still living.
Our own collections will present the same questions. A folder called “Important” may be less helpful to its next keeper than a short explanation of what it contains and why it matters.
Access needs planning as well as good intentions. Apple’s Legacy Contact system, for example, allows a chosen person to request certain account data after a death using an access key and required documentation. It does not include everything: passwords and passkeys in iCloud Keychain are excluded. That distinction is a reason to check a provider’s actual arrangements, rather than assume that one nomination transfers an entire digital life.
An inventory can begin modestly. Choose one account or collection that matters. Record where it lives, who can access it, whose interests it touches and what you want its next keeper to understand. Note what you can change yourself and what depends on somebody else. Keep this description securely; an inventory does not need to become an unprotected list of passwords.
Then make one useful improvement: review a shared album, add context to inherited files, inspect a device’s settings or investigate an account’s succession options. The aim is a clearer relationship with what is already in your care. Below the waterline lie real responsibilities, but they become manageable when we distinguish what we hold, what we can influence and what others must answer for.
