1. Introduction and Scope#

1.1 About this Policy. This Privacy Policy explains how Datumo, the name under which 셀렉트스타 주식회사, a company incorporated in the Republic of Korea, operates outside Korea ("Datumo," "we," "us" or "our") collects, uses, shares, retains and protects personal information in connection with DATUMO, including the DATUMO Console, Quick Eval, our websites, APIs and related services (the "Service"). It also explains how you can exercise your rights. We comply with Korea's Personal Information Protection Act ("PIPA"), the EU General Data Protection Regulation ("GDPR"), the UK GDPR, Japan's Act on the Protection of Personal Information ("APPI"), applicable US state privacy laws and other applicable laws.

1.2 Controller. Datumo is the controller of the personal information described in this Policy: Datumo (셀렉트스타 주식회사), 8th–11th floors, 8 Teheran-ro 38-gil, Gangnam-gu, Seoul 06221, Republic of Korea; [email protected].

1.3 When we process data for our customers. Customers upload, connect or generate content in the Service, such as evaluation datasets, conversation logs, production logs from their AI applications, policies, documents and evaluation results ("Customer Content"). Customer Content may contain personal information about a customer's end users, employees, testers or others. For that information, the customer is the controller, and Datumo processes it on the customer's behalf as a processor (a trustee under PIPA and a service provider under US state laws) under our agreement with the customer. This also applies to logs and policies uploaded to Quick Eval before sign-up, which we process only to produce the requested results. This Policy does not cover customers' own practices. If you are an end user of a customer's AI application, please contact that customer to exercise your rights; we will help the customer respond. We may also use Customer Content as a controller to the limited extent needed to secure the Service, prevent and investigate abuse, such as misuse of Red Teaming, and comply with law.

1.4 If you belong to an Organization. If you use DATUMO as a member of an Organization, its Owner and Admins can manage your access and roles. They can see your name, email address, roles, join date and last active time, and the content you create in the Organization. Content you create remains with the Organization after you leave it or delete your account.

1.5 EU and UK representatives. We are in the process of appointing a representative in the European Union under Article 27 of the GDPR. Until the appointment is finalized, please send GDPR-related inquiries to [email protected]. Users in the United Kingdom may also contact [email protected], and we will update this Policy if we appoint a UK representative.

2. Personal Information We Collect#

We collect only the personal information we need for the purposes in Section 3:

CategoryPersonal informationSource
AccountName; work email address; password (stored as a hash); sign-in method; for Google or Microsoft sign-in, the account identifier, name and email address that provider sharesYou; Google or Microsoft
Profile and preferencesAnswers to optional onboarding questions, such as your role; language; marketing consent status and historyYou
Organization and membershipOrganization and Workspace names; your Organization and Workspace roles; join date; last active time; history of role and access changes, including who invited, changed or removed youYou; your Organization's Owner and Admins
InvitationsInvitee email address; assigned roles and Workspaces; inviter's name and email address; dates sent and expiry; statusThe person who invites you
Support, sales and feedbackContent of inquiries and contact forms, such as company, use case and message; feedback; optional reasons for deleting your accountYou
Usage and deviceLog-in records; IP address; browser and operating system; device, session and cookie identifiers; pages and features used; actions such as runs started, exports and settings changes; API call logs; error logs; usage metrics such as evaluation scores, tokens, latency and costCollected automatically
Quick Eval guest dataUploaded conversation logs and policy text; generated results; a session identifier used to carry results over to a new accountYou, before sign-up, as or on behalf of the controller (we act as processor)
CredentialsModel API keys, Application request headers and tokens, AWS access keys for Observability, and DATUMO API keys, where they are linked to youYou
Customer ContentAny personal information contained in datasets, benchmark sets, conversation and production logs (such as end users' messages, user and session IDs and metadata), policies and documents, tool schemas and trajectories, prompts, model responses, simulation transcripts, attack prompts and captured responses, Evaluation Lab submissions and tester comments, annotations and evaluation resultsCustomers and their Users; we act as processor

As a controller, we do not intentionally collect sensitive information, such as health data or political or religious beliefs, or unique identifiers, such as resident registration numbers. Customer Content contains such data only if a customer submits it, and our Terms of Service require customers to minimize and mask it.

Your name, work email address and password, or a Google or Microsoft sign-in, are required to create an account. Answers to onboarding questions and marketing consent are optional, and you can use the Service without them.

3. How We Use Personal Information#

3.1 Purposes and legal bases. We use personal information for the purposes below. For users in the EEA and UK, the table also shows the legal basis under Article 6(1) of the GDPR.

PurposeExamplesGDPR legal basis
Provide the ServiceCreate and authenticate accounts; link sign-in methods; manage Organizations, Workspaces, roles and invitations; run evaluations, simulations, red teaming and monitoring; send alerts; carry over Quick Eval resultsContract (b); for invitations and Organization membership, the legitimate interests of the Organization and of Datumo in enabling collaboration (f)
Security and abuse preventionDetect unauthorized access, fraud and violations of our Terms; enforce the 14-day re-registration waiting period; keep audit logsLegitimate interests (f); legal obligation (c)
Support and service messagesAnswer inquiries; send verification, invitation, security and policy noticesContract (b); legitimate interests (f)
Improve the ServiceAnalyze usage trends and performance using aggregated or de-identified data; fix errorsLegitimate interests (f); consent for non-essential cookies where required (a)
MarketingSend product news and offersConsent (a)
Legal complianceMeet legal obligations; respond to lawful requests; establish or defend legal claimsLegal obligation (c); legitimate interests (f)

3.2 Korea. Under PIPA, we process personal information where it is necessary to conclude and perform a contract with you (Article 15(1)(4)), to comply with legal obligations (Article 15(1)(2)), or for our legitimate interests that clearly override your rights, within a reasonable scope (Article 15(1)(6)). We ask for your consent where the law requires it, for example for marketing. We do not use personal information for other purposes without a legal basis.

3.3 Legitimate interests. Where we rely on legitimate interests, we have balanced them against your rights and freedoms. You can object at any time by emailing [email protected].

3.4 Automated decisions. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you, within the meaning of Article 37-2 of PIPA or Article 22 of the GDPR. AI scoring in the Service evaluates AI systems and their outputs, not individuals. Customers can view statistics about their own testers, such as attack success rates, and are responsible for any decisions they make about their personnel.

4. AI Processing#

4.1 Models we use. The Service uses three kinds of models: Datumo Models, developed or tuned by Datumo; Provided Third-Party Models, from providers such as OpenAI, Anthropic and Google, which we use through our own accounts; and Customer-Registered Models, which customers connect with their own API keys or endpoints. The Service shows which model is used for each task.

4.2 What we send to models. We send only the data needed for the task you run. For example, to judge a response we send the input, the response, any retrieved context and the metric's instructions; to generate scenarios we send your policy and tool schema; and in simulations, red teaming and Evaluation Lab we send conversation transcripts. Data is sent over encrypted connections.

4.3 Third-party model providers. We use providers' paid API services under terms that do not allow them to train their models on our API data. Under those terms, providers keep API data only for a limited period to provide the service and monitor abuse: currently up to 30 days for OpenAI and Anthropic, and 55 days for Google, unless longer retention is needed to investigate a policy violation or required by law. These providers are our processors (Section 5.3).

4.4 No training on Customer Content. We do not use Customer Content to train, fine-tune or otherwise improve AI models, including Datumo Models, unless the customer expressly opts in. We improve the Service using only aggregated or de-identified information.

4.5 Customer-Registered Models and Customer Systems. When a customer registers its own model or endpoint, or connects its Application, agent or cloud log source, we send data to, or retrieve data from, those systems on the customer's instructions. Those providers are the customer's vendors, and the customer's agreements with them govern how they handle data.

4.6 Observability. If a customer connects Observability, we retrieve logs from the customer's cloud account (currently AWS CloudWatch), run the customer's parser code on them, and store the resulting sessions and turns. We send sampled turns to judge models, and email Fail Case alerts, which include the user input and application output of failed turns, to recipients the customer chooses. We do all of this as the customer's processor.

4.7 AI-generated content. We indicate AI-generated Outputs in the Service as required by Korea's AI Basic Act and other applicable laws. If you believe an AI-generated Output is inappropriate or contains personal information, you can report it or raise an objection by emailing [email protected], or [email protected] for privacy matters.

5. Sharing and Processors#

5.1 No sale. We do not sell personal information, and we do not share it for cross-context behavioral advertising.

5.2 When we share personal information. We provide personal information to third parties only:

5.3 Processors. We entrust the following processing to service providers. Our contracts with them set out the purpose and scope of processing, security measures, limits on further outsourcing, supervision and liability, as Article 26 of PIPA and Article 28 of the GDPR require.

ProcessorTaskLocation
Amazon Web Services, Inc.Cloud hosting and data storage; sending service emails, such as verification, invitation and Fail Case alert emails (Amazon SES)Republic of Korea (Seoul region)
OpenAI, L.L.C.AI model processing for Provided Third-Party Models (GPT)United States
Anthropic, PBCAI model processing for Provided Third-Party Models (Claude)United States
Google LLCAI model processing for Provided Third-Party Models (Gemini)United States
Google LLC (Google Analytics)Usage analyticsUnited States
Runpod Inc.Hosting Datumo Models (GPU cloud)United States and other countries where Runpod operates data centers (Section 6.2)

We update this list at least 30 days before we add or replace a processor that processes Customer Content, and post other changes as described in Section 11.3. Providers of Customer-Registered Models are customers' vendors, not our processors.

5.4 Datumo personnel. Authorized Datumo personnel can access every Organization through internal administration tools, with the ability to view content and to change settings, roles, ownership and deletion status. We use this access only to provide support you request, maintain and secure the Service, investigate violations and comply with law. It is limited to personnel who need it, logged and subject to confidentiality obligations.

6. International Transfers#

6.1 Where we store data. We store and process personal information mainly in the Amazon Web Services Seoul region in the Republic of Korea.

6.2 Overseas transfers under PIPA. We transfer personal information outside Korea where entrusting or storing it abroad is necessary to conclude and perform our contract with you, and disclose the transfers below as Article 28-8(1)(3) and (2) of PIPA require:

Recipient (privacy contact)CountryItems transferredWhen and howPurposeRetention by recipient
OpenAI, L.L.C. ([email protected])United StatesCustomer Content sent for the AI task, including any personal information it containsWhen you run a task with its model, by encrypted transfer through its APIAI model processingNot used to train its models; deleted within 30 days unless longer retention is needed for abuse investigation or by law
Anthropic, PBC ([email protected])United StatesSame as aboveSame as aboveAI model processingNot used to train its models; deleted within 30 days unless longer retention is needed for abuse investigation or by law
Google LLC (support.google.com/policies/contact/general_privacy_form)United StatesSame as aboveSame as aboveAI model processingNot used to train its models (paid Gemini API); kept for 55 days for abuse monitoring unless longer retention is needed for abuse investigation or by law
Google LLC, Google Analytics (support.google.com/policies/contact/general_privacy_form)United StatesCookie and device identifiers, pages and features used, approximate location, browser and operating systemWhen you use our websites and the Service, by encrypted network transferUsage analytics2 months (Google Analytics default setting)
Runpod Inc. ([email protected])United States, Canada, Japan, India, Australia, Iceland, Norway, EU member states and other countries where Runpod operates data centersCustomer Content sent for tasks that use Datumo Models, including any personal information it containsWhen you run a task with a Datumo Model, by encrypted network transferHosting Datumo ModelsProcessed only to run the task, under our data processing agreement with Runpod

How to refuse. You can refuse these transfers by emailing [email protected], by choosing Customer-Registered Models instead of Provided Third-Party Models or Datumo Models where available, or by blocking cookies in your browser or using Google's opt-out add-on. If you refuse a transfer needed for a feature, you may be unable to use that feature.

6.3 Customer Content. When we process Customer Content as a processor, the customer chooses which models and Customer Systems to use and is responsible for the notices or consents its own transfers require. We give customers the information they need for this.

6.4 EEA and UK. Transfers from the EEA to Datumo in Korea rely on the European Commission's adequacy decision for the Republic of Korea (December 2021), and transfers from the UK rely on the UK–Republic of Korea data bridge (December 2022). For onward transfers to processors in other countries, we use appropriate safeguards, such as the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, or the EU-U.S. Data Privacy Framework and its UK Extension where the recipient is certified, with supplementary measures where needed. You can request a copy of the relevant safeguards at [email protected].

6.5 Japan. If you are in Japan, your personal information is provided to Datumo in Korea and to the recipients listed in Section 6.2, in the countries shown there. Under their contracts with us, these recipients maintain systems for taking measures equivalent to those the APPI requires. The Personal Information Protection Commission of Japan publishes information on these countries' data protection systems, and we will provide details of the recipients' measures on request.

7. Retention and Destruction#

7.1 Retention periods. We keep personal information only as long as we need it for the purposes in this Policy, then destroy it without delay, unless the law requires us to keep it longer:

InformationRetention period
Account informationUntil you delete your account. After deletion, kept for 14 days to enforce the re-registration waiting period and prevent abuse of the Service, then destroyed
Organization, Workspace and membership dataWhile the Organization exists. After deletion, kept for 30 days so it can be restored or to respond to accidental or unauthorized deletion, then destroyed
InvitationsUntil accepted, or until an Owner or Admin deletes it; expired invitations stay in the list until deleted. Deleted with the Organization. Accepted invitations are kept as part of membership history
Customer Content, including evaluation results (such as datasets, criteria, settings and results)While the Organization exists. Items, Applications and Workspaces the customer deletes are removed from the Service immediately and may remain in our systems until the Organization is deleted, unless the customer asks us to delete them sooner. After the Organization is deleted, kept for 30 days so it can be restored, then destroyed
Observability dataSame as Customer Content. Collection stops when the customer disables the integration, asks us to disable it or deletes the Application, or when the Organization is deleted
Quick Eval guest dataIf not carried over to a new account, kept for 7 days after upload, then destroyed
CredentialsUntil the customer deletes them or the Organization is deleted. After the Organization is deleted, not used for new tasks, kept for 30 days so it can be restored, then destroyed with the Organization
Your name and email address in audit logs and in records of content you createdWhile the Organization keeps that content; audit logs 1 year
Log-in records1 year (the Protection of Communications Secrets Act requires at least 3 months)
Other service logs1 year
Marketing consent recordsKept with your account information and destroyed with it
Inquiries and support records3 years after the inquiry is resolved

7.2 Backups. Deleted data is removed from backups on a rolling schedule within 35 days.

7.3 Destruction. When a retention period ends or its purpose is achieved, we destroy the information without delay, generally within 5 days. We delete electronic files so that they cannot be recovered or, where permanent deletion is technically impractical, anonymize them irreversibly, and we shred or incinerate paper records. Information we must keep under law is stored separately from other data and used only for the purpose the law specifies.

8. Security Measures#

We protect personal information with the following measures, in line with Article 29 of PIPA:

9. Your Rights#

9.1 Rights of all users. Wherever you are, you can ask us to:

You can update your name, password and marketing preferences, and delete your account, in My Account. For other requests, email [email protected]. You may act through a legal representative or an agent with a power of attorney. We will verify your identity before acting on a request. While a correction or deletion is pending, we will not use or provide the information concerned. We may decline or limit a request where the law allows, for example where we must keep information under law, and we will tell you why.

9.2 Response times. We respond within 10 days to requests under PIPA, within one month to requests under the GDPR (extendable by two months for complex requests), and within the period other applicable laws require. Requests are free unless they are clearly unfounded or excessive.

9.3 Customer Content. If your information is in Customer Content, for example in a customer's logs or datasets, please contact that customer. We will help the customer respond.

9.4 EEA and UK. You also have the right to data portability, the right to object to processing based on legitimate interests, and the right to lodge a complaint with your supervisory authority (Section 11.5).

9.5 United States. Depending on your state of residence, you may have the right to know what personal information we collect, use and disclose; to access, correct and delete it; to receive a portable copy; and to opt out of the sale of personal information, sharing for cross-context behavioral advertising, targeted advertising and profiling. We do not sell or share personal information for those purposes, and we do not use sensitive personal information to infer characteristics about you. We will not discriminate against you for exercising your rights. Authorized agents may submit requests with proof of their authority. If we deny your request, you may appeal by emailing [email protected] with "Appeal" in the subject line, and you may contact your state attorney general if you remain dissatisfied.

9.6 Japan. You may request disclosure of your personal information and of records of its provision to third parties, as well as its correction, suspension of use, deletion, and cessation of provision to third parties, as the APPI provides.

10. Cookies and Marketing Communications#

10.1 Cookies. We and our providers use cookies and similar technologies:

TypePurposeExamples
EssentialSign-in, session security, "Remember me," load balancing, and carrying Quick Eval results over to a new accountAuthentication and session cookies
PreferencesRemembering settings such as languagePreference cookies
AnalyticsUnderstanding how the Service is used so we can improve itGoogle Analytics

In the EEA and UK, and wherever else the law requires, we use non-essential cookies only with your consent. Where we ask for your consent, you can withdraw it at any time through the cookie settings. You can also block or delete cookies in your browser settings, and opt out of Google Analytics with Google's browser add-on. Blocking essential cookies may stop parts of the Service from working. Where the law requires, we treat Global Privacy Control signals as a request to opt out. We do not currently respond to other "Do Not Track" browser signals.

10.2 Marketing communications. We send marketing emails only if you opt in, for example at sign-up or in Marketing Preferences. You can withdraw your consent at any time through the unsubscribe link in each email or in My Account. Users in Korea will be told their consent status every 2 years, as the Act on Promotion of Information and Communications Network Utilization and Information Protection requires. Service messages, such as verification, invitation and security notices, are not marketing and are sent regardless of this choice.

11. Children, Changes and Contact#

11.1 Children. The Service is intended for business users aged 18 or older. We do not knowingly collect personal information from children under 14 in Korea, under the applicable age (13 to 16) in the EEA and UK, or under 13 in the United States. If we learn that we have, we will delete it. Customers may include children's personal information in Customer Content only where they have a lawful basis and any required parental consent, and we process it as their processor.

11.2 Pseudonymized information. We do not currently process pseudonymized information under Article 28-2 of PIPA. If we start, we will update this Policy.

11.3 Changes to this Policy. We will post changes in the Service and on our website at least 7 days before they take effect, or at least 30 days before for changes that significantly affect your rights, such as using personal information we already hold for a new purpose or disclosing it to new third parties. Where the law requires consent, we will ask for it.

11.4 Chief Privacy Officer. Our Chief Privacy Officer handles privacy inquiries, complaints and requests:

11.5 Complaints and remedies. Please contact us first so we can try to resolve your concern. You may also contact:

11.6 Version history. Version 3, effective November 11, 2026 (this version); version 2, effective January 15, 2026; version 1, November 4, 2025.