Privacy Policy

Muze is a personal agent app operated by qthink Company ("we"). This policy explains what we collect, why, and the choices you have.

What we collect

Account information: the email address you sign in with, the name and email Sign in with Google shares (we don't keep a Google profile photo), or the information Sign in with Apple shares with us (which may be a private relay address), and the username you choose. So the app can open without a connection, it keeps on your device only the ID of the last account that finished setup and whether it opens Chat or Mail, until you sign out or reinstall. You can change your sign-in email in Me → Account by verifying the new external address. After a successful change, we send a security notice to your previous email, if one was provided. The notice contains neither a verification code nor your new email address and is separate from marketing and task-email preferences.
Content you give Muze: chat messages, tasks and their instructions, files you attach, and emails you send or receive through your Muze address (username@muze.bot).
Content Muze creates for you: reports, tables, files, and task activity.
Memory, schedules, and reminders: short facts Muze remembers about you (things you ask it to remember, or lasting details it notes from Chat, like your city, or facts you import from another assistant), and the scheduled tasks and reminders you set up. When you import, the app parses the pasted Markdown on your device and sends only the facts and retry identifiers to Muze, without the raw document or a model call. Imported facts are used in Chat and new tasks like other memories, including sharing them with our AI model provider for those interactions. You can see and delete memories in Me → Memory, or turn memory off. The optional import guide saves only whether guidance is pending or completed on the device, scoped to your account and API environment.
Things Muze follows for you: when you bring up something that will change, like a flight, a launch, or news you're waiting for, Muze notes what it is, why you care in your words, and the public pages or news feeds it will check, and keeps what it has already seen there so it only tells you what's new. Muze may also start following something you talked about in Chat that day, and says so in Updates. You can see and stop them in Me → Following, or turn following off.
Local news, if you ask for it: the name of the city you gave. You can change it or turn local news off in Me → Following.
Website sign-ins: tasks that use a browser work in your own cloud browser, so the cookies and stored data of the sites they open stay there, including any sign-in, and later tasks can use the same account without asking again. It's kept until you delete your account, and code a task runs can't read it.
Device information: a push notification token and whether your app supports unread badge updates if you turn on notifications, your time zone, and your app's language, so notifications, Live Activities, and emails from Muze use it. For Live Activities, we also store an installation identifier, an activity identifier and token, and progress-delivery state.
Location, if you allow it: while Muze has location permission, the app sends your approximate location (rounded to about 100 meters) with each Chat message. Muze uses it only for that reply, such as finding places near you or a route from where you are, and doesn't save it. It goes to our AI model provider with your message, and to Google Maps when Muze looks up places or routes. You can turn it off in iOS Settings.
Usage information: credits used, basic logs needed to run and secure the service, and when you use the app (the time of each signed-in request, with your account ID), which we use to count how many people use Muze each day. We also keep whether each saved Library item version has been opened, to show unread counts. This state stays until the version or your account is deleted and is not sent to an outside analytics provider. Before you first sign in on a device, the app sends a random identifier made for that installation with each step of signing in (such as seeing the welcome screen, choosing Apple or email, or a code that didn't arrive) and with the sign-in requests themselves, so we can see where signing in goes wrong. It isn't linked to your account, and the app stops sending it once you've signed in. Reinstalling the app makes a new one. While you're signed in, the app also tells us which screens you open, when it opens, comes back, or goes to the background (and how long it was open), when you open a notification or answer the notification permission prompt, when a screen couldn't load, and when you pull to refresh, use voice input, search, or open the share sheet for a file. These records include your account ID, the app version, and the app language, and only fixed names and codes: never what you typed or searched for, titles, file names, or which task or item you opened. We use them to see where the app is hard to use. For connected apps, we record connection times and tool-call metadata: the app and tool, account ID, time, Chat or task source, outcome, error category, duration, and whether a result was returned. These measurements contain no tool arguments, credentials, or result content and are shown to our team as aggregate statistics.

We don't use your content for advertising, and we don't sell your personal information.

Our team can see account details (email, username, sign-up date) and usage totals, such as how many tasks you ran and credits you used, to run the service and help you. That view doesn't show your chats, mail, tasks, or files. We also keep a flag for internal staff accounts so we can exclude their use from aggregate reports. The flag is removed when the account is deleted.

Voice input

If you choose voice input in Chat, Muze uses your microphone and Apple’s on-device speech recognition to turn your speech into text on your iPhone. Speech recognition models may need to be downloaded from Apple before first use. Muze does not save recordings or upload audio to Muze, Apple, or another transcription service. Stop places the recognized text in the input for you to edit without sending a message. Send submits the text with your selected attachments and mail as a Chat message, or as your answer to the current task question. Cancel discards the recording and keeps your selected attachments and mail. At 60 seconds, recording stops and the recognized text becomes an editable draft. Unsent text stays in memory on your iPhone and is cleared when the app process ends or you sign out. Sent text is processed and kept like other messages and task answers. You can switch back to the keyboard or turn off microphone and speech recognition access in iOS Settings.

Personalization

You can optionally choose a role and interests, including your own text, to personalize Chat's starter examples. Muze stores these choices with your account so they work across devices. We don't infer them or automatically send them to an AI provider. A custom interest may appear in an editable starter draft; only a request you choose to send reaches Chat. Selecting a preference doesn't start a task. You can skip this step, or edit or clear the choices in Me → Preferences. We keep whether you answered or skipped the guide so clearing your choices doesn't make you repeat setup. Your choices and guide status are deleted with your account.

To understand which first-use steps help, we record fixed identifiers for guide steps, selected role and interest options, and starter examples shown, picked, or sent. We also record when an artifact detail is opened, a Library item is added to a Chat draft, or a message carrying a Library attachment is saved. These events contain no artifact or task identifiers, titles, filenames, or file content. These records include your account, app language, time, flow version, and a retry identifier. They contain no custom preference text or conversation content and aren't sent to an outside analytics provider. They stay until you delete your account.

Feedback

When you submit feedback from Me or a feedback entry in Chat, the Muze team receives the text you confirm, linked to your account, together with the entry point, submission time, username, and contact email. Only authorized team members can see it in our dashboard. We may also send this feedback, username, contact email, entry point, submission time, and saved account time zone to our team workspace through Feishu to review and respond to it. Copies in Feishu follow the workspace retention settings and are not automatically removed when you delete your Muze account. The form doesn't attach your chats, emails, files, or diagnostics automatically, and edits you make in the form aren't sent to an AI provider. Submitted feedback doesn't expire automatically and is removed when you delete your account. Feedback from a Chat or task entry keeps that entry's ID so repeated requests save it only once.

During a conversation or task, the AI can prepare a brief feedback preview as part of its existing processing. That preview is stored with the ordinary message. It doesn't reach the team's feedback dashboard unless you review and submit it. After you submit, later conversations and tasks can use the original preview and its submission time to recognize feedback you've already sent. Your edits in the form aren't included in that AI context.

Before you submit, the app keeps your edits to a feedback draft only on that device, separately for each account and entry. Closing the form or restarting the app keeps the draft. A successful submission clears the corresponding draft; choosing to sign out clears the device's draft once your local session ends, but doesn't delete feedback already submitted to the team. If your session expires, the draft stays on your device so you can continue after signing back into the same account.

How AI processing works

To work on your tasks, Muze sends your messages, task details, what it remembers about you, and the emails, web pages, and files involved to an AI model. Requests go through Cloudflare's AI Gateway to the model provider we use (currently OpenAI). The provider processes this content to produce responses and, under our agreements, doesn't use it to train its models. Muze only starts AI tasks after you agree in the app, and you can withdraw consent at any time in Me → Privacy and AI processing. Without consent you can still use your Muze mailbox.

Service providers

Cloudflare hosts Muze, stores your data, sends and receives email, runs browsers and isolated computers for tasks, and routes AI requests.
Resend sends email when Cloudflare can't.
PlanetScale (through Cloudflare) hosts our database.
OpenAI provides the AI model.
Apple delivers push notifications, Live Activity updates, and Sign in with Apple.
Google signs you in when you choose Continue with Google (name, email, and a basic profile only; we don't keep the profile photo), separately from Gmail accounts and Google Calendars you choose to connect. Google also provides Maps place and route lookups (what Muze searches for, and your approximate location when you ask about places near you).
YouTube (a Google service) provides video search results and the video player. It receives the search words Muze looks up and, when a video card or player loads in the app, the information described in YouTube videos below.
Open-Meteo provides weather forecasts. It receives the place names Muze looks up.
Kiwi.com provides flight searches. It receives the routes and dates Muze searches for.
Feishu hosts our team workspace. It receives the feedback you submit, with the details described in Feedback above.

Task notification replies and approvals

Task notifications can include the complete current question, its answer options and descriptions, or an action awaiting your approval. Short single-choice questions can show buttons in the expanded notification; multiple choices and content that needs more review open the original question in Muze. For a short email draft, this includes its sender, recipient, subject, and body. Apple receives this content with account, task, notification, question, option, and approval identifiers to deliver it. Your selected choices and written answer are saved with the original conversation or task. Passwords, verification codes, keys, and sign-in links stay out of notification previews. Long content and actions that need additional consent open the existing app screen. Other task notifications say what happened, which can include who replied or who an email went to.

iOS controls notification previews. With previews hidden, the Lock Screen shows only a fixed line for each kind of notification, such as "A reply came in." Choosing Always can show content on your Lock Screen. Replying or approving requires device authentication, which does not itself hide the preview. To submit these actions while the app is closed, Muze keeps a copy of your current login session in this iPhone's Keychain, available only after unlocking. It is sent only to your Muze server, not in a notification. Signing out, reinstalling, or turning notifications off in Muze clears this copy. Your reply or decision is checked against the original task and approval version.

Later reminders on your iPhone

If you postpone a reminder from its notification, your iPhone keeps its original notification text, account and reminder identifiers, and the time to notify you again. Muze also keeps the current account and server address on the phone so notification actions work while the app is not open. The snooze time is not sent to our servers or another provider, and the original reminder schedule does not change.

You can view and cancel later reminders in the reminder's details. Turning off notifications in Muze or signing out clears them from that iPhone. Changes made on another device cannot immediately cancel a notification already scheduled on this iPhone while it is offline or Muze is not running.

Live Activities

Live Activities show progress for tasks on your Lock Screen and Dynamic Island. Apple receives fixed progress text and delivery identifiers, without your task titles, questions, messages, mail, or model output. Activity tokens are cleared after successful final delivery or when Apple reports that a token is invalid. Server tracking records become eligible for deletion after 24 hours. Hourly cleanup removes them in batches, oldest first; a backlog can delay removal. Deleting your account removes its server tracking records.

On your device, Muze keeps activity identifiers and status flags to restore progress, finish pending requests to stop updates, and remember displays that ended or that you closed. These records stay in the app's storage when new tasks arrive. They contain no conversation content or activity tokens.

You can turn off Live Activities for Muze in iOS Settings, independently of ordinary notifications. You can also stop one task's Lock Screen updates from that task's menu. Hiding its progress doesn't stop the task.

Email

Muze only sends email from your address to recipients you've allowed. When you ask it to email someone on your allowed list, it sends without asking again, unless it can't tell whether the email fits your request; email to anyone else needs your approval for each message. Emails you receive are stored so you can read them and so tasks can continue when replies arrive. We show email as plain text and don't load remote images.

If notifications are on, new mail to your Muze address can trigger a phone alert showing its sender and subject, never its body. Subjects with verification codes or links are replaced by fixed text. Apple receives the notification with account and mail IDs so a tap can open the email.

Emails from Muze

Marketing emails include welcome messages and updates from our team. They use common content reviewed by the team, rather than content generated from your conversations or memories. Task emails can tell you a task is finished, needs your input, or that a stored Library file is about to expire. They can include the task or file title and its current status. These emails go to your verified sign-in address, including an Apple private relay address.

You can turn Marketing emails and Task emails on or off separately in Me, independently of push notifications. Both categories contain an unsubscribe link that turns off only that category. The unsubscribe page also explains how to change either setting in the app. Sign-in codes are separate. Images in marketing emails are the same for everyone and aren't counted, so we don't track when you open an email. For marketing emails, we record when the email's link is visited and when the account that received it returns to the app. Link visits can come from automated scanners, so they don't prove that you read a message. Task emails aren't measured.

Marketing-email measurement stops after 30 days or when you turn off Marketing emails or unsubscribe. We associate manual tasks created within seven days of an app return with the most recent email return to measure how useful our emails are. Reports show aggregate counts, not your task instructions or conversations. Email measurements don't store your IP address or browser user agent. We also record delivery outcomes and unsubscribe requests. These records stay with your account and are deleted with it. We use them for Muze's own communications, not cross-app advertising. You can reply to the support address in these emails with feedback.

Connected Gmail accounts

If you choose to connect a Gmail account, Muze asks Google for permission to read, organize, and send email in that account. We use this access only to provide features you can see in the app: summarizing your inbox, finding subscriptions and bills, turning emails into reminders and tasks, reading available email settings, organizing messages and labels when you ask, and drafting and sending emails. Drafts can include HTML, Cc, Bcc, attachments, and a verified send-as address. Email to recipients outside your allowed list waits for your approval of each message; sending without review requires every To, Cc, and Bcc address to be allowed. Marking an email as spam, moving it to trash, and deleting a label each wait for your confirmation in the app. Muze only reads email settings; it doesn't change them.

What we access: message content, headers, labels, and attachments in the connected account, and the account's email address. When you ask about email settings, we also read the settings Google makes available, including language, forwarding, IMAP and POP, vacation replies, and send-as addresses and their verification status.
How it's stored: access tokens are encrypted at rest. We read email and settings from Gmail when a feature needs them and don't keep a copy of your mailbox. For emails Muze sends, we keep the sending address, To/Cc/Bcc recipients, plain text, HTML source, and independent copies of attachments, even if you delete the task, draft, or original file. We display email as plain text without loading remote images. Sent attachment copies expire after 30 days of inactivity unless you tap Keep on the email or its task. Sent records, settings summaries, Chat, tasks, and drafts follow the Retention rules below.
Disconnecting: you can disconnect Gmail in the app at any time. We then revoke our access with Google and delete the stored access tokens, so Muze can no longer read or change that account. Chats, tasks, drafts, and sent mail that involved it follow the Retention rules below and are deleted with your account. You can also remove access at myaccount.google.com/permissions.

iPhone calendar

If you allow calendar access, Muze reads up to 500 events from the past week to the next month with each Chat message. This includes event titles, times, locations, calendar names, recurrence information, and identifiers. Muze uses them to answer questions about your schedule, find free time, and prepare changes you request. The relevant details reach our AI model provider as described above.

Calendar snapshots and calendar tool arguments and results are used in memory for that reply and aren't saved on our servers or in application logs. Pending calendar card parameters and a separate proof held by your requesting iPhone can remain in server memory for up to 10 minutes after the reply ends to recover a lost connection. Only that iPhone can recover them; completing or cancelling the card, sending a new request, or reaching that limit clears them, and a server restart loses them. This recovery memory isn't written to server storage. Normal Chat messages, including event names and times mentioned in the conversation, are kept under the Retention rules below. Confirmation details and execution receipts stay on your iPhone, separately for each Muze account and server; our servers keep only the requested action and its status.

When you ask in Chat, the app adds events directly on your iPhone, and changes or deletes an event after you confirm on its card. The app writes the change through your iPhone's calendar access, without a background task or a cloud computer. Your calendar account may sync that change according to its own settings. You can turn off Muze's calendar access in iOS Settings.

iPhone reminders

When you connect iPhone reminders in Me → Connected apps or a Chat card, Muze asks for your permission to share requested reminders with Muze and its AI provider, separately from iOS access. A model tool requests only the matching reminders needed for your reply, up to 25. Each includes its title, due date, notes, completion state, whether it repeats, list name, and identifier. Reads default to unfinished reminders and can filter by the requested list and due or completion dates before selecting results. Only names of lists containing matching results are shared, not the whole list catalog. Reading does not happen automatically with every message or in the background.

Raw results are used in memory for that reply and aren't saved on our servers or in application logs. Pending card parameters and a separate proof held by your requesting iPhone can remain in server memory for up to 10 minutes to recover a lost connection, including after the reply ends. Only that iPhone can recover them. Completing or cancelling the card, sending a new request, or reaching that limit clears them. A server restart loses them. This recovery memory never contains raw read results and isn't written to server storage. Pending phone read parameters stay on the requesting iPhone until it receives Muze's confirmation; acknowledged reads retain only a status receipt. Normal Chat text can contain reminder details and stays under the Retention rules. Confirmation details and write receipts stay on your iPhone, separately for each account and server; our servers keep action/status receipts. Adding, changing, completing, reopening, or deleting reminders requires your confirmation on that iPhone. The app checks for changed targets and duplicate additions before writing through EventKit. Your reminder account may sync changes according to its own settings. Disconnect in Me → Connected apps to stop access for this account on this iPhone, or revoke Reminders permission in iOS Settings.

iPhone health

With your separate sharing consent and Health permissions, Muze can answer health and fitness questions from selected summaries of steps, sleep, workouts, and weight. The phone aggregates only the requested information, for at most 31 local dates, and sends the summary to Muze and its AI provider for that reply. Raw samples and source metadata stay on your iPhone. Missing values may mean there are no readable records or you haven't shared that type; they aren't treated as zero or as proof of read access.

This access is read-only and runs only when requested in Chat. Muze does not write Health records or read them in the background, and does not use HealthKit data for advertising or marketing. Results stay in memory for the reply, not in server history or application logs. Pending query parameters use the same requesting-iPhone proof and 10-minute recovery limit described above, without retaining the results. Normal Chat text may mention the values and is kept under the Retention rules. Disconnect in Me → Connected apps to stop access for this account on this iPhone, or manage data-type permissions in Apple's Health app.

Connected Google Calendar

When you connect a Google account, Muze asks Google for Gmail and Calendar permissions together, including permission to view and edit events in your calendars. We use this access only for features you can see in the app: answering questions about your schedule, finding free time, including your day's events in briefings you set up, and adding or changing events you ask for. Muze never invites anyone to an event, or changes an event other people are invited to, without your approval of that event.

What we access: events in your calendars (titles, times, places, descriptions, guests) and your busy times.
How it's stored: access tokens are encrypted at rest. We read events when a feature needs them and don't keep a copy of your calendar; events Muze proposes, and what it said about your schedule in Chat or tasks, are kept and deleted under the Retention rules below.
Disconnecting: you can disconnect the account in the app at any time, which also ends calendar access, or remove access at myaccount.google.com/permissions.

Muze's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don't use Gmail or Calendar data for advertising, don't sell it, don't use it to train or improve general AI models, and don't let people read it except with your permission, for security, or to comply with the law.

To provide these features, the Gmail and Calendar content involved in a request is sent to our AI model provider as described in How AI processing works. The provider processes it only to produce that response and doesn't use it to train its models. Gmail and Calendar data is never transferred to anyone else except as needed to run Muze, for security, to comply with the law, or as part of a merger or acquisition with your notice.

Connected apps

You can connect other services in Me → Connected apps: Notion, Todoist, Linear, Jira and Confluence, Canva, and Calendly. You sign in on the service's own page, and Muze stores the access it grants, encrypted. Muze then sends the service the requests needed for what you asked, which can include text from your chats and tasks, and reads what it returns. Muze looks things up on its own, but asks for your approval of each change before it adds or changes anything in one of these services, unless you chose Always allow for that tool on an approval card. Even then, it asks first when it can't tell whether a change fits your request. Each use still shows in the task's activity. We keep which tools you always allow until you remove them in Me → Connected apps, disconnect the service, or delete your account. Each service handles the data it receives under its own privacy policy.

You can also add a personal MCP service by sending its public HTTPS address in Chat. Before connecting, Muze shows the address and explains what may be shared. We store its name, address, connection state, discovery metadata, and encrypted access tokens until you disconnect it or delete your account. Requests and results can include information from your chats and tasks. You review each tool call before it runs, including reads, unless you chose Always allow for that tool. The service you choose handles the data it receives under its own privacy policy. Disconnecting removes the saved connection and tokens; the usage metadata described above stays until account deletion. Connection confirmations, including names and addresses, stay in Chat history until account deletion. We also keep discovered tool names with your saved connection to show its capabilities without contacting the service for every chat.

Disconnecting a service in the app deletes the access Muze stored. You can also remove Muze in that service's own settings.

Following

Muze checks the pages and feeds for the things it follows from its own servers, without your account, email address, or location. For news it often reads a Google News search feed, which sends the words of the topic to Google, under Google's privacy policy. Only when something new turns up does Muze ask the AI model whether it's worth telling you, sending what you follow, why, and the new content, as in Chat. News arrives in Updates, and as a notification if notifications are on. When a page or feed can't be read, Muze may look for the same news with the AI model's web search, which gets the topic and why you care. This never uses your credits.

Insights and local news

While Memory is on, once a night Muze sends that day's Chat, what it remembers about you, and your reminders and recent tasks to the AI model, as in Chat, to see whether anything is worth pointing out, like a date coming up with no reminder. What it finds is saved in Updates like other updates. You can turn insights off in Me → Following.

For local news, Muze asks the AI model, with its web search, for that day's news about the city you gave, without your account or email address. The brief is shared by everyone who asked for the same city and deleted after a few days.

YouTube videos

When you ask Muze to find or show videos, Muze uses YouTube API Services to search YouTube and shows the results as video cards you can play in the app. By using Muze's video features, you agree to be bound by the YouTube Terms of Service. YouTube is a Google service; the Google Privacy Policy explains how Google handles your information.

What Muze sends to YouTube: up to 5 search words Muze takes from your request. Searches are made from Muze's servers with Muze's own YouTube API key, not with your Google account, and don't include your name, email address, or location. Muze searches YouTube only when you ask for videos. To show relevant videos, we send your device's language and region to YouTube with your search. We don't link them to your account. Search results are cached for up to 6 hours, keyed by search words, language, and region.
What Muze receives and keeps: public details about matching videos, such as the video ID, title, channel name, thumbnail link, length, and publish date. Muze saves up to 50 results with the chat message so the card still works when you reopen the conversation. Older versions of the app show the top results as titles and links in the reply instead. The app stops showing these details 30 days after Muze got them from YouTube and says the results have expired, and Muze then removes them from its servers. To avoid repeating the same search, Muze's servers keep a shared copy of results for the same search words, language, and region for up to 6 hours; that copy isn't linked to your account. Muze never downloads or stores the videos themselves. If you ask for videos in a task, the top results are also kept in the task history and removed up to 6 hours before the 30-day limit to account for shared cache hits.
AI: the titles, channel names, links, and lengths of the top 5 results are sent with your message to our AI model provider, as described in How AI processing works, so Muze can write a short recommendation. That recommendation is written by Muze, not by YouTube. What Muze writes using these results, such as a Chat reply, a task result, a memory, or an email, is kept and deleted under that feature's own Retention rules below.
Playing videos: thumbnails load directly from YouTube, and videos play in YouTube's embedded player inside Muze. Muze uses YouTube's privacy-enhanced mode (youtube-nocookie.com) where available. When a thumbnail or player loads, or you play a video, your device connects directly to YouTube. YouTube may receive information such as your IP address, device details, and what you watch, may serve content including ads in the player, and may store or read cookies or similar data on your device, as described in the Google Privacy Policy. Muze doesn't remove or change YouTube's ads, branding, or links. Tapping the YouTube logo or video title in the player opens YouTube.
Your YouTube account: video features don't ask you to sign in to YouTube or Google. Muze can't see your YouTube account, watch history, subscriptions, or playlists, so there is no YouTube permission to revoke. If you connected a Google account for Gmail or Calendar, that connection doesn't give Muze access to YouTube; you can review or remove Muze's access to your Google account at any time in your Google Account permissions.
Deleting your data: deleting your account deletes all of your chats, including saved video results, within 7 days. Deleting data in Muze doesn't affect anything stored by YouTube or Google; to manage that data, use YouTube or your Google Account.
Questions: contact us at support@team.muze.bot with questions or complaints about how Muze handles YouTube data.

Report images

Reports can include images hosted by other websites. When you open a report, the app automatically loads its images directly from those hosts, without a separate confirmation. The hosts receive your IP address, the time of the request, and the full image URL, including any query parameters. A URL may contain tracking identifiers or signed access links. The app doesn't add your Muze sign-in token or other report content to these requests. Each host handles the information it receives under its own privacy policy.

Retention

Chats, tasks, mail, Library items, memories, schedules, and reminders stay until you delete them or your account. Something Muze follows stays until you stop it or its date passes, or after a month without you showing interest in it; what Muze saw while checking it goes with it. Video results saved with a chat or task are removed 30 days after Muze got them from YouTube, and the shared video search cache keeps results for up to 6 hours without linking them to your account. Files (Library files such as images and PDFs, email attachments, and files you attach in chat) are deleted 30 days after they were last used, unless you mark them Keep; the item itself stays. Records of when you made signed-in requests, the in-app usage records, and the sign-in steps above, are kept for about three months. Connected-app usage measurements stay until you delete your account, including after disconnecting an app. Deleted data is removed from active systems promptly. It may remain in our database backups for up to 30 days, after which it is deleted automatically.

Deleting your account

You can delete your account in the app (Me → Signed in as → Delete account). This stops your tasks, turns off your Muze mailbox, disconnects your connected accounts and apps, and deletes your data. If you used Sign in with Apple, we also revoke Muze's access to your Apple Account. Your username is retired and never given to anyone else. Emails that were already sent can't be recalled.

Security

Data is encrypted in transit and at rest by our providers. Each task runs in an isolated environment.

Children

Muze isn't directed to children under 13, and we don't knowingly collect their information.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your information. Contact us at support@team.muze.bot.

Changes

We'll post updates here and change the date above. Significant changes will be announced in the app.

Contact

qthink Company. Email: support@team.muze.bot.