Privacy Policy update notice
Announced: 29 October 2026 · Effective: 29 October 2026
The policy now explains campaign-limited browser hashes, playback and linking records used to detect duplicate entries in the voice-message card campaign, and destruction after completion of the actual draw is confirmed.
What changed
- We keep a hash of a random browser key limited to the campaign and playback events. When sign-in, installation or an actual call is verified, these are linked to existing account and installation attribution. Raw browser keys are not stored on the server.
- Hashes and linking/playback records are destroyed after completion of the actual draw is confirmed; if the draw is delayed, they are kept while needed to verify entries. The local raw key is deleted on the next card visit when the server confirms post-draw deletion. Records linked to an account are also deleted when the account is permanently deleted.
- We cannot guarantee that different browsers or private windows belong to the same person. This policy is published together with the brief notice on the card playback screen.
Sections updated
| Document | Section | Change |
|---|
| All six language versions of the Privacy Policy | Section 1 | Campaign-limited browser hashes, playback/linking records and destruction |
Current and previous versions
Contact: sudacall@creamhouse.net · +82-2-508-2712
한국어