1<!DOCTYPE html> 2<html lang="en"> 3<head> 4<meta charset="UTF-8"> 5<meta name="viewport" content="width=device-width, initial-scale=1"> 6<title>Send a preservation letter â WhoGaveTheOrder.in</title> 7<meta name="description" content="Four written requests asking Bihar police offices to preserve control-room logs, wireless logs and CCTV from the protests of 21 to 27 July 2026. Fill in your details and the letter opens in your mail window, addressed and ready to read."> 8<link rel="icon" href="favicon.svg" type="image/svg+xml"> 9<link rel="stylesheet" href="assets/styles.css"> 10</head> 11<body data-page="letters"> 12<a class="skip-link" href="#main">Skip to content</a> 13<div data-chrome="masthead"></div> 14 15<main id="main"> 16 <section style="border-top:0"> 17 <div class="shell"> 18 <p class="crumb"><a href='/'>Home</a> / Send a preservation letter</p> 19 <div class="section-head" style="margin-top:1rem"> 20 <p class="kicker">Records are destroyed on a schedule, not on a decision</p> 21 <h2 style="font-size:clamp(1.75rem,6vw,2.75rem)">Send a preservation letter</h2> 22 <p class="lede"> 23 Four written requests, to four Bihar police offices, asking that control-room logs, 24 wireless logs, CCTV and any body-worn footage from 21 to 27 July 2026 be kept rather than 25 overwritten. Fill your details in once and each letter opens in your mail window, 26 addressed, with the text in it. You read it and press send. 27 </p> 28 </div> 29 </div> 30 </section> 31 32 <section> 33 <div class="shell"> 34 <div class="grid grid--2"> 35 <div> 36 <p class="kicker">What these are</p> 37 <div class="prose" style="margin-top:0.5rem"> 38 <p> 39 A preservation representation is <strong>not a statutory instrument</strong>. It 40 compels nothing, and it is not an RTI application, so no clock starts when you send 41 one. Its value is narrower and worth stating plainly: once an office has been told in 42 writing that identified records are the subject of an inquiry, the destruction of 43 those records after that date is itself a documentable fact, with a date on it. That 44 is the whole mechanism. 45 </p> 46 <p> 47 The reason to send one now is that the police action of this period is before the 48 Supreme Court, which constituted a five-member High Powered Enquiry Committee by an 49 order reported 18 August 2026. Records of this kind are liable to be material to that 50 inquiry, and a record lost to a routine retention cycle is not recoverable. 51 </p> 52 </div> 53 </div> 54 <div> 55 <p class="kicker">Before you send one</p> 56 <div class="prose" style="margin-top:0.5rem"> 57 <ul> 58 <li><strong>Check who currently holds the office.</strong> This archive does not hold 59 the officeholders' names and does not guess them. A letter to a misidentified 60 officer can be ignored for a good reason.</li> 61 <li><strong>Read it.</strong> The Munger letter deliberately does not assert that 62 police force was used at Munger, because the archive does not establish it 63 (<span class="mono">INC-BIH-003</span>, UNVERIFIED). Do not firm that up.</li> 64 <li><strong>Keep the proof.</strong> Ask for a delivery receipt and keep the sent 65 item. It is weaker than a speed post receipt, which is why post is still better 66 wherever an address is known. One of these four has an address.</li> 67 <li><strong>Nothing you type here leaves this browser.</strong> Your name and address 68 are kept in local storage so you do not retype them four times, and they go into 69 your own outgoing mail. There is no account here and no server of ours in the path.</li> 70 </ul> 71 </div> 72 </div> 73 </div> 74 </div> 75 </section> 76 77 <section> 78 <div class="shell shell--narrow"> 79 <p class="kicker">Your details</p> 80 <h3 style="margin:0.3rem 0 0.4rem">Fill these in once</h3> 81 <p class="small" style="margin-bottom:1.1rem">
82 The drafts leave these blank rather than invent them, and the send buttons stay off until 83 every one is filled. A letter that reaches a public office with 84 <span class="mono">[sender name]</span> still in it is worse than no letter. 85 </p> 86 <div data-region="letters-form"></div> 87 </div> 88 </section> 89 90 <section> 91 <div class="shell"> 92 <p class="kicker">The four letters</p> 93 <h3 style="margin:0.3rem 0 0.4rem">Siwan first, if you send only one</h3> 94 <p class="small" style="margin-bottom:1.25rem"> 95 Siwan is the best-evidenced of the Bihar incidents here 96 (<span class="mono">INC-SIW-001</span>, CORROBORATED, resting on the State of Bihar's own 97 affidavit to the Supreme Court), it involves the discharge of firearms and injuries, and it 98 had no representation queued until one was written for it. 99 </p> 100 <div class="stack" data-region="letters-list"></div> 101 </div> 102 </section> 103 104 <section> 105 <div class="shell"> 106 <div class="grid grid--2"> 107 <div> 108 <p class="kicker">Where these addresses come from</p> 109 <div class="prose" style="margin-top:0.5rem"> 110 <p> 111 The official Bihar Police website, <span class="mono">police.bihar.gov.in</span>, 112 retrieved 18 September 2026. The district officer directory is not a page you can 113 link to: it ships inside the site's own application bundle, whose filename is 114 content-hashed and changes on every rebuild, so the citation is the site and the date 115 rather than a URL. 116 </p> 117 <p> 118 <strong>Munger is independently cross-confirmed.</strong> 119 <span class="mono">munger.nic.in</span> gives the same email, the same office number 120 and the same mobile, and adds a postal address. Two official sources agreeing on one 121 district is the reason to trust the directory for the other three; it is not proof of 122 them. At the time of retrieval <span class="mono">patna.nic.in</span>, 123 <span class="mono">katihar.nic.in</span> and <span class="mono">siwan.nic.in</span> 124 were all returning HTTP 503, so none of those three could be cross-checked. 125 </p> 126 </div> 127 </div> 128 <div> 129 <p class="kicker">Sending by email at all</p> 130 <div class="prose" style="margin-top:0.5rem"> 131 <p> 132 Every one of these addresses is <span class="mono">@nic.in</span> or 133 <span class="mono">@gov.in</span>, so they are government mail systems, and those are 134 the systems most likely to check SPF. That would have been a problem before: the 135 domain's own SPF record was wrong. Checked 18 September 2026 it reads 136 <span class="mono">v=spf1 include:secureserver.net include:spf.protection.outlook.com -all</span>, 137 which authorises the servers the domain actually sends from. 138 </p> 139 <p> 140 You are sending from your own address, not ours, so that record governs our mail 141 rather than yours. If your mail is rejected, send from a different provider or post it. 142 </p> 143 </div> 144 </div> 145 </div> 146 147 <div class="callout" style="margin-top:1.75rem"> 148 <p><strong>A copy for central Patna.</strong> The two Patna incidents, JP Golambar and 149 Dakbungalow Square, are both in central Patna, so the City SP (Central), 150 <span class="mono">[email protected]</span>, 0612-2219423, is the officer closest to 151 the records. A copy there is reasonable. The SSP stays the addressee.</p> 152 <p><a class='btn btn--small btn--ghost' href='/rti'>The RTI register</a> 153 <a class='btn btn--small btn--ghost' href='/submit#missing'>What we are missing</a></p> 154 </div> 155 </div> 156 </section> 157</main> 158 159<div data-chrome="footer"></div> 160
161<script src="data/taxonomy.js"></script>
vendor: 1 bytes, line 161
161
162<script src="data/i18n.js"></script>
vendor: 1 bytes, line 162
162
163<script src="data/i18n.generated.js"></script>
vendor: 1 bytes, line 163
163
164<script src="data/records.js"></script>
vendor: 1 bytes, line 164
164
165<script src="data/records.generated.js"></script>
vendor: 1 bytes, line 165
165
166<script src="data/letters.generated.js"></script>
vendor: 1 bytes, line 166
166
167<script src="data/samples.js"></script>
vendor: 1 bytes, line 167
167
168<script src="assets/model.js"></script>
vendor: 1 bytes, line 168
168
169<script src="assets/ui.js"></script>
vendor: 1 bytes, line 169
169
170<script src="assets/pages.js"></script>
vendor: 1 bytes, line 170
170
171<script src="assets/letters.js"></script>
vendor: 1 bytes, line 171
171
172<script src="assets/dyslexia-font.js" data-accent="var(--accent)" data-radius="var(--radius)" defer></script>
172 173</body> 174</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.