>>why wouldn't i just store cookie data in my local datastore, why would I want to use yours? The vast majority of my theoretical potential customers are the k

>>why wouldn't i just store cookie data in my local datastore, why would I want to use yours? The vast majority of my theoretical potential customers are the kind of buyers who need copy-paste solutions. This is most e-commerce sites and affiliate managers. >>Amazon offers simpledb, google app engine, both offers are very cheap, and wouldn't take much to create a simple datastore utilizing either of these services to simple key value pairs.. how would you differentiate? Technologically I would not be trying to compete. I would be competing on ease of use and having a system/dashboard that is specific to this use case. Infrastructure vs. product I suppose you could think of it as. >>In all honesty.. cookies are usually lost between uses and not during the session You mean between sessions? If so, that is the other major selling point. I am employing methods that will make the cookies as persistent as possible between sessions and even between browsers (yes, cross-browser cookies, via Flash storage). The idea here is that if you already have a person logged in, you don't need this. This is for people who want to associate an arbitrary amount of data with a visitor and ensure (to the best of the service's ability) that it won't get deleted. I have a feeling my customers will be more concerned with this feature than any other.