privacy policy

Olingal data handling

This page describes data used by the Olingal website at https://www.olingal.com and its browser extension.

Account and learning data

Olingal uses account information such as your email address, profile name and login identifiers to authenticate you and provide the service. Password-based accounts use password hashes; plaintext passwords are not stored. Dictionaries, vocabulary, learning records, settings, credits and billing records support your account's features and history.

Translation and AI requests

Text and the context you select for a translation or AI request are sent to the provider serving that request. Provider processing is needed to return the result. Avoid submitting information you do not want processed by that provider. Requests use account credits where applicable, and credit transactions are recorded.

Login and email

When the migrated Clerk login is enabled, Olingal uses its own dedicated Clerk application for sign-in, account verification and login email. If you choose Google sign-in, Google provides verified identity information through that application's Clerk connection. Retained legacy password hashes stay in Olingal's database; an original password entered for pending-account recovery is checked by Olingal's server and is not sent to Clerk. Recovery also requires a new Clerk email verification code.

The website uses Clerk session cookies and a host-scoped HttpOnly Olingal session cookie. The browser extension opens the Olingal website for sign-in and stores its own session locally.

Hosting and billing

The migrated website and API run together in one Next.js project on Vercel. Account and business data are stored in Olingal's dedicated Cloudflare D1 database. Existing account and business data are retained during migration. Payment processing is handled by the configured payment provider, with Creem used for the new billing integration. Olingal stores transaction and subscription references rather than full payment-card details. Legacy Stripe records are retained for reconciliation and billing history.

Optional analytics

The website may use Vercel analytics and performance measurements. Plausible runs only when a site-specific script is configured. These services receive the information required for their measurements.

Requests and contact

Contact support@olingal.com with questions about your data or requests to access, correct or delete account information. Billing records required for reconciliation may need separate handling from account content.

Reading and private review cards

The extension identifies words on pages where reading assistance is enabled. It keeps the existing local word/translation caches for that feature. An original sentence, page link and page title shown in a new review form are captured from the current page in memory; they are not added to a shared persistent context cache or uploaded as a review card in the background.

When you explicitly choose Save review card, Olingal receives the word, source and translation languages, meaning, original sentence, source URL/title and any pronunciation you confirm in that form. These fields and your difficulty responses, due times and review history are stored privately for your account in Olingal's dedicated database, so the website and extension can use the same review schedule. They are separate from the shared dictionary. Browser pronunciation is activated only when you choose its audio control and depends on your browser's available voices.

Browsing information is used only to provide the reading, translation and review features described here. Olingal does not sell it or use it for advertising. Olingal complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Text submitted for translation or AI generation is processed as described above; saving a review card does not itself send its context to an AI provider. Contact support@olingal.com to request access, correction or deletion of saved review data.

Account security and extension credit records

Olingal receives the client IP address supplied by its hosting platform and uses it to limit abusive sign-in and extension account-exchange requests. Rate-limit records contain a time-windowed hash derived from an IP-related key, a request counter and an expiry time. The extension does not request GPS location.

Olingal uses membership and billing-review status, free credits, paid-plan and purchased-credit balances, and usage charge/refund records to provide account features, show available credits and apply the current request price. The extension has no payment-card entry form or payment-history screen. Separate website and payment-provider handling is described above.