Why Age-Friendly Technology Must Adhere to Data Minimization

The question is how authorization, minimisation and human judgement constrain technical power

Age-friendly technology addresses family life and changes in ability, where data can be highly sensitive. Experience from Japan and globally indicates that minimization, transparency, consent, human review, and the right to withdraw must be established during the product definition phase.

“Collecting more data does not equate to better protection” is a proposition that evidence may support or overturn, not a conclusion established because a Japanese case exists. For how authorization, minimisation and human judgement constrain technical power, the analysis also tests “Every data field must specify its purpose, accessors, retention period, and deletion method” while retaining population, setting, period, failed cases and the current non-technical alternative.

What each source can and cannot establish

Evidence for “Every data field must specify its purpose, accessors, retention period, and deletion method” starts with publisher, year, population and method, and corporate statements need independent material or local testing before becoming outcome claims.

1. 01
   Japan Ministry of Health, Labour and Welfare: Promotion of Care Technology ↗

   Supports analysis of how Japan links care-technology adoption, workflow improvement, productivity and care quality.

2. 02
   World Health Organization: Integrated care for older people (ICOPE) ↗

   Supports person-centred assessment, continuity of care and integrated community-level services.

3. 03
   Danish Health Authority: Welfare Technology and Older-People Care ↗

   Supports comparison of welfare technology, independence and care quality without treating welfare systems as interchangeable.

4. 04
   Cabinet Office of Japan: Annual Report on the Ageing Society 2025 ↗

   Provides the demographic, living, employment, health and participation context for Japan’s ageing society.

Move from a feature to a complete accountability chain

Data minimisation begins at design, asking for every field its purpose, necessity, access, retention and consequence of omission. High-risk home data should become events on-device where possible, transmitting only what response needs and deleting data without a current purpose. Governance begins with purpose and limits each field, frequency, inference, accessor, retention, training use, human review, correction, export, deletion and stop. Safety is not unlimited permission.

Place the argument inside one observable task

Ask the person or proxy to restate collection and consequences, then actually change permission, correct, export and delete; showing a consent screen does not establish control. For this analysis, also record “data fields”, “access count” and the non-technical method so that “Every data field must specify its purpose, accessors, retention period, and deletion method” can be attributed to the intervention rather than hidden support.

Success is not a completed demonstration. “Collecting more data does not equate to better protection” must remain understandable, interruptible and closable across routine, exception and unavailable states.

Transfer operating method and evidence discipline

Japanese and global ethics place dignity, choice and exit inside the product rather than adding a privacy notice after deployment.

Redraw accountability before selecting product form

Chinese projects need local legal assessment by data type and must address the boundary between family concern and unauthorised viewing in multigenerational homes. Requirements for cross-border data, personal information, and health data differ; actual projects require local legal assessment.

Use consistent measures across routine, exception and unavailable conditions

1. 01
   data fields

   “data fields” helps answer how authorization, minimisation and human judgement constrain technical power. For “Collecting more data does not equate to better protection”, keep device output, human confirmation and completed action separate, and investigate when the three disagree.

2. 02
   access count

   Review the work and waiting time carried by the person, proxies, family, service providers and data stewards around “access count”. Improvement in “Every data field must specify its purpose, accessors, retention period, and deletion method” that depends on permanent extra labour cannot be attributed to the intervention alone.

3. 03
   withdrawal completion

   “withdrawal completion” must include exceptions, refusal and unavailable-system cases. While testing “Collecting more data does not equate to better protection”, using safety to justify unlimited collection and control means an improved average still triggers pause or reframing.

4. 04
   human review

   Compare “human review” with the same task, population, version and response rule. A material version change in this analysis requires a new baseline.

5. 05
   correction

   For “correction”, state the population, baseline and time window in this analysis, and retain “data fields” so one attractive metric cannot conceal deterioration elsewhere.

For “Collecting more data does not equate to better protection”, the period for “data fields” and “access count” covers weekends, nights, visitors, shift or environmental change. If “Every data field must specify its purpose, accessors, retention period, and deletion method” has health, safety or cognitive implications, it also requires predefined human review, professional referral and exclusion criteria.

Keep the conditions behind the decision traceable

Topic record: For “Collecting more data does not equate to better protection”, treat “Every data field must specify its purpose, accessors, retention period, and deletion method” as a judgment that field evidence may support or overturn.

Baseline record: Testing “Collecting more data does not equate to better protection” retains population, task frequency, current method, elapsed time, help, near misses and non-completion; data fields and access count use one denominator and period around “Every data field must specify its purpose, accessors, retention period, and deletion method”, including refusal and failed cases.

Ownership record: Around “Collecting more data does not equate to better protection”, the person, proxies, family, service providers and data stewards receive distinct duties for choice, operation, confirmation, maintenance, payment and stop authority; every action testing “Every data field must specify its purpose, accessors, retention period, and deletion method” names an owner, deadline and fallback.

Exception-closure record: “Collecting more data does not equate to better protection” predefines “using safety to justify unlimited collection and control” as a failed case and retains preceding conditions, version, human takeover, recovery time and impact; closure requires recovery of the life task behind “Every data field must specify its purpose, accessors, retention period, and deletion method” and human confirmation.

Change and exit record: After a change in threshold, place, people, shift, connectivity or service resources affecting “Collecting more data does not equate to better protection”, retain the reason, approver, new baseline and grounds under “Every data field must specify its purpose, accessors, retention period, and deletion method” for continuation, downgrade or exit.

Decision rationale: Continue, modify or stop decisions around “Collecting more data does not equate to better protection” cite source records, show how withdrawal completion and human review support “Every data field must specify its purpose, accessors, retention period, and deletion method”, and retain unresolved uncertainty.

Review cadence: At pilot entry, first exception, version change and before scale, reassess “Every data field must specify its purpose, accessors, retention period, and deletion method” and compare data fields, access count, withdrawal completion, human review, correction under unchanged definitions.

Know when not to adopt and when to stop

Stop processing when purpose expands, access is excessive, withdrawal is not executable, permissions go unreviewed after cognitive change, training exceeds authorization, or human review is nominal. Retain a lower-technology, lower-burden and reversible alternative.

Five checks before procurement, pilots or partnerships

Turn overseas experience into local methods

For BEIIU / 辈佑, “Every data field must specify its purpose, accessors, retention period, and deletion method” becomes useful when it leads to clearer requirements, evaluation methods, accountability and exit conditions in product and partnership practice.