About this notice
This notice (version privacy@2026-11-03, effective 3 November 2026) explains how 코어비스(COREVIS) (“COREVIS”, “we”) handles personal information in the COREVIS Windows app, the COREVIS Android app (Google Play, com.corevis.assistant), your COREVIS account, map refines, the phone connection, the account site at account.corevisos.com and this website. We are responsible for it; our details are at the end of this page. COREVIS is offered only in South Korea, the United States, Canada, Australia, New Zealand and Singapore; we do not offer sign-up or purchase in the European Union, the European Economic Area, Switzerland or the United Kingdom.
In short: your personal projects, your personal second brain, the lessons COREVIS learns and your friends list stay on your PC, while team projects are stored on our servers and shared with your team. Our server keeps what it needs to run your account, plan, devices and teams. For a map refine, our server gets only your request and the outline of your map, gives back a reference and keeps neither. The COREVIS Android app is a window onto the COREVIS on your PC from elsewhere: what passes between your phone and your PC is encrypted end to end, so we cannot read or store it, and our server keeps only a record of the phone connection. Paddle collects your payment details itself. We do not sell personal information or use it for advertising. When you use them, your AI provider, Paddle, Google (Google sign-in and Google Play) and Microsoft (which runs the Microsoft Store) handle information under their own privacy policies.
What changes on 3 November 2026: This notice describes how we handle information now, so this version applies to everyone from the day it is posted, 3 November 2026 (Korea time). It replaces privacy@2026-10-26, in force since 28 October 2026. There is no free trial any more, so the section The phone app and the phone connection no longer mentions it; What we process and why (Plan and payments) now lists a free Pro trial still on record and a free Pro period we gave you, and how long we keep them; Service providers and transfers abroad (Namecheap) now also covers the notices we send from our support mailbox. The personal second brain is now on every plan, so What stays on your PC and Lessons no longer describe a plan without it: on Free too, COREVIS hands your memories and lessons to your AI. Nothing else changes. (Corrected on 4 November 2026: why this version applies to everyone; Plan and payments now lists a free Pro trial and a free Pro period we gave you; the Namecheap row now covers the notices we send from our support mailbox.)
What stays on your PC
Your personal projects (their maps and step results), your personal second brain (the app’s memory of results, decisions, preferences and rules, with the lessons described under Lessons) and your friends list (the email addresses and names you add in the app to invite people and give them steps) are stored in the COREVIS storage folder on your PC and are not sent to our server. Only when you invite a friend to a team does the app send us their email address, to send the invitation (see Team invitations), and only when you give a friend a step does their name, with a pseudonymous key instead of their address, go into the team map (see Team projects). Team projects are different; see Team projects below. When your AI works with COREVIS, the app hands project content, related memories, lessons and material you added to the second brain to your AI as part of your conversation, and your AI provider processes them under its own terms. You can view, search and delete memories in the app. Photos, videos, files and text you send from the phone app are placed only in the COREVIS storage folder on your PC (its files folder) and are not kept on our server. A file not fully received waits in a temporary folder inside the storage folder and is deleted 24 hours after the last part arrived. When you put a file you sent into a project step or send it to the master, your PC’s AI (such as Claude Code) reads it to do the work, and what it reads goes to your AI provider as part of the conversation, as above. The pairing details of each paired phone, such as its name, model, phone app and Android versions, public keys and when it was paired, are encrypted on your PC with Windows-protected storage. The work record on your PC shows what you did from the phone as 나 · 폰 (me · phone). Removing the app may not remove the storage folder, so delete it yourself when you no longer need it.
Lessons
COREVIS learns how you like your work done. It learns from your feedback, such as the reason you give when you ask for a step to be done again, a remark when you confirm a step or a change you make to a step in the app, and from your AI looking back at a step it has just finished. Your AI writes each lesson down in a short sentence, and COREVIS applies it to later work right away. Lessons are stored only in the COREVIS storage folder on your PC, with the feedback they came from, which can include your own words. They are not sent to our server and never go into a team map, also when they come from a team project. When your AI works with COREVIS, the lessons that apply are handed to it as part of your conversation. On the app’s 기억 (Memory) screen, under 배운 점 (Lessons), you can see each lesson and where it came from, switch it off or undo it, and turn automatic learning off.
Services you connect yourself
Some things your PC does at your request go straight from your PC to other companies, not through us. When you connect an outside service in the app, such as an MCP server you add or a video or voice service, the app sends that service what the step needs, under your own account with it and its terms. When you download a skill, the app fetches it from GitHub (codeload.github.com), which sees your IP address. Your AI app (such as the Claude desktop app, Claude Code or Antigravity) talks to its own company under its own terms. We do not receive any of this; check each company’s privacy policy.
Team projects
Team projects are the exception to keeping your work on your PC. When you join a team, the team’s projects, including their maps, steps, results, team memories and the record of who did what and when, are stored on our servers at Cloudflare, in the United States with the rest of our account data, and are visible to every member of that team. Other members also see your name, which is the part of your email address before the @, your role and when you joined. Each member’s PC keeps a copy of their team projects, which is removed when they sign out. We keep up to 20 earlier versions of each team project so that it can be restored (fewer if the team reaches its storage limit), and a 30-day history of changes for notifications. Deleted team projects and teams are erased 30 days after deletion.
A step of a team project can be given to one person, and the team map then names that person: a member by their account and name, and a friend invited by email by the name you gave them (or, if you gave none, the part of their email address before the @) and a pseudonymous key made from their email address for that team (HMAC), never the address itself. When the friend joins the team and takes the step, their account replaces the key. The map is stored on our servers and visible to every member of the team, and its change history says who was given which step. Your friends list itself stays on your PC (see What stays on your PC).
Team content is never written to our logs or analytics, and our admin screens show only counts and sizes, not team names, project titles or maps. If you delete your account, you leave your teams; in a team you own, the member who joined earliest becomes the owner. What you contributed stays with the team with the link to your account removed, but names written inside a project, such as who reported a result or who was given a step, remain part of the team’s content. Your data download lists your teams, the invitations you sent and the team projects you created; the maps themselves belong to the team and open in the app.
Team invitations
To invite someone, a team owner enters that person’s email address or chooses a friend from the friends list in the app. We use it to send the invitation through Cloudflare Email Service, and the email says who invited them and to which team. We do not store the address itself: we keep only a keyed pseudonym of it, so that the invitation can be matched to the right account, and a masked form such as s***@example.com that the owner sees. The invitation link expires after 7 days, and we delete the invitation record 30 days after it is accepted, declined, cancelled or expires. Anyone who opens the link while signed in can accept it with their own account, so forward a link only to the person it was meant for. If you receive an invitation you did not expect, you can ignore it or write to support@corevisos.com.
What we process and why
Our account server and services process the information below. “Basis” names the article of the Korean Personal Information Protection Act (PIPA) we rely on.
Account
Items: email address, language and account status; your Google account identifier if you sign in with Google
Purpose: creating and running your account, signing you in and sending account emails
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: until you delete your account; destroyed once the 7 days to undo the deletion have passed
Sign-in security
Items: sign-in codes, session tokens and the one-time links that open account pages in the app’s window (stored only as hashes), when you last signed in, counts of failed attempts and temporary locks (kept under a keyed code of your email address, not the address itself)
Purpose: keeping sign-in secure, signing the app’s window in to your account pages, and stopping abuse
Basis: performing our contract with you and our legitimate interests (PIPA art. 15(1)(4) and (6))
Kept: sign-in codes expire within minutes and are deleted once used; a one-time link works once within 60 seconds and is deleted at the next daily clean-up; session tokens last until you sign out or they expire (in the app’s window, after 12 hours unused and 7 days at most)
Devices
Items: a random device ID made by the app, the device name (your Windows PC name), the app version, the date it was last used and how many personal projects it has (a number only, without titles or content); no IP address and no hardware fingerprint
Purpose: signing you in on your devices, applying the device limit and counting your project slots across your PCs
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: while the device is signed in; deleted 30 days after you remove it
Phone connection
Items: your account ID; the device ID of the PC each phone is paired with; the phone ID (a random value our server makes); a hash of the connection token; when the phone was paired and the day it was last used; pairing QR records (QR number, PC, issue, expiry and use times); why and when a PC’s connection ended; while the phone connection opens to some accounts first, the list of those account IDs. We keep no phone name or model, no IP address and nothing of what passes over the connection, and a phone is not one of your Devices
Purpose: connecting a phone only to the PC it is paired with, refusing phones that were disconnected and phones of PCs that signed out, checking that your plan includes the phone connection, limiting the number of phones per account, sending the new-phone email, and telling the phone why it cannot reach the PC
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: deleted at once when you disconnect the phone on the PC ([연결 끊기] in the phone app deletes only what is on the phone). When that PC signs out or is removed on the account site, its phones can no longer connect, and their records are deleted when our server next checks (for example when a phone tries to connect again, and within a few minutes for an open connection). In any case deleted 90 days after the day last used. QR records are deleted an hour after they are issued, and the record of a PC’s ended connection when that PC connects again (only the latest 16 PCs per account are kept). If you ask to delete your account, every device is signed out, which also ends the phone connections, and once the account is deleted 7 days later, all remaining records are deleted within a day. The list of early accounts is deleted when the phone connection opens to everyone
Age check
Items: the rule you passed (19+ or 18+), the wording version and the time; where you live and your birth year and month are used for the check and not stored
Purpose: making sure only adults have accounts
Basis: performing our contract with you and our legitimate interest in protecting minors (PIPA art. 15(1)(4) and (6))
Kept: until you delete your account
Plan and payments
Items: plan and team project slot subscriptions, their status, billing period, next payment date and amount; a free Pro trial still on record (when it began, when it was to end, and when and why it actually ended); a free Pro period we gave you (when we gave it, for how many days, when it began and when it ends, and when we took it back); from Paddle: your Paddle customer ID, subscription and transaction references, amount, currency, date, email address and country
Purpose: applying your plan and your team project slots, handling renewals, cancellations and refunds, and keeping transaction records
Basis: performing our contract with you and a legal obligation under the Korean E-Commerce Consumer Protection Act (PIPA art. 15(1)(4) and (2))
Kept: 5 years (contract, withdrawal and payment records); a free Pro trial still on record and a free Pro period we gave you: until you delete your account
Consent records
Items: account ID, time, wording version, plan or team project slot, interval, price and currency, the country of your connection when you opened the checkout, the state of each box, the Paddle transaction and subscription IDs, and the version of the terms you accepted
Purpose: proving what you agreed to and confirmed, and that the purchase was offered where you were
Basis: a legal obligation (PIPA art. 15(1)(2))
Kept: 5 years
Map refines
Items: your request (up to 2,000 characters) and the outline of your draft map (step names, kinds and order); how many references your account got this hour and today
Purpose: giving your AI a reference and applying the hourly and daily limits
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: the request and the outline are not stored; the counts only as long as the limits need them
Earlier map refines
Items: for each map refine our AI ran before this notice applied: when it ran, whether it counted, the model, and its token count and cost
Purpose: keeping the record of the service we provided
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: until you delete your account; after that only as totals not linked to you
Teams
Items: team name; each member’s account, role and date joined (other members see you by the part of your email address before the @); the team project slots you hold, with each one’s state and renewal date, and the team projects they hold
Purpose: running teams and applying team project slots
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: while the team exists; your membership ends when you leave or are removed; erased 30 days after the team is deleted
Team projects
Items: each team project’s map, steps, results, team memories and title, the people its steps are given to (by name, and for a friend invited by email by a pseudonymous key instead of the address), who changed what and when, short change summaries, and up to 20 earlier versions
Purpose: storing team projects and keeping them in step for every member of the team
Basis: performing our contract with you (PIPA art. 15(1)(4))
Kept: until the project or the team is deleted, then erased after 30 days; the change history is kept for 30 days
Team invitations
Items: the email address of the person invited (used to send the invitation, then kept only as a keyed pseudonym and a masked address), the team, who invited them, the status and the expiry
Purpose: sending invitations and matching them to the right account
Basis: performing our contract with the owner who invites, and our legitimate interest in delivering the invitation (PIPA art. 15(1)(4) and (6))
Kept: until 30 days after the invitation is accepted, declined, cancelled or expires
Support email
Items: your email address, message and attachments
Purpose: answering you and handling complaints and disputes
Basis: performing our contract with you, our legitimate interests and a legal obligation (PIPA art. 15(1)(4), (6) and (2))
Kept: 3 years
We process all of the above without asking for your consent, on the legal bases shown (PIPA art. 22(3)); none of it is based on consent. You need to give an email address to have an account; without it we cannot provide the account, map refines or paid plans. We do not make decisions about you based only on automated processing.
Where it comes from
You give us most of it when you sign up, use the app and write to us. The app creates the device ID and reports its version. If you sign in with Google, we receive your Google account identifier and email address from Google; Google is a source here, not a recipient. When you subscribe to a plan or a team project slot, Paddle collects your details in its checkout and sends us your subscription or purchase status, Paddle customer ID, email address, country and the transaction details. If a team owner invites you, the owner gives us your email address, and if a member gives you a step of a team project, their app writes your name into the team map (before you join, with a pseudonymous key of your email address). Cloudflare tells our server the country of your connection. Our server makes the phone ID and the connection token at random when a phone pairs; the token stays only on the phone, and our server keeps only its hash. The COREVIS on your PC tells our server which PC a phone is paired with when pairing finishes. The phone app tells your PC alone, inside the encrypted connection, the phone’s name and model when it pairs.
Map refines
When your AI asks for a map refine, the app sends our server your request (up to 2,000 characters) and the outline of your draft map: its step names, kinds and order, without methods, inputs or results. The server compares the outline with similar maps in our private vault and returns only a reference (checks, number ranges and how your draft differs). It does not send the examples, calls no AI and stores neither the request nor the outline; for the hourly and daily limits it keeps only how many references your account got. Your own AI then refines the map, under its provider’s terms. Map refines by our AI, which sent your request and draft map to Anthropic with a pseudonymous ID for your account, ended on 28 October 2026; Anthropic deletes what it received within 30 days, but may keep content flagged for a usage-policy violation for up to 2 years. We do not use your content to train AI. Please do not put sensitive information about yourself or other people into maps you send for refining.
What we do not keep
Apart from team projects, which we store so that your team can share them, our server does not keep the content of your work: no conversations, prompts, maps, memories, lessons, friends lists or project names. Nor does it keep what passes over the phone connection (screens, projects, the master chat, approvals, the files and text sent from the phone and the results received from your PC), which is encrypted end to end so that we cannot read it. Our server’s phone connection code does not read IP addresses, stores no phone name, model or network number, and counts its requests only as above. Our database stores no IP addresses and no hardware fingerprints, and we keep no access logs: the request logs, traces and log exports of our servers are switched off, and we count requests and errors only by route, result and response time, with no account ID, IP address or content. We read the country of your connection in memory to apply the age rule when you sign up, to show prices in your currency and check that we sell where you are, and to check whether map refines are available in your region; we keep it only in your checkout record (see Consent records). Cloudflare, which runs our servers and this website, processes IP addresses and request details to deliver and protect the service, including the Turnstile check; its own operational records follow Cloudflare’s privacy policy. We never see your full card number.
Payments and Paddle
Paddle sells COREVIS subscriptions (plans and team project slots) as merchant of record and is an independent controller of the information it collects. When you subscribe, the account page opens Paddle’s checkout and passes only a checkout reference; we do not fill in your email address or account ID for Paddle. You enter your email address, payment and billing details directly in Paddle’s checkout, and Paddle handles them under its privacy notice (paddle.com/legal/privacy). Paddle then sends us the subscription and transaction details listed above, so that your plan and your team project slots are linked to your account.
Account pages in the app
In the COREVIS app, the plans, subscription management and device pages open in a window of the app instead of your browser. It is the same account site (account.corevisos.com), and no new information about you is collected there. To open a page, the app asks our server for a one-time sign-in link: it works once, within 60 seconds and only in that window, and we keep it only as a hash, with your account, the device that asked and the page, until our next daily clean-up deletes it. The window is then signed in to your account with a session tied to that device, which ends after 12 hours without use, 7 days after it began at the latest, and at once when that device signs out or is removed. The window keeps the account site’s cookies in its own storage on your PC and clears them whenever the app’s sign-in ends. Paddle’s checkout and customer portal open in the same window and follow Paddle’s privacy notice; this website, including these policy pages, opens in your browser. You still sign in to the app in your browser.
The phone app and the phone connection
The COREVIS Android app (the “phone app”) is a window onto the COREVIS running on your PC. The phone app has no sign-up or sign-in of its own. On a PC where COREVIS is signed in to your account, you open a QR code in 설정 › 내 폰 › [폰 연결하기] (Settings › My phone › Connect a phone), scan it with the phone app and type the six-digit number the phone shows into the PC; this pairs that phone with that PC. A phone pairs with one PC only, and an account can connect up to 2 phones. Your projects and files stay on your PC and the phone app does not store projects, so the phone connection works only while your PC is on and COREVIS is running there, signed in to your account. The phone connection comes with Pro and Max, not with Free. The tour on the phone app’s first screen shows only sample material built into the app and connects to neither our server nor your PC.
Your phone reaches your PC through our server (mcp.corevisos.com), over the connection your PC keeps open to our server. When they pair, the phone and the PC pin each other’s public keys, and everything between them is encrypted end to end with mutually authenticated TLS 1.3, so our server and Cloudflare cannot read, change or store what passes between them. That includes the screens, projects, the master chat, what you approve, the photos, videos, files and text you send from the phone with their names, types and location data, and the results you receive from your PC. To decide whether to allow a connection, our server checks the state and plan of your account and whether that PC is still signed in.
Our server stores only the record of your phone connections: your account ID, the device ID of the PC each phone is paired with, a phone ID our server makes at random for each phone when it pairs, a hash of the connection token that only the phone holds (not the token itself), when the phone was paired and the day it was last used (updated at most once a day). It also stores each pairing QR code’s number, the PC that opened it and when it was issued, expires and was used, and why and when a PC’s connection ended (quit, restarted, signed out or lost). While the phone connection is open only to some accounts first, the list of those account IDs is kept in our server’s settings. Why we keep this record and for how long is under What we process and why. When a newly paired phone first connects, we send one email to your account’s email address with when it was paired, the name of the PC (as listed under your devices) and a link to the account site’s devices page, so that you notice a phone you do not know.
Our server passes the encrypted data on without opening it. When a connection opened and closed, how many connections are open, the size and timing of the data passing through, and a random number that notices when your phone changes network are handled only while the connection is open, for flow control and usage limits, and are not stored; like every other request, connections are counted only by route, result and response time, without account ID, IP address or content. The size and timing of the data could suggest how the link is used, such as playing a video or sending a large file, but we do not record or analyse them. Your phone’s name and model go only to your PC, inside the encrypted connection, never to our server. Our server reads the app and Android versions the phone app sends when it connects only to check that the app is not too old, and does not store them; it does not read the PC name your PC sends when it connects. Cloudflare processes IP addresses to deliver and protect the service; our server’s phone connection code does not read IP addresses.
Location data in photos and videos is removed on the phone before they are sent, by default, and your PC checks once more after receiving them that none is left. If the phone cannot remove it from a file, it tells you first, and if you choose to send the file anyway, it reaches your PC with its location data. Only if you turn on 사진·영상의 위치 정보 함께 보내기 (Send location data with photos and videos) in the phone app’s settings does the location data go to your own PC, and even then it is encrypted end to end, so we neither receive nor use it. If your PC’s AI reads a file sent with location data, or the file is uploaded somewhere, the location data can go with it. Location tracks recorded separately inside a video, and text or signs visible in a photo, cannot be removed. The phone app does not ask for location permission.
The phone app’s permissions
The phone app needs no permission to work. It asks for two optional permissions, through Android’s own prompt, the first time you use the feature that needs them. If you refuse, you can still use the rest of the service, and you can change the app’s permissions at any time in your phone’s settings.
· Camera (optional): scanning the QR code that pairs your phone with a PC, and taking photos and videos in the phone app. Without it you can still use the tour, the screens of a PC you have already paired with, and choosing and sending photos and files; pairing with a new PC needs it, because the QR code must be scanned.
· Notifications (optional, Android 13 and later): showing the progress of sending from your phone to your PC and of [폰에 저장] (Save to phone). The app asks once, the first time you send or save from outside the app; sending and saving work without it.
The phone app also uses these features. Biometrics unlock the app (a biometric such as your fingerprint, or the phone’s screen-lock code) and approve requests (a biometric only). Your phone’s Android does the biometric check; the phone app and we never receive biometric data, only the result. Pairing with a PC needs a screen lock and a strong biometric, such as a fingerprint, enrolled on the phone. Internet, network state and user-initiated transfer jobs connect to your PC through our server, reconnect when you move between Wi-Fi and mobile data, and finish a send or download you started even if you close the app; Android does not ask for these.
The phone app does not ask for storage, photo and video reading, location, contacts, microphone, phone or SMS permissions. It reads only the photos and files you pick in Android’s photo picker or file picker, or share to it from another app.
The phone app keeps the following on your phone. The pairing details (the fingerprint of your PC’s public key, the connection token and the relay address) are encrypted with a key in the phone’s Android Keystore. It also keeps your screen settings (such as theme and text size), a cache of the COREVIS screen code your PC sends (cleared when the COREVIS version on your PC changes) and the list of things waiting to be sent (the latest 20, encrypted). Temporary copies of results you open are deleted when the app has been locked for more than 30 minutes or the link is ended. The phone app does not use Android backup and contains no advertising, analytics or crash-reporting tools. When you press [연결 끊기] (Disconnect) in the phone app, or once the phone hears that it was disconnected on the PC, the phone app deletes its keys, the pairing details, the screen data, the temporary copies and the list of things to send. Files you saved with [폰에 저장] (Save to phone) and photos and videos you took in the phone app stay in the COREVIS folders of your phone’s Pictures, Movies, Music and Download, also after you disconnect. The phone app does not read the schedules, photos and memories that the earlier app (2.0.x) left on your phone; they are deleted when you press [예전 판 자료 지우기] (Delete data of the earlier version) under the phone app’s 설정 › 앱 정보 (Settings › About the app), or when you remove the app.
Google Play installs and updates the phone app, and Google handles information under its own privacy policy. In Google Play Console we see statistics that Google compiles, such as install counts and crashes.
Service providers and transfers abroad
We entrust the work below to these providers, which process information outside Korea. The legal basis is that this processing and storage is needed to make and carry out our contract with you, and that we disclose it here (PIPA art. 28-8(1)(3)). Each provider lists its own sub-processors on its website.
Cloudflare
Recipient and contact: Cloudflare, Inc. (101 Townsend St., San Francisco, CA 94107, United States · privacyquestions@cloudflare.com)
Country: United States; requests also pass through Cloudflare’s data centers around the world
What is transferred: all the account-server information above, including teams, team projects, invitations and phone connection records; the emails we send, with the recipients’ email addresses; the requests your app, phone app and browser make, including IP addresses; and the encrypted data passing between your phone and your PC, which we and Cloudflare cannot read and do not store
When and how: whenever you use the app, the phone app, the account site or this website, over encrypted connections
Purpose: running our servers and database (Workers, the D1 database, Durable Objects and Queues), storing team projects and keeping them in step, relaying the connection between your phone and your PC (Durable Objects, in the United States), the Turnstile bot check on the account site’s sign-in page, this website’s visitor statistics (Web Analytics) and sending our emails, including team invitations (Email Service)
How long they keep it: for the periods in this notice, and not after our contract with Cloudflare ends
Legal basis: PIPA art. 28-8(1)(3)
How to refuse, and what happens: do not create an account, or delete it; without Cloudflare we cannot provide the account, map refines, paid plans or this website. If you do not use the phone app, no phone connection information is transferred, but you cannot use the COREVIS on your PC from your phone
Namecheap
Recipient and contact: Namecheap, Inc. (4600 East Washington Street, Suite 305, Phoenix, AZ 85034, United States · legal@namecheap.com · namecheap.com)
Country: United States
What is transferred: emails you send to support@corevisos.com, our replies and the notices we send from support@corevisos.com, with the email addresses and attachments
When and how: when you email us or we email you, by email
Purpose: hosting our support mailbox (Private Email), from which we also send notices
How long they keep it: 3 years
Legal basis: PIPA art. 28-8(1)(3)
How to refuse, and what happens: do not email us; you can still use the app and the account page, but we cannot answer you by email. Notices about your account are sent while you have one and stop when you delete it
How long we keep it
We keep personal information only as long as the purposes above need it, and then destroy it without delay. When you ask to delete your account, you can change your mind for 7 days; after that we destroy your account, device, plan and usage records. Deleted team projects and teams are erased after 30 days, and invitation records 30 days after the invitation closes. Phone connection records are deleted at once when you disconnect the phone on the PC, after 90 days without use, and within a day after the account is deleted (see Phone connection under What we process and why). Records the law requires us to keep are stored separately, used only for that purpose and destroyed when their period ends:
• contract, withdrawal and payment records: 5 years (Korean E-Commerce Consumer Protection Act)
• consent and confirmation records: 5 years
• complaint and dispute records, including support emails: 3 years (E-Commerce Consumer Protection Act)
• records of how we displayed and advertised COREVIS: 6 months (E-Commerce Consumer Protection Act)
Copies in backups are overwritten within about 6 weeks. We delete electronic records so that they cannot be recovered, and we keep no paper records with personal information.
Your rights
You can ask to see, correct or delete your personal information, to stop us processing it, and to withdraw any consent you gave. On the account page you can download the information our server holds about you (including your teams, the invitations you sent and the team projects you created, but not the phone connection records), remove devices and delete your account. To correct your information, such as your email address, or for anything else, write to support@corevisos.com. You can end a phone connection at any time with [끊기] (Disconnect) in 설정 › 내 폰 (Settings › My phone) on the PC, which deletes that phone’s record on our server at once. [연결 끊기] (Disconnect) in the phone app’s settings deletes the pairing on the phone; the record on our server then goes when you disconnect the phone on the PC, or after 90 days without use. If you lose your phone, remove the PC it is paired with on the account page: every phone paired with that PC is disconnected and its record deleted. You can see your account’s phone connection records (the day each phone was paired and last used) in 설정 › 내 폰 on the PC; for anything else about them, write to us. A legal representative, or someone you authorize, can also make a request for you; we will ask for proof of the authority. We act on requests within 10 days. If we refuse or limit a request, for example because the law requires us to keep a record, we tell you why and how to object, and you can object by replying to us. Depending on where you live, you can also complain to your data-protection authority. Information on your PC is under your control; we cannot see or delete it.
Your right to object
You can object at any time, on grounds relating to your particular situation, to processing we base on our legitimate interests, and you can ask us to stop processing your personal information. We then stop, unless the law requires the processing, we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the information to establish, exercise or defend legal claims. If stopping means we cannot provide a service you signed up for, we tell you, and you can end the contract. We never use personal information for direct marketing. To object, write to support@corevisos.com. This is the right to ask for processing to stop under article 37 of PIPA and, wherever the EU GDPR applies, the right to object under its article 21.
If you are in the United States
We do not sell personal information or share it for cross-context behavioral advertising. Do Not Track: we do not track you across other websites or online services, and we do not let third parties do so through COREVIS, so we do not respond differently to Do Not Track signals. Other companies collect information through our service only as this notice describes: Cloudflare (hosting, the Turnstile check and cookieless analytics), Paddle (its checkout) and Google (if you choose Google sign-in). The categories of personal information we collect and the providers we use are listed above, and you can review and correct yours on the account page or by writing to us. Nevada residents: we do not sell covered information, and you can send requests to support@corevisos.com. COREVIS is not directed to children under 13. We tell you about material changes to this notice by email or in the app before they take effect.
This website
This website is hosted on Cloudflare Pages, and Cloudflare processes network information such as IP addresses to deliver and protect it. There is no checkout, sign-in, upload form or account sign-up here; the Sign in link at the top opens the account site, where you sign in, subscribe and manage your account. The interactive examples on the home page run only in your browser: they send nothing and use no AI. On your first visit to the address without a language, the website asks our server for the country of your connection to choose the Korean or English page; the answer is used once and not stored. We measure traffic with Cloudflare Web Analytics, which receives page views, page paths and referrers, country, device type, browser, operating system and page-loading performance, without cookies or localStorage and without fingerprinting. We use no advertising pixels or session replay. Cloudflare privacy information: cloudflare.com/privacypolicy
Children
COREVIS accounts are only for adults, and COREVIS is not directed to children. We do not knowingly collect personal information from children under 14, or under 13 in the United States. If we learn that we have, we delete it without delay and close the account. The COREVIS Android app is not directed to children either, and it neither creates accounts nor asks for personal information. Contact: support@corevisos.com
How we protect it
Administrative: only the people the company designates to handle personal information can reach it, and each only as far as their role needs. The roles are running the service (accounts, plans, devices and teams, and security checks) and support (answering you and handling refunds and cancellations). The providers we use are bound by contract to protect it.
Technical: traffic between the app, the websites and our servers is encrypted, and our hosting provider encrypts stored data. Sign-in codes and session tokens are stored only as hashes, and the app keeps its sign-in token in Windows-protected storage on your PC. The people who handle personal information reach our servers’ data only through the company’s Cloudflare account, in its dashboard or command-line tools, signed in with two-step verification. Sign-in attempts are limited, bots are blocked with Turnstile, and we keep our software up to date. Between your phone and your PC, traffic is encrypted end to end with mutually authenticated TLS 1.3, and each side pins the other’s public key. The phone’s connection and approval keys are kept in its Android Keystore (in a security chip where there is one) so that they cannot be taken out, and the connection key cannot be used while the phone is locked. Important requests, such as approving a step that acts outside your PC, are accepted by the PC only when signed on the phone with a biometric. Our server stores phones’ connection tokens only as hashes, and the list of paired phones is encrypted on your PC. The phone app does not use Android backup, blocks screenshots of its lock, pairing and settings screens, and by default blocks screenshots of the open COREVIS screen.
Physical: we run no servers of our own; our data sits in Cloudflare’s data centers, which control physical access, and we keep no paper records with personal information.
If a leak happens
If we learn that personal information has leaked or may have leaked, we tell the people affected within 72 hours: what leaked, when and how, what we are doing about it, what you can do, and whom to contact. We also report it to the authorities where the law requires.
Privacy officer and help
Privacy officer: Jo, Hwarin (representative) · phone: +82-10-2429-9547 · support@corevisos.com
Send privacy questions, requests and complaints to the same address. Please do not send passwords, keys, sign-in codes or your project files. If you are in Korea and need more help, you can contact the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr), the Personal Information Infringement Report Center (118, privacy.kisa.or.kr), the Supreme Prosecutors’ Office (1301, spo.go.kr) or the Korean National Police Agency (182, ecrm.police.go.kr).
Changes to this notice
We update this notice before we start any new kind of processing. We tell you about material changes by email or in the app before they take effect, and the version and effective date at the top of this page change. History: privacy@2026-11-03 (effective 3 November 2026) drops the free trial and follows the personal second brain on every plan, as described at the top of this page; privacy@2026-10-26 (effective 28 October 2026) followed the new plans of terms@2026-10-26 and the end of map refines by our AI, and was posted again on the evening of 27 October 2026, before it applied, with the COREVIS Android app and the phone connection added; privacy@2026-10-22 (effective 22 October 2026) added team maps, the friends list, lessons and the account pages in the app to privacy@2026-10-19; privacy@2026-10-19 (effective 20 October 2026) corrected privacy@2026-10-15 (effective 18 October 2026) to match how we handle information; privacy@2026-10-15 replaced the earlier notice, which covered this website only, for the launch of the COREVIS app and paid plans.
Who is responsible
The business responsible for your personal information is:
Business name COREVIS (registered in Korea as 코어비스(COREVIS)), a sole proprietorship
Representative Jo, Hwarin (조화린)
Business registration number 307-47-01114 · KFTC business information
E-commerce registration 2026-Gyeonggi-Songtan-0698 · filed with Pyeongtaek City Songtan Branch Office
Business address 100 Godeokjungang 2-ro, Pyeongtaek-si, Gyeonggi-do, Republic of Korea
Phone +82-10-2429-9547 · hours: Weekdays 10:00–18:00 (KST)
Email support@corevisos.com
Hosting provider Cloudflare, Inc.