Privacy

DBA Journey provides database administration, diagnosis, documentation, migration, and specialized support services. In that context we may receive contact details, technical environment information, performance evidence, metadata, logs, execution plans, schema structures, or limited samples required to complete the agreed scope.

Processing principles

We work with least access, confidentiality, and limited purpose. Client information is processed only to respond to requests, prepare proposals, deliver contracted services, document findings, and keep reasonable technical evidence of the work performed.

We do not sell personal data or client technical information. We do not use client data, tickets, evidence, schemas, SQL queries, logs, or business content to train models. When external support or third-party tools are required, we aim to use minimal, pseudonymized, or anonymized data whenever the technical objective allows it.

Security and access

Technical information is handled in workspaces separated by client or project. Access is limited to the assigned DBA team and reviewed according to the scope. When a service requires access to client environments, we recommend delegated credentials, least-privilege permissions, controlled windows, and activity logs where available.

Retention and closure

At service closure, deliverables are provided to the client and technical evidence is deleted, returned, or retained for a limited period according to the scope and applicable contractual, accounting, or legal obligations. Unless otherwise agreed, operational service information is kept only as long as needed for reasonable follow-up support and traceability.

Incidents and rights

If we identify an incident that may affect client information under our control, we will notify the primary contact without undue delay with available information, actions taken, and recommendations. The client may request access, correction, or deletion of contact data by writing to [email protected].

The form collects the information needed to respond to the request: name, email, company, engine, requested service, and message.