56:
356:
114:
84:
196:
We suppress some highly sensitive and potentially harmful non-public information, even if it does not strictly help "identify" the person. We suppress content such as the self-disclosure of one's age or date of birth if the user is a minor. In the past, we've also suppressed content such as an
221:
An example of one instance where an edit was exceptionally suppressed was an edit made as part of a real-world stalking campaign, where the edit had no project value, and where no lesser remedy was sufficient. Suppression may also be used for copyright violations upon instruction of
Wikimedia
461:. If the oversighter you're trying to contact is not currently online or available, using one of the recommended methods listed above will ensure that an oversighter acts upon your request. A list of Knowledge users who currently have the oversight user permissions can be viewed by clicking
242:. These processes remove content from public view and leave it visible only to administrators; this is adequate for most cases, and it means that the content is unavailable to almost all Knowledge readers and users. An appeal of our decisions can only be requested by contacting the
264:(web browser address) of the page, edit, log, or log entry containing the content or information that you think we need to suppress. If the facts or information are not obvious, please also supply a brief description of what we need to suppress and why we need to suppress it.
188:
This includes a telephone number, an address or location, the name of a workplace or school, other online and offline identities, accidentally disclosed IP addresses, and (subject to oversighter judgment) other information of an identifying
401:, then you can ask for an oversighter, or for help finding an oversighter, in any of Knowledge's official channels on Libera Chat. Visit the IRC channel listed below, and send the following stalkword as a message:
347:
If you don't have a
Knowledge account with email enabled, or if you prefer to use some other method of emailing, then you can send a request for suppression by emailing the required information to:
161:
We suppress edits that breach somebody's privacy or defame somebody. We only suppress if they do this in such a way that the edit should not be visible even to
Knowledge administrators; otherwise,
293:). This removes the material from public view and stops it being perpetuated in future edits. Never use an edit or log summary like "awaiting suppression" when you do this; be discreet.
256:
Any user or reader may request the suppression of content at any time, but we will require the following information. Please ensure you provide it, or your request will be delayed:
172:
that specifies that we only allow edits or logs, once they are suppressed, to be viewed by a small, vetted, and identified team of highly-trusted users ("Oversighters"). Please see
457:
If you know an oversighter and can contact one directly, you may certainly do so. While oversight requests do not have to be submitted through any official route,
429:
can also suppress, but will not usually do so as
English Knowledge has its own team of oversighters. In a true emergency, there is almost always a steward on
213:
that we would delete if usual deletion tools could handle it. This includes grossly improper user names. (This is an interim policy and subject to change.)
226:
We will use our best judgement in applying these criteria to your request. If your request does not meet the threshold required for suppression, but
500:
445:
post a diff to the suppressible edit(s) in any public channel. Find an oversighter, and then tell them about the edit in a private chat window.
369:
symbol into your e-mail client if you copy and paste the email address from here; pasting the email that you copy from here may render
470:
Consider using one of the recommended contact methods in addition to this method to make sure the request is seen as soon as possible.
133:
Read on for information on when to request suppression, how to request it, and what information the oversighter will need from you.
476:
459:
never post an oversight request, or any pertinent information regarding an oversight request, to the oversighter's user talk page
235:
463:
495:
243:
179:
We usually suppress an edit or other information on
Knowledge if it contains the following types of information:
475:
Note: The suppression team does not respond to threats of harm. Such emergencies are dealt with as described at
387:
with urgent situations, as these contact methods aren't guaranteed to be monitored reliably or nearly as often:
234:
instead, we will apply redaction using revision deletion. If your request is denied, you can instead request
17:
439:
If an oversighter is around, using IRC can be a very quick method of requesting suppression. However, you
419:
323:
95:
66:
197:
individual's medical information. This is subject to oversighter discretion, and can vary case-by-case.
379:
This is also one of the fastest ways to request suppression. Please use a descriptive subject line.
249:
143:
on
Knowledge or any public venue. Requests are only accepted by email or other private methods.
335:
This is one of the fastest ways to request suppression. Please use a descriptive subject line.
125:
contacting an oversighter personally and directly (using IRC or some other method of contact).
92:
Suppression removes edits which breach privacy or defame somebody. You may request it by:
8:
329:
176:
for more information on the oversight/suppression policy, application, and team members.
173:
99:
42:
34:
297:
169:
154:
426:
276:(s) of the content requiring suppression. This saves us a significant amount of time.
207:, regardless of their validity, when we have no editorial need to keep the revision.
290:
283:
279:
239:
231:
162:
98:, if you have a Knowledge account with email enabled, to send an internal message (
273:
141:
draw attention to suppressible material, or any links to suppressible material
489:
204:
219:
We are not likely to make other exceptions, but reserve the right to do so.
310:
that are actively monitored for new oversight requests at most times:
407:. This will alert all active oversighters that you have a request:
321:
If you have a
Knowledge account with email enabled, then use
304:
Choose one or more of the following contact methods below:
433:
on Libera Chat, and they are extremely helpful and alert.
261:
343:– recommended if you don't have a Knowledge user account
184:
Non-public personal information about a real individual.
186:
This could be private information about you or others.
193:
Clearly private, personal, or non-public information.
487:
286:the relevant revision(s) first (please do this
230:unambiguously meet the threshold for applying
341:Using your own email to send a message to us
63:The fastest way to request oversight is to
201:Clearly (or likely to be) libelous content
477:Knowledge:Responding to threats of harm
268:If you know how to do so, please also:
203:made either toward another editor or a
14:
501:Knowledge requests related to disputes
488:
100:click here to enable internal messages
317:– recommended if you have an account
78:
50:
418:on Libera Chat, for sending urgent
291:if it will not draw undue attention
24:
330:click here to enable account email
25:
512:
354:
112:
82:
54:
55:
28:
13:
1:
327:to directly post a request. (
365:. (You may have to type the
315:Using Knowledge's quick form
250:What information do we need?
7:
422:requests to administrators.
308:Recommended contact methods
10:
517:
452:By direct personal contact
163:Revision Deletion (RevDel)
32:
355:
113:
496:Knowledge administration
90:This page in a nutshell:
67:email the oversight team
168:Knowledge has a strict
298:How do you contact us?
155:When will we suppress?
105:composing an email to
244:Arbitration Committee
415:#wikipedia-en-revdel
431:#wikimedia-stewards
222:Foundation counsel.
174:Knowledge:Oversight
484:
483:
420:revision deletion
240:revision deletion
232:revision deletion
131:
130:
77:
76:
16:(Redirected from
508:
434:
432:
416:
405:
400:
376:
372:
368:
362:
361:
359:
358:
357:
142:
122:
120:
119:
117:
116:
115:
86:
85:
79:
71:
58:
57:
51:
45:
29:
21:
516:
515:
511:
510:
509:
507:
506:
505:
486:
485:
480:
473:
472:
454:
448:
447:
430:
425:
414:
403:
398:
394:
388:
385:not recommended
383:Available, but
381:
380:
374:
370:
366:
353:
352:oversight-en-wp
351:
350:
344:
337:
336:
318:
311:
300:
252:
236:speedy deletion
211:Gross vandalism
157:
137:
111:
110:oversight-en-wp
109:
108:
106:
96:using this form
83:
73:
64:
49:
48:
41:
37:
23:
22:
15:
12:
11:
5:
514:
504:
503:
498:
482:
481:
474:
455:
450:
449:
438:
437:
436:
435:
423:
395:
390:
389:
382:
345:
339:
338:
319:
313:
312:
306:
299:
296:
295:
294:
280:RevisionDelete
277:
266:
265:
251:
248:
224:
223:
220:
217:Other reasons:
214:
208:
198:
195:
190:
187:
170:privacy policy
156:
153:
150:
149:
146:
145:
129:
128:
127:
126:
123:
103:
87:
75:
74:
61:
59:
47:
46:
38:
33:
9:
6:
4:
3:
2:
513:
502:
499:
497:
494:
493:
491:
478:
471:
468:
466:
465:
460:
453:
446:
444:
428:
424:
421:
417:
412:
411:
410:
409:
408:
406:
393:
386:
378:
364:
363:
360:wikipedia.org
342:
334:
332:
331:
326:
325:
316:
309:
305:
302:
292:
289:
285:
281:
278:
275:
271:
270:
269:
263:
259:
258:
257:
254:
247:
245:
241:
237:
233:
229:
218:
215:
212:
209:
206:
202:
199:
194:
191:
185:
182:
181:
180:
177:
175:
171:
166:
165:may be used.
164:
159:
152:
151:
148:
147:
144:
140:
134:
124:
121:
118:wikipedia.org
104:
101:
97:
94:
93:
91:
88:
81:
80:
72:
69:
68:
60:
53:
52:
44:
40:
39:
36:
31:
30:
27:
19:
18:Knowledge:RFO
469:
462:
458:
456:
451:
442:
440:
413:
402:
396:
391:
384:
349:
348:
346:
340:
328:
322:
320:
314:
307:
303:
301:
287:
267:
255:
253:
227:
225:
216:
210:
200:
192:
183:
178:
167:
160:
158:
138:
135:
132:
107:
89:
65:
62:
26:
397:If you use
490:Categories
404:!oversight
392:Using IRC
324:this form
260:The full
136:You must
427:Stewards
272:Send us
35:Shortcut
189:nature.
284:revert
43:WP:RFO
441:must
139:never
464:here
399:IRC
375:-at-
288:only
274:diff
228:does
443:not
377:.)
373:as
282:or
262:URL
238:or
205:BLP
492::
467:.
333:)
246:.
102:).
479:.
371:@
367:@
70:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.