Lingoji · Legal
Privacy
Developer: Lingoji
Questions: lingoji@hexavueon.com
Scope
This draft covers the Lingoji iOS learning app and its official website. It describes the current Free and Plus implementation, not deferred AI features. Account-backed data is collected even when you use an anonymous account. Identifiers and hashes that can be associated with an account are not treated as anonymous simply because they are hashed.
Account and learning information
Lingoji uses Firebase Authentication to create an account identifier. When you sign in with Apple, Firebase can also receive the name and email Apple supplies, including a Hide My Email address. Lingoji’s learner database does not have name or email columns.
The app synchronizes learned characters, review types, ratings and times, schedules, and mastery outcomes with its backend on Cloudflare. This restores progress and personalizes your review queue. Review synchronization uses an app-generated device identifier stored in the iOS Keychain; that identifier may survive reinstalling the app. It is not an advertising identifier.
Purchases
Apple handles payment details. Lingoji does not receive your card or bank information. Lingoji verifies and stores subscription product and transaction identifiers, purchase lineage, purchase and expiry dates, entitlement status, and renewal or revocation events. These records connect purchases to the correct Lingoji account and prevent replay or conflicting ownership.
Practice that stays on your device
Pronunciation recordings stay on-device for local recording and playback when cloud checking is off. Optional Plus pronunciation checking is available. Enabling cloud checking sends completed recordings through Lingoji’s Cloudflare backend to Tencent for approximate pronunciation feedback, which may miss errors. The app explains this before the first upload, and cloud checking can be turned off in Study Preferences. Local practice remains available without cloud checking.
The cloud flow processes audio temporarily without storing clips in Lingoji’s database, object storage, or application logs. It retains limited assessment outcomes for up to 30 days and subscription-linked usage records to enforce the monthly allowance and recover interrupted checks. Account deletion removes assessment results and retains current-window subscription consumption needed for restoration. Tencent’s actual processing and retention settings still require owner confirmation; this draft does not promise that Tencent retains no audio. Provider outages or missed maintenance jobs can delay scheduled cleanup.
Raw handwriting paths are evaluated on-device and are not uploaded. Review ratings and handwriting mastery outcomes can synchronize as learning progress. Downloaded content, preferences, and caches are also stored locally.
Diagnostics and service providers
Lingoji’s backend diagnostics include request and error context. Some errors carry a stable hash of the user identifier and can therefore be account-linked. Diagnostics support operation and troubleshooting, not cross-company advertising.
Firebase Authentication also sends SDK/platform diagnostic information through its default user agent. Firebase describes this subset as unlinked diagnostic data used for SDK adoption analytics. This is separate from an app-owned Firebase Analytics or Crashlytics integration; neither is added by the current app.
Cloudflare hosts the API, database, content storage, and planned website delivery. Its infrastructure processes request metadata, such as IP addresses and routing information. The owner must confirm the actual deployed logging and backup settings before this policy is approved. See Firebase’s data disclosure and Cloudflare’s privacy policy for their descriptions of provider processing.
If you email support, we receive the information you choose to send and use it to respond to your request. Support email is hosted by Zoho Mail. There is no automatic retention rule configured for support messages; this does not mean messages are automatically deleted. Do not send passwords, private keys, payment credentials, or recordings. The owner must still define a support-message retention and deletion procedure.
Website visits
The website adds no analytics or advertising scripts, forms, third-party embeds, or application cookies. Hosting infrastructure can still process request metadata. This draft does not claim that visiting the site creates no data at all.
Deletion and retention
Open Profile → Account & Data. For an Apple-linked account, use Delete Account. The flow removes the live learner record and associated progress, performs local cleanup, and deletes the Firebase account. Interrupted deletion can require reconnecting and completing the app’s recovery steps. Deleting the app is not account deletion. Deleting an account does not cancel a subscription with Apple.
For an anonymous account, choose Delete My Data in the same menu without signing in with Apple. A connection and confirmation are required. The app deletes that anonymous account’s synced progress, clears its local learning history, and deletes its Firebase account before starting a fresh anonymous session. If deletion is interrupted after it starts, finish it from the same menu before learning or syncing. Contact support if you cannot access the app; a separate identification procedure for such requests still requires owner confirmation.
Limited purchase lineage and former-owner digests remain after account deletion for restoration, replay and ownership protection. These retained digests are pseudonymous, not guaranteed to be anonymous. Live account purchase records are not subject to this detached-account cleanup policy. Active subscriptions, grace periods, billing retry and unresolved Apple state retain their detached purchase records. A failed or inconsistent Apple verification retains those records rather than treating the subscription as expired.
The locally prepared cleanup policy uses a buffer of 30 days (30 times 24 hours) after the first successful Apple confirmation that a detached purchase is expired or revoked. A new terminal subscription period starts a new buffer; an active renewal, grace period or billing retry cancels the deletion deadline. A fresh successful verification and guarded ownership check are required before deletion. The daily job processes at most ten detached purchase lineages, so queue size, Apple outages or missed jobs may delay actual removal. This is not a promise to erase records at an exact expiry instant.
The initial Dev observation mode does not physically delete purchase history or notification receipts. Production cleanup is disabled. Hosted migration, deployment, restoration evidence and separate approval are still required before destructive purchase cleanup is enabled; this draft does not claim those steps have occurred. Once guarded cleanup is enabled and completes, it removes eligible detached transactions, lifecycle events, proven-associated notifications, owner digests and the temporary checkpoint, without leaving a permanent purchase marker. New unassociated Apple notification receipts omit transaction identifiers and have a 30 days retention window from first processing; destructive cleanup removes those expired receipts too. Unidentified legacy notifications require separate review.
A later valid renewal may be restored using a verified signed purchase and freshly checked Apple state even after old purchase records have been removed. This does not restore deleted learning history or merge it into an existing account. A signed purchase proves possession of Apple-verified purchase data, not that the claimant is the same person as the deleted learner. A different live account’s known purchase ownership prevents reassignment.
Deletion tombstones have a 30-day validity window, but that window alone does not establish an automatic physical purge. The daily maintenance job removes expired deletion markers and account-merge requests when it runs successfully. Backup/recovery history and provider retention are separate from live database cleanup.
Actual hosted retention settings, logs, backups, support procedures and production purchase cleanup still require owner confirmation. This draft does not promise immediate erasure of every record. Data security and deletion are not guaranteed solely by the presence of a privacy notice.
Owner confirmation before publication
The owner must verify production Firebase, Cloudflare, logging, backups, and other integrations; define retention and anonymous-account deletion procedures; review applicable privacy obligations and user-request handling; and approve the final wording. Search-indexing restrictions discourage indexing during review but do not make this document private. Please contact the developer using the address above with questions.
