Help Center

Privacy terms for trusted cultural exchange.

This launch notice explains what saii collects, why it is used, and which account controls are available before final Korean counsel review.

Current required consents

Version 2026-06-12

Sensitive data processing

Version 2026-06-12

Data we collect

Account identity, social-login references, verified phone status, profile details, interests, posts, comments, chat metadata, profile-view analytics, reports, blocks, device registrations, consent records, safety moderation/throttle metadata, identity-verification metadata, and subscription entitlement state.

Profile-view analytics

Public profile opens are stored as one aggregate row per viewer and viewed profile, including view count and last-viewed time. Account export includes profile views you made and profile views received.

Sensitive-data processing

Identity verification is vendor-SDK based. Rails stores verification metadata only, rejects direct document uploads, and keeps production KYC provider work behind the post-review webhook boundary.

Provider and billing posture

Premium access, calling, push delivery, and identity checks use provider boundaries so sensitive data and account controls stay separated.

Your controls

Export my data Request account deletion

The Settings & Privacy panel also manages notification categories, discovery visibility, the personal block list, and consent re-acceptance.

PIPA counsel review

This page is the product-facing implementation surface for launch review. Final legal copy, retention periods, deletion wording, and Korean PIPA consent language still need Korean counsel approval before public launch.