Kainauts

Kainauts Privacy Policy

Provisional. We are changing the entity that operates Kainauts; this document will be updated and the change announced once that is done.

Last updated: November 16, 2026

This Privacy Policy explains how LO YU-HUNG, an individual trading as "Kainauts" ("we", "us"), collects and uses personal information when you use the Kainauts website (https://kainauts.ai), apps and related services (the "Service"). We are the controller of this information. We intend to transfer the Service, and this role, to a company set up to run it; we will tell you before that happens.

Privacy contact: [email protected]
Country: Taiwan (R.O.C.)

1. Summary

  • We collect what we need to run your Crew: your account details, what you send to your bots, and basic usage and device data.
  • To answer you, we send your prompts to third-party AI model providers. Our built-in routes are set up to use only model providers whose terms say they do not use requests to train models; they may keep requests for a limited time for safety and legal reasons (see section 4). When your Crew searches the web, the search query goes to a web search service (see section 4).
  • We do not sell your personal information, and we do not use your content to train AI models.
  • We store your messages on our servers so your chats work across devices. You can delete any of your messages at any time, or request deletion of your data in Settings. After deletion we keep only what the law requires, what we need to prevent fraud and abuse and to handle disputes, emails you sent to our support address (for a limited period), and messages you posted in groups, which stay with the group, as described in section 7.
  • Payments on our website are handled by our reseller, which is the Merchant of Record. We do not see or store your full card details.
  • You can export or delete your data and delete your account in the app.

2. Information we collect

Account information. Email address, display name, date of birth (self-reported, used only to check that you are at least 18 and not stored), the fact that you confirmed you are at least 18, sign-in data (such as passkey public keys), plan and subscription status, and settings.

Unregistered members. If you join a group through an invite link without an account, we assign a random identifier and store the messages and settings linked to it.

Content. Messages, prompts, files, images, videos and other input you send; the responses your Crew generates; memories you ask a bot to keep; goals and tasks; and content you share in groups or chat rooms.

Voice. When you speak to the app (dictation or voice mode) and your device has no built-in speech recognition, your recording is sent to our servers and to a speech-to-text provider, then turned into text. We do not store the audio, and the app does not keep it on your device. When your device has built-in speech recognition, your voice is handled by your device's own service under its terms and does not reach us. Replies read aloud in voice mode are sent as text to a text-to-speech provider. Voice messages you send in a chat are different: they are stored like your photos and files (they count toward storage, in a group the owner's, and are deleted with the message), and the people in that chat can play them. When Crew is asked to reply and the plan covering that chat includes cloud dictation, the voice messages it needs, up to one minute each (longer ones are kept and played but not transcribed), are sent to a speech-to-text provider once, and the text is kept with the message so Crew does not need to listen again; it is deleted with the message. We use only providers whose terms say they do not use your voice or text to train models; they may keep requests for a limited time for safety and legal reasons (see section 4).

Connections. Credentials and settings for tools you connect (for example MCP connectors) and for custom models (your own API keys, model endpoints, and AI subscriptions you sign in with). Credentials are stored encrypted.

Payment information. For web purchases, our reseller collects your payment details and billing address and shares with us your name, email, country, the plan purchased and transaction status. For app store purchases, the app store shares purchase status with us. To enforce our refund policy, we also keep the customer number our reseller gives you and, for purchases in the iOS app, an identifier that is the same for every purchase from the same store account.

Usage and device data. IP address, approximate country, device and app version, a device identifier (on Android, the device's Android ID; on iOS, an ID the app creates when it is installed; on the web, a cookie in your browser), log and error data, the model route used for each request and usage counts needed for your weekly allowance, and push notification tokens. Error reports and performance measurements (how long each request takes, named by the type of request, not its address) have personal data removed before they leave our servers and are not tied to your account.

Usage statistics. Which screens of the app and website you open, how long the app takes to start and pages take to load, and how often each feature is used. These records carry only a random identifier created for each visit and kept in your device's memory, never your account, email, device identifier or message content. We count feature use on our own servers without recording who used it. You can turn usage statistics off at any time in Settings → Data & privacy; the choice applies to that device.

Communications. Emails and reports you send us.

Copyright notices and counter-notices. If you tell us that content on the Service infringes your copyright, we collect your name, your email address (your account's, or the one you write from), the description of the work you give and your statement. The person whose content is named sees that description, so do not include personal details in it. If content you shared is named in such a notice and you send a counter-notice, we collect your name, postal address, phone number or email address, and the reason you give, if any.

Removal requests on our website. If you use the form on our website (kainauts.ai/report-content) to ask us to remove intimate images shared without consent, we collect your name (which is also your signature), your email address, the name of the person you act for if that is not you, the content codes you enter, what you tell us about where the content is and why it was shared without consent, and your statements. If you send a copyright notice with the form on our website, we also collect your postal address, your phone number if you give it, and the name of the rights holder if you act for one; these are handled like the other notice details above. We use the IP address a form is sent from only to limit how many requests can be sent. When you get a content code in the app, we record which account got it, for which message, and when.

We do not knowingly collect information from anyone under 18 (see section 9).

3. How we use information, and our legal bases

Purpose Legal basis (where applicable)
Provide the Service: run your bots, memories, goals, groups and connected tools Performance of our contract with you
Send your input to AI model providers to generate responses Contract; and your consent where required
Manage subscriptions, usage allowances and support Contract
Keep the Service safe: detect abuse, filter content shown to others, enforce our Terms Legitimate interests; legal obligation
Respond to payment disputes and establish, exercise or defend legal claims Legitimate interests
Fix bugs and improve the Service using aggregated or pseudonymous usage data Legitimate interests
Send service emails (sign-in links, receipts, important notices) Contract; legitimate interests
Comply with law and respond to lawful requests Legal obligation

Some decisions in the Service, such as whether a goal should continue or whether content breaks our rules, are made with the help of automated AI decision services. Where the law gives you this right, you can ask for a person to review a decision made solely by automated means that has a legal or similarly significant effect on you.

4. AI model providers and training

To generate responses, we send the relevant part of your conversation and context to third-party model providers, sometimes through routing services. We route requests automatically between providers based on availability, speed and cost.

  • No training, on every plan. We do not use your content to train AI models. Our built-in (official) routes are set up to send requests only to providers and endpoints whose terms say they do not use that data for training. If none is available, we do not fall back to one that does.
  • We store your chats. We keep your messages and files on our servers so your chats work across devices, as described in sections 1 and 7.
  • Providers may keep requests for a limited time. Model providers and routing services may keep prompts and responses for a limited time for safety reasons (such as detecting abuse) and legal reasons, under their own terms. The longest period we know of on our official routes is up to 730 days, for content that a provider's safety systems flag or that it must keep for legal reasons. We do not promise zero data retention.
  • Everything else follows each provider's terms. Model providers, routing services, and any tool or connector your Crew uses process the content they receive under their own terms, including any safety checks they run.
  • Custom models: when you use your own key, endpoint or AI subscription, the request goes to that provider under your own agreement with it, and its privacy, retention and training terms apply.
  • Web search: when your Crew needs current information, it may search the web. We send only the search query your Crew writes from the conversation to a web search service, never your account details, but the query can include things you mentioned in the conversation. The search service handles queries under its own terms and may keep them; the no-training commitment above covers our AI model providers, not the search service. Search results come from third-party websites and may be inaccurate. If you do not want a topic searched, tell your Crew not to search the web.

5. Who we share information with

We share personal information only as needed to run the Service:

  • AI model providers and routers (see section 4).
  • A web search service, which receives the search queries your Crew writes when it searches the web (see section 4).
  • Infrastructure providers: hosting, network and security, email delivery, and error and performance monitoring. Usage statistics stay on our own servers and are not shared with analytics companies. Visitor statistics for the website kainauts.ai (pages viewed, referring site, country and device type) are aggregated by our network provider without cookies and without identifying you.
  • AI decision and content-safety services used to evaluate goals and moderate content.
  • A security check service on our sign-in and sign-up pages, which looks at technical information from your browser and connection (such as your IP address) to tell people from automated programs (bots).
  • A child-protection organisation, if we switch on checking of uploaded photos and videos against its list of known child sexual abuse material (we may do so as the service grows). Only the photo or video is sent for this check. We do not use AI or people to review your ordinary photos and videos.
  • Our reseller, as Merchant of Record for web purchases, and the app stores for in-app purchases. When you dispute an app store purchase with your card issuer or bank, or ask the app store for a refund, we may tell that store how much of the purchase was used and whether we recommend a refund; we never share your message content.
  • Tools you connect, when your Crew acts in them on your instructions.
  • Other members of groups and chat rooms you join, who see what you post there. Group owners cannot read members' private chats with a bot.
  • The person on the other side of a copyright notice. When you send a counter-notice, we forward it to the person who sent the copyright notice, with your name, postal address, contact details and the reason you give, and the start of the content concerned, as the law requires and as you agree when you send it. We do not tell the person whose content is named who sent the notice.
  • The person whose content is removed after a removal request. We tell them that the content was removed after a request and how to appeal, but not who asked for the removal or how to contact them.
  • Professional advisers and authorities, when required by law, to protect rights and safety, or in connection with a reorganisation or sale of the Service.

A current list of subprocessors is available on request at [email protected].

6. International transfers

We are based in Taiwan (R.O.C.). Our servers and service providers may process data in other countries. Where required, we rely on appropriate safeguards for these transfers.

7. Retention

  • Account data and content: kept while your account is active. When you request account deletion, your account keeps working for 14 days and you can cancel the request in Settings; after that, everything is deleted automatically, except messages you posted in groups, which stay with the group and are shown as coming from a "deleted account" (see Messages below) for as long as the group exists (a group is deleted, with everything in it, only when its owner's account is deleted and no member can take it over), the copies of reported messages and the other records described below as kept longer. Backups roll off within 30 days. If we delete an inactive free account as described in our Terms, its data is deleted in the same way.
  • Messages: stored on our servers while your account is active. You can delete any message at any time; it is removed from the Service right away, and its stored files and backup copies are deleted within 30 days. If a message was reported, a copy is kept for moderation review, including its photos, videos and files; if it is removed, that copy is kept for 180 days. A report that is still waiting for review is kept until it has been handled. These copies are kept until the end of that period even if you, or the other person involved, delete your account in the meantime, so that deleting an account cannot be used to avoid a report; they are then deleted automatically. If a report is dismissed, its copy is deleted sooner. You can also request deletion of all your chat data in Settings (your direct messages, your Crew conversations, summaries and Crew memories; messages you posted in groups stay with the group, and other people's messages are not affected): it is deleted automatically after 14 days, and you can cancel the request in Settings before then. Messages you posted in a group belong to the group and stay with the group, both when you delete your chat data and when you delete your account; after account deletion they are no longer linked to you and are shown as coming from a "deleted account". You can still delete any single message yourself at any time. A group itself is deleted, with all its messages, only when its owner's account is deleted and no member can take it over (see the Terms). We keep information beyond this only where the law requires it or as described in this section.
  • Child sexual abuse material: if we find, or are told, that a photo or video you uploaded is child sexual abuse material (including a match from the check above, if it is on), we keep that photo or video, the account email, the IP address and the device information from the upload for at least 365 days (and for at least that long after we report it to the authorities), even if the account is deleted, then delete them, and share them with the authorities as the law requires.
  • Unregistered members: data is deleted after 30 days without any use. Any use counts, including just opening the app or reading a group. If notifications are on, we send a reminder 7 days before. Messages, photos and videos you posted in a group chat stay in that group so its history stays complete, but they are no longer linked to you and are shown as coming from a "former guest". Everything else is deleted.
  • Billing and transaction records: kept as long as required for tax and accounting, also after your account is deleted. They include the customer number our reseller gives you and the app store account identifier described under Payment information above, in the form they were issued, not hashed.
  • Refunds and chargebacks: if you get a refund because you changed your mind (from us or from an app store) or file a chargeback, we keep scrambled (hashed) versions of your account ID, email address, device identifiers and payment identifiers, and of the IP addresses your account used, so that the same person cannot subscribe again with another account or device (see our refund policy). We keep them after your account is deleted. If you delete your account within 180 days of your last payment, we also keep hashed versions of your account ID, email address, device and payment identifiers until 180 days after that payment, only so that a refund or chargeback that arrives later can still be applied; then they are deleted. If you show us the block was applied by mistake, we lift it. While your account exists we also keep hashed versions of the device, IP address and payment identifiers seen when you start a purchase; they are deleted with your account.
  • Locked accounts: if a chargeback on your account is upheld (other than one raised because of our error) or we permanently suspend your account, the account is locked (see our Terms of Service). A locked account and its data are deleted automatically 90 days after the lock. While a payment dispute about it is still open, we wait until the dispute is closed, but at most 180 days after the lock. What the law requires us to keep is not deleted (see Child sexual abuse material above). In that case we keep hashed versions of your account ID, email addresses, device identifiers (including devices used to sign in while the account is locked), payment identifiers and app store account identifiers indefinitely, also after the account is deleted, only to prevent fraud: the same email address or device cannot be used to create a new account, and none of them can be used to buy again. The hashes are made with a secret key held only on our servers, and this block list does not contain the original values (billing records are described above). IP addresses are recorded next to the block, but we never use them to refuse anyone because of a lock or the block list. Separately, to stop automated abuse, we limit how many sign-in emails can be requested from one IP address in a short time, and new accounts created in bulk from one IP address have their free AI use paused for a while.
  • Chargeback evidence: when a chargeback locks an account, we copy a summary of how the account was used during the disputed period, its sign-in times, the device and IP address records from our logs, and which kinds of purchase identifiers we saw and when (not the identifiers themselves) into a separate record, to respond to the dispute and to establish or defend legal claims. We keep that record until the dispute is closed, but at most 180 days after the lock, even if the account is deleted in the meantime; then it is deleted.
  • Emails to our support address: emails sent to [email protected] (including reports, requests, copyright notices and counter-notices), and our replies to them, are deleted automatically from our support mailbox within 365 days after they arrive or are sent. Deleting your account does not by itself delete them. If an email is needed for a legal claim, a lawsuit or a request from an authority that is still open at the end of that period, we keep it until the matter is closed and then delete it. Information we copy from an email into our case records is kept for the periods described elsewhere in this section.
  • Removal requests sent with the forms on our website: a request that is not confirmed is deleted 24 hours after it is sent. If something goes wrong on our side while handling a confirmed request, we keep it, with your details, for 30 days so that we can finish it, then delete it. When a confirmed request has been handled, the name, email address and other details you entered are deleted from it, and the rest of it (when it arrived, the last characters of each content code, and the outcome) is deleted 30 days later. The report it creates keeps, with its copy of the content, your name, the name of the person you act for, what you said about where the content is and your statement, and is kept as described under Messages above, and a copyright notice as described in the next item. To limit abuse, we keep a hashed version of the requester's email address with the number of their requests we dismissed, for as long as the forms are offered. Content codes are deleted when they expire, 30 days after they are created, or when the account that got them is deleted.
  • Copyright notices and counter-notices: in our case records, the names, email addresses, postal addresses, phone numbers and reasons given in a notice or counter-notice are kept while the case is open and deleted when it is closed. Notices and counter-notices sent to us by email are also kept in our support mailbox, as described under Emails to our support address above. We keep a record of how each notice was handled: how and when it arrived, when the content was made inaccessible, when the person who shared it was told, when a counter-notice was received and forwarded, when proof of a lawsuit was received, and the outcome. The record has the content's identifier and a hashed version of the email address of the person who sent the copyright notice, but no names or contact details. We keep it for 3653 days after the case is closed, also after an account is deleted, so that we can show how a notice was handled if that is disputed. The count of copyright notices against an account keeps only that hashed email address and is deleted with the account that received them.
  • Activity records: which days you used the Service (only the date), used to count active users. Kept for 400 days and deleted with your account.
  • Usage statistics: kept for 90 days, then deleted. They are not linked to your account, so they cannot be found or exported by account.
  • Logs: server logs and error reports are kept for up to 30 days for security and debugging, then deleted.

We may keep information longer when the law requires it or to resolve disputes and prevent abuse.

8. Your rights and choices

Depending on where you live, you may have the right to access, correct, export or delete your personal information, to object to or restrict certain processing, and to withdraw consent. You can:

  • delete any of your messages at any time;
  • view, export and delete your bots' memories and conversations in the app;
  • request deletion of your data in Settings, and cancel the request within 14 days;
  • request account deletion in the app, and cancel it within 14 days;
  • turn usage statistics off in Settings → Data & privacy;
  • email [email protected] for any other request.

We answer email requests within the time required by the law that applies to you. If we need more time, we tell you why in writing before the deadline. We verify your identity by writing to the email address on your account; we do not ask for identity documents unless that is not enough. You may also complain to your local data protection authority.

9. Minors

The Service is only for people aged 18 or over. We ask for a date of birth at sign-up and do not verify it. If we learn that a user is under 18, we delete the account and its data; if you believe someone under 18 has given us personal information, contact [email protected]. If your device's app store shares an age range with the app, we use it only to check our minimum age: if it shows you are under 18, or that your store account is managed by a parent or guardian, the account is locked and deleted. We do not store the age range; if it leads to a lock, we keep only the fact that the account is locked for age, until the account is deleted. When we turn someone away as under 18, that browser or device refuses new sign-ups for 30 days. We never use any of this for advertising, marketing, profiling or analytics.

10. Security

We use encryption in transit, encryption of stored credentials, access controls and isolated sandboxes for code execution to protect your information. No system is perfectly secure, so we cannot guarantee absolute security.

11. Cookies

Our website uses cookies and similar technologies that are necessary for sign-in, security and checkout. Usage statistics (section 2) do not use cookies: their random identifier lives only in the page's memory for the visit, and a setting in your browser's storage remembers if you turned them off. Visitor statistics for kainauts.ai do not use cookies either. We do not use advertising cookies. You can control cookies in your browser settings.

12. Changes

We may update this policy. If we make material changes, we will notify you in the app or by email before they take effect.

13. Contact

LO YU-HUNG (Kainauts)
Email: [email protected]
Country: Taiwan (R.O.C.)
Postal address: available on request at [email protected]