Terms of Service

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

1. Who this is for

DropSentry is a private tool offered by invitation only. An account is created only when an existing member invites you. Accounts are personal; don't share your login, your authenticator, or your invite links. You must be at least 18 and old enough to hold an account on the rewards platform in your jurisdiction.

DropSentry is a paid service. Membership costs money, a month or a year at a time, and there is no free tier — an invitation gets you an account, not a free one. Priority — being sent a drop's codes earlier than other members — is sold alongside it, as an upgrade you add to your membership from inside your account rather than a thing you buy on its own. Sections 5 to 7 are the agreement for all of that, and they are written here before anything goes on sale so that none of it is news to you at the moment you are asked to pay.

Nothing is being charged to you today. Nothing is on sale yet and no payment is being taken. What a membership costs is on the pricing page rather than in these terms, so that a change of price is not a change of agreement. The same goes for priority: what it costs on top of a membership is on that page too, and not here. Sections 5 to 7 are what will apply when the service goes on sale; when it does, the date at the top of this page changes and you are asked to read and accept the current version, the same as any other change to these terms (section 13).

If you already have an account, what happens to it when charging begins is not settled here. Nothing on this page says an account that exists today carries on without paying, and nothing on this page says it stops. When that is decided it will be written into this section, the date at the top will change, and you will be asked to read it. Please don't read either promise into the silence — there isn't one yet.

2. What DropSentry does — and what you are doing

DropSentry watches public chat and streams for promotional reward codes. When it finds one, it dispatches that code to a client you have installed in your own browser.

That client is a userscript you install yourself, with your own userscript manager (Tampermonkey or Violentmonkey), in your own browser. It acts inside your own logged-in session on the rewards platform — the same session you would use by hand. It submits codes to that platform as you, it keeps that session signed in on its own, and any reward it obtains lands in your account on that platform.

So the central fact of this service is this: you remain the account holder on that platform, and activity carried out in your session is your activity. DropSentry decides which codes to send and when; you decide whether to run the client at all. You can stop at any time — disable or remove the userscript, sign out of that platform, or ask for your DropSentry account to be closed.

Your logins for the rewards platform are stored by DropSentry. When you sign in to that platform on a page the client is running on, the client captures the username and password you typed and sends them to this website, where they are encrypted at rest and held against your account. They are held for one purpose: so the client can sign your session back in by itself when it ends, which is the commonest reason a member misses a drop. Two logins are held this way — the shop login and the dashboard login.

Who can read them: the operator, and nobody else. One is decrypted only when the operator asks for it on your account page, and only after entering an authenticator code at that moment. Every reading is written to an audit record naming who read it and when, and the count is shown on your own account page. They are sent to no third party, shown nowhere else, and written to no log.

If you would rather we did not hold them, your userscript manager’s menu has a command to forget each saved login, and you can ask the operator to delete what this site holds. The client then works only from the session already in your browser, and a session that ends stops it until you sign in again yourself.

3. The rewards platform is not ours

The platform where codes are redeemed is a third party. It has its own terms and its own privacy policy, and your relationship with it is between you and it. DropSentry is not affiliated with it, not endorsed by it, and not acting as its agent.

You are responsible for reading that platform's terms and for deciding whether running an automated client inside your session is acceptable under them. If the platform objects — if it warns you, rate-limits you, withdraws a reward, or closes your account — that outcome is yours. The operator cannot reverse it, appeal it, or compensate you for it, and has no influence there. The operator will tell members plainly if it learns that a platform has begun objecting, but promises no warning, because it may get none either.

If a platform asks us to stop, or the operator judges the risk to members has changed, the service or your use of it may be suspended without notice.

4. Limits you should expect

The service runs inside limits set by the rewards platform, not by us. In practice that means:

• the platform allows about one redemption per account per day, so after a win your client goes quiet until that resets;
• the platform limits how fast codes can be submitted, so your client deliberately submits fewer codes than it was given rather than spending every one;
• a drop can be missed entirely, and a code can already be spent before it reaches you.

Those are the operator's current observations, not commitments. They can change the moment the platform changes, with no notice, and this page may lag behind reality.

5. Paid membership, and what happens when it lapses

None of this is live yet, as section 1 says. It is set down now so that you read it calmly, rather than at a payment page.

The operator can waive the fee for an account, and that is a favour rather than a plan. It is done at the operator's discretion, one account at a time, for its own reasons. It is not a tier, not something you can apply for, and nothing in these terms entitles any account to it — if you have to ask whether yours is waived, assume it is not. A waiver can be ended at the operator's discretion as well, and from that point the rest of this section is what applies to you.

A membership is bought for a fixed period, and the period is the one you paid for. A month, a year, or whatever lengths are offered when you pay: each payment moves the date your membership runs to the end of the period it bought. That date is the whole of what a payment buys — not a place held for you indefinitely, not a permanent upgrade. When it is reached, you pay again or you stop.

It renews itself unless you stop it, but the payment does not. Unless you cancel, the membership is treated as continuing, and a renewal falls due on the date it runs to. Payment is in cryptocurrency, and a cryptocurrency payment cannot be repeated without you — so nothing is ever taken from you automatically, and the renewal is a payment you make yourself, on that day, and on each one after that, until you cancel. Nothing here lets the operator charge a card or an account of yours on its own, and you are never charged for a period you cancelled before it began.

You have the whole of the renewal day to pay. Your membership runs to the end of the day it falls due, not to the hour it was bought, so a payment that arrives at any point during that day keeps you running without a gap. The day is counted in UTC. One clock is used for every account, so the deadline is the same day for everybody rather than depending on where you are.

If payment has not arrived by the end of that day, your client stops being sent codes from the start of the next one. That is the sentence to read twice, because it is the one people otherwise meet when the script goes quiet. The renewal day is the whole of the leeway there is: there is no further grace period, there is no reduced service, and your client gives you no warning of its own — the first day your membership is not paid for is a day nothing arrives. A payment that is attempted and fails is the same thing as not paying: the membership is not extended while it is being sorted out, and you should assume you have until the end of the renewal day to put it right rather than that somebody will chase you.

A lapsed membership is not a suspension and not a closure. Nothing in section 12 happens to you because you stopped paying. Your account stays as it is, your history stays as it is, your password and authenticator stay as they are, and you can pay again and carry on. Lapsing stops the codes and does nothing else.

How you cancel. Tell the operator, whenever you like. It takes effect at the end of the period you have already paid for — cancelling halfway through a month, or halfway through a year, does not forfeit the rest of it. And because the operator cannot charge you again on its own, simply not paying is a cancellation in itself: nothing further can be taken from you, and nothing will be.

A period you have paid for is paid in full, and if the service stops the rest does not come back. Section 10 says plainly that this is a beta service and that it may change, break or stop at any time, and paying for a year up front does not change that. If it stops partway through a period you have paid for, there is no refund of the remainder — so if that is a risk you would rather not take, pay by the month instead, where the most you ever have at stake is the month you are in. What does still come back is what section 7 promises: if the operator suspends or closes your account through no fault of yours, ask, and you get back what you paid for and did not get to use.

6. Priority: what you are buying, and what you are not

What it is. Priority changes the order, and only the order. With it, your client is sent a drop's codes earlier than members who do not have it.

What it is not. It is not more codes, and it is not a better guarantee of anything. Every limit in section 4 applies to a member with priority exactly as it does to a member without it: the rewards platform still allows about one redemption per account per day, and your client still submits fewer codes than it was given rather than spending every one, because that platform limits how fast codes can go in. Being earlier in the order does not lift either of those, and it cannot — they are the rewards platform's limits, not the operator's. So you can pay for priority and still miss a drop, still find a code already spent, and still go a long stretch with nothing.

And the operator makes no claim about how much difference the order makes. It has not been measured. No figure is offered here and none should be read into this: section 10 is still the whole of what is promised about results, which is nothing. If you want a number before you pay, the honest answer is that there isn't one.

7. Refunds

A refund is a person deciding, not a button. Nothing on this site issues one, and nothing issues one automatically. You ask the operator, and you get an answer from the operator.

Money taken wrongly comes back. A payment taken twice, a payment taken after you cancelled, a payment for a month in which the operator suspended or closed your account through no fault of yours — ask, and you get it back. If you had paid for a longer period than a month, the same applies to the rest of it: ask, and you get back the months you did not get to use, as well as the one it happened in.

A quiet month does not come back. A missed drop, a stretch with no reward, a code that was already spent, a reward the platform withdrew afterwards: none of those is a billing error, and none is a ground for a refund. Section 10 promises no results, and section 6 says priority buys the order and not an outcome. That is what you are agreeing to when you pay, and it is set out here rather than left to be discovered.

You pay in cryptocurrency, and that cannot be reversed for you. There is no payment provider in the middle to claw a payment back, so a refund is the operator sending money to an address you give, by hand, agreed with you first. There is no chargeback either: your card issuer is not involved and cannot be asked to step in, because no card was used. If you pay the wrong amount, or send it to the wrong place, tell the operator — getting it back may simply not be possible, and you will be told straight which it is.

Sending less or more than a deposit invoice asked for is not that wrong-amount case. If less arrives than the invoice showed, the address stays open for the difference — send the rest whenever you're ready, and nothing you already sent is lost. If more arrives, the extra is not refunded; it becomes a credit on your account instead. The paragraph above is for paying the wrong amount by mistake or sending to the wrong address, not for this.

No card is involved, and no card number is held here. Cryptocurrency is the only way payment is taken, for now. If card payment is ever offered as well, a payment processor takes it, the operator will not hold your card number, those details stay with that processor, and that processor is named in the Privacy Policy before it handles anything of yours.

8. Your account here

You're responsible for keeping your password and authenticator safe. An authenticator is required. Save your recovery codes when you're shown them — they're shown once. Tell the operator promptly if you think your account has been compromised.

9. Acceptable use

Use your account only for its intended purpose and only for activity you're entitled to carry out. Don't attempt to access other members' accounts or data, probe or attack the service, share or resell your access, redistribute the client, or run it on an account that isn't yours. The operator may suspend or close an account at any time, at its discretion, including for conduct that puts the service or its members at risk.

10. No warranty — availability or results

This is a beta service provided “as is” and “as available,” with no warranty of any kind and no guarantee of availability or fitness for any purpose. It may change, break, or stop at any time.

There is also no guarantee of results. Nothing here promises that a drop will be detected, that it will be detected in time, that a code will reach you, that your client will be running when it does, that a submission will succeed, or that a reward you obtain will be kept by the platform. Detection is imperfect: it misreads, and it misses.

11. Liability

To the fullest extent allowed by law, the operator isn't liable for any loss arising from your use of the service or your inability to use it — including a missed drop, a lost or withdrawn reward, action taken against your account on another platform, or any indirect or consequential loss. Nothing in these terms limits liability that can't be limited by law.

12. Ending your access

You can stop using DropSentry at any time by disabling or removing the client. Closing the account itself is a request, not a button: you ask the operator and the operator carries it out. There is no self-service close, and account state is changed only by the operator — which also means the operator may suspend or close an account without being asked, under section 9.

Three different things can happen to an account, and they are not the same:

• Suspended — you're signed out, your client is switched off, and sign-in is refused. Your password and authenticator are kept, so this can be reversed.
• Closed to use (banned) — you're signed out, outstanding email links stop working, and your client's access is withdrawn, so it stops and reinstalling won't revive it. Your password and authenticator are still kept, in protected form, at this stage.
• Closed and cleared — everything above, and in addition your password, authenticator secret and recovery codes are destroyed. This is what happens when you ask for your account to be closed.

In none of those cases is the whole record erased: a minimal account record — including the email address it was registered with — and its history are kept, as described in the Privacy Policy. An account that was suspended or closed to use can be reinstated, and it comes back attached to that same history, including the record of the closure.

13. Changes to these terms

These terms may change. The “last updated” date above identifies the version, and the version you agreed to is recorded against your account. When it changes, you'll be asked to read and accept the current version the next time you sign in to this website. You can decline. Declining signs you out of this website and nothing more. It does not disable, revoke or cut off your installed client, which keeps running, and it does not close your account — you can sign back in and accept the new version whenever you like.

14. Contact

Questions go to the person who invited you, or to the operator directly.

Home · Privacy Policy