Privacy Policy
Your files, your choices, and the information online features need.
Review draft — not yet effective. Company name and contact email are confirmed. Registered address, applicable jurisdictions, provider/transfer arrangements and the retention schedule still require confirmation and legal review.
01 Who we are
LocalAI Tools is operated by HubtersAI LLC (“we,” “us,” or “our”). This policy describes personal information handled through our website, browser tools, account services and related online features, including when you use the tools without an account. Contact us at contact@localai.tools or through our contact form.
Local processing and online services handle different information. A feature being local does not mean every interaction with our website is offline or anonymous. Separate notices may apply to future desktop or cloud features when they become available.
02 Optional referral tracking
If you arrive through an affiliate link, you can choose whether to allow a referral cookie before continuing. Accepted tracking stores an opaque HTTP-only identifier for up to 30 days. We retain the referring affiliate, destination, acceptance time, expiry, and attribution to a newly created account. Declining tracking does not prevent use of the service. Remove the browser cookie through affiliate settings.
Affiliate applications include your channel, promotion plan, country, and accepted terms. Payout setup records a contact email, verification status, commissions, adjustments, and settlement references. Referred customer contact information is not shown to affiliates. Already recorded account attribution and financial records are handled separately from the browser cookie. See the affiliate program terms.
03 Files processed on your device
Supported browser inference processes your prompts, files and outputs on your device. Basic run analytics does not include prompts, file contents, generated content or raw error messages. Choosing a feature that uploads information, such as a support attachment or enabled run sharing, is a separate action.
Projects, chat histories, saved results, settings and model caches may be stored in your browser, including local storage, IndexedDB and browser caches. These records are not automatically synced to another device. Clear them through the relevant product controls or your browser’s site-data settings. Keep independent copies of important work; clearing site data can permanently remove it.
04 Information online features handle
- Account
- Email address, name, profile image where supplied, sign-in provider identifiers, verification records, sessions and account preferences. Available sign-in methods include email, Google and GitHub; availability depends on configuration.
- Email preferences
- If you opt in, we use your email address and subscription preferences to send newsletter updates or promotional emails through Resend. Manage your choices in your account or through links in those emails.
- Purchases
- Customer and transaction references, plan, entitlement, subscription status and billing records. Stripe handles payment collection. Do not send payment-card information through support forms.
- Support
- Messages, contact details, issue descriptions, attachments you choose to send and relevant browser or device diagnostics. Attachments can contain personal information; share only what is necessary.
- Run metadata
- We collect basic operational logs when you use the product, including without an account. Model and variant, configuration, requested and actual execution context, timing, outcome, coarse error category, app or project identifiers, installation/session identifiers, browser/OS versions, language, approximate hardware capacity and WebGPU availability. Connection metadata can supply country, region and timezone; this is not GPS location.
- Connections
- Website and download requests expose connection information, such as IP address and request headers, to hosting, delivery and source providers. Security and operational logs may record information about these requests.
Installation and session identifiers and device metadata are not guaranteed to be anonymous. We do not describe basic analytics as anonymous merely because it excludes your files.
05 Purposes & legal bases
We use account and purchase information to authenticate users, provide purchased access, administer subscriptions and respond to requests. We use operational metadata to diagnose failures, measure compatibility and reliability, secure the service and investigate abuse. Support submissions are used to address the issue you raise.
Where applicable data-protection law requires a legal basis, relevant bases may include performing our contract with you, complying with legal obligations, legitimate interests in operating and securing the service subject to your rights, and consent for activities that require it. We must obtain consent before any processing for which local law requires consent; merely using the service is not consent to optional content sharing.
07 Service providers & disclosures
Online features use providers for hosting, database and asset storage, delivery, authentication, email and billing. Current integrations include Cloudflare infrastructure, Stripe payments, Resend email, and optional Google/GitHub sign-in. Model and runtime downloads can connect directly to original sources such as Hugging Face, GitHub and runtime/CDN hosts, or our asset mirrors. Those sources receive the requests sent to them and apply their own policies.
The draft Data Sharing Policy describes who could receive optional run contributions, including authorized researchers and reviewers outside the original model provider. Full sharing is optional. Open Privacy settings in the footer to change your browser’s choice without signing in.
We may disclose information to service providers as needed to perform their functions, to recipients identified by a sharing choice you make, to comply with lawful requirements, or to protect rights and security. A corporate reorganization may involve transferring relevant records, subject to applicable protections and notice requirements. This policy does not authorize selling private inputs or outputs or using them for targeted advertising.
08 Cookies & browser storage
Sign-in uses session cookies and related security state. Browser storage also supports preferences, project history, caches and an installation identifier used for analytics. Some analytics delivery records may be queued locally for retry. Browser controls can remove or block storage, which can affect sign-in and erase local work.
Privacy settings stores your optional full sharing choice in this browser. You can change it while signed out. Basic operational logging continues with either choice.
09 Retention & deletion
Local records remain under your browser’s storage controls until deleted, evicted or otherwise lost. Server records require separate handling. Account, transaction, security and support information is retained according to its purpose, outstanding requests, fraud prevention, legal obligations and applicable limitation periods.
Retention schedule pending confirmation: fixed server retention periods and automated deletion coverage have not been verified for this notice. Proposed periods in the draft sharing policy are not current guarantees. Before this policy becomes effective, we must confirm and document category-specific periods or criteria, backup deletion and provider retention.
Use Delete account in your profile. Confirm using a code sent to your account email. An open checkout, unresolved invoice, or subscription that has yet to end blocks self-service deletion. If you have a lifetime purchase or need help removing other server records, contact us. We may retain billing, security and support records where necessary. If your account had subscription history, we retain a keyed fingerprint of your email while we enforce our one-trial rule. We use it to check trial eligibility if you sign up again with the same email. Support messages and attachments can still contain information you supplied. Deleting your account does not remove files or history saved on your devices.
10 International processing & security
Providers and recipients may process information outside your country. Applicable transfer requirements depend on the locations and roles involved. Any required safeguards, including appropriate contractual protections, must be confirmed for the relevant transfers before this policy becomes effective; this draft does not certify a particular transfer mechanism.
We use access controls and other safeguards appropriate to the service, but no system is completely secure. Protect your device, sign-in credentials and license tokens. Contact us if you believe information has been exposed. Do not send secrets or unnecessary sensitive information in support requests.
11 Your choices & privacy rights
Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, restrict processing, object to certain uses, withdraw consent, and complain to a data-protection authority. Rights can have legal exceptions. Withdrawal does not undo processing lawfully performed beforehand.
Send requests to contact@localai.tools. Tell us which account or record is involved without sending passwords or complete license tokens. We may request proportionate identity verification and will respond within applicable legal time limits. Local files never transmitted to us generally need to be managed on your own device.
12 Children & other people’s information
The service is not intended for children under 13. Where a higher minimum age or parental authorization is required, that requirement applies. Contact us if you believe a child has submitted personal information inappropriately so we can investigate and take appropriate action.
Only upload or contribute information you are authorized to share. Processing someone’s voice, likeness or personal data can require permission or another lawful basis. Your use of the service does not replace those obligations.
13 Changes & contact
We will update the revision date when this policy changes and provide appropriate notice of material changes. Additional consent will be requested where required. A revised notice does not retroactively authorize new uses of information.
Questions or requests: HubtersAI LLC, contact@localai.tools. See also our Terms of Service and contact page.