Home / Safety / Kimi for the events sector

Moonshot AI

How safe is Kimi for the events industry?

GDPR profileOur summary of what the provider itself publishes about your data: EU hosting possible, no training on your data for business use, and self-hosting available. Caution means a model with a documented issue, such as an investigation by a regulator. How we measure for the events sectorCaution

Kimi raises a concrete GDPR concern. The parent company is based in Beijing and falls under Chinese security legislation; its privacy policy does not explicitly mention that jurisdiction. Keep confidential data out of the consumer app; self-hosting the open weights is the safe route. Weigh this heavily before using it in the events sector.

Where does Kimi stand in the events sector?

Shared spot 20 of 26 options for the events sector (professional tools and general assistants) on GDPR profile. 7 options, like Kimi, have a profile to watch. Each tile is an option we track for this field; click for the check.

Strong5
Good7
Limited4
Unknown3
Caution7

Stronger or equally strong in the events sector

Latest developments

26 July 2026Kimi K3 open weights (27 July): self-hosting avoids China transfer, licence still unclear

On 27 July 2026, Moonshot AI published the full open weights of Kimi K3 (2.8 trillion parameters, 1M-token context) on Hugging Face. Self-hosting on EU infrastructure sidesteps the GDPR data transfer problem of the hosted API (servers in China, no SCCs published). Point of attention: the final licence terms were not yet published at launch (26 July), Kimi K2 carried commercial restrictions above a certain usage scale. Verify the licence before production use. Infrastructure requirement: approx. 1.4 TB of storage, 350–400 GB of GPU memory with MXFP4 quantisation. source

16 July 2026Kimi K3: no opt-out for model training, data processed in China

At the launch of Kimi K3 (16 July 2026), Moonshot AI's privacy policy states that user content may be used for model training and optimisation, with no in-product opt-out. API calls via platform.moonshot.ai are processed on servers in China; an adequacy decision or SCCs are not explicitly documented. For EU organisations: do not enter personal data until Moonshot publishes a GDPR-compliant set-up. Self-hosting on EU infrastructure (open weights available from around 27 July 2026) avoids the transfer problem. source

Questions

How safe is Kimi for the events sector?
Kimi has a concrete GDPR concern. The parent company is based in Beijing and is subject to Chinese security legislation; the privacy policy does not explicitly name that jurisdiction. Do not put confidential data into the consumer app; self-hosting the open weights is the safe route. Weigh this heavily before deploying it in the events sector. There is a concrete GDPR concern, read the details on the page.
Does Kimi train on my data?
The international service is provided by Moonshot AI Pte. Ltd. (Singapore); according to the privacy policy, data is stored on servers in Singapore and content may be used to improve the service. The K2 models are open-weight and can be self-hosted.
What should I watch out for with AI in the events sector?
Attendee data (name, company, dietary requirements, payment details) is personal data under the GDPR. Only use platforms with a data processing agreement and preferably EU hosting. Automated matchmaking based on profile or behavioural data may be classed as profiling, be transparent and ask for consent. Never put attendee lists into a consumer version of a chatbot.

Source documents

Everything about Kimi Best AI for the events sector

Summarised by the editorial team from provider documentation · not legal advice

Last checked: 1 November 2026 · How we check

Every Friday: what changed in AI for the events sector

New models, prices, oversight and tools, with sources and what it means for you. One email a week, unsubscribe with one click.

View a sample

We only use your address for this newsletter. You confirm first by email.