Draw it · Fill it
Checking status…

Legal

Privacy Policy

Privacy Policy

Effective: 2026-10-26 (version 2026-10-26)

What we collect

  • Account data: your email address and an Argon2 hash of your password (never the password itself; OAuth-only accounts store no password at all).

  • Google Sign-In data: if you choose "Continue with Google", we receive from Google's identity token only your email address, whether that email is verified, and Google's stable account identifier (the "subject") — and nothing else. We use these solely to create or sign you into your account and to link a Google login to an existing account when the email is verified on both sides. We do not receive or store any Google access or refresh token, and we never gain access to your Gmail, contacts, or other Google data.

  • Two-factor authentication (2FA) data: if you turn on 2FA, we store your authenticator secret encrypted at rest and a one-way hash of each single-use backup/recovery code — never the plain secret or the codes themselves. These let you prove a second factor when you sign in and regain access if you lose your authenticator.

  • Product data you create: saved hunts, units you star, watchlists, reminders, hunter-profile fields (residency, birth year, veteran/disability status, preferences), and named draw parties.

  • Membership and billing data: if you open our payment page to start a paid plan or a free trial, the hosted payment provider's reference number for your customer record; and if you subscribe, your plan, its status and billing dates, the state a Pro plan covers, any promotion code you used, and the provider's reference number for your subscription. You enter your card details on the payment provider's own page; we never see or store card numbers.

  • Push notification data: if you turn on push reminders in a browser, we store, for that browser, its push address (a unique web address at your browser's push service that we send its notifications to) and the encryption keys the browser creates for it, your browser's User-Agent string (which normally names the browser, its version, and the operating system — we use it as the device's name in your device list), when the device was added and when that browser last checked in with us — which it normally does when you open your account, saved-hunts, or watchlists page there — and how many deliveries to it have failed in a row and when the latest failure was. See Push notifications below.

  • Where you first came from: the first time you open the site in a browser, that browser keeps a note in its own storage of the page you landed on (without any one-time sign-in or preview code in its address), the name of the website that sent you there (for example www.google.com, never the full address), any campaign tags in that first link (such as utm_source), and when that visit was. The note stays in that browser and is never replaced by a later visit. When you create an account in that browser, we store the note with your account, along with how you signed up (email or Google). If you open our payment page, we also store the Google Analytics browser identifier described under Usage analytics below, when your browser has one (we keep the most recent one recorded there; a visit without one keeps the earlier one), and we record the date of your first payment. We use this to learn which pages and websites bring people to a paid plan.

  • Operational records: outbound-email delivery logs and, when consent is recorded, the accepted legal version and timestamp.

  • Usage analytics: on deployments where it is enabled, pseudonymous page-view and interaction data collected via Google Analytics (which sets its own cookie to distinguish visitors), to understand how the site is used. When you start a free trial or pay for a plan, our server also reports it to Google Analytics: the plan, and for a payment its amount and currency, the payment provider's invoice reference, and whether it is your first payment, a renewal or an upgrade. Each report is keyed to the most recent pseudonymous Google Analytics identifier we recorded at our payment page or, when we have none, to an identifier we derive from your account with a keyed one-way hash. It never includes your email address, your name, or the product data you create. A browser stops sending usage analytics once one of our own staff signs in on it.

  • Crash reports: on deployments where error reporting is enabled, when something fails in the site in your browser or on our servers, a report of that failure goes to our error-tracking service. A crash report carries:

    • the error message and its stack trace (where in our code it happened);
    • the page or the server address involved, without anything after a ? or # in it;
    • from your browser, the pages you visited and the requests it made to our servers just before the error, with their results and times, again without anything after a ? or #;
    • your browser and its version (its User-Agent string), its language, and your device's locale and time-zone settings;
    • the app version and which of our deployments it was;
    • our internal ID number for your account, if you were signed in;
    • for some errors on our servers, such as one while deleting an account, the hosted payment provider's reference numbers for that account.

    A crash report never carries your email address, your IP address, or what you type into a form, and it does not record your clicks or key presses.

We do not sell personal data, share data with third-party advertising networks, or collect payment card numbers (payment is processed by a hosted payment provider).

How it is used

To operate the service: authentication (including Google Sign-In), your saved research, reminder delivery through the configured email provider and, if you turn them on, push notifications to your browsers, billing and managing a paid membership through the hosted payment provider, and support. Aggregated, non-identifying statistics may inform product decisions. Where you first came from, together with the trial-start and payment reports we send to Google Analytics, is used to measure which pages, websites and campaigns bring sign-ups and paid plans. Crash reports are used to find and fix errors in the service.

Push notifications

Push reminders are optional and stay off until you turn them on. You must be signed in, and they are offered only where this site has push notifications set up. When you choose Get push reminders on your account, saved hunts, or watchlists page and allow notifications, your browser sets up a push address and keys, and we store the push notification data described above so we can reach that browser.

  • What we send. Only the draw-deadline reminders you set — the single reminder and, on Pro, the reminder sequence before a deadline — never marketing. A push never replaces the reminder email. A notification shows the reminder's title and opening line (the hunt code or the name you gave the watchlist, and the deadline date) and links back to this site. It never includes your email address, your account details, or your reminder note. Depending on your device settings, it may appear on a locked screen.
  • Who delivers it. Notifications travel through the push service your browser uses (for example one run by Google, Mozilla, or Apple); your browser chooses that service, not us. We encrypt each notification's content to your browser's keys before sending it, so the push service cannot read it. The push service can still see which browser a notification is for, that it came from our server and when, and our site's contact address. We ask it to discard a notification it cannot deliver within 24 hours.
  • The service worker. To show notifications, our site installs a small background script (a service worker) in every visitor's browser that supports one. It does not cache pages, contacts only our site and your browser's push service, and does nothing unless push has been turned on in that browser.
  • Stopping it. Turn push off in that browser, or remove any device from the list on your account page. Logging out (even with Log out everywhere) and changing your password do not turn push off or remove a device, so on a shared device turn push off before you log out, and remove a device you no longer have from that list. Blocking notifications in your browser's settings stops them from appearing, but our record of that device stays until you remove it, delete your account, or deliveries to it keep failing — and if you have not removed it, simply opening the site in that browser can register it with us again. See How long we keep it below.
  • How long we keep it. A device's push notification data is kept until you remove the device from the list on your account page (turning push off in that browser normally removes it too), your account is deleted, or the push service tells us the push address no longer works or deliveries to it fail five times in a row. The push address and keys are stored as-is, not hashed, because we need them to send each notification.
  • What a removal leaves behind. When you remove a device — from the list on your account page, or by turning push off in that browser — we delete its encryption keys, its name, and its delivery-failure counts, but we keep its push address, linked to your account, together with the date you removed it. That short removal record is what tells the browser itself to switch push off the next time you open the site on it, and it is what stops the device from quietly registering itself again. We keep it until your account is deleted; it is not erased by time alone. (Turning push back on in that browser also clears it, but only if your browser hands us the same push address again, which it usually does not — it normally issues a new one, and the old record simply stays.) A device we drop because deliveries to it kept failing leaves no such record — that is what lets a working device you never removed come back on its own.

Your rights

  • See and download your data. Sign in, open your account page, and choose Export my data to download a copy. It covers your account and the data you created:

    • your account details and hunter profile;
    • your saved hunts, units you star, watchlists, reminders, saved strategies, and point balances;
    • the draw parties you created, including the details you entered for the other hunters in them;
    • the sign-in methods linked to your account;
    • the remembered devices currently active on your account — browsers where you chose "remember this device" so they skip the two-factor code at sign-in;
    • the browsers where you turned on push reminders;
    • where you first came from, as described under What we collect, with how you signed up, the Google Analytics browser identifier we hold, and the date of your first payment.

    It never includes your password, your two-factor authenticator secret or backup codes, or the keys your browser created so we can send it push notifications. It also does not include our own records about you, such as your membership and billing records, the record of emails we sent you, or a message you sent us through the contact form — ask us if you need those.

  • Delete your account. You'll find it on the same account page. Before anything is deleted we ask you to prove it's you: enter your password, or, if your account has no password, a code we email you. This is permanent and cannot be undone. Afterwards we email a confirmation to the address on your account — that email is a receipt, not a step you have to complete. Deleting your account removes:

    • your account details, including your email address;
    • your hunter profile, saved hunts, units you star, watchlists, reminders, saved strategies, and point balances;
    • any draw party you created, along with the details you entered for the other hunters in it;
    • your linked sign-in methods, two-factor authentication data, remembered devices, and push notification devices;
    • the record of where you first came from;
    • your plan, your subscription, and the link to your customer record at the hosted payment provider, in our own database (our log of payment events stays, as described below).

    If you have a paid subscription or a free trial, deleting your account also cancels it immediately, as our Refund Policy describes.

  • What is kept after deletion. A few kinds of record stay behind — some are our own business records, and one belongs to another hunter:

    • Emails we sent you. The date, the kind of message, and the address we sent it to — including the deletion confirmation, when we sent one. Never the message itself.
    • Messages you sent us through our contact form, with the name and email address you gave us and what you wrote.
    • A record of anything done to your account by someone on our team or by one of our own maintenance tasks — a role change, say, or a deletion a team member carried out for you. Some of these records keep a snapshot of your account details at the time, which includes your email address.
    • Details another hunter entered about you. If someone added you to their own draw party, their party still shows the name, residency class, birth year, and veteran status they typed in — but nothing in it points to you or to your deleted account.
    • Your records at the hosted payment provider. If you ever opened our payment page to start a paid plan or a free trial, even if you didn't finish, the hosted payment provider keeps the customer record we created for you then: your email address and our internal ID number for your account. If you completed checkout, it also keeps the card saved for your subscription, the billing details you entered (the cardholder's name and, where the payment form asks for them, the billing country and postal code), and your invoices and payment history. These records stay with the hosted payment provider for seven years after your account is deleted, for refunds, payment disputes, and tax and accounting records. The hosted payment provider may also keep payment records longer, under its own legal obligations.
    • Our log of payment events. We keep a log of the notifications the hosted payment provider sends us and of our requests to it that failed. It holds only the provider's reference numbers for those notifications, requests, and subscriptions — never your name or email address — and has no set end date.
    • Reports already sent to Google Analytics. Usage analytics and the trial and payment reports described under What we collect stay with Google Analytics under its retention settings. They carry a pseudonymous identifier, never your email address or name.
    • Crash reports. A crash report already sent, as described under What we collect, is not erased when you delete your account. It stays in our error-tracking service until that service's retention removes it. It carries our internal ID number for your account, never your email address.

    Copies of your data can also remain in our database backups until those backups are rotated out.

  • Anything else you need. Use the Contact link at the bottom of any page. It works even if you can't sign in.

Retention & security

Account data is kept while the account exists; deleting your account removes it, apart from the kinds of record listed under Your rights above. Passwords are hashed (Argon2); tokens are stored hashed; database backups are retained per the operations policy. For Google Sign-In we retain only the linked email and Google account identifier, never a Google token. Two-factor authenticator secrets are encrypted at rest and backup/recovery codes are stored only as one-way hashes; both are removed when you disable 2FA or when an administrator resets it to help you recover access to your account. Unlike passwords, tokens, and recovery codes, push addresses and keys are not hashed: they are stored as-is so we can send notifications, and are removed as described under Push notifications.