Three main interaction mechanisms are exposed:
-LocalStorage
-SessionStorage
-KeyValueStorage
Since Outsystems natively uses the WebStorage API to store context information and client variables the three mechanisms are designed not to conflict with OutSystems behavior.

One of the main features of the WebStorage API is that data separation is done automatically based on the domain of the web application, it often happens that several web applications share the same domain and therefore all three mechanisms use "scope" as the data separation mechanism:
-Global : All web apps that share the domain can access data in this scope.
-Application : All web apps in an Outsystems application can access the data in this scope.
-Module : Only the outsystems module that exposes the web app can access the data in this scope.
-Screen : Only the screen can access this data.

In addition, the KeyValueStorage provide for the storage mode (Local or Session) as an additional parameter.

Characters Support (By Design) : The methods exposed accept only text within Latin1 Range.
Browser Offline limit : Each browser has different policy for max quota for the offline storage. However the advice is "Don't store too much information."