A cookie is a small text file with an identifier sent by us to your computer or mobile device, and stored in your browser. “Session-based” cookies last only while your browser is open and are then deleted. “Persistent” cookies last until you or your browser deletes them, or they expire. Cookies do not typically contain any personally identifiable information, but may be linked to personal information we store about you. E.g. if you are logged in with a registered user, the cookie will help us remember that you are logged in when you return to the site. To find out more about cookies, visit this site.
Local storage is a component of the Web storage application programming interface. It is a method by which Web pages can store information inside your Web browser. Similar to cookies, this stored information exists even when you close a browser tab, surf away from the current website or close the main browser. But unlike cookies this data is not carried to the remote Web server unless sent explicitly by the web page. Local storage is often used to remember choices a user has made inside a Web application or to cache information to improve performance. Elements stored in browser Local storage is covered by this policy to the extent that the information stored in these elements is communicated back to the server.
Most browsers allow you to refuse to accept cookies and to delete cookies. If you block cookies, you may not be able to use all the features on our website, or have a worse experience.
Authentication: We use local storage to identify you when you visit our website and to authenticate calls our web application makes to the backend servers on your behalf. If you're signed in to Scales, this helps us show you the right information and personalize your experience.
We may make available integrations to other web-based services, allowing you to open those services inside Scales. In order to use third-party integrations in this category, it may be necessary for you to enable support for third-party cookies in your browser. The reason for this is that such integrations may depend on cookies to assert your identity and/or authenticate your access to any non-public assets (documents, boards, etc) opened through them.