Peekaboard Privacy Policy
Hot Blood (핫블러드, the “Operator”) runs the Peekaboard apps (the adult app, the kids app “Peekaboard Kids” and the Android TV app; together the “Service”) and handles your personal information as described below, in line with the Personal Information Protection Act of the Republic of Korea. The kids app has not been released yet; this policy will apply to it when it is.
Effective date: November 4, 2026
1. Information we process and why
| Category | Items | Purpose | How it is collected |
|---|---|---|---|
| Account | Apple or Google account identifier, email address (if the provider shares it), name (if the provider shares it), sign-in time | Identifying members, sign-in, account deletion | Sign in with Apple or Google |
| Space | Space name, time zone, subscription status | Running the shared board | Entered by users |
| People | Display name or nickname, color, emoji, whether the person is under 14, linked account | Showing each person’s schedule on the board | Entered by admins |
| Events and to-dos | Title, date, time and duration, repetition, people involved, routines and weekly plans, check records (who and when) | Showing events and to-dos, keeping track of progress | Entered by users |
| Guardian consent records | Consenting account, time of consent, wording version, consent method | Confirming legal guardian consent for processing information about children under 14 | Consent screen |
| External calendar — private address | Private calendar address (ICS); time and title of events fetched from it (titles are not stored if “busy only” is selected) | Showing events from another calendar on the board | Entered by users; fetched periodically by the server |
| External calendar — calendars on this device (iCloud, etc.) | Time and title of events in the device calendars you choose (titles are not sent from the device if “busy only” is selected); a random value that identifies the device. The list of chosen calendars is stored only on the device | Showing the connected person’s events on the board | You allow calendar access on the device; the device sends them when the app opens on it |
| External calendar — Google and Microsoft accounts (turned off in the first release; applies once turned on) | Read-only access token issued by the provider; an account marker that prevents connecting the same account twice (the primary calendar name for Google; a transformed value of the organization and user identifiers for Microsoft, with the original values not stored); time and title of primary calendar events (titles are not stored if “busy only” is selected or the event is marked “private” or similar). Event descriptions, locations, attendees, attachments, mail and contacts are not fetched | Showing the connected person’s events on the board | You allow it on the provider’s consent screen; fetched periodically by the server |
| Connected devices | Anonymous device identifier, device type (TV, tablet, kids app), time of connection | Connecting and disconnecting boards and the kids app | Generated automatically during connection |
| Push notifications (adult app, if turned on) | Firebase installation identifier, device type, app display language, notification settings (spaces and times), the last day the app was opened | Event change and summary notifications, service announcements | Generated automatically when notifications are turned on |
| Terms agreements and received notifications | Agreed terms, version and time; title and body of notifications sent by the Operator; read marks | Confirming agreement to terms, in-app notification box and read marks for announcements | Consent screen; generated automatically during use |
| Operations records | Target identifier, operator, reason and time when an operator looks up, suspends, deletes or sends to a member or space | Accountability for operations, responding to abuse | Generated automatically during operations |
| Subscription (not sold in the first release; applies once sales begin) | Subscription product; purchase, renewal and cancellation status; store transaction identifier | Providing paid features, managing subscriptions | App Store, Google Play, RevenueCat |
| Automatic processing | IP address, device and app information (operating system, app version), app integrity check results | Security, preventing abuse, service stability | Generated automatically during use (Firebase) |
| Reports | Reporting account; report target (a person, event or space, and the account that last wrote it); reason; note written by the user; time of report; outcome | Reviewing and acting on reports (removing content, restricting use), preventing false reports | When a user sends a report |
| Feedback | Sending account; category; text written by the user; operating system; app version; time sent; handling status | Reading and answering inquiries, improving the service | When a user sends feedback |
| Blocks | Blocked account, the other person’s display name at the time of blocking, time of blocking | Not receiving invites from a blocked account and hiding events it wrote from your screen | When a user blocks someone |
| Usage analytics and error reports (adult app only) | App usage records (screen and feature events, pseudonymous app instance identifier, approximate location derived from the IP address); crash logs (error location, device model, operating system, app version) | Improving features, fixing errors | Generated automatically during use (Firebase Analytics and Crashlytics). Advertising identifiers are not used. Not collected in the kids app or on TV boards |
- The camera is used only to read QR codes. Camera images are not stored or sent.
- Event reminders are scheduled on the device. Events changed by other people, morning and weekly summaries and service announcements are sent by the server through Firebase Cloud Messaging, and the notification text may include event titles.
- We do not use advertising or advertising identifiers (IDFA, AAID), and we do not read the device’s location (GPS and the like). Usage analytics and error reports run only in the adult app, not in the kids app or on boards.
2. Personal information of children under 14
- Registering a child under 14 as a “person” or connecting the kids app requires consent from the legal guardian. Without it, registration and connection do not go through.
- Information processed about a child: display name or nickname, color and picture, event and to-do titles, check records, and the anonymous identifier of the device connected to the kids app.
- The kids app has no sign-in, payments, camera or external links.
- Guardians can delete a child’s information or disconnect the kids app at any time from the manage screen.
3. Retention and deletion
| Information | Retention |
|---|---|
| Account and the information it created | Until the account is deleted, then destroyed without delay |
| People, events and check records | Until an admin deletes them or the space is destroyed |
| Guardian consent records | Until that person is deleted |
| External calendar addresses and fetched events | Until the connection is removed or the account or space is deleted |
| Google and Microsoft tokens and fetched events; events received from device calendars | Until the connection is removed or the person, account or space is deleted. On disconnection we also ask Google to revoke access (Microsoft offers no way to request this, so you remove the app in your Microsoft account settings). Pending connections that were not finished are deleted automatically after 10 minutes |
| Push device information, terms agreements, received notifications, read marks | Until the account is deleted. Push device information is deleted when notifications are turned off |
| Operations records | For the period needed for accountability of operations |
| Device connection information | Until disconnected. Pending connection information is deleted automatically after it expires |
| Subscription records | For the period set by applicable law |
| Report records | 180 days after the report, then deleted automatically. If the reporting or reported account is deleted before then, its identifier is removed from the report record |
| Feedback records | 180 days after sending, then deleted automatically. Deleted with the account if the account is deleted before then |
| Block lists | Until the user unblocks or deletes the account |
| Backups | Deleted information may remain in backups for up to 14 days before it is removed |
- Deleting an account destroys every space used only by that account and everything in it. A space with other account members is handed to another admin, and the author of records you left is changed to “Deleted account”.
- When a retention period ends or the purpose is met, the Operator deletes the information without delay. If a law requires keeping it, the Operator stores it separately for that period.
- Electronic files are erased in a way that cannot be recovered.
- The Operator reviews reports within 24 hours. Report notes are opened by the Operator only when needed to handle the report, and each opening is recorded. The other person is not told that you reported them.
4. Sharing with third parties
The Operator does not provide your personal information to third parties.
Information received from external calendars (Google, Microsoft, device calendars) is used only to show events on the board of the space the connected person belongs to. It is not used for advertising, sold, transferred to other services, or read by people. Information received from Google follows the Limited Use requirements of the Google API Services User Data Policy. What members of the same space can see is what users chose to share themselves. Requests based on law are an exception.
5. Processors and transfers outside Korea
| Recipient | Work entrusted | Country or location | Items transferred | When and how | Retention |
|---|---|---|---|---|---|
| Google LLC (Firebase, Google Cloud). Contact: https://support.google.com/policies/contact/general_privacy_form | Service servers, data storage, sign-in, backups, usage analytics, error reports | Republic of Korea (Seoul region); management systems in the United States and elsewhere | Everything in section 1 | Sent over the network during use of the Service | Until the contract ends or for the periods in section 3 |
| RevenueCat, Inc. (applies once subscription sales begin). Contact: compliance@revenuecat.com | Managing subscription status | United States | Account identifier (Firebase UID, not pseudonymized), subscription status, store transaction identifier | Sent over the network on purchase and renewal | Until the contract ends |
| Microsoft Corporation (applies once Microsoft calendar connection is turned on). Contact: https://www.microsoft.com/concern/privacy | Reading the Outlook or Microsoft 365 calendar a user connected (lookup at the user’s request) | United States and elsewhere | Read-only access token, the period to read | Sent over the network when syncing | Until the connection is removed |
| Apple Inc. (contact: https://www.apple.com/legal/privacy/contact/) and Google LLC (contact: as above) | Sign-in, in-app payments | United States and elsewhere | Information needed for sign-in and payment | When a user signs in or pays | According to each company’s policy |
- When you connect an external calendar, the server fetches it from the address you entered. The company that provides that calendar receives the server’s request. The Operator does not hand your personal information to that company.
- When you connect a Google or Microsoft account, the server calls the Google Calendar API or Microsoft Graph with the read access it received. Only that access token and the period to read are sent to the provider. Microsoft Corporation processes them in the United States and elsewhere.
- Device calendars are sent directly by the device. The Operator does not connect to Apple or other calendar providers.
- These transfers are needed to provide the Service under our contract with you, and this policy discloses them as Article 28-8 of the Personal Information Protection Act requires.
- If you do not want your information transferred outside Korea, you can choose not to use the Service or delete your account. In that case you cannot use the Service.
6. Rights of users and legal guardians
- You can view, correct and delete your information in the app at any time. You can delete your account directly in the app under “My account → Delete account”. If you cannot use the app, send a request to support@hblood.co.kr (account deletion guide).
- You can ask us to stop processing and withdraw consent.
- Legal guardians have the same rights over a child’s information.
- Requests go to support@hblood.co.kr, and we reply within 10 days.
7. Security measures
- Encryption in transit (HTTPS, TLS) and encryption of stored data (Google Cloud default encryption).
- Private external calendar addresses and Google and Microsoft access tokens are encrypted once more with a separate key and kept where the app cannot read them. Account access is limited to reading events.
- Every data request checks space membership. Operators do not view user content through operations tools either (only status and counts).
- Operations access is limited to as few people as possible, and we keep billing and unusual-usage alerts.
8. Automatic collection tools and app permissions
The app does not use cookies or advertising trackers. The adult app collects usage events and crash logs with Firebase Analytics and Crashlytics to improve features and fix errors (section 1). They are not used for advertising and are not collected in the kids app or on TV boards. Settings on a device (screen brightness, the TV “keep on” option and so on) are stored only on that device. The web pages (peeka-board.com) also use no cookies or analytics tools.
The app has no setting to turn off usage events and crash logs. If you do not want them collected, stop using the app and delete your account.
The app asks for these device permissions only when you use the feature. None is required, and you can refuse or withdraw them in your device settings and keep using the rest of the Service.
- Camera: scanning a QR code to connect a board. You can type the connection code instead.
- Calendar: bringing in the calendar on this device, only if you choose it.
- Notifications: reminders and notices.
9. Privacy officer
| Item | Value |
|---|---|
| Officer | Lee Kangho (Representative) |
| Contact | support@hblood.co.kr · +82 70-7666-9768 |
10. Remedies
You can report or get advice about privacy violations from the following Korean agencies.
- Personal Information Infringement Report Center: 118 (within Korea), privacy.kisa.or.kr
- Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
- Supreme Prosecutors’ Office: 1301 (within Korea), www.spo.go.kr
- National Police Agency: 182 (within Korea), ecrm.police.go.kr
11. Changes
If we change this policy, we will announce it in the app and on peeka-board.com 7 days before it takes effect (30 days for changes unfavorable to users).