You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Privacy and Surveillance | Data collection, use, storage, and retention, informed consent, transparency |
33
-
| Cybersecurity | Data breaches, security mechanisms, verification and authentication processes |
34
-
| Censorship | Content prohibitions and restrictions, reporting mechanisms |
35
-
| Access and Accessibility: | Access to services, discrimination/exclusion risks |
36
-
| Mis/Disinformation | Definitions of false/harmful content, content sharing, verification and reporting mechanisms |
37
-
| Hate Speech | Definitions of violent content, content sharing, reporting mechanisms |
38
-
| Algorithmic Accountability | Data use in AI training |
39
-
| Data Sovereignty | Data governance, cross-border data flows |
40
-
| Copyright | Fair use and licensing rules, verification and reporting mechanisms, monetisation |
41
-
42
-
- Include topics in the frontmatter metadata of the draft.
28
+
Each element is explained in detail below.
43
29
44
30
## Title
45
31
46
32
- Write a short declarative sentence to highlight the key change.
47
33
- 140 characters maximum.
48
34
- Use the name of the service as the subject.
49
35
- Write in the present tense.
50
-
- Prefer active phrasings over passive (e.g. ‘Microsoft expands reach’ rather than ‘Reach expanded by Microsoft’).
36
+
- Prefer active phrasings over passive (e.g. “Microsoft expands reach” rather than “Reach expanded by Microsoft”).
51
37
- Describe the policy change, not the name of the document. This information will be given in the metadata below.
52
38
- Use no punctuation.
53
39
- Use international title casings (i.e. only the first letter of the leading word should be in capital).
@@ -61,7 +47,7 @@ Identify topics from the following list:
61
47
62
48
## Service name
63
49
64
-
- Write the service name and not the company name, e.g., ‘Facebook’ rather than ‘Meta’.
50
+
- Write the service name and not the company name, e.g., “Facebook” rather than “Meta”.
65
51
66
52
**Examples**
67
53
@@ -83,8 +69,8 @@ Identify topics from the following list:
83
69
## Date modified
84
70
85
71
- Use `Month Day, Year` format.
72
+
- Avoid repeating months or years.
86
73
- Multiples dates are allowed.
87
-
- Avoid repeating months or years
88
74
89
75
**Examples**
90
76
@@ -95,20 +81,20 @@ Identify topics from the following list:
95
81
## Body text
96
82
97
83
- Describe changes in a neutral, objective, non-judgmental manner.
98
-
- Write in the past tense (e.g. ‘added’, ‘removed’…).
84
+
- Write in the past tense (e.g. “added”, “removed”…).
99
85
- Bolden the most important point.
100
86
- Do not repeat the date, it is already in the metadata.
101
87
- Systematically add a link to the diff on this action verb.
102
-
- Title of the link: ‘See the change’.
103
-
- Avoid verbs like ‘announce’, because most of the time the changes detected are not announced.
88
+
- Title of the link: “See the change”.
89
+
- Avoid verbs like “announce”, because most of the time the changes detected are not announced.
104
90
- Do not hesitate to quote the new text.
105
91
- Do not italicise citations, use quotes.
106
92
- Minimise the length of citations because legal text is often very wordy.
107
93
- Only quote the text before modification if it is strictly necessary to understand the change, to reduce the risk of confusion and length.
108
94
-__If changes have been made in a specific jurisdiction, mention it in the memo. Do not mention jurisdiction when changes have been made globally.__
109
95
- If you write in a different language than the detected change, always look for citations in the version of the document that matches the language of writing if it exists instead of translating them yourself.
@@ -119,16 +105,47 @@ Identify topics from the following list:
119
105
> OpenAI [specified](https://github.com/OpenTermsArchive/GenAI-versions/commit/30f1df7d18676c57a0ae1c43c3ccdfc264535cb3) that, as far as European (EEA and Swiss) developers were concerned, their Agreement is with OpenAI Ireland Ltd. OpenAI stopped acting as a separate controller of personal data, and developers now have to present a privacy notice to their users prior to processing their data.
120
106
>
121
107
> OpenAI also extended export restrictions to plugins ‘located’ in countries embargoed or sanctioned by the US. This provision previously concerned only plugin owners.
108
+
109
+
## Topic (optional)
110
+
111
+
- You can fill a topic by identifying it from the following list:
| Privacy and Surveillance | Data collection, use, storage, and retention, informed consent, transparency |
116
+
| Cybersecurity | Data breaches, security mechanisms, verification and authentication processes |
117
+
| Censorship | Content prohibitions and restrictions, reporting mechanisms |
118
+
| Access and Accessibility: | Access to services, discrimination/exclusion risks |
119
+
| Mis/Disinformation | Definitions of false/harmful content, content sharing, verification and reporting mechanisms |
120
+
| Hate Speech | Definitions of violent content, content sharing, reporting mechanisms |
121
+
| Algorithmic Accountability | Data use in AI training |
122
+
| Data Sovereignty | Data governance, cross-border data flows |
123
+
| Copyright | Fair use and licensing rules, verification and reporting mechanisms, monetisation |
124
+
125
+
Please note that if the diff has changes related to more than one topic, write separate memos for each topic.
126
+
127
+
## Contextualisation (optional)
128
+
129
+
Explain which wider problems are tackled by this policy change, or give a historical perspective on the change.
130
+
131
+
- Write the contextualisation text in a new paragraph.
132
+
- Add external links to the most authoritative sources available.
133
+
134
+
**Example**
135
+
136
+
> [...]
122
137
>
123
-
> OpenAI Ireland Ltd is a Dublin-based subsidiary of OpenAI [set up](https://openai.com/blog/introducing-openai-dublin) in 2023.
138
+
> This opens up the question of moderation of private discussions, as social platforms show difficulties in managing content related to child abuse —as recently as late March, the New York Times [showed](https://www.nytimes.com/2022/03/31/business/meta-child-sexual-abuse.html) that moderation remains very light in this area, even though platforms are supposed to list this type of content and [report it](https://www.theverge.com/2022/3/31/23005576/facebook-content-moderators-child-sexual-abuse-material-csam-policy) to authorities.
139
+
140
+
Source: [June 23, 2022 Memo on French Elections](https://sh1.sendinblue.com/aijgxqzlolpfe.html).
124
141
125
142
## Complete examples
126
143
127
144
### Memo 1
128
145
129
146
> **Midjourney strengthens policies on intellectual property infringements**
130
147
>
131
-
> *Midjourney ▪ Terms of Service ▪ December 23, 2023*
148
+
> *Midjourney ▪ Terms of Service ▪ December 23, 2023 ▪ Copyright*
132
149
>
133
150
> Midjourney introduced an explicit [prohibition](https://github.com/OpenTermsArchive/GenAI-versions/commit/2cb30a2b4b338a4dffbeab9add8262cec78a3062) regarding the infringement of others’ intellectual property rights in its conditions for service availability and quality, mentioning the possibility of legal action and permanent ban from the service.
134
151
>
@@ -138,24 +155,6 @@ Identify topics from the following list:
138
155
139
156
> **Instagram adds a posting ban to protect copyright**
140
157
>
141
-
> *Instagram ▪ Community Guidelines ▪ March 28, 2022*
158
+
> *Instagram ▪ Community Guidelines ▪ March 28, 2022 ▪ Copyright*
142
159
>
143
160
> On March 28, Instagram [updated](https://github.com/OpenTermsArchive/france-elections-versions/commit/1be4b836e3012344558b60d8f9f871bc42cfa4ca?short_path=c108c01#diff-c108c013f0b8769389f20259465cb81324e805f4334bcda6931344e16f999441) its intellectual property community rules, prohibiting the posting of content that ‘facilitates copyright infringement through unauthorized devices or services.’ The text presents a list of cases in which users would risk infringing the copyright of a third party or even merely ‘facilitating’ such infringement, even if they did not intend to do so. After the previously listed cases, which include ‘you purchased or downloaded the content’ or ‘you saw others post the same content,’ Instagram adds that users risk infringing copyright if they ‘use an unauthorized streaming device or service (examples: a “jailbroken” or “loaded” app or service).’
144
-
145
-
## Contextualisation (optional)
146
-
147
-
- Body text in a new paragraph: contextualisation with external links to the most authoritative sources available.
148
-
- For example, explain which wider problems are tackled by this policy change, or give a historical perspective on the change.
149
-
- For clarity, separate body text and contextual elements instead of grouping all changes in a single paragraph and then a lengthy context paragraph with multiple threads.
150
-
151
-
**Example**
152
-
153
-
> **Meta expands reach against child exploitation**
154
-
>
155
-
> *Facebook ▪ Community Guidelines ▪ June 13, 2022*
156
-
>
157
-
> The section on child exploitation for both Facebook and Instagram [expanded](https://github.com/OpenTermsArchive/france-elections-versions/commit/0396436542fa7ef8dd8ae4dd02ff0ed5500e08a2) to cover not only publications that exploit minors, but also ‘any activity’ related to such acts.
158
-
>
159
-
> This opens up the question of moderation of private discussions, as social platforms show difficulties in managing content related to child abuse —as recently as late March, the New York Times [showed](https://www.nytimes.com/2022/03/31/business/meta-child-sexual-abuse.html) that moderation remains very light in this area, even though platforms are supposed to list this type of content and [report it](https://www.theverge.com/2022/3/31/23005576/facebook-content-moderators-child-sexual-abuse-material-csam-policy) to authorities.
160
-
161
-
Source: [June 23, 2022 Memo on French Elections](https://sh1.sendinblue.com/aijgxqzlolpfe.html).
0 commit comments