# Data Transmission #### Peptype counts activity signals, not content. This is important because Peptype does not collect the content of what users type and does not transmit keyboard input data or personal text. The system only uses basic activity signals needed for gameplay, while keeping typed content private and untouched. *** #### From browsing to progression **After setup, browsing continues normally. Progress is generated passively during everyday activity, for example:** * typing in text fields or search bars * clicking, scrolling, and navigating pages * using web apps No distinction is made between websites or interaction contexts. *** #### From activity to energy **While the extension is active:** * activity signals are detected (typing, clicks, basic interaction) * signals are aggregated in real time * energy is generated based on the Peptypes rules > **Only the presence of activity is counted. Input content is never analyzed or collected.** *** #### Privacy and data handling **Peptype does not collect or store browsing content:** * **no text is recorded** * **no messages are saved** * **no form data is collected** * **no page content is read** Only abstract activity events are used to power gameplay mechanics. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://peptype.gitbook.io/peptype/features/data-transmission.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.