CINXE.COM

<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0"> <title>Have I Been Pwned: Privacy policy</title> <meta property="og:title" content="Have I Been Pwned: Privacy policy" /> <meta name="description" content="Have I Been Pwned allows you to search across multiple data breaches to see if your email address or phone number has been compromised."> <meta property="og:description" content="Have I Been Pwned allows you to search across multiple data breaches to see if your email address or phone number has been compromised." /> <meta property="og:url" content="https://haveibeenpwned.com/Privacy" /> <meta property="og:image" content="https://haveibeenpwned.com/Content/Images/SocialLogo.png" /> <meta property="fb:app_id" content="553845121487108" /> <link href="//cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous" /> <link rel="alternate" type="application/rss+xml" title="Have I Been Pwned latest breaches" href="https://feeds.feedburner.com/HaveIBeenPwnedLatestBreaches" /> <link href="/content/css/pwned?v=l-PSrblX7vf9eicCwy8GIKZZEgr2tgWv8vdHZNKZii81" rel="stylesheet"/> <link href="//cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" rel="stylesheet" integrity="sha384-wvfXpqpZZVQGK6TAh5PVlGOfQNHSoD2xbE+QkPxCAFlNEevoEH3Sl0sibVcOQVnN" crossorigin="anonymous" /> <link rel="shortcut icon" href="/favicon.ico"> <script type="text/javascript" nonce="DQs8HLILkZf6LhgS4xG1"> var appInsights=window.appInsights||function(config) { function r(config){ t[config] = function(){ var i = arguments; t.queue.push(function(){ t[config].apply(t, i)})} } var t = { config:config},u=document,e=window,o='script',s=u.createElement(o),i,f;for(s.src=config.url||'//az416426.vo.msecnd.net/scripts/a/ai.0.js',u.getElementsByTagName(o)[0].parentNode.appendChild(s),t.cookie=u.cookie,t.queue=[],i=['Event','Exception','Metric','PageView','Trace','Ajax'];i.length;)r('track'+i.pop());return r('setAuthenticatedUserContext'),r('clearAuthenticatedUserContext'),config.disableExceptionTracking||(i='onerror',r('_'+i),f=e[i],e[i]=function(config, r, u, e, o) { var s = f && f(config, r, u, e, o); return s !== !0 && t['_' + i](config, r, u, e, o),s}),t }({ instrumentationKey:'9744aaee-21f7-42b6-95b2-8ebc0f2bcfeb' }); window.appInsights=appInsights; appInsights.trackPageView(); </script> </head> <body > <div class="bodyGradient"> <header class="navbar navbar-inverse navbar-static-top"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a href="/" class="navbar-brand">';--</a> </div> <div class="navbar-collapse collapse"> <ul class="nav navbar-nav navbar-right"> <li ><a href="/">Home</a></li> <li ><a href="/NotifyMe" class="notifyOfPwning" data-toggle="modal" data-target="#notifyMeModal" data-remote="false">Notify me</a></li> <li ><a href="/DomainSearch">Domain search</a></li> <li ><a href="/PwnedWebsites">Who's been pwned</a></li> <li ><a href="/Passwords">Passwords</a></li> <li class="dropdown "> <a href="#" class="dropdown-toggle" data-toggle="dropdown">API</a> <ul class="dropdown-menu"> <li ><a href="/API/v3">Overview</a></li> <li ><a href="/API/Key">API key</a></li> </ul> </li> <li class="dropdown "> <a href="#" class="dropdown-toggle" data-toggle="dropdown">About</a> <ul class="dropdown-menu"> <li ><a href="/About">Who, what & why</a></li> <li class="active" ><a href="/Privacy">Privacy</a></li> <li ><a href="/FAQs">FAQs</a></li> <li ><a href="/Pastes">Pastes</a></li> <li ><a href="/OptOut">Opt-out</a></li> <li><a href="https://twitter.com/haveibeenpwned" rel="noopener">Twitter</a></li> <li><a href="https://www.facebook.com/haveibeenpwned/">Facebook</a></li> <li><a rel="me" href="https://infosec.exchange/@haveibeenpwned">Mastodon</a></li> <li><a href="https://haveibeenpwned.uservoice.com/" rel="noopener">Suggest a feature</a></li> <li><a href="http://feeds.feedburner.com/HaveIBeenPwnedLatestBreaches" rel="noopener"><i class="fa fa-rss"></i> Breaches</a></li> </ul> </li> <li ><a href="/Donate">Donate <i class="fa fa-bitcoin"></i> <i class="fa fa-paypal payPalLogo"></i></a></li> </ul> </div> </div> </header> <div class="secondaryHeader"> <div class="container"> <h1>Privacy policy</h1> <h2> How we protect your personal information </h2> </div> </div> </div> <div class="container"> <h3>About us and what we do</h3> <p>HaveIBeenPwned.com (<strong>HIBP</strong>) is owned and operated by Superlative Enterprises Pty Ltd ABN 62 085 442 020 (<strong>"Superlative"</strong>, <strong>"we"</strong> or <strong>"us"</strong>), a small business based in the state of Queensland, Australia. We have created this policy to explain what limited personal information we collect when you use the HIBP site and how we handle and protect your personal information.</p> <p>HIBP's purpose is to help individuals and organisations combat violations of privacy by enabling them to identify when information has been involved in a data leak. HIBP helps create visibility as to how personal data spreads. Individuals and organisations may no longer be able to control information once it is breached, however, they can at least understand what has been leaked, where it has been leaked from and what precautionary measures should be taken as a result.</p> <p>HIBP delivers a range of free and paid services to individuals and organisations anywhere in the world to help them determine if they have been impacted by a data breach, including:</p> <ul> <li>a point-in-time search to check whether an email address entered by an individual into the HIBP search engine has been involved in a data breach;</li> <li>a point-in-time search to find all breached email addresses on a domain verified as controlled by the enquirer;</li> <li>a point-in-time search for real world passwords previously exposed in data breaches;</li> <li>a subscriber service for verified individuals to be notified of data breaches connected to their email address; and</li> <li>a subscriber service for enterprises and individuals to assist in monitoring breaches.</li> </ul> <h3>What kinds of personal information do we collect and hold?</h3> <p>When we use the term personal information, we mean any information or an opinion about an individual who is identified or reasonably identifiable to us. Personal information is sometimes also referred to as personal data. We only collect the limited personal information we need for the purposes of providing our services.</p> <p>We collect and hold email addresses for the purposes of providing our subscription services to verified email addresses.</p> <p>We collect and hold only the bare minimum logging information required to keep the service operational and combat malicious activity. This includes transient web server logs, Google Analytics to assess usage patterns and Application Insights for performance metrics. These logs may include information submitted in a form by the user, browser headers such as the user agent string and, in some cases, the user's IP address.</p> <p>We do not collect or store your personal information when you conduct a search in the HIBP database. Searching for an email address or phone number only ever retrieves the data from storage then returns it in the response. The data from the search is not explicitly stored anywhere.</p> <p>We also store some lists of data classes that were impacted in a particular data leak that is loaded into HIBP. For example, we will state that email addresses and passwords appeared in a leak but will not provide any information about which email addresses had corresponding compromised passwords.</p> <p>The information we collect is not always personal information, as it may not relate to an identified individual or we otherwise may not be able to identify you from it.</p> <p><a href="https://haveibeenpwned.com/Passwords">The Pwned Passwords feature</a> searches compromised passwords from data leaks for the presence of a user-provided password. The password is hashed client-side with the SHA-1 algorithm then only the first 5 characters of the hash are sent to HIBP following <a href="https://blog.cloudflare.com/validating-leaked-passwords-with-k-anonymity/">the Cloudflare k-anonymity implementation</a>. HIBP never receives the original password nor enough information to discover the original password. No identifying information about who the password belongs to is stored.</p> <p>Sensitive information is a subset of personal information that includes health information and other forms of sensitive personal information, and generally requires a higher level of privacy protection than other types of personal information. We do not collect sensitive information.</p> <h3>How do we collect, hold and use personal information?</h3> <p><em>Collection</em></p> <p>We collect personal information:</p> <ul> <li>from individuals directly, who subscribe to our services; and</li> <li>from third parties, such as breached organisations, where Superlative can verify the legitimacy of a breach.</li> </ul> <p><em>Storage</em></p> <p>When a data breach is loaded into HIBP by Superlative, the email addresses are stored in the online system. In limited cases, phone numbers are loaded in separately where they exist in an isolated data store not attached to any other personal information. Phone numbers are not linked to any corresponding email addresses. No other data of any kind (like names) is stored on data load.</p> <p>Superlative securely stores the personal information we hold in a Western United States of America Microsoft Azure data centre.</p> <p><em>Uses</em></p> <p>We use the personal information we hold for the purpose of providing our services.</p> <p>Our subscriber database is checked when new breach data is loaded to establish if the subscriber appears in a new breach, and to send an email notification to the subscriber if required. These email notifications are only ever sent to subscribers who 鈥榙ouble' opt-in to receive notifications. This involves entering an email address on the notification page or domain search page, and then successfully proving control of the email address through email verification. The verification email contains a unique link which must be followed to confirm the subscriber opts-in. Anti-automation measures are in place to limit attempts to subscribe email addresses in bulk.</p> <p><em>Sensitive data breaches</em></p> <p>Data breaches that we flag as sensitive are not returned in public searches, they can only be viewed by using the subscription service and verifying ownership of the relevant email address first. Sensitive breaches are also searchable by domain owners who prove they control the domain using the domain search feature. For more information about how we flag sensitive breaches, see <a href="https://www.troyhunt.com/heres-how-im-going-to-handle-ashley/">Here's how I'm going to handle the Ashley Madison data</a>.</p> <h3>Who do we disclose your information to, and why?</h3> <p>We only disclose the limited personal information required for the purposes of providing our services.</p> <p><em>Domain searches</em></p> <p>Domain searches allow the exposure of all email addresses on that domain to be returned in a single search. Only someone who controls the domain or the website it is bound to can perform a search via one of the verification processes:</p> <ul> <li>Via email address on the WHOIS record</li> <li>Via a common security or administrative email address (security@, hostmaster@, postmaster@, webmaster@)</li> <li>Via a meta tag with a unique code placed on the website</li> <li>Via a file with a unique code uploaded to the website</li> <li>Via a txt entry on the DNS record with a unique code</li> <li>A domain search logs the domain name and requestor's IP address as part of anti-abuse measures.</li> </ul> <p>If you ask Superlative to notify you of future appearance of email addresses on that domain and you provide your email address so it can be notified, that email address is also stored. Anti-automation measures are in place to limit attempts to automate searches.</p> <p>When someone subscribes to notifications or searches a domain, that information is not passed to any third parties under any circumstances other than to send email using the SendGrid service.</p> <h3>Will we disclose your information overseas?</h3> <p>We store all personal information securely in a Western United States of America Microsoft Azure data centre. This data is not shared or disclosed to any third parties overseas.</p> <h3>How do we protect your data?</h3> <p>Security on HIBP is handled by a "defence in depth" approach, that is the service employs many different layers of security including (but not limited to):</p> <ul> <li>all data transmitted over the internet is done over HTTPS;</li> <li>Cloudflare is used extensively to block potentially malicious requests;</li> <li>rate limits on APIs are implemented at both the code level and via Cloudflare;</li> <li>regular security scans are performed to identify code or configuration vulnerabilities;</li> <li>firewalls are employed to limit access to services running on Microsoft Azure; and</li> <li>disclosure of any security vulnerabilities are encouraged via <a href="https://haveibeenpwned.com/.well-known/security.txt">the security.txt file</a>.</li> <li>Third party components are kept well-maintained (see <a href="https://owasp.org/www-project-top-ten/2017/A9_2017-Using_Components_with_Known_Vulnerabilities.html">OWASP's Using Components with Known Vulnerabilities</a>).</li> </ul> <h3>Access to and correction of your personal information</h3> <p><em>Access</em></p> <p>You may access the limited information we hold about you in the HIBP platform in real time. Where there are sensitive breaches, we verify that the requester is the person to whom the information relates prior to allowing access.</p> <p><em>Correction</em></p> <p>To ensure the quality and accuracy of the information we publish, we limit the information we collect and take steps to verify identified and reported breaches. Once we receive personal information known to be involved in a verified data breach, the information cannot be changed retroactively.</p> <p><em>Sensitive data breaches</em></p> <p>Data breaches flagged as sensitive are not returned in public searches. If you wish to prevent any other breached information from being publicly associated with your email address, please utilise our opt-out feature detailed below.</p> <p>In certain circumstances, subscribers may request correction to their personal information, such as their contact email address, by contacting us. Our contact details are set out below.</p> <h3>Unsubscribing and opt-out</h3> <p><em>By email</em></p> <p>Every breach notification email that we send contains an unsubscribe link in the footer. If you would like to unsubscribe but cannot find a recent email from us, use <a href="/NotifyMe">the notification service</a> to send another email to yourself and that will contain the unsubscribe link.</p> <p><em>Using our opt-out feature</em></p> <p>Superlative provides <a href="/OptOut">an opt-out feature</a> for HIBP that, if used, removes an email address from public visibility. The opt-out feature provides you with 3 different ways to control how your personal data is stored and accessed:</p> <ul> <li>Just removal from public searches: The public email address search no longer returns your address. Your address is still stored, you can still see breaches against it by verifying control with the notification service and anyone control the domain your address is on can continue to see breaches against it using the domain search feature.</li> <li>Remove all current and future breaches: No existing breaches impacting your address nor any occurring in the future will be stored against your address. No searches of any kind will return a breach associated with your address. Your address is retained alongside instructions to never load future breaches against it.</li> <li>Remove the email address entirely: The address and associated breaches are permanently removed. If a future breach is loaded that includes your address, it will become publicly searchable again.</li> </ul> <h3>Questions, concerns or complaints</h3> <p>If you have any questions, concerns or complaint about the way in which we have handled your personal information, you should contact us in the first instance. Our contact details are set out below.</p> <p>We will endeavour to reply to you within a reasonable time following receipt of the complaint and, where appropriate, will advise you of the general reasons for the outcome of the complaint.</p> <p>If you remain unsatisfied with the way in which we have handled a privacy issue, you may approach an independent advisor. There is more information and guidance on the website of the Office of the Australian Information Commissioner (<a href="https://www.oaic.gov.au/">www.oaic.gov.au</a>) about protecting your privacy.</p> <h3>Our contact details</h3> <p>If you have any questions, please contact us at:</p> <p> Superlative Enterprises<br /> Level 11<br /> 2 Corporate Court<br /> Bundall 4217<br /> Queensland<br /> Australia<br /> <a href="https://support.haveibeenpwned.com">support.haveibeenpwned.com</a><br /> <a href="mailto:support@haveibeenpwned.com">support@haveibeenpwned.com</a> </p> <h3>Changes to this policy</h3> <p>From time to time, we may change our Privacy Policy on how we handle personal information or the types of personal information which we hold. Any changes to our Privacy Policy will be published on our website.</p> <p>You may obtain a copy of our current Policy from our website or by contacting us at the contact details above.</p> </div> <div class="modal fade" id="notifyMeModal" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true"> <div class="modal-dialog"> <div class="modal-content"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button> <h4 class="modal-title">Notify me</h4> </div> <div class="modal-body" id="notifyMeContainer"> <div class="panel-collapse in" id="notifySubmission"> <form action="/NotifyMe" id="notifyMeForm" method="post" role="form"> <p> Get notified when future pwnage occurs and your account is compromised. </p> <div class="form-group row"> <div class="col-lg-7"> <input class="form-control" data-val="true" data-val-maxlength="The field Email must be a string or array type with a maximum length of '255'." data-val-maxlength-max="255" data-val-regex="That doesn't look like a valid email address" data-val-regex-pattern="^(?!^.{256})[^\x00-\x1F\*\x7F]+@[^\x00-\x1F\*\x7F]+$" data-val-required="Can't do much without an email address" id="NotifyEmail" maxlength="255" name="NotifyEmail" placeholder="enter your email address" type="email" value="" /> </div> </div> <div class="form-group row"> <script src="https://www.google.com/recaptcha/api.js" async defer></script> <div class="g-recaptcha" data-sitekey="6Lcb0woTAAAAAJAbo3ToF_yAJMKMsZgSATbQTRmI"></div> </div> <div class="form-group row"> <p class="termsOfUse">Using Have I Been Pwned is subject to <a href="/TermsOfUse" target="_blank">the terms of use</a></p> </div> <div class="validation-summary-valid alert alert-danger" data-valmsg-summary="true" id="notifyError"><ul><li style="display:none"></li> </ul></div> <div class="form-group row" id="notificationSubmitRow"> <input type="submit" value="notify me of pwnage" class="btn btn-primary" /><i class="fa fa-3x fa-cog fa-spin fa-loader" id="notificationLoading" style="display: none;"></i> </div> </form> </div> <div class="panel-collapse collapse" id="notifySuccess"> <p> You've just been sent a verification email, all you need to do now is confirm your address by clicking on the link when it hits your mailbox and you'll be automatically notified of future pwnage. In case it doesn't show up, check your junk mail and if you <em>still</em> can't find it, you can always repeat this process. </p> <hr /> <p class="text-center" id="postNotificationCallsToAction"> <a class="btn btn-primary" id="addAnotherNotification">add another address</a> <a class="socialLink" href="https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fhaveibeenpwned.com" rel="noopener"><i class="fa fa-facebook-square fa-3x"></i></a> <a class="socialLink" href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fhaveibeenpwned.com&text=Have%20you%20been%20pwned%3F%20Get%20told%20when%20you%20are%20with%20a%20free%20%40haveibeenpwned%20subscription" rel="noopener"><i class="fa fa-twitter-square fa-3x"></i></a> </p> </div> </div> </div> </div> </div> <footer> <div class="container text-center"> <hr /> <p> <a href="/Privacy">Privacy policy</a> | <a href="/TermsOfUse">Terms of use</a> </p> <p> <a href="https://www.facebook.com/haveibeenpwned" rel="noopener"><i class="fa fa-facebook-square fa-3x"></i></a> <a href="https://twitter.com/haveibeenpwned" rel="noopener"><i class="fa fa-twitter-square fa-3x"></i></a> <a href="https://www.troyhunt.com/contact/" rel="noopener"><i class="fa fa-envelope fa-3x"></i></a> </p> </div> </footer> <script src="//cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js" integrity="sha384-rY/jv8mMhqDabXSo+UCggqKtdmBfd3qC2/KvyTDNQ6PcUJXaxK1tMepoQda4g5vB" crossorigin="anonymous"></script> <script nonce="DQs8HLILkZf6LhgS4xG1">(window.jQuery) || document.write('<script src="/scripts/jquery"><\/script>');</script> <script src="//cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script> <script nonce="DQs8HLILkZf6LhgS4xG1">($.fn.modal) || document.write('<script src="/scripts/bootstrap"><\/script>');</script> <script src="/scripts/pwned?v=qOEvxMGdb7fzpGwL-Drr_5-E9ITnykQm7LlRo-n_EP41"></script> </body> </html>