Privacy Policy
What Conjure does with your data.
Last updated May 10, 2026. Plain language, then the detail. Questions go to fadi@maivenx.com.
The short version
- Conjure builds rooms of avatars who talk to you and to each other. To do that it processes your microphone audio (always), your webcam video (while you’re inside the room, optional), photos you upload (only the ones you upload), and the text of what you and the avatars say.
- Most of that data is processed on the fly by third-party APIs (Anthropic, Runway, Deepgram, LiveKit) under their own privacy terms.
- Room artifacts (transcript, summary, postmortem, cinematic shot) are stored on Conjure's servers for 7 days by default (Redis cache) and persist longer in Postgres only if you're signed in.
- Your saved Circle and your Reflections list live in your browser's
localStorageby default — they never leave your device unless you sign in and we sync them. - You can delete any room at any time. Account deletion wipes server-side records too.
- Conjure does not sell your data. There are no advertising trackers. There is no analytics SDK reading your transcripts.
What we collect, and why
Microphone audio
Captured while you’re inside a room so the avatars can hear you. Streamed to LiveKit and Deepgram for speech-to-text. Not recorded as audio files on our servers — the transcript text is kept; the raw audio is not.
Webcam video (optional)
Captured while you’re inside a room if you grant access, so the avatars can “see” you. Streamed to Runway through LiveKit for the live session. Not recorded on our servers.
Uploaded photos
Only when you choose to upload a photo for a custom persona. Sent to Runway's gen4_image and Custom Avatar APIs to generate the persona avatar. The Custom Avatar object stays in your Runway-side scope; Conjure does not retain a local copy of the original photo beyond the upload window.
Text inputs
Your scenario, persona descriptions, behavioral notes, and any on-screen prompts. Sent to Anthropic Claude for orchestration and to Runway for avatar prompting.
Web-search persona extracts
When you use the “extract from name” feature, the name and affiliation you typed are sent to Anthropic Claude, which uses its own web search tool to look that person up. The search query travels to Anthropic's upstream search provider.
Generated transcripts and videos
What was said inside the room (text), the written summary, the avatar-narrated debrief, the postmortem dialogue + per-turn videos, and any cinematic shot. Stored on Conjure's servers (Redis 7-day TTL by default, Postgres if you're signed in). Video files mirror Runway-hosted URLs and are re-served from Conjure's storage so they don't expire when Runway's temporary URL expires.
Account data (only if you sign in)
Email address and the auth identifiers your sign-in provider (Supabase) returns. Used solely to associate your rooms with you across devices. No marketing emails.
Browser storage (localStorage)
Your Circle (saved personas) and your Reflections list when you're anonymous. Stays in your browser. Conjure cannot read it from elsewhere.
Operational logs
Standard server logs (request paths, status codes, error traces) kept for short windows for debugging. We do not log transcript bodies or persona content into operational logs.
Third parties that process your data
Conjure is built on top of several third-party services. Each has its own privacy policy that governs its handling of the data we send.
- RunwayAvatar generation, live multi-avatar Realtime Sessions, offline avatar video renders, Seedance 2 cinematic shots
- AnthropicClaude LLM for persona synthesis, scenario classification, postmortem dialogue, summary script, real-time turn coordination, web-search persona extract
- DeepgramSpeech-to-text (Nova-3) and text-to-speech (Aura-2) for the live room
- LiveKitWebRTC transport for the live room — audio/video routing between you and the avatars
- SupabaseAuthentication and durable Postgres storage for signed-in users only
- RailwayServer hosting (the Conjure web app and the agent worker)
- Redis (Railway-hosted)Short-lived cache for live room state (7-day TTL)
Retention, deletion, and your rights
Retention
Server-side room data lives in Redis with a 7-day TTL by default. Signed-in users get a Postgres copy that persists until they delete it. Anonymous users have no server-side durable copy — once Redis TTLs out, only what your browser saved in localStorage remains.
Deletion
You can delete any room from the Reflections page (the trash icon on each card). Signed-in deletes remove the Postgres record too. You can wipe your local Circle and history by clearing the site's storage in your browser settings.
Account deletion
Email fadi@maivenx.com with the email address you signed up with. We will delete your account, your server-side rooms, and any associated data within 14 days.
Data export
On request to fadi@maivenx.com we will provide a JSON export of your server-side room records.
Children
Conjure is not intended for users under 16 and we do not knowingly collect data from children.
Real-photo personas — extra care
When you upload a photo of a real person to create a custom persona, you are responsible for having the right to do so. Conjure does not republish that photo or its derived avatar outside your own session. The avatar is created as a Custom Avatar object in Runway's scope and is governed by their content policy.
If someone whose likeness has been used contacts us at fadi@maivenx.com, we will remove the avatar and any associated room artifacts within 7 days.
Changes to this policy
Conjure is still evolving. The policy will evolve with it. Material changes will be flagged in the app and dated at the top of this page.
Questions or requests?
Email fadi@maivenx.com.
Conjure · A solo project by Fadi Abbas · Built on Runway, Anthropic, Deepgram, LiveKit