TechnoMindsSaudi digital infrastructure

Data practices

Data follows the organization, environment, resource, and request.

This is a technical summary, not a substitute for the privacy notice, DPA, or customer contract.

Tenant separation

Organization-scoped resources and row-level boundaries are enforced in the provider data model and tested for cross-tenant denial.

Credentials

Complete developer and webhook secrets are revealed once where appropriate. Secrets must not enter logs, analytics, or public support cases.

Request evidence

Durable request, operation, provider-correlation, response, retry, webhook, and final-outcome records are distinct from transient application logs.

Exports and termination

The customer console includes data-export and account-termination paths. Contractual retention and deletion terms remain governed by applicable agreements.

Environment separation

Sandbox data and credentials are not authority for production resources. Synthetic activity must not be reported as production customer activity.

Hosting location

No blanket Saudi data-residency claim is made. Hosting and subprocessor facts are stated only where verified for the deployed service.