top of page

This policy covers the AmYah CAT Tool app. It does not describe the separate cookies, hosting, forms, or analytics used by the AmYah website.

AmYah CAT Tool Privacy Policy

Last updated: October 16, 2026

This policy describes how AmYah CAT Tool handles translation projects, optional cloud-service credentials, purchases, and related app data.

Local Projects

AmYah CAT Tool is designed to keep translation projects on your device or in the file location you choose unless you choose to export or share them. Project files, translation memories, termbases, segmentation rules, import settings, and editor preferences are stored locally by the app or in files you choose. While you edit, the app keeps a device-local recovery journal in its Application Support folder so interrupted work can be restored. Segment and edit-operation payloads in that journal are authenticated and encrypted with a per-journal AES-256-GCM key held in the device Keychain; journal files are excluded from device backups and use the platform's strongest complete file-protection class where available. Journal filenames and stored identifiers do not contain project, file, segment, source, or target text. Deleting a source file or project through the app closes and removes its corresponding journal, its SQLite sidecars, and its encryption key.

Optional Cloud Providers

Cloud features are optional and use API credentials that you provide for your own provider account (often called bring your own key, or BYOK). Before AmYah CAT Tool sends project content to a cloud provider for the first time—and again after that provider credential changes—it identifies the provider, describes the kinds of content that can be sent, links to the provider's current information, and asks for affirmative confirmation. The only available cloud integrations in this build are the OpenAI API and Anthropic API (Claude API). They support translation and the user-invoked generative review, quality-estimation, and terminology features. Google Cloud Translation API, Gemini Developer API, DeepL API, and xAI Grok API are unavailable in this release.

AmYah CAT Tool sends the content needed for a user-invoked request directly from the device to the selected provider using the credential you supplied. The request does not pass through an AmYah relay, analytics, or advertising server.

If you import an email message, the text sent can include the email subject or body that you chose to translate. Depending on the invoked feature, sent content may also include source or target segments; language codes; project, client, and document names; relevant termbase entries; up to three ranked translation-memory source/target matches; protected placeholders; Translation Brief instructions; approved source/target examples; and up to 24,000 characters of bounded document-wide bilingual context. Translate All makes requests for eligible segments. AI review, quality estimation, and terminology extraction may send selected bilingual content and the same bounded project context. Nothing is sent to these providers merely because a project is opened or edited locally.

Current versions store provider API keys in the system Keychain on your device and do not write new keys to project files or UserDefaults. When upgrading from a legacy version, AmYah CAT Tool makes a one-time attempt to move an older UserDefaults key into Keychain and removes the plaintext copy even if that attempt fails. If migration fails, you must enter the key again. AmYah CAT Tool does not send provider keys to an AmYah CAT Tool server. When you use a provider, that provider's API key is sent directly to that provider as request authentication.

The selected provider, rather than AmYah CAT Tool, controls provider-side processing, retention, account and network records, billing, safety or human review, model-improvement use, and processing location. Those practices can differ by free or paid tier, feature, project setting, region, data-processing agreement (DPA), and negotiated terms. Possession of an API key does not prove that the account is eligible for confidential or personal content. The API account holder—not AmYah—must accept or arrange any applicable DPA and confirm authority under client agreements. AmYah CAT Tool cannot promise full provider-side confidentiality, zero retention, no review or training, or processing in a selected region.

Use a dedicated project credential, restrict it to the intended API where the provider supports restrictions, set provider-side spending limits and monitoring, and rotate or revoke it in the provider console when needed. Do not send confidential, personal, regulated, or client text unless the provider account, tier, settings, DPA, region, and your client agreement all permit that processing.

Offline, rule-based translation features do not send text to third-party MT providers. Apple system translation features are handled by Apple frameworks and do not use your third-party provider API keys.

Provider Terms And Account Responsibility

The provider's current documentation, console settings, and agreement for your exact API account—not a summary embedded in this app—are the source of truth for provider-side retention, safety or human review, model training or improvement, regional processing, account eligibility, and deletion. Review them immediately before sending a project, and review them again when the provider or your account configuration changes:

Those pages and the agreement attached to the account may change without an AmYah CAT Tool update. A link is not a representation that an account is appropriate for a particular project.

For personal-data processing through an available provider, the API account holder must determine whether the current OpenAI or Anthropic DPA applies, complete any required acceptance or signature process, and confirm that the DPA binds the exact account and service configuration being used. These agreements attach to the provider account holder; they do not attach to AmYah CAT Tool merely because the app makes a direct BYOK request. A DPA also does not replace the account holder's legal basis, client permission, professional duties, or restrictions on confidential, regulated, or export-controlled content.

These account-holder responsibilities do not remove AmYah's own applicable privacy, disclosure, security, or contractual duties for the app and its integrations. Linking to a provider's policies does not transfer those duties to you or to the provider.

A consumer chatbot subscription does not necessarily provide API access. Use a valid OpenAI Platform or Anthropic Console API credential with the provider-side billing and controls required by that provider. AmYah requests that OpenAI not store application state, but this request parameter is not a promise of zero provider retention and does not override OpenAI's current policies or your account agreement.

Google Cloud Translation is unavailable for new requests. Previously saved or imported Google-derived text retains the applicable provider provenance and attribution; displaying a legacy badge does not create a Google connection or send the project to Google. Google's attribution requirements and the disclaimer in Legal Notices remain relevant to legacy output. Disabling new requests does not waive applicable conditions on displaying or distributing that output. For records from earlier Google use, consult Google's data usage, Cloud Terms, and Cloud DPA; removing the integration does not delete provider-side records.

Google Cloud Translation API, Gemini Developer API, DeepL API, and xAI Grok API are unavailable in this release. Stored legacy settings for those providers do not enable transmission. If any is considered for a future release, the developer must first perform a new contractual, privacy, security, attribution, localization, and App Store review and update this policy before enabling it.

Purchases

In-app purchases and subscriptions are processed by Apple StoreKit. AmYah CAT Tool receives purchase entitlement status from Apple so it can unlock paid features. Payment information is handled by Apple, not AmYah CAT Tool.

Diagnostics And Analytics

AmYah CAT Tool does not include third-party advertising or cross-app tracking SDKs and does not operate an analytics or advertising server. Apple may provide crash reports, performance information, or App Store analytics to the developer when users have enabled sharing such information with Apple. The app's no-tracking statement does not mean that a user-selected cloud provider receives no account, network, billing, security, or usage data under that provider's own terms.

Data Sharing

AmYah CAT Tool does not sell personal data. AmYah CAT Tool does not use your translation content for advertising or cross-app tracking. Data is shared only when needed for functionality you choose, such as sending text to a selected cloud provider, processing purchases through Apple, or exporting/sharing files at your direction.

Deletion And Control

You can delete project files and exported files from your device or storage provider. Removing a source file, translation memory, or termbase from a project and then saving removes its stored package data; deleting a project through the app removes its local recovery journal. You can remove available providers' keys in AmYah CAT Tool settings by clearing the corresponding key field. Clearing a local key or removing an integration does not revoke the credential at the provider; use the provider's console if you want to revoke it, including credentials from a disabled integration. You can reset cloud AI consent in Settings, after which each available provider asks again before content is sent.

Resetting consent, clearing a key, or deleting a local project does not delete content that a provider has already received. AmYah CAT Tool's developer cannot access or delete provider-side records. Use the provider account controls or support process linked from its official data-handling page for provider-side access or deletion requests. Providers may retain requests or account records according to their terms, safety obligations, legal requirements, and account settings.

Security

AmYah CAT Tool stores provider API keys in the system Keychain with device-local protection and sends cloud requests over HTTPS. Legacy plaintext key copies are removed after migration is attempted, including when migration fails. No method of storage or transmission is perfect, so only use cloud services for content you are permitted to process with those services.

Operator And Contact

The developer of AmYah CAT Tool is responsible for the app's own local-data handling described in this policy. Use the AmYah CAT Tool support page or the App Support link on AmYah CAT Tool's App Store product page for privacy and support questions about the app. For data held by a cloud provider, use that provider's account controls or privacy-support process because AmYah CAT Tool's developer cannot access the provider account or its records.

​

​

bottom of page