Azure ACS and saving information for users on it compared to local ones?

I work with Azure ACS and have included it in the SSO strategy for my .NET 4.0 website. On the "Rule Groups" page, I see that a bunch of different claims can be saved and transferred to the RP (for example, country, address, phone, etc.). It looks like you can also return back any type of application you want to create. This made me think about many issues related to the storage of information for users:

• Does it make sense to store user information (except for the identifier name) in ACS and local database tables?
• It sounded like you could create unlimited groups of rules and rules within them. It is right?
• I would deal with different companies and users within the company. Would creating a group of rules for each company and then creating rules for each user be a smart choice?
• It seems that the API is quite reliable and would allow this to be done automatically as a result of page registration, etc. Right or wrong?
• It would be advisable and recommended to run a request against ACS in order to return information about the user (for example, a request for their email address when they offline send a message about something).
• Could you capture voluminous information for reporting purposes outside of ACS?