Privacy Policy — TrainMyLoRA
At TrainMyLoRA, your images, models, and creative work matter. This Privacy Policy explains what information we collect, why we need it, who helps us process it, and what choices you have.
We've written this policy in plain English so you can understand what happens to your data when you use TrainMyLoRA.
Effective Date: July 27, 2026
1. Information We Collect
We collect the information needed to provide, improve, and protect our LoRA training and generation services.
1.1 Account Information
When you create or access an account, we may collect:
| Data Type | Why We Need It | Required |
|---|---|---|
| Email address | Sign-in, account recovery, support, and service notices | Yes |
| Name | Account identification and personalization | Yes |
| Profile picture | Account personalization | No |
| Authentication provider ID | Secure Google or other social sign-in | When using social sign-in |
If you sign in with Google, Google sends us the account information you approve, such as your name, email address, profile image, and Google account identifier. We do not receive your Google password.
1.2 LoRA Training Data
When you train a LoRA, we collect and process:
- Images and ZIP archives you upload
- Filenames, captions, masks, and archive structure
- Image count, dimensions, formats, and dataset diagnostic results
- LoRA name, trigger word, and training type
- Selected base model and training settings
- Training task status, logs, errors, and provider responses
- Trained LoRA weights, configuration files, and related artifacts
- Your confirmation that you have permission to use the dataset
Your training data may include personal information about you or other people. Only upload material you own or have permission to use for AI training.
1.3 Generation Data
When you use a LoRA to generate content, we collect:
- Prompts and trigger words
- Selected LoRA and base model
- Image size, LoRA strength, seed, output format, and other settings
- Generated images or videos
- Generation task status, errors, timing, and provider responses
We refer to your training data, prompts, LoRA weights, and generated results together as User Content.
1.4 Usage and Technical Data
We automatically collect technical information that helps us run the Service:
Device Information
- Device type
- Operating system
- Browser type and version
- Language and screen size
Network Information
- IP address
- Approximate country or region
- Referring website
Service Activity
- Pages and features you use
- Task creation and completion events
- Downloads and account actions
- Error reports, performance data, and security events
1.5 Payment and Credit Information
When paid features are available, we collect:
- Product, plan, or credit pack purchased
- Order number, purchase date, amount, currency, and payment status
- Credit balance, credit usage, restorations, and adjustments
- Subscription status and renewal information
- Billing name, country, and other details returned by the payment processor
Important: We do not store complete card numbers, CVV codes, bank passwords, or other complete payment credentials. Payment details are handled by the payment provider shown at checkout.
1.6 Communications
If you contact us, we collect:
- Your email address
- Support requests and replies
- Files or screenshots you attach
- Feedback and feature requests
2. How We Use Your Information
We use your information for specific purposes.
2.1 Providing TrainMyLoRA
- Account Management: Create, authenticate, secure, and support your account
- Dataset Processing: Upload, store, inspect, and prepare training files
- LoRA Training: Submit training jobs and deliver trained weights
- LoRA Generation: Run compatible generation jobs and deliver results
- Storage and Downloads: Store and provide access to LoRA weights and generated files
- Credits and Billing: Reserve, charge, restore, and audit credits
- Customer Support: Investigate problems and respond to requests
2.2 Improving the Service
- Find and fix product errors
- Measure performance and reliability
- Understand which features are useful
- Improve dataset guidance and workflow design
- Prevent duplicate tasks and recover failed jobs
- Develop new features and supported model integrations
AI Training Transparency: We do not use your private datasets, LoRA weights, prompts, or generated results to train a general-purpose TrainMyLoRA model for other users unless you give us express permission.
We may use aggregated or de-identified usage statistics that cannot reasonably identify you or reconstruct your User Content.
2.3 Communications
We may send:
- Account and security notices
- Task, credit, payment, and refund updates
- Important changes to the Service or policies
- Replies to support requests
- Marketing messages only where permitted and with any consent required by law
You can opt out of marketing messages, but we may still send essential account and service messages.
2.4 Safety and Security
We use information to:
- Prevent fraud, stolen accounts, and credit abuse
- Enforce rate limits and protect our infrastructure
- Detect prohibited, illegal, or harmful use
- Investigate rights, safety, and security complaints
- Comply with valid legal requests
3. AI Processing
TrainMyLoRA uses third-party AI infrastructure to perform training and generation. When you start a task, we send the information needed to complete it to the selected provider.
This may include:
- A URL to your training dataset
- Training settings and trigger word
- LoRA weights
- Generation prompt and settings
- Task identifiers
- Generated results
Our current AI infrastructure provider is fal.ai. fal.ai may store API request inputs, outputs, and usage information under its own terms and privacy practices. Its documentation explains that request data may be stored by default and that some storage or deletion controls may be available.
Do not upload confidential, regulated, health, financial, biometric, or other highly sensitive information unless you have independently confirmed that TrainMyLoRA and every provider involved are appropriate for that information.
4. Legal Bases for Processing
For users in the European Economic Area, United Kingdom, or Switzerland, we process personal data under these legal bases:
| Legal Basis | When It Applies |
|---|---|
| Contract Performance | Accounts, training, generation, storage, downloads, credits, and payments |
| Legitimate Interests | Security, fraud prevention, analytics, support, and product improvement |
| Consent | Optional analytics, marketing, and any use that legally requires consent |
| Legal Obligation | Tax records, rights requests, disputes, and valid government requests |
You may withdraw consent at any time. Withdrawal does not affect processing that was lawful before withdrawal.
5. How We Share Information
We do not sell your personal information for money.
We share information only when needed to operate the Service, follow your instructions, protect people and systems, or comply with law.
5.1 Service Providers
| Provider | Purpose | Information Processed |
|---|---|---|
| Cloudflare | Website delivery, security, networking, CDN, and R2 storage | Website traffic, logs, datasets, LoRA files, and generated files |
| Supabase | Managed PostgreSQL database infrastructure | Account, task, credit, and application records |
| fal.ai | LoRA training and generation infrastructure | Task inputs, settings, LoRA weights, and outputs |
| Account authentication and analytics | Authorized profile data and website usage data | |
| Microsoft Clarity | Product analytics, heatmaps, and session recordings | Browser, device, and page interaction data |
| Payment providers | Payments, fraud prevention, and refunds | Billing and transaction information |
Providers may process information in countries other than your own. Their own terms and privacy policies also apply to their services.
5.2 Legal and Safety Requests
We may disclose information when reasonably necessary to:
- Respond to a valid court order, subpoena, or government request
- Protect someone's safety
- Investigate fraud, abuse, infringement, or illegal activity
- Enforce our Terms of Service
- Protect TrainMyLoRA, our users, or our providers
Where legally permitted, we may notify you before disclosing information in response to a legal request.
5.3 Business Transfers
If TrainMyLoRA is involved in a merger, acquisition, financing, reorganization, or sale, information may be transferred as part of that transaction. We will provide notice where required and continue to protect information under this policy until a replacement policy takes effect.
5.4 With Your Direction
We may share information when you ask us to, consent to it, or intentionally use a feature that sends information to another service.
6. Cookies and Analytics
6.1 Cookies We Use
Strictly Necessary Cookies
- Authentication and login status
- Security and fraud prevention
- Session management
- Core account functions
Functional Cookies
- Language and theme preferences
- Product settings
Analytics Technologies
- Page views and navigation
- Feature usage
- Error and performance measurement
- Click, scroll, and page interaction patterns
We may use Google Analytics and Microsoft Clarity. Clarity may provide heatmaps and session recordings. Sensitive form fields are intended to be masked by the analytics provider, but do not enter sensitive information into fields that do not request it.
6.2 Managing Cookies
Most browsers let you block or delete cookies through their privacy settings. Blocking necessary cookies may prevent sign-in or other account features from working.
Depending on where you live, you may have the right to opt out of certain analytics, sharing, or targeted-advertising activity. You can also contact support@trainmylora.io with a privacy request.
7. Data Security
We use reasonable safeguards designed to protect your information:
- Encrypted HTTPS connections
- Authenticated account access
- User-scoped database queries and storage paths
- Restricted administrative access
- Secure provider credentials
- Request validation and security monitoring
- Backups and recovery controls provided by our infrastructure vendors
No internet service can guarantee perfect security. You are responsible for keeping your account secure and for avoiding the upload of information that requires protections TrainMyLoRA does not expressly provide.
If you believe your account or data has been compromised, contact support@trainmylora.io immediately.
8. Data Retention
We keep information only as long as reasonably needed to provide the Service, maintain security and records, resolve disputes, and comply with law.
| Data Type | Typical Retention | Why |
|---|---|---|
| Account information | While active, then a reasonable deletion period | Account access, recovery, security, and legal obligations |
| Training datasets | Until you request permanent deletion or close your account | Retries, continued model management, and user access |
| LoRA weights and configuration files | Until you delete them, request permanent deletion, or close your account | Downloads and continued generation |
| Generated files | Until you delete them, request permanent deletion, or close your account | History, downloads, and reuse |
| Payment and credit records | As required for tax, accounting, disputes, and fraud prevention | Legal and financial compliance |
| Support conversations | As long as reasonably needed for support and dispute records | Support quality and legal protection |
| Analytics and security logs | According to operational need and provider settings | Security, debugging, and improvement |
Deleting an item from your Dashboard may first hide its application record without immediately deleting every underlying storage object, provider copy, log, or backup.
To request permanent deletion, email support@trainmylora.io from the address connected to your account. We may verify your identity. We aim to complete verified requests from active systems within 30 days unless a longer period is required or permitted by law.
Provider systems, logs, and backups may retain limited copies until their normal deletion cycles finish.
9. Your Privacy Rights
Depending on where you live, you may have the right to:
- Access: Request a copy of your personal information
- Correction: Correct inaccurate or incomplete information
- Deletion: Request deletion of personal information
- Portability: Receive certain information in a machine-readable format
- Restriction: Ask us to limit certain processing
- Objection: Object to certain processing based on legitimate interests
- Withdraw Consent: Withdraw consent for optional processing
- Opt Out: Opt out of certain sharing, targeted advertising, or profiling
- Appeal: Appeal a decision concerning a privacy request
To exercise a right:
- Email support@trainmylora.io
- Use the subject line "Privacy Request"
- Include the email address connected to your account
- Explain the right you want to exercise
We may ask for information needed to verify your identity. We will not discriminate against you for exercising a privacy right.
10. California Residents
California residents may have the right to:
- Know what personal information we collect, use, and disclose
- Request access, correction, or deletion
- Opt out of sale or sharing as defined by California law
- Limit certain uses of sensitive personal information
- Receive equal service after exercising privacy rights
We do not sell personal information for money. Some analytics technologies may be treated as "sharing" under California law even when no money changes hands.
To submit a California privacy request, email support@trainmylora.io with the subject "California Privacy Request."
11. European Residents
If you are in the EEA, United Kingdom, or Switzerland, you may have rights under the GDPR, UK GDPR, or similar law, including:
- Access
- Rectification
- Erasure
- Restriction
- Portability
- Objection
- Withdrawal of consent
You may also complain to your local data-protection authority. We encourage you to contact us first so we can try to resolve your concern.
12. International Data Transfers
TrainMyLoRA and its providers may process information in the United States and other countries. These countries may have different data-protection laws from your country.
Where required, we rely on lawful transfer mechanisms such as contractual protections, adequacy decisions, or other safeguards recognized by applicable law.
13. Children's Privacy
TrainMyLoRA is for users who are at least 18 years old and at least the age of legal majority where they live.
We do not knowingly collect personal information from children. If you believe someone under 18 has created an account or submitted information, contact support@trainmylora.io so we can investigate and take appropriate action.
14. AI and User Content
14.1 What AI Does
TrainMyLoRA uses AI systems to:
- Train LoRA weights from user-provided datasets
- Generate images or videos with compatible LoRAs
- Perform model-specific safety checks
- Support future dataset diagnostics and recommendations
14.2 What We Do Not Do
Without your express permission, we do not:
- Train general-purpose models on your identifiable private datasets
- Use your private LoRA weights to create models for other users
- Publish your private datasets or generated files
- Sell your User Content
Third-party AI providers may process and retain request data under their own policies, as explained in Section 3.
15. Changes to This Policy
We may update this policy as TrainMyLoRA, our providers, or the law changes.
- We will update the date at the top
- Material changes may be announced in the Service or by email
- Non-material changes take effect when posted
- Your continued use after an update means you acknowledge the revised policy
16. Contact Us
Questions, requests, or security concerns are welcome.
TrainMyLoRA Support
- Website: trainmylora.io
- Email: support@trainmylora.io
Typical response times:
- General privacy questions: 5–7 business days
- Verified rights requests: within 30 days
- Urgent security concerns: as quickly as reasonably possible
