What exactly occurs when a jts.push command for a "pageview" or "submit" event is executed?

The data processing will start with the same condition with which the general cookies are set: JENTIS Cookies 

The following cookies are set when JENTIS JS SDK (embed code snippet) is integrated on a website with the following conditions:

A) user actively grants consent to any installed tool in your JENTIS Data Capturing Platform

OR

B ) consent administration is turned off (you have actively turned off the link between your Consent Management Platform and JENTIS vendors)

OR

C ) a single tools vendor is configured with “JENTIS Essential Mode” and consent is actively granted/denied by the website visitor (users decision is awaited)

OR

D ) a single tools vendor is configured with “No Consent” (decision of user is not awaited)

Data Storage and Structure: Once the data is on the tracking servers, how is it stored, and what does it look like? For our internal records and potential legal inquiries, it is crucial to know the structure of the stored data, including any identifiers or personal data captured.

Generally there is no storage of traffic data (this is all data such as a page title, url visited, timestamp of a particular event, etc) by default. Traffic data is discarded the moment all tools tags were executed.

Only data persistent is the JENTIS cookie (that is living in the users device) and server-side stored key-value pair data (ie. with GA4 we will generate, based on your configuration, a client-id for GA4 and to make it consistent with GA4 this key-value pair (the key is for example the static “ga4_client_id” and the value is for example “123456789.123456789”) is stored on the servers runtime memory.