First of all, modules should not be limited to a model from a database. You may have a Foo module that does not use database content and a Bar module that is mainly based on three different models. Separating a module is a way to logically divide your site into manageable sections. For example, an e-commerce site may have a Products module, a Categories module and a Shopping cart module, etc.
Your last sentence can be divided into two parts:
1) Static information can be on any page - if it is suitable for things like "About Us" and "FAQ", etc., I personally prefer to use the "default" or "home" module and create various actions there counterpart:
./symfony generate:module appname home
and
class homeActions extends sfActions
{
public function executeAbout(sfWebRequest $request)
{
}
public function executeFaq(sfWebRequest $request)
{
}
}
with the corresponding template files (aboutSuccess.php, faqSuccess.php).
2) - ORM ($this->data = MyModel->findByColumn(...) ..). , , , , ( ..). . Symfony.