How leapCAT handles your account, source, and translation data

1. Information we process

• Account reference and profile information supplied through Replex Accounts, such as email address and sign-in state.
• Source text (including uploaded manuscript files and scanned images) and target text, language direction, project instructions, answers, terminology, edits, versions, and export records.
• Workspace state, product usage, device and browser information, access time, error records, and security logs.
• Email address, message, and reply history when you contact support.
• When you request a trial: your name, email address, book title and optional note, the book's language, the languages you want, and the time and version of your consent.
• The campaign labels (utm_source, utm_medium, utm_campaign, utm_term, utm_content, ref) and landing page of the link that first brought your browser to leapCAT, kept with a trial request and, once, with your account when you first sign in.

2. Why we process it

• Create and maintain your account and workspace.
• Analyze the source, propose a direction, translate, review, run quality checks, save edits and versions, and generate exports.
• Prevent abuse, protect accounts, diagnose failures, and improve reliability.
• Respond to inquiries and provide product notices.
• Answer trial requests, contact you about the trial, and understand which introductions bring authors to leapCAT.

3. How long we keep it

Account information and workspace content (source, translation, and their work records) are kept while you keep your account and are destroyed under section 4 when you close it.

A trial request is kept until it is answered and, after that, while it is needed to run the trial with you. It is deleted when you ask us or when you delete the Replex account that uses the same email address.

Server operation logs, which include access and error records, are deleted automatically after 30 days, and error-monitoring records after at most 90 days. Database backups are deleted 35 days after they are made and are purged within 7 days after that.

4. How we destroy it

Information whose retention period has ended or whose purpose has been met is destroyed without delay. When you close your account, a tracked cleanup job deletes your workspace content, trial request, and first-visit record from the database, deletes your files from storage including their earlier stored versions, and replaces your account record with values that no longer identify you. If cleanup fails, the request stays open and is retried rather than marked complete. Copies in database backups disappear when those backups expire as described in section 3.

5. Processors and overseas transfer

To perform our contract with you, Replex entrusts the processing below to these companies. Because they process or store the information outside Korea, each is also an overseas transfer (Personal Information Protection Act, Article 26 and Article 28-8(1)(iii)). Information is sent over an encrypted internet connection (TLS) when you use the function concerned. Each entry lists the recipient and contact; the work and purpose; the country; the items; and how long the recipient keeps them.

• Google Cloud Korea LLC (contact: https://support.google.com/policies/troubleshooter/7575787) — hosting the service, its database, file storage, and backups, and keeping server operation logs — Google Cloud Tokyo region (Japan); server operation logs are kept in Google Cloud's global log storage, whose location Google decides — all information in section 1 — for the periods in section 3.
• Google Cloud Korea LLC, Vertex AI Gemini (contact: https://support.google.com/policies/troubleshooter/7575787) — detecting the source language, analyzing the source, reading scanned manuscripts, and checking terminology and consistency — the country of the Google data center that handles each request, which Google decides and Replex does not choose — source (including scanned images), translation, instructions, answers, terminology, and work context — not stored after the response; a temporary processing cache is deleted within 24 hours, and abuse-detection records follow the Google Cloud terms.
• OpenAI, L.L.C. (contact: privacy@openai.com) — generating and correcting the translation, cross-review, quality judgments, and web search for terminology, style, and publishing references — United States — source, translation, instructions, answers, terminology, and work context, and search queries with short descriptions of their concept and field — leapCAT asks OpenAI not to store responses; abuse-monitoring logs are kept for up to 30 days.
• Anthropic, PBC (contact: privacy@anthropic.com) — independent review, quality judgments, and terminology decisions — United States — source, translation, instructions, answers, terminology, and work context — deleted within 30 days of receipt; records flagged for a usage-policy violation may be kept for up to 2 years.
• Functional Software, Inc. (Sentry) (contact: compliance@sentry.io) — detecting and diagnosing errors — United States — error records, device and browser information, and the page path and time of the error, with source, translation, email, token, and file-name fields filtered out — up to 90 days.

6. Refusing overseas transfer

If you do not want your information transferred overseas, do not save a manuscript, or close your account through the account controls or by contacting hello@replex.me. Because leapCAT stores its data and runs its AI processing outside Korea, refusing the transfer means you cannot use leapCAT.

7. How AI processing works

Analysis, translation, review, and quality checks are split among different AI models, and each task sends only the source and work context it needs to the recipient listed in section 5. To research terminology, style, and publishing references, leapCAT sends short search queries and descriptions of their concept and field to OpenAI web search; the full manuscript is not sent to search. Source links, collected original excerpts, collection dates, and verification limitations are kept with the project as evidence for translation decisions and reports.

AI processing of each saved manuscript is approved before analysis starts: a manuscript from a trial account is approved automatically, and a leapCAT operator opens any other manuscript to approve it.

Replex does not use your source or translation to train an AI model. The AI recipients in section 5 do not use API inputs or outputs for model training by default.

Do not submit personal information or confidential material that is unnecessary for the translation. You remain responsible for having the right to use and translate the submitted source.

8. Provision to third parties

Replex does not provide personal information to third parties, except when you ask us to or a law specifically requires it. We do not sell your source or translation data.

9. Cookies and browser storage

leapCAT uses a cookie that keeps you signed in and a cookie that remembers the interface language. Your browser also stores reading settings and progress, and the campaign labels (utm_* or ref) and landing page of the link that first brought you; the campaign labels are sent to leapCAT only with a trial request or once when you first sign in, and they are never sent to Google Analytics. leapCAT currently uses no external web analytics such as Google Analytics. You can clear or block cookies and storage in your browser settings, but blocking the sign-in cookie means you cannot sign in.

10. Security measures

Replex uses access controls, encrypted transport, private storage, least-privilege service identities, monitoring, and deletion workflows appropriate to the service. Error monitoring is configured not to send default personal information and filters common source, prompt, translation, email, token, and file-name fields.

11. Your rights and how to exercise them

You may request access, correction, deletion, or suspension of processing of your personal information, and you may close your account through the account controls. A legal representative or a person you authorize may make these requests for you. Send requests to hello@replex.me.

12. Privacy officer

Privacy officer: 김태현, CEO of 주식회사 리플렉스 (Replex) (phone 010-4445-6670, email hello@replex.me). Send privacy questions and complaints to this contact.

13. Changes to this policy

We publish changes on this page with a new effective date. If a change materially affects your rights or how source and translation data is processed, we will provide additional notice through an available service or account channel where required.