Security & operations
SHINCHUK
How data is connected, who reviews it, and where systems operate: we agree on scope and responsibilities to fit your environment and the importance of the work.
Permissions
Configure access around each person's operational role.
Data
Agree on processing purposes, data, retention, retrieval, and deletion.
Operations
Define versions, changes, recovery, and support scope.
Operations and support
We define operating responsibility, support hours and channels, incident response, service levels, and recovery conditions. Initial response, remedial work, workarounds or recovery, and final resolution are distinguished.
Data and AI use
We define processing purposes, data categories, access, retention, deletion, subprocessors, cross-border transfers, and CONTROL management data. AI models, providers, inputs, outputs, review responsibilities, and model-specific terms are specified.
Environment and regional requirements
We agree on managed systems, deployment locations, and remote access. Permitted uses, prior approvals, regional alternative terms, and document versions are also defined.
Frequently asked questions
Can you deploy in our environment?
The agreement defines deployment and management, whether SHINCHUK cloud, your cloud, or on-premises servers. We first verify environment requirements and implementation scope.
Are AI results finalized automatically?
Human review and approval are defined according to the importance of the work. Models, data, evaluation criteria, and permitted actions are specified in the agreement.
Can we retrieve our data when the agreement ends?
At your request, retrieval access is available for 30 days after termination. The agreement defines the data, format, delivery method, subsequent deletion, and necessary retention.