Privacy

Privacy Policy

Last updated: 6 August 2026

The short version

HadithBot has no accounts and no tracking. It stores one row per channel you set it up in — the channel and server it posts to, and which hadith it left off at — and nothing else. It cannot read your messages, and it does not know who any of your members are. Run /bismillah stop and that row is deleted.

1. Who this covers

This policy applies to the HadithBot Discord application and to this website. HadithBot is a free, open-source hobby project run by an individual, not a company. You can read every line of the code that handles your data at github.com/SaiyedRushan/HadithBot.

2. What the bot stores

When someone runs /bismillah setup in a channel, one row is saved for that channel. That is the entirety of what HadithBot keeps:

What Why it's needed
Channel ID To know where to post the daily message. This is the only identifier the bot actually keys off.
Channel name Readability only — so rows can be told apart when maintaining the database. Refreshed if you rename the channel.
Server ID and name Readability, and so /bismillah status can list only the channels belonging to your server. Your server's name is never published anywhere unless an admin asks for it to be — see section 6.
Reading position The book, chapter, and hadith number, plus which of the 99 names is next, so each channel picks up where it left off.
Your settings How many hadiths and names to send per day, and whether the channel is currently active.
Timestamps When the row was created and last updated.

None of this is personal data about a member of your server. It describes a channel, not a person.

3. What the bot does not do

4. Where the data lives

Channel rows are stored in a hosted Supabase Postgres database, which acts as the data processor. The bot process itself runs on a private server. Access is limited to the maintainer of the project.

The bot also writes ordinary operational logs (for example, that a daily post to a given channel failed because permissions were missing) so that faults can be diagnosed. These logs are short-lived and are not used for any other purpose.

5. Deleting your data

Run /bismillah stop in a channel and that channel's row is deleted from the database immediately — not flagged, not archived. Deleted.

One thing worth knowing: removing the bot from your server does not by itself delete those rows, because Discord stops telling the bot anything about a server the moment it's kicked. If you want a clean exit, run /bismillah stop in each set-up channel before removing the bot. If you've already removed it and want the rows gone, open an issue on GitHub with your server ID and they will be deleted.

6. This website

This site is a handful of static pages. It sets no cookies, loads no third-party scripts, and runs no analytics. The one thing it saves is your light/dark preference, kept in your own browser's local storage under hb-theme — it never leaves your device and is never sent anywhere.

The home page shows how many servers and channels the bot posts in. Those are plain counts, worked out in advance and written into the page; they identify no server and describe no person.

It also shows a short list of communities using the bot, by name. That list is opt-in only. A server appears there when one of its admins asks for it — through this form — and never merely because the bot is installed. Ask and it comes straight back off.

The site is hosted on Vercel, and the "Add to Discord" button takes you to Discord's own authorization page. Those services will handle your visit under their own privacy policies, which are outside this project's control.

7. Children

HadithBot is not directed at children. Discord's own Terms of Service require users to be at least 13, or older where local law sets a higher minimum age.

8. Changes to this policy

If this policy changes, the date at the top of the page changes with it, and the edit will be visible in the project's public commit history. Continued use of the bot after a change means the updated policy applies.

9. Contact

Questions about privacy, or a request to delete data, go to the GitHub issue tracker. Please don't include anything sensitive in an issue — it's public.