Privacy Policy

Last updated 2026-11-03 · DropSentry is a private, invite-only service in beta.

DropSentry is run by one person, not a company. This policy says what is collected, why, who else sees it, and — because the honest answer isn't one number — how long each kind of record is kept.

What we collect

• Your email address — to create your account, confirm it, and send you account email (confirmation and password resets). A display name or Discord handle is held only if the operator adds one to recognise you; you aren't asked for either.
• Your sign-in credentials — your password, your authenticator secret and your recovery codes, held only in protected form. The password and the recovery codes are stored so that they cannot be read back out, and the authenticator secret is encrypted.
• Your rewards-platform logins — the username and password for the shop and for the dashboard, captured by the client and held encrypted against your account, as set out below.
• Sign-ins and account changes — an audit record of what happened and when, with the network address you connected from, the country that address resolved to, and the identifying string your browser sends.
• Your session — a session record holds the same three: address, country, browser string. You have one while you're signed in, and also from the moment you reach any of the forms named under Cookies below, whether or not you have an account.
• What your client reports — while your client is running it reports its own health back: the network addresses it connects from and their country, the browser and client version, whether it is currently listening for codes, whether your logins on the rewards platform and its shop are still alive, how much of its allowance it has used, and whether it is waiting out a pause. This is what your own status page is built from. It is a health signal, never your session itself and never a credential.
• Your drop history — for each drop your client took part in: when it was, what kind it was, how many codes you were given, how many were submitted, how many won, and the reward names your client reported.
• Who invited whom — each account records the invite it came from.
• Your membership — that the account is paid for, the date it is paid up to, one reference that lets a payment be matched to it, and whether the fee has been waived for the account. Nothing is charged today, so there is none of this held yet. Your card number is not part of it and will not be: if card payment is ever taken, a payment processor takes it and those details stay with that processor.
• Which legal version you accepted — the “last updated” date of the Terms and Privacy Policy you agreed to, and when you agreed.
• A message you send the operator — if you use the contact form: what you wrote, the email address you give so that you can be answered, and your name if you choose to give one. Anyone can use that form, with or without an account. The message is emailed to the operator and the site keeps no copy of it; what it does keep is an audit record that a message arrived, carrying the same three details as the records above.

Your rewards-platform logins — the shop login and the dashboard login, username and password — are received from the client in your browser and held against your account, encrypted at rest, with the key that unlocks them kept apart from the database that holds them. They are held so the client can sign your session back in when it ends. One is decrypted only when the operator reads it, which needs an authenticator code at that moment and is written to the audit record. They go to no third party and appear in no log. They are deleted when you ask, and when an account is closed and cleared.

How we use it

Only to run the service: to sign you in, keep it secure, show you and the operator what your client is doing, reach you about your account, answer a message you send us, and keep a provable record of which version of these documents you accepted. We don't sell your data, we don't use it to advertise or profile you, and we don't share it except as set out below or where the law requires.

Who else touches it

Your data stays with the operator. Two other companies are involved in running this website, and only these two:

• Cloudflare — every request to this website passes through Cloudflare, so Cloudflare sees that traffic. It is also where the network address and country we record come from.
• Resend — sends account email (confirmation and password-reset links), and carries a contact-form message to the operator. It receives your email address and the contents of those messages.

Both act as processors: they handle the data to provide that one service and for no other purpose of ours. Each has its own privacy terms.

One more, and only if it applies to you: Discord. If the operator has recorded a Discord handle for you, it is used to check that you are in the Discord server, and to mention you there when your client has stopped reporting so that you know. Discord sees that handle and that message, and nothing else about your account.

And one that does not join the list after all. Payment will be in cryptocurrency, taken by the operator directly, so there is no payment company in the middle to add here. If that ever changes — if a processor, or any other company, is ever involved in taking payment — it will be named on this page before it handles anything of yours, and the date at the top will change so that you are asked to read it. A list of who touches your data is worth nothing if one can be added to it quietly.

Separately, and not through us: the rewards platform sees your activity in your own session there, under its own privacy policy. That is your relationship with it, not ours.

How long we keep it

Different records have different lifetimes:

• Drop and win history — deleted automatically on a rolling 60-day window.
• Sessions — a session, and the address, country and browser string on it, are deleted when it ends. Signing out ends it there and then; otherwise it expires on its own, both after a spell of inactivity and at an outer limit, and expired sessions are deleted. None of them lasts indefinitely.
• Your client's status — one record per account, replaced each time your client reports. It is kept for as long as your client is reporting; once your client stops, it ages out on the same 60-day window as the drop history, and it is deleted outright when the account is closed.
• The audit log — sign-ins, account changes, and the record that a contact message arrived are kept indefinitely. That's deliberate: it is the record of who did what, and it is what lets a question about an account be answered months later.
• Account records — kept while the account exists, and after closure as described next.
• Membership and payment records — kept while the account exists, and kept after it closes. They are the record of money moving, in both directions, and that has to still be there when somebody asks about it. None of the three closure states below deletes them.

What suspension, closure and deletion actually do

You can't change your own account state — there is no self-service close. Closing an account is a request you make to the operator, which the operator then carries out, and the operator can also suspend or close an account without being asked. These are three different things and they remove different amounts, so we'd rather set them out than round them off:

• Suspended — every session is deleted and your client is switched off. Your password, authenticator secret and recovery codes are kept, because a suspension can be lifted.
• Closed to use (banned) — every session is deleted, outstanding confirmation and reset links stop working, and your client's access is withdrawn so it stops and cannot be revived by reinstalling. Your password, authenticator secret and recovery codes are still kept at this stage, in the protected form described above.
• Closed and cleared — all of the above, and in addition your password, authenticator secret and recovery codes are deleted. This is what happens when you ask for your account to be closed. The account is then marked closed, disappears from the site, and the email address becomes free to register again.

That distinction is the point: being locked out is not the same as having your credentials erased, and only the last of the three erases them.

A lapsed membership is none of the three. If you stop paying, nothing on that list happens to you: nothing of yours is erased, your sessions are not ended for that reason, and your account simply stops being sent codes until it is paid for again.

What none of the three deletes: the audit log, the account record itself (including the email it was registered with, so the history and the invite chain stay readable), and any drop history still inside its 60-day window — that ages out on its own. If you want more than this removed, ask the operator and you'll get a straight answer about what is and isn't possible.

How it's protected

Traffic is encrypted in transit, and the secrets we hold are encrypted at rest, with the key that unlocks them kept apart from the database that holds them. Reaching the operator's own administrative pages takes more than a password. This website runs no client-side JavaScript at all, so nothing on these pages measures or follows you.

Your choices

You can ask to see what's held about you, to correct it, to get a copy, or to have your account closed. Each of those is a request to the operator — none of them is something you carry out yourself from the site, and you'll get an answer from a person. If you think something here is wrong, say so: this policy is meant to be accurate, and being told where it isn't is how it stays that way.

Cookies

This site sets one cookie, and it is strictly necessary: it is what keeps you signed in, and before that it carries the token that stops a form being submitted from somewhere else. It is set when you reach a form that signs you in, signs you up, sets a password, or sends the operator a message — reading the site, including this page, sets nothing. There are no advertising cookies, no analytics cookies, and no third-party trackers anywhere on this site.

Changes to this policy

The “last updated” date above identifies the version. When it changes, you'll be asked to accept the current Terms and Privacy Policy the next time you sign in to this website, and the version you accept is recorded against your account.

Contact

Reach the operator through the person who invited you, or directly.

Home · Terms of Service