===== Summary =====
I need the long version for legal reasons, but here's a brief summary:
* This Privacy Policy forms part of the Terms of Service - you should
read those too.
* If you provide me with data, I'm allowed to store it, analyse it,
and use it to run FicLab.
* I'm also allowed to share that data with my suppliers so they can
help me run FicLab.
* Custom metadata (e.g. tags) and statistical analysis may be shared
with other users and the public; everything else stays private.
* Your information may never be sold, disclosed to third parties, or
used for communication about things that aren't FicLab.
* If you want a copy of your data, ask, and I'll send it to you.
* I'll do my best to keep your data secure, and passwords will always
be stored using an appropriate strong hash.
* Unfortunately, nobody is immune to hackers - so while I'll do my
best to prevent it, I'm not liable if that happens.
===== FicLab Privacy Policy =====
This Privacy Policy forms part of the Terms of, and governs how
information that you provide in the course of using The Services
may be used. Please read it carefully.
1. Definitions
In this Privacy Policy, unless the context otherwise requires:
a. "Clause" means a specific clause in this document.
b. "Privacy Policy" means this document.
c. "Identity Data" means any data which uniquely and positively
identifies the User.
d. "User Data" means any data relating to the User, or relating
to items or services associated with the User.
e. "Terms of Service", "Terms", or "TOS" means the document
provided here.
2. Interpretation
In the interpretation of this Privacy Policy, including the Privacy
Policy, unless the context otherwise requires:
a. this Privacy Policy forms part of the Terms of Service;
b. the 'Summary' section on this page does not form part of these
Terms, and that section or its interpretation shall not
influence the interpretation or enforcement of these Terms in
any way;
c. all heading are provided for convenience only, and are to be
ignored in the interpretation of these Terms of Service;
d. in the event of any conflict between this document and the
Privacy Policy, this document shall prevail;
e. singular terms shall also include the plural, and vice-versa;
f. terms such as "including" do not imply any exclusion or
limitation.
3. Collection and Usage
a. All User Data or Identity Data provided or generated by the
User through their use of The Services may, by Erayd LTD or
any of its Suppliers, either automatically or manually, be:
i. collected; or
ii. stored; or
iii. copied; or
iv. used or analysed for the purpose of providing or
improving The Services; or
v. used in communication with the User relating to The
Services.
b. The results of statistical analysis of User Data may be
displayed to other users or to Third Parties for the purpose
of providing The Services (e.g. positive / negative story
ratings).
c. User Data of a bibliographic nature, including custom tags,
may be displayed to other users or to Third Parties for the
purpose of providing The Services.
d. User Data or Identity Data provided as part of Works may be
treated as if it was any other part of the Works, and for the
purposes of this Privacy Agreement shall not be considered to
be either User Data or Identity Data.
e. User Data and Identity Data may not be transferred by Erayd
LTD or its Suppliers to any Third Party, for any reason,
whether or not that data is anonymised.
f. The User consents to User Data and Identity Data being used by
Erayd LTD or any of its Suppliers to contact the User
regarding The Services.
g. Neither Erayd LTD nor any of its Suppliers may use User Data
or Identity Data to contact the user where that contact does
not primarily relate to The Services.
h. Neither Erayd LTD nor any of its Suppliers may sell the
results of any analysis of User Data or Identity Data.
4. Storage and Transit
a. Erayd LTD shall make its best reasonable effort to ensure that
Identity Data is stored securely and is not accessible to
Third Parties.
b. Wherever possible, User Data and Identity Data shall always be
encrypted while in-transit over any public network, using a
cryptographic scheme widely accepted as suitable for that
purpose.
c. Neither Identity Data nor User Data shall be required to be
encrypted when at-rest (e.g. when stored on disk or in a
database).
d. Notwithstanding clause (4c), passwords shall always be stored
in a cryptographically hashed form, and shall be hashed using
an algorithm widely recognised as being suitable for secure
storage of passwords.
5. User Access
a. The User may request a copy of all User Data and Identity Data
relating to them and held by Erayd LTD.
b. If the user requests a copy of User Data or Identity Data,
that data shall be provided via email to the email address
specified by the User.
6. Liability
a. Erayd LTD shall not be liable for any unauthorised access,
loss, publication, use or misuse of User Data or Identity Data
stored on or in transit through any of its systems.
b. Erayd LTD shall not be liable for any unauthorised access,
loss, publication, use or misuse of User Data or Identity Data
by any of its Suppliers.
c. Erayd LTD shall not be liable for any costs, losses or damages
arising out of or in connection to any unauthorised access,
loss, publication, use or misuse of User Data or Identity
Data.