1. Who We Are

Citra is operated by Citra ("Citra", "we", "us", or "our"). Citra is a closed, consent-based AI image generation and model training platform designed to help artists, asset owners, developers, and users participate in an ecosystem where images used for model training are uploaded, reviewed, permissioned, and tracked inside Citra.

Contact: citra.ai.tech@gmail.com

Business address: Not publicly listed. Contact us by email for legal notices.

2. Eligibility, Accounts, and Beta Access

You must be at least 18 years old, or the age of legal majority in your jurisdiction, to use Citra. A single Citra account may act as a User, Artist / Asset Owner / Rights Controller, and Developer. Admin accounts are separate internal accounts used for review, approvals, payouts, moderation, and platform operations.

Citra may be offered as a beta, staging, private access, or early access service. Features may change, break, or be removed; pricing, availability, model behavior, training cost, and generation performance may change; and certain Services may be experimental, unstable, incomplete, or subject to interruption.

3. User Content and Operational License

"User Content" includes images, captions, tags, prompts, metadata, model names, model descriptions, generated outputs, training parameters, and other materials you upload, create, submit, store, train with, publish, or otherwise provide through Citra.

You keep ownership of your User Content, subject to rights you grant through Citra. You grant Citra a limited, worldwide, non-exclusive license to host, store, process, display, reproduce, transmit, moderate, review, format, analyze, internally distribute, and otherwise use your User Content only as needed to operate, secure, improve, and provide the Services, enforce these Terms, comply with law, and support the rights and revenue tracking systems. Citra does not owe a separate fee for this operational use unless a separate written agreement or platform rule says otherwise.

This operational license does not mean every developer may train on every uploaded image. Developer training rights are governed by image status, permission workflows, and Creator / Developer terms. Removing, deleting, or unpublishing User Content does not automatically revoke rights already granted for completed training jobs, completed generations, historical revenue accounting, compliance records, audit logs, permission records, model lineage records, or other records Citra reasonably needs to preserve platform integrity and legal compliance.

4. Image Rights Status

Free to Use: eligible Citra developers may use the image for model training and monetization on Citra without a revenue share owed to the image owner, unless otherwise stated.

Standard: eligible Citra developers may use the image for training on Citra, subject to Citra's revenue sharing or rights tracking rules.

Permission Required: developers must request permission and provide the required code or approval before using the image for training. Custom compensation, collaboration, or usage terms may need to be arranged directly between the relevant parties unless Citra provides an automated system.

Publication or visibility settings, such as whether an image is publicly discoverable, are separate from the image rights status above and do not automatically change the rights category selected for the image.

5. Review, Permission, Workspace, Generation, and Training

Citra may require artist verification and image approval before images enter the training ecosystem. Citra is designed to reduce training-data rights risk through upload controls, permission workflows, rights records, and review, but approval does not create an absolute legal guarantee that no third party will ever raise a claim. Citra may use automated systems, machine learning systems, human review, or hybrid moderation systems to review content, permissions, training requests, model publishing, transactions, payouts, or platform activity.

For Permission Required images, developers may need to submit a permission request, provide a permission code, and receive owner approval. Citra may store permission decisions to support rights tracking, training records, revenue logic, and disputes.

Citra may record dataset composition, image status, permission status, captions, training parameters, model lineage, and rights metadata when a training job begins (a "Training Snapshot"). Later changes may not retroactively invalidate completed training records, completed generations, historical revenue accounting, or audit records.

6. AI Generation and Generated Outputs

Citra is built as a closed, consent-based AI image ecosystem, and Citra controls the platform-side rights, permissions, training records, and model publishing rules for models made available through the Services. Generated results may still be imperfect, unexpected, similar to other outputs, or unsuitable for your intended use.

Unless Citra clearly states otherwise in the product or these Terms, generated outputs may be used commercially by the generating user, subject to applicable law, third-party rights outside Citra, foundation model or provider restrictions, and Citra platform policies. Citra grants the generating user the platform-side permission to use generated outputs under Citra's rules, but this does not override applicable law or third-party rights outside Citra.

Citra's consent-based training controls are intended to reduce the risk that Citra models are trained on unauthorized image datasets. However, Citra cannot guarantee that a specific generated output will be original, trademark-safe, likeness-safe, suitable for every commercial context, or free of every possible third-party claim. Users are responsible for reviewing outputs before publication, client delivery, advertising, or other sensitive commercial use.

Foundation model notice: Some Citra models, training workflows, or generation workflows may use or be derived from third-party foundation models, including Stable Diffusion 1.5, SDXL, or other models that have their own license terms, acceptable use restrictions, and provider requirements. Citra may record base model metadata, model lineage, training snapshots, and provider configuration to help determine which rules apply to a model or generated output.

Open-source and third-party tool notice: Citra may use, interoperate with, or reference third-party tools and open-source projects for training, generation, workflows, infrastructure, or development. Those tools remain owned by their respective rightsholders. Citra's use of a third-party tool or model does not imply endorsement, sponsorship, partnership, or approval by that project unless Citra clearly says otherwise.

7. Payments, Revenue, Payouts, and Providers

Citra may use credits for image generation, model training, and other paid features. Deposits and payments may be processed by Stripe or another provider. Payouts and withdrawals may be subject to review, provider requirements, fees, limits, minimums, and availability.

Citra may temporarily hold balances, delay payouts, freeze withdrawals, reverse credits, or require additional review where fraud, abuse, chargebacks, disputes, legal risk, payment provider review, rights disputes, or policy violations are suspected. Citra does not guarantee visibility, discovery, sales, generation volume, training demand, revenue, payouts, creator earnings, developer earnings, or commercial success.

Citra may update future revenue-sharing, cost-sharing, minimum price, platform fee, payout, and provider-cost allocation rules as the platform changes. Material changes will generally apply prospectively and, where reasonable, Citra may provide notice through the product, website, or other appropriate channel. Retroactive corrections may be made where needed to fix errors, comply with law, handle fraud or abuse, address chargebacks, respond to provider requirements, or resolve platform integrity issues.

Certain Services depend on providers such as Supabase, Cloudflare R2, Stripe, Modal, Render, and others. Citra is not responsible for outages, delays, failures, restrictions, pricing changes, policy changes, payment holds, data processing delays, GPU failures, storage failures, network failures, or service interruptions caused by providers outside Citra's reasonable control.

8. Prohibited Conduct, Enforcement, and Disclaimers

You may not upload unauthorized content, bypass permission systems, scrape or exfiltrate assets, abuse payment/balance/training systems, violate sanctions or export control laws, or use Citra for illegal, abusive, exploitative, hateful, harassing, non-consensual, or harmful content. Uploaded images must be works you created or have the rights and permission to share for AI training, and must not be copyrighted characters, direct copies, or third-party works you do not have permission to use.

Citra may warn, restrict, suspend, terminate, remove content, unpublish images, deactivate models, freeze balance, withhold payouts, or take other reasonable action. The Services are provided "as is" and "as available." Citra does not provide legal advice, copyright clearance, trademark clearance, or infringement determinations.

These Terms are governed by the laws of Thailand, unless applicable consumer or data protection law requires otherwise. Questions may be sent to citra.ai.tech@gmail.com.

1. Information We Collect

Citra may collect account information, artist verification information, uploaded and generated content, Workspace and training information, payment and wallet information, usage and technical information, and communications you send to us.

2. How We Use Information

We use information to create and secure accounts, operate image discovery, upload, Workspace, permission requests, generation, training, model publishing, wallet, payments and payouts, verify artists, review images, track image rights, permissions, model lineage, revenue sharing, prevent fraud and abuse, investigate reports, improve reliability, and comply with legal, tax, accounting, payment, and regulatory obligations.

3. Sharing, Transfers, Cookies, and Retention

We may share information with service providers such as Supabase, Cloudflare R2, Stripe, Modal, Render, admins and reviewers, relevant developers or asset owners in permission workflows, legal or safety authorities, and business transfer parties where needed. Citra and its providers may process and store information in countries outside your country of residence.

Citra uses cookies for login sessions, security, preferences, consent settings, and service operation. Optional analytics or marketing cookies may be added only where disclosed and, if required, with consent.

We retain information as long as reasonably needed for account operation, transactions, tax/accounting, refunds, chargebacks, payouts, audit logs, fraud prevention, rights ledger, permission records, model lineage, revenue distribution, moderation, rejected uploads, appeals, IP complaints, legal compliance, and disputes. Citra may retain Training Snapshots, permission decisions, model lineage records, transaction records, and audit logs where needed.

4. Security and Your Rights

Citra uses technical and organizational measures intended to protect information, including HTTPS, access controls, session security, hashed passwords, provider-managed storage security, audit logs, rate limits, and administrative controls. No system is completely secure.

Depending on your location, you may have rights to access, correct, delete, object to, restrict, or request a copy of certain information, withdraw consent where applicable, and complain to a data protection authority. Contact citra.ai.tech@gmail.com to make a request.

Citra uses strictly necessary cookies for login sessions, authentication, account security, cookie consent state, and routing. Preference cookies may remember settings. Analytics or marketing cookies may be added in the future only where disclosed and, if required, with consent. Some providers such as Stripe may use their own cookies when you use checkout or payment features.

You can manage cookies through Citra's cookie settings where available and through your browser settings. If you block necessary cookies, some Citra features may not work correctly.

Citra credits may be used for image generation, LoRA training, and other paid features. Credits are not a bank account, stored-value account, securities account, or cash deposit account.

Users may add credits through supported providers such as Stripe. Citra may show payment processing fees before checkout. Generation and training may charge credits according to prices shown in the product. If generation or training fails because of a platform/provider error, Citra may refund or reverse the charge according to platform logic.

Citra wallet credits are recorded internally in U.S. dollars. Checkout may be offered in supported local currencies, such as USD, THB, JPY, or EUR, using an exchange-rate quote available when the checkout session is created. Payment providers, card issuers, banks, and payment networks may apply their own exchange rates, fees, holds, declines, or refund handling. A displayed exchange-rate reference is an operational estimate for that checkout session and does not guarantee the rate used for any later deposit, refund, withdrawal, or provider-side charge.

For developer-published models, Citra may estimate or allocate GPU/provider generation costs to the model revenue side before calculating developer or model-owner earnings. Estimates may use provider pricing, example generation measurements, cold-start estimates, safety margins, or other operational data, and actual costs or earnings may differ.

Eligible users may request withdrawals or payouts where available. Withdrawals may be subject to minimums, payout fees, identity/tax/fraud/compliance review, provider availability, account status, balance availability, and admin review. Withdrawal requests are recorded against the user's U.S. dollar wallet balance. If Citra or a provider shows a local-currency payout estimate, the final payout amount may depend on the payment method, provider, and exchange-rate information available when the withdrawal is approved or paid. Refunds are not guaranteed except where required by law or expressly stated by Citra.

If you upload images or datasets to Citra, you confirm that you own the content or have sufficient rights to upload it, you can select the relevant image status, the content does not violate third-party rights, and metadata is accurate to the best of your knowledge. You should upload works that you created and have the rights to share for AI training, and avoid copyrighted characters, direct copies, or works you do not have permission to use.

Developers may train LoRA models using Citra Workspace datasets and permitted images. Developers must use only images they are allowed to use, prepare captions responsibly, not import unauthorized external datasets, not bypass permission codes or approvals, not hide or mislabel training sources, and not exploit training quotas, generation quotas, or cost controls.

Citra may record Training Snapshots for rights tracking, revenue sharing, dispute handling, audit, and platform safety. Models trained, merged, adapted, fine-tuned, or derived from datasets or prior models may remain subject to underlying rights, permissions, attribution, revenue-sharing rules, or platform restrictions.

Foundation models and training tools may have their own licenses, technical limitations, usage restrictions, attribution notices, or commercial-use conditions. Developers must follow Citra's published workflow rules and must not use Citra to bypass foundation model licenses, open-source licenses, provider restrictions, export restrictions, or acceptable-use rules. Citra may require or preserve base model metadata, training configuration, model lineage, and related records to support rights tracking, revenue logic, compliance, and future audits.

Developers may set model pricing within limits provided by Citra. Citra may require minimum pricing based on estimated GPU/provider generation cost, cold-start cost, safety margin, platform settings, or other operational factors. Estimated generation costs and developer earning previews are estimates only and may differ from final earnings.

Unless Citra clearly states otherwise in the product or these Terms, generated outputs may be used commercially by the generating user, subject to applicable law, third-party rights outside Citra, foundation model or provider restrictions, and Citra platform policies. Citra does not provide legal advice, copyright clearance, trademark clearance, logo clearance, or infringement determinations for uses outside Citra's platform rules.

You may not upload, generate, train, publish, request, or distribute content that infringes rights, contains non-consensual intimate imagery, sexualizes minors, promotes hateful conduct, facilitates fraud, impersonates another person in a misleading or harmful way, violates law, sanctions, export control, payment provider rules, or platform rules, contains malware, or bypasses Citra's permission, rights ledger, payment, balance, training, generation, or security systems.

If you believe content on Citra infringes your rights, contact citra.ai.tech@gmail.com with your contact information, identification of the work or rights, the Citra URL or other information that helps locate the content, an explanation of the claim, a statement that your information is accurate, and your electronic or physical signature.

Citra may remove, unpublish, restrict, disable, or investigate reported content. Citra may suspend accounts, withhold payouts, freeze balances, or preserve records where necessary. Citra may restrict or terminate accounts associated with repeated intellectual property complaints or repeated policy violations.

Citra may use or interoperate with third-party software, open-source projects, AI model families, infrastructure providers, payment providers, storage providers, database providers, hosting providers, and other services. These third parties are not sponsors, partners, or endorsers of Citra unless Citra expressly states otherwise.

Training and generation workflows may involve tools or model families such as Kohya_ss, ComfyUI-compatible workflows, Stable Diffusion 1.5, SDXL, or other technologies. Each project, model, or provider may have its own license, acceptable-use rules, commercial-use conditions, attribution requirements, technical restrictions, or service terms. Citra may update this notice as the platform changes.

Citra intends to respect applicable open-source and model-license obligations. Where Citra uses third-party materials, those materials remain subject to their original licenses and rightsholders. Users and developers must not use Citra to bypass third-party licenses, provider restrictions, export restrictions, safety rules, or acceptable-use policies.

If you believe Citra is missing a required attribution, license notice, or third-party rights statement, contact citra.ai.tech@gmail.com so we can review and correct it where appropriate.