Privacy Policy | LiduAI

Local-review draft · Not yet effective. Operator: LIDU AI LABS. Complete the contact and jurisdiction details below and verify operational practices before public launch.

1. Operator

LIDU AI LABS operates LiduAI. This policy covers personal data handled in accounts, generation, billing and support. The full registered address, privacy email, target jurisdictions and any required representative remain unconfirmed. This is a local-review draft until these details and operational practices are verified.

2. Data processed

• Account data: your supplied name and email, authentication information and sessions. Passwords are handled in protected form by the authentication system; never send passwords or verification codes to support.
• Creation data: prompts, parameters, uploaded images or audio, task status, output links, timestamps and account associations. Media may contain personal data about you or others. Current task records retain prompts, parameters and results; they are not promised to disappear on completion.
• Operational data: IP addresses, request logs, browser details, errors and abuse indicators as needed to run and protect services.
• Transactions: when paid features are enabled, orders, subscriptions, amounts, payment status and necessary accounting records. Payment credentials are processed through the relevant payment provider's actual flow.
• Support: tickets, contact details and copyright notices or counter-notices you submit. Provide only what is necessary.

3. Purposes and legal grounds

We process account and creation data to provide requested services; necessary records for legal duties; and, where permitted, proportionate data for legitimate security, troubleshooting and abuse-prevention interests while considering individual impact. Optional purposes requiring consent need separate consent. General terms are not blanket permission for sensitive-data processing, international transfers, marketing or training.

4. Providers, disclosures and transfers

Prompts, media and parameters needed for generation are sent to third-party inference services. Hosting, storage, email and payment providers may process necessary data when those features are enabled. Removing supplier branding from the interface does not remove disclosure obligations. Before launch, actual recipients, processing regions, purposes and privacy terms must be verified and published, including recipient-specific disclosures or separate consent where required. The local database is on the device running this project; external model calls may still send Inputs abroad, so local operation does not mean all data stays on-device.

Necessary disclosures may be made to service providers, legally authorized authorities or parties handling disputes. Any business-transfer disclosure must follow applicable notice and protection requirements. This policy does not authorize selling personal data or cross-site targeted advertising.

5. Training, likenesses and sensitive data

The current platform code does not implement training its own models on user submissions. This is not a guarantee that third parties have zero retention or never train: their actual settings and terms must be checked. A new training purpose requires clear notice and consent where legally required, not a retroactive policy rewrite. Do not upload identity documents, financial credentials, medical records, trade secrets or unnecessary children's data. Obtain appropriate permission for another person's face, voice or sensitive data, including both people in a duet.

6. Cookies and local storage

Sessions, security, language and interface preferences use necessary cookies or local storage. Browser controls can remove them but may sign you out. Optional analytics and advertising are not configured in the current local version. If enabled later, the actual technologies and choices must be disclosed and consent obtained where required. Reading this policy does not accept optional tracking.

7. Retention, security and deletion

There is currently no unified automatic deadline that purges every task, log and third-party copy. Retention should be limited to service, legal accounting, dispute and security needs; specific schedules and deletion procedures must be finalized before public launch. Outputs are not promised permanent storage; download works you need. Access controls and server-side key protection reduce risk but cannot guarantee absolute security.

Verified deletion requests will be handled according to applicable law and technical scope. Required legal or dispute records may be retained, and backups and third-party copies follow their respective procedures. Removing a visible record does not necessarily erase all copies immediately.

8. Rights, children and complaints

Depending on applicable law, you may have rights to information, access, correction, deletion, restriction, objection, portability, withdrawal of consent and complaints to a regulator. These are not unconditional rights in every jurisdiction. Withdrawal does not invalidate earlier lawful processing. Support tickets can receive requests; a separate public channel is still needed for people without account access, as noted below. Do not post identity documents in public comments.

The service is intended for adults, not children. Report improperly submitted children's information for review. Material purpose changes require reasonable notice and renewed consent where applicable.

Contact and launch requirements

Operator: LIDU AI LABS. Existing users can submit general questions or rights requests through support tickets. The full legal entity and registration details, address, applicable jurisdictions, public contact email, privacy email and copyright/DMCA agent details remain to be supplied. Tickets require sign-in and do not replace a public channel for non-users. An effective date will be announced after these items are completed.