APPS INTELLECT TRUST CENTER

Data protection

Principles for protecting information handled in connection with Apps Intellect products and services.

Publication status: Draft / pending verification. This page describes the intended policy and evidence topics. It does not assert that every listed control is currently implemented, tested or independently certified. Service-specific details will be published after review.

Purpose and scope

This section describes the data-protection practices Apps Intellect intends to govern across its software products, supporting services, development and hosting environments. The applicable requirements must be determined for each product, customer engagement, deployment model and data flow.

Data lifecycle

1. Identify

Identify information assets, data owners, data subjects where relevant, systems, integrations and processing purposes.

2. Classify

Classify information by sensitivity and business impact, including customer-confidential, personal, operational, financial and public information where applicable.

3. Protect

Define access, transfer, storage, logging, backup and supplier safeguards proportionate to classification and risk.

4. Retain or dispose

Set documented retention periods and secure disposal methods, subject to contract, legal obligations and preservation requirements.

Data minimisation and purpose limitation

Products and integrations should collect and use only information needed for documented service purposes. New data fields, integrations, analytics uses or secondary purposes should be assessed before introduction. Customer instructions and contractual restrictions take precedence where applicable.

Ownership and accountability

Each in-scope information asset should have an identified business owner. Product and engineering teams should document relevant data flows, access paths, storage locations, suppliers and deletion dependencies. Responsibility for determining the lawful basis and purposes of processing must be assigned according to the actual relationship and contract.

Customer and operational data

Depending on the service and customer configuration, information may include account and contact details, application records, operational or scheduling information, financial or maintenance-related records, support communications and technical logs. This is an illustrative list, not a statement that every product collects or stores every category.

Evidence maintained

  • Information asset and data inventory
  • Data-flow and integration diagrams
  • Classification and handling standard
  • Retention schedule and disposal records
  • Supplier and subprocessor register
  • Access reviews and relevant security test records

Current publication status

Product-specific inventories, storage locations, retention periods and technical safeguards remain subject to verification. This page does not claim that every described practice is implemented across every environment.