Effective and last updated: October 2, 2026.
1. Who this policy covers
This Privacy Policy explains how Model J Labs handles information when you visit modeljlabs.com, use the J Studio web workspace or Windows desktop application (including versions formerly called Axon Studio), contact us, or use account and licensing features. Model J Labs is responsible for the information handled by these services.
Some account and membership pages open our linked ChatGPT-hosted Model J Labs site. This policy also covers the Model J Labs records created there. Services you connect yourself have their own privacy policies. Products marked “coming soon” may have additional privacy information when they become available.
2. Information we handle
- Website requests. Our hosting and security providers process technical information such as IP addresses, browser and device information, requested URLs, timestamps, and operational or error logs to deliver and protect the website. Desktop sign-in rate limiting stores a hash derived from the requesting IP address.
- Messages and launch lists. When you submit a form, we store your name, email address, selected topic, message, and submission time. These records let us review your request and manage the launch interest you asked to register. Form submissions do not currently start an automated email campaign.
- Sign-in and account records. We store an account identifier, email address, display name when supplied, and account creation information. J Studio uses Cloudflare Access email sign-in. Linked membership pages may use ChatGPT sign-in. Authentication providers handle their own sign-in process; Model J Labs does not receive your ChatGPT password.
- Web workspace records. The web workspace stores model names, architecture and configuration documents, drafts, saved revisions, and training-run records or logs submitted by the workspace. Documents may contain file paths, dataset descriptions, custom formulas or code, and other text you include. Anonymous drafts can be stored on our servers under a browser-session identifier before you sign in, then associated with your account when you sign in.
- Desktop authorization and licensing. When you connect J Studio to an account, we process the device name you provide, sign-in codes, authorization times, token hashes, token expiry and revocation information, and licensing or membership status. Desktop and MCP access tokens are stored as hashes on the server. Treat the original token shown to you as a secret.
- Payments, when used. If you use a payment or license feature, we process the invoice identifier, amount, recipient wallet, payment status, public transaction hash, and related membership tier or expiry. Blockchain transactions are public and may reveal wallet activity. Do not send wallet private keys or recovery phrases.
3. J Studio files, training, and connected services
J Studio works with datasets, model files, project documents, and output folders you select for your workflow. Desktop features can inspect local hardware and runtime information to configure training. Project exports and outputs of local training are saved on your device; locally saved projects and hosted web workspace records are separate.
Using a web workspace, saving online records, submitting support material, authorizing a desktop device, or choosing a cloud or external integration involves sending the information needed for that operation. Depending on the integration, this can include a project configuration, selected files or datasets, prompts, training logs, and access credentials needed by the service you choose.
Examples include Hugging Face, Google Colab, cloud GPU providers, and model or API services you configure. Review the destination and its privacy terms before transferring personal or confidential data. Exported training code can also make network requests according to its configuration and dependencies.
Saving or editing an architecture in the hosted workspace does not by itself start training. The simple Open Lab browser experiments run locally and their downloaded experiment exports are saved to your device. Those experiments are distinct from J Studio’s hosted project storage.
4. How we use information
The current website does not include third-party advertising trackers. Project storage and account records are used to provide the relevant workspace and access features; storing a project is not an instruction to publish it or start a training job.
- Provide the service. Authenticate accounts, authorize desktop access, save and retrieve projects, record submitted training results, and support the features you choose.
- Respond to you. Review support and privacy requests, respond to messages, and manage requested product or launch interest.
- Manage access and payments. Maintain memberships, verify invoices or public payment transactions, and resolve licensing issues.
- Protect and operate the service. Diagnose failures, limit abuse, secure accounts and downloads, and meet applicable legal obligations.
7. Retention and security
Hosted projects, submitted logs, messages, and account records can remain stored after you close the browser or uninstall J Studio. Signing out, clearing cookies, and token expiry do not automatically delete all related records. We retain records needed for the service, support, security, payment administration, or applicable legal requirements, and review verified deletion requests manually.
Local files you create or export remain under your control on your device or the storage location you choose. External providers control the retention of information sent to them, and public blockchain records cannot be removed by Model J Labs.
We use HTTPS, account checks, access controls, and hashed desktop and MCP tokens to protect relevant records. No online service or storage system can guarantee absolute security. Avoid including passwords, access tokens, financial account details, or unnecessary sensitive personal information in project documents or support messages.
8. Your choices and privacy rights
You can choose whether to submit a message, register launch interest, save workspace records, or connect an external service. You can sign out and manage browser storage. An account is required for some desktop, cloud, and membership features.
Depending on the law that applies to you, you may have rights to access or obtain a copy of your personal information, correct it, request deletion, withdraw consent, or object to or restrict certain processing. Use the form below for these requests, to leave a launch list, or to raise a privacy concern. We may need to verify your identity before acting. We will explain if a legal, security, or record-keeping requirement limits a request.
To help identify anonymous workspace records, make the request before clearing the relevant browser cookie if possible. Do not include the cookie or an access token in your message. Removing hosted records does not remove copies you downloaded or data retained by an external service. You may also contact the privacy regulator that applies where you live.
9. Children
These services are intended for people who can understand and manage software projects and their data. They are not directed to children under 13. If you believe a child has provided personal information without appropriate permission, contact us so we can investigate and address it.
10. Changes to this policy
We will update this page when our services or information practices change and show the revised date above. Where required, we will provide an additional notice or request consent for a material change.
11. Contact Model J Labs about privacy
Use the privacy-request form below to contact the Model J Labs team responsible for privacy. State whether your request concerns the website, web workspace, desktop app, membership, or a connected service. Include the account email and relevant project or invoice identifier when needed, but do not include passwords, tokens, private keys, or sensitive dataset contents.
Your request is saved for the team to review manually; it does not subscribe you to a launch list. We use the name, email address, and message you submit to identify and respond to the request.