Privacy Policy
Effective: October 27, 2026 · Last updated: November 3, 2026
언제돼? (Pickatime, the “Service”) is an independently operated service that helps friends choose a meeting date by voting on lunch and dinner times with stickers. This policy explains what information the Service processes, why it processes that information, and how you can access or request deletion of it.
- Meeting nicknames and sticker votes are visible to people who have the meeting link.
- Imported personal calendar events are displayed only on your current page. They are not stored in the Service database or shared with other participants.
- Connecting a calendar is optional. You can vote manually without connecting one.
1. Information We Process and Why
| Category | Information | Purpose |
|---|---|---|
| Kakao login | The account identifier and profile nickname supplied by Kakao, and signed session information used to maintain your login | Recognizing your account, maintaining your login, and linking your nickname and joined meetings to your account |
| Meetings and votes | Meeting title, candidate period, expected participant count, creation time, participant account identifiers and nicknames, joining time, sticker selections by date and lunch/dinner slot, and joined meeting lists | Creating, joining and sharing meetings; saving votes and calculating rankings; importing your own votes from another meeting; and operational statistics |
| Google Calendar connection (optional) | Calendar identifiers, names and time zones; event titles, start/end times, all-day status and display-related information such as cancellation and attendance responses for the selected calendars within the meeting period; and temporary access tokens | Displaying your personal events alongside the voting calendar |
| Calendar files (optional) | Event titles, times, time zones, recurrence rules/exceptions, all-day status and other event display information in .ics files you select | Reading the files in your browser and displaying your personal events |
| Access and usage information | Access times; technical information such as IP address, browser and device information exchanged during communications; cookies/device identifiers; page views; and actions such as creating meetings, voting and sharing | Providing and troubleshooting the Service and analyzing usage through Google Analytics |
| Support inquiries | Your sender email address, inquiry content and the minimum information needed to verify your identity | Answering inquiries and handling requests to access, correct or delete information |
We do not collect your Kakao or Google account password. Login and calendar authorization take place on the respective provider’s screens. You can use the basic meeting voting features without granting calendar access.
2. Personal Calendars and Google User Data
- When you connect Google Calendar, we use
calendar.calendarlist.readonlyandcalendar.events.readonlyto read your calendar list and events from the calendars you select within the meeting period. We do not create, modify or delete Google Calendar events. - Your browser requests events directly from Google APIs. We do not store imported events or Google access tokens on our servers, in Firebase, or in localStorage. .ics files are also read in your browser and are not uploaded to our servers.
- Imported events are used only in the date cells and event details on your own screen. Event titles and content and Google access tokens are not sent to other meeting participants, sharing messages or Google Analytics. Importing events does not automatically change your sticker votes.
- The Service does not provide its operator with a feature for viewing your imported calendar events. Google user data is not used for advertising, sale, credit assessments, or training general-purpose AI or machine-learning models.
- 언제돼? (Pickatime)’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The Service currently does not provide a feature for transferring imported calendar data to other apps.
3. Information Shared Within a Meeting
Anyone with a meeting link can view its title, candidate period, participant count, nicknames, sticker selections and aggregated results. The link can be forwarded to others. When you use a sharing feature, the meeting URL and an invitation or voting status/leading dates are passed to the app you select. Personal calendar events are not included in sharing messages.
The operator can view operational statistics through an administrator-only page, including meeting participation and voting statistics and counts of distinct accounts. Calendar content is not included in these statistics.
4. External Providers and International Processing
The Service uses the providers below. They may access information when processing requests or process technical information under their own privacy policies. Information travels over the internet and may be processed in infrastructure outside your country.
| Provider | Role and information processed | Location and policy |
|---|---|---|
| Kakao | Login and KakaoTalk sharing initiated by you | Subject to Kakao’s operating locations and privacy policy. |
| Google LLC — Firebase | Account authentication, and storage and synchronization of account profiles, joined meeting history, meetings and votes | The current Realtime Database region is Singapore (asia-southeast1). Authentication, operational and support processing use Google infrastructure as described in Firebase’s privacy information. |
| Google LLC — Google Calendar and authorization | Calendar reading and authorization permitted by you | Subject to Google’s global infrastructure and privacy policy. |
| Google LLC — Google Analytics 4 | Usage statistics including cookie identifiers, browser/device information, approximate location, page views and actions | Processed through Google’s global infrastructure. Retention and deletion depend on the Service’s GA4 settings and Google’s policies. |
| Cloudflare, Inc. | Website hosting, execution of login and administration APIs, and access/technical information needed to process requests | Processed through Cloudflare’s global infrastructure according to the Service’s configuration. See Cloudflare’s privacy policy. |
| Vercel Inc. | Redirecting legacy website addresses to the current website, and technical information from requests to those legacy addresses | Processed through global infrastructure, including the United States. See Vercel’s privacy policy. |
Requests to these providers occur when you use relevant features, such as login, saving a meeting or connecting a calendar, or when related page resources are loaded. Providers of external SDKs, fonts and static resources, including Google and Kakao, may also receive technical information needed to serve those resources. Processing duration depends on the retention criteria below and each provider’s contracts, settings and policies.
5. Cookies, Browser Storage and Analytics
- Login session cookies are configured to last for up to 30 days. They can be removed by switching accounts/signing out or deleting cookies. Sessions contain account identifiers, nicknames and other information needed to restore your login.
- Browser storage may contain account-specific nickname and joined meeting caches, previous vote confirmation state, whether you have seen import guidance, and meeting drafts. You can remove this information by clearing site data in your browser. Clearing browser data does not automatically delete meetings or votes stored on our servers.
- Our analytics events do not send meeting titles, nicknames, Kakao account identifiers, meeting IDs, shared URLs, calendar events or authentication tokens to GA4. Page locations are sent as category URLs without meeting-identifying query parameters. Google Signals and advertising personalization signals are disabled. Google may nevertheless receive technical information such as your IP address during communications and use cookie identifiers and similar information to process usage statistics.
- Retention of GA4 cookies and events depends on Google’s cookie policies, the Service’s GA4 configuration and your browser settings. You can restrict cookies/tracking in your browser or use the Google Analytics Opt-out Browser Add-on. Restricting cookies or storage may affect features such as maintaining your login.
6. Retention and Deletion
- Meetings, votes and account profiles: We retain these while providing meeting rejoining and history features. There is currently no automatic expiration. We process deletion requests within the necessary scope after verifying your identity. If separate retention is required by law, we will explain the applicable scope and period.
- The meeting deletion button: After verifying the creator, a successful deletion permanently removes the meeting details, participants and sticker votes from Firebase. It also removes references from the creator’s and current participants’ meeting lists and the administrator index. Only a private deletion identifier remains to prevent reuse of old links. For meetings previously hidden using the earlier deletion method, you may request removal of the underlying data at the contact address below.
- Personal calendars: Imported events are used only in the current page’s memory. The “Clear imported events” control removes the display data; imported events do not persist after a reload or page closure. After switching to another account or meeting, the previous calendar is not displayed. You can separately revoke Google authorization.
- Support records: We retain these for as long as needed to resolve the inquiry or deletion request and delete them when that purpose is complete.
- Electronic information designated for deletion is removed from the relevant storage system. External providers’ logs and backups may be subject to their own retention and deletion policies.
7. Your Rights and Disconnecting Google
You can request access to, correction or deletion of your information, suspension of processing, or withdrawal of consent. You can directly change your nickname and edit or remove your stickers in the Service. For other requests, contact the email address below. We may request the minimum information needed to verify your identity, such as the meeting URL or account verification. Do not send passwords.
You can revoke Google permissions at any time through your Google Account’s third-party connections. Clearing imported events in the Service clears the displayed data and is separate from revoking Google authorization. To also clear information already displayed in your browser, clear the imported events or reload the page.
8. Security Measures and Google User Data Protection
언제돼? (Pickatime) treats events read from Google Calendar and Google access tokens as sensitive information and uses the following measures to reduce the risk of unauthorized access or disclosure.
- Encryption in transit: The Service is delivered over HTTPS, and communications between the browser and Google authorization/Calendar APIs are encrypted using HTTPS/TLS. Your browser requests events directly from Google APIs. Google access tokens are passed in the Authorization header of Calendar API requests and are not included in shared URLs or analytics events.
- Storage minimization: Imported Google events and access tokens are processed only in the current page’s browser memory. They are not persisted to our servers, Firebase database, server-side calendar backups, browser localStorage or sessionStorage. The Service therefore does not maintain long-term storage of these Google events or tokens. Retention and protection of the original events in your Google Account are governed by Google’s policies.
- Minimum, read-only permissions: We request only read access to the calendar list and events. We retrieve events from the calendars you select within the meeting period. We do not request permission to create, modify or delete Google events.
- Separation of personal and shared data: Imported events are displayed only on the requesting account’s own screen for the relevant meeting. The previous events are not displayed after switching accounts or meetings. Event titles/times and Google access tokens are excluded from shared voting records, administrator statistics, sharing messages and Google Analytics. Event titles are escaped and displayed as text rather than interpreted as HTML.
- Ending use and revoking access: The app removes its token references when the import dialog closes and after a successful event fetch. You can remove references to displayed event data using “Clear imported events”; imported events are not restored after a page reload or closure. You can also revoke permissions through your Google Account’s connections page. These actions do not delete the original events stored by Google.
- Protection of other Service information: Login uses signed HttpOnly and Secure session cookies. Firebase Authentication identifies the participant, and database rules restrict changes to each meeting’s participant record and sticker votes to the authenticated participant’s own identifier. Server credentials are stored as encrypted Secrets in Cloudflare. The server checks authorization for administrator pages and meeting deletion requests. Shared information such as meeting nicknames and sticker votes is available to people with the meeting link and has a different visibility scope from imported personal calendar data.
9. Operator and Contact
Privacy contact: the operator of 언제돼? (Pickatime)
Support and requests to access, correct or delete information: hpnpix.locked@gmail.com
For privacy-related counseling in South Korea, you may also contact the Personal Information Infringement Report Center (118 within South Korea) or the Personal Information Dispute Mediation Committee.
10. Changes to This Policy
When Service features or information handling practices change, we will publish the changes and effective date on this page. For significant changes affecting your rights or the purposes of information use, we will provide any necessary additional notice and consent process.