Privacy Policy

2.1 Account information

When you create an account we collect:

• Email address — used to identify your account and enable authentication.
• Account role and status — internal flags (e.g., whether the account is active).
• Timestamps — when your account was created and last updated.

We do not collect your name, display name, profile picture, or any other personal identifiers beyond your email address.

Authentication is managed by Supabase Auth, which issues and validates JSON Web Tokens (JWTs) for every session. Supabase processes your email and authentication credentials in accordance with Supabase’s privacy policy.

2.2 Conversation and chat history

When you use the AI chat assistant we collect and store:

• Your messages (the questions you type) and the AI’s responses, labelled by role (user / assistant).
• Chat session metadata — a session title, session ID, and the timestamps of session creation and last message.

This data is stored in two places:

• Short-term (Redis): Your most recent conversation history (up to 30 messages) is kept in Redis with a rolling expiry of approximately 3.3 hours (12,000 seconds). This is used to give the AI context about your current conversation.
• Long-term (Supabase PostgreSQL): Full conversation history is persisted in our Supabase-hosted PostgreSQL database and linked to your account. It is retained until you delete it or request account deletion.

2.3 Learning progress

We track your progress through lessons and content, including:

• Which lessons and content pages you have completed or partially completed.
• Percentage of completion and your last reading position within a piece of content.
• Any notes you write directly within a lesson.

This data is stored in our Supabase-hosted database and used to resume your progress across devices and sessions.

2.4 AI-inferred memory profile

As you interact with Deen, our AI builds and maintains a personal learning profile to personalise your experience. This profile is stored in our database and includes AI-generated notes across five categories:

• Learning notes — insights about how you learn and what topics you are working on.
• Interest notes — subjects and themes you have expressed interest in.
• Knowledge notes — what the AI has inferred about your existing knowledge and gaps.
• Behavior notes — observed patterns in how you engage with content.
• Preference notes — your preferred language, style, and other stated preferences.

Each of these categories is stored as a list of structured notes generated entirely by the AI based on your chat interactions and lesson activity. The profile is stored in our Supabase-hosted database, updated over time, and used to personalise AI responses and lesson introductions. A record of each update event (the trigger, the raw context, and the AI’s reasoning) is also retained as a memory event log.

2.5 Personalized lesson primers

For each lesson you access, the AI generates a short, personalized introduction (a “primer”) based on your memory profile. This generated content is cached in our database and associated with your account and the relevant lesson.

2.6 Note embeddings

To enable semantic search — for example, to match your learning interests to relevant lessons — we compute and store vector embeddings (numerical representations) of notes in your memory profile. These embeddings are produced by a locally-running open-source model and stored in our database. They do not leave our servers.

3.1 Data you provide directly

Account information is collected when you register or update your profile. Notes written within lessons are collected when you save them.

3.2 Data generated automatically through your use of the app

Conversation messages, session metadata, learning progress, and updates to your memory profile are collected automatically as you use the app. You do not need to take a separate action — using the chat or navigating lessons is sufficient to generate this data.

3.3 Data sent for AI processing

Every time you send a message to the AI chat assistant, the following data is transmitted to our backend server and then forwarded to Anthropic (the maker of Claude) for processing:

• Your current message.
• Recent conversation history (up to the last 30 messages).
• Your AI memory profile (the notes described in Section 2.4), where relevant to the request.
• Retrieved passages from our Islamic knowledge base (hadith, Quranic tafsir, Ayatollah Sistani’s published rulings) — reference text, not your personal data.

This data is transmitted only when you actively interact with the AI. It is not collected passively in the background.

4.1 Anthropic (AI model provider)

Anthropic provides the Claude large language models that power Deen’s AI chat assistant, memory system, and all AI-driven features.

Models used: claude-sonnet-4-6 for primary response generation, query classification, fiqh reasoning and evidence evaluation, language translation, memory profile updates, and memory consolidation; claude-haiku-4-5-20251001 for lightweight tasks such as query enhancement and primer generation where speed is prioritised.

Data is transmitted over TLS to Anthropic’s API. Anthropic’s API usage policies govern how API-submitted data is handled. We require Anthropic, as a service provider processing data on our behalf, to provide the same or equivalent protection of user data as described in this Privacy Policy.

4.2 Supabase (authentication and database)

Supabase provides two distinct services that are central to Deen:

• Supabase Auth — manages account sign-up, sign-in, and session management. It issues and validates the JWTs that authorize your requests to our API. Your email address and authentication credentials are processed by Supabase Auth.
• Supabase-hosted PostgreSQL — our primary database runs on Supabase’s managed PostgreSQL infrastructure. All persistent user data described in Section 2 (conversation history, learning progress, memory profile, primers, note embeddings) is stored here.

Supabase provides a unified, secure platform for both authentication and database hosting, reducing the number of third parties that handle your data. Refer to Supabase’s privacy policy for details on how Supabase handles data stored on its infrastructure.

4.3 Pinecone (vector search — knowledge base only)

Pinecone hosts our Islamic knowledge base as a vector index (hadith, Quranic tafsir, Ayatollah Sistani’s rulings). When you ask a question, a search query derived from your message is sent to Pinecone to retrieve relevant source passages. An embedding (a numerical vector) of your query is sent — your personal information, account data, and conversation history are not sent to Pinecone.

4.4 Redis (session memory — our infrastructure)

Redis is used to store your short-term conversation history (up to 30 messages, ~3.3-hour TTL) during active sessions. This is part of our own infrastructure. It provides the AI with recent conversation context so you can ask natural follow-up questions without the AI losing track of the thread.

Data access

You can view your conversation history and learning progress directly within the app.

Account and data deletion

You can request full deletion of your account and all associated data through the account settings in the app. Upon deletion, your data is removed from our database as described in Section 7.

AI memory profile

The AI memory profile is built automatically to improve your experience. If you wish to understand what is stored or request its deletion, contact us using the details in Section 13.