Privacy policy | DeepManim

1. The service and contact

DeepManim is operated by David KAMGANG NINTCHEU, who is responsible for the personal information described in this policy. This policy covers DeepManim at deepmanim.com and its chat, video-generation and API features. For privacy questions or requests concerning the operation of DeepManim, email support@deepmanim.com. Our terms of service explain use of the service.

2. Information handled by DeepManim

Account information: email address, account identifiers, and, when supplied by your sign-in provider, display name and profile picture. Authentication and session information keeps your account signed in.
Your requests and content: prompts, conversation messages, feedback, uploaded files and their names/types, selected generation settings, and generated scripts, scene code, narration, images and videos.
Account activity: saved chats and projects, sharing settings, generation jobs and results, credits and credit transactions, subscription status and payment-related identifiers.
Technical and usage information: page visits, feature interactions, session/device identifiers, browser and request information, generation timings, errors and service diagnostics. Hosting and infrastructure providers also receive information such as IP addresses needed to deliver and protect the service.
Support information: information you send when contacting support, together with the relevant account, request, billing or diagnostic records used to investigate your issue.

3. Google sign-in information

If you choose Google sign-in, Google supplies basic account information such as your email, name, profile picture and Google account identifier through Supabase Authentication. DeepManim uses it to authenticate you, identify your account, display your profile, associate your saved work and credits with you, and handle account support and service operations. Basic sign-in does not authorize DeepManim to read your Gmail, Google Drive files or calendar.

Account identifiers can be associated with usage analytics. Registration and subscription notifications used by service operators can include your email and account identifiers. You can review or remove the Google connection in your Google Account settings; removing it does not itself delete data already stored by DeepManim. Google also processes information under Google’s privacy policy.

4. How information is used

Information is used to provide authentication and saved history; generate, render, narrate, deliver and revise the explanations you request; operate sharing and API features; account for credits and payments; provide support; understand feature use; and diagnose failures, prevent abuse and maintain the service. Operational staff may access relevant requests, content and records to fulfill requests or investigate problems.

A generation request can send your prompt, attachment content, prior conversation context and generated material to AI and rendering providers. Upload only information you are authorized to share for this processing. Avoid passwords, payment-card details and other sensitive or confidential information in prompts and uploads.

5. Service providers and other recipients

DeepManim shares information with service providers that help us operate the service:

Account and infrastructure services: handle sign-in, account records, file storage, and delivery of the website and media.
AI and media-generation services: process prompts, attachments, conversation context and generated content to create the explanations, images, narration and videos you request.
Payment services: process checkout and billing information, and exchange contact, purchase, payment-status and billing identifiers with us to manage credits and subscriptions.
Analytics, support and operations services: where configured, receive account identifiers, usage information and diagnostics; generation or support records can also include prompts, outputs and error details.

Providers may process information in countries other than yours. Their processing also depends on their applicable terms and privacy practices. Information may also be disclosed when required by applicable law or when necessary to investigate abuse, protect the service or respond to a legal request.

Making a chat public allows people with its link to view the shared questions, answers and videos, and supported sharing features can allow copying or forking its content. Turning sharing off stops access through that public-chat feature, but cannot recall copies or downloads that others have already made.

Uploaded attachments and generated media can have publicly readable direct URLs. Anyone who obtains such a URL may be able to access the file even when the conversation itself is not shared. A private chat setting is not a promise that its file URLs require account authentication. Do not use the service for material requiring confidential storage.

7. Cookies and browser storage

DeepManim uses cookies and browser storage for sign-in persistence, session recovery, cached chat information, language, appearance and other preferences. A server-set cookie backs up the sign-in refresh token to help restore sessions when browser storage is lost. These are not all limited to a single browser visit. Configured analytics can also use persistent device and session identifiers.

You can sign out and use your browser controls to clear cookies/storage or restrict analytics connections. Clearing or blocking storage can remove local preferences and interrupt sign-in or other features. Clearing your browser does not delete server records.

8. Storage, deletion and requests

Account information and saved conversations are stored between visits so that the service can maintain your account and history. There is not one automatic deletion date for all record types. Billing, support and diagnostic records are separate from your chat history.

The chat’s delete action removes a conversation from the application’s saved history. It does not by itself guarantee deletion of uploaded or generated files, provider traces, operational records, backups or copies held by other people. For account deletion or a broader data-deletion request, email support@deepmanim.com from the account email and describe the request. Retention and deletion can depend on the type of record, provider systems and applicable billing, security or legal requirements.

Depending on the law that applies to you, you may have rights to access, correct, delete or receive a copy of your personal information, or to object to or restrict processing. Contact the same address to make a request or raise a concern. We may need information to verify that a request concerns your account. Where applicable, you may also contact your local data-protection authority.

9. Policy updates

Updates to this policy will be posted on this page with a revised date. Questions about what information is involved in a particular feature or request can be sent to support@deepmanim.com.