This Privacy Policy explains what data Meku Bot ("Meku", "the bot", "we") may collect, why it is collected, how it is stored, and how to request deletion. By using Meku features, you acknowledge this policy.
Meku is a multi-purpose Discord bot operated independently. For data requests, contact the official support channel used by this bot distribution.
We only collect data needed to provide bot features. Summary:
| Data | Purpose | Type | Stored where |
|---|---|---|---|
| Discord IDs (user/guild/channel/role/message) | Command execution, permission checks, server scope and feature linking | Required | SQLite databases stores |
| Guild config (prefixes, welcome/farewell config, autoroles, birthday channel) | Server customization and onboarding flows | Feature-based | guilds.db, welcomes.db, autoroles.db |
| Message/command activity metrics (message count, XP, level progress, command usage by day/hour/source) | Leveling systems, anti-spam rewards, analytics and bot health metrics | Required | levels.db and stats stores |
| Server rewind aggregates (messages by user/channel/day, voice duration/session aggregates) | Guild activity summaries and rewind views | Feature-based | data/serverRewindData/*.db |
| Interaction counters (given/received) per interaction type (hug, kiss, pat, etc.) | Social feature stats and profile counters | Required | interactions.db |
| Birthday data (day, month, optional year, timezone, guild mapping) | Birthday reminders and per-guild birthday notifications | Optional | birthdays.db |
| Profile fields (bio, pronouns, country, timezone, personality/MBTI/device, style settings) | Profile card rendering and web profile editor | Feature-based | profiles.db |
| User preferences (language, embedless, silent command mode, notsofurro) | Localization and response behavior preferences | Optional | languagepref.db and profiles-linked preference stores |
| External links (Last.fm username, osu! account link and main mode) | User-requested third-party integrations | Optional | profiles.db and osu link store |
| Economy records (balances, transfers, rewards, charge requests, request reason/status) | Economy features, receipts, and payment-like flow between users | Feature-based | economy.db and economyTransactions.db |
| Marriage system records (partner links, proposal metadata and expiration timestamps) | Social/marriage commands and relationship display | Feature-based | marriages store |
| Furdex records (fursona metadata, likes, image metadata and file paths) | Furdex profile/gallery feature and community interactions | Feature-based | furdex.db and data/furdex/ files |
Data is stored in local sqlite files and bot-managed storage. Access is limited to bot runtime and operators with infrastructure access. Security controls may evolve over time as features change.
All databases containing user data are encrypted at rest using SQLCipher with AES-256-CBC encryption at the page level. Encryption keys are derived via PBKDF2-HMAC-SHA512 with a unique salt and are never stored alongside the database files. Database files are unreadable without the correct key, even with direct filesystem access.
Profile images and uploaded assets are stored in an access-controlled directory on the host server and are only accessible via authenticated API requests.
Retention depends on feature usage and operational needs. Some caches and historical metrics may be pruned automatically (for example usage windows and bot snapshots). Feature datasets can remain stored while the related feature is active. You may request deletion at any time via Delete My Data.
Data is NOT sold. Limited processing can occur through services required for bot operation, such as Discord APIs and optional integrations explicitly used by the user.
We may update this policy when legal, security, or feature requirements change. Continued use after updates means acceptance of the latest version.