View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010785 | Taler | deployment and operations | public | 2025-12-16 14:39 | 2025-12-16 17:24 |
| Reporter | vecirex | Assigned To | Stefan | ||
| Priority | none | Severity | feature | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0010785: Privacy Statement (link) missing | ||||
| Description | Even though the taler-merchant-httpd service warns for not having a privacy statement defined (as in: a folder location for files per language following a certain structure for naming and formats), @sebasjm could confirm we don't even have a link at the site. Two things here: (1) Define location where to put the Privacy Statement link(s); can also be global IMHO, at a footer location, e.g., as it's quite usual. (2) Ship / Rephrase the texts to be used, at least in EN; if possible, also in DE. Some kind of Privacy Statements already exist, but perhaps not tailored to the self-provisioning system. | ||||
| Additional Information | Manpage docu on how the settings are supposed to be done, taler-merchant-wise; with support for I18N and also versioning: https://docs.taler.net/manpages/taler-merchant.conf.5.html | ||||
| Tags | No tags attached. | ||||
|
|
The TOPS Privacy Policy is in the exchange.git (exchange/contrib/exchange-pp-v0.de.rst and exchange/contrib/exchange-pp-v0.en.rst ) - Let's take the German version which makes most sense in the presentation in front of German speaking customers. https://git-www.taler.net/exchange.git/tree/contrib/exchange-tos-tops-v0.de.rst https://git-www.taler.net/exchange.git/tree/contrib/exchange-tos-tops-v0.en.rst |
|
|
Are they applicable to the taler-merchant self-provisioning system without any change? |
|
|
In additional info field, add docu which florian linked; ty! |
|
|
Another point would be the documented support for versioning, see additions to this ticket: is this reflected in the text? We can of course just go for "v0" for now, but then it would be good to just put this into the text already at the top inline; I suggest also: with a date; as "v0" alone is not very helpful. |
|
|
These are Privacy policies, Datenschutzbestimmungen. The software and our server-sided processes are obliged to live up to these rules that we applied respectively that are supposed to have been made applicable to our services by Swiss law. But the PP has nothing do to with fee structures, costs, limits and so on, just with data and data management/forwarding. So we are safely managing the privacy of merchant users with these PP for TOPS and it can be assumed that the Merchant Backend complies with these rules (as long as the DB is not set public or synchronized with an untrusted cloud provider in countries outside the EU and different from EFTA states). |
|
|
Versioning: The version number is mostly for our file sanity, but also from a legal point of view. User-sided, the date plays the major role here. Customers (here: merchant users of the Taler Merchant Backoffice) are not interested in the version number, but to get notified about new applicable updates of the TOPS Privacy Policy and the version of the Backend itself. |
|
|
I would still say, it makes sense (as others do), to just put version number and date into the document itself. Already for transparency reasons this makes sense. |
|
|
The date is already there in the second line. I do believe, to display a month suffices (as month == starting day 1) |
|
|
OK, as CG wants to have it, just changing blocking direction: first live, then solve this, making thus this ticket depending on 0010630. :) (As long as we act quick enough, it's fine.) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-16 14:39 | vecirex | New Issue | |
| 2025-12-16 14:39 | vecirex | Status | new => assigned |
| 2025-12-16 14:39 | vecirex | Assigned To | => Stefan |
| 2025-12-16 14:40 | vecirex | Relationship added | child of 0010630 |
| 2025-12-16 14:47 | Stefan | Note Added: 0027014 | |
| 2025-12-16 14:50 | vecirex | Note Added: 0027015 | |
| 2025-12-16 14:51 | vecirex | Additional Information Updated | |
| 2025-12-16 14:51 | vecirex | Note Added: 0027016 | |
| 2025-12-16 14:52 | Christian Grothoff | Priority | urgent => none |
| 2025-12-16 14:52 | Christian Grothoff | Severity | major => feature |
| 2025-12-16 14:52 | Christian Grothoff | Status | assigned => acknowledged |
| 2025-12-16 14:52 | Christian Grothoff | Target Version | => post-1.0 |
| 2025-12-16 14:53 | vecirex | Note Added: 0027017 | |
| 2025-12-16 14:55 | Stefan | Note Added: 0027018 | |
| 2025-12-16 14:58 | vecirex | Additional Information Updated | |
| 2025-12-16 14:59 | Stefan | Note Added: 0027019 | |
| 2025-12-16 15:01 | Stefan | Note Edited: 0027018 | |
| 2025-12-16 15:11 | vecirex | Note Added: 0027023 | |
| 2025-12-16 15:13 | Stefan | Note Added: 0027025 | |
| 2025-12-16 17:17 | vecirex | Note Added: 0027032 | |
| 2025-12-16 17:17 | vecirex | Relationship replaced | parent of 0010630 |
| 2025-12-16 17:24 | vecirex | Relationship added | related to 0010771 |
