Data practices
Privacy
Last updated July 13, 2026.
Information you provide
We process product prompts, design constraints, uploaded or generated project information, account details, and messages you choose to send. Avoid placing confidential information, trade secrets, personal data about others, credentials, or regulated data in a prompt unless you have determined the service is appropriate for that use.
If you subscribe to a project notification, we process the email address and project identifier needed to provide that update. Account and guest-session identifiers help connect requests with the correct project experience.
How the service uses information
Information is used to provide generation, store and retrieve projects, operate authentication, send requested notifications, prevent abuse, troubleshoot, understand product performance, and improve the service. Product prompts and project data may be sent to model, generation, storage, or infrastructure providers needed to perform the requested workflow.
Analytics and local storage
The site uses PostHog for intentionally instrumented product and content events when configured. Events can include page or resource viewed, CTA clicked, prompt or generation started, project status, and technical context such as referrer and campaign parameters. Browser storage may hold device, guest, feed-cache, service-worker, and content-attribution state. You can use browser controls to clear local data.
Service providers and retention
Current infrastructure may include Clerk for authentication, Supabase for application data and storage, PostHog for analytics, Vercel for hosting, Resend for requested email, and AI or media-generation providers for product outputs. Each provider processes information under its own terms and configuration. Retention depends on account, project, operational, security, and legal needs; beta data may not have a single universal retention period.
Your choices
You may choose not to create an account or submit a prompt. You may request access, correction, or deletion through the contact page. Some records may need to be retained for security, dispute, operational, or legal reasons, and some generated or public project copies may require separate handling. We will explain material limits when responding.
Children and changes
ConjureAnything is not directed to children and should not be used to submit a child's personal information. We may revise this page as product data flows change. Material revisions will receive a new updated date; changing the date alone is not treated as an update.