Privacy Policy
Maktabah Wasatiyyah · maktabahwasatiyyah.org
Last updated: 16 November 2026
At a glance
- This website does not track you. There is no analytics, no advertising, no tracking cookies, no social media buttons, no embedded videos, no newsletter and no contact form. To use the website you need a reading account, with no email address and no password (section 9B). Only this privacy page can be read without one.
- Comments and likes are optional. If you post a comment, your text, the name you choose (or none) and the time are published. To prevent abuse, a one-way code made from your IP address is stored with your likes and reports, and for up to an hour to count your comments (section 9A).
- Apart from comments and reading accounts you choose to use, the only personal data processed is the technical data every web server needs to deliver a page: mainly your IP address, the time, the page requested and your browser type. Our hosting provider, Netlify, records this automatically and deletes it after a short time (Netlify has stated: less than 30 days).
- Your settings and reading progress stay on your device. The site remembers your theme and where you stopped reading in your own browser. None of it is sent to us or to anyone else, except your Corpus reading progress, which is kept in your reading account so that it is on all your devices (section 9B).
- Nothing is loaded from other companies. All fonts, pictures and scripts come from this website itself.
- No cookie banner is shown, because the site uses no cookies that would require your consent.
- You can delete everything the site stored in your browser at any time (section 7.5).
The rest of this page explains each of these points in detail, together with the legal basis, your rights and answers to common questions.
Contents
- About this policy
- Who is responsible
- Words used in this policy
- What happens when you visit a website
- Overview: what is and is not processed
- Hosting and server log files
- What the website stores in your own browser
- Cookies
- Features that run entirely in your browser
9A. Comments and likes
9B. Reading accounts
- What we deliberately do not use
- Links to other websites
- Sharing, saving and screenshots
- Transfers outside the European Union
- Security
- How long data is kept
- Automated decisions and profiling
- Children
- Your rights
- Complaints to a supervisory authority
- Is providing data required?
- If something goes wrong
- Changes to this policy
- Frequently asked questions
- Legal references
1. About this policy
1.1 Why this page exists
Maktabah Wasatiyyah is a library of short studies in fiqh and related subjects, with every quotation given in Arabic and English and traced to its volume and page. Just as we try to show readers exactly where every quotation comes from, we want to show visitors exactly what happens to information about them when they read our pages.
The law also requires it. The European Union's General Data Protection Regulation (GDPR) obliges anyone who runs a website in the EU to tell visitors what personal data is processed, why, on what legal basis, for how long, who receives it and what rights visitors have. German law adds rules about storing information on visitors' devices. This page fulfils those obligations.
1.2 How this policy is written
Privacy policies are often long documents written in legal language that few people read. We have tried to do the opposite: to describe in plain English what really happens, to name every item the website stores, and to explain technical terms when they first appear. Where the law requires a precise reference, such as an article of the GDPR, we give it, and section 24 lists all of them in one place.
Where something does not happen on this website, we say so explicitly. Many visitors are used to websites that track them, and it is useful to know that this one does not.
1.3 What this policy covers
This policy applies to the website maktabahwasatiyyah.org, including all its sections: Home, Booklets, Compendium, Index, the ʿAwra Map and Scans, as well as the individual booklet pages.
It does not apply to other websites that we link to, such as Shamela, TikTok or Instagram, or to our accounts on social media platforms. Those are governed by the privacy policies of the companies that run them (section 11).
1.4 Who this policy is for
This policy is written for everyone who visits the website, wherever they are. Because Maktabah Wasatiyyah is run from within the European Union, the GDPR applies, and the rights it gives (section 18) are available to all visitors.
2. Who is responsible
The controller responsible for this website within the meaning of Article 4(7) GDPR is:
Maktabah Wasatiyyah
Website: maktabahwasatiyyah.org
You can reach Maktabah Wasatiyyah through the TikTok and Instagram accounts linked on this website.
We have not appointed a data protection officer. The law requires one only for organisations that process personal data on a large scale or as a core activity, or that employ a certain number of people in data processing; none of this applies to this website.
3. Words used in this policy
The following terms appear throughout this policy. They follow the definitions in Article 4 GDPR, explained in everyday language.
Personal data. Any information relating to an identified or identifiable natural person. This includes obvious information such as a name, but also information that could identify someone only in combination with other information, such as an IP address. The European Court of Justice has confirmed that IP addresses can be personal data, so we treat them as such.
Processing. Anything done with personal data, whether automated or not: collecting, recording, organising, storing, adapting, retrieving, consulting, using, transmitting, combining, restricting, erasing or destroying it.
Controller. The person or organisation that decides why and how personal data is processed. For this website, that is Maktabah Wasatiyyah.
Processor. A person or company that processes personal data on behalf of the controller and only according to the controller's instructions. For this website, that is our hosting provider, Netlify.
Recipient. Anyone to whom personal data is disclosed. On this website, the only recipient of personal data is Netlify as our processor. Comments you post are also published, so anyone visiting the site can read them.
Third country. A country outside the European Union and the European Economic Area. The United States, where Netlify is based, is a third country.
IP address. A number that identifies a device on the internet at a particular moment, comparable to a postal address for data. Your internet provider assigns it to you; it often changes, and many people share one address (for example, everyone on the same home or office network). Without an IP address, a server would not know where to send the page you requested.
User agent. A short description your browser sends with every request, for example "Safari 18 on iOS". It tells the server what kind of browser and device it is talking to, so that the page can be delivered in a suitable form.
Referrer. The address of the page you were on when you clicked a link to our website. Browsers often send it automatically, sometimes only the domain name.
Cookie. A small text file that a website places in your browser and that your browser then sends back to that website with every request. Cookies are commonly used to recognise returning visitors and, by advertising companies, to follow people across websites.
Local storage. A small storage area inside your browser where a website can keep notes and read them back later. Unlike cookies, the contents of local storage are not sent to the website with each request; they stay on your device unless a script on the website deliberately sends them somewhere. This website never does.
IndexedDB. A larger storage area built into every modern browser, used here by Scans to keep books you add yourself. Like local storage, it stays on your device.
Server log / access log. A record that a web server keeps automatically of the requests it receives: which file was requested, when, from which IP address and with which browser.
Content delivery network (CDN). A network of servers in many countries that keep copies of a website, so that each visitor is served from a server near them and pages load quickly.
4. What happens when you visit a website
To understand what data is processed and why, it helps to know what happens technically when you open a page.
4.1 The request
When you type maktabahwasatiyyah.org or tap a link to it, your browser first looks up which server is responsible for that name. It then sends that server a request: a short message saying, in effect, "please send me the page at this address". Every request automatically contains your IP address (so the server knows where to send the answer), the address of the page you want, the time, and usually your browser type and the page you came from.
4.2 The response
The server sends back the page itself, written in HTML. Your browser reads it and sees that it also needs other files: the design (CSS), the program that makes the page interactive (JavaScript), fonts and pictures. For each of these, it sends a further request. A single visit to the home page therefore involves around a dozen requests, all to our own website.
4.3 Why the server must see your IP address
This exchange cannot happen without your IP address, in the same way that a letter cannot be answered without a return address. Every website in the world receives the IP addresses of its visitors for this reason. What matters for your privacy is what happens with that information afterwards: whether it is stored, for how long, whether it is combined with other data and whether it is shared. Sections 6 and 15 answer these questions for this website.
4.4 Where trackers usually come in
On many websites, the page also contains code from other companies: analytics services, advertising networks, social media buttons, embedded videos or fonts loaded from external servers. Each of these makes your browser send requests to those companies too, often with cookies that let them recognise you across many websites. This website contains none of that (section 10). Every request your browser makes while you are on our pages goes to our own website and nowhere else.
5. Overview: what is and is not processed
| What | Happens on this site? | Where it goes | Details |
|---|---|---|---|
| Server access logs (IP address, time, page, browser) | Yes, automatically, on every visit | Our hosting provider, Netlify | Section 6 |
| Cookies | No (one temporary exception while the site is password-protected) | — | Section 8 |
| Analytics or visitor tracking | No | — | Section 10 |
| Advertising or advertising networks | No | — | Section 10 |
| Fonts, scripts or pictures from other companies | No: everything comes from this website | — | Sections 9, 10 |
| Embedded content (videos, posts, maps) | No | — | Section 10 |
| Social media buttons that report to their owners | No: only plain links | — | Section 11 |
| Theme and reading progress | Yes, in your own browser | Stays on your device; Corpus progress is also kept in your reading account if you create one | Sections 7, 9B |
| Books you add to Scans, pictures you check | Yes, in your own browser only | Stays on your device | Section 7 |
| Search | Yes, inside your browser | Stays on your device | Section 9 |
| Share cards | Made inside your browser | Only where you choose to send them | Sections 9, 12 |
| Comments, likes and reports you choose to make | Only if you use them | Netlify Blobs (our host's storage), published as described | Section 9A |
| Optional reading account in the Corpus | Only if you create one | Netlify Blobs (our host's storage) | Section 9B |
| Contact forms, newsletters | None exist | — | Section 10 |
| Selling, renting or trading data | Never | — | — |
6. Hosting and server log files
6.1 Who hosts the website
This website is hosted by Netlify, Inc., San Francisco, California, USA ("Netlify"). Netlify stores the website's files and delivers them through its worldwide content delivery network, so that visitors in Europe, the Middle East, Asia or the Americas are each served from a server close to them.
We chose a static website, meaning that every page is prepared in advance and delivered as a finished file, rather than one built anew from a database for every visitor. Apart from being fast and secure, this means there is no database of visitors and no login system. The only server program is a small one for comments and likes (section 9A); it stores nothing about you unless you use them.
6.2 What is collected
Whenever your browser requests a file from this website, Netlify's servers automatically record technical information in server access logs. This typically includes:
- your IP address;
- the date and time of the request;
- the address of the file requested, for example
/booklets/niqabor/img/covers/niqab.webp; - the result of the request, for example whether the file was found, and the amount of data transferred;
- the referrer, meaning the website you came from, if your browser sends it;
- the user agent, meaning your browser and operating system, for example "Chrome on Android";
- the approximate country, derived from the IP address.
A single log entry might, in simplified form, read: "203.0.113.24 — 12 Nov 2026, 14:03:11 — /booklets/awra — found — 41 KB — from tiktok.com — Safari on iOS — Germany." There is no name, no email address and nothing that tells us who you are.
6.3 Why this is processed
These logs serve four purposes:
- Delivering the website. The server must know where to send each page.
- Keeping it running. Logs show whether pages are being delivered correctly and help find errors, such as a link that leads nowhere.
- Security. Logs make it possible to recognise and block attacks and misuse, such as floods of requests meant to overload the site, or attempts to find weaknesses.
- General understanding of use. In aggregated form, logs show how much the site is read and which pages are visited, which helps us decide which subjects to write about.
6.4 Legal basis
The legal basis is Article 6(1)(f) GDPR (legitimate interests). Our legitimate interest, and Netlify's, lies in delivering the website securely, reliably and efficiently, and in understanding in general terms whether it is working and being read.
We have weighed this interest against your interests and rights. We consider that our interest prevails, because:
- the data is purely technical and does not reveal who you are without further information that we do not have and do not seek;
- it is processed only as far as necessary and kept only briefly;
- it is not combined with other data, not used for advertising and not used to build profiles;
- processing of this kind is expected by every internet user, since no website can be delivered without it.
You have the right to object to this processing (section 18.6).
6.5 What we do and do not do with it
The person running Maktabah Wasatiyyah can view recent request information in Netlify's dashboard, for example how many requests a page received or which browsers and operating systems visitors use. We use this only to understand, in general terms, whether the site is working and being read.
We do not:
- combine log data with any other data;
- try to identify individual visitors;
- export, download, copy or keep the logs outside Netlify;
- pass log data to anyone else;
- use it for advertising, marketing or profiling.
6.6 How long it is kept
Netlify keeps server logs for a limited time and then deletes them automatically. Netlify has stated that access logs containing IP addresses are kept for less than 30 days. We keep no copies of our own.
6.7 Netlify as processor
Netlify processes this data on our behalf as a processor under Article 28 GDPR. Netlify's terms of service include a Data Processing Agreement, which obliges Netlify in particular:
- to process the data only on our documented instructions;
- to ensure that people with access are bound to confidentiality;
- to take appropriate technical and organisational security measures;
- to use further sub-processors only under equivalent obligations;
- to help us respond to requests from visitors exercising their rights;
- to delete or return the data at the end of the service.
6.8 Can you avoid it?
The processing described in this section is necessary to show you the website and cannot be switched off from within the site. If you prefer that your own IP address does not reach our hosting provider, you can use a VPN or a similar service; our server will then see the address of that service instead.
7. What the website stores in your own browser
7.1 Why the website stores anything
Some conveniences need the website to remember something between visits: that you prefer the dark theme, where you stopped reading a booklet, or that you have already seen a short tip. Instead of keeping this information on our side, which would require recognising you, the website keeps it in your own browser, where only you can reach it.
7.2 How it works
The website uses two storage areas built into your browser:
- local storage, for small notes such as your theme and reading positions; and
- IndexedDB, used only by Scans, for books you add yourself.
Everything stored this way:
- stays only on your device, in the browser you used;
- is never sent to us, to Netlify or to anyone else;
- contains no identifier that could recognise you, on this website or any other;
- is not visible to other websites;
- can be deleted by you at any time (section 7.5).
The one exception: if you create a reading account in the Corpus (section 9B), your Corpus reading progress (mw_corpus) is also sent to that account, so that it is kept on your other devices.
We never see any of it. We could not tell you what is stored in your browser even if you asked, because it never reaches us. The one item you write yourself, the name you use for comments (mw_name), is sent only when you post a comment, as part of that comment (section 9A). If you use a different browser or device, the website will not know your settings there.
7.3 What exactly is stored
On the main site
| Name | What it holds | Why | Example |
|---|---|---|---|
mw_theme | light or dark | So the site opens in the colour theme you chose | dark |
mw_read | For each booklet you opened, how far down you have read, as a number between 0 and 1, and which booklet you read last | So "Continue reading" can take you back to where you stopped | {"pos":{"niqab":0.42},"last":"niqab"} |
mw_hint | Whether the short reading tip has already been shown | So the tip ("Tap a number for its source…") appears only once | 1 |
mw_notice | Whether you closed the short privacy note on your first visit | So the note appears only once | 1 |
mw_name | The name you last wrote above a comment, if any | So you do not have to type it again | Maryam |
In the Corpus (the library)
| Name | What it holds | Why | Example |
|---|---|---|---|
mw_corpus | For each book you read: when you started, how many words of each page have counted, when you finished, and books you marked "Read before" | So your progress, points, levels and Finished shelf work | {"v":1,"b":{"g1656":{"s":1763200000000,"c":{"0":290},"f":1763210000000}}} |
mw_corpus_recent | The books you opened last and where you were in them | So "Continue reading" can take you back | [{"id":"g1656","f":0.4}] |
mw_acc | Only if you signed in to a reading account: its username, its login code and when it last synced | So this device stays signed in (section 9B) | {"name":"reader_1","code":"…","synced":1763210000000} |
mw_acc_seen | Whether the account welcome box has been answered | So it appears only once | 1 |
In Scans (the citation-scan tool)
| Name | What it holds | Why |
|---|---|---|
sw_theme | light or dark | Your colour theme inside Scans |
sw_colors | The highlighter colours you picked | So your colours are kept |
sw_page_… | The page you last had open in each volume | So a volume opens where you left it |
sw_count, sw_studio_spp | Settings for how pages are shown and prepared | So your layout choices are kept |
sw_tour | Whether you have seen the quick tour | So the tour is not shown again |
IndexedDB database mw-scans | Books you add yourself with "Add a book": their page images and titles | So your own books stay available in your browser |
When you use "Check a scan" in Scans, the picture you choose is opened and read inside your browser only. It is not uploaded anywhere and not stored.
None of these entries contains your name, your IP address, a unique number identifying you, or any information about other websites you visit. The only exception is mw_acc, which exists only if you sign in to a reading account, and holds the username you chose and your login code. Signing out removes it.
7.4 Legal basis
Storing information on your device, and reading it back, is governed in Germany by § 25 of the Telecommunications Digital Services Data Protection Act (TDDDG), which implements the EU's ePrivacy Directive. As a rule, it requires consent, with an exception in § 25(2) no. 2 TDDDG for storage that is strictly necessary to provide a service the user has explicitly asked for.
Everything listed in section 7.3 falls under this exception: it exists only to provide functions you actively use (your chosen theme, continuing where you stopped, not seeing the same tip or note twice, not retyping your name above comments, your own work in Scans), and none of it serves any other purpose. That is why the website does not ask for consent and shows no banner.
To the extent that any of this information counts as personal data at all, its use is based on Article 6(1)(f) GDPR, our legitimate interest in offering these conveniences. As the data never leaves your device (except Corpus reading progress you choose to keep in a reading account, section 9B), no one but you has access to it.
7.5 How to see and delete it
You can remove everything this website stored in your browser at any time:
- Chrome: Settings → Privacy and security → Third-party cookies / Site data (or "Site settings" → "View permissions and data stored across sites") → search for maktabahwasatiyyah.org → Delete;
- Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data → See all cookies and site data → search for maktabahwasatiyyah.org → Delete;
- Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → select maktabahwasatiyyah.org → Remove Selected;
- Safari on Mac: Settings → Privacy → Manage Website Data → select maktabahwasatiyyah.org → Remove;
- Safari on iPhone or iPad: Settings app → Safari → Advanced → Website Data → swipe left on maktabahwasatiyyah.org → Delete.
If you want to see exactly what is stored, desktop browsers show it in their developer tools (usually opened with F12), under "Application" or "Storage" → "Local Storage" and "IndexedDB".
Private or incognito windows delete all of this automatically when they are closed. Deleting it only resets your theme, reading positions, Scans books and the name you used for comments; it has no other effect. It does not delete comments you have posted (section 9A.6).
8. Cookies
8.1 No cookies
This website does not set any cookies of its own: not for analytics, not for advertising, not for recognising returning visitors and not for anything else. The settings the site remembers are kept in local storage instead (section 7), which is not sent to any server.
8.2 The temporary exception
While the website is protected by a password during its preparation, our hosting provider Netlify may set a technically necessary cookie after you enter the password, so that you do not have to enter it again on every page. This cookie:
- contains no information about you beyond the fact that the correct password was entered;
- is used only by Netlify, only for this purpose;
- is permitted without consent under § 25(2) no. 2 TDDDG, as it is strictly necessary to give you access you asked for.
Once the password protection is removed and the site is open to everyone, this cookie is no longer set.
8.3 Why there is no cookie banner
Cookie banners are required when a website wants to store information on visitors' devices that is not strictly necessary, typically for analytics or advertising. Because this website stores nothing of that kind, there is nothing to ask consent for, and therefore no banner. If this ever changes, the website will ask for your consent first, before anything is stored, and this policy will be updated (section 22).
9. Features that run entirely in your browser
Many websites send what you do to their servers: what you search for, what you click, how long you read. On this website, the interactive features work inside your browser, using information that has already been loaded with the page. Comments and likes are the only exception (section 9A).
Search. When you search for a question, term or scholar, the search runs inside your browser on data the site has already loaded. Your search words are not sent to us, to Netlify or to any search engine, and they are not stored.
Reading booklets. Moving between sections, changing the text size and following the table of contents all happen in your browser. Your reading position is kept only in your own browser (section 7).
Footnotes and the source panel. Opening a footnote shows the original Arabic, the translation and the reference, all of which are already part of the page. Nothing is sent when you open one.
Index terms. Tapping a dotted term shows its meaning from information already loaded. Nothing is sent.
The Compendium. Choosing a subject and searching passages happens inside your browser.
The ʿAwra Map. When you tap a part of the figure, your browser works out which part it is, from the colours of the picture itself, and shows the ruling and its proof. Nothing you tap is recorded or sent.
Share cards. When you select words in a booklet, or an answer on the ʿAwra Map, and choose "Share as a card", the picture is drawn inside your browser. Nothing about it is sent to us (section 12).
Quote of the day. The quote shown is chosen inside your browser from your device's own date, from a list delivered with the page. Nothing is sent.
Dark theme. Switching between light and dark happens in your browser, which remembers your choice locally (section 7).
Scans. Turning pages, highlighting, adding your own books and checking a scan all happen inside your browser (section 7).
Fonts and pictures. All fonts, pictures, icons and scripts are delivered from this website itself.
9A. Comments and likes
9A.1 What happens when you comment, like or report
Under booklets and articles, under Compendium passages and on the quote of the day, you can like the text, write a comment, reply to comments, like comments and report a comment you think is inappropriate. All of this is optional.
When you post a comment, the following is stored and published on the website for everyone to read:
- the text you wrote;
- the name you entered, or "Anonymous" if you left it empty;
- the date and time;
- which booklet, passage or quote it belongs to, and which comment it replies to.
Please do not write anything in a comment that you do not want to be public, such as your full name, address or phone number.
9A.2 The visitor code
To make sure each person can like something only once, to count reports from different people, and to stop floods of comments (at most 20 per hour), the website stores a visitor code with every like and report, and for up to an hour with a mark that counts your comments. It is made from your IP address with a one-way calculation (HMAC-SHA-256) using a secret random value. Your IP address itself is not stored, the code is not published and it is not stored with your comment. It is a pseudonym: we never try to link it back to an address.
9A.3 Where it is stored
Comments, likes, reports and visitor codes are stored in Netlify Blobs, the storage service of our hosting provider Netlify (section 6), which processes them on our behalf under the same Data Processing Agreement (section 6.7) and the same safeguards for transfers to the United States (section 13).
9A.4 Legal basis
Publishing your comment is based on Article 6(1)(f) GDPR: our legitimate interest in offering readers a place to discuss the texts, and your own interest in taking part, which you show by choosing to post. The visitor code is based on Article 6(1)(f) GDPR: our legitimate interest in preventing duplicate likes, abuse and spam, with as little data as possible.
9A.5 Moderation
Comments appear immediately. A comment reported by two different visitors is hidden until it has been checked. Maktabah Wasatiyyah can keep it, which shows it again, or delete it. We may also delete comments that break the law or are abusive, spam or off-topic.
9A.6 How long it is kept
Comments, likes and reports are kept until they are deleted by us, or at your request. Rate-limit marks are deleted once the hour is over.
To have a comment of yours removed, press Report on it and reply to it that you want it removed. Reported comments are shown to us first, and we will delete it. You can also contact us (section 2).
9B. Reading accounts
9B.1 What an account is for
Every page of this website, except this privacy page, needs a reading account. The account also keeps your Corpus reading progress, points and levels on all your devices, so they are not lost when your browser data is cleared.
9B.2 What you give and what is stored
You choose a username (3 to 20 letters, numbers or underscores). The website then gives you a login code of 32 characters. There is no email address and no password, and nothing else is asked.
On the server we store:
- your username;
- a one-way fingerprint of your login code (SHA-256), never the code itself;
- the date the account was made and when it last synced;
- your reading progress in the Corpus: for each book, when you started, how many words of each page have counted, when you finished, and books you marked "Read before";
- a sign-up log entry: your username and the exact time the account was made (section 9B.6).
We do not store your IP address, an email address, your name or anything about your device with the account. Other readers never see your username or your progress.
9B.3 Limits on attempts
To stop people from guessing usernames and codes, the number of sign-ups and wrong codes is limited per hour. For this, the same one-way visitor code as for comments (section 9A.2) is written for up to an hour, with a mark that counts the attempts. It is not stored with your account, and the marks are deleted once the hour is over. When an account is made, the form also checks that it was filled in by a person: it has a hidden field that only automated programs fill in, and it measures how long the form was open. Neither is stored.
9B.4 Where it is stored
Accounts are stored in Netlify Blobs, the storage service of our hosting provider Netlify (section 6), which processes them on our behalf under the same Data Processing Agreement (section 6.7) and the same safeguards for transfers to the United States (section 13).
9B.5 Legal basis
The account is based on Article 6(1)(b) GDPR: you ask for it, and we need the data above to provide it. The limits on attempts are based on Article 6(1)(f) GDPR: our legitimate interest in keeping accounts safe, with as little data as possible. The sign-up log is based on Article 6(1)(f) GDPR: our legitimate interest in keeping the website safe from automated sign-ups.
9B.6 Your code, signing out and deleting
Your login code is the only way back into your account. Because there is no email address, a lost code cannot be recovered. On a signed-in device you can show your code again, or make a new one (the old code then stops working). Sign out removes the account from that device. Delete my account removes the account and its synced progress from our storage at once and for good. Its entry in the sign-up log (your username and when the account was made) is kept for 12 months after the deletion, to spot automated sign-ups, and is then deleted automatically. The progress kept in your own browser stays until you clear it.
9B.7 How long it is kept
An account is kept until you delete it. Its sign-up log entry is kept while the account exists and for 12 months after it is deleted. Rate-limit marks are deleted once the hour is over.
10. What we deliberately do not use
Many websites use services from other companies that collect data about their visitors. We have chosen not to use any of them. For clarity, here is what this website does not contain:
Analytics services. No Google Analytics, no Matomo, no Plausible, no Facebook Pixel, no "heatmaps" and no session recording. Nobody records how you move through the site, what you click or how long you stay.
Advertising. No advertisements and no advertising networks. Nothing on this website is paid for by advertisers, and no advertising company receives any information about you from us.
Externally loaded fonts. Many websites load their fonts from Google Fonts or similar services, which tells those companies your IP address and the website you are visiting. All fonts on this website are stored on and delivered from this website itself.
Embedded content. No embedded YouTube or TikTok videos, Instagram posts, maps or other content that would load from other companies' servers as soon as you open a page.
Social media plugins. No "Like", "Follow" or "Share" buttons supplied by social networks, which would report your visit to those networks. The links to our TikTok and Instagram accounts are ordinary links (section 11).
Contact forms and newsletters. The website has neither. It never asks for your email address. Comments are the only place you can write anything for others to see, and a name there is optional (section 9A). The only account is the optional reading account in the Corpus, which needs no email address and no password (section 9B).
Payment. The website sells nothing and takes no payments.
Third-party scripts of any kind. The website's security settings (section 14) instruct your browser to refuse any script that does not come from this website itself.
11. Links to other websites
The website contains ordinary links to other websites. The most important are:
Shamela (shamela.ws). Footnotes and the source panel link to the Shamela digital library, so that you can read the original Arabic source in its context. Shamela is an independent library and is not connected to us.
TikTok. Links lead to the Maktabah Wasatiyyah account on TikTok, operated by TikTok Technology Limited and its affiliates.
Instagram. Links lead to the Maktabah Wasatiyyah account on Instagram, operated by Meta Platforms Ireland Limited.
These are plain links. Viewing our pages sends nothing to these websites; they cannot see that you are on our site. Only when you click a link do you leave our website and connect to theirs. From that moment, the other website's own privacy policy applies. It will receive your IP address and may, for TikTok and Instagram, recognise you if you are logged in to them. It may also learn, through the referrer, that you came from our website.
We have no influence on what these websites do with your data and accept no responsibility for it. We recommend reading their privacy policies before using them.
12. Sharing, saving and screenshots
12.1 Share cards
Share cards are pictures of a quotation, with its source and a QR code leading back to this website. They are created entirely inside your browser.
- If you press Share, your device's own share menu opens, in the same way as when you share a photo. The picture is then sent only where you choose, for example to a chat or a social media app, and is subject to the privacy terms of that app. We receive nothing and do not learn that you shared anything.
- If you press Save picture, the picture is saved to your device.
12.2 Sharing links
When you share a link to this website, for example in a chat, the app you use may load a preview: the page title, a short description and a preview picture. To do this, the app's servers request the page from our website, and those requests appear in Netlify's server logs (section 6) like any other. We do not learn who shared the link or with whom.
12.3 QR codes
The QR codes on our printed booklets and share cards contain only the address of a page on this website. Scanning one simply opens that page. The codes contain no information about you and do not tell us who scanned them.
13. Transfers outside the European Union
13.1 Why data leaves the EU
Netlify is a company based in the United States, and its content delivery network has servers in many countries. Server log data (section 6), and comments, likes and visitor codes (section 9A), may therefore be processed outside the European Union, including in the United States.
13.2 Why this is permitted
Under the GDPR, personal data may be transferred to a third country only if adequate protection is ensured. For the transfer to Netlify, this is ensured in two ways:
- Adequacy decision. Netlify is a certified participant in the EU-U.S. Data Privacy Framework. On 10 July 2023, the European Commission decided that the United States ensures an adequate level of protection for personal data transferred to companies certified under this framework (Article 45 GDPR). You can check Netlify's certification on the official list at dataprivacyframework.gov.
- Standard Contractual Clauses. Netlify's Data Processing Agreement additionally includes the Standard Contractual Clauses adopted by the European Commission (Article 46(2)(c) GDPR), which oblige Netlify by contract to protect the data to EU standards.
13.3 What remains on your device
Data stored in your browser (section 7) never leaves your device, so no transfer of it takes place at all. The one exception is Corpus reading progress kept in a reading account you chose to create (section 9B), which is stored with Netlify like comments (section 13.1).
14. Security
We protect the website and your connection to it with the following measures:
Encryption (HTTPS). Every page and file is delivered over an encrypted connection, so that no one between you and the server (for example on a public Wi-Fi network) can read or change what you see.
Always encrypted (HSTS). The website instructs browsers to always use the encrypted connection, even if someone types or follows an unencrypted address.
Content Security Policy. The website tells your browser exactly which sources it may load scripts, fonts, pictures and other content from: only this website itself. If anyone ever managed to slip foreign code into a page, your browser would refuse to run it.
No third-party scripts. The most common way websites leak data is through code supplied by other companies. This website contains none.
Protection against embedding. The website cannot be shown inside other websites' pages, which protects against attempts to trick visitors into clicking something they did not intend.
Further browser protections. The website instructs browsers not to guess file types, to send limited information about where visitors came from to other websites, and not to give the website access to your camera, microphone or location, which it never needs.
Static website. Almost every page is prepared in advance and delivered as a finished file, with no database and no login, so there is very little that could be attacked. The only part that accepts input is the small comments program (section 9A). It accepts posts only from this website's own pages, limits the length of comments, allows at most 20 comments an hour from one visitor and quietly ignores automated spam.
Publishing. Changes to the website can only be published from a single computer, using an access key stored in encrypted form.
No method of transmission over the internet is completely secure. But because we keep the amount of personal data processed so small, very little could ever be exposed.
15. How long data is kept
| Data | Where | How long |
|---|---|---|
| Server access logs (IP address etc.) | Netlify | Deleted automatically; Netlify has stated less than 30 days |
| Comments (text, name, time) | Netlify Blobs, published on the website | Until deleted by us or at your request (section 9A.6) |
| Likes and reports, with the visitor code | Netlify Blobs | Until deleted by us or at your request |
| Reading accounts (username, code fingerprint, dates, Corpus reading progress) | Netlify Blobs | Until you delete the account (section 9B.6) |
| Sign-up log (username, time the account was made, time it was deleted) | Netlify Blobs | While the account exists, and 12 months after it is deleted (section 9B.6) |
| Rate-limit marks, with the visitor code | Netlify Blobs | Deleted once the hour is over |
| Theme, reading positions, tip and privacy note shown, your name for comments, Corpus progress and account session | Your browser | Until you delete them or sign out (section 7.5) |
| Scans settings and your own books | Your browser | Until you delete them (section 7.5) |
| Password cookie (while the site is protected) | Your browser | As set by Netlify; no longer used once the protection is removed |
| Anything else | — | Nothing else is collected |
16. Automated decisions and profiling
We do not make decisions about you based solely on automated processing, and we do not create profiles of visitors, whether to predict their interests, to show them particular content or for any other purpose (Article 22 GDPR). Every visitor sees the same website.
17. Children
This website is a library of educational texts and is open to readers of all ages. It does not ask anyone, child or adult, for personal information, and it does not try to identify any visitor. Comments are public, so we ask children not to post their real name or anything that identifies them; we delete such comments when we see them.
18. Your rights
The GDPR gives you a number of rights regarding personal data about you. This section explains each of them and what it means for this website.
18.1 Right of access (Article 15 GDPR)
You have the right to know whether personal data about you is processed and, if so, to receive a copy of it, together with information about the purposes, recipients, storage period and your other rights.
On this website: comments you posted are public, so you can see them yourself. If you created a reading account, we hold its username and your Corpus reading progress; every device signed in to it shows that same progress (section 9B). Apart from those, we do not hold any personal data that identifies you. The server logs are held by Netlify for a short time, and they and the visitor codes (section 9A.2) cannot be linked by us to you as a person. Everything else is in your own browser, where you can see it yourself (section 7.5).
18.2 Right to rectification (Article 16 GDPR)
You have the right to have incorrect personal data about you corrected and incomplete data completed.
On this website: server logs record technical facts as they occurred; there is no data about you that could be incorrect in the usual sense.
18.3 Right to erasure (Article 17 GDPR)
You have the right to have personal data about you deleted, in particular when it is no longer needed for its purpose, when you have successfully objected to its processing, or when it was processed unlawfully.
On this website: server logs are deleted automatically after a short time. Comments you posted are deleted at your request (section 9A.6). A reading account and its synced progress are deleted at once with "Delete my account"; its sign-up log entry follows 12 months later (section 9B.6). Data in your browser can be deleted by you at any time (section 7.5).
18.4 Right to restriction of processing (Article 18 GDPR)
You have the right to have the processing of your data restricted, for example while its accuracy is being checked or while an objection is being considered.
18.5 Right to data portability (Article 20 GDPR)
You have the right to receive personal data you provided to a controller in a structured, commonly used and machine-readable format, where processing is based on consent or a contract and carried out by automated means.
On this website: comments are public, and their processing is not based on consent or a contract, so this right does not apply to them. A reading account is based on a contract (section 9B.5): its progress is kept, in a structured, machine-readable form (JSON), in the browser of every device signed in to it (mw_corpus, section 7.3), where you can take it with you.
18.6 Right to object (Article 21 GDPR)
You have the right to object at any time, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR (legitimate interests), which is the basis for the server logs (section 6), for comments, likes and the visitor code (section 9A), and for the limits on attempts for reading accounts (section 9B.3). We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims.
On this website: the server logs are necessary to deliver the website at all (section 6.8). If you object, the practical way to avoid them is not to visit the website, or to use a VPN.
18.7 Right to withdraw consent (Article 7(3) GDPR)
Where processing is based on consent, you may withdraw it at any time, without affecting the lawfulness of processing before the withdrawal.
On this website: no processing is currently based on consent.
18.8 How to exercise your rights
You can reach Maktabah Wasatiyyah through the TikTok and Instagram accounts linked on this website. To have a comment of yours removed, you can also use Report (section 9A.6). Please note that, because we do not know who our visitors are, we may not be able to find any data relating to you; in most cases, the honest answer to a request will be that we hold none.
19. Complaints to a supervisory authority
If you believe that the processing of personal data about you infringes the GDPR, you have the right to lodge a complaint with a data protection supervisory authority (Article 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. This right exists regardless of any other remedy.
In Germany, each federal state has its own data protection authority; a list is available from the Federal Commissioner for Data Protection and Freedom of Information (BfDI) at bfdi.bund.de. In other EU countries, the national data protection authority is responsible; a list is available from the European Data Protection Board at edpb.europa.eu.
20. Is providing data required?
You are not required by law or by contract to provide any personal data to use this website. Commenting is optional, and so is the name above a comment. The technical data described in section 6 is, however, necessary to deliver web pages to you; without it, the website cannot be displayed.
21. If something goes wrong
If a security incident ever affected personal data processed for this website, we would assess it without delay. Where required by law, we would report it to the competent supervisory authority within 72 hours (Article 33 GDPR) and inform affected visitors where the incident is likely to result in a high risk to them (Article 34 GDPR). Because so little personal data is processed, and the comments stored are public anyway, the risk of such an incident affecting you is very small.
22. Changes to this policy
We will update this policy whenever the website changes in a way that affects your privacy, for example if a new feature processes data differently, or if our hosting arrangements change. The date at the top shows when it was last changed.
We will not start using your data in new ways without first updating this page. If we ever wanted to introduce something that requires your consent, such as visitor statistics using cookies, the website would ask you first and nothing would be stored or sent until you agreed.
23. Frequently asked questions
Do you know who I am?
No. The website never asks for contact details, and we do not try to identify visitors. If you write a name above a comment, that name is published; you can leave it empty. Netlify's server logs contain your IP address for a short time, but we have no means of linking it to you as a person.
Do you know which booklets I read?
Not as an individual. Netlify's logs show which pages were requested, which lets us see roughly how often each booklet is read overall. Your own reading positions are stored only in your browser and never sent to us. In the Corpus, if you create a reading account, the books you read there are kept in it under the username you chose, which tells us nothing else about you (section 9B).
Why is there no cookie banner?
Because the website uses no cookies or storage that would require your consent (section 8.3).
Is my search history stored?
No. Searching happens inside your browser and your search words are neither sent anywhere nor stored (section 9).
Do TikTok or Instagram know that I visited this website?
Not from visiting our pages: there are no TikTok or Instagram buttons or embedded posts that would tell them. Only if you click a link to our accounts do you connect to their websites (section 11).
Does Google know that I visited this website?
Not through this website. We use no Google services: no Google Analytics, no Google Fonts and no Google advertising. If you found us through a Google search, Google knows about that search, as with any other.
Why do you need my IP address at all?
Without it, the server could not send the page to you (section 4.3). Every website receives it; what matters is that we do not store it ourselves, combine it with anything or use it to identify you.
Can I use the website without leaving any trace?
You can use a private or incognito window, so nothing remains in your browser afterwards, and a VPN, so our hosting provider sees the VPN's address instead of yours.
What happens if I delete the site's data in my browser?
The website will forget your theme, your reading positions, the name you used for comments and any books you added to Scans. Comments you posted stay. If you have a reading account, sign in again with your username and login code and your Corpus progress comes back. Nothing else changes, and you can keep using everything.
Are the books I add to Scans uploaded?
No. They stay in your browser on your device (section 7).
Is the picture I check with "Check a scan" uploaded?
No. It is read inside your browser and not stored (section 7.3).
Can I delete a comment I posted?
Yes. Press Report on it and reply to it that you want it removed; reported comments are shown to us first, and we will delete it (section 9A.6).
Do you sell data?
No. We do not sell, rent or trade data. Apart from public comments, we hold almost nothing about anyone.
What happens when I share a quote as a card?
The picture is created on your device and goes only where you send it (section 12).
Will this ever change?
If it does, this page will be updated first, and anything that needs your consent will ask for it before anything happens (section 22).
24. Legal references
This policy refers to the following provisions:
General Data Protection Regulation (GDPR), Regulation (EU) 2016/679:
- Article 4: definitions;
- Article 6(1)(f): processing based on legitimate interests;
- Article 7(3): withdrawal of consent;
- Article 12: transparent information;
- Article 13: information to be provided to visitors;
- Articles 15 to 21: the rights of data subjects;
- Article 22: automated decisions and profiling;
- Article 28: processors;
- Articles 33 and 34: notification of data breaches;
- Article 45: transfers on the basis of an adequacy decision;
- Article 46(2)(c): transfers subject to Standard Contractual Clauses;
- Article 77: the right to lodge a complaint with a supervisory authority.
Telecommunications Digital Services Data Protection Act (TDDDG), Germany:
- § 25: protection of privacy on end devices; § 25(2) no. 2: storage strictly necessary to provide a service explicitly requested by the user.
European Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 on the adequate level of protection of personal data under the EU-U.S. Data Privacy Framework.





