SAFE-FS Risk Disclosure
Download Link (.doc version)
===COPIED BELOW, FOR THOSE WITHOUT DOCUMENT EDITORS===
SAFE-FS Risk Disclosure Document
Last updated June 28th, 2016
As in any new technology project on the cutting
edge, many unforeseen events can occur, new variables can come into
effect, and things can turn out in ways we are unable to predict. As
such, it is imperative that SAFE-FS discloses a non-exhaustive list
of possible and potential risks involved with the project and your
purchase of our crowdsale coin, to protect your interests.
1) General Risks & Risk Associated with the
SAFE Network
SAFE-FS is a technology based on the SAFE
Network, being developed by maidsafe.net. This means that any
malfunction, delay, or unintended / unexpected functioning involving
anything—including rise in value of coin or the amount of Safecoin
received—is not the fault or responsibility of SAFE-FS, and we can
not be held liable for any such circumstances.
2) Risks of not reaching financial goals
SAFE-FS is being developed by WhiteOutMashups
and a dynamic team, and will continue to be developed regardless of
the completion of the crowdsale. However, certain goals or offerings
may be unable to be funded depending on the level of success that the
crowdsale achieves. This will not halt development, but will mean
that certain offerings will not be made available within the
originally desired time period, but may still become available at a
later date.
3) Risks of uneven Crowdfunding
There is a very exact and finite number of
SAFE-FS Coin (“SFSC”) being created for the crowdsale, and in the
event of an uneven amount of funds being purchased, the coins will be
rounded to the next whole integer at the discretion of SAFE-FS before
being sent to the crowdsale purchasers.
4) Risk of Insufficient Interest in Distributed
Applications
It is possible that SAFE-FS will not catch on
with the main stream, and not generate enough users to become
profitable. Such a lack of interest and revenue could impact the
development of the platform and uptime for the application.
5) Risk of Hacking or loss of digital assets
It is not imppossible for hackers to gain access
to any types of data, and this includes SAFE Network logins and
SAFE-FS crowdsale coins through the use of many attack vectors
including keyloggers, the recording of keystrokes / screens, and
other types of attacks. SAFE-FS can not be held responsible for any
such attacks, and it is up to you to protect that which is yours.
6) Risk of Loss of Access to Refunded Payment
If—for any reason—any payments made by you
are refunded, it is up to you alone to protect the coins sent back to
you. We are not responsible for the actions or policies of any
wallet, exchange, or other medium anyone may be using to hold, send
or otherwise use Bitcoins or MaidSafeCoins. If you are for any reason
unable to access your coins after they have been refunded to the
address which they were sent from, that is no fault of SAFE-FS and
they can not be held liable or accountable in any way. Furthermore,
if your purchase was sent from multiple addresses, we will refund the
entire amount (as visible on the blockchain.info webpage of the live
sale address) to the address that the larger amount has been sent
from. In the event of an even split, we will send to the first
address as listed in alphabetical order.
7) Risk of Team Member Dispute
Our SAFE App Store team will grow in number if
certain funding goals are successfully reached. This will be a
welcome advancement, and strengthen our project, but can also open up
new possibilities for dispute or disagreement in the future. If there
should be a dispute in the future, and any of the newly added team
member(s) have to leave the project due to any reason, including
career, family, emergency or anything else, there is the possibility
that they will be replaced with someone else, in order to fill that
role for the SAFE App Store. Our first priority is achieving our
deliverables to the community, and in the unfortunate event that any
of our planned team members are unable to commit fully to the SAFE-FS
in the future, we must be flexible enough to allow for this and be
open to the fact that we may have to pivot, and bring on new team
members. A technology startup can be a hostile and demanding
environment at times, and achieving the deliverables must come before
personal connections.
8) Risk of Deliverable Dissatisfaction
All parties have different expectations for the
results of the SAFE-FS deliverables, including but not limited to
rewrites in new languages, the aesthetic appeal of the layout, the
ease of the functionality and integration, and all are accounted for
and in some cases voted upon in the SAFE-FS Forum and FSDGC
discussions / polls. However, the development team is under no
requirement—either implied or contractual—to bend to the will of
any party, except a collective 66% vote of the following three
parties: the SAFE-FS company, WhiteOutMashups, and the FSDGC. The
only responsibility they are under is to create and distribute the
deliverables—as interpreted by SAFE-FS—to the SAFE Network once
it is live. They may not be held to any outside requirements /
responsibilities.
9) Unanticipated / Other Risks
maidsafe.net's Safe Network is a completely new
and untested technology, and as SAFE-FS is based on this technology,
there are countless unforeseeable possibilities ahead. There may be
many different types of risks that lie ahead, and that is to be
understood by anyone embarking on this crowdsale with us.
