Privacy Policy

1. What we collect

• Account data: your email address, display name, password authentication records, session data, profile settings, profile avatar if you upload one, and account status such as admin, ban, subscription, or X-Mode eligibility.
• Payment records: invoice IDs, order/payment status, product or plan selected, credit pack or subscription tier, renewal status, timestamps, and webhook metadata needed to credit your account exactly once.
• Usage/accounting data: credit balances, credit ledger events, anonymous daily generation counts, and basic generation metadata needed to enforce limits and prevent duplicate credits or refunds.
• Public content: forum posts, comments, gallery posts, likes/dislikes, gallery comments, gallery tags, and the generation settings you choose to publish with a gallery post.
• Safety and admin data: moderation reports, ban records, admin audit context, LoRA catalog metadata, LoRA verification results, and source URLs submitted by admins for catalog management.

2. Generation prompts and images

Private generation prompts and generated images are processed only as needed to provide the generation result. A normal generation is returned to your browser and is not automatically posted to the public gallery.

• Your prompt must pass through Silumin's server and our generation infrastructure so the image can be produced. We do not intentionally save private prompts in our database for normal generations.
• Generated images are kept in your browser cache/local browser storage for convenience, such as surviving a reload for a limited time. Clearing browser/site data removes that local copy.
• We avoid logging prompt text. Infrastructure logs may still contain request timing, status codes, error traces, route names, account/session context, or other diagnostic metadata needed to operate the site.
• If a generation fails, we may use provider status/error responses and local credit ledger events to refund reserved credits. We do not need to permanently store the prompt to do that.

3. Opt-in public gallery

The public gallery is fully opt-in. A generation is not public unless you click to share it and then post it.

When you post to the gallery, we store the image, title, prompt, model, dimensions/aspect ratio, generation settings, LoRAs and LoRA weights, tags, NSFW/SFW label, creator ID, votes, comments, and stored counters. This is public content and can be viewed by other users, subject to X-Mode gating for NSFW posts.

If you enable anonymized identity, gallery posts display you as Anonymous. That changes the public display name; it does not erase the internal creator ID needed for deletion, moderation, and abuse handling.

4. Prompt safety checks

Silumin uses safety checks to block prohibited public-figure prompts and child/underage sexual content. Some checks happen in your browser before a request is sent. Server-side checks may also be used to enforce rules for direct API calls, public gallery publishing, and abuse prevention.

Client-side checking is privacy-friendly, but it is not a promise that no safety processing ever happens server-side. If you submit content to our API, we may process it temporarily to enforce the rules described in Our Beliefs.

5. Third parties we rely on

Silumin cannot operate completely alone. We use infrastructure and service providers for hosting, database/storage, authentication/session support, image generation, crypto payment processing, email or webhook delivery, security, and basic diagnostics.

We send these providers only what is needed for their role. For example, generation infrastructure receives generation inputs needed to create an image; the payment processor receives payment/invoice information needed to process crypto payments and notify us when a payment succeeds or fails.

6. Cookies and local browser storage

We use cookies and local browser storage for sessions, age verification, selected models and LoRAs, theme/X-Mode preference, generated image cache, generation presets, and other settings that keep the app usable.

Some of this data stays only on your device. Removing site data in your browser may sign you out and clear local generations or preferences.

7. How we use data

• To create and manage your account.
• To process payments, renewals, top-ups, credits, and refunds.
• To provide image generation and return generated images.
• To operate the opt-in gallery, forum, profiles, and comments.
• To enforce X-Mode, NSFW visibility rules, safety rules, and bans.
• To debug errors, secure the service, prevent abuse, and comply with law.

8. Deletion and control

You can delete your account from the profile page. Account deletion removes or tombstones account-linked content according to the feature involved and deletes associated private assets where possible. Public posts or comments may need tombstones so conversations, moderation records, and abuse prevention remain coherent.

You can delete or unshare your own gallery posts. Admins may remove public content that violates site rules. You can also clear browser storage to remove local-only generations and preferences from your own device.

9. Retention

We keep account, payment, credit, moderation, and public-content records as long as needed to operate the site, resolve disputes, prevent abuse, and comply with legal or accounting obligations. Private generation prompts and generated images from normal generation are not intentionally kept as permanent product records.