동의 및 데이터 역할 프레임워크
본 문서는 검토를 위해 준비된 버전 1.0 초안입니다. 당사의 검증된 기술 및 데이터 보호 관행을 반영하나 경영진 및 법률 최종 승인을 대기 중입니다. 일부 조항은 여전히 경영진 또는 법률 검토 중인 항목을 포함하므로 최종 정책으로 신뢰해서는 안 됩니다.
This framework explains how EDUMOVIA collects separate, purpose-specific consents, how data-controller and processor roles are assigned, and how acceptances are versioned and recorded.
시행일: 2026년 8월 31일 · 버전 v1.0
Separate, purpose-specific consents
EDUMOVIA does not bundle unrelated permissions into a single checkbox. Where consent or acceptance is needed we collect it separately: (a) acceptance of the Terms of Service — a mandatory contractual step; (b) acknowledgement of the applicable privacy notice; (c) explicit consent — only where the applicable law requires it for a specific purpose; (d) international-transfer consent — only where the chosen transfer mechanism requires it; (e) marketing communications — always a separate, optional choice, unchecked by default and withdrawable at any time; (f) cookies and analytics — managed through the cookie banner according to the visitor’s jurisdiction.
Data-controller and processor roles
Roles depend on the scenario and are confirmed per relationship [LEGAL REVIEW REQUIRED]. Typically: a student provides data to a tenant, who acts as controller; EDUMOVIA acts as processor for the tenant under the Data Processing Addendum, or as an independent controller for its own website, billing and security operations; a destination university that receives an application acts as an independent controller; AI and infrastructure providers act as processors / sub-processors. The Data Role Matrix in the management pack sets this out in full.
Consent ledger
When a person accepts a document or grants/withdraws a consent, the event is recorded in the platform’s existing audit system with the document, version, jurisdiction, language, timestamp and acceptance type. Records are tenant-scoped and are not visible across tenants. We record what is needed for accountability without logging unnecessary personal data.
Versioning and re-consent
Each document carries a version identifier (for example GLOBAL-PRIVACY/v1.0). A material change increases the version and triggers a re-acceptance policy for affected users. Any mandatory re-consent campaign for existing customers is a [MANAGEMENT GO REQUIRED] action and is not performed automatically.
본문에 표시된 일부 항목(감독 기관 연락처, 데이터 보호/개인정보 보호책임자, 관할권별 법적 사항)은 EDUMOVIA 경영진과 법률 자문이 확정 중이며 향후 개정판에서 업데이트됩니다.
법률 및 데이터 보호 관행에 대한 문의는 연락 주세요.
문의하기