Privacy Policy
Policy version: privacy-2026-09-10 · Effective date: 2026-09-10
This policy explains how SCENEDAM collects, uses, shares, protects, retains, and deletes information when you use the app, website, support channel, and related services.
Information We Collect And How We Receive It
- Account and sign-in data: the Google, Apple, Kakao, or NAVER sign-in provider you choose, provider account identifier, display name, email address when the provider supplies it, policy-consent version, and account timestamps.
- Apple account-status notifications: if you use Sign in with Apple, we process a hash of each account-deletion, consent-revocation, or email-forwarding event identifier; bounded event type, time, and outcome; a purpose-limited HMAC of the Apple account identifier; and terminal deletion state to prevent replay and preserve event ordering. The notification ledger does not retain the raw signed notification or raw Apple account identifier.
- Account-deletion verification information: we encrypt the authentication information received after you sign in again with Apple, Kakao, or NAVER. The deletion confirmation is valid for ten minutes by default; expired information is deleted progressively afterward. For Kakao, we also retain the member identifier and the time of an attempted disconnection. The provider authentication information is not sent to the app in its original form.
- NAVER disconnection notifications: we use the verified member identifier to find your linked account. To prevent misuse through repeated notifications, we process the latest sign-in and disconnection times, a value derived from the verified notification signature, the notification and processing times, and the processing result. These notification records do not retain the original notification, signature, or member identifier.
- Session and device data: session identifiers, sign-in and expiry timestamps, IP address, user agent, and security events received automatically when the app or browser contacts the service.
- Activity and preferences: ratings, one-line reviews, spoiler choices, saved or watched states, recommendation preferences, hidden titles, and blocked accounts that you submit or select.
- Optional community data: a chosen public handle, display name, short bio, public taste tags, follows, review-like state, comments, and community notification read state. Like identities and relationship pairs are not displayed in aggregate review-like notifications.
- Optional push-notification data: when you grant device notification permission and enable push notifications, we process an account-linked Expo push token, device platform, app identifier and environment, notification content, and delivery status.
- Safety and support data: report categories and notes, moderation decisions, appeals, support messages, and the non-secret diagnostic details you choose to send.
- Operational data: request times, error and reliability events, and aggregate service usage needed to secure, troubleshoot, and improve the service.
Kakao supplies a consented nickname; email is stored only when supplied with consent, validity, and verification flags. NAVER may supply a nickname or name and email; its email is not treated as verified. Received fields depend on provider configuration and your choices.
We do not ask you to send passwords, OAuth codes, access or refresh tokens, or private keys to support. Sign-in and deletion credentials are processed through the authentication flow between the provider and server.
How We Use Information
We use the information above to authenticate accounts, sync personal activity, publish ratings and reviews, generate explainable recommendations, deliver push notifications you enable, operate reporting and blocking, answer support requests, investigate abuse or security incidents, maintain service reliability, enforce the terms, and comply with law.
Recommendation inputs are limited to product activity such as watch states, ratings, and explicit preferences. SCENEDAM does not use them to infer sensitive personal characteristics.
Community Information And Visibility
Community profiles are private by default. One-line reviews remain public with a generic author unless you opt in to a community profile. When enabled, your chosen handle, display name, bio, public taste tags, follower and following counts, selected visible reviews, and visible comments may be displayed. Ratings, library state, private taste analysis, like identities, email addresses, OAuth provider identifiers, IP addresses, user agents, private watch states, preferences, block relationships, and session data are not displayed publicly. If you disable a profile, its handle remains reserved and non-public until you reuse or deliberately replace it when re-enabling the profile, or delete the account.
Community Controls
Disabling a public profile removes it from profile lookup and following feeds, prevents new follows, clears follow edges in both directions, and returns reviews to a generic author presentation. It does not delete your private ratings, library, preferences, or reviews. Blocking another account immediately removes follow edges and hides each side from community profile, feed, comment, and social-context reads.
Sharing And Service Providers
We share information only as needed with the Google, Apple, Kakao, or NAVER sign-in providers you choose, cloud hosting and database providers, the Expo push-notification provider, monitoring and support processors, and content-data providers involved in delivering the service. Before production release, we must document that each applicable provider agreement requires the same or equivalent protection required by this policy and applicable law, and that its terms match the actual processing scope. Production release remains blocked until that review is complete. We may also disclose necessary information to respond to lawful requests, protect users, or investigate fraud, abuse, or security threats. SCENEDAM does not sell personal information or share it for third-party behavioral advertising.
Security
We use HTTPS in transit, restricted production access, short-lived authentication proofs for destructive actions, session revocation, least-privilege operational access, secret separation, and logging controls. No online system is completely secure, so please report suspected account or privacy issues through the support channel without sending credentials or tokens.
Retention And Deletion
Account data, ratings, reviews, watch states, and preferences remain while your account is active or until you edit or delete them. Session, operational, support, and moderation records remain only as long as needed to authenticate users, resolve requests, secure the service, prevent repeated abuse, meet legal obligations, or resolve an active dispute, after which they are deleted or de-identified.
Popular-search aggregation events contain only the query and occurrence time without account, IP, or device identifiers and are automatically deleted after 90 days. When a search returns no result and requests catalog enrichment, the stored query and filters likewise contain no account, IP, or device identifiers and are automatically deleted after no more than 30 days. Active push-device registrations remain until you disable push or delete the account. Completed, failed, or cancelled push-notification delivery records are automatically deleted after 30 days. Pending delivery records are retained until they reach a terminal state so that notification attempts are not silently lost.
Apple server-notification event-identifier hashes and terminal account-deletion state that excludes the raw account identifier are retained without a time limit to prevent replay of captured destructive events and conflicts between new accounts and old notifications. This ledger does not store the raw signed notification, raw Apple account identifier, or relay email.
To delete an account using Apple, Kakao, or NAVER, first sign in again with the same linked account to verify your identity. We then revoke the provider sign-in permission or disconnect the account. For Kakao, we request disconnection using the verified member identifier; for NAVER, we request revocation of sign-in permission. Once this succeeds, we erase the encrypted deletion-verification information and related identifier before deleting your SCENEDAM account. A failed request can be retried while its verification information remains valid; expired information is deleted progressively afterward.
A NAVER disconnection notification does not delete your SCENEDAM account. A valid current notification signs you out and disables the NAVER connection while preserving other sign-in connections and app data. The disabled connection record is removed on account deletion and can be reconnected by a later sign-in. To prevent repeated-notification misuse, the signature verification values, notification and processing times, and results currently have no automatic expiry and remain after account deletion. Their legal basis, access controls, and review schedule must be finalized before production release.
You can permanently delete your account in the app or start a verified request on the account deletion page. Successful deletion immediately revokes sessions, removes private account data, the community profile, follow edges, likes, notifications, and authored comment text; it also hides reviews, removes review text, and removes user-authored report notes. A minimal non-identifying comment, report, or moderation audit shell may remain when needed for safety and abuse prevention; deleted actor identifiers and user-authored text are not retained in that shell.
Your Choices And Requests
You can edit or delete ratings, reviews, public-profile fields, and comments; disable your public profile; unfollow profiles; change watch states and preferences; manage blocked accounts, withdraw from further use by deleting your account, and request access, correction, deletion, or information about privacy handling through support. Where consent is the legal basis, you may withdraw it for future processing; withdrawal does not make earlier lawful processing invalid.
Policy Changes
Material changes will receive a new version and effective date. When required, SCENEDAM will provide notice in the service and request renewed acceptance before affected processing or contributions continue.