Privacy
Last updated: October 10, 2026.
Summary
Scriptorium does not collect, store on a remote server, or transmit any personal data to any third party. No analytics, no telemetry, no user account, no advertising. Everything the extension does happens locally, in your browser: the Bible texts are files shipped with the extension and read on your device.
Data stored on your device
- Chosen Bible, 2nd Bible, “offline page” setting, Bible text formatting (alignment, font, size), in the extension’s storage. They are used to remember your preferences. If you have turned on your browser’s sync, it is your browser that syncs them across your devices: the extension has no server.
- Theme and last reading position, in the extension’s local storage, to reopen your reading where you left it. Never synced.
- Your 🔥 notes and your 💬 comments: the reference of the verses you noted (book, chapter, verse), the date and time of creation and, for a comment, the text you wrote and the date of its last change. They are in the extension’s local storage, on your device only: never synced, never transmitted, with no backup or export. You can delete them one by one from their window.
- Addresses of pages that failed to load, in the extension’s session memory, to keep a click on “Back” from trapping you on the offline page. They are cleared when the browser closes, with at most 20 addresses per tab.
Nothing else is saved: no reading history (only the last reading position is kept), no browsing history, no statistics. Uninstalling the extension removes this data, your notes and comments included, with no way to get them back.
What the extension does with your navigation
To display the offline page, the extension is told when a page fails to load, and when a successful page finishes loading, only to reset its protection against redirection loops.
- It only cares about failures caused by an internet access problem (network down, site name not found, timeout, failing proxy) on public sites. Certificate errors, refused connections, cancellations, subframes and local sites are ignored.
- The address of the failed page is never transmitted: it is used to show the site name, to reload the page if you click “Try again”, and to remember it for the protection described above. The offline page’s own address contains the requested address, so it appears in your browser’s local history like any visited page.
Clipboard
When you click the 📋 button, the extension writes the quotation of the selected verses to the clipboard. This is write-only, on your request: the extension never reads the clipboard, saves nothing of what it puts there and does not transmit it.
Network requests
The extension calls no server of its own. It only:
- reads its own files, the Bibles shipped with the extension;
- on the offline page, when you click “Try again” or your browser reports that the network is back, sends one request to the page you wanted to open, to see whether it answers. No cookies or credentials, the response is not read, 8 seconds at most. The requested site sees this request like any visit, including your IP address.
Bible texts and license
The built-in texts are in the public domain (Louis Segond 1910, American Standard Version 1901, Reina-Valera 1909, and the Hebrew text of the Westminster Leningrad Codex) or open access (SBL Greek New Testament, for the Greek). The data files that contain them have TechForFaith as rights holder and are distributed under the Creative Commons BY-NC-ND 3.0 FR license: attribution, no commercial use, no modification. They are shipped without any modification. Attribution and license are shown in the extension’s Settings, under “Credits and licenses”.
Permissions requested
storage: to remember your preferences, your last reading position, your notes and comments, and the protection against loops described above.webNavigation: to detect that a page could not load, in order to show the offline page. The browser presents this permission as access to your browsing history; the extension builds none and transmits nothing.
No other permission: no access to page content, no authorisation on specific sites, no script injected into pages.
No remote code
All the code is inside the extension, which never loads any from a server.
Children
Scriptorium is not specifically aimed at children and does not collect personal data from any user, whatever their age.
Changes to this policy
Any change to this policy will be published at this same address, with the date above updated.
Contact
A question about privacy or how the extension works? Use the contact form.
Still unclear? Suggest an improvement to the docs.