Miku Experimental Privacy Policy

Effective: upon publication

Miku Experimental is an independent Discord application operated by Aiko IT Systems. This page presents the shared confirmed Miku data-practice policy for Miku Experimental. It explains what personal data Miku processes, why it is processed, how long it is kept, when it is shared, and how to request access or deletion.

1. Operator and scope

Controller: Aiko IT Systems. Privacy requests can be sent to privacy@aitsys.dev and support or abuse reports to support@aitsys.dev.

This policy applies when you interact with Miku, are present in a Discord server, channel, or voice channel where Miku is used, or use a related Miku web surface. Server administrators decide whether to install Miku, which permissions to grant, and whether optional server features are enabled. Miku is not operated or endorsed by Discord Inc.; Discord processes data under its own privacy policy.

2. Data Miku processes

Discord account and server data. Miku may process Discord user, guild, channel, role, message, interaction, and application IDs; usernames, display names, avatars, roles, membership state, and voice-channel state when needed for an interaction or enabled server function. The Guild Members privileged intent is used only for operation of Miku’s official support server, including support-server onboarding. Miku does not request the Guild Presences or Message Content privileged intents.

Content you provide. Miku processes commands, interaction options, direct messages or mentions addressed to Miku, search or query text, URLs, names, descriptions, selections, and other content you intentionally submit. Discord may also provide the surrounding metadata needed to respond. Miku does not ask for your Discord password, bot token, access token, or other login credential.

Saved application data. Depending on what you choose to save or what a server administrator configures, Miku may retain user- or guild-scoped settings, named collections, favorites, collaborator and visibility choices, source references and metadata, recent activity or history, timestamps, and the Discord IDs needed to associate those records with the correct user, server, channel, or role.

Voice data. Where Miku’s voice-processing subsystem is enabled by the operator and opted into by a server administrator, audio from users in the connected voice channel is processed in memory to recognize spoken commands. Raw voice audio is not intentionally written to disk or retained as an audio recording by Miku. Recognized text, together with user and guild IDs, may appear in short-lived diagnostic logs. If a configured intent-classification endpoint is enabled, recognized text may be sent to that endpoint; raw audio is not sent to it. Server administrators must inform participants before enabling voice processing and obtain any consent required by law.

Technical data. Operational records may include timestamps, request and connection metadata, command or error context, stack traces, service responses, recent log entries, and an IP address where a web request necessarily exposes it. Error reports may include limited user or server context after available redaction.

3. How and why data is used

We use this data only to respond to users and administrators, provide and remember requested settings or saved content, maintain and recover active sessions, operate support-server onboarding, enforce configured safety controls, prevent abuse, troubleshoot failures, secure Miku, and comply with legal obligations.

Where applicable, processing is based on performing a service requested by you, our legitimate interests in operating and securing Miku, consent where required for an optional feature, or compliance with law. We do not sell Discord data, disclose it to data brokers or advertising networks, use it for targeted advertising or unrelated profiling, or use message or voice content to train machine-learning or AI models.

4. Storage and retention

Live interaction, member, voice, and session data is often held only in memory and is discarded when the operation completes, the connection ends, or the process restarts. Short-lived cache and recovery records generally expire within seconds to several hours; technical cache markers may remain for up to seven days.

Miku keeps two daily rolling local application log files. Diagnostic events sent to Sentry, when enabled, are retained according to Aiko IT Systems’ Sentry account settings. Recognized voice text can appear in those diagnostic records as described above.

Durable settings and user- or guild-scoped saved data are kept while needed to provide the associated function, until deleted through an available control, until the relevant user or server relationship ends and the data is no longer needed, or until a verified deletion request is completed. Messages and other records stored inside Discord remain subject to Discord and the relevant server’s controls. We delete or de-identify data under our control when it is no longer necessary or when Discord or the affected user validly requests deletion, unless a limited legal, security, or abuse-prevention reason requires temporary retention.

5. Sharing and service providers

Data may be shared with Discord to operate the application; with authorized Aiko IT Systems personnel; with Contabo for hosting; with our database, cache, and infrastructure systems; with Sentry for error monitoring; and with configured lookup, processing, or intent-classification services when needed to complete a request. These recipients receive only the data reasonably needed for that purpose. We may also disclose data when required by law or necessary to protect users, Miku, or our legal rights.

Miku’s filesystems are encrypted, administrative access is restricted, and we apply reasonable technical and organizational safeguards. No system is completely secure. Discord and service providers may process data in countries other than yours; where required, we use appropriate safeguards for international transfers.

6. Your choices and privacy rights

You can choose not to interact with Miku, leave a voice channel where voice processing is enabled, ask a server administrator to disable an optional server setting, or ask an administrator to remove Miku. Server administrators can restrict Miku’s permissions and channel access.

To request access, correction, deletion, restriction, portability, or to object to processing, email privacy@aitsys.dev. Include your Discord user ID and, where relevant, the guild ID so we can locate the correct records. Do not send passwords or tokens. We may ask for reasonable proof that you control the account. Subject to applicable law, you may also withdraw consent and complain to a competent data-protection authority.

7. Children, changes, and contact

Miku is not directed to anyone under 13 or below the minimum age required to use Discord in their country. If you believe data relating to an ineligible child has been processed, contact us.

We may update this policy when Miku’s data practices, providers, or legal obligations change. The public version will show its effective date and will be linked from Miku’s Discord application profile or another easily accessible application surface.

Privacy and deletion requests: privacy@aitsys.dev

Support and abuse reports: support@aitsys.dev