An inofficial blog about the Serendipity blog engine

Responsible for this site

Mario Hommel
Birkenweg 2
D - 34596 Bad Zwesten

E-Mail: mario (at)

Here is how this site is storing personal data. You can contact the given E-Mail-Adress for request deleting of eventually stored personal data on this site.

Serendipity Core

Serendipity uses a so-called "Session cookie" for both frontend and backend. A visitor will receive a cookie with a unique ID, which is used on the server to store temporary session user data (i.e. login validity, user preferences). This cookie is mandatory for logging in to the backend, but optional for the frontend. Certain plugins can use the session cookie to store additional temporary data.

The following data can be stored by the Serendipity application on the server (temporarily, invalidated after the server-configured timeout, usually in the range of hours):

  • HTTP browser referer when entering the blog
  • Unique author ID token
  • User data of a logged in author as stored in the database for faster access:
    • Password
    • ID of the user
    • Configured language of the user
    • Username
    • E-Mail
    • Login hashtype
    • Publishing right
  • Last blog entry contents when saving
  • Indicator if Smarty templating is used
  • Possible content of a generated captcha image
  • The configured frontend theme

The following data is stored in cookies:

  • PHP session ID
  • State of entry editor toggle, sort, sort order and filter toggles, last used media library directory (only if logged in)
  • Author login token (only if logged in)
  • Display language
  • After commenting: Last name, E-Mail, URL, state of "Remember comments" (if enabled)

The IP addresses of users are utilized at these places:

  • Stored in logfile of the webserver

User input from visitors (not editors):

  • Comments (all comment metadata, stored in Database table serendipity_comments)
  • Referring URL when entering the blog (if referrer tracking is enabled, in database table serendipity_referers)

Additionally, the following plugins are currently enabled and this is their automatically generated manifest:

Active Theme "timeline"

  • This theme can optionally use webfonts. If enabled, webfonts are loaded from Google/CDN servers, who will receive the IP address of the visitor and his metadata (browser, referrer, user agent, possible cookies)