ArcSolve AI Privacy Policy

English

ARC-SOLVE (“we”) explains in this policy what information the Mac app ArcSolve AI (“the app”) handles. The app is a local app that lets an AI client you connect use Apple apps on your Mac over MCP. It consists of the menu bar app, a background service, and the embedded command-line tool arcsolve. The app has no built-in AI model or chat.

This policy applies to the app and to inquiries you send us directly about the app. Visits to our websites that carry the app help and this policy are described in Visits to our websites. Control names in this text follow the app’s English interface. If the English text differs from the Korean text, the Korean text prevails.

Information we handle

• We do not receive the inputs or responses of the personal-app tools below. The app does not send the personal records it processes to our servers or to data-processing servers we designate.
• The app has no sign-up, sign-in, advertising, built-in usage analytics, or tracking. It contains no third-party SDK for those purposes. The app does not use cookies or advertising identifiers.
• The main app and the background service handle Apple app data and have no network entitlement. Only arcsolve, which runs Web collection below, has network access.
• For company inquiries and websites outside the apps, we process information you send us directly and web access information that passes through Cloudflare. See Information we handle when you contact us and Visits to our websites. We receive and use crash reports and app usage statistics provided by Apple. See Crash reports and app usage statistics provided by Apple below.

Information processed on your Mac

The purpose of processing is to carry out requests from the AI client you connect. The app reads or writes only what each request needs. It works within the macOS permissions you grant. Audio files are read only from the folder you connect. Allow AI Client Connections is off by default.

Notes, Mail, and Messages tools send requests to each Apple app through Apple Events automation APIs. For Notes and Mail attachments, tools read only lists and properties; no tool reads attachment bytes. Messages tools do not read past messages or attachments in conversations.

Send commands for Mail and Messages send content through the Apple app to the recipients you specify. Account sync and communication by Apple apps follow those apps’ settings and policies. Reply and forward commands open a Mail window; you send the message in Mail.

Voice Memos reads local files in the Recordings folder you connect. It does not open the app’s recordings database or record through the microphone. It does not transcribe, play back, download from the cloud, or write source files. File names and modification times are not original recording titles or recording dates. Files remaining in the folder may appear in lists even if the Voice Memos app does not show them.

Location

Places and coordinates stored in events and reminders are fields in those records. Allow Location Sharing below applies to the tools for your Mac’s location.

• The app makes a single location request through macOS Location Services only when the AI client you connect asks for it. The response contains the location measurements and measurement times macOS returns. It does not guarantee freshness or the requested accuracy. It does not track your location continuously or keep a location history. The app does not ask for confirmation for each location request, so approval follows your AI client’s execution approval settings.
• Location is processed on your Mac. We do not receive the location the app reads on our servers or retain it as company location records. The app does not send it to our servers or to servers we designate. The main app and the background service, which read the location, have no network entitlement. Processing by macOS Location Services itself follows Apple’s Mac Location Services information and your system settings.
• The location goes through the embedded arcsolve to the AI client on the same Mac that asked for it, and that client processes it. If that client uses a cloud AI service, the location may be sent to the servers of the external AI provider you use. Any later transmission, retention, training, and deletion follow that provider’s policy.
• Consent: in ArcSolve AI Settings, read the notice in the Location Sharing section. Turn on Allow Location Sharing before the app can read your location. It is off by default. Until you turn it on, the app does not read your location or request macOS Location Services permission. You can still use location_service_get, which reads only service status without reading your location. Your consent choice is stored only on your device and is not sent to us. After you turn on Allow Location Sharing, the app still needs macOS Location Services permission to read your location. With Allow AI Client Connections on, a permission request starts from the Location item in Settings or from a request by your AI client. If you have not decided on the permission yet, macOS may ask you. A request from your AI client comes from the background, so macOS may not show a prompt. If precise location is needed, the AI client can separately ask macOS for temporary full accuracy, but macOS may decline without showing a prompt.
• Withdrawal: you can turn consent off at any time. In ArcSolve AI Settings, turn off Allow Location Sharing in the Location Sharing section. Later location requests are then refused. Location already sent to an AI client is not recalled. To remove the macOS permission too, turn off ArcSolve AI in System Settings → Privacy & Security → Location Services. Turning off Allow AI Client Connections in Settings also blocks location requests. Removing the MCP connection from an AI client stops location requests that arrive through that client’s MCP connection. A client that can run commands can still start the embedded arcsolve, so turn off Allow Location Sharing or Allow AI Client Connections to block them.

Location and other results pass through the embedded arcsolve, which has network access for web collection. arcsolve returns personal-tool results as MCP responses to the AI client on the same Mac. It does not send those results to web servers on its own. If your AI client puts results into a web collection request, that content goes to the specified web server.

Information sent to your AI client

Results go from the background service through XPC and an MCP response from the embedded arcsolve to the AI client on the same Mac. Results may include requested record content, location, contact photos, or audio bytes. If that client uses a cloud AI service, the results may be sent to that provider. These results may include information about other people, such as event attendees, contacts, email correspondents, and chat participants.

We do not operate your client or AI provider. Their transmission, retention, training, and deletion follow their own policies. Check those policies and the client’s approval settings before you connect.

The app does not ask for confirmation for each command. Your AI client manages execution approvals. While connections are allowed, any program in your macOS account that runs the embedded arcsolve can call the tools within your macOS permissions.

Web collection

The web collection tool sends requests to addresses that your AI client or you specify. A request contains the address, headers, query, and form or JSON content you specify.

Target servers and redirect servers may receive your IP address and the request content. Web collection does not use cookies, saved credentials, or a URL cache. Do not put passwords or personal records in requests.

Web collection works independently of Allow AI Client Connections. After you turn off connections, the web collection tools in an open arcsolve mcp connection and standalone runs (arcsolve collect, arcsolve mcp --network-only) still work. To disconnect completely, remove the MCP connection from your AI client.

Information kept on your Mac

The app does not separately cache or store the content of the personal records it processes on disk. The following stays on your Mac.

• The connection setting and your location sharing consent are stored in small files in the app’s storage.
• Access bookmarks for the recordings folder and client configuration files you choose, the path of the embedded arcsolve, and the background service registration state are stored in the app’s settings.
• In client configuration files, the app adds or removes only the ArcSolve AI MCP entry. It does not keep a copy of other settings. The app reads the whole configuration file you choose into memory for registration and status checks. It saves through a temporary file. For Codex, it appends an ArcSolve AI managed block to config.toml. The app rewrites the whole Claude Code .claude.json file, so its formatting and key order may change.
• To prevent duplicate execution, the background service keeps request IDs, inputs, and results of change requests, such as write, send, delete, and permission requests, in memory. It keeps running requests and up to the latest 1,000 completed requests. Requests that clearly fail before any effect are removed from the ledger. Nothing is written to disk, and the data is lost when the background service ends. Read requests such as location reads are not kept there.
• Input bytes for notification attachments are temporary files in the app’s storage while the app asks macOS to schedule the notification. The app cleans up those files after native processing of that request ends or fails. Files may remain after an abnormal exit or cleanup failure. Attachments that macOS takes over are managed by macOS. macOS may keep an unused attachment copy even if scheduling fails.
• App diagnostics go to the macOS log. Each personal-app tool call records its time and name, duration, and, if it fails, a reason code. These call logs do not contain tool inputs, results, or location coordinates. macOS determines log retention and deletion. The app itself has no feature that uploads diagnostics to us.

Events, reminders, contacts, notes, mail, sent messages, and notifications that commands create or change are stored in the Apple app or macOS. Their retention and deletion follow that app and macOS. Apple account sync may work separately.

Paths from the app to external recipients

The app does not send the personal records it processes to our servers or to data-processing servers we designate.

Information goes to AI clients, AI providers, web servers, and Mail or Messages recipients because of your connection and requests. Whether it leaves Korea depends on the services you choose.

Disconnecting and deleting

1. In Settings, under Mac App Permissions, open the Voice Memos menu and use Disconnect to remove access to the recordings folder and delete its saved bookmark. This section works only while Allow AI Client Connections is on, so do this before you turn connections off.
2. In the Location Sharing section of Settings, turn off Allow Location Sharing. Later location requests are then refused.
3. In the Agent Connections window that Manage Connections… opens, use Remove to delete the ArcSolve AI entry from Claude Code or Codex. For other clients, remove it in that client.
4. In Settings, turn off Allow AI Client Connections. This blocks new personal-app requests and asks the background service to stop. Work already started is not guaranteed to stop or be undone. Quitting the menu bar app does not turn connections off.
5. In System Settings → Privacy & Security, revoke each macOS permission.

Disconnecting blocks later access. It does not recall information already sent to an AI client. Ask that client and AI provider to delete it.

Before deleting the app, use Remove in Manage Connections… to delete the ArcSolve AI entry from your client configuration. Deleting the app does not delete that entry or the original records in Apple apps. macOS may also keep the app’s storage (settings and access bookmarks).

Crash reports and app usage statistics provided by Apple

These statements apply to App Store builds. If you enable analytics sharing and sharing with app developers, Apple may collect this app’s crash reports and usage statistics. Apple may provide these materials to us. We receive and use these materials from Apple.

Crash reports may include app and operating system versions, device information, and call stacks of the code that crashed. App usage statistics may include session counts, time in the app, and active device counts. We use these materials to analyze crashes, fix errors, understand app usage, and improve app quality.

We view these materials only in App Store Connect and Xcode. We do not download them for separate storage. Xcode may automatically download local copies for viewing. Retention and deletion of these materials follow Apple’s policies. We do not link these materials to you or use them for tracking.

Collection, sharing, retention, and privacy protections within Apple’s services follow Apple’s Privacy Policy and Apple’s App Analytics information.

To refuse future sharing, open Settings on iPhone or iPad, or System Settings on Mac. Under Privacy & Security → Analytics & Improvements, turn off sharing with app developers. See iPhone and iPad analytics information and Mac analytics sharing information for your choices. Stopping sharing does not mean that materials already provided are deleted.

Device information and deletion

• We do not hold personal-app tool inputs or responses, so we cannot access or delete them on your behalf. You disconnect clients and the recordings folder yourself as shown in Disconnecting and deleting.
• Remove in Manage Connections… deletes only the MCP entry; the configuration-file access bookmark and the path of the embedded arcsolve remain in app settings for reconnection. The current interface has no separate control to delete these values.

Safeguards

• If data categories or purposes change, we will update this policy and the App Store privacy details before the change.

• The app runs in the macOS App Sandbox.

• The main app and the background service, which access Apple apps directly, have no network entitlement.

• The background service accepts connections only from the arcsolve command-line tool signed by us.

• The background service checks the current Allow AI Client Connections setting for each request.

• Location tools, except location_service_get which reads only status, check your current location sharing consent at each call.

Children

The app has no accounts and does not ask your age.

Product inquiries

The app has no feature for sending inquiries. When you contact us yourself by email or phone, we handle the information in Information we handle when you contact us.

• Do not include real personal records, passwords, keys, or full logs in your inquiry.

Adding [ArcSolve AI] to the start of the email subject helps us respond faster.

Operator and privacy contact

The operator is 아크솔브(ARC-SOLVE). Our privacy officer is 조경민 (Kyungmin Cho), the representative. Send privacy questions and rights requests to the contact below.

• Email: support@arcsolve.ai
• Phone: 050-6508-1228 (Korea)
• Business name: 아크솔브(ARC-SOLVE) · ArcSolve
• Representative: 조경민(KYUNGMIN CHO)
• Business registration number: 843-54-01035
• Address: 서울특별시 성북구 장위로19길 25, 1동 302호(장위동, 장위 에스하임1), Seoul, Republic of Korea

Information we handle when you contact us

We handle the information below when you contact us directly by email or phone.

We process inquiry email through the processors below. We do not provide inquiry information for another company’s independent use, except where the law requires it.

Deleting inquiry information

• Procedure: When the retention period ends, we delete inquiry emails and records without delay. If a law requires longer retention, we keep them separately from other records for that period and then delete them.
• Method: We delete electronic records, and delete inquiry emails from the mailbox and its trash as well.
• Our deletion of email is separate from completion of deletion within Google’s systems. Google’s deletion process and time limits follow the customer data deletion provisions of the Google Data Processing Addendum.

Processors

We use Google Workspace to receive and store email for support@arcsolve.ai. We use Cloudflare to serve our websites and process web requests. These processors handle company inquiry email and websites. This processing does not send documents, model inputs, or tool results from the apps to Google or Cloudflare. Content you put in an inquiry is processed as inquiry email.

Google’s public contracting entity table identifies Google Asia Pacific Pte. Ltd. for Google Workspace contracts with a Korean billing address. The Cloud Data Protection Team is a channel for our Workspace administrator to contact Google about customer data. Send your privacy inquiries and rights requests to our company contact above. We contact Google through our administrator when needed.

Google’s role in processing customer data is described in the Google Data Processing Addendum. Cloudflare’s processing role is described in the Cloudflare Data Processing Addendum.

Processing outside Korea and your choices

Google and Cloudflare may use facilities and subprocessors in multiple countries under their respective data processing addenda. Inquiry email and web access information may be processed outside Korea while these services are provided.

• The table above lists the inquiry email information processed through Google Workspace. It is sent over the network when email is received. We retain it for one year after we finish handling the inquiry.
• If you do not want to use the Google Workspace email route, contact us by phone instead of email. In that case we do not answer by email.
• Cloudflare processes the IP address and browser request information sent over the network when you open our web pages. Web access information is used to serve pages and for security processing.
• Google’s processing locations and subprocessors are described in the Google Workspace subprocessors information. Cloudflare’s subprocessors are described in the Cloudflare subprocessors information.

Visits to our websites

The websites that provide our company and product introductions, help, and legal documents are static pages. The sites themselves use no cookies, advertising, analytics, or tracking scripts. When you open a page, your IP address and the request information your browser sends pass through Cloudflare’s servers. Our site code has no feature that stores this access information separately.

Your rights and how to use them

• You can ask to access, correct, or delete the personal information we handle about you (your inquiry records), or to stop processing it. Send your request to the contact above. We will explain how we confirm your identity and then handle the request.
• A legal representative or a person you authorize can also make the request.

Safeguards for our websites

Our websites are served over HTTPS. Their Content Security Policy restricts scripts from outside origins, additional network connections from pages, and form submissions.

Inquiries from children

Children under 14 should contact us together with a legal guardian.

Privacy violation assistance

You can also report or ask about a privacy violation to these Korean public bodies.

• Personal Information Infringement Report Center: privacy.kisa.or.kr, 118 (in Korea)
• Personal Information Dispute Mediation Committee: www.kopico.go.kr, 1833-6972 (in Korea)

Changes to this policy

When this policy changes, we publish a new version and its effective date. If earlier versions have been published, they are available in the change history.