गोपनीयता विकल्प

हम वैकल्पिक विश्लेषण का उपयोग यह समझने के लिए करते हैं कि वेबसाइट का उपयोग कैसे होता है और पेज बेहतर बना सकें। कुकी स्वीकार करने पर हम दोबारा आने वाली विज़िट पहचान सकते हैं। आप यह विकल्प कभी भी बदल सकते हैं।

LogoUnimeType
  • Features
  • Pricing
  • Docs
  • Blog
  • Support
डाउनलोड
LogoUnimeType

Type in Latin. Convert when ready.

X (Twitter)Reddit
Product
  • Features
  • Download
  • FAQ
Resources
  • Blog
  • Documentation
Company
  • About
  • Support
Legal
  • Cookie Policy
  • Privacy Policy
  • Delete account
  • Terms of Service
© 2026 UnimeType. All Rights Reserved.

Privacy Policy

How UnimeType processes account, text, purchase, website and optional analytics data

2026/08/03

Effective August 3, 2026.

This policy applies to the UnimeType website, account service, Unime Credits service, support channels, and the iOS, iPadOS, macOS, Android, Windows, and Linux clients and input extensions.

1. Controller and contact

FIGURICH LTD is the controller for data handled by the UnimeType account, website, managed gateway, purchase, support, and optional product-analytics systems. FIGURICH LTD is registered in England and Wales under company number 15975561. Its registered office is 5 Brayford Square, London E1 0SG, United Kingdom. Contact support@unimetype.com about privacy, access, correction, objection, consent withdrawal, or deletion.

When you configure a Bring Your Own Key provider, that provider independently controls its own request logging, retention, training, billing, and security practices.

2. When text leaves your device

Showing the UnimeType keyboard and pressing ordinary character keys do not start an AI request. A request starts when you choose Convert, Polish, or Explain. The request includes the text selected for that action, an instruction describing the action, the selected model, and the credential required by the route you chose.

Convert may also include up to 100 characters immediately before the target in the same paragraph as read-only context for disambiguation. Do not submit passwords, payment-card details, health information, or other information you do not want an AI provider to process. iOS normally replaces third-party keyboards with the system keyboard in secure text fields.

3. Information processed and purpose

  • Account and sign-in records. Email or password registration processes your name, email address, password authentication record, email-verification state, account identifier, and sign-in time. Email-code, Google, or Apple access can create an account when the email does not already identify one. Google or Apple may provide a name, email address, provider account identifier, profile image, and provider authentication tokens. Sessions record an identifier, expiry, IP address, User-Agent, and account identifier so UnimeType can authenticate the device, show or revoke its session, prevent abuse, and protect the account.
  • Action content. Text submitted through Convert, Polish, or Explain is processed to return the requested result. Convert may also contain up to 100 preceding characters from the same paragraph as read-only context.
  • Connection settings and credentials. On Apple platforms, non-secret settings are stored in the app group shared by the app and keyboard. BYOK API keys, UnimeType sessions, and short-lived managed credentials are stored in Keychain items shared only with the corresponding UnimeType app or input extension. A BYOK profile may be stored in synchronizable iCloud Keychain when iCloud Keychain is enabled. Android stores settings in private SharedPreferences, encrypts secrets with a key held in Android Keystore, and disables Android backup. Windows protects sessions and short-lived managed credentials with Windows Data Protection API. Linux stores non-secret settings in the user's configuration directory and uses the available system secret service for provider credentials. The active request credential is sent only to the endpoint selected for that request.
  • Purchase and balance records. The managed service processes the signed-in account identifier, store account token, provider transaction identifier, product identifier, credited amount, provider environment, transaction time, subscription state, and refund or revocation status to verify purchases, prevent duplicate crediting, maintain the account balance, process refunds, and provide support.
  • Managed-service usage and security records. The managed gateway may process request identifier, request time, selected model, token usage, cost, response status, product-scoped gateway user identifier, short-credential identifier, network address, and security events to meter usage, operate the service, investigate abuse, and diagnose failures. These metering records do not require storing submitted text or model output.
  • Optional native product analytics. Product analytics defaults off. If you turn on Share product usage data, Apple, Android, Windows, and Linux clients may send PostHog a random installation identifier; app, build, platform, surface, distribution channel, internal-test status, device, and operating-system information; signed-in state; route type; action type; outcome and error category; language and gateway-region labels; onboarding step; purchase kind; and latency range. After sign-in, supported clients replace the analytics identity with account_ plus a domain-separated hash of the UnimeType account identifier so consented events can be associated across devices. The raw account identifier, name, and email are not sent to PostHog. Input, output, surrounding context, clipboard contents, credentials, Base URLs, model names, raw errors, transaction identifiers, and purchase tokens are excluded.
  • Optional network performance data. On Apple and Android, the same Share product usage data choice also controls network timing samples. When enabled, a sample can contain the request route, destination host, protocol, connection-reuse state, HTTP status, success state, DNS/TCP/TLS/first-byte/gateway/body/total timings, platform, build, and channel. The UnimeType service can derive country and Cloudflare data-centre code from the request. Samples do not contain action text, output, credentials, or a stored user/session identifier. Turning analytics off stops later samples; Android also clears its pending in-memory sample buffer.
  • Website analytics and logs. The website uses PostHog to record page paths, external Referrer origin and domain, normalized UTM source/medium/campaign/content slugs, browser and operating-system categories, selected download platform, and signed-in status. PostHog project settings discard the request IP address. Before a choice is made, PostHog sends no website events. If you select cookieless analytics, PostHog creates a privacy-preserving server hash and does not store a PostHog identifier in cookies, Local Storage, or Session Storage; the website does not identify your account. If you allow analytics cookies, PostHog can recognize later visits and associate website events with account_ plus the same domain-separated account hash used by supported native clients. The raw account identifier, name, and email are not sent. A single Local Storage value remembers the analytics choice. The first-party D1 database separately retains AddMana cross-site beacons and server-confirmed UnimeType installer downloads; it is not the source for ordinary UnimeType pageviews or UTM analysis. Cloudflare may process request and security logs as the website and service infrastructure provider.
  • Support and reports. If you contact support, FIGURICH LTD processes the message and contact details you provide. If you submit the Android AI output report form, FIGURICH LTD stores the selected reason, optional details, app version, and submission time. The report does not automatically attach source text, AI output, API key, or device identifier. Do not put private text or credentials in the optional details field.

The current apps do not request contacts, photos, location, microphone, or advertising identifiers. UnimeType does not display advertising and does not use the collected data to track activity across other companies' apps or websites for advertising.

4. Request routes and recipients

In Unime Credits mode, the app obtains a short-lived, product-scoped credential and sends action content over HTTPS to the Unime gateway. The gateway authenticates the credential, routes the request to the configured model provider, returns the result, and meters usage against the account balance. At the effective date, managed tiers may use Volcengine/Doubao or OpenRouter and its routed model provider. Provider availability can change, and provider retention settings differ.

In Bring Your Own Key mode, the keyboard sends action content and the API key directly to the compatible Base URL saved in the app. The Unime gateway is not part of that request route.

Other recipients are limited to the service involved in the selected action: Apple or Google for store purchases; the website payment provider for website purchases; Apple or Google when you select that sign-in method; PostHog for the website analytics choice and when optional native product analytics is on; and Cloudflare for website, database, email-delivery, security, and network infrastructure. Each service processes data under its own terms and privacy policy. FIGURICH LTD requires processors acting on its behalf to protect data consistently with this policy and applicable law. UnimeType does not receive payment-card numbers handled by Apple, Google, or the website payment provider.

5. Legal bases

FIGURICH LTD processes account, requested AI-action, managed-service, balance, and purchase data because it is necessary to provide the service or take steps you request before using it. It processes security, fraud-prevention, cookieless aggregate website measurement, first-party download records, reliability, and support data for its legitimate interests in operating and protecting UnimeType, except where those interests are overridden by your rights. It processes transaction and accounting records where needed for legal obligations. Analytics cookies, account-linked website analytics, optional native product analytics, and native network-performance samples rely on your consent; refusing or withdrawing that consent does not block account access, purchases, paid functionality, or AI actions.

6. Choices and consent

Before the first AI action can send text, the app or keyboard asks for permission. You can withdraw that permission in the app; the next AI action asks again before sending text. On iOS and iPadOS, Full Access permits the keyboard to read shared settings and make a requested network call, but it does not make every keystroke an AI request. You can revoke Full Access in iOS Settings. Android provides equivalent AI-text permission and input-method controls in the app and Android settings.

Optional native product analytics starts off. You can turn Share product usage data on or off during onboarding or in Privacy/About settings. Turning it off calls the analytics opt-out path and stops later product events. Signing out or deleting the account resets the PostHog account association before later anonymous activity.

On the website, select Allow analytics cookies or Use cookieless analytics before PostHog begins website measurement. The Analytics settings button remains available after the choice. Switching to cookieless analytics removes the browser analytics identity and prevents later website events from being associated with the account.

You can also sign out of a device session, revoke another session, switch between Unime Credits and BYOK, replace or clear a BYOK credential, or stop using AI actions.

7. Retention and deletion

On-device settings and credentials remain until you replace or clear them, sign out where applicable, or the operating system removes app data. A synchronizable Apple BYOK record may remain in iCloud Keychain until you clear it or remove it through Apple's account and device controls. UnimeType account sessions and short-lived managed credentials are not synchronizable iCloud Keychain items. Android backup is disabled, and uninstalling the Android app removes its private preferences and encrypted credentials.

Account, purchase, balance, usage, security, website analytics, optional product analytics, and support records are retained only while needed for the purposes described above, to protect the service, resolve refunds or disputes, or meet accounting and legal obligations. The current service does not promise one fixed automatic deletion period for all of those records. Network timing rows stored by the UnimeType service are configured for deletion after 30 days. Model providers, store providers, PostHog, Cloudflare, and BYOK providers apply their own retention settings. This policy does not make a zero-retention claim for those systems.

Android AI output reports are retained until reviewed and no longer needed for support, security, or legal obligations. To request deletion, email support@unimetype.com with the approximate submission time, reason, and app version. Because the report contains no account or device identifier, FIGURICH LTD may be unable to distinguish it from another anonymous report with the same details.

You can delete a UnimeType account in the app or website. The public account-deletion page provides the website path and an email alternative when sign-in is unavailable. Deletion removes sign-in access, remaining credits, settings, sessions, managed credentials, and account-linked usage records not required for a retained transaction or legal obligation. Active website balance subscriptions are cancelled before deletion; App Store and Google Play subscriptions must be cancelled in the applicable store. Limited purchase, refund, support, security, and accounting records remain only where needed for transaction integrity, fraud prevention, refunds, unresolved disputes, accounting, or law.

8. Your rights

Depending on applicable law, you may request access, correction, deletion, restriction, objection, or portability of personal data. You can withdraw optional analytics consent at any time without affecting earlier lawful processing. Email support@unimetype.com from the account email address for a managed-record request. Include a provider transaction identifier only when needed to locate a disputed purchase. Do not email a password, session token, managed credential, or BYOK API key.

If UK data-protection law applies, you may complain to the UK Information Commissioner's Office. You may also contact the supervisory authority where you live or work when applicable.

9. Security and international processing

UnimeType uses HTTPS for the network routes described above and limits managed-service access to systems needed for authentication, purchases, routing, metering, analytics, security, email, and support. No transmission or storage system can be guaranteed completely secure. Depending on the selected route, processor, and provider, information may be processed outside your country, including in the United States or China. Applicable contractual and legal safeguards depend on the service and transfer.

10. Changes

If a data practice or purpose changes, FIGURICH LTD will update this page and its effective date before the new processing starts where required.