View Issue Details

IDProjectCategoryView StatusLast Update
0006843Talermerchant portal webuipublic2026-01-25 14:10
Reportersebasjm Assigned ToResolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritylowSeverityfeatureReproducibilityalways
Status implementingResolutionopen 
Product Versiongit (master) 
Target Versionpost-2.0 
Summary0006843: every input type can be forgetable, handle UI to add checkbox
Descriptionthis apply to the order

https://docs.taler.net/core/api-merchant.html#private-order-data-cleanup
Tagsprivacy

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

sebasjm

2022-01-19 13:54

developer   ~0018643

Adding example of the current new order form
Selection_999(167).png (40,342 bytes)   
Selection_999(167).png (40,342 bytes)   
Selection_999(166).png (45,165 bytes)   
Selection_999(166).png (45,165 bytes)   

sebasjm

2022-01-19 15:52

developer   ~0018644

Selection_999(165).png (55,516 bytes)   
Selection_999(165).png (55,516 bytes)   

belen

2022-01-22 11:46

reporter   ~0018650

I may be missing something here, but putting the responsibility of removing customer information on merchants doesn't seem to me the ideal way of going about this. If Taler as a project considers that certain customer information should not be kept by merchants after it is no longer needed (e.g. the customer’s shipping address), why not introducing this behaviour by design? Essentially, after an order has been fulfilled, and taking into consideration the TAX_RECORD_EXPIRATION value, Taler deletes the customer information that is no longer needed, rather than relying on merchants marking fields as "forgettable".

If a merchant chooses to use Taler, they do so because they are responsible merchants regarding privacy, and want to do the right thing. We should help them with that, by introducing privacy-preserving best practices (like forgetting customer information whenever possible) by design.

Issue History

Date ModifiedUsernameFieldChange
2021-04-12 14:33sebasjmNew Issue
2021-04-12 14:33sebasjmStatusnew => assigned
2021-04-12 14:33sebasjmAssigned To => sebasjm
2021-08-24 18:32Christian GrothoffTarget Versiongit (master) => 0.8.5
2022-01-19 13:49sebasjmTag Attached: needs ui design
2022-01-19 13:49sebasjmTag Attached: needs ux design
2022-01-19 13:54sebasjmNote Added: 0018643
2022-01-19 13:54sebasjmFile Added: Selection_999(167).png
2022-01-19 13:54sebasjmFile Added: Selection_999(166).png
2022-01-19 15:52sebasjmNote Added: 0018644
2022-01-19 15:52sebasjmFile Added: Selection_999(165).png
2022-01-20 19:31sebasjmAssigned Tosebasjm => belen
2022-01-22 11:46belenNote Added: 0018650
2022-08-25 19:15Christian GrothoffSeveritymajor => feature
2022-08-25 19:16Christian GrothoffAssigned Tobelen => sebasjm
2022-08-25 19:16Christian GrothoffPrioritynormal => low
2022-10-20 08:45Christian GrothoffTarget Version0.8.5 => 0.9
2022-10-20 09:21Christian GrothoffTarget Version0.9 =>
2023-04-04 17:34Florian DoldTarget Version => post-1.0
2024-08-12 08:13Christian GrothoffTarget Versionpost-1.0 => post-2.0
2025-04-17 22:34Christian GrothoffTag Attached: privacy
2025-04-17 22:34Christian GrothoffAssigned Tosebasjm =>
2025-04-17 22:34Christian GrothoffStatusassigned => implementing
2026-01-25 14:10Christian GrothoffTag Detached: needs ui design
2026-01-25 14:10Christian GrothoffTag Detached: needs ux design
2026-08-23 14:18Florian DoldCategorymerchant backoffice SPA => merchant portal webui