Pickey
PRIVACY

Privacy Policy

Pickey processes personal information only as needed to run the service. This policy covers login, comments, notices, user-created content, and advertising on the website and Android app.

Account and personal data deletion

1. Information we collect

  • Social login data: provider name and the provider’s account identifier
  • Information you enter while using the service: comments, notice comments, and user-created game content (title, description, image or image URL, and item data)
  • When you use the user-game Open API: token identifier, token hash, and issued, revoked, and last-used times
  • Guest comments: nickname, comment text, and a password used to delete the comment
  • Cookies, coarse connection country codes, access logs, service-use logs, restriction logs, and masked connection IPs may be created and collected automatically while you use the service.
  • Drafts, recently entered nicknames, and notice-read status may be stored in your browser when needed to use the service.
  • Usage analytics events such as page paths and button clicks

2. How we use the information

  • Identifying members, keeping you signed in, protecting accounts, and managing API tokens
  • Providing comments, notice comments, and user-game create/edit/submit features, and enforcing operating policies
  • Managing comments, reducing spam, and confirming the author when a comment is deleted
  • Saving drafts, restoring a recently used nickname, and showing that a notice has been read
  • Temporarily hiding comments or user games after repeated reports, then deleting or restricting them after staff review
  • Checking play-record integrity, detecting abnormal scores, and analyzing repeated abuse
  • Showing data-based games such as coins or stocks for entertainment, and sending service notices
  • Responding to outages, blocking abusive traffic, and improving service quality

3. Retention and deletion

  • Account data: closing your account disables sign-in and changes the account nickname. You may ask the operating team to delete remaining personal data, including social sign-in connection information. After verifying your identity and the scope of the request, we reply with the result. If any data must be retained separately, we explain the items, reasons and retention period.
  • Comments, notice comments, and user-game data: handled based on your deletion request, operating policy, and any legal retention duty
  • Report data: content may be hidden first when reports accumulate, then deleted or restored after staff review
  • Access and security logs: kept only as needed for security and stability, then deleted
  • Drafts, recent nicknames, and notice-read status stored in the browser can be deleted by you or by clearing browser data

Electronic files are deleted so they cannot be recovered. Printed copies are shredded or incinerated.

4. Sharing and processors

  • Pickey does not sell personal information for monetary consideration and does not disclose it to third parties unless permitted or required by law.
  • Data transfers involved in personalized advertising may be treated as a 'sale' or 'sharing' of personal information under some U.S. state laws.
  • We may use infrastructure providers to run the service. If they process personal information, we notify and manage that as required by law.
  • Some features such as comments use Cloudflare Turnstile to reduce abuse. Cloudflare’s privacy policy and terms may apply.
  • We use Google Analytics and Firebase Analytics to understand usage and quality.
  • When ads are shown, Google AdSense or Kakao AdFit scripts may run. Each platform’s policy governs that processing.
  • The Android app uses Google AdMob. Google may receive connection addresses and inferred approximate locations, app and ad usage, performance data, and device identifiers such as advertising IDs to deliver and measure advertising, improve quality, and prevent fraud.
  • The Android app uses Google's User Messaging Platform (UMP) to manage advertising consent and privacy choices. Google's privacy policy explains its data practices: https://policies.google.com/privacy.

5. Cookies and local storage

  • Pickey may use cookies or storage to keep you signed in, make the service easier to use, save drafts, and restore recent input.
  • Some notice-read status and in-game state may be stored in your browser.
  • Visitors in the European Economic Area, the United Kingdom, and Switzerland may see Google's consent message and can consent, decline, or manage options.
  • You can refuse or delete cookies in your browser settings.
  • If you refuse cookies, some signed-in features may not work.

6. Your rights

  • You may request access, correction, deletion, restriction of processing, or withdrawal of consent, including log-out and account deletion. Please send requests through the contact channel below.
  • Visitors in the European Economic Area, the United Kingdom, and Switzerland can manage choices by purpose in the consent message shown on the site and may request withdrawal through the contact channel below.
  • Where applicable under U.S. state law, you may request access, correction, or deletion and opt out of the sale or sharing of personal information or its use for targeted advertising. Use the 'Do Not Sell or Share My Personal Information' link at the bottom of the site or contact us below.
  • We do not discriminate against you for exercising privacy rights. We may request the minimum information needed to verify a request.
  • The Android app shows privacy messages according to applicable regions and settings. Where privacy options apply, you can revisit your choices through '광고 개인정보 설정' (Ad privacy settings) in the app menu. You can also reset or delete your advertising ID in Android settings.

7. How we protect information

  • HTTPS encryption in transit
  • Access control and protection of authentication data
  • Monitoring access logs for unusual activity

8. Contact

  • Privacy contact: Pickey operations team
  • Email [email protected]
  • Send privacy questions and access, correction, or deletion requests to that address.
  • Effective date: 2026.10.15

Bingo creation and participation records

  • We store bingo titles, descriptions, prompts and creator accounts. Creators choose link-only or listed visibility. Responses remain attached to the prompt version they answered.
  • We save O, triangle, X, unanswered cells, completed lines and save times with your account or browser/app visit record. Unsent responses and unfinished drafts may be stored on your device.
  • Opening a board after signing in on the same browser or app may link its guest responses to your account. Account closure also deletes guest responses identified by the current visit record. We cannot identify guest responses on other devices or after the visit record is cleared from your account alone.
  • Making your record public is your choice and off by default. A public record can be read by anyone with its link. Saved answers, including partial results, are automatically included in anonymous per-version statistics that show the O/triangle/X rates for each item and completed lines. Records saved without opting in before the October 2026 update, and records saved in the Android app without turning statistics on, stay excluded (participations started on the new web screen with the updated notice are included). Statistics appear from a single record, so with few participants individual answers may be inferred from the statistics. Records saved with statistics turned on before the update or through an older web/app screen that still promises a 20-record minimum are still counted only once at least 20 records are included for that board version, as promised then. Records are not a count of unique people across devices. The bingo list shows a board's participation count and popularity labels only once at least 20 included participants exist.
  • Turning off sharing removes your record from its public link; deleting your record removes it from both the public link and statistics. To leave statistics, delete your record or contact [email protected]. Pickey cannot recall images downloaded or shared elsewhere.
  • If you keep the option to show your picks on (the default) when commenting on a bingo board, your saved O/triangle/X board and completed-line count at that moment appear with the comment, visible to anyone who can view the board. This is separate from record sharing; turn it off to post the comment alone. The board shown stays as it was when you posted even if you later change your answers or delete your record, and is no longer shown once you delete the comment. Closing your account clears the boards on comments written with that account and on comments written in the browser you close it from; delete guest comments written in other browsers or on other devices individually from there. The board you show is also published as an image (only the board title, cell text, O/triangle/X marks and completed lines, never your nickname or comment), and the same answers always use the same image. Once the comment is deleted or hidden, or the board is cleared when you close your account, the image stops opening, but copies already opened can stay in browser and network caches for up to an hour, and the image keeps opening while another comment shows the same board. Signed-in accounts with a verified CHZZK channel can also turn on 'Show my verified CHZZK channel' when commenting (on by default while a verified channel is connected); the verified channel name and a link to the channel then appear with the comment as a 'CHZZK verified' badge. The badge is checked against the current connection each time comments are shown, so it disappears from all of that account's comments when you disconnect the channel, the verification expires (90 days) or you close your account, and it shows the channel connected at that time once you verify again.
  • Deleted participation records immediately leave public views and aggregates, then are purged after 30 days. Reports and moderation records support abuse handling and are purged after 180 days. Creator blocks remain until you unblock or close your account.
  • Account closure removes account links from bingo responses, excludes them from public views and statistics, and deletes channel links, blocks and the answer boards shown with comments written with the account or in the current browser. Created boards may remain under a deleted-author name under our existing content retention policy. Contact [email protected] to request deletion of remaining personal data.

Play video submissions and reports

  • When you submit or report a play video, we store the linked game, canonical YouTube or CHZZK URL, video title, streamer name, optional start time, and review note. For signed-in submissions, we may also link the submitting account and a connected verified streamer channel.
  • Videos submitted by an operator, the relevant game creator, or an active verified streamer may be published immediately. Other reports are stored for review. For approved videos, we publish the original URL, title, streamer name, start time, linked game, and submission time. We do not show the review note, reporter or reviewer account, report count, or review reason in public lists.
  • To distinguish duplicate reports of the same video, we store a record tied to your signed-in account or browser/app visit record and the report time. The visit cookie may remain for up to one year. Report counts affect review order only and do not publish a video automatically.
  • The relevant game creator and operators can view pending and approved videos, review notes, report counts, review reasons, and action times. Approval, rejection, hiding, and restoration are stored as moderation records.
  • Rejecting or hiding a video, or making the linked game unavailable, stops public display but does not immediately delete the video, report, or moderation records. Closing an account does not automatically delete these records or remove their account links. To request deletion of a specific video or related personal information, email [email protected] with the link and requested scope.
  • Thumbnails are loaded from YouTube or NAVER/CHZZK servers, which may receive connection addresses and browser or app information. The provider's privacy policy and terms may apply when you open the original video.

Budget results and creation drafts

  • Budget results store chosen options, the published version, total cost, optional nickname and explanation, and whether the result is public and included in statistics. An account or this browser/app's visit record identifies your results; signing in in the same environment may attach a guest result to your account.
  • Result sharing is off by default and can be changed on the result. Anyone with a public result link can view it. Editing or completing again saves a new result and preserves the earlier link's choices. You contribute at most one statistical record per version; a new save withdraws the earlier contribution and counts the new result instead. Deleting a result excludes only that result from sharing and statistics; externally shared images cannot be recalled. Published creations may remain after account closure, while personal results are subject to deletion.
  • Saved results are automatically included in anonymous per-version choice statistics (choice rate per option and average spending). Results saved without opting in before the October 2026 update, and results saved in the Android app without turning statistics on, stay excluded. Statistics appear from a single result, so with few participants an individual's choices may be inferred from the statistics. Results saved with statistics turned on before the update or through an older web/app screen that still promises a 20-record minimum are still counted only once at least 20 results are included for that version, as promised then. The list shows a game's participation count (all versions combined) and popularity labels only once at least 20 included participants exist. To leave statistics, delete the result or contact [email protected].
  • If you keep the option to show your picks on (the default) when commenting on a budget game, the option names for each row and the spending and budget of your most recently saved result appear with the comment, visible to anyone who can view the game. Result nicknames, explanations and result links are not shown, and this is separate from result sharing. Turn it off to post the comment alone. The picks shown stay as they were when you posted, and are no longer shown once you delete the comment. Closing your account clears the picks on comments written with that account and on comments written in the browser you close it from; delete guest comments written in other browsers or on other devices individually from there. The picks you show are also published as a picks image (only the game title, the photos, names and prices of the chosen options and the totals, never your nickname or comment), and the same picks always use the same image. Once the comment is deleted or hidden, or the picks are cleared when you close your account, the image stops opening, but copies already opened can stay in browser and network caches for up to an hour, and the image keeps opening while another comment shows the same picks. Signed-in accounts with a verified CHZZK channel can also turn on 'Show my verified CHZZK channel' when commenting (on by default while a verified channel is connected); the verified channel name and a link to the channel then appear with the comment as a 'CHZZK verified' badge. The badge is checked against the current connection each time comments are shown, so it disappears from all of that account's comments when you disconnect the channel, the verification expires (90 days) or you close your account, and it shows the channel connected at that time once you verify again.
  • Draft input may be stored in your browser.

MBTI guessing game

  • This game does not keep personal play history for signed-in accounts. Its progress is not linked to your account, nickname or service visit record.
  • To resume play, your browser receives a random temporary cookie. The server stores a transformed temporary ownership check, your answers and progress for up to two hours. Page scripts cannot read this cookie; starting a new game renews its lifetime. A game reference is also kept in temporary tab storage to resume after a refresh. Closing the tab or quitting the game removes that tab's resume reference.
  • Per-person answer rates and average strokes, and per-set play counts and average strokes, remain as aggregate totals without identifying players. A temporary record of already counted items prevents repeated play in the same browser from counting again; it expires two hours after the last participation. Aggregate totals may remain after the session expires.
  • Featured people's types use verified sources and dates of their own public disclosures. This is not a personality assessment or a guarantee of their current type. Sources and dates appear when answers are revealed. Send corrections to [email protected]. Photos retain author, license and original-source links.

Three Kingdoms life saves and play analytics

  • Sharing a result card compresses its displayed character, birth, ending, resources and major events into the URL. Cards are not stored in a separate database; anyone with the link can view them. Compression is not encryption, and clearing local records cannot revoke links or images already shared. Where image sharing is unsupported, you can save the image and copy the link instead.
  • Progress and endings are saved locally in separate guest and account browser storage. Only pressing Cloud Save while signed in sends an account-linked checkpoint for continuing on another device; seasonal actions are not automatically uploaded.
  • One private checkpoint per account contains a compressed code with character, attributes, resources, choices, random state, up to 160 recent chronicle entries and 10 ending summaries, plus account ID, revision and save time. The code is limited to 16 KiB; saving again replaces the previous checkpoint.
  • Cloud data is retained for continued play until account closure or fulfillment of a personal data deletion request. Clearing browser data removes local records but not the cloud checkpoint. Loading preserves the previous life in a separate local backup. Clear browser data after using a shared device.
  • New-life start, completion and reached age-bracket records use existing service analytics. A random play observation ID, start/completion phase, the age bracket reached (one of 1, 6, 12, 15, 20, 30, 40, 50, 60 or 70, used to see where players stop before finishing) and fixed game path are sent. Records are linked to the visitor cookie identifier and, when signed in, your account, and stored with the event time, country code when available, normalized path and acquisition information. A minimal summary also includes the public character category, birth type, career, game age, progress mode, completion category and unification status; generated names, choices, attributes and individual ending text are not sent, and observations are not server-verified play counts.