App-only services: preserving access and privacy

Epigraph

“HOW NOT TO DO IT.”

Charles Dickens, Little Dorrit, Book I, chapter 10, Gutenberg 963. The Circumlocution Office’s satirical motto, rather than a complete aphorism. The selected chapter opening and context were read, not the whole novel. It depicts institutional activity diverging from a task; it establishes neither a particular employee’s malicious intent nor the nature of every digital service.

About this article

In an imagined situation, an adult named Inna needs a document copy. Following treatment, holding her phone and reading small controls for long periods is difficult, although she previously managed digital tasks herself. The required app version also does not work on her phone. The service accepts requests through an app. Her son offers to do everything that evening. Perhaps the document will arrive. But who will see health information, receive the next reply and be able to end access? Someone disabled since childhood may have a very different history, without earlier digital ease. Both remain adult participants in their own affairs.

This article distinguishes a service, its channel, help with a particular action and a broad grant of permissions. It considers actual completion, fluctuating support needs and privacy that should not become the price of care. The discussion addresses illness and disability without assuming identical skills. Dickens and Montaigne help examine institutional arrangements and personal space. Their images establish neither local rights nor the security of a particular program.

I. The needed result differs from the way of applying

Inna needs a document copy, rather than merely an app appearing on a screen. This distinction is easily lost. An employee explains installation, her son offers his account, acquaintances suggest a newer phone. Each addresses part of the situation, but none establishes the result by itself. Name the task in ordinary language: what does the person want to obtain, why now, and what would count as completion? The technical route can then be discussed as a means, rather than becoming the sole purpose of the conversation.

Clarifying the purpose need not disclose a whole personal history. The organization may need particular information, but necessary data is a separate question. Inna can want to understand application conditions without publicly explaining why she owns this phone. Age does not replace a description of the barrier. Someone can have a recent device and an inaccessible interface, an older device and sufficient skill, or an appropriate channel with necessary support. “Does not use the app” does not yet identify what prevents completion or what an appropriate response would involve.

A service’s name can conceal several actions. Submitting a request, confirming information, receiving a message and obtaining the result differ. Assistance requested for the first stage should not turn the remainder into an implied promise. Clarify where help ends and what Inna, her son or the organization must do next. This is no universal document-application sequence. It asks how an actual process leads to the wanted outcome, and where the person has only reached an entrance to a system rather than a completed service or accepted request.

Distinguishing purpose from channel does not make technical rules irrelevant. Identification, transmission or verification can have actual requirements. Respect alone cannot abolish them, but a technical barrier should not automatically become a trait of the applicant. Clarify the basis and purpose of the particular condition. An understandable explanation can reveal which question concerns the organization, which concerns a device and which needs separate competence. Any participant’s confident manner is no substitute for an answer about how the service actually operates or what has been established in this case.

II. Different barriers need different answers

No device, no connection, unreadable text, an unclear instruction and inaccessible confirmation are different situations. Another lesson does not create a compatible phone; buying a phone does not guarantee an understandable form. Reading assistance may not resolve verification, while successful entry may not produce a result. This is no ready-made classification of every person’s abilities. For Inna, one actual barrier matters more than general advice to become confident online. Before selecting a solution, understand the question it is supposed to answer and the obstacle it could reasonably address.

W3C WAI Accessibility Principles considers different aspects of access to the web. Here it supports the narrow point that access is not exhausted by one action or one mode of perception. This article audits no app against a standard and turns no web description into certification of an entire service. One readable page does not establish an accessible next step. A useful function does not establish that a particular person can use it on the present device and under the conditions actually available to them.

A barrier can lie beyond a screen. An in-person route needs a suitable place, time and a way to reach it; a telephone route needs usable communication and an actual answer. Offering an alternative differs from providing it. If someone is told to visit instead, clarify what can be done there and which conditions apply. A journey should not rest solely on hope that any counter will resolve the task. Equally, uncertainty about a channel does not prove that no alternative exists. It identifies a question still needing an answer.

Several barriers may coexist without becoming one large project to reform the applicant. Inna can receive help with today’s task and separately discuss whether she wants a device change or learning. Expenditure, someone else’s time and disclosure are real costs of a proposed solution. See them before promising that everything is easy. A person may accept that cost or decline a particular route. Declining the route does not establish that they have rejected the necessary service itself or lost any basis for seeking an accessible way to obtain it.

III. Assistance and service accessibility are connected but distinct

Her son may complete the task that evening and provide real benefit. Help need not be withdrawn to demonstrate a system’s shortcomings. Where a matter is important, the person can choose the currently manageable route. A family’s one-off success still does not establish access next time. Both facts can be named: his help moved this task forward, while independent or organized supported access remains unestablished. Naming reliance does not devalue the actual assistance or make the son responsible for causing the broader problem that the service arrangement has left unresolved.

In GOV.UK guidance, assisted digital support means help using online parts of a service. It can be provided by telephone or in person; the guidance addresses the UK government service setting. This is a particular example of support belonging to service arrangements rather than being only a family duty. It supplies no worldwide legal rule or promised service for every visitor: the source has its own scope and exceptions. Check current conditions for the actual case rather than transferring foreign guidance into a ready-made demand on any employee.

Such support need not mean an entirely paper process. A member of staff might assist with a digital part while information continues through the system. Another channel may work differently. Clarify “alternative”: who performs the action, how does the person participate, and where will the reply arrive? Help completing a form and a different application route should not be merged. Otherwise, a debate over the word “offline” can continue without establishing whether any practically usable path exists for the particular task now. The label alone answers little about actual access.

A relative should not automatically become a permanent operator between someone and every organization. Their availability and limits matter. Inna should not be deprived of chosen assistance simply because her case illustrates a larger problem. The current task can be addressed while a recurring barrier is recorded separately. Immediate institutional change cannot be promised. This distinction avoids requiring a family to repair a whole service alone, and avoids treating their work as proof that the access problem has disappeared merely because one document has eventually been obtained.

IV. Ask the organization an answerable question

“Everything here is impossible” may describe a real experience while leaving the next step unclear. Inna can state the wanted action and a particular boundary: the offered version cannot be used on her device. Ask what application route or support the organization actually provides in that situation. This is an example of a clear subject, rather than a universal application form. Someone need not know professional accessibility vocabulary to describe the point where a required route stops working for them or what they still need to obtain.

Read the answer for its content. A help-section link differs from an explanation of a suitable route. An invitation to call differs from an actual conversation; a sent inquiry differs from an accepted request. If the new channel demands the same unavailable action, the problem may remain. That can be stated without assuming deliberate mockery. What practically changed: an accessible next step, a precise condition or merely another direction? What remains unknown can remain unknown until an answer arrives, rather than being filled with either optimism or a verdict that nothing can work.

One consequential point can be clarified when an answer is unclear. Does the offered help concern obtaining the document or only installing software? A specific question makes the answer’s limit easier to understand. Clear wording still guarantees neither a desired decision nor speed or courtesy. This article supplies no universal persuasion script, complaint procedure, deadline or telephone number. A legal question needs its applicable grounds examined for the country, service and circumstances, rather than a procedure inferred from a literary example or an unrelated foreign service-design manual.

A person can request support with that conversation. Clarify who asks and what information may be shared. A helper can make an explanation more accessible without turning Inna into a silent attachment to their own confidence. Where an employee addresses only the son, a question can be returned to the applicant in a form she can use. This is an author’s suggestion for communication, rather than a promise that every organization accepts any participation arrangement or waives particular authority requirements for the action actually being requested.

V. Follow access through to the outcome, rather than just entry

A created account can look like a major victory. Inna may still have submitted no request or learned nothing about its state. New conditions and notifications may follow entry. Consider the needed process rather than a general “connected” status. Which part was actually completed? What does the confirmation say? Where is the next reply expected? These questions require no technical audit of the whole system. They concern the task for which the person agreed to engage with an app, and the distinction between entering and obtaining the service.

Who receives notifications is particularly important. If a son helped submit the request, only he may see a message about missing information. That creates another dependency, even where the original action took minutes. Clarify how Inna will learn of the next step and who accepted that task. Hope that a relative notices an email between work and travel is no arrangement. This article prescribes no forwarding technique or account handover. An appropriate solution depends on the actual service and the chosen boundaries of participation, access and ongoing assistance.

The result may have conditions of use too. Receiving a file, understanding it, suitability for the purpose and obtaining the required document differ. An attachment does not automatically establish completion. Clarify what the organization issued and what next action is actually necessary. This establishes neither a copy’s legal effect nor an obligatory format in every case. The point is to avoid replacing the wanted outcome with a technically successful transmission when the task remains open and requires further participation. A delivered message can contain an unresolved question rather than the result itself.

Where an important stage has no usable continuation, describe that stage. The whole route need not be restarted, nor a working setting repeatedly changed. Preserve what is known and direct a new specific question to the relevant participant. One established fact need not vanish because another step failed. One unresolved step need not make the person incapable of everything. Access concerns completing the needed matter under actual conditions, rather than an obligation to keep demonstrating readiness for another technical obstacle without a clear way to reach the intended outcome.

VI. Access need not cost a whole private life

Inna may need assistance with personal information. Access to one matter does not by default require every conversation, document and future notification. Distinguish information needed for the action from the participation she chooses. “I cannot help without this” can express a real technical limit or the helper’s usual method. Clarify it without premature accusation or assuming that every broad demand is inevitable. An unknown appropriate method is better investigated than replaced with confident advice to disclose everything. The need for help does not settle the appropriate scope.

Official Gmail guidance shows why a feature name is insufficient: a delegate can read, send and delete email but cannot change the password. That is broader than help with one reply. In the NHS example, a chosen person’s access to GP services is arranged with the practice, can have limits and can be ended. These systems differ. Neither example establishes narrow access in the app you need. Check the actual permissions and ending arrangements first; nothing is being configured here.

Passwords or codes need not be handed over to demonstrate adult responsibility. Account rules, permissible assistance and representation require separate checking. Explanation differs from a legal action on someone’s behalf, and kinship does not establish all necessary authority. This article provides no identity-check bypass or instructions to use an inappropriate account for someone else’s affairs. If another participation arrangement is needed, seek its conditions from a suitable source, preserving the distinction between convenience, technical possibility and an action permitted under the actual service’s rules and relevant circumstances.

Someone can want assistance with one form without continuing oversight of their affairs. Consent to present support does not automatically extend to later applications. Purchases, an added service, publication or disclosure to a third party have their own subject. This need not require a formal discussion of every detail. A consequential action should not disappear inside “help.” Clarity supports the helper too: they can see an accepted task rather than having to guess an endless future responsibility for someone else’s digital life, notifications and access to necessary services.

A support request may need an error description or screenshot, without requiring unnecessary disclosure. This article does not establish a safe transfer method for every kind of information; the particular data and channel need their own consideration. Documents should not be posted publicly simply to obtain a quick stranger’s suggestion. Missing access to a service does not make privacy a luxury that must be surrendered first. Keeping boundaries does not mean abandoning necessary assistance either. A person may need support while still seeking a comprehensible route with appropriate limits to information and participation.

VII. Respect and an unresolved task can coexist

In Dickens’s satire, an institution efficiently continues its process without resolving the matter. The image can prompt a question about form and result. It does not establish that an actual employee wants to obstruct Inna, or equate a telephone queue with the historical fictional office. Literature remains a comparison. There can be different causes and actual limitations this article does not establish. No choice is required between declaring the entire system malicious and accepting oneself as the sole cause of an inaccessible step. The actual obstacle can be named without either conclusion.

Courtesy matters without equaling completion. Inna may be heard carefully yet receive no usable route, or a channel may work after an unpleasant conversation. These aspects can be named separately without gratitude for one being required to erase the other. Respect includes acknowledging an actual difficulty. It requires neither promising a result beyond what is provided nor presenting an unresolved service as a beneficial lesson in patience. The person still needs a substantive answer even where all participants remain calm, and calmness does not itself establish that the access question was answered.

Adult status should not wait for a successful installation. Technical difficulty does not, by itself, assess understanding of the task. Conditions and disagreements can be discussed while addressing the person through an accessible method. This is an editorial ethical position, not a judgement about local law or an individual’s decision-making ability.

Declining an unsuitable route need not mean declining the service. Inna may not want installation on terms she does not understand while still needing the document. Relatives should not automatically withdraw assistance as punishment for declining their proposed purchase. A family also cannot guarantee another channel by its own efforts. Limits can be named, chosen manageable support retained, and the organizational part acknowledged as unresolved. The distinction preserves both practical consequences and the person’s actual purpose, rather than interpreting refusal of one method as refusal of every possible outcome.

VIII. Solving it once and facing the next occasion

When the document arrives, name how it happened. A son helped with submission and reply; the organization provided suitable support; Inna completed part herself. These are different arrangements, without a single dignified winner. Describing them shows what supported the result and what repetition may require. “She knows everything now” can hide a dependency; “she can do nothing herself” can erase participation. Precision preserves both the achievement and the assistance still needed, instead of assigning the entire experience one family label that fits neither the task nor the person.

Ongoing access needs repeatable conditions, but one episode cannot guarantee them. Her son’s work, the device and the service process can change. Prior success is useful experience, rather than a permanent certificate. Reuse what still applies and check what changed when a new matter arises. There is no need to repeat the whole discussion of aging and the digital world. Clarify a particular dependency and current condition. Availability of renewed help differs from a general good intention to be somewhere nearby at an unspecified point in the future.

A recurring problem can be described to an organization as recurring. The actual sequence and remaining question matter more than every past digital disappointment. Yet someone need not become a public-interest researcher to receive their own service. Reporting a barrier promises no system change and should not delay seeking available support for the current task. Feedback and obtaining a result have different aims, though they may connect and help each other. An applicant’s need should not disappear behind an expectation that they first repair the process for everyone else.

A family can review its arrangement too. If help has become regular, name the workload, accepted scope and unavailable part. This need not be a contest between affection and independence. Avoid making another person’s time invisible or blaming Inna for every organizational constraint. Clear limits permit exploration of another arrangement on real conditions. It may remain unavailable. That does not cancel useful assistance already given or make the person a failed digital-reform project that relatives supposedly did not manage to finish through sufficient persistence, expenditure or instruction.

IX. Return the service to the human task

Inna’s purpose is no victory over a phone. She needs a document and an understanding of what is happening to her request. Technology may support that or leave an unsuitable route; a particular outcome requires facts. A screen should not be declared either liberation or humiliation in advance. Ask what became accessible, with what assistance and limits. This keeps the subject visible without requiring a person to endorse someone else’s judgment of progress before discussing their own need, or treating every difficulty as resistance to innovation.

An adult need not perform every movement personally to remain involved. Chosen assistance may be substantial. Asking what the person wants to understand, decide and delegate is more useful than assigning either complete digital independence or a permanent family operator in advance.

An unresolved question can have a precise state: an alternative-channel inquiry sent without reply; an incompatible device and unknown support; the document obtained but repetition dependent on a son. These descriptions are more useful than “everything is arranged” or “nothing is possible.” They promise no next success and demand no endless rechecking without new grounds. Identify the consequential question to revisit when information changes, and the current support limit that should not be concealed for reassurance. A precise unknown can remain open without erasing everything already established.

Access becomes a human question when the means stop obscuring the purpose. A person may learn, choose assistance, prefer another route or remain before an unconfirmed possibility. These states differ without measuring worth. A useful arrangement provides a clearer action, a retained voice and an honest limit to the result. It does not permanently replace an organization with a family or abolish family care to demonstrate a principle. Inna remains a person needing a service, rather than an obstacle in a report counting how many users have already moved into an app.

X. Today's assistance does not decide every future role

Imagine Inna completing a form herself yesterday, asking someone to read a question today and perhaps only being able to indicate an answer tomorrow. Variation need not mean inconsistency or justify taking over every decision. Clarify the action, an accessible way to participate and when the issue actually needs deciding. Illness does not establish the same assistance every day; disability does not mean inevitable deterioration.

Sometimes the hardest barrier is a demand to finish everything in one session. Ask whether an unfinished application is retained and what other route the organisation offers. Do not promise a save function that has not been checked in the particular service. The article prescribes no activity schedule. If necessary health care is involved, arrange a route with the responsible service according to urgency, rather than following a universal instruction to wait for a better day.

Someone with extensive support needs may not press buttons yet still choose an answer's content through an accessible method. If their preference cannot currently be established, a relative's opinion should not automatically be substituted. Appropriate communication support and the conditions of the particular decision need attention. Technical difficulty, understanding the question and legal authority are not one state.

Without family, money or accessible writing, a next step might be one oral request to an employee: “I cannot get through this stage. Who can explain the available assistance?” It guarantees no solution but does not require finding an unpaid relative first. Organisers should hear a service-design question, not a request to judge an applicant's gratitude or character.

XI. Personal space and institutional arrangements

Dickens's Circumlocution Office directs attention outward: why does the procedure outlive the very task? Montaigne's Of Solitude turns toward a person's own space. Together these perspectives help prevent someone disappearing into either an institution's process or family care. They are not one doctrine: satire exposes a social mechanism; the essay examines one's relationship with one's life.

An inward room is a useful image for discussing assistance, but the essay cannot simply be adopted as contemporary disability ethics. Near the statement about belonging to oneself, Montaigne argues for withdrawal when one can no longer add to society. We do not transfer that judgement to the reader. Needing help does not end membership of society, and privacy is not earned through social usefulness.

This raises a harder question than “alone or with a helper”: how can execution depend on someone else while decisions retain boundaries? Relationships and services need suitable arrangements. Someone might delegate sending one agreed document, continue receiving explanations of the outcome and decline permanent access to their whole inbox. If the service cannot support that boundary, the limitation should be visible before deciding. Inner freedom does not supply missing permission controls, and technical controls do not replace respectful conversation.

What this means in practice

If appropriate, choose one needed service and name the desired outcome without naming its app. Identify a stage where the route currently stops. Distinguish a missing device, connection, understandable action or available support without establishing a cause unsupported by information.

One question about a suitable channel or help can be formulated for the organization. Sending it is optional and differs from an accepted request. Where a relative participates, clarify their chosen part, necessary information and how the next answer will be received. No password transfer, another person’s account, device purchase or document publication is required to finish the practice.

Name what became known and what remains open. A channel answer does not establish service delivery, and one-off family help guarantees no next occasion. This practice clarifies the subject; it creates no legal authority, working channel or result. An important current matter and appropriate necessary assistance should not wait for the exercise to end or for a whole system to be repaired.

Key quotation

“The greatest thing in the world is for a man to know that he is his own.”

Montaigne, Essays, Of Solitude, I.XXXVIII in the Cotton/Hazlitt 1877 edition. Gutenberg 3600. Selected context was read, not the whole essay. This article explicitly rejects applying the neighbouring historical judgement about withdrawal after losing social usefulness to its readers.

Connections between traditions

Comparison	A shared question	A boundary
Dickens, Little Dorrit I.10, and Montaigne, Of Solitude	A person should not disappear into an external order	Social satire and Renaissance inquiry into personal space address different tasks
Montaigne and chosen digital assistance	Support and a separate sphere of life can coexist	An inward image creates no technical restriction and does not justify exclusion because support is needed
Dickens and assisted digital support	A procedure's movement differs from access to its result	Literature proves no malicious intent; UK guidance has a defined scope and exceptions

These are three substantive comparisons of different kinds. Product guidance below supports its own narrow claims; it is not an additional religious tradition.

Primary sources and research

1. DICKENS. Book I chapter10 opening, web lines1732–1751; edition preface lines158–163. Institutional satire and epigraph. Not a factual claim about a current employee.

2. MONTAIGNE. Cotton/Hazlitt1877 title; Of Solitude I.XXXVIII, lines3301–3307 and3317–3319. Private space, key quotation and explicit rejection of usefulness-conditioned withdrawal. Selected passages, not full essay; English translation mediation.

3. GOVUK. Main text lines69–99 and update date. Assisted digital as organisational support. UK guidance includes stated exceptions; not a worldwide entitlement.

4. W3C. Summary, four principle groups, components and text alternatives, lines95–148. Access has several components and interaction requirements. Not complete standard or app audit.

5. GMAIL. Main text lines17–21,39–66,77–82. Delegate scope and separate removal. No current account checked; not one-message access.

6. NHS_PROXY. Full main text lines12–68. Chosen scope, limits and ending proxy access in GP system. Example in its specific system, not universal procedure.

Pages and selected passages checked again on 24 October 2026. This is not full-book reading, a specific service audit or an access change.

Tags

illness, disability, adult, app, service, accessibility, digital exclusion, assistance, document, channel, skill, support, participation, consent, privacy, relatives, outcome, notifications, boundaries, dignity, fluctuating condition, communication, Dickens, Montaigne, humanism, satire, authority

About the authors

Andrey Zarinsh is the author and founder of United Wisdom. He explores inner transformation, unity among traditions, intercultural dialogue and contemporary spiritual discipline. Instagram: @andrey.zarinsh.

Maria Evilkut is a coauthor of United Wisdom. Alongside her research, she seeks to test these ideas in practice and observe how unity and mutual understanding work between people and cultures in real life. Instagram: @ilkutki.