> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/historical-activation-and-usag.md). # Historical Activation and Usage Records Explains which activation and cloud usage records ENERCALC retains and how to request aggregated cloud-project data. ### Does ENERCALC retain historical activation data to help you determine the right seat count? **License > View Activation and License Information** provides the Registration Number, License Holder Name, License Type, and Subscription Expiration Date. **License > View List of Activated Computers** shows the computers currently activated for that license. The activation information currently available is an instantaneous view. We record historical activation data, but don't currently use it. We plan to eventually use this data to help you determine an ideal seat count, not as a sales pitch, but to provide data that supports your license decisions. ### Does ENERCALC retain historical usage data for your company? For projects stored locally, we don't collect any usage metrics. For projects in our hosted cloud storage, we don't collect ***detailed usage*** metrics. We can analyze calculation records across cloud projects to identify used modules and their counts. This data is currently aggregated across all users. We can't identify your module usage without running the analysis solely on your files. We can also run the same query for governing code options. The aggregation limitations above also apply to this data. If this information would be useful, contact to request cloud project usage data. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/historical-activation-and-usag.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.