ZeniGraph Analytics is a fully offline desktop application. Customer datasets are processed locally and are never transmitted to ZeniGraph, a cloud service, or a third-party processor.
During analysis, dataset contents and derived analytical caches exist only in volatile application memory. ZeniGraph Analytics does not write customer datasets, analytical caches, logs containing customer data, or telemetry containing customer data to disk. When the dataset is replaced or the application session ends, that in-memory analytical state is discarded.
ZeniGraph does not receive your analytical data
ZeniGraph has no technical access to the datasets analyzed with the software. We do not host them, receive them, back them up, synchronize them, inspect them, or use them for product analytics, model training, advertising, or any other secondary purpose.
Roles under data protection law
Because ZeniGraph does not receive or process customer dataset contents on behalf of the customer, ZeniGraph is generally not acting as a data processor in relation to those datasets. The customer remains responsible for determining the lawful basis, purpose, and scope of any personal data processed locally using the software.
Where applicable, terms such as “controller”, “processor”, “personal data”, “data subject”, and “processing” shall have the meanings given to them under applicable data protection legislation, including the GDPR.
Customer data
- ZeniGraph does not obtain ownership of customer datasets.
- Customer data remains under the customer’s control at all times.
- ZeniGraph does not sell customer data, use it for advertising, profile individuals, or reuse dataset contents for any secondary purpose.
Offline processing
- ZeniGraph Analytics is designed to function without requiring cloud connectivity.
- Analytical processing is performed locally on the customer’s workstation.
- The software does not require customer datasets to be sent to ZeniGraph servers or third-party processing infrastructure.
Local memory processing
During an active session, dataset contents may be held temporarily in system memory for analytical processing. When the session ends, the application is closed, or the dataset is replaced, the dataset is no longer retained by ZeniGraph Analytics as active analytical state.
ZeniGraph Analytics does not intentionally create persistent copies of customer datasets as part of normal operation.
Licensing and activation
Licensing or activation mechanisms may process technical device-identification information required to validate a license. Such licensing information is separate from customer analytical datasets and is not used to access or reconstruct dataset contents.
Support
ZeniGraph does not require access to customer datasets in order to provide standard product support. If a customer voluntarily provides diagnostic information, screenshots, sample data, or files for support purposes, that information will be handled only for the purpose for which it was provided and subject to any applicable confidentiality terms.
Security responsibilities
Because customer datasets remain on customer-controlled systems, the customer is responsible for securing the workstation, operating system, storage environment, user access, and any source files used with ZeniGraph Analytics.
ZeniGraph is responsible for the security of the software it provides and for the handling of any information that is voluntarily submitted to ZeniGraph through sales, licensing, support, or other direct communication channels.
Subprocessors
ZeniGraph does not use subprocessors to process customer analytical datasets because those datasets are not transmitted to or processed on ZeniGraph infrastructure.
Third-party providers may still be used for ordinary business operations such as email, website hosting, payment processing, or support communications. These services are separate from the local analytical processing performed by ZeniGraph Analytics.
Data deletion
Because ZeniGraph does not store customer analytical datasets on its own systems, there is normally no customer dataset for ZeniGraph to delete.
Customers retain control over their own source files and local environments.
Data subject requests
ZeniGraph does not have access to the customer’s local analytical dataset and therefore cannot independently identify, retrieve, modify, or delete records relating to data subjects contained in that dataset.
Any such requests must be handled by the customer as controller of the underlying data.
International transfers
Customer analytical datasets are not transferred to ZeniGraph as part of normal use of the software.
Accordingly, use of ZeniGraph Analytics does not by itself require cross-border transfer of customer dataset contents to ZeniGraph infrastructure.