(Still a draft and subject to change.)
- I will only knowingly store identifying
information if such information is actually needed for
identification. This will include names, email addresses,
websites and possibly user IDs such as OpenIDs. All of the
applications I develop will use hashed passwords. I will make
the best efforts to keep identifying information safe. I've
made effort to reduce the use of information that can
potentially expose the user to abuse (e.g. email addresses,
which could end up to the hands of spammers). Email addresses
will not be shown publicly unless requested by the user. All
other information will only be shown if provided and
*explicitly* stated as publicly viewable.
- I make no guarantees what information third-party
applications (e.g. Melody) store. However, I try to keep them
up-to-date and I only use open source packages that appear to
use sane security practices.
- My webhost collects standard Apache log information. Some
of these pages use Google Analytics, but I, personally, am only
concerned of aggregate information that doesn't identify users:
what search keywords people use to find the pages, which
websites they come from, maybe which countries they come from
and what they do on the site, on broad terms (e.g. do they
actually read the pages or do they go away).
- External image use is discouraged, and should only appear
in third-party applications. Some pages use third-party
- Visitor IP addresses may be logged to make spam quenching
easier, but neither the address itself nor the block owner
are ever displayed publicly. Spammers may be ridiculed, though.
There is admittedly currently no easy way to contact me if
problems are actually present, but you can try
emailing me. Since I
believe email is a moribund medium, I cannot make guarantees
about reaction times, which is admittedly a pretty bad
thing. Expect this to be fixed in due time.
(Back to main page)
Last modified: $Date: 2011-05-25 16:24:08 +0300 (ke, 25 touko 2011) $