Agentlas
Agentlas
← Back to app
Legal

Privacy policy

How Appbridge Inc. (주식회사 앱브릿지) handles personal data in the Agentlas service, under the Korean Personal Information Protection Act. Revised 17 November 2026, effective 24 November 2026 (adds what the mobile app's personal agent processes and the notification delivery providers; see section 13).

1. Why we process personal data

  • Registration, authentication, identity checks, and account management
  • Providing Agent Cloud storage and the free Hub: publication, discovery, file viewing, discussions, comments, experience-chip sharing, and bookmarks
  • Running the mobile app's personal agent (the phone agent): generating its responses, keeping memory, running scheduled tasks, passing messages and work to desktop agents, and delivering phone notifications
  • Subscription payments and historical one-time credit purchases, invoicing, refunds, and payment-fraud prevention
  • Resolving historical payment claims, refunds, disputes, and legally required transaction retention
  • Keeping the Service stable, responding to incidents, and investigating abuse
  • Building a shared, anonymous catalog of what third-party apps can do, only when a user turns on the desktop app's “Explore this desktop's apps” setting
  • Meeting obligations imposed by law

2. What we hold, and for how long

Account
Email, social sign-in identifier, display name, plan, session state — until the account is closed
Usage
Agent Cloud records, Hub bookmarks, agent call history, credit ledger, audit events — deleted on closure, except where the law requires retention
Billing
Payment and subscription status, order and subscription identifiers, and refund records — contract, withdrawal, payment, and supply records: 5 years; consumer complaint and dispute records: 3 years under Korean e-commerce law. Routine benefit eligibility history is not automatically a 5-year legal record.
Historical transactions
Previously collected payout details, verification results, and settlement records only as needed for outstanding transactions or legal retention. New creator-settlement collection is discontinued. Contract, payment, and supply records: 5 years; consumer complaint and dispute records: 3 years under Korean e-commerce law. Unnecessary information is deleted.
Personal agent in the mobile app (phone agent)
Agent settings (name, look, speaking style, language, time zone), conversation messages and attached photos and text files, files the agent creates, memory (information about you and short quotes of the words it came from), contacts at a time you asked for and scheduled tasks, messages and work sent to desktop agents, and notification registration (notification address, operating system, app build number, time zone, whether notifications are allowed, whether a desktop is paired) — until the account is closed. The oldest messages are deleted once a conversation grows beyond a set size, and after 180 days without account activity the conversations, photos, files, memory, scheduled requests, agent settings, and notification registrations from before that period are deleted automatically. A notification registration is deleted on sign-out or when the phone has not opened the app for 60 days; a scheduled request once it runs or is cancelled; the earlier version of a replaced memory after 30 days. Messages and work sent to a desktop are kept as long as needed to deliver them and report the result. After the account is deleted, a record holding only the account identifier and the deletion times is kept for 30 days. Approximate location and phone status that you allow the agent to read are used only to generate the response and are not stored separately. Details: https://agentlas.cloud/mobile/privacy
Access
IP address, access time, browser and device information — 3 months under the Korean Protection of Communications Secrets Act
App capability catalog (optional)
Only if you turn on “Explore this desktop's apps” in the desktop app: anonymous descriptions of what third-party apps can do (app identifier and version, capability name, parameters, and steps) and a salted code used to count distinct installations — kept without a fixed expiry while the catalog is maintained; no account, IP address, or device details are stored with them

We do not collect or store card numbers or other payment instrument details. The seller or payment processor shown at checkout and on the receipt handles that information under its own policy.

Public community content

Published agent descriptions, display names, discussions, comments, and experience chips are visible to other users. Files in releases whose authors allow source disclosure may be viewed and downloaded. Do not publish secrets, other people's personal data, sensitive information, or national identifiers. Keep material private in Agent Cloud instead of publishing it to the Hub when you do not want public access. Request unpublishing or deletion at appbridge@appbridge.co.kr. Copies already lawfully downloaded by others cannot necessarily be recalled.

Historical records and data minimisation

Following the end of paid agent commerce, legally required transaction records are retained separately only for their applicable purpose and period. Ending settlement does not justify indefinite retention of identity documents or payout information. Information no longer needed and without a legal retention basis is subject to deletion. Free Hub access does not require new payout-account or settlement identity-verification information.

Optional app capability catalog (desktop app)

The Agentlas desktop app has a setting, “Explore this desktop's apps”, that is off until you turn it on. When it is on, the desktop may look at how the third-party applications installed on your computer can be operated (for example which menu commands they offer and which scripting-interface entries they publish) and may send what it derived to us as anonymous, content-free descriptions: the application's identifier, name, and version, and the capability's name, parameters, and the steps or interface reference that perform it. It never sends documents, screen contents, file names, text you typed, clipboard contents, your account identity, or anything about what you do with those applications. Before sending, the desktop removes anything that looks like a credential, an e-mail address, a personal file path, or a long number, and our server screens every record again and discards any that fail.

What we keep: each description is stored once in a shared catalog together with the application versions it was seen in, how strong the evidence is, and how many distinct installations reported it. An installation is counted only by an irreversible code derived from a random installation identifier and a secret value held on our server; the identifier itself, your IP address, your account, and your browser or device details are not stored with the description (ordinary access logs are covered by “Access” in section 2). We keep these records without a fixed expiry for as long as the catalog is maintained, to give every Agentlas user a shared, growing catalog of what apps can do. They are stored with the processors in sections 4 and 5. Because they are not tied to your account, they cannot be traced back to you and are not deleted when you close your account.

How to refuse: leave the setting off, or turn it off in the desktop app at any time; nothing further is sent. Records already contributed are anonymous and stay in the catalog. Questions: appbridge@appbridge.co.kr.

3. Disclosure to third parties

We do not disclose personal data to third parties except with the data subject's consent, where a statute specifically provides for it, or on a lawful request from an investigating authority.

For a Paddle purchase, the seller is the Paddle entity shown on the receipt. Paddle separately handles payment instrument, billing, tax, and refund data as a seller under its own privacy policy; we receive the order and subscription identifiers and payment outcome needed to confirm access and support the customer. For Google or Apple sign-in, the selected identity provider authenticates the user under its own policy and sends us the account identifiers the user agreed to share.

4. Processors

나이스정보통신㈜ (NICEPAY)
Payment processing, invoicing, and refunds for transactions made through NICEPAY
MongoDB, Inc. (Atlas)
Service data storage
Railway Corp.
Application hosting
Anthropic, PBC
Response generation for hosted AI (Agentlas Light, Normal, Hard) and the mobile app's personal agent (the phone agent) — primary provider
OpenAI, L.L.C.
Response generation for hosted AI and the phone agent — standby provider, used only when the primary provider is unavailable
Google LLC
Phone notification delivery (Firebase Cloud Messaging)
Apple Inc.
iPhone notification delivery (Apple Push Notification service)

Each processing agreement covers the safe handling of personal data, and we supervise compliance. Changes to the processors or the work entrusted to them are published in this policy.

5. Transfer outside Korea

The legal basis for the Railway, MongoDB Atlas, Anthropic, OpenAI, Google and Apple processing or storage transfers listed below is Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act: they are necessary to perform the service contract, and the transfer details are published in this policy.

Railway Corporation · California, United States
Application hosting and request processing. Account identifiers, request content, and connection/security records are transferred over the network when the service is used. They are processed within the applicable retention periods in section 2. Contact: privacy@railway.com.
MongoDB, Inc. (Atlas) · United States
Storage of account, workspace, public community, subscription, and usage records. Those records are transferred over the network while the service is used and processed within the applicable retention periods in section 2. Contact: privacy@mongodb.com.
Anthropic, PBC · California, United States
Response generation for hosted AI (Agentlas Light, Normal, Hard) and the mobile app's personal agent (the phone agent). Items: the conversation text, attached images, tool results and instructions a user submits to hosted AI or the phone agent. For the phone agent this includes the agent settings, its memory about the user, recent conversation, the content of scheduled tasks, and the approximate location and phone status the user allowed; when the agent uses web search or reads a web page, the search terms and page addresses are also sent. Any of these may include personal data the user put in them. When and how: sent over encrypted HTTPS each time a request is made to hosted AI or the phone agent. Purpose: generating the response. Retention: the time needed to generate the response plus the short retention period (typically up to 30 days) the provider keeps for safety and abuse review under its API terms; we do not ask the provider to keep this content longer. Account identifiers such as the sign-in email are not sent. Contact: privacy@anthropic.com.
OpenAI, L.L.C. · California, United States
Response generation for hosted AI and the phone agent (standby). Same items, timing, method and purpose as Anthropic above, sent only when the primary provider cannot serve the request; web search and web page reading are not handed to the standby provider. Requests are sent with provider-side conversation storage turned off; retention is the time needed to generate the response plus the short retention period (typically up to 30 days) the provider keeps for abuse review under its API terms. Contact: privacy@openai.com.
Google LLC · California, United States
Phone notification delivery (Firebase Cloud Messaging). Items: the notification address (registration token) of the phone that receives the notification, the notification content (which may contain part of an agent's message, an approval request notice, or, for a hand-off notice, the agent's name) and notification identifiers. When and how: sent over encrypted HTTPS each time a notification is sent. Purpose: delivering notifications to the phone. Retention: the time needed to deliver the notification; a notification that cannot be delivered is discarded once the validity period we set (at most four weeks) ends. Account identifiers such as the sign-in email are not sent. Contact: https://firebase.google.com/support/privacy/dpo.
Apple Inc. · California, United States
iPhone notification delivery (Apple Push Notification service). A notification that has passed through Google LLC is delivered to the iPhone through Apple. Items: the notification address of the receiving iPhone and the same notification content as in the Google LLC row. When and how: sent over an encrypted network each time a notification is sent. Purpose: delivering notifications to the iPhone. Retention: the time needed to deliver the notification; a notification that cannot reach the device at once may be kept for that notification's validity period. Account identifiers such as the sign-in email are not sent. Contact: https://www.apple.com/legal/privacy/contact/.

To refuse a transfer, contact appbridge@appbridge.co.kr or stop using the relevant feature. That feature may then be unavailable; we will explain statutory rights and available alternatives. If you use neither hosted AI nor the phone agent, nothing is sent to Anthropic or OpenAI. If you turn off Agentlas notifications on your phone, no notification content is sent to Google or Apple. When you use your own API key (BYOK), a local model, or a CLI you connected, the transfer is between you and the provider you chose and is not covered by this table. Before using a new overseas processor, we verify its receiving country, contact details, and retention period and update this policy.

6. Destruction

Personal data is destroyed without delay once its retention period ends or its purpose is met. Electronic files are deleted so they cannot be recovered; printed material is shredded or incinerated. Data that must be kept under law is stored separately from other personal data.

A request submitted from the account page or mobile app is acknowledged as pending. Submission does not immediately delete the account or its data. We check public posts, private Cloud data, separate stores, and legally retained records before confirming completion. For progress, contact appbridge@appbridge.co.kr.

7. Your rights

You may at any time ask to access, correct, delete, or suspend the processing of your personal data. Do it from the account page or write to appbridge@appbridge.co.kr; we act within 10 days of receiving the request. A legal representative or an authorised agent may exercise these rights on your behalf.

8. Cookies

Essential cookies support sign-in and language settings. Visit measurement runs only after the visitor chooses Allow in the notice at the bottom of the page. Allowing stores a random visitor identifier cookie (agentlas.vid) and the choice cookie (agentlas.analytics) for one year, and records on our own servers (MongoDB Atlas) only the page path, the referring site's domain, campaign markers, pricing and checkout step events, the country code, the device type, and whether the visitor was signed in. This measurement stores no IP address, email address, or card data and is not sent to any third-party analytics tool. Records are deleted automatically after 400 days. Choosing Decline records nothing; deleting the agentlas.analytics cookie in the browser lets the visitor choose again. The former Google measurement tags and the agentlas.growth cookie remain discontinued and are removed on a visit. Google and Apple sign-in are authentication features chosen by the user and are separate from measurement.

9. Security measures

  • Access is limited to the smallest possible number of people, with managed permissions.
  • Traffic is encrypted in transit, passwords are hashed, and credentials needed for service integrations are subject to access controls.
  • Access logs are retained and protected against alteration.
  • Content in an uploaded package that looks like a credential is removed before storage, and the removal is recorded.
  • Optional app capability descriptions received from the desktop app are screened on the server for credentials, e-mail addresses, personal file paths, and long digit strings before storage; records that fail are discarded.

10. Data protection officer

Data protection officer: Jeongmin Kim, representative of Appbridge Inc. · appbridge@appbridge.co.kr · +82-10-5031-7599. Questions, complaints, and remedy requests about personal data go to this address and are answered without delay.

11. Where else to complain

  • Personal Information Dispute Mediation Committee — 1833-6972 / www.kopico.go.kr
  • Korea Internet & Security Agency privacy centre — 118 / privacy.kisa.or.kr
  • Supreme Prosecutors' Office cybercrime division — 1301 / www.spo.go.kr
  • National Police Agency cyber bureau — 182 / ecrm.police.go.kr

12. Children's data

The Service requires a user to be at least 14 years old (see the terms of service). We do not knowingly collect personal data from a child under 14. Where we learn that we have, we delete it without delay unless the child's legal guardian has given consent required by the Korean Personal Information Protection Act, in which case we process only what that consent covers.

13. Changes to this policy

This policy was revised on 17 November 2026 and, under the last sentence of this section, applies from 24 November 2026. This revision adds what the mobile app's personal agent (the phone agent) processes and how long it is kept to sections 1 and 2, adds the notification delivery providers (Google LLC and Apple Inc.) to sections 4 and 5, and states that the hosted AI processor entries (Anthropic and OpenAI) in sections 4 and 5 also cover the phone agent's conversations. The revision of 10 October 2026 added the hosted AI processors (Anthropic and OpenAI) to sections 4 and 5. The end of optional measurement in section 8 applies when posted. The optional app capability catalog added to section 2 applies only to desktop users who turn on its setting, from the first desktop version that includes it. Other additions, removals, or corrections are announced in the Service at least 7 days before they apply.

Data controller

The data controller is Appbridge Inc. (주식회사 앱브릿지, Republic of Korea). Paddle.com Market Ltd. is a separate controller for the payment data it processes.

Privacy policy · Agentlas docs