|
We will not read or modify the content of "private" data files (as defined
below) uploaded or otherwise generated by you on our servers, unless you
provide us written permission to do so.
Copies of your private data files are produced for backup purposes, so
this policy also applies to all backup copies of your files.
Files that do not have the "world-readable" permission (or the
"read-by-others" permission if the group of the file is "users")
are considered private.
Mailboxes and databases are an example of private content.
File permissions are easily managed through a variety of interfaces,
such as our web interface, "file transfer" applications, or your
unix shell.
There are two specific exceptions to this rule:
-
System administrators may read and modify your
crontab(5) file.
This file contains commands that you wish to execute periodically on
the server.
-
System administrators can view your e-mail configuration settings.
For the more advanced customers who use the mail-to-command
feature, this includes scripts and configuration files related to
the specified programs
(for example, ~/.procmailrc or ~/.mailfilter).
Although we will not access the content of private files, we can obtain
the following information about any file on the server:
-
The name of the file
-
The file size
-
Date and time of last modification
Although we will not read the contents of your private files, we encourage
you to
encrypt and
and
digitally sign
any sensitive information you wish to place on our servers.
This is very easy to do using the
gpg(1) tool,
which is available on our servers.
Specifically, we recommend the algorithms AES, 3DES and RC4, since our
servers have specialized hardware to handle these operations efficiently.
|