View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006843 | Taler | merchant backoffice SPA | public | 2021-04-12 16:33 | 2024-08-12 10:13 |
Reporter | sebasjm | Assigned To | sebasjm | ||
Priority | low | Severity | feature | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | git (master) | ||||
Target Version | post-2.0 | ||||
Summary | 0006843: every input type can be forgetable, handle UI to add checkbox | ||||
Description | this apply to the order https://docs.taler.net/core/api-merchant.html#private-order-data-cleanup | ||||
Tags | needs ui design, needs ux design | ||||
|
Adding example of the current new order form |
|
|
|
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. |
Date Modified | Username | Field | Change |
---|---|---|---|
2021-04-12 16:33 | sebasjm | New Issue | |
2021-04-12 16:33 | sebasjm | Status | new => assigned |
2021-04-12 16:33 | sebasjm | Assigned To | => sebasjm |
2021-08-24 20:32 | Christian Grothoff | Target Version | git (master) => 0.8.5 |
2022-01-19 14:49 | sebasjm | Tag Attached: needs ui design | |
2022-01-19 14:49 | sebasjm | Tag Attached: needs ux design | |
2022-01-19 14:54 | sebasjm | Note Added: 0018643 | |
2022-01-19 14:54 | sebasjm | File Added: Selection_999(167).png | |
2022-01-19 14:54 | sebasjm | File Added: Selection_999(166).png | |
2022-01-19 16:52 | sebasjm | Note Added: 0018644 | |
2022-01-19 16:52 | sebasjm | File Added: Selection_999(165).png | |
2022-01-20 20:31 | sebasjm | Assigned To | sebasjm => belen |
2022-01-22 12:46 | belen | Note Added: 0018650 | |
2022-08-25 21:15 | Christian Grothoff | Severity | major => feature |
2022-08-25 21:16 | Christian Grothoff | Assigned To | belen => sebasjm |
2022-08-25 21:16 | Christian Grothoff | Priority | normal => low |
2022-10-20 10:45 | Christian Grothoff | Target Version | 0.8.5 => 0.9 |
2022-10-20 11:21 | Christian Grothoff | Target Version | 0.9 => |
2023-04-04 19:34 | Florian Dold | Target Version | => post-1.0 |
2024-08-12 10:13 | Christian Grothoff | Target Version | post-1.0 => post-2.0 |