Privacy has lately become a much discussed and mission-critical issue in the realm of social networking applications.
Protection of your privacy has been built into Zurker's DNA.
For the purposes of security, Zurker records activity logs which record data including the IP address. However,
IP addresses are discarded after 72 hours. The logged information includes the time stamp, the user's IP address (for 72 hours),
the users' user agent (browser), and the URL accessed. If the user is logged in, the user's Account Number is recorded as well.
Zurker asks for a member's email address when the member creates an account. Zurker does not require real names, genders or
birthdates to be disclosed by default, and Zurker does not ask for full names to be disclosed. Zurker does not ask for ID's.
Like all sites that offer user accounts, Zurker installs a cookie to tie the user to a specific user account. Complex web apps, and
just about all modern websites, would not function without cookies. Note that Zurker does NOT use 'super cookies' which
rely on third-party applications such as Adobe Flash. We just use regular cookies saved by whatever browser you are using. The
content of the cookie is nullified when you logout (sign out) of Zurker.
Zurker does not use, neither directly nor indirectly, any third party web bugs.
Zurker allows precise management of who can see your posts (such as updates, finds, or photos). The settings of who sees what
aren't buried in a privacy tab you have to go to and manage. Every time you upload or post something, the settings are
right there, in plain view, for you to approve or modify. The settings can also be edited later.
All photos are served dynamically, and viewing permissions are checked every time a photo is served.
Members' profiles are viewable by default but access can be restricted to contacts only under Preferences. Members can choose
whether or not to accept notes on their profiles. Avatar photos can be seen by the public, but the visibility of other
photos can be controlled with precision.
Members can restrict whether they accept connect requests from other members or not, and whether they accept notes from
non-contacts or not.
Convos (private messages) can only be sent by members who are in the recipients' contacts, unless the member has specifically
allowed public convos.
All actions are conducted securely via SSL. At this time, passwords are encrypted but other data is not. Zurker's medium-term goal
is to encrypt all data, starting with convos, confabs,
and whispered comments, as well as all other data.
No staff other than the Custodian have automatic access to all data. The web hosting supplier does NOT have access to Zurker's
data. Contractors may be granted temporary access but are closely monitored while working.
Zurker complies with court orders if such court orders are valid. However, since members' IP addresses are not stored permanently, the
information sought by the court order is unlikely to be available.
As with all issues on Zurker, privacy functions and features are subject to discussion and debate. If you are not happy with
something, submit your idea to the #ideas zone with suggestions on how to make it better.
Other users can vote on your idea.
We think our privacy control policy is pretty good, but if the members want to improve it, it will be improved.