Privacy Policy

1. Who this policy covers

This policy applies to the website and features made available at eidolune.com. The full legal name and postal address of the operating entity have not been published in the current site configuration. Those details should be verified and added if required by applicable law.

2. Information we collect

You can browse public pages without creating an account. When you visit, our servers receive technical request information such as an IP address, browser and device details, requested pages, and the time of a request. The contact form uses a temporary, in-memory IP-based rate limit. The hosting environment may also keep operational logs according to its own configuration; no specific log retention period is published here.

If you create an account, the service processes account and profile information such as your name, email address, username, profile details, authentication records, and session information. The exact fields depend on the features you use and the sign-in method.

If you contact us, we store the name, email address, message, submission time, and contact-triage status in the application database. The form also uses Cloudflare Turnstile to help prevent automated abuse.

If you submit prompts or use generation and AI tools, the relevant feature may process the prompt text, uploaded or referenced images, source or creator details, settings, generated outputs, and account identity needed to provide that feature. Prompt views, copies, likes, and other interactions may be recorded for the library and its internal counters.

Google Analytics is optional: the site loads it only when an administrator enables tracking and configures a valid measurement ID. It may then collect browser and usage information as described by Google. No advertising or marketing pixel is configured in the website code reviewed for this draft.

3. How we use information

The Privacy Policy acknowledgment on the contact form records that you have read this policy. It is not consent to marketing, a newsletter, or unrelated processing, and contact-form users are not automatically subscribed to marketing communications.

• To provide, secure, and maintain the website, accounts, and requested features.
• To respond to contact messages, handle content reports, and administer submitted content.
• To prevent spam, fraud, abuse, and automated attacks, including through rate limiting and Turnstile.
• To operate prompt counters and, if enabled, understand aggregate site usage through Google Analytics.
• To classify contact messages for administrative triage when the optional contact-triage feature is enabled.
• To meet legal obligations, enforce our policies, and protect users and the service.

4. Cookies and similar technologies

Authentication features use cookies or similar browser storage to maintain account sessions and security. Cloudflare Turnstile may use browser storage or other technical signals for bot detection. If Google Analytics is enabled, its scripts may use cookies and similar technologies for analytics.

The current site does not provide an in-product cookie preference panel. Browser controls can be used to block or remove cookies, but doing so may prevent sign-in or affect security checks. Read the Cookie Policy for details. The contact-form acknowledgment does not control analytics cookies.

5. Legal bases and your privacy rights

Where applicable, processing may be necessary to provide a feature you request, to operate and protect the service, to comply with law, or to pursue legitimate interests such as preventing abuse and responding to messages. If a particular activity requires consent, we will seek it separately; the contact-form acknowledgment is not a blanket consent.

Depending on your location and the applicable data protection laws, including the GDPR where it applies, you may have rights to request access to, correction of, deletion of, or a copy of personal information, to restrict or object to certain processing, to withdraw consent where consent is the basis, or to complain to a relevant authority. These rights may have conditions and exceptions under law.

To make a request, use the contact form and write "Privacy request" in your message. Include enough information for us to locate the relevant record, but do not send passwords or unnecessary sensitive information. We may ask for reasonable verification before acting.

6. Sharing and service providers

We do not sell personal information. Information may be made available to service providers only as needed for a feature or operation, under the settings selected for the deployment. Integrations present in the code include Cloudflare Turnstile for abuse prevention; Google Analytics when an administrator enables it; email delivery and authentication integrations for account features; and configurable image-storage and AI-provider integrations.

When contact triage is enabled, only the contact message text, truncated to 1,500 characters, is sent to the administrator-configured AI router for classification; the sender name and email address are not included. That router may be self-hosted or provided by another service; its actual operator and location depend on the administrator's configuration. Do not include highly sensitive information in contact messages.

When you use an AI generation or AI tool feature, the relevant prompt, reference material, or image may be sent to the provider configured for that feature. Provider terms and privacy practices apply to their processing. We do not represent that every provider is active or that a particular provider is configured for every deployment.

7. International data transfers

The location of the production database, hosting, storage, and optional providers is determined by deployment configuration and may be outside your country. The current public configuration does not identify every processing location or a universal transfer mechanism. The operator must verify actual locations and put any legally required transfer safeguards in place before publication or use in a particular jurisdiction.

8. Storage, retention, and security

Account details, prompt submissions, and contact messages are stored in the application's database. Images use the storage provider configured for the deployment, which may be local storage or a configured remote provider. Contact messages can be reviewed and deleted by administrators.

No fixed retention schedule for contact messages, technical logs, or backups is currently documented in the site configuration. Information is kept for operational and legal needs and should be deleted or anonymized when no longer needed under the applicable retention rules. The responsible operator should set and publish concrete retention periods.

The service uses security controls in its application and infrastructure, but no method of storage or transmission is completely secure. This policy does not claim a particular security certification or guarantee that unauthorized access can never occur.

9. Children's privacy

The service is not designed to collect children's personal information, and it has no child-specific account flow. Do not submit a child's personal information or images unless you have the authority and a lawful basis to do so. If you believe a child has provided information to us, contact us through the contact form so we can review the request.

10. Changes to this policy

We may update this policy when the service, integrations, or applicable requirements change. The date at the top of the page identifies the current draft. Material changes should be reflected here before they take effect.

11. Privacy requests and contact

For questions, access or deletion requests, or other privacy matters, contact us at /contact and mark the message "Privacy request." The site does not currently publish a dedicated privacy email, the operating entity's legal name, or a postal address. Verify and add those details if required by the laws that apply to the service.

This is an implementation draft and must be reviewed by a qualified legal professional before publication or reliance.