CLAPLOG PRIVACY
This policy explains how ClapLog handles information in the iOS, iPadOS and macOS apps, the claplog.app web portal, and the connected project services.
Effective: September 1, 2026 · 시행일: 2026년 9월 1일
Everglow Studio operates ClapLog, a film-set workflow product. “ClapLog,” “we,” and “us” refer to that product operation. This statement identifies the current operator and does not describe a separate corporate legal entity.
Everglow Studio는 영화 촬영 현장용 워크플로 제품인 ClapLog을 운영합니다. 이 문구는 현재 운영 주체를 나타내며 별도의 법인 지위를 의미하지 않습니다.
Google 계정 기본정보, 프로젝트·크루 구성, 카메라·사운드·스크립티 기록, 사용자가 만든 사진과 요청 시의 대략적 장면 위치, 서비스 보안을 위한 최소 진단정보를 처리합니다.
ClapLog requests Google Sign-In identity scopes and the Google Drive drive.file scope. This lets ClapLog create and update Google Sheets files that ClapLog created or that the user explicitly opened or selected. It does not grant ClapLog general access to search or read every file in the user's Drive.
At sign-in, the app sends a Google ID token to the ClapLog Project Service. The service verifies that token and returns an opaque ClapLog session. The app does not send its Google Drive access token to the Project Service. It obtains that token on the device and uses it directly from the device to Google's Sheets and Drive APIs.
Current Google file use is limited to creating and updating Google Sheets reports and managing access to those reports. For a department report, active project members assigned to that report receive read-only Google Drive viewer permission. If membership changes, ClapLog removes only permissions whose exact permission IDs it recorded as permissions created by ClapLog. It does not remove or downgrade the file owner, inherited permissions, or permissions the user managed outside ClapLog.
Google data is used only to sign the user in, connect that person to a project role, create or update those user-directed Sheets reports, and share them with active project members. We do not sell Google user data or use it for advertising, credit or lending decisions, surveillance, or training generalized artificial-intelligence models.
ClapLog's use and transfer of information received from Google APIs will comply with theGoogle API Services User Data Policy, including its Limited Use requirements.
ClapLog은 앱이 만들었거나 사용자가 명시적으로 연 파일에만 접근하는 최소 범위인 drive.file 을 사용합니다. 서버에는 본인 확인용 ID 토큰만 보내며, Drive 액세스 토큰은 기기에서 Google로 직접 전달됩니다. 현재 Google 파일 기능은 Sheets 리포트에만 사용합니다.
We do not use personal or production information for advertising, credit or lending decisions, surveillance, or training generalized artificial-intelligence models.
Core capture records and continuity photos are stored on the device first. Camera, local network, photo-library and approximate location permissions are requested only when the related feature needs them. Receiver pairing codes and encrypted cue payloads are intended for short-lived connection use and are not stored as cloud project records.
Online log viewing and automatic backup are separate, user-visible features. Reserved or unavailable paid features do not upload project content merely because the user signs in.
Information may be visible to authorized members of the same ClapLog project according to their role. Google Sheets reports are shared as described in Section 3. We use Google for sign-in and user-directed Sheets files, Cloudflare for web/API infrastructure, and Apple for app distribution and platform services. These providers process information under their own terms and privacy commitments.
Data may be processed outside Canada. We do not disclose project content to data brokers or unrelated advertisers. We may disclose information when required by law, to protect users or the service, or as part of a business transaction subject to appropriate safeguards.
Local records remain on the device until the user removes them or removes the app, subject to device and system backups. Deleting a local project is not guaranteed to erase every related copy, continuity photo, export or archive. Google Sheets reports remain in the user-controlled Google account until the file owner or an authorized collaborator deletes them in Google.
ClapLog sessions expire within a maximum of 30 days. A daily cleanup removes expired session rows; a revoked session stops authorizing requests immediately and its row is removed at normal expiry or after 30 days from revocation, whichever comes first. Expired or revoked invitation records are removed after 30 days. Join-attempt counter windows older than 24 hours are removed by the daily cleanup.
User profiles, projects, memberships, expected-crew records and the report registry do not currently have automatic deletion. The current project delete action archives the project and blocks normal access; it does not physically erase the project. A future audited erasure workflow is required for that deletion.
To request access, correction or deletion of ClapLog-hosted data, email support@claplog.app. We may need to verify the requester's identity and authority over shared production records before acting.
We use encrypted transport, Google-signed identity tokens, opaque app sessions, hashed stored credentials, role-based authorization and bounded service logs. No security measure is infallible; users should protect device passcodes, Google accounts and invitation links and should revoke access they no longer need.
ClapLog is a professional production tool and is not directed to children under 13. We do not knowingly collect a child's personal information through a child-directed service.
Users can decline optional permissions, remove local records, control Google file sharing and request access, correction or deletion where applicable. Signing out of ClapLog does not revoke the Google access previously granted to the app. Revocation is a separate action in the user's Google Account access controls. Some features cannot operate without the data they require.
We may update this policy as features or legal requirements change. Material changes will be identified by a new effective date and, when appropriate, an in-product notice. Questions and privacy requests can be sent to support@claplog.app.