Privacy Policy
Last updated: October 7, 2026
TensorTrace ("we", "us") operates TensorTrace.net, its model library, public API and optional community features. This notice explains how we handle information about people who use these services. For privacy questions or requests, email i@leaskh.com.
Information we handle
- Browsing and API requests. Our hosting and delivery services receive technical information such as your IP address, browser information, requested address, request time and errors. This supports delivery, troubleshooting and protection against abuse. Searches are part of requests; avoid putting sensitive personal information in them.
- Website analytics. We use Google Analytics to understand website usage and improve the service. It processes page views, interactions, page addresses and referrers, browser and device information, and approximate location.
- Accounts, when enabled. We store your account identifier, username, profile names, email address when provided, avatar and linked sign-in identity information. Email passwords are stored as salted hashes. Verification, recovery and session tokens support account security.
- Third-party sign-in. A provider may supply an account identifier, profile name, email and avatar according to the permissions you approve. We use these to authenticate you and maintain your profile. We do not receive your password for that provider.
- Favorites and contributions. We store saved models and any comments, mentions or topics you submit. Favorites are private to your account; public profiles and comments are visible to other people and through the public API.
- Public catalog information. Model and benchmark records may include publicly listed author names and source links. We collect these from the sources identified in the model's evidence and use them to maintain the catalog.
- Correspondence. If you contact us, we use the information you send to address your request.
Account and community features can be disabled. This notice describes their data handling when available; browsing the public library does not require an account.
How we use information
We use information to deliver the service you request, authenticate accounts, maintain profiles and favorites, publish contributions you choose to make public, send necessary account emails, answer requests and keep the service secure. We do not sell personal information or use private account information to train AI models.
Where applicable, our grounds for processing include providing the service you request, legitimate interests in operating and protecting the service and maintaining a useful public catalog, your consent where required, and legal obligations. Optional profile fields are not required to browse the library. Account functions require the information needed to identify and secure the account.
Cookies and browser storage
When accounts are enabled, TensorTrace uses a necessary session cookie to maintain sign-in and prevent unauthorized requests. Anonymous sessions expire after two hours and signed-in sessions after 30 days; temporary sign-in cookies may also be used during authentication. You can clear or block cookies through your browser, although account features may then stop working.
Google Analytics uses first-party cookies, including _ga, and a browser identifier to measure visits and activity across sessions. Our network providers may also use their own security mechanisms and process technical request information.
Service providers and external websites
- Hosting and Cloudflare. Hosting providers and Cloudflare help deliver and protect the website and may process network request information. See Cloudflare's Privacy Policy for its handling of this information.
- Google Analytics. Google provides website analytics and processes the information described above. See Google's Privacy Policy for its handling of this information.
- Identity and email providers. Your chosen sign-in provider handles its authentication flow. When email sign-in is enabled, our configured email delivery service receives the address and message needed for verification or recovery.
- Avatars. Your browser may load a third-party profile image, Gravatar or a DiceBear-generated image. These services receive the image request and technical network information. Gravatar URLs include a hash of an email address; DiceBear URLs use an account identifier as a seed. You can upload an avatar to have TensorTrace serve that image instead.
- Linked content. Model links, user links and externally hosted images may lead to other services. Their privacy practices apply to your interactions with them.
We may also disclose information when required by law or necessary to protect the service and people's rights. Hosting and providers may process information in countries other than yours. Contact us for information about the providers involved in your request and applicable transfer protections.
Public content
Your username, display name, avatar and published comments can appear on public profiles, model pages, timelines and API responses. Your email address and private identity details are not included in public user profiles. Public content may be indexed by search engines or copied by other people and services. Removing it from TensorTrace cannot remove copies they already hold. Do not publish information you want to keep private.
Retention and security
Account, profile and favorite records are kept to provide your account until they are removed or a deletion request is fulfilled. Comments remain available until removed. Session and authentication records expire; verification and recovery links expire after 30 minutes. Expired records are cleaned up while the account service runs. Expiration of a credential does not imply immediate removal from every backup.
Technical records and correspondence are kept only as needed for troubleshooting, security, handling requests or legal obligations. Retention depends on the purpose of the record, account status and these operational or legal needs. Public catalog evidence may be retained to support provenance and historical comparisons. Backup copies, where kept, may persist through their normal replacement cycle.
We use access controls, HTTPS on the public service and password hashing to protect information. No service can guarantee absolute security.
Your choices and rights
You can manage cookies through your browser and use the Google Analytics opt-out browser add-on to prevent Google Analytics from receiving website activity from supported browsers.
When account features are available, you can update your profile, replace your avatar, remove favorites and delete your own comments. You can also request access, correction or deletion of personal information by emailing i@leaskh.com. Include enough information to identify the account or public record; do not send a password or API key. We may ask for proportionate verification before changing or disclosing private information.
Depending on applicable law, you may also have rights to receive a portable copy, restrict processing, object to processing, withdraw consent or complain to your local data protection authority. We assess requests under applicable law and explain any limits, including information needed for legal obligations or security.
Children and updates
The service is not directed at children under 13. If you believe a child has supplied personal information, contact us so we can investigate and remove it where appropriate.
We will update this page when our practices change and revise the date above. For material changes affecting existing accounts, we will provide additional notice where required.