Privacy management

Drupal's access control facility is used to grant permissions on content to users or roles. Sometimes these access restrictions are wrongly referred to as "privacy". Privacy as discussed here revolves around storage data retention, including what information is saved in database or the filesystem and how it is stored. Examples of privacy are random IP addresses being used, or fields being cyphered before saving in the database.

• IP Anonymize: protects users' privacy by establishing a retention policy for IP addresses logged in Drupal's database tables. IP addresses are scrubbed on each cron run according to a configurable retention period. In some jurisdictions there may be legal requirements for you to retain this information.
• Cryptolog: Cryptolog enhances user privacy by logging ephemeral identifiers rather than actual client IP addresses in Drupal's database tables and syslog.
• Invisimail: Invisimail provides a content filter to hide email addresses from spam-bots. Email addresses are converted to ascii code and optionally written to the page using a concatenated JavaScript "write" command so they will appear normally in the page, but they will be obfuscated in the HTML source.
• Private Number: defines a CCK field type for numbers which should be kept private, such as government-issued identification or account numbers. The module enables two of the industry standard best practices for handling confidential data: masking the number when viewed by users without view private number access permission and encrypting the number with a md5 block cipher in 128 bit CFB mode when stored.
• Encrypted Text: defines a CCK field type for texts that will be cyphered in the database.
• Fast Private File Transfer: Makes use of the mod_xsendfile, a small apache 2 module that processes X-SENDFILE headers to manage file downloads, instead of relaying in Drupal private file system management.