Linqo privacy — development preview
Policy revision: 13 November 2026. This notice covers the feature variants below; it does not enable a feature or change an earlier purchase agreement. The v0.9.2 beta enables account-bound Polar checkout; contribution uploads remain disabled.
Linqo is in active development. Optional cloud features are configuration-gated; current preview builds with no Firebase configuration keep the library local. This document describes the implemented feature boundaries, not proof that checkout is live.
Your library
Saves, notes, file copies and English AI inference live on your device. Public title/caption/preview requests contact the original providers; optional model downloads contact the model host. GitHub update checks contact GitHub. No hosted inference, general analytics or automatic crash upload is introduced. Local diagnostics remain separately opt-in.
Those network requests disclose your IP address, the requested resource or URL and ordinary connection metadata to the contacted service and its infrastructure. A URL can itself contain personal information or an access token; do not use public preview fetching for private or secret-bearing links. Local inference does not make these separate network requests anonymous. Opening a link or choosing a cloud document provider is subject to that provider's own processing.
Optional accounts and purchases
Google sign-in uses Firebase Authentication. New paid upgrades use Polar hosted web checkout as Merchant of Record when activated. The backend verifies Google identity and binds the server-priced checkout to that account using a pseudonymous customer identifier. Linqo does not ask for a phone number for Polar checkout or receive card credentials. Polar receives billing/contact/payment details entered directly in checkout and applies its own privacy terms. The backend forwards the requesting IP to Polar for checkout eligibility and fraud handling; it is not persisted in Linqo's payment ledger. Historical Cashfree checkouts forwarded a phone number for order creation; these historic purchases remain restorable, but new public checkout is configured for Polar.
The backend keeps minimal account bindings, environment (sandbox/production), order/payment/refund IDs, amount/currency, timestamps and payment state. Linqo's application code does not intentionally persist raw provider responses/webhooks or log their contact fields. Checkout sessions use opaque, short-lived links and no-referrer/no-store responses. Cashfree session identifiers are cleared after expiry; unpaid orders/checkouts without financial records are removed after 90 days. Signed Polar webhook receipts retain only event/resource identifiers, type, digest and processing timestamps for up to 30 days, without the raw contact/billing payload. Production Polar orders retain minimal binding, status, refund-revocation and timestamp records for restoration. Account deletion does not erase needed financial history. Minimal payment/refund records remain for restoration, support and required records. Account ownership is never inferred from a checkout email. Ordinary Buy Me a Coffee donations do not automatically grant a tier. For a separately requested manual upgrade, the backend stores a pseudonymous account code, a hash of the provider payment reference, tier, verified USD amount and grant/revocation timestamps. The code links to the verified Google identity for restoration. You email the developer your payment reference, requested tier and account code privately; those support emails are not training data. Private account-bound offer eligibility and gift/revocation records are also retained to restore access and prevent reassignment. Manual grant records and identity bindings are retained for restoration, refunds and required records even after deleting the Firebase account. Pseudonymous identifiers can still be linked to an account; they are not anonymous data.
Signing out removes access to the account tier on this device while preserving local saves. Account deletion removes Firebase identity and retained contributions/consent; it does not erase local files, personal Drive backups or necessary purchase records. The same Google identity can restore a valid purchase after account recreation.
Password-protected backups and Drive
Backup behavior depends on your installed build. Earlier previews may export unencrypted ZIPs and may offer optional automatic Drive app-data backups. The updated backup flow below applies only to builds that ask for a password and export a .linqo file. Updating the app does not encrypt or delete an existing ZIP or cloud snapshot.
In the updated flow, new exports are password-protected .linqo files. Linqo encrypts them on the device using AES-256-GCM with a fresh random salt and PBKDF2-HMAC-SHA256 (600,000 iterations). Keep the password separately: Linqo cannot recover it. Passwords are not uploaded, stored in the account or included in backups. Saves, notes, extraction results, collections and copied files are included; models, credentials, entitlements and cached previews are excluded. Temporary plaintext staging files remain inside the app's private cache while preparing/restoring. Cleanup is attempted after the operation; crashes, interruption or cleanup failures may leave temporary files until the app or operating system removes them. Encryption does not protect a compromised or unlocked device.
Choose your destination explicitly in Android's Files picker. If Google Drive's document provider is available, you can save/open the file there using that provider's own account and permissions. Updated builds make no new automatic Drive API uploads. Google sign-in in Linqo is not required for Files-based backup. Restores are validated merges, not continuous sync. An incorrect password or failed authentication does not import content. Old unencrypted ZIP backups remain importable and are not retroactively encrypted. Your chosen provider may retain its own copies or versions; delete these through that provider when no longer needed.
A separate connection to Linqo's earlier Drive app-data snapshots remains available for restoration only. Those older ZIP snapshots are unencrypted by Linqo and use Google's storage protection. They remain after signing out/disconnecting; manage/delete them through Google Drive settings. This legacy connection uses the narrow app-data scope and cannot read the rest of Drive. New Files-based backups must be restored using Import saves in the Files picker.
Google account information and Drive backup content are not sold, used for advertising or supplied as training data. Contribution uploads remain disabled pending provenance/consent review. Linqo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Optional extraction contributions
Default off and separate from account/backup/diagnostics consent. If enabled, Linqo can upload small eligible English public-source excerpts, category, model/schema version, extraction result and optional correction. Personal notes, files and manual/private inputs are excluded. Obvious links, emails, handles and long numbers are removed; sensitive-looking inputs are rejected. Filtering cannot guarantee anonymity or identify every private fact. Do not enable this option if you do not want any source excerpts uploaded.
Limits: two/account/day, 100 samples globally/day, 8 KiB each, bounded contribution storage. Raw server source/output expires after 30 days. Minimal contribution IDs/owner metadata remains to let you request deletion of exported examples. Maintainer copies are pulled privately, unreviewed copies expire after 90 days, and reviewed examples may be retained for permitted model development. A sample is not automatically considered correct or authorized for training merely because it is public.
View or delete contributions in Account & backup, including deletion requests for expired server examples. Deletions apply to maintainer copies at the next successful pull and invalidate prepared datasets. Opt-out immediately stops future queuing and persists locally even when the server is unavailable. Already completed/in-flight transfers may require a deletion request. Removal of an example cannot guarantee removal of its influence from an already trained model. No automatic phone training or model publication occurs.
Controls and contact
Continue without an account, keep password-protected backups, disconnect legacy Drive access, opt out of contributions, inspect/delete samples, or delete your account in Settings. Avoid posting private receipts or source text to public GitHub issues. Contact aryandurgude123@gmail.com privately for support or privacy requests. Linqo’s software supplier and support/privacy contact is Aryan Durgude (NotAl2), India, at aryandurgude123@gmail.com. Only this name, country and contact email are published. Polar is the Merchant of Record for purchases through its hosted checkout; its buyer terms identify the payment seller and address. This does not remove the supplier’s own applicable legal obligations.
Google/Firebase, Cloudflare, Polar (and its payment subprocessors), historical Cashfree services, Buy Me a Coffee, Buy Me a Tea and their payment processors, GitHub and source providers apply their own policies. Linqo's application logging is designed to exclude secrets, checkout links, phone numbers and content payloads. This is not a promise that infrastructure providers collect no access, security, billing or account metadata. Email support also processes the information you choose to send. Providers may process information outside your country; Linqo does not promise India-only storage for these services. Infrastructure quotas/outages can interrupt optional services without deleting the local library.
Privacy requests and retention
Email aryandurgude123@gmail.com with the subject Privacy request to ask what account-linked data is held, request correction or deletion, withdraw optional consent, or raise a privacy complaint. Identify the affected account or Linqo account code and the request; do not send passwords, tokens, full card/bank details or identity documents. Only the minimum additional information needed to verify the request will be requested. If you cannot access the original account, explain that privately so a safe verification route can be considered.
Support will acknowledge a complaint within 48 hours and work to resolve it within one month. Keep the email thread as your reference. A response will explain the action taken, any information still needed, or any data that must remain and why. This process does not limit a shorter applicable legal deadline or your right to approach the appropriate authority. It is not necessary to post a complaint publicly first.
Local library data stays until you delete it, clear app storage or uninstall. Files-based backups and legacy Drive snapshots stay under your control until deleted through their respective storage providers. Account deletion is separate from deleting those copies. Minimal purchase, identity, offer and gift records currently remain where linked to restoration, revocation or payment history; the preview does not implement an automatic purge of those records. Retention is not a licence to reuse them for advertising or training. Support correspondence is used to handle the request and related disputes or legal obligations, not as training material. A deletion request can also cover support correspondence; any necessary retained portion must be explained.
Final seller-specific accounting, dispute and statutory retention periods have not yet been qualified. They must be documented before public paid sales; no universal or indefinite statutory retention period is claimed here. Contribution retention is described separately above. Actual security-incident reporting and provider retention obligations require an operational review, not just a statement in this policy.
Children and changes
The connected account, purchase and contribution preview is not offered to children under 18. A verifiable parental-consent flow is not implemented; a parent or guardian should contact support if a child has supplied account data. Linqo does not claim that Google sign-in verifies age. This notice does not authorise collecting additional identity documents from children.
Material changes to cloud-data use will be described in an updated notice before the new use starts, with separate consent where required. An updated policy does not retrospectively authorise training on previously collected library or Google data.
Current prebuild access
Tier limits apply locally, including without sign-in. For a reviewed XL/XXL prebuild grant, you can email aryandurgude123@gmail.com with the requested tier and a pseudonymous Linqo account code. That support email and the minimal grant/revocation record are used for access and restoration, not model training. Donations are separate and do not automatically assign a tier. Do not send Google passwords, authentication tokens or private saves. Existing verified entitlements remain restorable with the same Google account.