Legal

Privacy Policy

Effective October 27, 2026 · Version 2026-10-27

Wedelia is provided by OLI & CECE INC, located at 6175 Spring Mountain Rd, Las Vegas, Nevada 89146-8845, United States. OLI & CECE INC is the controller of the personal information described in this Privacy Policy. "Wedelia," "we," "us," and "our" refer to OLI & CECE INC when you use the Wedelia mobile application, website, and related services (the "Service").

1. Information we collect

Information you provide

• Account details, such as email address, display name, date of birth, and an optional profile photo you upload or import from Google.
• Conversation content, images you choose to share, reactions, and preferences.
• Voice input and, during a live call, the microphone audio you transmit.
• Photos you choose to take or pick for translation in Travel Interpreter.
• Money you ask Wedelia to track: income and expense entries described in Section 3.
• Meal logs you ask Wedelia to keep, with estimated calories and nutrients and any meal photos, described in Section 3.
• Reading progress for books you import into the reading room, described in Section 3.
• Website account details you choose to save for browser tasks — the website, your username, and your password — described in Section 3.
• Phone numbers of businesses you ask Wedelia to call, and the text transcript and outcome of those calls, described in Section 3.
• Photos you attach to a person's card, used only for the face matching described in Section 5.
• Scene photos and clothing photos you upload in My scenes, used only to place Wedelia or Alder in your scene or to change her outfit. Each upload and each image made from it is safety-checked before you see it, and both are processed by the AI providers in Section 3. Your scene photo stays viewable to you on that scene. The uploads and the images made from them are kept until you delete the scene or your account.
• Device context you allow Wedelia to read — location, calendar and reminders, and health metrics — described in Section 4.
• Support requests, feedback, and communications with us.
• Your product-email preference, language, consent record, and delivery status. Product email is off unless you turn it on separately in the app.
• Subscription, purchase-history, and entitlement status. Payment card details are handled by the applicable app store, not stored by Wedelia.

Information collected automatically

• Device and app information, including app version, operating system, language, and diagnostic events.
• Security and service logs, including sign-in events, IP address, request timing, and abuse-prevention signals.
• Usage information, such as feature interactions and AI token consumption used to operate and price the Service.
• Public website analytics described in Section 7, but only after you accept optional analytics.

2. How we use information

We use information to:

• create and secure your account;
• provide, personalize, and maintain AI conversations;
• apply age, safety, moderation, fraud, and abuse protections;
• measure reliability, troubleshoot problems, and understand service costs;
• manage subscriptions and customer support;
• send account emails such as verification, password reset, and a welcome email when you sign up, and—only after your separate opt-in—product tips, updates, offers, and promotions that you can unsubscribe from at any time; and
• comply with law and protect the rights and safety of users and others.

We do not sell your personal information. We do not connect your account to an external service unless the integration is separately enabled and you explicitly authorize the requested access.

3. AI processing and service providers

Your prompts and relevant conversation context are processed by AI models so Wedelia can generate a response. We use two AI providers from different companies: Google Cloud, through Google Vertex AI (Google's Gemini models and third-party models that Google hosts on Vertex AI), and OpenAI, through the OpenAI API, processed in the United States. In live voice conversations, where you keep the microphone on in chat, the reply may instead be written and spoken in one step by Alibaba Cloud Model Studio, provided by Alibaba Cloud (Singapore) Private Limited and processed in Singapore. For those replies it receives what an AI provider receives to write a reply, described below, together with the recording of what you just said so it can hear you directly rather than rely on a transcript. For accounts that have connected Google Workspace, this applies only after you have agreed to this version of this Policy, and those replies can include information Wedelia obtained from Gmail, Google Calendar, and Google Drive when it is needed for the reply. Alibaba Cloud also acts as our service provider and does not use this data to train its models. Each of the following may be handled by either or both of these providers, depending on which is available at the time: chat replies and the results of tools Wedelia uses for them; reading photos and images you send, including the safety check on them; creating images you ask for, such as avatars, pictures in chat, and portraits; structured canvas content; memories derived from your conversations; translation; the steps of browser tasks; meeting minutes; and the posts in your Feed, including your daily brief. Both act as our service providers and do not use this data to train their models. When Vertex AI is used, it does not use Google Search or Google Maps grounding, supervised tuning, fine-tuning, or customer data to train or improve a model. OpenAI may keep what it receives for a limited period, as its API terms allow, to monitor for abuse. The embeddings used to search your own memories and other account-scoped context are generated by a model we run ourselves in our own Google Cloud project; this data does not leave Google Cloud and is not sent to an outside AI provider. The specific models we use change over time as providers release new versions; the providers and data locations above are what we commit to, and we update this section whenever a provider or processing location is added.

What the AI providers receive. To write a reply, the provider receives your message, the conversation context and saved memories Wedelia includes to write the reply, the profile and device context sent with that request, and the results of any tools Wedelia uses for that reply. For the other features above, it receives what that feature needs, such as a photo you sent, the description of an image you asked for, or the browser task's goal and screenshots. If one provider cannot complete a request, Wedelia may send the same request to the other so the feature keeps working. Accounts that have connected Google Workspace may also have chat replies and the other features above handled by OpenAI once you have agreed to this version of this Policy. This can include information Wedelia obtained from Gmail, Google Calendar, and Google Drive when it is needed for the feature you asked for. Section 6 explains how Google user data is handled and protected.

Before Wedelia sends what you share to these AI services for the first time, the app shows you what is sent and who receives it, and asks for your permission. If you do not agree, nothing is sent and you can sign out. We share personal data only with service providers that are bound by contract to protect it with the same or equal level of protection as this policy, and only for the purposes described here.

When you ask Wedelia to search the web, carry out a browser task, or use a custom connector, it may use relevant conversation, saved memories, profile information, and device context to prepare the request. This includes information from connected services, as described in Section 6. The sections below explain what is shared and with whom.

The interactive canvas feature, including small running mini applications such as a game, timer, or calculator and ordinary canvas pages such as a checklist, a data page, or a travel itinerary, is handled by the AI providers described above.

Speech synthesis. To create a voice reply, Wedelia's cloud runtime sends the text to be spoken to a speech service. We use Alibaba Cloud Model Studio, provided by Alibaba Cloud (Singapore) Private Limited and processed in Singapore. If it is unavailable, we use a cloned-voice system running on hardware owned by the operator. If you choose one of Wedelia's additional designed voices, we instead use Google's Gemini API, provided by Google LLC, and fall back to the services above if it is unavailable. The request contains a reply written by Wedelia, which may repeat or paraphrase something you just said, together with a voice ID, voice settings, and sometimes cues for tone or for sounds such as a laugh. It does not include your user ID, conversation history, saved memories, profile information, device context, or files. If your account has connected Google Workspace and you have agreed to this version of this Policy, the reply being spoken can contain information Wedelia obtained from Gmail, Google Calendar, or Google Drive; until you agree, Wedelia does not send replies for a Google-connected account to Alibaba Cloud. The exception is a live voice conversation, described in section 3, where Alibaba Cloud Model Studio writes the reply as well as speaking it and receives what section 3 lists, including the recording of what you just said, without your user ID. Each provider handles the request under its own terms. The returned audio is stored in Wedelia-controlled storage that only you can access.

If you connect your own Obsidian vault, Wedelia can search it while she answers you. Your notes stay on your own device: we do not upload them and we do not store them in our cloud. When a search matches, the matching excerpts travel with that one request and are processed by the AI providers described above, the same as the rest of your message.

You can also let another AI app, such as Claude or ChatGPT, search your Obsidian notes through the Wedelia Notes plugin. This starts only after you sign in to Wedelia and allow that specific app. That app then receives the matching excerpts and any note it opens, and handles them under its own privacy policy; on this path your notes are not sent to our AI providers. We record the time and the app of each search or opened note, never the query or the note text, to apply daily limits. You can remove an app's access at any time on the Obsidian page of the Wedelia app.

Safety review and crash reporting. Wedelia uses OpenAI's API modelomni-moderation-latest only to screen the current inbound user message, including user-supplied quoted text, and the final assistant reply for disallowed content. This moderation model does not write Wedelia's replies or perform Google Workspace features. OpenAI's endpoint-specific data-control table states that /v1/moderations data is not used for training and has no abuse-monitoring or application-state retention. This applies to safety screening only; the other OpenAI requests described in this section may be kept for a limited period for abuse monitoring. If the app crashes, technical crash data — stack trace, device model, operating system version, and app version — is sent to Sentry (Functional Software, Inc., a US provider) so we can find and fix the problem. Crash reports never include your conversations, and we do not attach your identity to them. When you ask about the weather or places near you, your coordinates are sent to the weather and map providers serving your region — QWeather and Amap, providers based in China, or Google — to fulfil those requests. Separately from those requests, your precise coordinates and the place labels derived from them are synced to Wedelia's own servers and kept with your account, where they are used for your daily brief and as context in conversation. Section 4 describes that in full.

Self-hosted and offline model components. Wedelia runs Qwen3-TTS 0.6B for speech output, SenseVoice int8 ONNX through sherpa-onnx for realtime voice transcription, and InsightFace buffalo_l for the face matching described in Section 5 inside infrastructure controlled by OLI & CECE INC. These model components run locally within that controlled infrastructure and do not transmit text, audio, images, face measurements, or Google user data back to their model publishers for training or any secondary purpose.

Subscription processing. RevenueCat (RevenueCat, Inc., a US provider) helps Wedelia validate app-store purchases, restore subscriptions, and keep your Plus entitlement current. RevenueCat receives a pseudonymous Wedelia app-user identifier and purchase metadata such as the store, product, transaction identifier, purchase and expiration dates, and subscription status. We do not send RevenueCat your email, conversations, images, health information, or payment card details. On iPhone, if you installed Wedelia from an Apple Search Ads ad, Apple's privacy-preserving AdServices attribution tells RevenueCat which ad campaign and search keyword led to the install, so we can see which ads bring people who keep using Wedelia. This uses no advertising identifier and no cross-app tracking.

Email delivery. Loops, an email delivery provider, delivers Wedelia account emails and, if you separately opt in, product emails. For delivery and suppression, Loops receives your email address, a pseudonymous Wedelia user identifier, language, subscription status, and message-delivery events. For account email, Loops also receives the single-use verification or password-reset action link needed to deliver that message. If custom delivery is unavailable, or an older app version uses the legacy flow, Google Identity Platform/Firebase may deliver the account email instead. To make email-verification and password-reset delivery reliable and enforce rate limits, we may keep the normalized address briefly in a restricted delivery queue while the request is pending or retrying. The queue removes the address after delivery completes or permanently fails. We send account and service notices by email, including a welcome email when you sign up. After you verify your email, your account may receive a complimentary membership; the welcome email mentions that membership only if you have opted in to product email. Account verification, password-reset, and welcome messages do not enroll you in product email. Product email, including offers and promotions, is not enabled by registration or by accepting this Policy: you must opt in separately in the app, either with the unchecked box shown when you first sign in or later in Settings, and you can turn it off in Settings or use the unsubscribe link in any product email. We do not use Google Workspace data, conversation content, images, health information, or payment details for product email.

Voice and call processing. When you record a short voice input, the audio clip is sent securely to Wedelia and processed by Google Cloud Speech-to-Text so it can be converted into text. Wedelia does not save that raw clip to your account unless you turn on “Let Wedelia recognise your voice” in Settings (off by default). With it on, your voice inputs are stored to your account and used only to build a voice profile that tells your voice apart from other people and background sound during calls; turn it off at any time to stop, and the stored clips and profile are deleted. The resulting transcript is handled as conversation content. We keep operational metadata such as the request identifier, audio duration, subscription plan, and whether transcription succeeded for allowance and cost accounting. Live calls are audio-only: your microphone audio is transmitted in real time, encrypted, to Wedelia's own calling service on Google Cloud so Wedelia can respond. When your network does not allow a direct connection, the encrypted call stream may pass through the network relay service of Cloudflare, Inc. (United States). We do not record or store the live audio stream as a media file, though text produced during the call may become part of your conversation history. You can deny microphone permission; calls then cannot start, and the rest of the app keeps working.

Travel Interpreter photos. Wedelia uses your camera only when you choose Take a photo in Travel Interpreter, to translate a menu, sign, or other text in front of you. You can also pick a photo from your library instead. Where your phone can read the text itself, the photo stays on your phone and only the recognized text is sent for translation, which is handled by the AI service providers described above. If no text can be read on the phone, the photo is sent to Wedelia and translated by the AI providers described above. Translation photos are not saved to your account.

Money tracking. When you tell Wedelia in chat that you spent or received money, or show her a receipt, and ask her to track it, she records an entry in your ledger: the date, whether it is income or an expense, a category, the merchant or payer if you give one, the amount and currency, receipt line items, and an optional note. If you have connected Gmail and ask her to, she can read a statement email and record each transaction on it. You can review your entries in the app. Wedelia does not connect to your bank. If you join a savings challenge, the other participants see only the nickname you choose for that challenge and your progress number, never your individual entries; a challenge invite link shows only the challenge title, rules, and dates. You can leave a challenge at any time.

Meal logs. When you describe a meal or send a photo of it and ask Wedelia to log it, she records the meal, the foods and estimated portions, and estimated calories, protein, fat, and carbohydrates, using a food-composition reference table together with the AI model's own estimate. Photos you send for a meal are kept in private storage linked to that meal so you can see them in the app. These estimates are for general tracking and are not medical or dietary advice.

Reading room. Books you import stay on your phone; we do not upload the book file. To keep your place across devices, the app sends each book's title, author, current chapter label, reading position, and progress, along with reading-activity events such as starting or ending a session, creating a highlight, or finishing a chapter or book. These events carry only positions, counts, and times, not the text of your book or highlights. When you ask for Wedelia's spoken after-chapter talk, the end of that chapter, your highlights, and your reading conversation are sent with that one request to write and voice it, processed by the AI and speech providers described above, and are not stored.

Meeting minutes. When you record a meeting under Minutes, that recording is uploaded to Wedelia's storage and transcribed by Google Cloud Speech-to-Text, which also separates the recording into speakers. The AI providers described above then write the minutes from the transcript. The recording itself is deleted as soon as transcription finishes, and in any case within 24 hours. The written minutes and the transcript are kept with your account for 30 days so you can reopen them, and are then deleted automatically. You can delete any set of minutes yourself at any time, which removes the transcript with it. We keep operational metadata such as the request identifier, audio duration, subscription plan, and whether transcription succeeded for allowance and cost accounting. Recording a meeting captures everyone who is speaking, so only record where you are permitted to.

AI output may be inaccurate or incomplete. Safety systems may review, block, or limit content before a response is returned.

4. Device context you choose to share

Wedelia can read context from your phone so she can write your daily brief and answer with the situation you are actually in. Each category below is read only after you grant the matching operating-system permission, and only from a phone where you granted it.

• Location. Your precise coordinates from the phone's location service — not a city-level or reduced-accuracy approximation — together with the place labels your phone derives from them: city, district, and the street or building name at that point.
• Calendar and reminders. Events from the calendars on your phone — title, start and end time, calendar name, and the location written on the event — covering roughly the past year and the next two years, whether calendar access was granted at all, and, on iOS, your incomplete reminders and their due dates. When you ask Wedelia to create, change, or delete a calendar event, that action is performed directly on your phone's calendar.
• Health (Android only). Your step count for the day, recent sleep duration, and resting heart rate, read from Health Connect on Android. The iOS app does not read health data.

While you are using the app, your phone sends this snapshot to Wedelia about every 30 minutes, and again when you bring the app back to the foreground or send a message, so that something you just added to your calendar is not missing from her answer. Only the most recent snapshot is kept: each one replaces the last and is stored with your account. Its non-health fields can support the daily brief and the calendar posts in your Feed (Section 3) and serve as background context in conversation; health fields support only the Food screen's wellbeing overview and the private daily brief, as explained below. It is not on a separate deletion timer — it stays until you delete it by deleting your account. Your contacts are never part of this snapshot: if you turn on Contacts in the app's settings, your phone looks for the people you name in a message and sends only the matching entries (name, phone numbers, email addresses, and birthday) with that message so Wedelia can answer it; the rest of your address book stays on your phone, and the entries sent are not stored.

Because Wedelia's replies are written by an AI model, this snapshot is part of the context sent to the AI providers described in Section 3 for the turn being answered, except your health metrics, which are never sent to an AI model provider. Your coordinates are also sent to Amap, a map provider based in China, as each snapshot arrives, so Wedelia can name the venue you appear to be at.

Health metrics are used only to show you your own numbers in the Food screen's daily wellbeing overview and in your private daily brief. The overview places your calorie intake beside permitted activity, sleep, and resting-heart-rate data so you can follow general wellness patterns; it is not a medical or diagnostic feature. Health metrics are processed only on Wedelia's own servers by fixed app logic, without any AI model involved, and they are not part of what Wedelia is given when she writes a reply to you. They are never used for advertising, never sold, and not shared with any third party.

When you call her from another app (Android)

On Android you can make Wedelia your phone's digital assistant, so that holding the power button brings her up from wherever you are. If you also turn on "Use screen and app data" on that same system settings page, Android hands Wedelia the text of the screen you were looking at when you called her, along with the name of the app it belongs to. If you also turn on "Use screenshot" there, Android additionally hands over one still image of that screen. Password fields are left out of the text, as is anything an app marks as off-limits to assistants; a screenshot, by its nature, shows whatever was on screen.

That text, and the screenshot if there is one, stay on your phone until you send your next message; the screenshot is written to the app's cache and the previous one is deleted each time. They are attached to that one message as context for the AI providers described in Section 3 to answer it, and are not saved to your conversation history or kept with your account. It is never carried into a later message, and if you send nothing within five minutes it is discarded. None of this happens on its own: only when you call Wedelia up yourself, and only while that Android setting is on. Choosing a different assistant, or turning off "Use screen and app data", stops it. If you ask her to help you reply, she shows a suggested reply you can copy; you paste and send it yourself. She never types or sends anything in another app.

Chat notifications you choose to share (Android)

If you turn on Notification access for Wedelia in Android's settings and choose chat apps under Settings > Privacy in Wedelia, she can read recent notifications from those apps — the sender or conversation name and the latest lines of the message — to tell you who has been in touch and help you reply. They are kept only in the app's memory on your phone; recent ones are attached to the message you send as context for the AI providers described in Section 3, and are not stored with your account. A reply is sent only when you tap Send on its card, through that notification's own reply box. Turning those apps off, or revoking Notification access, stops it.

If “Nudge me about new messages” is on (it is on by default once you choose apps), the Wedelia app may post its own notification on your phone when a message from one of those apps has gone unanswered for a few minutes, showing who wrote and the latest line, and asking whether you would like help replying. The lock screen shows only who wrote. This reminder is created on your phone from the notification already there; nothing is sent to us or the AI providers unless you tap it, which opens a chat asking Wedelia to help you reply. There is at most one reminder per conversation per hour, none between 11 pm and 8 am, and you can turn them off in the same settings.

Actions you finish on your phone

When Wedelia prepares directions, a message, a call, a new contact or, on Android, an alarm, it appears as a card under her reply. Nothing happens until you tap it, and you finish it yourself in the app it opens. On iPhone, her actions in the Shortcuts app use your existing Wedelia sign-in on that phone and work like sending her a message. The details are kept with your conversation like any other reply.

Turning it off

Each category has its own switch under Settings > Phone data in the app — location, calendar and reminders, and, on Android, health. Turning one off stops its automatic context from being collected or sent at all, even while the operating-system permission is still granted. Turning off location additionally stops Wedelia from using your location in replies, weather, and nearby search. You can also revoke the permission in your operating system's settings — Location, Calendars, Reminders, or, on Android, Health Connect — and Wedelia stops collecting that category straight away; the app reads nothing it has not been granted. Deleting your account, from Settings > Privacy in the app or through the account deletion instructions, removes the stored snapshot along with the rest of your data. Calendar actions that you explicitly request are handled on your phone and require the calendar permission; Wedelia does not keep a separate cloud copy of the event created by that action beyond the next context snapshot. A Feed post written from an event is stored as described in Section 3 until you delete it or turn off the calendar source. On Android, turning off Health also asks Health Connect to revoke all Health permissions granted to Wedelia; the app provides a direct link to Health Connect if you want to inspect or change them yourself.

5. Face matching on people you save

Wedelia can help you identify people in photos you send, but only people you have chosen to save a photo for. Nothing happens here until you save a photo yourself.

What we store

• The photo you attach to a person's card, stored the same way as other images you share.
• Nothing else. We do not create or keep face templates, faceprints, or embeddings.

How matching works

When you ask who is in a photo, we compute face measurements from that photo and from the photos you saved, compare them in memory, and discard the measurements immediately. They are never written to a face database, because we do not operate one. Matching happens only within your own account: your photos are never compared against another user's, and never against any outside database.

This is biometric processing

Not storing face measurements reduces risk, but it does not change what this is. Analysing a face to identify a person is biometric processing of sensitive personal information under laws including China's Personal Information Protection Law and the EU and UK GDPR. We rely on your consent, which you give by choosing to save a photo, and you can withdraw it at any time as described below.

Photos of other people

The people you save are usually not you. Before saving someone else's photo, you are responsible for having that person's permission and for telling them it will be used to recognise them in your photos. Please do not save photos of people who have not agreed, and do not save photos of children.

Turning it off

Delete the photo from the person's card. Recognition for that person stops immediately, because that photo is the only thing that made it possible. Deletion works even when face matching is otherwise unavailable. Deleting your account removes these photos along with the rest of your data.

Voice recognition

"Let Wedelia recognise your voice" is off unless you turn it on. The app asks once, when you first switch on always-listen mode ("一直听"), whether to enable it, with Yes and No choices. If you choose No, the app remembers that choice and collects nothing for voice recognition. If you turn it on, Wedelia keeps the recordings of your push-to-talk voice messages and derives a voiceprint from them.

The voiceprint is a numeric voice embedding: a vector averaged over samples of your own voice. It is not a recording and cannot be played back. We store it in your own account. Matching happens only within your own account: your voiceprint is compared only against your own voice, never against another user's, and never against any outside database.

We use the voiceprint only to check whether the person speaking is the account holder, so that a television or someone else talking in the room is not recorded as your own words. The check is one of several filters and can be wrong in either direction. We do not use the voiceprint to identify anyone else or for advertising, and we do not share it with third parties.

Analysing a voice to recognise a person is biometric processing of sensitive personal information under laws including China's Personal Information Protection Law and the EU and UK GDPR. We rely on your consent, which you give by choosing to turn the setting on, and you can withdraw it at any time by turning the setting off.

When always-listen mode is running, this check can happen on your device. The app downloads a voice-recognition model and compares the speech with your voiceprint locally. On that path, the audio does not leave your phone for this check.

Turning the setting off deletes both the voiceprint and the stored voice-sample recordings. They are on the same deletion path, and the derived voiceprint is not kept after the recordings are gone. Account deletion removes both by cascade.

6. Google, Apple, Telegram and other connected accounts

Signing in

If you choose Sign in with Google, we receive identity information needed to authenticate you: your Google account identifier, email address, and, when Google returns it, your display name. The display name prefills the editable name field during onboarding; you can change it before continuing. Wedelia does not receive your Google password, and signing in does not give Wedelia access to Gmail, Google Calendar, or Google Drive.

If you choose Sign in with Apple, we receive an Apple account identifier and an email address, plus your name if you choose to share it on the first sign-in. Apple lets you hide your real address; if you do, we receive a private relay address ending in privaterelay.appleid.com and never see the address behind it. Wedelia does not receive your Apple password. Signing in with Apple gives us no access to iCloud, Apple Health, or anything else in your Apple account.

Optional Google Workspace connection

Separately from Sign in with Google, you can choose Connect Google after confirming that you are 18 or older during onboarding, or later under Profile > Connections & integrations. Immediately before Google's consent screen, the app explains the data requested and requires you to tap Continue. You can connect or disconnect Gmail, Google Calendar, and Google Drive separately. Each connection asks Google only for access to that product; the profile access described below is included with the first product you connect. Connecting during onboarding asks for all three at once. Disconnecting one product stops Wedelia from using it while your other connected products keep working. To withdraw the Google grant completely, remove Wedelia from your Google Account's third-party apps. Depending on the products you connect, Wedelia can:

• read your Google display name and profile photo and offer them as candidate account details during onboarding. Your name remains editable and a Google name does not overwrite a name you entered;
• read event titles, times, locations and descriptions from your primary Google Calendar, and create, update or delete events when you ask;
• periodically check and search Gmail, read message headers and bodies, and save mail you request into your Gmail Drafts folder. Wedelia sends a draft only after you review its recipients, subject, and body on the app's confirmation card and tap Send. Each message requires its own confirmation. Wedelia never sends automatically or without confirmation. The message sent is the current version of that draft in Gmail, including any changes you make there before sending. If you ask Wedelia to draft replies to new mail, she reads new messages that may need a reply and prepares drafts for your review, as described in Section 3. If you turn on the mail source in your Feed, Wedelia also keeps a short summary of messages you would want to know about or act on, as described in Section 3; and
• search Google Drive metadata by file name or a content keyword and return file names, types, modified times and links. The Drive access is metadata-only: Wedelia cannot open, download or read file contents.

The candidate Google display name and original profile-photo URL are kept in encrypted, account-isolated connector storage only while the Google connection remains active. If you have no custom account avatar, the Wedelia app downloads the candidate photo, resizes and re-encodes it, and uploads a separate copy to Wedelia's self-avatar storage. The app does not overwrite an existing avatar or use the original Google URL to display the copied avatar. A Google display name becomes your Wedelia display name only when you choose to use and save it. A saved display name can be included in the account context sent to the AI providers described in Section 3.

We use this Google Workspace data to provide the visible features you request or enable, including the user-initiated external requests described in Section 3. Relevant data is encrypted in transit to Wedelia's servers and is processed by the AI providers described in Section 3 to produce the answer, important-mail alert, or Feed post you requested or enabled. When you use a feature that needs Gmail, Google Calendar, or Google Drive data, such as a chat reply or a canvas, that data and stored chat history that can contain Google-derived information may be handled by Google Vertex AI or, once you have agreed to this version of this Policy, by OpenAI, depending on which is available. Background features you have enabled, such as mail monitoring and the memory derivation described below, may likewise be handled by Google Vertex AI or, once you have agreed to this version of this Policy, by OpenAI, depending on which is available. Once you have agreed to this version of this Policy, the replies Wedelia speaks aloud and live voice conversations may also be handled by Alibaba Cloud Model Studio, as described in Section 3. The same safeguards apply: this data is used only to provide the features you enabled and is not used to train models, and, as described below, OpenAI may keep it for up to 30 days to monitor for abuse, with human review only to investigate abuse. On these AI processing paths, raw or derived Google Workspace data is not sent to DeepSeek, Zhipu AI, or any AI provider that uses it to create, train, or improve a foundational or generalized AI or machine-learning model. The embeddings used to search memories derived from this data are generated by the model we run ourselves in our own Google Cloud project, described in Section 3, so generating them does not send this data outside Google Cloud. The current inbound user message, including user-supplied quoted text, and the final assistant reply may be sent to OpenAI's omni-moderation-latest API only for the safety screening described in Section 3. Only when Memory learning is enabled for the account, Wedelia's background mail monitoring may use only the sender, subject, and snippet to derive short, durable facts about the account holder and save them to that account's personal memory. Message bodies are never fetched for memory and never leave the mailbox as part of this process. We save the derived fact, not the message: no copy of the message and no quoted text are saved. We save only facts about the account holder, not facts about the sender or the sender's business. Verification codes, credentials, account numbers, card numbers, and invoice or order specifics are explicitly excluded and never saved. This derivation may be handled by Google Vertex AI or, once you have agreed to this version of this Policy, by OpenAI, as described above. This memory-generation process does not send raw or derived Workspace data to Zhipu AI, DeepSeek, or any provider that would use it to train a generalized model. Each saved fact is labeled with its source on the in-app memory page, where you can read it and delete it individually. With Memory learning enabled, Wedelia may derive the same kind of short, durable facts about the account holder from calendar events the phone uploads as part of device context; this snapshot may include events from accounts you sync on the device. Only an event's title and time are used for memory. Event descriptions, notes, and attendee addresses are never used for memory. The calendar derivation is handled by the same providers under the same conditions and uses the same Memory learning setting, source label, and individual deletion controls on the memory page. Turning Memory learning off stops both mail- and calendar-derived memory capture. If Memory learning is enabled, a Google-derived fact that appears in a user-visible chat reply may be processed by Google Vertex AI or, once you have agreed to this version of this Policy, by OpenAI, and written into personal memory in the same way. If mail alerts and notification previews are enabled, the resulting short alert can also pass through Expo and the applicable Apple or Google push-notification service for delivery to your device.

When you ask Wedelia to search the web, read a page, carry out a browser task, or use a custom connector, relevant information from Gmail, Calendar, and Drive may be shared with the providers or websites involved, as described in Section 3. This includes saved memories and replies based on that information. Sharing takes place for requests you initiate; browser submissions and connector requests that write data still require your confirmation on a card.

Google user data and OpenAI. We transfer Google user data to OpenAI only to provide the user-facing features described in this Policy that you use or enable, and only after you have agreed to this version of this Policy. OpenAI processes it as our service provider under its API terms and does not use it to train its models. OpenAI may keep it for a limited period, up to 30 days, to monitor for abuse, and OpenAI personnel may review content flagged by that monitoring only to investigate abuse, which is a security purpose. Neither we nor OpenAI use raw or derived Google Workspace data to create, train, or improve a generalized AI or machine-learning model.

Google user data and Alibaba Cloud. We transfer Google user data to Alibaba Cloud (Singapore) Private Limited, through Alibaba Cloud Model Studio processed in Singapore, only to provide the voice features described in this Policy that you use — spoken replies and live voice conversations — and only after you have agreed to this version of this Policy. Alibaba Cloud processes it as our service provider under its service terms and does not use it to train its models. Neither we nor Alibaba Cloud use raw or derived Google Workspace data to create, train, or improve a generalized AI or machine-learning model.

We store the OAuth refresh credential in an encrypted, account-isolated vault. We fetch Calendar, Gmail and Drive data only when needed for these features and do not build a separate copy of your mailbox, calendars or Drive. An answer, alert or Feed post may include information from that data. Answers and alerts are retained as part of your Wedelia chat history, and Feed posts and their mail summaries as described in Section 3, under Section 9. We do not allow employees or contractors to read raw Google user data or information derived from it, such as Feed mail summaries, except with your specific consent, when necessary for security, or when required by law.

You can disconnect Google at any time under Connections & integrations. Disconnecting immediately disables the stored credential and stops new access, and deletes the connector's candidate Google name and original profile-photo URL. A display name you chose to save and a profile photo already copied into Wedelia remain as Wedelia account data after disconnection; you can edit the name or replace the avatar, and deleting your Wedelia account removes both. Disconnecting Google, including Gmail, stops all further mail-derived memory capture. It also deletes Feed mail summaries and the Feed posts made from Gmail. Facts already derived remain in personal memory because they are facts about you, not copies of mail. You can delete them individually at any time on the memory page or request deletion of your account data as described in Section 9. You can also revoke Wedelia in your Google Account settings. Account deletion also removes the encrypted credential and Google-derived chat history with the rest of your account data. See the account deletion instructions.

If you turn on "Require unlock to open" in the app, your face or fingerprint is checked entirely by your phone. Wedelia only learns whether the check passed — no biometric data of any kind reaches the app, our servers, or anyone else.

Optional Telegram connection

Under Profile > Connections & integrations you can connect Telegram to talk with Wedelia from the Telegram app. Connecting opens Telegram with a one-time link that expires after ten minutes. When you tap Start, Wedelia stores a keyed one-way hash of your Telegram user identifier, your Telegram chat identifier, and the first name Telegram shows for you, so that messages you send to the Wedelia bot can be matched to your account and replies can be delivered to you. We do not receive your Telegram phone number, your contacts, or any message you send to anyone other than the Wedelia bot.

Messages you send to the Wedelia bot are treated exactly like messages sent in the app: they become part of your conversation history, are processed by the same AI service providers described in Section 3, and count toward the same daily allowance. Telegram also processes these messages under Telegram's own privacy policy. Only text is exchanged over Telegram; voice, images and every other feature remain in the app. The Telegram connection is available only after you confirm that you are 18 or older.

You can disconnect at any time from the same screen or by sending /disconnect to the bot. Disconnecting stops delivery immediately and revokes the stored Telegram identifiers. Conversation history stays in your account and is covered by Section 9. Deleting your account deletes the Telegram link together with everything else.

Optional LINE and Discord connections

Under Profile > Connections & integrations you can also connect LINE or Discord to talk with Wedelia from those apps. For LINE, Wedelia stores a keyed one-way hash of your LINE user identifier and the LINE user identifier needed to deliver replies to you; it does not store your LINE display name. For Discord, you sign in on Discord's own consent screen, which shares your Discord user identifier and name and adds Wedelia's chat commands to your Discord account; Wedelia stores a keyed one-way hash of that identifier, the identifier needed to deliver replies, and the name Discord shows for you. We do not receive your LINE or Discord password, contacts, friends, servers, or any message you send to anyone other than Wedelia.

As with Telegram, only text is exchanged. Messages you send to Wedelia become part of your conversation history, are processed by the AI service providers described in Section 3, count toward the same daily allowance, and are also processed by LINE (LY Corporation) or Discord (Discord Inc.) under their own privacy policies. You can disconnect from the same screen in the app, or by sending /disconnect. Disconnecting stops delivery and revokes the stored identifiers. Conversation history stays in your account under Section 9, and deleting your account deletes these links.

Optional WhatsApp connection

You can also connect WhatsApp under Connections & integrations. Connecting opens WhatsApp with a one-time message addressed to Wedelia's WhatsApp business number; the link is made only when you send it. WhatsApp then shares your WhatsApp phone number and the profile name you set in WhatsApp with us. Wedelia stores a keyed one-way hash of that phone number and the profile name. Your phone number is used to deliver each reply and is not kept in our database. We do not receive your contacts, groups, or any message you send to anyone other than Wedelia, and Wedelia does not start conversations with you on WhatsApp.

Only text is exchanged; photos, voice notes and other media you send there are ignored. Messages you send to Wedelia become part of your conversation history, are processed by the AI service providers described in Section 3, count toward the same daily allowance, and are also processed by WhatsApp (Meta) under its own privacy policy. You can disconnect from the same screen in the app, or by sending /disconnect. Disconnecting stops delivery and revokes the stored identifiers. Conversation history stays in your account under Section 9, and deleting your account deletes this link.

Optional text message (SMS) connection

In the United States you can also connect text messages under Connections & integrations. Connecting opens your phone's messaging app with a one-time message addressed to Wedelia's US number; the link is made only when you send it. Text messages are carried by Twilio (Twilio Inc., United States) and your mobile carrier, which receive your phone number and the messages. Wedelia stores a keyed one-way hash of your phone number; the number itself is used to deliver each reply and is not kept in our database. Wedelia only replies to messages you send and does not start conversations by text. Message frequency varies and message and data rates may apply.

Messages you send become part of your conversation history, are processed by the AI service providers described in Section 3, and count toward the same daily allowance. Reply STOP to stop receiving texts, or disconnect in the app; deleting your account deletes this link.

Optional Notion connection

You can connect Notion under Connections & integrations. Notion's own consent screen lets you choose which pages Wedelia may access. Wedelia stores an encrypted Notion access token. When you ask about your notes, Wedelia searches and reads the pages you shared at that moment. When you ask Wedelia to create or edit a page, it first shows a confirmation card with exactly what will be sent to Notion, and nothing is written until you confirm; Wedelia cannot delete pages. Wedelia does not keep a copy of your pages. Matching excerpts travel with that one request and are processed by the AI service providers described in Section 3, the same as the rest of your message. Disconnecting deletes the stored token; you can also remove Wedelia's access in Notion's settings. Deleting your account deletes the connection.

Optional music connections and playlist imports

Where the app offers it, you can connect Apple Music. Wedelia stores an encrypted Apple Music user token and, from time to time, reads a summary of your listening, such as top artists, songs on repeat, recently played tracks, and the songs in playlists you created yourself. You can also share a playlist from any music service by sending Wedelia a screenshot or a share link in chat; Wedelia reads the song titles and artists from it and keeps that list with your account. Wedelia never stores or streams the songs themselves, and never changes your music library. This information is used to pick music for your radio, to suggest music at moments when you have allowed suggestions, and to keep a few facts about your taste in music on your memory page, where you can delete them. Disconnecting Apple Music deletes the token and the listening summary; you can delete an imported playlist at any time; memory facts stay until you delete them. Deleting your account deletes all of it.

7. Optional public website analytics

The public website may use Google Analytics 4, but only after you choose "Accept analytics." It helps us understand referral and campaign sources, pages viewed, and interactions with beta, enterprise, language, and support links. We do not send Wedelia account IDs, email addresses, or conversation content to website analytics.

Google Analytics may process the page URL, referrer and UTM campaign details, browser and device information, coarse location, and the interaction events described above. Google signals and advertising personalization are disabled. Google states that GA4 uses IP addresses at collection time to derive location and discards them before they are logged.

Choosing "Necessary only" prevents the Google Analytics tag from loading. You can reopen "Analytics settings" at any time to change your choice. Withdrawing consent stops future analytics events and removes Wedelia analytics cookies available to this site; Google may retain information already collected according to its policies.

8. Data location and international transfers

The Service is offered to users outside mainland China. Data may be stored or processed in Singapore, the United States, mainland China, or other countries where our providers operate. When you request weather or nearby-place features, or when location context is synchronized as described in Sections 3 and 4, QWeather or Amap may process your coordinates in mainland China. Privacy laws in those locations may differ from those where you live. We use appropriate contractual and technical safeguards where required.

9. Retention

We retain account and conversation data while your account is active and as needed to provide the Service. We may retain limited security, transaction, consent, and legal records for longer where necessary to prevent abuse, resolve disputes, comply with law, or enforce agreements. We retain product-email consent and unsubscribe or suppression records as needed to honor your choice and prevent further delivery. The device snapshot described in Section 4 is kept as a single most-recent copy that each sync replaces, with no separate expiry, and is removed when you delete your account. Money entries, meal logs and their photos, and reading progress are kept while your account is active and are deleted when you delete your account. Feed posts are kept while your account is active, unless you delete them or turn off their source as described in Section 3, and are deleted when you delete your account. Backup copies are removed on their normal rotation schedule. Photos, images and other files in our cloud storage, including the recent photo described in Section 3, stay recoverable by us for 7 days after they are deleted, to guard against accidental loss, and are then permanently erased.

10. Your choices and rights

Depending on where you live, you may have rights to access, correct, export, delete, restrict, or object to certain processing of your personal information. You may also withdraw consent where processing is based on consent.

You can export your data or permanently delete your account from Settings > Privacy in the app. You can also follow the account deletion instructions to start a verified request by emailing jack@wed.chat from the address associated with your account.

If Wedelia shuts down or changes hands. If we decide to discontinue the Service, or if Wedelia or its assets are sold, merged, or otherwise transferred, we will tell you by email and in the app at least 30 days in advance. During that time, export from Settings > Privacy stays open so you can download your data. We will not transfer your conversations, memories, or diary to a new owner without your consent; if you do not consent, we will delete them.

11. Security

We use access controls, encryption in transit, account-scoped data boundaries, monitoring, and other safeguards appropriate to the Service. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.

12. Changes to this policy

We may update this policy as the Service evolves. We will post the new version and effective date here and provide additional notice when required. Material changes may require you to accept the updated policy before continuing.

13. Contact

OLI & CECE INC
6175 Spring Mountain Rd
Las Vegas, Nevada 89146-8845
United States
Privacy questions and requests: jack@wed.chat.