Privacy Policy
Effective date: 2026. 11. 20.
Vooy Korea Inc. (the “Company”) establishes and publishes this Privacy Policy to protect users’ personal information and to handle privacy-related inquiries promptly and appropriately in accordance with the Personal Information Protection Act of the Republic of Korea and other applicable laws.
Vooy is a service in which an AI agent interprets a user’s natural-language request received through the Vooy app and web, performs the necessary tasks, and returns the result. In the Vooy app and web, users can converse with other users and call an agent in group chat rooms, and the agent can make or receive phone calls on the user’s behalf.
To provide the service, Vooy may process the user’s request content, service usage records, agent execution records, and, where necessary, information associated with connected external services.
Article 1 (Purposes of Processing Personal Information)
The Company processes personal information for the purposes listed below. Personal information will not be used for purposes other than those stated below, and if a purpose changes, the Company takes the measures required by applicable law.
- Account registration and management: confirming registration intent, login, identity verification, maintaining and managing account status, responding to inquiries, delivering notices, and confirming whether the user is at least 14 years of age
- Service provision: providing the AI agent service through the Vooy app and web, receiving and responding to user requests, interpreting requests from conversation context, planning and performing tasks, returning execution results, calling external services or connected tools, providing user-visible conversation context and AI agent memory features, conversations between users, finding and inviting friends through contacts, calling agents in group chat rooms and coordinating appointments in group rooms, schedules, to-dos, briefings, and notifications, recipes, voice input, image generation, and phone calls (the agent placing or answering calls on the user’s behalf)
- External service connection and requested task execution: performing tasks requested by the user through external services that the user has connected or directed the agent to use, including search, reservation, ordering, payment, vehicle dispatch, and the management of documents, files, email, and calendars, as well as retrieving transportation, location, weather, and legal information; searching for information and performing tasks on websites through an external browser; and logging in, making payments, and performing tasks using login information, card information, and other information stored in Vault or entered for the current task
- Security and reliability: error analysis, incident response, prevention of misuse, security log management, service health monitoring, and management of AI usage costs
- Customer support: receiving and processing inquiries, reports, objections, and requests to exercise privacy rights and notifying the results, and handling incident and error reports received through conversation
- Service operation and improvement: analysis of usage flows and failure points to diagnose problems, measure stability, and understand feature usage, as well as quality improvement and development of new features. However, the Company does not use users’ personal information or conversation content to train AI models. Article 11 takes precedence for Google API User Data, which is used only to provide or improve user-facing Google integration features.
- Sending marketing information: sending advertising information such as product news, events, and benefits by email, app push, and text message (SMS) to users who have consented to receive marketing information.
Article 2 (Categories of Personal Information Processed)
The Company processes the following categories of personal information.
| Category | Information processed |
|---|---|
| Account registration and identification | User ID, nickname or profile name, email address, password verification value, the identifier, name, email, and profile of the Apple or Google account where the user registered with that account |
| Identity verification information | Email address and phone number, and verification codes and sending records |
| Profile and settings information | Name and nickname, profile photo, language and time zone, agent name, and agent personality and tone settings |
| Conversation and request information | Messages, commands, request content, and the contents of attached documents or files entered by the user, requests sent to the AI and answers received, and voice messages and transcripts, and image generation instructions, reference images, and generated images |
| User-to-user conversation information | Message body and attachments, the sender, chat room, and time of messages, reactions and replies, read and activity status, records for search, and links in messages and preview results |
| Friend and invitation information | Invitation links and acceptance history, friend relationships, (optional) where the user has enabled contact syncing, phone numbers in the device address book (including numbers of people who do not use Vooy), and app installation identifier values for preventing duplicate invitation rewards |
| Schedule, to-do, and recipe information | Copies of events, to-dos and change history, the interests, times, and recurrence of briefings and notifications, and the names, descriptions, and instructions of recipes and their publication and installation history |
| Task execution information | AI agent execution process, external tool, API, or MCP call records, execution results, error information, records of the user’s confirmation before an external change is executed, and model, token, latency, error, and cost records of AI request processing |
| External service connection information | External service account information, authentication and connection information, sessions or tokens, and the login state information of connected services required for a connection or requested task |
| External execution information such as reservations and orders | Name, phone number, and address required for reservation, ordering, payment, dispatch, and pickup, origin and destination, vehicle number, and reservation and order details and processing results (may include information of other persons such as companions and recipients) |
| Phone call information | The other party’s phone number, the date, time, and length of the call, a transcript of the call content in text and its summary, records of outcomes such as appointments made on the call, phone numbers and names that the user has directly registered as numbers from which incoming calls are allowed (which may be information of other persons), incoming call settings, and the phone number assigned to the user by the service (only for users provided with that feature). Call audio is not stored |
| Appointment coordination information | Content of the appointment coordination request, negotiation content and draft answers exchanged by the participants’ agents, shared answers and the final plan, participants’ confirmation records, memory, preferences, past conversations, and schedule information (including event details) used to prepare answers, and automatic answer settings |
| External browser task information | Task instructions, the content of web pages visited during the task, name, address, contact details, reservation information, and other information entered as needed for the task, task results and images and links of result screens, and task completion notifications |
| Vault information | Login information for external websites and services stored by the user or entered for the current task (ID, password, PIN, one-time password setup value), card information (cardholder name, card number, expiration date, security code (CVC), card password), identity information (name, email, phone number, date of birth, address), one-time verification codes and payment passwords (deleted after use), storage method (keep stored or use only for the current task), usage records, and the names and values of fields that the user or the agent added directly to an item (stored and displayed masked where the user marks them as secret) |
| (Optional) Device contacts and device calendar information | Processed only where the user has agreed to the relevant connection. Device installation identifier and platform; contact names, nicknames, phone numbers and their labels; device calendar names and identifiers (a Google calendar’s may be an email address) and event titles, times, locations, attendees, organizers and response status |
| Google API User Data | (Information received from Google when the user connects a Google account) Google account identifiers; OAuth tokens; Gmail messages, metadata, labels, and drafts; Calendar events, calendars, and free or busy information; Drive files, folders, metadata, and permissions; Docs document content; Sheets cell and formatting information; Tasks task lists and tasks; Google API results; and data derived from them as necessary to perform user-requested features |
| (Optional) Automatically collected email and calendar information | Subject, body, sender, recipients, date, and attachment information of email from the past 90 days and of email newly received while connected, and title, description, time, location, organizer, and attendees of events from the past 90 days and the next 180 days and of events newly created or changed while connected |
| AI agent memory information | Preferences, settings, relationships, and facts automatically extracted from one-on-one conversations or that the user asked to be remembered, portions of statements by the user and the AI, memory creation status, excerpts and indexes for search, memory created through automatic collection of email and calendar events, and the recent conversation of a group chat room stored when the agent is called in that room and memory created from it |
| Sensitive information | Sensitive information such as health, religion, and political opinions that the user discloses in conversations or notes, or that is contained in connected email and calendars |
| Automatically collected information | IP address, access time, service usage records, device and browser information, cookies or similar identifiers, access logs, and session information |
| Error and diagnostic information | Error and stack information when the app freezes or encounters an error, app and device information, certain performance trace information, server error reports (error type, message, and stack, report classification and trace id, masked additional values), web and server activity records (screen navigation, elements pressed, console logs, request and external call addresses and request headers. Masked), and internal identifiers (account, agent, session, conversation, and chat room ids) (including before registration) |
| Usage analytics information (collected automatically in the course of using the Service) | Usage events, the app installation identifier before sign-in, the account identifier after sign-in, session and conversation identifiers, and app, device, operating system, screen, session, and performance information. Conversation content is not transmitted |
| (Optional) Marketing receipt information | Email address, mobile phone number, app push token, name and nickname, and consent or withdrawal status and time for each channel |
| Notification information | Device and installation identifiers, and push token |
| Consent records | The content and time of consent to the Terms of Service and to personal information processing, the latest status and time of marketing consent, and records of consent to overseas transfer for AI |
| Invitation link connection information | App installation, launch, and deep link events and their times of occurrence (all users who install and launch the app), random device identifier, device identifier values (iOS IDFV, Android App Set ID), IP address, and device, operating system, language, country, and time zone information. Advertising identifiers, member account identifiers, email, and phone numbers are excluded |
| (Only for users of the former paid service) Payment records | Payment date, time, and amount, type of payment method, payment approval information, and token top-up, use, and refund history for the former paid service (token top-up) |
| Customer support information | Content of inquiries, reports, objections, and requests to exercise rights and reply contact details, information required for identity verification, attachments selected by the user, and, where reported through conversation, the report summary confirmed by the user, selected materials, and technical information |
Article 3 (Processing and Retention Periods)
The Company processes and retains personal information for the period prescribed by law or for the period consented to by the data subject when the information is collected.
The applicable processing and retention periods are as follows.
| Category | Retention period | Basis |
|---|---|---|
| Account information (account, profile, and settings information, and email address and phone number used for identity verification) | Until account deletion | Conclusion and performance of a contract |
| Conversation content (conversations with the AI, attachments, requests and answers, user-to-user conversation messages, voice messages and transcripts, and generated images) | Until account deletion | Conclusion and performance of a contract |
| Verification codes and sending records among identity verification information | Verification codes are deleted without undue delay upon completion of verification or expiration of the validity period (5 minutes for text messages, 1 hour for email). Text message verification records are retained until account deletion, and sending-limit records for 7 days | Conclusion and performance of a contract |
| AI agent memory information (including excerpts and indexes for search) | Until the memory is deleted or the account is deleted | Conclusion and performance of a contract |
| Sensitive information | Until the memory is deleted, the account is deleted, or suspension of processing is requested | Processed within the scope the user entered or connected (Article 12) |
| Google OAuth authentication information and other external account authentication information | Until the Google connection is disconnected, consent is withdrawn, or the account is deleted | User consent |
| Google service request data and original processing results | Deleted immediately after the request is processed. However, if included in conversation history, until account deletion or withdrawal of consent | User consent |
| AI agent memory information derived from Google API User Data (including memory created by reading past email and calendar events) | Until the user requests deletion of the memory or deletes the account. Where consent to reading past email and calendar events is withdrawn, memory created under that consent is also deleted. Temporary copies of the original text read are deleted without undue delay after the memory is created | User consent |
| Contact syncing information | Until contact syncing is disconnected, the account is deleted, or consent is withdrawn | User consent |
| Device contacts | Deleted immediately when that device is disconnected, when it reports the permission was withdrawn, or on account deletion. Stored encrypted | User consent |
| Device calendar events | Deleted immediately when that device is disconnected or on account deletion. If only the permission is withdrawn, the last synced copy is kept until the user reconnects or disconnects | User consent |
| Friend and invitation information, schedule, to-do, and recipe information, task execution information, and external execution confirmation records | Until account deletion | Conclusion and performance of a contract |
| App installation identifier values for preventing duplicate invitation rewards | Until account deletion. After account deletion, converted into a value that only the Company can match and kept separately for 6 months solely to prevent duplicate invitation rewards | Conclusion and performance of a contract |
| Phone call information (the other party’s phone number, call date, time, and length, and transcript, summary, and outcome records) | Retained until account deletion; records and summaries of call content and their search indexes are destroyed within 30 days after account deletion. Call audio is not stored | Conclusion and performance of a contract |
| Phone numbers and names registered as numbers from which incoming calls are allowed, and incoming call settings | Until the user deletes them or deletes the account | Conclusion and performance of a contract |
| Appointment coordination information (negotiation content, draft answers, shared answers and plans, and confirmation records) | Until account deletion. However, answers and plans shared in a chat room are handled in the same way as the chat room’s messages | Conclusion and performance of a contract |
| Task instructions and result records retained by the Company among external browser task information | Until the relevant conversation is deleted or the account is deleted | Conclusion and performance of a contract |
| Login state information of connected services used for external browser tasks | Until the user requests deletion or deletes the account | Conclusion and performance of a contract |
| Information stored in Vault | Until the user deletes it or deletes the account. One-time verification codes are deleted after 5 minutes and payment passwords after 10 minutes. Vault usage records are retained for 90 days | Conclusion and performance of a contract |
| Login information and other information entered for use only for the current task | Deleted within 30 minutes after the task is completed. Request records excluding the values are retained for 90 days | Conclusion and performance of a contract |
| Link preview results | 1 day | Conclusion and performance of a contract |
| Error and diagnostic information, and server diagnostic and error logs | Error and diagnostic information for 90 days, and server diagnostic and error logs for 31 days | Conclusion and performance of a contract |
| Invitation link connection information | Until termination of the processing agreement with AB180 Inc. (based on the processor’s retention) | Conclusion and performance of a contract |
| Search indexes of chat room messages and call records | Until the message is deleted, or within 30 days after account deletion | Conclusion and performance of a contract |
| Usage analytics information | 730 days from the collection date. Deletion is requested from the analytics provider within 30 days after account deletion, and the provider’s deletion may take up to 30 more days after the request | Performance of the contract (service operation and improvement) |
| Marketing receipt information | Until consent is withdrawn or the account is deleted. However, the latest consent status and its time are kept for 1 year after account deletion | User consent, Act on Promotion of Information and Communications Network Utilization and Information Protection |
| Consent records (consent to the Terms and the Privacy Policy, the latest status of marketing consent, and consent to overseas transfer for AI) | 1 year after account deletion. Stored separately from other information | Confirmation of consent and dispute response |
| Model, token, latency, error, and cost records of AI request processing | 1 year after account deletion (for AI usage cost management; stored separately from other information) | Conclusion and performance of a contract |
| Notification information | Until logout or account deletion | Conclusion and performance of a contract |
| Customer support and rights-exercise handling records | 3 years | Conclusion and performance of a contract, compliance with a legal obligation |
| (Only for users of the former paid service) Records on payment and the supply of goods, etc., and records on contracts or withdrawal of offers, etc., for the former paid service | 5 years | Act on Consumer Protection in Electronic Commerce |
| Access records | 3 months | Protection of Communications Secrets Act |
| IP address, device and browser information, and session information | Until session expiration (365 days for the app, 7 days for the web), logout, or account deletion | Conclusion and performance of a contract |
| (Only for users of the former paid service) Consumer complaint and dispute records concerning the former paid service | 3 years | Act on Consumer Protection in Electronic Commerce |
Upon account deletion, login is blocked immediately, and personal information is deleted within 5 days. Copies remaining in backups are deleted within 30 days. However, the following information is handled as described below.
- One-on-one conversations with another user are handled in the same way as chat room messages. The conversation remains in the other party’s chat room, the deleted user’s account information is removed, and if the other party also leaves and no participants remain, the entire chat room is deleted.
- Messages in chat rooms shared with other users and results shared by the user remain in the chat room, and the sender is displayed as “Unknown.” The user may directly delete messages the user does not wish to leave before deleting the account, and may request deletion of personal information contained in the remaining messages by emailing privacy@vooy.com.
- Copies of a recipe installed by other users remain with the creator attribution removed, and the original of a recipe published by the user is taken down from the store.
- Records and summaries of call content and their search indexes, and the search indexes of chat room messages, are destroyed within 30 days after account deletion.
- Call records kept by the telephone line carriers (Teamrunners Co., Ltd. and Flover Inc.) under the Protection of Communications Secrets Act and other applicable laws, and call records kept by the overseas carrier (Telnyx LLC) that provides the outgoing line for calls to phone numbers outside Korea under the laws of its own country and its retention policy, are retained for the period set by the carrier.
- For usage analytics information, deletion is requested from the analytics provider within 30 days after account deletion, and the provider’s deletion may take up to 30 more days after the request.
- Files, call records, and task results shared in a group chat room are handled in the same way as chat room messages.
- Copies remaining in backups are not deleted individually and are deleted once the backup retention cycle (within 30 days) has passed. The Company does not restore and use backups during that period.
- Information preserved under applicable laws is stored separately from other personal information and is used only for the purposes prescribed by those laws.
When an external account is disconnected, the Company does not retrieve new information from that service. However, memory and event copies already created remain and are deleted when the user deletes them or deletes the account. Records remaining on that service’s side must be checked directly with that service.
Even if a message is edited or deleted, content the AI has already read and memory created from it are not reverted. The user may request deletion of such content by emailing privacy@vooy.com, and the Company will notify the user of the result within 10 days from the date it receives the request.
Even if the user leaves a chat room, task records exchanged by the AI in that room and memory created there remain. Memory can be deleted in memory management, and the user may request deletion of task records by emailing privacy@vooy.com.
External browser task records retained by the Company are deleted together when the conversation is deleted or the account is deleted. Records remaining on the external browser service’s side are subject to the periods set out in Article 5.
Even where information is deleted from Vault or set to be used only for the current task, records and login state remaining on external websites and services are not deleted. Such records must be checked directly on the relevant website or service.
Article 4 (Provision of Personal Information to Third Parties)
① The Company processes personal information only within the purposes specified in Article 1 and provides it to a third party only with the user’s consent or where specifically permitted by law.
② Because the service uses AI agents, the minimum information necessary to complete a user-requested task may be transmitted to an external service when the user asks the agent to act on that service or directs the agent to connect it. The Company handles this by distinguishing the following cases.
A. Where information is provided with the user’s consent (connection of an external account, reservations and orders with overseas businesses, etc.)
The Company informs the user of the matters below and obtains consent at sign-up, and the actual provision takes place when the user connects an external account or uses a feature such as reservations and orders with overseas businesses. After sign-up, the user can stop the provision by disconnecting the service or not using the feature.
| Recipient | Purpose | Information provided | Retention and use period |
|---|---|---|---|
| Google LLC | Execution of requests directed by the user, such as sending email, creating and changing events, and working with documents and files, in Google services connected by the user, including Google Calendar, Docs, Drive, Gmail, Sheets, and Tasks | Google account identifiers, the content and recipients of email to be sent, events to be created or changed and their attendees, the content of documents and files to be created or edited, and other information necessary for the work entrusted by the user | For content stored in the Google account, until the user deletes that content or the Google account. Other retention is subject to Google’s retention policy |
| Operators of other overseas external services connected by the user (the full list is in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com)) | Execution of requests directed by the user, such as search and lookup or reservations and orders | Information entered or connected by the user for the requested task, request content, and processing results | In accordance with the recipient’s privacy policy |
B. Where information is provided for a task directed by the user
To perform search and lookup tasks directed by the user, requests for reservation, ordering, payment, dispatch, and pickup with domestic businesses, and external browser tasks, there are cases where the Company additionally provides personal information pursuant to Article 17(4) of the Personal Information Protection Act and Article 14-2 of the Enforcement Decree of the same Act. Where the Company additionally provides personal information, it reviews the matter taking the following into consideration.
- Whether it is related to the original purpose of collection
- Whether the additional use or provision of personal information is foreseeable in light of the circumstances in which the personal information was collected or processing practices
- Whether it unfairly infringes the interests of the data subject
- Whether measures necessary to ensure security, such as pseudonymization or encryption, have been taken
The cases in which the Company additionally provides personal information are as follows.
| Recipient | Information provided | Purpose of use | Retention and use period |
|---|---|---|---|
| Operators of external services necessary to perform search and lookup tasks directed by the user (e.g., Naver Shopping, Search, and Maps, Naver Flights, KakaoMap, Korean legal information, Korean weather and air quality information, shipment tracking, MyRealTrip, etc. The full list is in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com)) | Information necessary for performing the task among the user’s inputs, outputs, and instructions (search terms, place names and addresses, schedules, tracking numbers, etc.) | Performing tasks on the user’s behalf, such as information search and lookup | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| Operators of domestic websites on which the user has directed an external browser task | Information necessary for performing the task among the user’s instructions (search terms, name, address, contact details, reservation information, etc.), and the login information and card information in Vault needed for the task requested by the user | Performing tasks directed by the user, such as information search, login, and reservation | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| Catch Table, Yogiyo | Request content entered by the user, information required to process a reservation, waitlist, or order (name, phone number, address, etc. of the person making the reservation or the recipient), and processing results | Restaurant search, reservation, waitlist registration, ordering, and other user-requested tasks | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| Charan | Applicant’s name, contact details, and address, pickup request details, and processing results | Receiving and processing pickup requests | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| Modu Parking | Name and phone number, vehicle number, reservation details, and processing results | Receiving and processing parking reservation, payment, and cancellation requests | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| Swing Taxi | Name and phone number, origin and destination, dispatch request details, and processing results | Receiving and processing taxi dispatch and cancellation requests | The recipient receives the information directly and processes it in accordance with its own privacy policy |
| The other party to a phone call directed by the user (restaurants, businesses, etc.) | Content the user has entrusted the agent to convey (name, contact details, reservation or inquiry content, etc.) | Performing calls directed by the user, such as reservations and inquiries | The other party receives it directly through the call, and it is subject to the other party’s handling standards |
| Operators of other domestic external services connected by the user (the full list is in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com)) | Information entered or connected by the user for the requested task, request content, and processing results | Execution of requests directed by the user, such as search and lookup or reservations and orders | The recipient receives the information directly and processes it in accordance with its own privacy policy |
Review of the additional provision of personal information
- Relevance to the original purpose of collection: The Company does not provide information collected in advance at a different time for a different purpose, but provides information in the course of accessing an external service within the scope of that purpose in order to perform a specific task directed by the user. Accordingly, the Company has determined that there is a close relevance to the purpose of collection directed by the user.
- Foreseeability: Because the Company is an AI agent service that accesses external services for the user and carries out the user’s instructions, entering the instructed content into an external service in order to carry out the user’s instructions is within a foreseeable scope. In addition, where the user directs a task, the Company provides information within a temporally close scope in order to perform that task.
- Whether the data subject’s interests are infringed: The Company provides information to external services only to the extent necessary to fulfill the purpose directed by the user, and such provision takes place within the scope that would also arise if the user used the external service directly. Accordingly, the Company has determined that it does not unfairly infringe the interests of the data subject.
- Security measures: The Company takes security measures under the Personal Information Protection Act and its subordinate statutes, such as transmitting only the information necessary for performing the task, through encrypted communications.
The information transmitted may include the names, phone numbers, and addresses of other persons, such as companions, recipients, and the other party to a call. Where the user enters another person’s information, the user must inform that person in advance, and that person may request confirmation of the source of collection and other matters pursuant to Article 14(5).
③ Transfers of personal information to overseas third parties are described in Article 6.
Article 5 (Outsourcing of Personal Information Processing)
① The Company outsources the following personal information processing activities to provide the service.
| Processor | Processing activity | Subprocessor | Retention and use period |
|---|---|---|---|
| Cloudflare, Inc. | Service infrastructure, security, traffic management, and storage environment operation (including storage of conversations, memory, attachments, Vault, and connection information), and search processing (embedding and reranking) | As listed in Cloudflare’s privacy policy or subprocessor list | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| PlanetScale, Inc. | Database operation (including storage of the login state information of connected services, encrypted device contacts, and device calendar events) | As listed in PlanetScale’s privacy policy or subprocessor list | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Anthropic, PBC | AI response generation (direct connection) | As listed in Anthropic’s privacy policy or subprocessor list | Up to 30 days after the request is processed |
| OpenRouter, LLC | AI response and image generation, interpretation of user requests, and connection to AI model providers | AI model providers called through OpenRouter (their names and countries are published in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com), and that list forms part of this Privacy Policy) | Not retained after the request is processed (zero-retention condition). However, image generation requests may be retained by the model provider (OpenAI) for up to 30 days for abuse monitoring. Until termination of the processing agreement |
| OpenAI OpCo, LLC | Assisting AI response generation (short determinations) | As listed in OpenAI’s subprocessor list | Up to 30 days after the request is processed |
| TypeSafe AI, Inc. | Assisting AI response generation (short determinations) | As listed in TypeSafe’s subprocessor list | In accordance with the processor’s default retention policy |
| Soniox Inc. | Real-time transcription of phone call audio, and transcription of voice messages into text | As listed in Soniox’s privacy policy | Call audio is not stored. For voice messages, deletion is requested after transcription, 30 days at the latest |
| Eleven Labs Inc. | Speech synthesis of sentences to be spoken by the agent in a phone call | As listed in ElevenLabs’ privacy policy or subprocessor list | In accordance with the processor’s default retention policy |
| Teamrunners Co., Ltd. (ClawOps) | Provision of lines for outgoing and incoming calls, and processing of call records (calling and receiving numbers, date and time, call duration) | Not applicable | 12 months (the period the carrier retains under applicable laws). Deletion or masking is requested upon account deletion |
| Flover Inc. (KAT Cloud) | Provision of lines for outgoing and incoming calls, and processing of call records (calling and receiving numbers, date and time, call duration). Applies from the time of the line switchover | Not applicable | 12 months (the period the carrier retains under applicable laws). Deletion or masking is requested upon account deletion. Call audio is not stored |
| Telnyx LLC | Provision of the outgoing line for calls to phone numbers outside Korea (using a US outgoing number held by the Company), and processing of call records (calling and receiving numbers, date and time, call duration) | As listed in Telnyx’s subprocessor list | In accordance with the processor’s retention policy and applicable laws (may be retained after the agreement ends, and deleted or anonymized when no longer needed). The Company does not use Telnyx’s call recording feature |
| Kernel Technologies, Inc. | Running the external browser and performing website tasks directed by the user | UAB Data troops (Decodo): provision of network connectivity for the external browser | Session recordings, visited URLs, and telemetry are deleted immediately upon session end, session metadata 30 days, security audit logs 12 months |
| Browser Use Inc.(Browser Use Cloud) | Running the external browser and performing website tasks directed by the user (only for some websites; including storage of profiles containing the login state of connected services) | As listed in Browser Use’s subprocessor list | Deletion is requested when the conversation is deleted or the account is deleted (Browser Use’s deletion may take up to 90 days after the request, based on the deletion deadline in Section 10 of the Browser Use DPA) |
| Elasticsearch B.V. (Elastic Cloud, Google Cloud Seoul region) | Storage of search indexes of chat room messages and call records | As listed in Elastic’s subprocessor list | Until the message is deleted, or within 30 days after account deletion |
| Exa Labs, Inc. | Web search, link previews, and search result summaries | As listed in Exa’s privacy policy | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Plus Five Five, Inc.(Resend) | Sending verification and password reset email and (only for users who have consented to receive marketing information) marketing email | As listed in Resend’s subprocessor list | 30 days |
| NAVER Cloud Corp. | Sending verification text messages and (only for users who have consented to receive marketing information) marketing text messages (SENS) | Not applicable | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Infobank Corp. (Bizgo) | Fallback sending of verification text messages (only when NAVER Cloud refuses to send) | Not applicable | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| 650 Industries, Inc.(Expo) | Delivery of mobile push notifications (including advertising push to users who have consented to receive marketing information) | Google (FCM), Apple (APNs) | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Mixpanel, Inc. | Usage statistics analysis for service operation and improvement (problem diagnosis, stability measurement, and understanding of feature usage). Google API User Data is excluded from this processing | As listed in Mixpanel’s privacy policy or subprocessor list | 2 years (730 days) from the collection date. Deletion is requested within 30 days after account deletion, and the provider’s deletion may take up to 30 more days after the request |
| PostHog, Inc. | AI usage cost management and incident response (processing of model, token, cost, latency, and error records of AI calls and session and agent identifiers). Google API User Data is excluded from this processing | As listed in PostHog’s privacy policy or subprocessor list | 1 year after account deletion |
| Raintank Inc. d/b/a Grafana Labs (Grafana Faro) | App performance and usage diagnostics | As listed in Grafana Labs’ privacy policy or subprocessor list | Within 90 days (the retention period for error and diagnostic information in Article 3) |
| Raintank Inc. d/b/a Grafana Labs (Grafana Cloud) | Service operation and incident response through server logs, metrics, and traces | As listed in Grafana Labs’ privacy policy or subprocessor list | 31 days |
| Functional Software, Inc.(Sentry) | Diagnostics of app, web, and server errors and web and server performance | As listed in Sentry’s privacy policy or subprocessor list | 90 days |
| AB180 Inc. (Airbridge) | Identifying the app installation path and delivering invitation codes (deferred deep linking) | Amazon Web Services, Inc. (Japan), Snowflake Inc. (Japan), New Relic, Inc. (United States) | Until termination of the processing agreement or fulfillment of the processing purpose |
| Sampark Inc. (Composio) | Relaying connections to external accounts (existing Google connections not yet moved to the Company’s direct connection, Instagram, YouTube, and TikTok) | As listed in Composio’s subprocessor list | Until disconnection or termination of the processing agreement |
| Supabase Pte. Ltd. (Seoul region) | Storage (database) of login sessions and connection tokens for some external services (such as restaurant reservation and ordering) | As listed in Supabase’s subprocessor list | Until disconnection or account deletion |
| Amazon Web Services Korea LLC (Seoul region) | Management of the encryption keys for the login sessions and connection tokens above | As listed in AWS’s subprocessor list | Until disconnection or account deletion |
| Google Cloud Korea LLC (Google Cloud, Seoul region) | Provision of an isolated execution environment for tasks that use Vault information | Google LLC | Processed only during task execution and not stored |
② When entering into an outsourcing arrangement, the Company documents requirements concerning prohibition of processing outside the outsourced purpose, technical and organizational safeguards, restrictions on subprocessors, supervision, and liability in the applicable agreement, terms, privacy documents, or equivalent records, and supervises the processor’s handling of personal information.
③ Where a processor engages a subprocessor, the Company requires the processor to obtain the Company’s approval. Current subprocessors may be found in the processor’s privacy policy, subprocessor list, or equivalent public documentation. The current list of AI model providers called through OpenRouter and of external services that users can connect is posted in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com), and the Company updates that list when it changes. For AI model calls through OpenRouter, OpenRouter selects at the time of the request from among the providers that meet the conditions set by the Company (such as zero retention), and those candidate providers are added to the list in advance. Image generation requests are an exception to the zero-retention condition and are processed by the model provider (OpenAI).
④ If outsourced activities or processors change, the Company will disclose the change through this Privacy Policy and the list above without undue delay.
⑤ Overseas outsourcing is described in Article 6.
Article 6 (Overseas Transfers of Personal Information)
The Company transfers personal information collected from service users overseas as described below. An overseas transfer may include storage, access, outsourced processing, third-party provision, or transmission over a network.
■ Legal basis for overseas transfer: Article 28-8(1)(3) of the Personal Information Protection Act
If a user refuses an overseas transfer, all or part of the service may be unavailable. A user who does not want an overseas transfer may disconnect an external service in the account or connection management screen or contact customer support to request account deletion, withdrawal of consent, or suspension of processing. Information for invitation link attribution (Airbridge) is not linked to an account, so deleting the app stops its transmission. Deletion of information already transmitted can be requested by emailing privacy@vooy.com.
| Overseas recipient or processor and contact | Country | Information transferred | Purpose | Timing and method | Retention and use period |
|---|---|---|---|---|---|
| Cloudflare, Inc. (dpo@cloudflare.com) | United States | Account and usage information required to operate the service, encrypted Google API User Data and authentication information, encrypted device contacts, device calendar events, access information, security and error logs, and stored information such as conversations, memory, attachments, and Vault | Service infrastructure, security, traffic management, and storage environment operation | Transmitted over a network when the service is used | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| PlanetScale, Inc. (privacy@planetscale.com) | Japan | Information stored in the database, such as accounts, conversations, memory, call records and transcripts, friends and schedules, encrypted device contacts and device calendar events, and login state information of connected services | Database operation | Transmitted through encrypted communications when the service is used | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Anthropic, PBC (privacy@anthropic.com) | United States | User requests and conversation content, conversation context, memory, and attachments, the minimum Google API User Data needed to generate a response to a Google-connected request, device contacts and device calendar events needed to process the user’s request, and processing results | AI response generation (direct connection) | Transmitted through encrypted communications when the service is used | Up to 30 days after the request is processed |
| OpenRouter, LLC (privacy@openrouter.ai) | United States and the countries in which the providers listed in the Article 5 list are located | User requests and conversation content, conversation context, memory, and attachments, the minimum Google API User Data needed to generate a response to a Google-connected request, device contacts and device calendar events needed to process the user’s request, processing results, image generation instructions and reference images (including photos the user posted in the conversation), and records of call content | AI response and image generation, interpretation of user requests, and connection to AI model providers | Transmitted through encrypted communications when the service is used | Not retained after the request is processed (zero-retention condition). However, image generation requests may be retained by the model provider (OpenAI) for up to 30 days for abuse monitoring |
| OpenAI OpCo, LLC (privacy@openai.com) | United States | Recent messages in the group chat room and the question needed for the determination | Assisting AI response generation (short determinations) | Transmitted through encrypted communications each time a determination is requested | Up to 30 days after the request is processed |
| TypeSafe AI, Inc. (privacy@typesafe.ai) | United States | Recent messages in the group chat room, portions of the text transcribed during a phone call, and sentences spoken by the agent | Assisting AI response generation (short determinations) | Transmitted through encrypted communications each time a determination is requested | In accordance with the processor’s default retention policy |
| Soniox Inc. (support@soniox.com) | United States | Phone call audio (including the other party’s voice) and call context, voice message files, transcription job identifiers, and transcripts | Real-time transcription of phone call audio, and transcription of voice messages into text | Transmitted through encrypted communications each time a call or voice transcription is requested | Call audio is not stored. For voice messages, deletion is requested after transcription, 30 days at the latest |
| Eleven Labs Inc. (dpo@elevenlabs.io) | United States | Sentences to be spoken by the agent in a phone call | Speech synthesis for phone calls | Transmitted through encrypted communications at each call | In accordance with the processor’s default retention policy |
| Telnyx LLC (privacy@telnyx.com) | United States | The other party’s phone number (a number outside Korea), the Company’s outgoing number, the date, time, length, and connection status of the call, and call audio (relayed in real time over the line) | Provision of the outgoing line for calls to phone numbers outside Korea | Transmitted over the telephone network and through encrypted communications each time a call is placed to a number outside Korea | In accordance with the processor’s retention policy and applicable laws (may be retained after the agreement ends, and deleted or anonymized when no longer needed). The Company does not use Telnyx’s call recording feature |
| Kernel Technologies, Inc. (privacy@onkernel.com) | Singapore (browser execution), United States (account information, session metadata, security audit logs) | The content of and input values on external service pages visited by the agent (including the login information and card information in Vault needed for the task requested by the user), login state information of connected services used for the task, and task instructions | Running the external browser and performing website tasks directed by the user | Transmitted through encrypted communications each time a task is requested | Session recordings, visited URLs, and telemetry are deleted immediately upon session end, session metadata 30 days, security audit logs 12 months |
| UAB Data troops (Decodo, subprocessor of Kernel, privacy@decodo.com) | Lithuania | Communications between the external browser and websites | Provision of network connectivity for the external browser | Transmitted over a network each time a task is requested | Communication content is not recorded. Connection metadata is retained for up to 90 days after the end of the billing period |
| Browser Use Inc. (privacy@browser-use.com) | United States | Task instructions, the content of web pages visited during the task, name, address, contact details, reservation information, and other information needed for the task, the login information and card information in Vault needed for the task requested by the user, browser profiles containing the login state of connected services, and task results and images of result screens | Running the external browser and performing website tasks directed by the user (only for some websites) | Transmitted through encrypted communications each time a task is requested | Deletion is requested when the conversation is deleted or the account is deleted (Browser Use’s deletion may take up to 90 days after the request, based on the deletion deadline in Section 10 of the Browser Use DPA) |
| Exa Labs, Inc. (privacy@exa.ai) | United States | Search terms, public URLs to be previewed, and search result information | Web search, link previews, and search result summaries | Transmitted through encrypted communications each time a search is requested | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Plus Five Five, Inc.(Resend) (support@resend.com) | United States | Email address, email body including verification and reset links, marketing email body and the recipient’s name and nickname, and sending records | Sending verification and password reset email and marketing email | Transmitted through encrypted communications each time an email is sent | 30 days after sending (backup copies 7 days) |
| 650 Industries, Inc.(Expo) (contact through the inquiry form on the Expo website) | United States | Push token, device and installation identifiers, and notification title, body, and display name | Delivery of mobile push notifications | Transmitted through encrypted communications each time a notification is sent | Until account deletion, termination of the processing agreement, or fulfillment of the processing purpose |
| Raintank Inc. d/b/a Grafana Labs (Grafana Faro) (dsr-privacy@grafana.com) | Japan | Usage events, device installation identifier and session identifier, app, device, operating system, screen, session, and performance information, app logs (console info, warn, error), JS error messages, and HTTP request records (email addresses, phone numbers, and tokens masked) | App performance and usage diagnostics | Transmitted through encrypted communications at each collection | Within 90 days (the retention period for error and diagnostic information in Article 3) |
| Raintank Inc. d/b/a Grafana Labs (Grafana Cloud) (dsr-privacy@grafana.com) | Japan | Server logs, metrics, and trace information | Service operation and incident response through server logs, metrics, and traces | Transmitted through encrypted communications at each collection | 31 days |
| Functional Software, Inc.(Sentry) (compliance@sentry.io) | United States | Error and stack information, app and device information, certain performance trace information, server error reports (error type, message, and stack, report classification and trace id, masked additional values), web and server activity records (screen navigation, elements pressed, console logs, request and external call addresses and request headers. Masked), and internal identifiers (account, agent, session, conversation, and chat room ids) | Diagnostics of app, web, and server errors and web and server performance | Transmitted through encrypted communications each time an error is reported or performance trace information selected as a sample is collected | 90 days |
| Amazon Web Services, Inc. (subprocessor of AB180 Inc., aws-korea-privacy@amazon.com) | Japan | App installation, launch, and deep link events and their times of occurrence, random device identifier assigned by Airbridge, device identifier values (iOS IDFV, Android App Set ID), IP address, device, operating system, language, country, time zone, screen, carrier, and network information, Android app installation source information, and browser information and the link address containing the invitation code when an invitation link is clicked. Advertising identifiers (IDFA, GAID), member account identifiers, email, and phone numbers are excluded | Processing of invitation link installation connection (hosting) | Transmitted over a network at the first app launch and when an invitation link is clicked | Until termination of the processing agreement or fulfillment of the processing purpose |
| Snowflake Inc. (subprocessor of AB180 Inc., privacy@snowflake.com) | Japan | Same as the Amazon Web Services, Inc. row above | Storage of invitation link installation connection processing data (data warehouse) | Transmitted over a network when the processor stores the processing data | Until termination of the processing agreement or fulfillment of the processing purpose |
| New Relic, Inc. (subprocessor of AB180 Inc., privacy@newrelic.com) | United States | Information included in performance monitoring of the processing environment | Performance monitoring of the processing environment | Transmitted over a network when the processor’s systems are monitored | Until termination of the processing agreement or fulfillment of the processing purpose |
| Sampark Inc. (Composio, support@composio.dev) | United States | Identifiers and authentication information of connected external accounts, and request content directed by the user and processing results | Relaying connections to external accounts (existing Google connections not yet moved to the Company’s direct connection, Instagram, YouTube, and TikTok) | Transmitted through encrypted communications each time an external account is connected or a request is executed | Until disconnection or termination of the processing agreement |
| Mixpanel, Inc. (compliance@mixpanel.com) | United States | Usage events, the app installation identifier before sign-in, the account identifier after sign-in, session and conversation identifiers, and app, device, operating system, screen, session, and performance information. Conversation content and Google API User Data are excluded | Usage analytics for service operation and improvement | Transmitted through encrypted communications at each collection | Until 730 days have passed from the collection date or the processing agreement is terminated. Deletion is requested within 30 days after account deletion, and the provider’s deletion may take up to 30 more days after the request |
| PostHog, Inc. (privacy@posthog.com) | United States | Records of the model, tokens, cost, latency, and errors of AI calls, and session and agent identifiers. Conversation content and Google API User Data are excluded | AI usage cost management and incident response | Transmitted through encrypted communications at each AI call | 1 year after account deletion |
■ Legal basis for overseas transfer: Article 28-8(1)(1) of the Personal Information Protection Act
If a user refuses an overseas transfer, only that feature is unavailable, and other features remain available. The user may disconnect an external service in the account or connection management screen, or contact customer support by email to withdraw consent. A user who does not want usage analytics information (Mixpanel) or app diagnostic information (Grafana Faro) transferred overseas may make a request to privacy@vooy.com or delete their account.
| Overseas recipient and contact | Country | Information transferred | Purpose | Timing and method | Retention and use period |
|---|---|---|---|---|---|
| Google LLC (data-protection-office@google.com) | United States | Google account identifiers, the content and recipients of email to be sent, events to be created or changed and their attendees, the content of documents and files to be created or edited, and other information necessary for the work entrusted by the user | Execution of Google service requests directed by the user (sending email, creating and changing events, working with documents and files, etc.) | Transmitted through encrypted communications each time a connection, lookup, or execution is requested | For content stored in the Google account, until the user deletes that content or the Google account. Other retention is subject to Google’s retention policy |
| Operators of overseas external services that perform search and lookup or reservation and order tasks directed by the user. The name and country of each provider are available in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com) | Shown in the list | Information entered or connected by the user for the requested task, request content, and processing results | Execution of the external service connection or task directed by the user | Transmitted over a network when the service is connected or the task is executed | Until the user’s request is completed or the connection is disconnected, except where the recipient must retain it under applicable law or policy |
| Operators of overseas websites on which the user has directed an external browser task | Country in which the website operator is located | Information necessary for performing the task among the user’s instructions (name, address, contact details, reservation information, etc.), and the login information and card information in Vault needed for the task requested by the user | Performing website tasks directed by the user | Entered through the external browser when the user directs a task | In accordance with the recipient’s privacy policy |
Article 7 (Deletion Procedures and Methods)
When personal information is no longer necessary because the retention period has expired or the processing purpose has been fulfilled, the Company deletes it without undue delay.
Electronic files are deleted using technical methods designed to prevent recovery or reconstruction. Paper records and other non-electronic records are shredded or incinerated.
The timing of deletion upon account deletion and the handling of messages remaining in chat rooms and of backup copies are as described in Article 3. Personal information that must be preserved under applicable laws is stored separately from other personal information.
Article 8 (Rights and Obligations of Data Subjects and How to Exercise Them)
A user may exercise the following privacy rights at any time.
- Request access to personal information
- Request correction of inaccurate information
- Request deletion
- Request suspension of processing
- Withdraw consent or delete the account
- Disconnect an external service
These rights may be exercised through the in-service settings, memory management, or the account or connection management screen, by emailing privacy@vooy.com, or through support@vooy.com. Account deletion, withdrawal of optional consent, deletion of memory, and disconnection of external services can also be done within the app. Upon receiving a user’s request, the Company verifies the requester’s identity and, within 10 days from the date it receives the request, takes action or notifies the user of the result.
A user may exercise these rights through a legal representative or an authorized person, in which case a power of attorney must be submitted.
The Company may refuse all or part of a request where there are grounds prescribed by law, and where it refuses, it informs the user of the reason and how to object. Where materials provided for access contain another person’s personal information, that portion is masked or deleted before the materials are provided.
When a user withdraws optional consent, the Company stops the relevant processing and deletes without undue delay the personal information processed under that consent. However, this does not apply where the information must be preserved under applicable laws.
A person who is not a Vooy user may also, if information entered by a user contains that person’s personal information, request confirmation of the source of collection and the purpose of processing, suspension of processing, or deletion by emailing privacy@vooy.com.
Article 9 (Safeguards for Personal Information)
The Company implements the following measures to protect personal information.
- Organizational measures: establishing and implementing an internal privacy management plan, regular employee training, and supervision of processors
- Technical measures: access-right management that limits the staff who can access personal information to the minimum necessary for their duties, access controls for personal information systems, encryption of personal information, encrypted storage of authentication information and tokens, installation and updating of security software, and audit log management
- Physical measures: access controls for data centers, records storage rooms, and other physical storage locations
Article 10 (Special Provisions for AI Services)
- No use as training data: The Company does not use users’ personal information, conversation content, or Google API User Data to develop, improve, or train any AI or ML model.
- AI model provider settings: The Company transmits users’ information through routes for which a condition that the AI model providers under Article 5 (the providers the Company connects to directly and the providers called through OpenRouter) do not use information received from the Company to develop, improve, or train their own models has been confirmed by terms or settings, and manages it so that it is processed only as necessary to provide the user-requested service. The Company may change the AI models it uses for service quality, and the current list of AI model providers called through OpenRouter is posted in the “Processors and External Services List” (a policy page on the Vooy website, vooy.com).
- AI relay records: The Company does not store conversation content in the course of relaying AI requests, and retains only model, token, latency, error, and cost records for AI usage cost management and incident response for the period set out in Article 3.
- Automatic memory: Even without a separate request from the user, the AI agent extracts preferences, settings, relationships, and facts from one-on-one conversations and stores them as memory. This feature starts turned on. Memory may include sensitive content, such as health, that the user discloses in conversation. The user can view, edit, and delete stored memory in memory management. To turn the memory feature off or to stop the processing of sensitive content, the user can contact privacy@vooy.com. In group conversations, memory is created only from what the user asks the agent to do by calling it.
- Public calls in group chat rooms: In a chat room that the user’s agent has joined, other members can call that agent, and where another member calls it, the agent answers using only the recent conversation in that room without using the user’s memory or email and calendar, and where the user calls it directly, it answers also using the user’s memory and email and calendar. In either case, the answer is visible to all members of the room. This feature is turned on by default and can be turned off at any time in settings. If memory or email and calendar contain sensitive content, it may be included in the answer and be visible in the room, so please ask about content that must not be visible in a one-on-one conversation. When an agent is called in a chat room, the recent conversation in that room may be transmitted to the AI.
- Storage and use of group chat room conversations: When an agent is called in a group chat room, the recent conversation in that room (including statements of other participants) is stored in the agent owner’s conversation history and search index, and that content and memory created from it may be used in the owner’s one-on-one conversations to re-check schedules decided or tasks assumed in that room. It is not used in other group chat rooms. The Company informs chat room participants of this fact when an agent is invited to a chat room and when a new participant joins, and the owner can turn off the storage of group chat room conversations in settings. Even if a message is deleted or the user leaves the chat room, content already stored remains, and its deletion may be requested by emailing privacy@vooy.com.
- Appointment coordination: When a user requests appointment coordination in a group room, the participants’ agents negotiate the schedule and conditions using each participant’s memory, preferences, past conversations, and schedule information (including event details), and present the negotiated plan in the group room. When another participant’s agent asks a question, processing to prepare an answer may begin even without the user’s direct request, and the AI model providers under Article 5 are involved in preparing the answer. Answers are prepared to the extent needed to answer the question and shared in the group room. Negotiated answers and the final plan are shared with participants and may also be displayed in notifications, and negotiation records and drafts are retained for the period set out in Article 3.
- External browser tasks: At the user’s request, the agent uses an external browser service (Kernel, or Browser Use Cloud for certain websites) to find information or perform tasks on websites. Information necessary for the task, such as task instructions and web page content, is processed by the external browser service and the AI model providers under Article 5, as described in Articles 5 and 6. The Company keeps the connection information of connected services needed to maintain login state and uses it for tasks. Task results displayed in a conversation (including images and links) can be viewed by the participants in that conversation. Task records are not deleted immediately when a task ends and are retained for the periods set out in Articles 3 and 5. If a website blocks automated access, the task may fail or use of the account on that website may be restricted.
- Vault: The user can store login information, card information, and other information for external websites and services in Vault, or use it only for the current task without storing it. Information stored in Vault is encrypted with a key created on the user’s device, and the Company retains it only in encrypted form. Information stored under the previous method can be moved to the new method in the app. Only where necessary for a task requested by the user, and only while a time-limited use permit signed and issued by the user’s device is valid, the Company decrypts the information in an isolated execution environment with restricted access and enters it into the login or payment screen of the target website or service, and does not use it for any other purpose. The Company records and manages access to Vault information, and deletes it without undue delay when the user deletes it. “Use only for the current task” means that the information is not kept stored in Vault, and does not mean that no record remains on the external browser service or the target website. The user can view and delete information stored in Vault at any time, but deletion does not delete records and login state on external websites and services. Unauthorized use arising after card information has been entrusted to another service may be the user’s responsibility under the card issuer’s terms and conditions.
- External execution confirmation: The agent is designed to seek the user’s confirmation before executing payments and tasks that are difficult to reverse, such as placing phone calls, sending email or messages, calling a taxi, and placing orders. However, tasks that the user has entrusted in advance or clearly directed may be executed without asking again. Cancellations, refunds, and the like after execution are subject to the policies of the relevant external service.
- External service credentials: Authentication information, sessions, and tokens for connected external services are stored in encrypted form and are deleted or rendered unusable without undue delay when the user disconnects the service or requests deletion.
- Phone calls: At the user’s request, the agent places calls from an outgoing number provided by the Company, and answers incoming calls within the scope set by the user. Calls to phone numbers outside Korea pass through the line of an overseas carrier (Telnyx LLC) and the Company’s US outgoing number, and incoming calls to that carrier are not answered. The agent discloses to the other party to the call that it is the user’s AI assistant and that the content of the call may be recorded. Call audio is transmitted to the processors under Article 5 for real-time transcription into text and for speech synthesis and is not stored. Transcripts and summaries of call content are stored in the user’s records and used in subsequent conversations and search. The other party’s phone number and statements are processed pursuant to Article 14 in order to perform the call requested by the user.
- Conversation search: The Company stores chat room messages and call records as search indexes so that users can find past conversations. When a message is deleted, it is also deleted from the index.
- Image generation: At the user’s request, the agent sends the request text and reference images (including photos the user posted in the conversation) through OpenRouter to the AI model providers under Article 5 to create or edit images. Generated images are stored in the conversation and can be viewed by its participants. Image generation requests are an exception to the zero-retention condition, and the model provider (OpenAI) may retain them for up to 30 days for abuse monitoring.
Article 11 (Special Provisions for Google API User Data)
- Definition and scope: “Google API User Data” means data that Vooy receives directly from a user’s Google account through Google Workspace APIs and data derived from it. It includes the Google account identifiers, authentication information, Gmail, Calendar, Drive, Docs, Sheets, and Tasks data, and processing results described in Article 2.
- Access and use: The Company accesses and uses Google API User Data only to the minimum extent necessary to provide Gmail search, reading, draft, and label management; Calendar viewing and event management; Drive file search, reading, creation, and permission management; Docs document reading, creation, and editing; Sheets reading, entry, and editing; Tasks viewing, creation, editing, and completion; and to maintain or improve the reliability and quality of these user-facing Google integration, conversation context, and AI agent memory features.
- Storage and deletion: Google OAuth tokens are encrypted and retained until the Google connection is disconnected or the user deletes the account. Google service request data and original processing results are deleted after the request is completed, except that information included in conversation history is retained until account deletion to provide that history to the user. If a persistent preference, setting, relationship, or fact useful to that user is identified from a response containing Google API User Data, Vooy may retain only a concise derived memory for that user and not the original tool result, and such information is not combined with other users’ information to build a general-purpose database. The user may request deletion in a conversation or by emailing privacy@vooy.com, and the memory is deleted upon request or account deletion. When the Google connection is disconnected, related authentication information is deleted or rendered unusable. Even in this case, memory and event copies already created remain until the user deletes them or deletes the account. Where the user has separately consented, the Company may read email from the past 90 days, events from the past 90 days and the next 180 days, and email and events newly received while connected, and create memory in the same manner, and temporary copies of the original text read are deleted without undue delay after the memory is created.
- Limited transfers: Google API User Data may be processed by the service infrastructure of Cloudflare and PlanetScale, the connection relay environment of Composio, and the AI model providers under Article 5 only where necessary to provide a feature requested by the user. When a user asks the AI agent to summarize, draft, organize, or otherwise process Google data, only the minimum Google API User Data necessary to generate the result is processed, and it is not used to develop, improve, or train a model.
- Use in public calls: Only where the user directly calls the agent in a group chat room, Google API User Data and memory created from it are used to the extent necessary to answer that request. The answer is visible to the members of that chat room. They are not used where another member calls the agent.
- Exclusion from analytics and marketing: Original Google API User Data, tool inputs or results, and derived content are not transmitted to Mixpanel, PostHog, Grafana, or any advertising or marketing provider. Limited operational metadata that does not contain Google API User Data, such as feature type, success or failure status, and latency, may be processed solely to improve service quality and reliability.
- Prohibited uses and transfers: The Company does not use or transfer Google API User Data for marketing; advertising; ad targeting, retargeting, personalization, or interest-based advertising; sale; data brokering or information resale; building a cross-user or general-purpose database; credit, lending, or eligibility decisions; or the development, improvement, or training of any AI or ML model, including a generalized or non-personalized model.
- Restrictions on human access: Company personnel do not read Google API User Data unless the user has affirmatively agreed to access to specific data for support, access is necessary to investigate a security issue or misuse, access is necessary to comply with applicable law, or the data, including derivations, has been aggregated and anonymized for internal operations.
- Compliance with Google policy: Vooy’s use and transfer to any other app or service of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace APIs are not used to develop, improve, or train generalized or non-personalized AI or ML models.
Article 12 (Processing of Sensitive Information)
① The Company does not require users to enter sensitive information such as health, religion, or political opinions. However, because conversations and notes entered directly by the user and connected email and calendars have no fixed format and may contain sensitive information. The Company processes it only to the extent necessary to create the answers and memory requested by the user.
② The Company uses such sensitive information to create answers requested by the user and to maintain memory, and may also use it to create answers visible to the entire room when the user directly calls the agent in a group chat room. In addition, where the user participates in appointment coordination, the Company may also use it to create answers shared with other participants. The Company does not use it for any other purpose or provide it to third parties.
③ A user may refrain from entering sensitive content, delete the relevant memory in memory management, or request suspension of the processing of sensitive information by emailing privacy@vooy.com. Upon such a request, the Company deletes the stored memory and stops reading past email and calendar events, and conversation features remain available.
④ Please take care not to enter other persons’ sensitive information. When creating memory by reading past email and calendar events, the Company filters out sensitive content such as financial details, identification numbers, health, and job-seeking activities so that it is not stored as memory, but it is difficult to guarantee that it is filtered out in every case. Answers shared in appointment coordination may also contain sensitive content included in memory or schedules, so please check answers before sharing them and take this into account when turning on automatic answers.
Article 13 (Processing of Personal Information of Children Under 14)
① The Company does not accept account registration by children under 14 years of age, and confirms at registration whether the user is at least 14 years of age.
② Where it is confirmed that a child under 14 years of age has registered, the Company terminates the account and deletes the personal information without undue delay.
Article 14 (Personal Information of Other Persons Entered by Users)
① Information that a user enters or causes to be processed through conversations, attachments, contact syncing, device contacts and calendar synchronization, external account connection, reservations and orders, external browser tasks, appointment coordination, phone calls, and the like may include personal information of other persons, such as email correspondents, event attendees, other participants in group chat rooms, non-users of Vooy in the address book, companions and recipients, the other party to a call, persons registered as numbers from which incoming calls are allowed, and persons appearing in photos, audio, and documents. The Company processes such information pursuant to Article 15(1)(6) of the Personal Information Protection Act to the extent necessary to provide the service requested by the user.
② The Company processes other persons’ personal information only for the purpose of providing the service to that user, and does not accumulate it as a separate profile or use it for recommendations to other users. Phone numbers in the address book are stored only as values converted with a key known only to the Company and are used only to find friends who use Vooy, and are not used for soliciting registration or for recommendations. Where the user has consented to device contacts and device calendar synchronization, the Company stores contact names and phone numbers in encrypted form and uses other persons’ information contained in contacts and events only to process that user’s requests or to identify the caller of an incoming call.
③ The Company does not perform processing that identifies a specific individual from photos or audio.
④ A user who enters another person’s personal information must inform that person in advance.
⑤ A person whose personal information is being processed may request confirmation of the source of collection and the purpose of processing, suspension of processing, or deletion by emailing privacy@vooy.com.
Article 15 (Installation, Operation, and Refusal of Automatic Personal Information Collection Devices)
① Automatic personal information collection devices installed and operated by the Company
- On the Vooy web, the Company uses “cookies,” which store and frequently retrieve the user’s information, to maintain login state and for security verification. In the Vooy app, identifiers such as session information stored on the device are used for the same purposes.
- A cookie is a very small text file sent by the server used to operate a website to the user’s browser, and is stored on the storage device of the user’s device.
- The Company automatically collects error and diagnostic information when the app freezes or encounters an error and app performance diagnostic information (Sentry, Grafana Faro), and, automatically collects app installation and launch information of all users in order to deliver the invitation code to users who installed through an invitation link (Airbridge). For service operation and improvement, the Company automatically collects service usage information with the usage analytics tools in ② below. Collected items and retention periods are described in Articles 2 and 3, and overseas transfers in Article 6.
② Matters concerning the collection and use of behavioral information
- The Company collects service usage information as described below for service operation and improvement (problem diagnosis, stability measurement, and understanding of feature usage). The Company does not collect or use behavioral information or provide it to third parties for personalized advertising, and does not collect sensitive behavioral information that may infringe an individual’s rights, interests, or privacy, such as ideology, beliefs, or medical history.
| Items collected | Collection method | Purpose of collection | Retention and use period |
|---|---|---|---|
| Usage events, the app installation identifier before sign-in, the account identifier after sign-in, session and conversation identifiers, and app, device, operating system, screen, session, and performance information | Automatically collected when the web or app is used (Mixpanel; the app and web send the data to the Company’s server, which forwards it) | Service operation and improvement through analysis of service usage flows and failure points | 730 days from the collection date. Deletion is requested within 30 days after account deletion (the provider’s deletion may take up to 30 more days) |
| Records of the model, tokens, cost, latency, and errors of AI calls, and session and agent identifiers | Automatically collected when an AI request is processed (PostHog) | AI usage cost management and incident response | 1 year after account deletion |
- A user who does not want usage analytics information collected may make a request to privacy@vooy.com or delete their account. Upon such a request, the Company asks the analytics provider to delete that user’s information.
③ The Company does not allow third parties to directly collect behavioral information for personalized advertising purposes through tags or SDKs installed in the Company’s web or app.
④ Users may refuse the storage of cookies, but in that case there may be difficulty using some services, such as login persistence and security verification. The methods of refusal are as follows.
- Chrome: ⋮ at the top right > Settings > Privacy and security > Delete browsing data, then delete cookies and other site data / in Third-party cookies in the same menu, block third-party cookies
- Microsoft Edge: ··· at the top right > Settings > Privacy, search, and services > Tracking prevention, then select a level (Balanced or Strict)
- Safari (iPhone): Settings > Apps > Safari > Advanced > Block All Cookies
- Samsung Internet: ≡ at the bottom > Settings > Privacy and security > Smart anti-tracking settings
※ Menu names and paths may differ depending on the browser, device, and OS version.
⑤ Google API User Data is not used for cookie-based analytics or usage analytics.
Article 16 (Chief Privacy Officer)
The Company designates the following point of contact to oversee personal information processing and respond to privacy complaints and requests.
- Chief Privacy Officer: Seojun Kim (Representative Director)
- Email: privacy@vooy.com
- Support: support@vooy.com
Article 17 (Remedies for Infringement of Rights)
Users may contact the following organizations for dispute resolution or consultation regarding a privacy infringement.
- Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
- Personal Information Infringement Report Center: 118, privacy.kisa.or.kr
- Cyber Investigation Division of the Supreme Prosecutors’ Office: 1301, www.spo.go.kr
- National Police Agency Cyber Bureau: 182, ecrm.police.go.kr
Article 18 (Changes to This Privacy Policy)
This Privacy Policy takes effect on November 20, 2026, and the Company will provide advance notice of changes through the policy page on the Vooy website or by email. When the list of processors and external services changes, the Company also updates the “Processors and External Services List” (a policy page on the Vooy website, vooy.com).
Addendum (Transitional Measures for the Retirement of Messenger Channels)
① On November 6, 2026, the Company ended the provision of the service through Telegram, LINE, and KakaoTalk Consultation Talk. The personal information of users who did not migrate to the Vooy app or web by that date is destroyed by December 6, 2026. Even in this case, conversation content is not retained beyond the retention period set out in the previous Privacy Policy.
② Notwithstanding paragraph ①, information that must be preserved under applicable laws is stored separately from other personal information for the relevant period and then deleted.
③ Conversation records remaining on each messenger service are managed by the operator of that messenger and therefore cannot be deleted by the Company, and users may delete them directly in that messenger.
Addendum (Changes to the Privacy Policy)
This Privacy Policy applies from November 20, 2026. However, matters concerning newly added features such as phone calls and newly added processors apply from the posting date (November 13, 2026). Previous versions of the Privacy Policy can be found in the change history on this page.
Privacy Policy change history
This Privacy Policy applies from 2026. 11. 20..
Previous Privacy Policy versions are available below.