Privacy Policy

•

Account details and consent records. If you register with an email address, we store that address, Supabase Auth stores your password in hashed form, and we record the date and version of the Terms of Service and Privacy Policy you accepted along with your confirmation that you are at least 18 years old. If you sign in with Google or with Apple instead, we receive the account identifier and basic profile that provider returns, which can include your name and picture.

•

Profile details. A display name, an optional short description of yourself, and an optional profile picture.

•

Chat conversations and file attachments. The messages you send, any text you paste in (such as letters, drafts, or receipts), and any files you attach (text, PDF, or Word .docx documents up to 10 MB and 200 pages), together with the replies, citations, and follow-up suggestions the assistant produces.

•

Voice conversations (Walkie-talkie and Live call). Microphone audio while you record a Walkie-talkie turn or run a Live call, a written transcript of what you and the assistant each said, and (where applicable) an AI-written summary of the call.

•

Voice profiles and optional context. A name, a gender, a preferred level of formality, a language, and optionally a religion, an age range, a marital status and a location, each left empty unless you fill it in. When starting a general-assistant chat, you may optionally turn on a switch to share only your default voice profile's name, gender, formality and whichever of those optional fields you have set with that provider for that chat. That switch is off by default, is not remembered between chats, and the sharing line names exactly what goes. The religion field is covered separately below.

•

Voice settings. Microphone sensitivity and the voice or model options you configure.

•

Credits, purchases, and gift invitations. Your credit balance, usage history, gift codes claimed, and—when you send a gift credit invitation to a friend—the recipient email address you bind that single-use gift code to. Payment card details are handled directly by Stripe (on the web) or Apple / Google (via RevenueCat on mobile); we store only the billing customer identifier, transaction status, amount, currency, and credits granted.

•

Team membership and permissions. If you create or join a team account, we store your membership, your role (such as owner or member), and any pending team invitations.

•

It is entirely optional. Every part of WesenAI, voice and chat included, works without it.

•

It is stored in our database against your account and protected by database row level security.

•

It is never included in the instructions sent to Google when a voice call begins.

•

It is sent to a third-party general-assistant provider only when you turn on profile sharing for a chat, with the sharing line naming it, so that the assistant can take your fasts, feasts or observances into account for that chat. It is stored with that chat on our servers, deleted with it, and never returned, logged or sent to analytics. Leave the switch off, or clear the religion field, and no provider receives it.

•

You can change it or clear it at any time by editing the voice profile. Deleting the profile, or deleting your account, removes it.

•

To create your account, sign you in, verify multi-factor authentication when enabled, and process credit purchases, subscriptions, and gift redemptions (performance of our contract with you).

•

To answer your messages, process attached documents, and run Walkie-talkie or Live voice calls by sending what you write, upload, or say to the AI providers described below (performance of our contract with you, and your explicit consent when enabling microphone capture or optional context sharing).

•

To show you your own conversation history, voice sessions, transcripts, and credit usage allowances (performance of our contract with you).

•

To personalise how the assistant addresses you when you opt in, and to store your optional voice profile fields (your explicit consent, which you may withdraw at any time).

•

To enforce rate limits, prevent fraud or abuse, and diagnose crashes or interface bugs (our legitimate interests in keeping the service secure and reliable, and your consent where required for web session diagnostics).

•

Supabase hosts our authentication, PostgreSQL database, and file storage in the United States. Your account record, billing metadata, voice sessions, transcripts, voice settings, voice profiles, and uploaded profile picture live there.

•

The WesenAI API service (chat.api.wesen.ai) is operated by TE Web Solutions, Inc. in the United States. It stores your chat sessions, conversation history, voice turn transcripts, uploaded file attachments, and credit ledger, and routes each turn to the AI model provider selected for that conversation.

•

AI model and voice providers receive the prompt, conversation context, audio stream, or document text needed to generate a reply. Companion chats and Gemini Live voice calls use Google (Gemini models). When you choose a model under “General assistants”, your messages for that chat are processed by the model maker shown on that model's info sheet in the app (which may include providers such as Google, OpenAI, Anthropic, or other listed vendors).

•

Stripe and RevenueCat (Apple App Store / Google Play) process payments. On the web, Stripe Embedded Checkout processes credit pack and gift purchases. On iOS and Android, in-app subscriptions are processed by Apple or Google and verified through RevenueCat using your internal Supabase user UUID as the app user ID.

•

Google and Apple act as sign-in providers if you choose to sign in with a Google or an Apple account.

•

Expo delivers the mobile app and its over-the-air updates, which means your device contacts Expo servers to check for updates.

•

ui-avatars.com generates a placeholder profile picture when you have not uploaded one. Your display name is included in that request. If you have not set a display name, nothing identifying you is sent and a generic placeholder is returned instead.

•

PostHog receives error and crash diagnostics and, on the web app, masked interface recordings on servers in the United States. Reports are keyed by your internal Supabase user UUID, and when you are signed in your email address is attached as a PostHog person property so we can look up and troubleshoot support or billing issues for your account. We never include your email address, message text, voice transcripts, filenames, file contents, or voice profile fields (`userContext` or religion) in analytics event properties or error payloads.

•

Personal accounts. By default, you use your personal account (`account_id` matching your user ID). Your personal chats, file attachments, voice sessions, transcripts, voice settings, and voice profiles are isolated so that only your signed-in account can read or modify them.

•

Team workspaces vs. Together sponsor plans. WesenAI supports team accounts with role-based permissions (`owner` and `member`, covering capabilities such as billing, member, and invitation management). If you explicitly switch into a shared team workspace, records created under that team's `account_id` are accessible to members of that team according to their role. By contrast, under a family-or-friends Together subscription plan, the team account is used only for billing and seat invitations: each member's conversations, voice transcripts, and profiles remain strictly inside their own private personal account, and the plan organizer cannot read them.

•

Audio recordings are not retained. We do not keep raw microphone audio files after a Walkie-talkie turn or Live call completes. On mobile, temporary audio buffers on your device are removed once transmitted; what is retained in history is the text transcript.

•

Access a copy of the personal data we hold about you and request it in a portable format.

•

Correct inaccurate personal data or clear optional profile fields.

•

Delete your conversations or your entire account, or ask us to erase your personal data.

•

Withdraw consent at any time where processing is based on consent (such as clearing the religion field, disabling microphone permissions, or keeping optional context sharing off), without affecting the lawfulness of prior processing.

•

Object to or restrict certain processing, and lodge a complaint with your local supervisory authority (such as an EU Data Protection Authority or the Ethiopian Communications Authority).