Privacy Policy

1. Who We Are

Azra is a Discord bot and web dashboard operated by Bluebell Solutions LLP ("Bluebell", "we", "us", "our"), based in India. This Privacy Policy explains what data we handle when you use the bot or the dashboard, why we handle it, and the choices you have.

Two kinds of data are involved. Your account data — signing in, paying, contacting support — is ours, and we decide how it is used. Server data — everything inside a Discord server — belongs to that server: its owner decides which features and logs are on, and we process that data only to run what the server asked for.

By adding the bot to a server, using the dashboard, or signing in, you acknowledge this policy.

2. Data We Collect

2.1 Discord Account and Sign-In Data

When you sign in with Discord OAuth2 we receive and store:

Your Discord user ID, username and avatar
Your OAuth access token, encrypted at rest and kept only in your server-side session. It is used to list the servers you can manage and is never exposed to another user
The list of servers you can manage, read from that token for dashboard pages
Whether you are Azra staff, based on the internal BOT_OWNER_IDS list

A sign-in session lasts 7 days or until you log out. See the Cookie Policy for the cookies involved.

2.2 Server (Guild) Configuration

When the bot is in a server we store what is needed to run and configure it:

The guild ID, plus its name and icon where a page or log needs to name the server
Settings you save — moderation, logging, Auto Moderation rules, security and raid protection, welcome and goodbye messages, leveling, tickets, forms, giveaways, reaction roles, sticky messages, ghost pings, social notifications, and permission grants
Channel and role metadata fetched from Discord to fill dashboard pickers
Images you upload (server icon, banner, rank-card art). They are posted to Discord with the bot's token, and each upload is recorded in an abuse ledger: guild, uploader, SHA-256 hash, size, file type, and the channel and message it was posted to — so a reported image can be found and removed
Server snapshots — a copy of the server's structure (channels, roles, permissions, settings, emojis, invites, webhooks) used for backup and recovery. Snapshots do not contain messages, tickets or member cases

2.3 Message Content (narrow, and only where a feature needs it)

We do not keep an archive of your chat. Message content is stored in only five narrow exceptions — the thread message archive, deleted images copied into a deletion log, copies of purged messages, ticket transcripts and messages you send the bot directly. Each one is described below, together with whether it is off until a server administrator switches it on, and each is removed with the rest of that server's data if the bot is removed.

2.3.1 Thread message archive (only when deletion logging is enabled)

Discord provides no way to read a message once it has been deleted. So when a server administrator switches on the Message Deleted log, the bot keeps a short-lived copy of messages posted in threads so that a deletion can be logged with what was actually said — which is the entire point of that log. This copy holds the message text, its author's ID and tag, the message, thread and channel IDs, the timestamp, and a summary of any attachments, embeds, links and mentions.

It is off unless the server turns deletion logging on. A server that does not log message deletions has nothing stored.
Threads only — not ordinary channels.
Bot messages are never stored.
A copy is deleted as soon as it is used to write a deletion log, and otherwise expires automatically (see Data Retention).
It is visible only to that server's own log channel and is never shared or used for anything else.

2.3.2 Deleted images in the deletion log (only when deletion logging is enabled)

Discord provides no way to read a message once it has been deleted, and the link behind an image attached to it stops resolving at the same moment. So when a server administrator switches on the Message Deleted log, the bot fetches a deleted image — while the link still works — and re-uploads it into that server's own log message, so the deletion can be logged with what was actually posted rather than with a filename.

It is off unless the server turns deletion logging on. A server that does not log message deletions has nothing downloaded or uploaded for it.
Nothing is stored on our side. The image is held in memory only while the log is being posted; the copy lives in the server's own log channel, under that server's control.
Spoilered images are never copied, because the member marked them as content nobody should see.
Only images are copied — the bot checks the file's actual content, not its name, and a file that is not an image is never re-uploaded.

2.3.3 Purged messages, kept for seven days (only when bulk-delete logging is enabled)

A bulk delete ("purge") can remove up to a hundred messages at once, and Discord provides no way to read or recover them afterwards. So when a server administrator has the Messages Bulk Deleted log on, the bot keeps a copy of what the purge removed — the message text, the author's ID and tag, and when it was sent — which is what the log's View & Restore Log button reads, and what lets a moderator put those messages back.

Seven days, then gone. A sweep deletes these rows once they are seven days old, and they stop being readable — not listed, not restorable — the moment that window ends, whether or not the sweep has run. Restoring a batch does not extend it.
Off unless the server turns it on. A server with the bulk-delete log off has nothing stored for it.
A purge Azra itself performed keeps nothing. When a moderator runs /purge, that action is logged by the command's own card (which names the moderator and the exact command), so there is no second log and no copy of the messages is kept for it.
Text only. A message that was only an image or a file cannot be put back, so it is not stored at all.
Visible only to that server's own staff — the view and the restore both require the Manage Messages permission — and it is never shared or used for anything else.

2.3.4 AI moderation (optional, per-server toggle)

AI moderation is disabled by default and runs only if a server administrator enables it. When it is on, the message text, or the image being checked, is sent to the OpenAI Moderation API in real time for classification. We do not store that content: it is transmitted in real time and only the verdict — whether a rule fired — is kept. Message content is never used to train, fine-tune or evaluate any machine-learning model. OpenAI's handling of data is governed by OpenAI's Privacy Policy.

2.3.5 Ticket transcripts (only for servers that use the ticket system)

When a server uses the ticket system, closing a ticket saves a transcript of that ticket's own channel — the messages, their authors and attachment links — so that server's staff can review a closed conversation afterwards.

That ticket's own channel only — never an ordinary channel, and nothing at all is stored for a server that does not use the ticket system.
On by default for servers that use the ticket system, so a ticket that is opened and then closed has a transcript without the server having to ask for one.
It can be switched off. A server administrator can turn off "Save a transcript on close". With that setting off, a ticket whose channel is only archived saves nothing.
Visible to that server's own staff through a private link that carries its own access token. We open a transcript only to answer a support request or handle an abuse report.
Deleted with the ticket, and removing the bot from a server takes that server's transcripts with it — see Data Retention.

2.3.6 Messages you send the bot directly

If a server owner or administrator sends Azra a direct message, that message and our reply are stored as a conversation, so the team can answer it. Anyone else is not stored — their message is read only to check whether they run a server Azra is in, and they get one automated reply pointing them at our support server.

2.3.7 Can you opt out of message content being tracked?

Yes. Any member can sign in to the dashboard and open Account & privacy to stop Azra storing their message text, and to erase what is already stored. The switch belongs to the person, applies everywhere Azra is, and does not have to be set server by server.

Opting out stops the storage, not the features. Azra still reads a message in the moment to run what a server has switched on — prefix commands, Auto Moderation, leveling, the logs above — and that reading is transient: the content decides what happens next and is then discarded. What changes is that none of it is written to the stores in this section for that member, and a rule that catches their message is still recorded but without its text.

One store is not covered: a ticket transcript, which is that server's own support record rather than a log we keep about a person. A member who wants their content removed from a transcript can ask us, and we handle it as a deletion request under Your Rights. A server that wants no message content retained at all can also turn every store in this section off. Message content is never used to train, fine-tune or evaluate any machine-learning model.

2.4 Tickets, Forms and Support Conversations

Where a server uses these features, we store what the feature needs to work:

Tickets — who opened, claimed and closed a ticket, timestamps, priority and department, and a transcript of the ticket channel (messages, authors and attachment links) so staff can review a closed conversation. A transcript is opened through a private link that carries its own access token
Ticket ratings — the score a member gives, the comment they leave and the staff member rated
Forms — the answers a member submits, which may include anything they choose to type, plus reviewer notes and an anonymous flag
Support inbox — direct messages sent to Azra by a server owner or administrator, kept as a conversation so we can reply. A message from anyone else is answered but not stored
Internal notes, tags and blacklists inside the ticket system

2.5 Moderation and Security Records

Actions taken to keep a server safe are recorded, because that is what an audit trail is:

Moderation cases — warnings, kicks, bans, timeouts, jails, role and channel locks, and the reason, duration, evidence and any DM sent to the member, together with the Discord user IDs of the moderator and the target
Auto Moderation — the rule that fired, the member's ID and tag, the action taken, and a short excerpt of the triggering message (up to 500 characters). The copy-paste filter keeps an excerpt in the same way
Verification — a pending one-time code (which expires within minutes) and operational events such as a failure to assign a role
Raid and bot detection — username, account age, join time, risk score, the signals that produced it, and the action taken
Server recovery — a short-lived cache of a deleted channel, role or ban so it can be restored, and the snapshots described in 2.2

These records are visible to that server's own administrators in the dashboard. When an Auto-Moderation rule catches a message, the record includes the rule that fired and a short excerpt (up to 500 characters) of the message that triggered it, so a moderator can see what was caught. They are never used for advertising or shared with another server.

2.6 Leveling, Giveaways and Community Features

Leveling — XP, level, message, voice-minute and reaction counters, first-seen date, prestige and earned badges
Rank cards — the background and accent colour you choose for your card, and any image you upload for it (see the upload ledger in 2.2)
Giveaways — who entered, bonus entries, winners and backups, prize-claim tickets, and invite tracking (who invited whom, and when they joined)
Reaction roles and sticky messages — which role a member picked and in which channel

2.7 Azra Profiles

A member has an Azra profile, assembled only from the servers that choose to share data with it. It is visible to Azra staff — with every staff view logged — and, where a server has switched sharing on, to that server's own staff:

Verification state — verified, pending, not verified or revoked, with the date and reason
Badges and showcase — milestones earned and the items you choose to display
Server history — for each server: its name, when you joined and left, and whether you are current, left or were removed. It is descriptive of that server only
Staff flags — under review or restricted, with the reason and who set it
Access log — every time staff opened a staff-only part of your profile: who looked, what they saw and when. The point of logging access is that access is never secret

A server owner decides what that server shares with profiles: membership and verification by default, and moderation, activity, roles and support only if switched on. Moderation reasons, staff notes, evidence and ticket contents are never copied into a profile — only counts and dates.

2.8 Analytics and Usage Data

We collect aggregate server metrics to power the analytics dashboard:

Daily and hourly counts of messages, joins, leaves, voice minutes, commands, reactions, threads, channels, roles, emojis and stickers
Daily unique active users — a row of guild, user ID and date, so "how many people were active" can be answered without reading a single message
Feature usage — which module and action ran, whether it succeeded or was blocked, the Discord user ID that ran it, and when. Raw events are kept for 90 days, then only daily totals remain

We do not store the content of individual messages in analytics — only counts and IDs.

2.9 Payment, Billing and Affiliate Data

Payments are processed by Dodo Payments, our merchant of record. We store the Dodo payment and order IDs, amount, currency, plan and duration, payment status (paid, failed, refunded), the server and Discord user it relates to, and a link to the receipt Dodo issues.

We never receive or store your card number, UPI ID, bank account details or other payment instrument data. Those are handled exclusively by Dodo Payments and subject to Dodo Payments' Privacy Policy.

If you join the affiliate programme we also store:

Your affiliate code, the users you referred (by Discord ID), commissions and balance
Your PAN, encrypted at rest, and payout requests including the UPI details you give us — required for Indian tax reporting and TDS

For older Indian GST invoicing we keep the legal name, GSTIN, billing address, state and email supplied at checkout. These are frozen accounting records and are not used for anything else.

2.10 Cookies and Consent Records

The Cookie Policy lists every cookie we set and the choice you are offered. When you are signed in, we also record that choice on our side — your Discord user ID, which groups you allowed, which version of the notice you saw, and when — one row each time your answer changes, so consent can be demonstrated and a withdrawal honoured. Visitors who are not signed in have no such record, because none is needed to respect a choice their browser already holds.

3. How We Use Your Data

Run the bot and dashboard — process commands, apply the settings a server saved, and render its management pages
Sign you in and authorise you — verify who you are and which servers and pages you may open
Apply plans and limits — decide which features are active for a server
Keep an audit trail — let server staff review moderation, security and configuration history, and restore what was wrongly removed
Protect servers and the service — detect raids, nukes, spam and bots, and keep the upload ledger that makes a reported image removable
Answer you — reply to support messages and ticket conversations
Measure the product — aggregate analytics that show what works and what is unused, so we can fix it
Take payment and meet tax duties — create checkouts, confirm settled payments, issue invoices and pay affiliates
Send the notifications you set up — Twitch and YouTube alerts to the channels you chose
Tell you about the service — downtime, security notices and material policy changes

Automated rules can act on a message or a member — deleting a post, timing out an account, stopping a raid. A server administrator chooses and configures those rules, can see every action they take and can undo most of them. We do not use your data to make automated decisions that have a legal or similarly significant effect on you.

4. Legal Bases and Our Role

Where data protection law requires a legal basis, we rely on:

Contract — to provide the bot and dashboard you or your server asked for, including tickets, forms, leveling and support
Legitimate interests — keeping servers and the service safe (moderation, raid and nuke protection, abuse records), understanding how features are used, and improving them. Optional content features are off by default precisely so this interest stays proportionate
Consent — optional cookies and preferences, and the optional AI moderation a server administrator switches on. Consent can be withdrawn at any time
Legal obligation — invoices, tax and accounting records, and responding to lawful requests

Who decides what. For your account, payments, affiliate records and support conversations with us, Bluebell is the controller (a Data Fiduciary under India's Digital Personal Data Protection Act, 2023). For data inside a Discord server — its settings, member records, tickets, forms and logs — that server's owner is the controller and we act as a processor (a Data Processor), handling it only on the server's instructions and for the features it enables.

We share data only with the following parties, and only as needed to deliver the service:

Recipient	Purpose	Data Shared
Discord	Running the bot, posting messages and logs, OAuth2 sign-in, image delivery	Bot token, your access token (through Discord's own API), and the server IDs, channel IDs and content a requested action needs
Dodo Payments	Payment processing, subscriptions, invoices, refunds and tax as merchant of record	Order amount, currency, plan, payment status and the billing details Dodo requires. All card, UPI and bank data is handled by Dodo, never by us
OpenAI	AI content moderation (optional, per-server toggle)	The message text or image being classified — only when AI moderation is enabled for that server
Twitch / YouTube	Polling for live and upload events to trigger notifications	The username or channel ID you configured. No viewer data
Hosting and database providers	Storing and serving the data described in this policy	The data described in this policy, under contract and access-controlled
Authorities	Responding to a lawful request, or protecting a person's safety	Only what the request legally requires. We tell you unless we are prohibited from doing so

We do not sell your data, share it with advertisers or data brokers, or disclose it to any other third party. Data from one server is never shown to another server's staff.

6. Where Your Data Is Stored

Data is held on the servers and managed databases we use to run Azra, in whichever regions those providers operate. That may mean your data is processed outside the country you live in. Where that happens, we rely on the provider's contractual safeguards and keep the data limited to what this policy describes. Our security measures are summarised in Security.

Server data stays under that server's control: its owner can change or delete settings, and removing the bot starts the deletion timeline in Data Retention.

7. Data Retention

We keep data only as long as it is needed for the purpose it was collected for, or as long as the law requires.

Data Type	Retention Period
Sign-in session and its encrypted access token	7 days, or immediately when you log out
Guild configuration, settings and saved content	While the bot is in the server; then 6 months after it is removed (in case it is re-added), after which it is purged — or immediately on deletion request
Moderation cases, warnings, blacklists and notes	While the server keeps Azra, or until the server deletes them
Auto-Moderation detections (the rule and a short excerpt of the message that triggered it)	With that server's moderation records — see above
Raid, bot-detection and verification records	While the server keeps Azra; pending verification codes expire within minutes
Ticket transcripts (only for servers that save them on close)	Until the server deletes the ticket, or 6 months after the bot is removed, or on deletion request
Ticket ratings, form answers and giveaway entries	Until the server deletes them or removes Azra
Levels, badges and rank-card settings	While the server keeps Azra, or until the member or server asks for deletion
Azra profile, badges and server history	Until you ask us to delete your account data
Profile access log (staff views)	Kept as an accountability record while the profile exists
Messages sent to the bot's direct-message inbox by a server owner or administrator	Until deleted, or on deletion request
Thread message archive (only if deletion logging is enabled)	14 days rolling, or immediately once used to write a deletion log — whichever comes first
Deleted images copied into a deletion log	Not retained by us — held in memory only while the log is posted
Copies of bulk-deleted ("purged") messages	7 days from the purge, then deleted automatically and permanently
Analytics totals (daily, hourly, per-channel)	While the server keeps Azra
Raw feature-usage events	90 days, then only daily totals remain
Upload ledger (hash of every dashboard image posted)	Kept as the takedown record, even after the server removes Azra
Payment, invoice and tax records	As long as tax and accounting law requires; kept even after the bot leaves a server
Affiliate records, including PAN and payout details	As long as tax law requires after the last payout
Consent records	As long as needed to demonstrate the choice you made
Admin audit log	Indefinitely

When the bot is removed from a server, that server's stored data is purged 6 months later if the bot has not been re-added. The server's own record, subscription history and payment records are kept for accounting and tax, and our internal admin audit log is kept as a record of our own staff's actions.

8. Security

We use reasonable technical and organisational measures to protect your data: HTTPS-only transport, parameterised database queries (no raw SQL interpolation), server-side sessions, encrypted OAuth tokens and encrypted affiliate PAN data, CSRF protection on dashboard actions, and access limited to the staff who need it. Staff views of staff-only profile data are logged.

No system is perfectly secure and we cannot guarantee absolute security. If a breach affects your personal data, we will notify the relevant authority and affected users as required by law.

9. Your Rights

Subject to applicable law, you may ask us to:

Access — confirm what data we hold about you and give you a copy
Correct — fix data that is inaccurate or incomplete
Erase — delete your account data, profile and support conversations
Port — give you your data in a machine-readable format
Withdraw consent — at any time, for optional cookies and preferences
Opt out of message content — sign in to the dashboard and open Account & privacy to stop us storing your message text, and to erase what is already stored (see §2.3.7)
Object or restrict — ask us to stop a use based on legitimate interests, or limit what we do with the data
Complain — to us first, and then to your data protection authority

Email [email protected] from the account you are asking about, or tell us your Discord user ID. We may ask you to verify control of that account before acting, and we respond within 30 days.

Some requests have limits. If the data sits inside a server you do not own, that server's owner is the controller and we will pass the request on or help you reach them; moderation records a server is entitled to keep may stay with that server. We may also keep what tax law, fraud prevention or a legal claim requires, and we will tell you what was kept and why.

Grievance redressal. If you are not satisfied with our answer, write to our Grievance Officer at [email protected] with "Grievance" in the subject. If that does not resolve it, you may complain to the Data Protection Board of India or your local supervisory authority.

10. Children's Privacy

Azra is not directed at children under the age of 13, and Discord's own Terms of Service require users to be at least 13 (or older where local law says so). We do not knowingly collect data from children under that age. If you believe a child has provided us with personal data, contact us and we will delete it.

11. Changes to This Policy

We may update this Privacy Policy as the service changes. When we do, we update the effective date at the top of this page. For material changes we may also notify you in the dashboard or in our support server. Continued use of Azra after a change is posted means you accept the revised policy.

12. Contact Us

Questions about this Privacy Policy, or a request about your data:
Bluebell Solutions LLP
Privacy and data requests: [email protected]
Content and abuse reports: [email protected]
Security vulnerabilities: [email protected]