Skip to main content

Privacy

Privacy begins with the data flow.

Identify purpose, data categories, processing roles, providers, location, access, and retention for the actual service. Roles and safeguards depend on the deployment and signed terms; APPNEURAL does not act only as a processor in every context.

Our Principles

Privacy Foundation

Use these principles to define privacy requirements for a specific website, product, or engagement.

Purpose Limitation

Define the specific purpose and permitted instructions before processing data.

Data Minimization

Collect or expose only the information required for the agreed task.

Transparency

Identify processing roles, recipients, locations, and limitations for the service.

Access Control

Limit information access to authorized people and system components.

Retention Discipline

Set system-specific retention, deletion, backup, and legal-hold rules.

User Choice

Provide choices and rights where supported by the applicable service and law.

Data Practices

Questions to resolve for each data flow

No universal retention, deletion, residency, or transfer commitment is published here.

Data Collection

  • Identify the fields and data categories requested by the actual form or product.
  • Do not submit credentials, regulated records, or confidential files through a general enquiry.

Data Usage

  • Document purposes and instructions for each data flow.
  • Confirm which systems and external providers receive data before enabling a workflow.

Data Retention

  • No universal retention schedule is published.
  • Agree separate periods for enquiries, product records, uploads, logs, and backups.

Data Deletion

  • Define request handling, verification, return/export, deletion, backup expiry, and legal exceptions.
  • No standard deletion deadline is published.

Data Residency

  • Confirm storage, access, backup, and model-processing locations per deployment.
  • No selectable residency or universal transfer mechanism is claimed.

Your Rights

Privacy requests

Rights and available actions depend on the applicable law, processing role, request, and identity verification.

Access

Ask what personal data is processed and whether a copy can be provided under applicable law.

Correction

Request correction where the relevant right applies.

Deletion

Request deletion where applicable, subject to identity checks and legal exceptions.

Portability

Ask whether portability applies to the specific processing and format.

Restriction or objection

Requests depend on the applicable law, processing purpose, and circumstances.

Rights depend on applicable law, identity verification, and the processing context. To make an initial request, use the general contact form. No dedicated privacy-request inbox or completion deadline is represented here.

Cross-Border Transfers

Confirm where data is stored, accessed, backed up, and shared with providers. Applicable transfer mechanisms and contractual safeguards must be assessed for the actual parties and route; no universal SCC or adequacy arrangement is claimed here.

  • Identify transfer locations
  • Confirm provider terms
  • Agree applicable legal mechanism
  • Verify regional deployment capability

Consent Management

Consent requirements depend on the data use, jurisdiction, and actual website/product configuration. Review the published cookie notice and verify that any non-essential tracking respects applicable consent requirements before enabling it.

  • Review essential and optional storage
  • Verify consent before optional tracking
  • Keep notices aligned to deployed integrations
  • Document applicable user choices

Enterprise Intelligence

Have a privacy question?

Describe the service or website, the request, and relevant data categories through the general enquiry form. Do not attach sensitive personal records; response timing and applicable rights depend on the request.

Scope and availability confirmed individually · Written terms define the engagement