This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
cbdc:public:cbdc_omg:04_doc:15_common:50_international:30_sovern [2022/04/09 20:08] nick created |
cbdc:public:cbdc_omg:04_doc:15_common:50_international:30_sovern [2022/06/17 18:17] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 4.6.3 Data Sovereignty ====== | ====== 4.6.3 Data Sovereignty ====== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | Return to Top]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start| International Considerations]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | 4.6.3 Data Sovereignty | ||
| + | |||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:data_sovereignty | Data Sovereignty ]] is concerned with any jurisdictions' laws and regulations covering any data collection or processing done within that jurisdiction, governing the data. **Data Sovereignty** differs from **Data Residency** in that Data Residency reflects a business decision on where to store and process data, often based on **Data Sovereignty** Laws and Regulations applicable to a particular jurisdiction. | [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:data_sovereignty | Data Sovereignty ]] is concerned with any jurisdictions' laws and regulations covering any data collection or processing done within that jurisdiction, governing the data. **Data Sovereignty** differs from **Data Residency** in that Data Residency reflects a business decision on where to store and process data, often based on **Data Sovereignty** Laws and Regulations applicable to a particular jurisdiction. | ||
| - | Much of the current interest in **Data Sovereignty** by jurisdictions (i.e., Countries) around the world are traceable to the revelations made public of U.S. activities of surveillance and collecting data globally on people (i.e., internally and externally to the U.S.) (( | + | Much of the current interest in **Data Sovereignty** by jurisdictions (i.e., Countries) around the world is traceable to the revelations made public of U.S. activities of surveillance and collecting data globally on people (i.e., internally and externally to the U.S.) (( |
| - | Ewen Macskill and Gabriel Dance, | + | Ewen MacAskill and Gabriel Dance, |
| The Guardian, | The Guardian, | ||
| __NSA Files: Decided - What the revelations mean for you__, | __NSA Files: Decided - What the revelations mean for you__, | ||
| Line 11: | Line 19: | ||
| Accessed: 9 April 2022, | Accessed: 9 April 2022, | ||
| [[https://www.theguardian.com/world/interactive/2013/nov/01/snowden-nsa-files-surveillance-revelations-decoded#section/1]] | [[https://www.theguardian.com/world/interactive/2013/nov/01/snowden-nsa-files-surveillance-revelations-decoded#section/1]] | ||
| - | )). The simplest way to look at **Data Sovereignty** is to consider national [[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start | Privacy Considerations]] and preventing data stored in a foreign country from subpoenas by the host country’s government. | + | )). The simplest way to look at **Data Sovereignty** is to consider national [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy:start| Privacy Considerations]] and preventing data stored in a foreign country from subpoenas by the host country’s government. |
| A globally accepted U.S. CBDC needs to take the Data Sovereignty issues seriously if there is any hope of //"Preserving the dominant international role of the U.S. dollar (**''B0036''**)// | A globally accepted U.S. CBDC needs to take the Data Sovereignty issues seriously if there is any hope of //"Preserving the dominant international role of the U.S. dollar (**''B0036''**)// | ||
| - | A theoretical example of how much complicated a globally accepted U.S. CBDC would be: | + | A theoretical example of how complicated a globally accepted U.S. CBDC would be: |
| * Assume U.S. CBDC transactions that occur in the E.U. are stored and processed in the U.K. | * Assume U.S. CBDC transactions that occur in the E.U. are stored and processed in the U.K. | ||
| - | * A U.S. CBDC transactions occurs in Italy and would be subject to the **Data Sovereignty** laws and regulations of Italy and the EU | + | * A U.S. CBDC transaction occurs in Italy and would be subject to the **Data Sovereignty** laws and regulations of Italy and the EU. |
| * However, since the data is stored and processed in the U.K., the data would be subject to the data sovereignty rights of the U.K. as Italy and the E.U. | * However, since the data is stored and processed in the U.K., the data would be subject to the data sovereignty rights of the U.K. as Italy and the E.U. | ||
| * To further complicate matters, U.S. CBDC transactions made and stored in the U.K. are backed up on servers in Ireland, making the CBDC transaction also subject to the data **Sovereignty Rights** of Ireland too. | * To further complicate matters, U.S. CBDC transactions made and stored in the U.K. are backed up on servers in Ireland, making the CBDC transaction also subject to the data **Sovereignty Rights** of Ireland too. | ||
| - | A real world example is of **Data Sovereignty** issues in the //__Microsoft’s Data Privacy Case vs. the DoJ__// case(( | + | A real-world example of **Data Sovereignty** issues is //__Microsoft’s Data Privacy Case vs. the DoJ__//(( |
| Benjamin Vitaris, | Benjamin Vitaris, | ||
| Permission.io, | Permission.io, | ||
| Line 35: | Line 43: | ||
| : //After the DoJ ordered the tech company to grant access to emails stored in Ireland-based servers related to a narcotics investigation in 2013, Microsoft had refused to comply with the Department of Justice’s request.// | : //After the DoJ ordered the tech company to grant access to emails stored in Ireland-based servers related to a narcotics investigation in 2013, Microsoft had refused to comply with the Department of Justice’s request.// | ||
| - | : //Despite that Microsoft stated that complying with the request would break the data privacy laws of the European Union, the initial ruling ordered the company to fulfill the DoJ’s request.// | + | : //Despite that Microsoft stating that complying with the request would break the data privacy laws of the European Union, the initial ruling ordered the company to fulfill the DoJ’s request.// |
| : //However, later on, after Microsoft won the appeal and the DoJ changed its data-related policies.// | : //However, later on, after Microsoft won the appeal and the DoJ changed its data-related policies.// | ||
| - | The adoption of U.S. CBDC, could break traditional geopolitical barriers more than ever before, especially depending on the [[cbdc:private:cbdc_omg:04_doc:15_common:08_currency_models:start | Currency Model]] selected. Depending on the perception of privacy protection of the CBDC, many countries may amend existing laws and regulations or greatly restring the use of a U.S. CBDC. | + | The adoption of U.S. CBDC could break traditional geopolitical barriers more than ever before, especially depending on the [[cbdc:public:cbdc_omg:04_doc:15_common:08_currency_models:start| Currency Model]] selected. Depending on the perception of privacy protection of the CBDC, many countries may amend existing laws and regulations or greatly restrict the use of a U.S. CBDC. |
| The U.S. CBDC needs to be completely honest and open about where data: | The U.S. CBDC needs to be completely honest and open about where data: | ||