# \[Be Aware\] Bountysource revising ToS. May jeopardize Syncthing bounties.
**URL:** https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218
**Category:** General
**Created:** [June 19, 2020, 5:13pm UTC](https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218 "2020-06-19T17:13:20Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@sunjam](https://forum.syncthing.net/u/sunjam)
#### Post date: [June 19, 2020, 5:13pm UTC](https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218/1 "2020-06-19T17:13:20Z")
I’ll attach the emails here, [along with the Nextcloud discussion thread](https://help.nextcloud.com/t/dont-use-bountysource-anymore/84943/). All of this happened about 48 hours ago, but revised ToS have been promised in their last email to donors.
Announced new Terms of Service. Unclaimed bounties 2 years old or more will be seized by bountysource itself. This would include the $5k bounty for e2e encryption on Syncthing and any others.
> **Click for: Terms of Service Update email**
>
> Hi,
>
> You are receiving this email because we are updating the Bountysource Terms of Service, effective 1st July 2020.
>
> **What’s changing?**
>
> We have added a Time-Out clause to the Bounties section of the agreement:
>
> _2.13 Bounty Time-Out._
>
> _If no Solution is accepted within two years after a Bounty is posted, then the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. For Bounties posted before June 30, 2018, the Backer may redeploy their Bounty to a new Issue by contacting_ _[support@bountysource.com](mailto:support@bountysource.com)_ _before July 1, 2020. If the Backer does not redeploy their Bounty by the deadline, the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource._
>
> You can read the full [Terms of Service here](http://email.bountysource.com/ls/click?upn=kFsTHJG5ArrYpBprdsidpNXIp34iXblmb2Pvhn6D7LNtcEuJtubp-2FpuwURwQC68wPUqJ_iHezpJCanpawYytaDrufypyjTP5PwpjcbkVsn2zPg19w5c9RojZzaJi0BHD4M29NALRA-2F-2F1FOQZRNb5Jb9l36kkLV2aOmcaSavMyTGJR-2BiX2HNKe7U6pC9vFJhardO-2F-2FCIQF0eRf71Bfp9DL7zCc8NbRWOtPhH-2BSX6KAMIg4pKpB1EKmDWhE3mhF67q-2Bs2PgFTACxgnjZ-2F6-2B7Qu5NivGQi0YAu74VHfx0kl50D3WDzyzfhuW-2Blrxr5V0Iw8QKGfHT-2Fp2PhimkFVPzn9qBjwIDV1tI3Htt8h6-2BlLwq5E-2FdAkLZ-2F00WFVI4kYI1Eq-2BO1niXpIvZXDwmOF3JOEAax7E2PWJVmAJFQ985dO973tNkJd3iJgMNSWcVOV93AWnpi4exgsBHp9BPVcanki1belgcF55DwvGbA9xjfklQtGA9XKL-2BKzpnypSWGrysuSJ5dwPjPpe9NPMdLcSO2AcoQzX0Zk-2F3jQZua8CmxZQwcXn23l-2BN8-2Fw7etRaFw9FIpHdC4AUFDcGId0ePFm-2F5eYOchm2CgtTe4fGwTy7CNZ7fbWFYHXeKsdEGdj4ydwstTH-2BChLHkba4bCp5STP0f7uKqfS19tEINTS-2BDcXZ5EtqF298p9xX-2FhvGPEXc0mbqoXDIM2NCdP-2FJe3uslrgE-2BVeOTZcHF3JsFMA08BiSkjHsmy24AbbjPeTK464Ob8vfzB8dZSN8BMQ61bn9OYoGDw4HxPBLwXgwuMW0rf6VVeImxNvP8QarV-2FuN2oHN1XQD4Y-2BW6gX1yynKrtx5pH-2Fh-2FqJc92-2BepycVydFJDjWBvQBfVAMp-2BMUOD-2Br-2BSrax0n4qr7s0WiSFkakNSHCtweAWO2ggy437w-3D-3D)
>
> **What do I need to do?**
>
> If you agree to the new terms, you don’t have to do anything.
>
> If you have a bounty posted prior to June 30, 2018 that is not currently being solved, email us at [support@bountysource.com](mailto:support@bountysource.com?subject=&body=) to redeploy your bounty. Or, if you do not agree with the new terms, please discontinue using Bountysource.
>
> Thanks for reading
>
> Bountysource Team
> **Click for: Terms of Service withdrawn, revised ToS promised email**
>
> Hi
>
> You’re receiving this because we updated our [Terms of Service.](http://email.bountysource.com/ls/click?upn=kFsTHJG5ArrYpBprdsidpNXIp34iXblmb2Pvhn6D7LNtcEuJtubp-2FpuwURwQC68wfFGP_iHezpJCanpawYytaDrufypyjTP5PwpjcbkVsn2zPg19w5c9RojZzaJi0BHD4M29NALRA-2F-2F1FOQZRNb5Jb9l36kkLV2aOmcaSavMyTGJR-2BiX2HNKe7U6pC9vFJhardO-2F-2FCIQF0eRf71Bfp9DL7zCc8NmYq7FoO-2F2PGgI0txFEbd2EZExoIXU1SgrfVco02eapY8NdhKGSnJiA5naEcTxappgh7i-2BMEPWp-2F5dF4h1NptlJgolyWQPMiGBnN13kwZLwKnPtafhKfeRSmGzOQ1cQnRbwippDK1YF2OW1pvkByCyz2BLi5K10fXtXEmc-2FafxUGkglDiNq2OjlNx-2BjBUbao1a6BpRdQ0pZNSQxZoNUgsABz8Qwxv1ZVBpkvH9FHN72m0k2oPqV03lVM6LZs-2BN-2B075FjdFUIR8cYtLC-2FmxTRsvZVk3RkOI768CQ7iupzmuSS4BJsv4UIWsA52NttjVc9fgQ-2BER7W0eQh9GbQiSUy2mTR1MPMaN9oro4QttWXZltMBljHt5X-2FfaswRP-2FKHLcg0udq6W2wokNEsYKoqfZWzzj5aujxZiKldMQ95hn1cXyCKwrGwEVOjpheOUINRPhKGeeO-2FYXWXC7TtQ-2FVvw9IVGALE213BZWpaaaqAJ3TaSGlcIU5aCR4Ca06wUQEwnaYndoaxIyZz8-2FWVZ2Obai23NbeIOzhUAwJ2kMdTu5SSXJNdjD-2Fh-2BbjbBHnQFzdQshu2mEEwPytRafqaYZVRiunczXjbcPr0g9EhdD1-2FjmzfliKcrgsDEaycWZ0Xmz9B4k4gsskUa0-2FBW8ZMEjiCZB4NqiZZ8RS9kEVUBC2P-2BhKl0A1dDDQC9fP8ZWK4DezTq-2BmXGlnHbSZ3ps71Mj9gjrSuef0j-2BTxdw-2Bw3lTQlvk7TjNGj8zC6eO-2BXRBnLct4LgSKA-3D-3D)
>
> **Withdrawal of new Terms of Service**
>
> Yesterday, we communicated a change to the Bountysource Terms of Service (ToS) agreement.
>
> **These changes have been withdrawn and the ToS reverted to its prior state.**
>
> The ToS will be revised and clarified in the future.
>
> Thankyou
>
> Bountysource Team
>
> [support@bountysource.com](mailto:support@bountysource.com)
---
### Author:  [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [June 19, 2020, 5:56pm UTC](https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218/2 "2020-06-19T17:56:04Z")
We’ve seen this, but I don’t think we have any controls over this. The money is not ours, and we can’t “give back” the money.
A payout, in general, requires all people who chipped in money to accept the work, which by definition jeopardises the bounty from the point of view being possible to claim it.
I think I spent over 2 months claiming a bounty that was 10 or so backers for a hundred bucks or something.
I can’t imagine a 5 year old bounty with a lot more people being feasible to claim. (I can’t check now many backers now, bountysource seems mostly broken atm)
---
### Author:  [@sunjam](https://forum.syncthing.net/u/sunjam)
#### Post date: [June 20, 2020, 2:08am UTC](https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218/3 "2020-06-20T02:08:33Z")
> [@AudriusButkevicius](#):
>
> I can’t imagine a 5 year old bounty with a lot more people being feasible to claim. (I can’t check now many backers now, bountysource seems mostly broken atm)
Actually have seen bounty claims going through fine. Marcel claimed a [2013 bounty](https://www.bountysource.com/issues/1692470-add-sharing-use-share-api?utm_campaign=plugin&utm_content=tracker%2F216513&utm_medium=issues&utm_source=github) two days ago without issue.
> [@AudriusButkevicius](#):
>
> A payout, in general, requires all people who chipped in money to accept the work, which by definition jeopardises the bounty from the point of view being possible to claim it.
I didn’t actually click the approve button personally, but seemed to be claimed just fine regardless.
> [@AudriusButkevicius](#):
>
> We’ve seen this, but I don’t think we have any controls over this. The money is not ours, and we can’t “give back” the money.
My hope is to raise awareness and provide more incentive for bountysource to continue supporting your work without claiming the donations for themselves. I’d argue the money is no more theirs than yours after fees, as it is set aside for people to claim who help your project.
Thanks for all you do either way. Cheers.
---
### Author:  [@mexsudo](https://forum.syncthing.net/u/mexsudo)
#### Post date: [June 22, 2020, 4:17pm UTC](https://forum.syncthing.net/t/be-aware-bountysource-revising-tos-may-jeopardize-syncthing-bounties/15218/4 "2020-06-22T16:17:19Z")
FYI: the TOS revision was abandoned the following day, now it is back to the old version. … Bountysource sends email notices, I assume those of us that have used the “service” at one time were notified. … BTW: My money evaporated into the ozone a few years ago under the Old TOS… Burned once, never again!