ABOUT

Before sharing personal information

You can plan for important accounts, photographs and bills without gathering every password or private record. Start by describing what matters, who may need help and where authorized instructions are kept. This guide helps you decide what to leave out of a note, worksheet or message. It is advice about what you choose to share—not an account of what this website collects or retains when you visit.

Read the website privacy notice

Before you share anything

Choose the kind of information you are about to use. See what can usually be written as a general description, what should not go into a public form and a safer next step.

An account or sign-in

Do I need to write the password or recovery code?

Usually no. A private inventory can name the service, describe why it matters and identify where authorized recovery instructions are kept. It should not turn a public worksheet into a password list.

Record a descriptive service name and the location of its official instructions. Store actual credentials only in an appropriately secured arrangement.

Build a private inventory map

Photographs or messages

Should I upload a picture or copy a conversation to explain the problem?

A description is usually enough to choose guidance. A photograph may reveal people, locations and dates; a private conversation affects everyone who participated. Do not upload them simply to obtain general advice.

Describe the kind of material instead of showing its contents, then check that a safe, separate copy exists if preservation matters.

Check a recoverable copy

Bills, banking or health records

Can I include an account statement or medical record in a question?

Avoid entering statements, account numbers, patient information or identification documents into a general feedback or learning form. Even a cropped image can reveal private details. The necessary next step depends on whether you have permission or legal authority.

Write down only the category and issue—for example, “a utility bill may stop”—and use the responsible provider’s protected process for a specific account.

Sort a recurring payment

A correction or broken link

What is enough information to report a problem?

The page title, visible wording, public source and description of what happened are generally enough. You do not need to send an account number, private screenshot, sign-in code or a relative's records.

Prepare a correction note using public facts. Review it before choosing whether and how to send it.

Prepare a correction note

Start with what you can leave out

An email address may be important because it receives bills and recovery messages. That does not mean a preparation worksheet needs its password, every message in the inbox or a copy of a person’s identity document. For many useful plans, the name of the service, the reason it matters and where authorized instructions can be found are enough.

Use the least revealing description that still lets you take a useful step. Instead of typing a bank account number, write 'the household account that pays the electricity bill' in a private note. Instead of attaching family photographs, note where the originals and any separate backups are held. People who later need access can follow the provider's lawful process, rather than inheriting an unsafe list of secrets.

Reading, writing and sending are different activities

Reading an article does not require you to volunteer information about your family. Typing into a search field or worksheet is a different choice. Sending a correction, opening a third-party website or downloading a file creates another set of questions about where information goes and who may receive it.

Even a website without a form asking for your name can create technical records when you visit. Depending on the service, those may include network requests, server logs, cookies or analytics. Before sharing private information, look for a clear explanation of what that particular website collects and what happens to it. If the explanation is missing, choose a less revealing way to find what you need.

Before you use a tool, find out where the information goes

A printable checklist, a form that prepares text in your browser and an online submission may look similar. They are not the same. Before entering sensitive details, check whether the result stays on your device, is saved in browser storage, is sent to a server or is passed to another service. A button that says 'Save' does not, by itself, answer that question.

The guides and planning questions are designed to work with general descriptions. If a feature asks for more than the task needs, stop and consider a less revealing route. A paper note kept securely, the provider's official channel or advice from an appropriately authorized professional may be more suitable than an unfamiliar form.

Account recovery is not permission to enter an account

Knowing that someone uses a password manager, phone or cloud service is different from being entitled to open it. The person may have chosen to share some practical information while keeping private correspondence private. This remains important when illness, disability or grief makes a situation urgent.

Where a person can still make decisions, involve them and respect the limits of their consent. When assistance is legally delegated—or after death—check the scope of that authority and the provider’s current process. A family relationship, possession of a device or a copied password does not settle the question.

Photographs and messages belong to more than one story

A family photo can be precious and revealing at the same time. It may show children, a location, a medical setting or someone who would not want it made public. A message can contain someone else’s confidential information. Preserving memories calls for judgment about both the person whose records they are and the people represented in them.

When discussing a photo problem, describe what matters—'the originals may be in one cloud library'—rather than uploading the images to explain it. When making a backup, check where the copies travel and who can open them. Deletion, memorialization and sharing should not be treated as interchangeable decisions.

Paper, downloads and shared devices need care too

An offline worksheet can be useful because it works without a network connection. It can also be left on a kitchen table, a shared printer or a device used by several people. A downloaded document may remain in a Downloads folder long after the task is finished. A browser's recent files and print queue can make a private note easier to find than expected.

Choose storage that matches the sensitivity of the content. If you share a computer, consider who can see saved files or printing history. Record categories and instructions separately from passwords and recovery codes. Ask before taking a paper list home from someone you are helping.

Check third-party pages on their own terms

The guides may point you to a bank, a technology provider, a regulator or a research publisher. Following those links takes you to a different organization and a different set of rules. Check the destination before supplying information, especially when a link asks you to sign in or upload identity documents.

An official help article can explain an account provider’s procedure, but it does not authorize the project—or you—to access someone else's account. Use current provider instructions for account-specific requests, and check the destination address rather than relying on a familiar-looking logo.

Give people room to decide what is shared

A digital-life plan should not require one person to surrender their private life to another. Some people share devices because of cost or need help reading; others must keep accounts private for personal safety. A relative or someone in the same household is not necessarily a safe choice. Ask the person concerned who should see which records, and respect their wish to use an independent, appropriately authorized helper.

Ask what assistance is wanted before collecting information. Use plain-language descriptions, offer time to think, and separate practical responsibilities from personal messages. For children and others whose information is particularly sensitive, avoid circulating photographs, diagnoses or identification details as examples in a public form.

What to look for in a website’s privacy information

Before sending a form or using a digital planning tool, look for an explanation that applies to that particular service. What information does it receive? Are technical visit records made? Who else may handle the information, why is it used and how long is it kept? How can a visitor ask a question or exercise rights that apply to them? A promise to “respect privacy” does not answer those questions.

If the information is missing or unclear, choose a general description instead of a password, statement, medical record or family photograph. A calculation inside a browser can still accompany other network requests. A downloadable worksheet and a page that sends a message may also handle information differently, so check the specific action before using it.

Choose a safer next step

If you want to prepare for yourself, start by recording the kinds of accounts that matter, not their passwords. If you are helping someone living, ask what they want assistance with and what authority exists. If someone has died, do not assume access to their phone or email provides authority to use private content.

Choose one of the four situations in Before you share anything. Each opens a short explanation and points to an existing guide or preparation activity. When your next step requires documents, credentials or a provider account, use an appropriately protected route outside the general educational tools.

Questions people ask

Do I need to enter passwords to use the guides?

No password is needed to understand the written guidance. Use descriptions such as 'main email account' or 'phone used for codes.' Do not place actual credentials or recovery codes in public feedback forms or printed worksheets that other people can see.

Does downloading a worksheet mean the site has saved my information?

Not necessarily. Downloading can create a file on your device, but that alone does not tell you what the website recorded about the visit or whether a form sent information. Keep saved files in a secure place and use general descriptions until the service explains its data handling.

If a tool says it runs in my browser, is it completely private?

Not necessarily. A calculation performed in your browser may avoid sending the answers to an application server, but the page can still make other network requests. Do not assume a whole website is private because one activity happens in your browser. Use general descriptions rather than passwords, account numbers or private records.

Can I share a relative’s passwords to get better advice?

No. Describe the situation without passwords, access codes or private messages. Advice about legal authority and recovery should come from the provider's official process or a qualified adviser.

Should I upload a photograph to ask about backups?

You can usually explain a backup problem without showing the image. Start by checking whether an independent copy exists and whether it can be opened. Consider every person pictured before sharing an image.

Does the project see every account or device I read about?

Reading general advice does not tell an article which accounts you personally own. It also does not establish what visit records or selected topics a website may collect. A website should explain its own practices separately; do not enter your private account list just to use educational guidance.

What information is useful in a correction report?

Usually a public page title, the wording or control at issue, what happened and a public source. Avoid names, addresses, account statements and private screenshots. A draft correction note is not the same as sending it.

What if I use a shared computer?

Think about who can see downloads, browser history, printed pages or files left open. For sensitive notes, use a secure place you control or a trusted offline arrangement.

Is consent the same as legal authority?

Not always. An adult who can decide may give limited permission, but formal financial, medical or after-death processes can require particular authorization. Provider rules and local law matter.

Can I print these instructions?

The explanations are written to remain useful on paper. Printed guidance does not update automatically, so verify current provider procedures before relying on an older copy.

Where can I start if I do not want to enter any personal details?

Read Explore Your Digital Life or open the four general situations under Before you share anything. You can select a topic without identifying yourself or the person you are thinking about.

Further reading and source scope

These references explain the evidence and its limits. Inclusion here does not verify current provider procedures or establish authority in your circumstances.

Website privacy notice

This notice describes this website's operation. The guidance above explains how to share information safely; it is not a description of website processing. Last updated: 29 October 2026.

Who is responsible

Digital After Life Project is the project responsible for this website. Questions and requests about website processing can be sent to info@digitalafterlifeproject.org. Do not send passwords, account statements, identity documents, private conversations or authentication codes.

Browsing and local tools

Public pages do not require an account. This application does not include advertising trackers. Optional first-party usage analytics is off unless you choose Allow analytics. We respect Global Privacy Control and Do Not Track signals. Use Analytics preferences in the footer to decline or withdraw permission at any time; this stops future collection and clears the analytics browser identifiers.

If you opt in, this website records public page paths (not query strings), referring website names (not full URLs), broad device classes, selected public controls, reading-depth milestones and active viewing time. Anonymous random browser and session identifiers are hashed before database storage. A browser identifier expires after 30 days; a session expires after 30 minutes of inactivity. Consent and the browser identifier use local storage; the session identifier uses session storage. Analytics does not set cookies. Counts are estimates of opted-in browsers, not exact people or all visitors.

No raw IP addresses, full user-agent strings, form entries, inventory content, passwords, article-search text or private admin activity are stored in analytics. Country and region remain unknown because no trusted geographic source is currently configured. We do not infer location from browser language or send visitor IP addresses to a geolocation service. Active time excludes hidden and idle tabs and is still an estimate, not a measure of attention.

The illustration-theme preference is also stored in your browser's local storage. You can remove local data through your browser settings. The on-page planning tools operate in the browser; their entries are not submitted to our server. Information you choose to print, copy or save is under your control.

Restricted editorial sign-in

Admin sign-in accepts only the approved owner email address. The server sends a single-use code through Gmail using a server-held Google App Password. Gmail processes the recipient address and email contents to deliver that message. Never enter a Google password or App Password in the public sign-in form.

Sign-in codes expire after ten minutes and allow at most five attempts. The database stores keyed code digests, hashed session identifiers and rate-limiting records, not plaintext codes or session tokens. A secure, HttpOnly session cookie lasts up to eight hours; a separate short-lived cookie binds the code to the requesting browser. Sign-out revokes the server session and clears these cookies.

Hosting and service providers

The website is hosted through Replit and uses PostgreSQL for editorial records and authentication state. Hosting and network providers may process technical connection information to deliver, secure and operate the service. Their own infrastructure logging and retention are governed by their policies; this project does not promise a specific deletion period for provider-controlled logs. Gmail is used for admin sign-in messages, not marketing.

Retention and requests

Usage analytics is held separately from editorial and authentication records. The application targets 90-day retention: older page records and their associated events are deleted during collection, with cleanup attempted at least hourly while collection is active. If the site receives no collection requests, cleanup waits until collection resumes. Withdrawing analytics permission does not automatically erase previously collected, pseudonymous records. There are no session recordings or keystroke logs.

Expired session, code and rate-limit records are cleaned up when approved sign-in requests run. Expiry prevents their use, but is not a guarantee of immediate database deletion. Editorial revisions, review records and audit history are retained for accountability and are append-only in the application. Published article text may remain available until the owner updates or withdraws it.

Contact the project using the address above to ask about access, correction or deletion of information relating to you. The project must consider the request, applicable requirements and the need to preserve legitimate editorial or security records; deletion is not promised automatically. Do not send sensitive evidence unless a suitable process has first been agreed.

Related provider information: Replit privacy policy and Google privacy policy. This notice is an operational explanation, not a claim of independent legal certification.