Legal

Stop Honking Privacy Policy

Who we are

Stop Honking is an initiative of Public Relations Society of India, Kolkata Chapter (PRSI) in association with Indian Institute of Technology, Kharagpur. Data Controller contact: connect@stophonking.com

What we collect and why

Each form asks only for what its stated purpose requires, and we use it for nothing else. Required fields are marked; all others are optional.

The pledge. Your full name, age, gender, state, district, pin code, mobile number, e-mail address and consent to be counted. Your name and the date of your pledge appear on your certificate; the public total shows no names. Your age, gender, state, district and pin code are used only in totals, to show who is pledging and where; the public Pledge analytics page shows gender, age group, state and district, never a pin code. Your e-mail address carries your certificate; with your consent, it and your mobile number bring campaign news. Both are also used to allow one pledge per address and per number, and to let you get your certificate again, as set out below. The certificate is drawn in your browser; to e-mail it, the page passes the image through the site's server, which keeps no copy, to our e-mail provider, Google. For a name in English letters (accented ones too), the server may instead draw the certificate itself: when it is e-mailed again, or when your browser's image cannot be used. It uses only the name and date saved with your pledge, sends the image to Google the same way, and keeps no copy of it. Our sent mail may retain a copy of each message.

Taking the pledge only once. Each e-mail address and each mobile number can be used for one pledge only, even if family members share it. Small differences, such as capital letters in an address or +91 before a number, do not make a new one. A second pledge with either is refused before any of it is stored. It leaves no record, no row in the team's private Google Sheet, no e-mail and no change to the public total. Our forms keep nothing of it but the hourly count of requests from your connection, described below. If your address or number was used without your knowledge, write to us.

Getting your certificate again. The link "Already taken the pledge? Get your certificate again" asks for the e-mail address and mobile number you pledged with. They are compared with the index of pledges described below, and not stored. Only when both belong to one pledge are you shown its name and date, from which your browser draws the certificate. Otherwise the answer is the same as for no pledge at all. "Download my certificate", offered when a second pledge is refused, also shows the certificate only when both belong to one pledge; downloading sends nothing to our server. "E-mail it to me again", offered in both places, sends the certificate only to the e-mail address saved with your pledge, never to one typed later. For a name in English letters, a copy can be asked for with only one of the two; it still goes only to that saved address. At most three certificate e-mails a day go to one address, the first certificate included. None goes to an address on our list of people who have asked us not to e-mail them.

Contact. Your name, e-mail address, an optional phone number, a subject and your message, used only to reply to you.

Newsletter. With your consent, your e-mail address, used to send one e-mail a month about the campaign and related facts.

Children. Our forms are for persons aged eighteen or above. As Section 9 of the Act prescribes, a child's personal data is never processed without the verifiable consent of a parent or lawful guardian; any received without it is erased.

Every form. Each submission we keep is stored with its time and a short code derived from your IP address, which changes daily and is kept only on the site's server, to detect and prevent abuse. The same code is used to limit how many requests a connection can make in an hour, including searches for a certificate and requests to e-mail one again, and how many certificate e-mails it can ask for in a day. Certificate e-mails to each address are also counted each day, under a code derived from the address: a string of letters and digits that stands for it without showing it. Google, which sends our e-mails, keeps a similar count for up to six hours after the latest certificate e-mail to that address. The site's counts stay on its server; each is dropped by a later request once its hour or day has passed, and any left when the campaign ends are deleted with the records.

Visit statistics and cookies

The site uses Google Analytics, loaded through Google Tag Manager, to count visits and see how the site is used. It records the pages you open, with their address and title, and the page you came from; when you scroll to the end of a page; the links you follow to other sites; the files you download; and when you start or send a form, never what you type into it. Google also receives your browser's request, from which it works out your approximate location and the kind of device and browser you use.

Google Analytics sets two cookies on this site, _ga and _ga_76X8S06RQ4. They hold a random number, the times of your first and latest visits and how many visits you have made, so that a returning browser is recognised. Each page you open renews them, so they last up to two years after your latest visit unless you delete them. Google processes this data on our behalf under its data processing terms, on servers that may be outside India. It deletes the details of each visit after two months, and what links your visits to your browser 14 months after your latest visit. We look only at totals, not at individual visitors. Analytics is not linked to any advertising, and Google's optional sharing of the data is switched off. You can block or delete these cookies in your browser, or use Google's opt-out browser add-on; the site works fully without them.

What the site does not do

The site carries no advertising tags, and sets no cookies beyond the two above and those a form needs to work.

The typefaces of the site and the pledge certificate load from Google Fonts, and its photographs from Wikimedia Commons; the servers of both receive your browser's request, and Wikimedia's may set a cookie of its own. The developer may host them on this site instead. A map from OpenStreetMap loads only when you press Load the map; OpenStreetMap's servers then receive your browser's request. The share buttons open WhatsApp, X or Facebook in a new tab with the text you choose to share; what those services do with it is governed by their own policies, not this one.

Where it is stored, how it is protected and for how long

Public Relations Society of India, Kolkata Chapter (PRSI) holds your data, with a copy of each form record in a private Google Sheet that only the campaign team can open. Reasonable security safeguards protect it, as Section 8(5) of the Act prescribes: encryption in transit, access confined to authorised persons and logged, and regular back-ups. Our service providers act only on our instructions, under contracts binding them to the same safeguards.

Beside the pledge records, the site's server keeps an index of pledges, a list it uses to look pledges up. It allows one pledge per e-mail address and per mobile number, and finds a pledge when its certificate is asked for again. It files each pledge under a code derived from its e-mail address and one derived from its mobile number. The index lists no mobile number, only its code. For each pledge it keeps its reference number (made from the date and time it was taken), the name and date its certificate shows, and the e-mail address as you typed it. The site checks that address, and counts the e-mails sent to it, before a certificate is e-mailed again. The index is made from the pledge records on the site's server, so it includes pledges taken before the one-pledge rule began.

The server also keeps a log of certificate e-mails, so the team can see what happened to each and why one did not go. Each line records one event: the time, the step, its result, the pledge's reference number and a short note. It never holds a name, an e-mail address or a mobile number, though the reference number links a line to its pledge. While a certificate waits to be e-mailed, the server holds the e-mail address and name it is for, but not the certificate. All of these sit with the records, under the same safeguards.

Pledge records are kept for the life of the campaign; newsletter addresses until you unsubscribe. We then erase them, or earlier if you withdraw consent, subject to the one-year minimum retention the Rules prescribe. The index of pledges is made from the pledge records, and we delete it when we erase them; once we erase a pledge, it also leaves the index, so it no longer blocks its e-mail address and mobile number or answers a search. The certificate log is kept for one year. The address and name held for a certificate waiting to be e-mailed are deleted once it is sent; an unsent one stops working after an hour and is deleted the next time someone pledges, writes to us, signs up or asks for a certificate. Any left when the campaign ends are deleted with the records.

Who sees it

Individual records are seen in full only by the campaign team, and by our Data Processors only as their service requires: Hostinger, which hosts the site; Google, which holds the team's private Sheet; and Google, solely to deliver your certificate. The rest of the associated entities, the public dashboard and the Pledge analytics page see aggregate counts only; no name, phone number or e-mail address is ever published. Beyond the team and our Data Processors, a pledge's name and date are shown only to someone who enters both its e-mail address and its mobile number. Their browser may also receive its reference number, which shows when it was taken. The pledge form shows anyone who types in an e-mail address or mobile number whether it has already been used for a pledge, and which of the two. A request to e-mail a certificate again shows whether either has, without saying which. We never sell your data or share it for marketing.

Your rights

Under Sections 11 to 14 of the Act, you may obtain a summary of your personal data and of those with whom it has been shared; have it corrected, completed, updated or erased; and nominate a person to exercise these rights in the event of your death or incapacity. You may withdraw consent at any time, as easily as you gave it, through the unsubscribe link in our messages or by writing to us.

Write to connect@stophonking.com; we reply within two business days.

Changes

When this policy changes, we note the change here with its date. : this policy now covers visit statistics, Google Analytics loaded through Google Tag Manager, and their two cookies; it also says that the photographs load from Wikimedia Commons. : this policy now covers the rule of one pledge per e-mail address and per mobile number, getting your certificate again, and what these show to others. It also covers certificates drawn on the site's server, the index of pledges, the certificate log and the counts that limit requests. Last updated .