Privacy Policy
This Privacy Policy lists what Scrollwork stores and sends today, field by field, and separates it from what is planned. An account, a message and a donation each leave a different record; reading does not leave a history against your name.
Accurate as of 19 November 2026
Scrollwork is owned and operated by Tech Portfolio Monster LLC, a company owned by the Guillory family, in Arizona, United States.
What is collected today
A message is kept if you send one, and an account if you make one. What you write and mark in the Study Reader stays in your own browser, as set out first below. Your browser also remembers a few choices. Scrollwork's hosting provider serves the pages and sees their requests. None of this is used for advertising.
What you keep in the Study Reader, on this device
Your notes, the notebooks you keep them in, your highlights and the highlight
categories you make, your bookmarks and their folders, your reading history
(the chapters you read and the views you open), and the reading plans you follow,
with each day’s reading you tick off, are kept in this browser's own
storage, IndexedDB, in a database named scrollwork-study. While you
are signed in they are also kept in your account, so they follow you from device
to device, as set out under Kept by Scrollwork, against your account’s identifier, below; they
are never sent to anyone else. The pages that show them read them from this
browser and request only the Scripture text they quote, from this site. Scrollwork
does not read, count or share them. While you are signed in, your reading history is
kept in your account with the rest, so it follows you between devices.
They belong to this browser on this device. Clearing the browser's site data clears them here, though not the copy in your account, and in a private window, or where the browser blocks storage, nothing is kept past the page. So that nothing is lost, My Notes downloads a backup of all of them as a file, and restores one. When you sign in they move into your account; signed out, they stay in this browser alone. Deleting your account deletes the copy in it.
While you are signed in, the Study Reader also keeps on this device some chapters of a
Bible shown through YouVersion, whose publisher licenses it: the chapters you read and any you choose to
keep for offline, so they open without the network. They are
kept in this browser's IndexedDB, in a database named scrollwork-licensed, each with its
translation's name and its publisher's copyright line. At most 500 verses of each such Bible are kept, never a
whole book; each chapter is deleted 30 days after it was last fetched, and all of them when you sign out. They
are never sent anywhere, and Scrollwork does not read or count them.
If you send a message through the contact form
| Stored | Why |
|---|---|
Your email address, subject and message
(from_address, subject, body) |
To read and reply. The subject is optional. Your address is kept encrypted, as an account’s is, and read only when a message is answered. |
A message identifier and the time it arrived
(id, received) | To find it and read messages in order. |
A salted hash of your IP address (source_ip_hash) |
Kept with the message. The address itself is not stored; the hash can recognise repeat submissions without holding the address in the clear. |
The same kind of hash and the time of an
attempt, numbered in the order they came (id, ip_hash, at) | To rate-limit submissions. Older attempts are cleared when a later submission is stored, after a day; refused message text is not kept in this table. |
Messages have no automatic expiry today. They are not part of an account; write and ask to have yours deleted.
If you request a feature
| Stored | Why |
|---|---|
Your account’s identifier, the
title, what you are trying to do and the time it arrived
(account_id, title, body,
received), with a request identifier (id); and,
beside it, when it happens, the part of Scrollwork it concerns, how you
manage now and how much it matters, the last two only if you gave them
(situation, area, workaround,
importance) |
So the person who builds Scrollwork can read it, and no one else: there is no public list and no voting. Your address is not asked for: it is your account’s, held by the sign-in service, so we can tell you when what you asked for ships. The same rows limit a reader to five requests an hour. When the sign-in service erases your account, after its thirty-day hold, your requests are deleted here too. |
The second half of a request: when
it happens, the part of Scrollwork, how you manage now and how much it
matters (situation, area, workaround,
importance), kept beside the request it belongs to
(request_id) |
The same: read by the person who builds Scrollwork alone, and deleted with the request. |
If you ask Help’s Advisor, or say whether a page of Help was useful
The Help Advisor on help.scrollwork.app finds the page of Help that answers a
question in your own words. When you send a question, it goes from that page to
scrollwork.app, with nothing else of yours: no account, no cookie and no name.
Scrollwork passes the question to Cloudflare Workers AI, the AI service Scrollwork
uses, which returns numbers describing its meaning; scrollwork.app compares them
with Help’s own pages and answers with links to them. The AI service writes
no answer. The feedback form at the foot of each page of Help sends the page, your
Yes or No and, after No, the optional line of what was missing, to scrollwork.app;
it is not sent to the AI service. Both are checked first by Turnstile, the hosting
provider’s bot check, loaded from challenges.cloudflare.com by
help-advisor.js only when you open the Advisor or press Yes or No.
Questions and answers are kept without identity, for 90 days, to improve Help: each question’s words, with email addresses and phone numbers removed, and each page’s answers. Never your IP address, account, cookie or device. After 90 days they are deleted; what is left is the number of questions behind an FAQ entry the administrator has published.
| Stored | Why |
|---|---|
Each question the Advisor answered, with email
addresses and phone numbers removed; the day; the page of Help it matched, or
none; whether that page was opened; and the numbers describing its meaning
(id, text, day, slug,
followed, vector) |
So the administrator can see what readers ask most, which questions no page answers, and which answers were not followed, and improve Help and draft its FAQ. No IP address, account, cookie or device. Deleted after 90 days. |
A one-way hash of a question’s words
and Help’s pages, the day, and the answer and numbers it was given
(qkey, day, results, slug,
vector) |
So the same question is answered again without asking the AI service. The question’s words are not kept here. Deleted after 90 days. |
A salted hash of your IP address, as the contact
form keeps one, the day and how many questions it sent
(ip_hash, day, calls) |
So no one visitor can use up the day’s questions. Only today is kept; earlier days are deleted. It is never stored with a question. |
The page of Help, your Yes or No, the optional
line of what was missing, with email addresses and phone numbers removed, and
the day (id, slug, useful,
missing, day) |
So the administrator can see which pages help and what they lack. No IP address, account, cookie or device. Deleted after 90 days. |
A salted hash of your IP address, the page
and the day (ip_hash, slug, day) |
So each page takes one answer a day from each visitor. Kept apart from the answer, and only today; earlier days are deleted. |
The day and how many answers came that day
(day, answers) |
To stop at a fixed number a day. No reader is recorded. |
Each FAQ entry the administrator publishes: its
question as he wrote it, its links to Help, how many questions stood behind it,
their combined meaning, whether it is shown, and when it was made
(id, question, links, asked,
vector, published, created) |
For Help’s FAQ page. It holds no question as a reader typed it unless he keeps those words, and nothing about who asked. |
The scripts on these pages
The contact form uses a bot check from
Scrollwork's hosting provider; the registration and password reset forms use the
same check, verified by the sign-in service (see Who else is involved). Our turnstile.js loads it from
challenges.cloudflare.com only when you start filling in a form. It
checks whether a submission is automated and receives browser and connection
signals, including your IP address and browser description; it is not sent the
message or password you typed. Its browser storage belongs to the provider's
address, including cf.turnstile.u, rather than to Scrollwork. The
provider describes that processing in its
privacy
addendum for the bot check. It is the only outside script loaded here.
rail.js reads sw_nav, the sign-in hint described under Cookies.
When it finds the hint, it asks /app/nav on this site, with your
session cookies, for the account button's avatar or initials and the way back
into the application. The local storage script sw-text-size.js reads or
refreshes the copy of your text size. The home page's hero-carousel.js moves its screenshots, its compare.js
opens and closes How we compare, and its genesis-fit.js sizes the faint Hebrew of Genesis 1
behind the page to fill your screen; all three store nothing and send nothing. Its number-panels.js asks this
site, without your cookies, for the counted figures the page shows (/api/stats: totals only, the same for
every visitor) and writes them into the page; it stores nothing.
sync.js, on the application's pages and only while you are signed in, keeps the twelve settings marked below and your notes, highlights, bookmarks and reading history in your account, so they follow you to your other devices; signed out, it sends nothing. password.js lets you show a password while typing; timezone.js fills the form's timezone from your browser; avatar-upload.js crops an image you chose to a 256-pixel square before the form sends it here; avatar-choose.js saves the avatar you click on the account page, sending only your choice, here; account-passkey.js makes a passkey you ask for on the account page and sends it, through this site, to the sign-in service, storing nothing; account-style-1.js, the sign-in service's own script for the account's pages, saves the avatar you click from its set and lets you edit your profile in place, sending only what changed, through this site, storing nothing; account-switch.js submits an account setting's form when you flip its switch, storing nothing and sending nothing beyond that form; save-button.js shows that a form is saving; app-drawer.js opens the application's menu; licence-prompt.js asks once on each device that you accept the terms of use and this notice, and remembers your answer as set out below; about.js filters the change logs on the two About pages, storing nothing; and whats-new.js shows, once for each new version of the application, what changed in it, and remembers the version you last saw, as set out below; and small-screen.js says, on a window smaller than Scrollwork is made for, what it needs, and remembers that you closed the note, as set out below. The contact and feature forms send the details you submit to Scrollwork; the sign-in, registration, confirmation and reset forms send what you type straight to the sign-in service, as described under If you make an account below, and no password reaches Scrollwork's own server.
scroll.js, chart.js, network.js, library.js, people-race.js, tribes.js, tribe-race.js and family-tree.js draw the scrolls and charts. They request the data, Scripture text and pictures they need from this site; those requests carry the usual browser headers and, when you are signed in, the session cookie. They remember only the choices listed below in browser storage, not a reading history. shelf.js shows the shelf's tabs and gallery; shelf-view.js switches its cards and list; megiddo.js tilts the mosaic's pictures and opens them full size; art-viewer.js opens the home page's pictures full size; daily-reader.js opens the home page's verse of the day in the small reader, requesting that verse's Scripture text from this site, and remembers only the translation you choose, as listed below; story-in-gold.js opens a coin's story beside the Story in Gold's thread, requesting it as scroll.js does; biblical-art.js draws Biblical Art's road and opens its works; menu-search.js puts the same Search in the menu on larger screens, opened only when the menu is, and asks this site for what Search asks it on any page; roadmap-filter.js shows one Sprint's deliverables on the roadmap when you press it, and asks nothing of anyone; session-watch.js asks this site whether your sign-in is still live while an application page is open, and shows a Sign in link when it has ended; donation-reminder.js, on every application page, tells this site once a minute that you are reading, only while the page is visible and you have acted on it in the last two minutes, and asks this site at a natural break (a page opened, a chapter finished) whether a donation reminder is due; Square's own script is loaded from Square when the donation dialog opens, or when you press Add a card or Replace on your account page (donation-cards.js), and draws Square's card form, and in the dialog Google Pay's button, which Square loads from Google (pay.google.com) for a one-time donation; Apple's Apple Pay script is loaded from Apple (applepay.cdn-apple.com) before Square's when the donation dialog opens, for Apple Pay; card-brands.js names a card's brand on that page, and asks nothing of anyone; gift-chooser.js puts the gift amount you choose into the link to PayPal, and asks nothing of anyone; receipt-print.js opens your browser’s print dialog when you press Print or save as PDF on a donation receipt, and asks nothing of anyone;scripture.js draws the whole Bible on one scroll, requesting from this site the Scripture text of the book in view and the books on either side, a book at a time, and in the original languages the chapters in view, and keeps your place there on this device as set out below; echarts.js and map.js draw a map: the places and journeys, on a base of land, lakes and rivers, requested from this site, remembering nothing in browser storage; search-charts.js draws a search's hits as charts when you open Charts, from what is already on the page, fetching nothing. reader.js draws a chapter in the Study Reader: it requests that one book's Scripture text from this site, in each translation you show, and, when you open a verse's menu, that book's cross-references, that chapter's people, places and events, and that book's works on Biblical Art, from this site too. To read a notebook along the timeline, and to place your notes and highlights on the lineage, the reader's pages request the year files of the books you have marked, from this site; what you marked is not in the request. Share Verse hands the verse to your device's own share sheet only when you choose it. study.js draws My Notes and its views from what this browser keeps on this device, and fetches only the Scripture text it quotes, from this site; it sends nothing you keep. With its My progress rim shown, library.js reads your reading history from this device to colour the books you have read; it sends nothing. None of these sends your reading to an advertising or analytics service. The one counting script, described under If you visit any page, sends the address of each page it is on.
Every script loaded from another site, and why it is there. The
application's pages allow these and no others; a page that refuses one reports it to
this site, as a count (see csp_report under What is collected today).
| Site | What it is | Why it is there |
|---|---|---|
| web.squarecdn.com | Square's
payment script (/v1/square.js), loaded when the donation dialog opens
or when you press Add a card or Replace on your account page | It draws Square's card form inside Square's own frame, so every card digit goes to Square and none to Scrollwork, which receives only a one-use token. Donations by card cannot be taken without it. |
| sandbox.web.squarecdn.com | The same script from Square's test environment | Loaded only for the administrator's own account, to test donations with Square's test cards; no reader is ever sent it. |
| pay.google.com | Google Pay's script, which Square's script loads | It draws the Google Pay button beside Square's card form in the donation dialog, for a one-time donation. |
| applepay.cdn-apple.com | Apple's Apple Pay script, loaded before Square's when the donation dialog opens | It offers Apple Pay, and draws Apple's button, in browsers other than Safari as well. |
| challenges.cloudflare.com | The
bot check, loaded by turnstile.js on the public contact form and the
sign-in service's registration and reset forms | It keeps automated submissions out of those forms. It is never loaded on an application page. |
When you search
Search finds people, places, books, verse references, the words of the Bible's text, the original language and topics on your device. The first time you search a translation, the page downloads that translation's whole search index, its text, the topics and the data its filters use, from this site, and keeps them in your browser; what it downloads depends only on the translation, never on what you type. Every search by words and topics, and every filter, is then worked out in your browser, and is never sent anywhere. The My study filter reads your notes, highlights and bookmarks from this browser's own storage, as set out above; they are not sent either. A search you share as a link carries only its words and its filters, in the link itself, to whoever you give it to.
Search by meaning is the one exception. When you use it, the question you typed, and nothing else, is sent to Scrollwork's own search on this site, which passes it to the AI service Scrollwork uses to be turned into numbers that describe its meaning; your browser then finds the closest verses itself. Your account is not sent to the AI service. Neither Scrollwork nor the AI service keeps the question: Scrollwork's search writes no log and stores nothing but a count of how many questions were asked that day, and how many you asked today, as listed below; and the service states that it stores what it is sent only when a storage service is used with it, which Scrollwork does not, and never uses it to train a model. If you would rather nothing leave your device, search by words and topics only; once the day's count is reached, or if the AI service does not answer, search does that by itself and says so.
What your browser remembers
These are local storage, not cookies. They belong to this browser on this device, and are shared by its tabs and anyone using the same browser profile. Signing out or deleting an account does not clear them. The twelve marked as kept in your account are also sent to it when you are signed in, as set out under Your account below. You can clear them in your browser's site-data settings; when storage is blocked, the choices last only while the page is open.
| Key | What it holds |
|---|---|
sw-text-size | One of standard, plus2, plus4 or plus6. It copies the account's text-size setting so public pages open at the same size. The account setting is also stored on the server; this script does not send the local copy. |
sw-translation | The translation you chose for a mini-reader, a drill-down, the Study Reader or the whole-Bible scroll. Its identifier determines which Scripture file the page requests here; the saved choice is kept in your account as well, so it follows you to your other devices. |
sw-scripture-place | Where you were on the whole-Bible scroll -- the verse, the zoom and the layout, as {"at":"Isa.40.1","z":"verse","m":"columns"} -- so it reopens there. It is not sent anywhere. |
sw-map-names | biblical, modern or both: which names the Jesus map shows for its places, the Bible's or today's. It is not sent anywhere. |
sw-reader-bibles | Which translations the reader's pickers offer, and in what order, as you chose them in Manage Bibles. Kept in your account as well, so it follows you to your other devices. |
sw-reader-pairs | For each of the Study Reader's columns, the two translations it flips between, as {"0":["kjv","bsb"]}. Kept in your account as well, so it follows you to your other devices. |
sw-reader-split | The chapter you read beside another, as John.19, until you close it. |
sw-reader-commentaries | Which commentaries you have open in the Passage Guide. |
sw-reader-focus | on or off, whether the Study Reader is in focus mode, its controls hidden until you move. |
sw-reader-inline | on or off, whether the Study Reader shows your inline notes as marks in the text. |
sw-reader-columns | 1 to 4, how many columns the Study Reader sets one translation's text in. |
sw-reader-width | comfortable, wide or full, how wide the Study Reader runs its lines. |
sw-reader-aa | open or closed, whether the Study Reader shows its reading settings. Kept in your account as well, so it follows you to your other devices. |
sw-reader-mode | The reading mode you chose, Normal or Study, or the features you turned on yourself. Kept on this device only. |
sw-reader-recap-open | 1 while the Study Reader's Bible Recap pane is open, so it opens again on the next page you read. Kept in this tab only (the browser's session storage), gone when you close the pane or the tab. |
sw-reader-size, sw-reader-leading, sw-reader-face,
sw-reader-numbers, sw-reader-strongs, sw-reader-layout and
sw-reader-paper |
The Study Reader's reading settings: its text size, line spacing, typeface, whether verse numbers show, whether every Strong's number shows, a verse per line or paragraphs, and the paper. |
sw-reader-margin | open or closed, whether the Study Reader shows its margin of notes. |
sw-listen-rate | How fast Listen reads a chapter aloud: 0.75, 0.85, 1, 1.15 or 1.3. Kept on this device only. |
sw-listen-recorded | Which of Scrollwork's recorded voices Listen reads in, one for each language. Kept on this device only. |
sw-shelf-view | grid or list, the shelf view you chose. Kept in your account as well, so it follows you to your other devices. |
sw-tribe-race-order | lived or named, whether The Tribe Race runs by when each person lived or by when each is first named. |
sw-shelf-layout | shelf or mosaic, whether the Bookshelf opens on its shelf or on its mosaic of every artifact. Kept in your account as well, so it follows you to your other devices. |
sw-mosaic-mode | full or screens, so the Bookshelf's mosaic shows every cover whole, not cut, or every artifact's screenshot. Kept in your account as well, so it follows you to your other devices. |
sw-lineage-welcome | seen, so the welcome to The Lineage of Jesus Christ is not shown again on this device. |
sw-lineage-notes | on or off, whether the lineage shows your notes and highlights as gold marks. |
sw-backup-reminder | When you last downloaded a backup or chose Not now on My Notes' reminder to back up, and which, so the reminder waits for many changes before it shows again. |
sw-lineage-strips | Whether you show the related events and the finds, as two choices named lane and finds. |
sw-lineage-kings | Whether you show the kings' reigns on the lineage, and which chronology they are drawn by. |
sw-lineage-coins | on or off: whether you show the coins on the lineage. |
sw-lineage-books | Whether you show the books of the Bible on the lineage, and whether you show them alone. |
sw-fact-last | Which fact from Scripture the lineage last showed you, so the next one is a different fact. |
sw-small-screen | dismissed, once you have closed the note that your window is smaller than Scrollwork is made for. |
sw-map-base | Which base you chose on a map: the physical map, the street map, the satellite picture or the historic map. Kept in your account as well, so it follows you to your other devices. |
sw-scripture-track | on once you turn on Track my reading on the whole-Bible scroll; absent while it is off. Kept in your account as well, so it follows you to your other devices. |
sw-scripture-progress | The chapters you have marked read on the whole-Bible scroll. Written only while Track my reading is on; Erase my progress removes it. Kept in your account as well, so it follows you to your other devices. |
sw-scripture-plan | The reading plan you chose on the whole-Bible scroll, its day and whether it is paused. Kept in your account as well, so it follows you to your other devices. |
sw-place | Where you last were, in the Study Reader or on the whole-Bible scroll: the page, the passage and the time, as {"route":"/app/reader/John.3","passage":"John.3","at":1790000000000}. It offers Continue where you left off on the Bookshelf and opens the reader or the scroll there. Kept in your account as well, so it follows you to your other devices. |
sw-sync | When this browser last sent its changes to your account and last heard from it, and the time you changed each of the settings marked above, so the later change wins. Kept on this device only. |
login-style-1:last | Which way you last signed in on this device -- a password, a passkey, or an account such as Google's -- so the sign-in page offers that way first and says Last time you used it. A way that ends in an error is not kept. If you tick Save my username, it also keeps the email address you signed in with, to fill it in next time; untick the box and the address is removed. The box starts unticked. Both are kept on this device only, and never sent to Scrollwork or the sign-in service. |
sw-scripture-welcomed | seen, once you have seen the whole-Bible scroll's welcome, so it is not shown again. |
sw-search-carry | The words of a search you carried from one page to another, and the page they were carried to. Kept in this tab only (the browser's session storage), and gone when the tab closes. |
sw-licence-v1 | Which version of the terms of use you accepted, its date, and when you accepted it, so the application does not ask again on this device until the terms change. Kept on this device only; nothing is stored if you decline. |
sw-whats-new-app-v1 | The version of the application whose What's new you last saw, so it shows once for each new version. |
scrollwork.folded. followed by a tool's name |
1 or 0, whether you folded that tool. |
scrollwork.place. followed by the page and tool |
The tool's x and y position on screen. |
scrollwork.coin. followed by a coin's identifier |
The x and y offset of a coin you moved on the lineage. Reset coins clears those offsets. |
Listen's speed and voice, the race order, welcome, strips, licence acceptance, versions seen, the note of how you last signed in, folds and positions are not sent to the server. The bot check's storage is separate, described above.
If you visit any page
Scrollwork's hosting provider sees the request's IP address, page and browser headers, as the host serving it. Scrollwork does not keep a log of which pages a named reader opened. There is no advertising pixel. There is one counting script, described next. The administrator sees the host's totals of requests, page views and visitors, the counting script's daily visits, how many signed-in readers opened a reading page each day, and account counts drawn from the sign-in service's records, described below.
The public site, the application’s reading pages and Help’s pages carry
one counting script, Cloudflare Web Analytics, from Scrollwork’s hosting
provider, Cloudflare. It is served from this site, as beacon.min.js, and it
counts visits by people rather than bots, so that the public site and the
application can each be told how many people read them.
Help’s pages on help.scrollwork.app carry the same page-view script, Cloudflare Web Analytics, which sets no cookie.
When a page that carries it opens, it sends Cloudflare the address of the page, the referring page you came from, your browser and device type, and the page’s load timings. It sets no cookie and keeps nothing on your device. It is not sent your account, your notes, your searches or anything you type. Cloudflare sees your IP address in any case, as the host serving every page. Scrollwork is shown only the counts.
It is never on the pages that are about you or that you type into: sign-in, registration, password reset, your account, the contact form, the terms you accept, the admin pages, and any page whose address carries a sign-in code. Help’s pages are counted; a public-site or application page is counted only when it is named on Scrollwork’s list, and a new one is not until it is added on purpose.
| Stored | Why |
|---|---|
The day, and your account’s identifier,
once for each day you open a reading page while signed in (day,
account_id) |
So the administrator’s chart can count signed-in readers each day exactly, each account once. Which pages you opened, and when in the day, are not recorded, and the chart shows only the number. They have no automatic expiry today, and they are erased with your account. |
The countries signed-in readers have read
from: each country once, and the day it was first seen (country,
first_seen) |
So the home page can say how many countries Scrollwork is read in. When you open a reading page while signed in, the country the hosting provider names for the request is added to the list if it is not there already. Your account is not stored with it, nor your IP address, nor how many readers or how often: the list cannot say who read from a country. It has no automatic expiry, and since it holds nothing of your account, erasing your account does not change it. |
Each reading plan a reader has finished: an
unreadable key, which plan, and the day (key, plan_id,
day) |
So the home page can say how many reading plans have been read through. When you tick the last reading of a plan, one row is added. The key is there only so the same finished plan is never counted twice: it is a one-way code made from your account and that plan with a secret only the server holds, and neither can be read back out of it. Your account's identifier is not stored. The rows have no automatic expiry, and stay when an account is erased, as they name no one. |
How many times the application was opened each day
(day, count) |
So the home page can say how many times Scrollwork was opened in the last forty days. Arriving in the application while signed in adds one to the day's count; moving from page to page inside it does not, and one sign-in is counted at most once in thirty minutes. Only the number is kept: no account, no session and no page. To know the thirty minutes have passed, the server's short-lived cache holds a one-way fingerprint of the sign-in, never the sign-in itself, for those thirty minutes and then drops it. The daily counts have no automatic expiry. |
The day, desktop, mobile and tablet visitor
totals, every other kind of device counted together, and when they were stored
(day, desktop, mobile, tablet,
other, stored_at) |
The daily job saves these counts for the administrator's chart because the host keeps the device split for only thirty days. Older daily totals have no automatic expiry here. No visitor identifier is stored in them. |
A count of the scripts and other sources the
application's pages refused to load, each day: whether it was a payment page or
another application page, which kind of source it was, and the address of the site
it came from, or inline (day, area,
directive, blocked, count) |
So an unexpected script on the pages where Square's card form opens is seen and answered. Your browser sends the report on its own when a page refuses something; only these counts are kept, never the page's address, your IP address, your browser description or who you are. They are kept one year, then deleted. |
Each weekly check of the payment pages: when it
ran, whether the pages matched their known-good copy, a fingerprint of what was served,
how many differences there were and the first twenty of them, under a row number
(id, checked_at, result, fingerprint,
differences, detail) |
So a change to the page where Square's card form opens is noticed within a week. It is about the page, never about a reader. Each is kept one year, then deleted. |
Cookies
The public pages set none. A signed-in browser does send its session cookie and navigation hint to public pages, which serve the same page to everyone and do not read the session cookie; their rail can request the account button as described above.
Signing in sets three at most. __Host-scrollwork-session is the session cookie: a random
identifier and nothing else, no account, name, address or token. It is sent across this site, is Secure and HttpOnly,
and names your sign-in record, kept on Scrollwork's side as described under If you make an account. With
Keep me signed in, which starts unticked and which you tick to stay signed in, it lasts as long as that sign-in can be renewed:
30 days after the last renewal, never more than 90 days after you signed in. Without it, it lasts until your browser
closes. Signing out removes it and deletes the record at once, so a copy of the cookie opens nothing afterwards.
__Host-scrollwork-auth is set while a sign-in or a sign-out is under way, for at most thirty minutes.
It holds a random identifier for this browser, kept to tie each tab's sign-in to the browser that began it, whichever
way you sign in, including with Google, Apple, Microsoft or YouVersion. It is Secure and HttpOnly. A finished sign-in
leaves it, as another tab may still be signing in, and it ends thirty minutes after the last sign-in or sign-out began.
The sign-in service sets cookies only on its own address, auth.scrollwork.app.
__Host-family holds a random token that means nothing by itself; the
service stores only a one-way hash of it, and the cookie carries no address, name
or account identifier. It is sent only to that address, and is Secure and
HttpOnly. With Keep me signed in it lasts 30 days; without it,
it lasts until your browser closes, and the session ends at the service after
one day. __Host-oauth is set only during a Google, Microsoft,
Apple or YouVersion sign-in, or while linking one; it holds sealed one-time values and lasts
10 minutes. The service sets no other cookie.
sw_nav is the third cookie: one word, app or
admin, readable by the page and sent across this site. It identifies
no account and grants no access. With Keep me signed in it lasts 30 days, without it until your browser closes,
and signing out removes it. These cookies serve sign-in and navigation,
not advertising. There is no advertising or analytics consent banner.
What is not collected here
- Your card or bank details. Card details are entered into Square's own form and are never seen or stored by Scrollwork: Square takes the card and gives this site a one-use token in its place. Donations are made only by card through Square. Gifts to the Guillory family through GitHub Sponsors and PayPal are made on those platforms' own pages. Scrollwork receives no card number or bank details.
- A reading history for anyone else. Your notes, highlights, bookmarks and reading history are kept in this browser on your device and, while you are signed in, in your account so they follow you between devices, as set out above. Scrollwork does not read, count or share them, or use them to build a profile.
- An advertising profile. No advertising, pixels or tracking of your reading for sale. The bot check's security signals and the host's request processing are described above.
- Data for sale. Your information is not sold. The services that process it to run the site are named below.
What is kept when you donate
A donation goes to Scrollwork; a gift goes to the Guillory family, and the two are kept apart: each record says which it is, never inferred from the platform. Square processes donations made in the application, in the reminder's dialog: card details are entered into Square's own form and are never seen or stored by Scrollwork. Scrollwork keeps the amount, the date and Square's payment identifier, and a donation is confirmed by Square itself, never by the browser. The cardholder's name and billing address, asked before Square's own card fields, and your account's email address are sent to Square with the card, so that Square can verify the card with your bank when the bank asks; Scrollwork does not keep them. A donation made in the application is linked to your account, so that it appears in your account's Donations section and the reminder knows you have given. No donor is ever named publicly unless they opt in.
A monthly donation makes a customer record at Square, which holds the card you agreed to save, with its cardholder's name and billing address; Scrollwork keeps only the link between your account and that customer, and the subscription's identifier. A billing address you save under Payment methods is held by Square on that customer record, never by Scrollwork, until you remove it. Your saved cards, your billing address and your monthly donation are read from Square each time your account page shows them, and not copied here.
Each donation gets a receipt, emailed to you when the donation is made. For a one-time donation, Square is given your account’s email with the payment, so the receipt can be sent to it; for a monthly donation, the receipt goes to the email on its Square customer record. Scrollwork reads the address from Square when it sends the receipt and does not keep it.
A gift to the Guillory family through GitHub Sponsors or PayPal opens that platform's own page; neither takes donations. Neither platform tells this site that you paid; matching a payment against the platform's own record, and marking it as a gift, is done by hand.
| Record | Why |
|---|---|
A donation or gift identifier, the giver's name and email,
amount and currency, platform (Square, PayPal or GitHub Sponsors), date given and date
confirmed, and for a Square donation Square's payment identifier
(id, donor_name, donor_email,
amount_cents, currency, platform,
given_at, confirmed_at, square_payment_id), whether it is a
donation, a gift to the family or a payment for a companion (purpose), and which of
Square's environments took it (square_env: production, or the sandbox the administrator
tests with).
Scrollwork's record of a Square donation keeps no name or address from you (they
go to Square with the card): its email is empty and kept encrypted, as every one is. | To account for money received. Kept seven years, then deleted. |
An account link (account_id) |
A donation made in the application is linked to the account that made it, so it appears in that account's Donations section. A gift to the family is linked only if it is recorded against an account by hand. |
A name chosen for publication and the consent to show it
(shown_as, shown_as_consented) |
Separate from the platform's name, and only recorded for publication if you ask. There is no form for that request here today. |
A refund Square reports: its identifier, the
payment it refunds, the amount and when (refund_id,
square_payment_id, amount_cents, refunded_at) |
So a donation counts net of its refunds. It names no account. Kept as long as the donation it refunds, and deleted with it. |
A refund’s currency and which of Square’s
environments reported it (refund_id, currency, square_env) |
So a refund counts only against a donation in the same currency and environment. It names no account. Kept as long as the refund, and deleted with it. |
For a payment to Scrollwork for a companion: Square’s identifier
for the payment and the short name of the companion it bought; and, only while the payment is not yet
linked to an account, Square’s identifier for the customer who paid (square_payment_id,
app_slug, square_customer_id) |
So a companion payment is counted as one, never as a donation, and is counted for you once that customer is yours. It names no account. The customer’s identifier is cleared once the payment is linked. Kept as long as the payment’s record, and deleted with it. |
While a donation is being taken: your account’s identifier,
which of Square’s environments, whether it is one-time or monthly, the key this site gives Square for it,
a one-way fingerprint of the request, whether it is in progress or its outcome is not yet known, and
when it began (account_id, square_env, kind,
idempotency_key, request_hash, state, created_at) |
So the same donation is never taken twice. Deleted once Square’s answer is recorded; one whose answer never came is checked with Square after ten minutes, at your next donation or the daily check, whichever comes first, and then deleted. Deleted when the sign-in service erases your account. |
While a monthly donation is being taken: Square’s identifier for
the card saved for it, beside the donation it belongs to, under a number of its own (id,
account_id, square_env, kind, card_id) |
So a monthly donation that never started leaves no saved card behind, and no other card of yours is touched. Deleted with the donation it belongs to, and when the sign-in service erases your account. |
A receipt for each donation, and a credit note for each refund of
one: its number, its place in its series, whether it is a receipt or a credit note, Square’s identifier
for the payment or the refund, your account’s identifier, the amount and currency, when it was issued,
which of Square’s environments, the receipt a credit note reverses, and when its email was sent
(number, sequence, kind, square_payment_id,
refund_id, account_id, amount_cents, currency,
issued_at, square_env, reverses, emailed_at).
No card details and no email address are kept: the card’s brand and last four digits are read from
Square each time the receipt is sent or shown. |
To give you a receipt for every donation and account for money received. Each receipt is emailed to you once, when the donation is made, and kept on your account page to print or save. Kept seven years, then deleted. When the sign-in service erases your account, its link to your account is removed and the receipt itself is kept for the rest of the seven years. |
The last number issued in each series of receipts and credit notes
(series, last) |
So no receipt number is ever repeated or skipped. It holds nothing about any reader. |
Your account’s identifier and its
Square customer’s identifier (account_id,
square_customer_id) |
Only if you set up a monthly donation, so Square's monthly payments are counted to your account and your account page can show your cards. Deleted when the sign-in service erases your account; the customer record itself remains at Square, under Square's notice. |
Your account’s identifier, the
monthly donation's Square identifier, when it began and in which of Square's environments
(account_id, subscription_id, started_at, square_env) |
So your account page can show, change or cancel it. When the sign-in service erases your account, the monthly donation is cancelled at Square first, and then this is deleted. |
A monthly donation’s Square
identifier, how many times cancelling it has been tried, when it is next tried, and
which of Square's environments it is in
(square_subscription_id, attempts, next_at,
square_env: production, or the sandbox the administrator tests with) |
Only if Square could not be reached when your account was erased: the donation is cancelled again, once a day, until Square confirms it, and then this is deleted. It names no account. |
For each of Square's two environments, the identifier of the
monthly donation's plan (env, plan_variation_id, created_at) |
So a monthly donation is made on the right plan. It holds nothing about any reader, and is kept while monthly donations are offered. |
The donation reminder
Signed in, the application counts the minutes you are active in it, so a reminder to donate can follow the time you spend in it, and goes quiet after a donation or after “I can't donate right now”.
| Record | Why |
|---|---|
Your account’s identifier, the day, the
minutes you were active that day and when the last was counted
(account_id, day, minutes,
last_credit_at), kept beside reader_day |
A minute counts only while the page is visible and you have acted on it in the last two minutes, never an idle tab, and at most one a minute by this site's own clock. Which pages, and what you read, are not recorded. Kept while your account is, and deleted when the sign-in service erases it. |
Your account’s identifier,
when a reminder was shown, which hour mark, and which message
(account_id, shown_at, mark,
message_id) |
So each reminder is shown once and the daily limit holds across your devices. Kept while your account is, and deleted when it is erased. |
Your account’s identifier and when the
reminder may next show (account_id, until) |
When the reminder may show again after a donation or “I can't donate right now”. Kept while your account is, and deleted when it is erased. |
The public costs ledger is kept in a file and shows the date, amount, platform and any recorded fees. It publishes no donor names or emails, and no donor is ever named publicly unless they opt in, by a name they choose.
The commitment is seven years from a donation or gift, then deletion. Those records older than seven years are deleted by the daily job. A donation stays linked to its account until the sign-in service erases the account, thirty days after the request to delete it; only then is the link removed, and the record itself is not deleted. An account restored within those thirty days keeps its donations. The financial record remains for its stated period.
A donation or a gift never unlocks a companion. It buys no feature, tier or influence. A reader who gives nothing has the same access as a reader who gives a great deal. A companion is its own purchase.
Who else is involved
| Who | What they see |
|---|---|
| Scrollwork's hosting provider | Hosts the pages, Scrollwork's database and the sign-in service, and stores uploaded avatars. It sees the requests it serves. It sends account emails, so it sees the recipient address and the confirmation, reset or notice being sent. |
| The sign-in service (auth.scrollwork.app) | Holds accounts, as set out under If you make an account. Like Scrollwork, it is run by Tech Portfolio Monster LLC, on the same hosting provider. The sign-in, registration, confirmation and reset forms on this site send what you type to it, not to Scrollwork. It sends the account emails: confirmation, reset, notices and emailed sign-in codes, through the hosting provider's email sending, from no-reply@scrollwork.app. Only the To address, subject and text are involved; there is no other mail provider, analytics or tracking. Mail is capped each month. |
| The AI service Scrollwork uses | Only when you search by meaning, or ask Help’s Advisor: it is sent the question you typed, by Scrollwork's search or the Advisor, and returns numbers describing its meaning. It is not sent your account, your address or anything else you keep, and Scrollwork does not ask it to keep the question. |
| The hosting provider's bot check | Checks the contact form (run by Scrollwork) and the registration and reset forms (run by the sign-in service) on first use, and Help’s Advisor and its feedback form when you open or answer them, with browser and connection signals as described above. It is not sent the form's message, question or password. |
| Tyndale House Publishers | Only when you read the New Living Translation. Scrollwork’s server asks Tyndale’s service for that chapter, with Scrollwork’s own key, and passes the text on to you. Your browser never contacts it, and it is sent no name, no email, no address and no identifier of yours: it learns only that Scrollwork asked for that chapter. |
| YouVersion | Only when you read a Bible Scrollwork shows by licence from its publisher, such as the NIV or the NASB. Scrollwork’s server asks YouVersion for that Bible and chapter, with Scrollwork’s own key, and passes the text on to you. Your browser never contacts YouVersion, and it is sent no name, no email, no address and no identifier of yours: it learns only that Scrollwork asked for that chapter. YouVersion and the Bible’s publisher see counts of what Scrollwork asked for, under their licences. The translations that are Scrollwork’s own, such as the King James, never involve it. Read without an account, Scrollwork’s server counts how many of these chapters one visitor asked for in the last hour, so that no one visitor uses up what every reader shares. The count is held only in the server’s memory, under a salted one-way hash of your IP address; it is written to no database and no log, sets no cookie, and is gone within the hour. |
| YouTube | The Bible Recap’s episodes: on Watch, on Reading plans and a reading plan’s page, and in the Study Reader when you open Bible Recap. Where an episode is shown, YouTube’s privacy-enhanced player loads, from youtube-nocookie.com: on Watch and a plan’s day when the page opens, elsewhere when you choose the episode. The episodes’ thumbnails load from i.ytimg.com. Nothing plays until you press play. YouTube sees that visit and that you watched an episode, and your IP address and device, as any site you visit does; its player may show ads, which are YouTube’s and the Bible Recap’s, not Scrollwork’s. In your account, under Reading, you can have episodes open on YouTube’s own page instead of playing here; the thumbnails still load. |
| Have I Been Pwned | When you choose a password, the sign-in service sends the first five characters of its SHA-1 hash to api.pwnedpasswords.com. The matching is done there against the returned list. The password, its full hash and your account details are not sent. |
| Identity Services (identityservices.cloud) | The sign-in service Scrollwork uses for signing in with Google, Microsoft, Apple or YouVersion: it handles that sign-in for Scrollwork. The provider you choose shares your name, your email address and an identifier for your account with Identity Services, which uses them only to sign you in to Scrollwork. |
| Only if you choose to sign in with Google, or link it to your account, through Identity Services. Google knows you used it with Scrollwork’s sign-in service and supplies your verified address, its identifier for you and a name. You confirm the name kept. No Google password, contacts or mailbox contents. | |
| Apple | Only if you choose to sign in with Apple, or link it to your account, through Identity Services. Apple knows you used it with Scrollwork’s sign-in service and supplies your address (a private relay address if you chose Hide My Email), its identifier for you and a name on first use. You confirm the name kept. No Apple password, contacts or mailbox contents. |
| Microsoft | Only if you choose to sign in with Microsoft, or link it to your account, through Identity Services. Microsoft knows you used it with Scrollwork’s sign-in service and supplies an address, its identifier for you and a name. You confirm the name kept. No Microsoft password, contacts or mailbox contents. |
| YouVersion | Only if you choose to sign in with YouVersion, through Identity Services. YouVersion knows you used it with Scrollwork’s sign-in service and supplies your address, its identifier for you and a name. The first time, a confirmation is mailed to that address before an account is made or linked. You confirm the name kept. No YouVersion password. |
| Square | Only when the donation dialog opens in the application, or you add a card on your account page. Square's script loads from Square when the donation dialog opens, or when you press Add a card or Replace, and its card form takes your card details, which Scrollwork never sees. Square processes the donation under its own notice, holds a saved card and, for a monthly donation, a customer record, and tells this site when a payment or refund completes. It knows your account only as an identifier. |
| Only when you type a billing address on your account page or in the donation dialog: the address as you have typed it is sent by this site’s server to Google, to find it as you type and to check it before it is saved. No script of Google’s runs on the page, and nothing that names your account is sent with it. Google handles it under its own notice. | |
| GitHub Sponsors, PayPal | Only when you open their payment pages: PayPal and GitHub Sponsors, to give to the Guillory family. They handle your payment under their own notices, and their records let me account for gifts. They do not automatically report a payment to this site. |
Typefaces and the pictures used on these pages are served from this site. Choosing an outside source link takes you to that source; opening a page does not load it in the background.
If you make an account
An account lets you sign in, save settings and manage your sessions. It carries no billing surface for a companion, and a donation or a gift changes none of its features.
Accounts are held by the sign-in service at auth.scrollwork.app, not by Scrollwork. Like Scrollwork, it is run by Tech Portfolio Monster LLC, on the same hosting provider. The sign-in, registration, confirmation and reset forms on scrollwork.app send what you type straight to it; no password reaches Scrollwork's own server. Suspending an account, signing a reader out everywhere, deleting an account and inviting someone are done by the administrator in the service's console, not in Scrollwork, and each is logged there.
Held by the sign-in service
| Stored | Why |
|---|---|
| Your account identifier, encrypted email, one-way email index, password hash if you set one, name, optional nickname, and creation, confirmation, suspension and deletion times; and the time you chose the emailed code as a second step, if you did | To find and secure your account. Your password is never stored as text. An account using only a provider need not have a password. Which app’s administrator role you hold, if any, is kept with it; ordinary readers hold none. |
| Your avatar, only if you chose one of the service’s built-in pictures | The service holds only its own built-in avatars. Scrollwork’s own set and any photo you upload stay with Scrollwork, as set out below, and are never sent to the service. |
| Each linked provider and its identifier for you, with the link time | So Google, Apple or Microsoft sign-in finds the account you linked. |
| Each sign-in session: its identifier, your account, when it began and how you signed in, when it expires and when it ended; and a record of the sign-in tokens issued to Scrollwork for it, with their expiry | To keep you signed in and let you end a session. The list shows only when each session started and when it expires. The service stores no browser description, IP address or device. A session past its expiry is deleted once it has no token record; a token record is deleted 30 days after it ends or expires. |
| Confirmation, reset, address-change and emailed-code links: a one-way hash of the link, your account, the purpose, the times issued, expiring and used, and, for an address change, the new address, encrypted | Each works once. A confirmation link lasts 24 hours; a reset link lasts one hour and ends every session of the account; an address-change link lasts one hour and the old address is told; an emailed code is six digits and lasts ten minutes. Expired ones are deleted by the daily housekeeping. |
| Second steps: for a passkey, its identifier, public key, signature count and creation and last-use times; for an authenticator app, its secret, encrypted, and when it was confirmed; for recovery codes, ten, kept only as hashes with the time each was used | A second step is offered to every reader and required of an administrator. A recovery code signs in once in place of the second step, and using one tells your address. |
| A one-way index of your address, or a keyed hash for the client, the kind of attempt and its time | To slow repeated attempts to sign in, register, reset or change an address. The daily housekeeping deletes attempts older than an hour. |
| An invitation: the invited address (encrypted, with its one-way index), the role, a one-way hash of the link, who invited, the times issued, expiring, accepted and revoked, and an optional name | So an invited person can sign up with the address invited. An invitation is valid for seven days. An ended invitation (expired, revoked or accepted) is deleted 30 days after it ends. |
| A log of administrator actions: identifier, time, who acted, the action, the target account’s identifier and the outcome | A record of suspensions, sign-outs, deletions and the like. It holds no address, secret or token, outlives the account it names, and is deleted after 365 days. |
| The month and the count of emails sent | To stop at the month’s mail allowance. No recipient or subject. |
A registration never confirmed, with no session, is deleted seven days after it was made.
Kept by Scrollwork, against your account’s identifier
Scrollwork’s own database keeps no address, password, name, session or second step. Every row below is keyed by the identifier the sign-in service gave your account. When the service erases your account, after its thirty-day hold, it tells Scrollwork, and these rows are deleted then; nothing is cleared before that. Scrollwork also asks the service once a day which accounts it has erased, so an account is deleted here even if that message never arrived.
| Stored | Why |
|---|---|
Your account’s identifier, as the sign-in
service gave it, and when Scrollwork first saw it (id,
created_at) | So every row below belongs to an account Scrollwork knows, and goes when it goes: when the sign-in service erases your account, this row is deleted, and every row below with it. |
Your account link and each setting's name
and value (account_id, key, value) |
The settings are look, brightness,
text_size, reader_target (where the reader opens),
drawer_side (which edge a Drawer opens from),
recap_play (whether Bible Recap videos play here or open on YouTube), your timezone
(which places dates and your verse for today) and your choice
among Scrollwork’s own avatars. Those pictures are held and served by
Scrollwork and never sent to the sign-in service. The settings
follow you across devices when you sign in. Your communication preferences
are kept here too, as comm.newsletter, comm.companions
and comm.whats_new, each on or off, and off until you turn it on. |
Your account link, which
communication preference changed, to on or off, when, and whether from your
account or from an email’s unsubscribe link, each change numbered
(id, account_id,
key, value, at, via) |
So the date you agreed to each kind of email can be shown, to you on your account page and to no one else. No address and no email is recorded. A save that changes nothing adds nothing. |
| A photo you upload as your avatar, cropped in your browser to a 256-pixel square | Kept by Scrollwork in the hosting provider’s storage, against your account’s identifier, and never sent to the sign-in service. Only you and the administrator can view it. It is removed when cleared. |
Your account link, the name of each browser setting kept in your account, its
value, the time it was changed, and the time it reached your account (account_id, key, value,
updated_at, received_at) | Carries the twelve settings marked above between devices, so the Bookshelf, the reader and the whole-Bible scroll open the way you left them on every device you sign in on. They follow your account. Only those twelve names are accepted; the later change wins. The time a change reached your account, by Scrollwork’s own clock, lets a device that is catching up be sent every change made meanwhile, so none is missed. Deleting your account deletes them. |
Your account link, and each note, notebook, highlight, highlight category,
bookmark, bookmark folder and reading history entry you made, and each reading plan you follow (its plan, start, length
and whether it is paused) and each of its readings you tick off, by its kind and identifier, its content, the time
it was changed, whether you deleted it, and the time it reached your account (account_id, kind, id,
body, updated_at, deleted, received_at) | Carries your notes, highlights, bookmarks, reading history and reading plans between devices, so what you write on one is on every device you sign in on. The time each one reached your account, by Scrollwork’s own clock, lets a device that is catching up be sent every change made meanwhile, so none is missed. A deletion is kept as a mark with no content, so your other devices remove it too, and the mark is forgotten 90 days after it reached your account. The content is stored as plain text, not encrypted, so it is readable by the service that keeps it; it is shown only to you, and deleting your account deletes them. |
Your account link, accepted terms version
and time (account_id, version,
accepted_at) | Each version is kept so a change asks once without erasing earlier acceptances. |
Your sign-in on this browser: a random identifier (the one your session cookie
holds), your account’s identifier, the sign-in service’s identifier for its own session, the roles it gave
you, its tokens for you (an access token, a refresh token and an ID token, which carries your name and email address
as the service holds them), when they end, and whether you ticked Keep me signed in. While a sign-in or sign-out is
in progress, a record of each for thirty minutes: random values that match the service’s answer to the browser
that began it.
And the list of your sign-ins’ identifiers, so the service can end them all at once, and, after the service
changes your roles or your membership, a random mark that has your next request renew the sign-in first
(key, value, version, sid, expires_at) | Keeps you signed in without the tokens ever being in your browser, and lets a sign-out, a change of role or a deletion at the sign-in service take effect at once. Each record ends when the sign-in it belongs to ends: at most 30 days after the last renewal and never more than 90 days after you signed in; the list and the mark 90 days after they were last written, and the list once it names no sign-in. A daily run deletes every record past its end. Signing out deletes this browser’s record at once, and deleting your account deletes all of yours. |
A random identifier of one sign-in record, a version number and an
expiry time (key, version, expires_at) | Lets one request at a time renew a sign-in with the sign-in service, so two open pages do not both renew it. Each lasts 20 seconds and holds nothing about you. |
Your donations and gifts, feature requests and daily search count, listed under their own headings on this page, are kept against the same identifier.
Records that keep the service running
| Stored | Why |
|---|---|
The day and how many search-by-meaning
questions were asked that day (day, calls) |
To stop at a fixed number a day, inside the AI service's free allowance, so search by meaning never costs anything. No question, no reader and no account is recorded. |
Your account’s identifier, the day
and how many search-by-meaning questions you had answered that day
(account_id, day, calls) |
So no one reader can spend the day’s shared allowance; a question the AI service fails to answer is not counted. Only today is kept: earlier days are deleted when you next ask. No question is recorded. They are deleted when the sign-in service erases your account. |
Your account’s identifier, the day
and how many Morning and Evening pages you opened that day
(account_id, day, pages) |
So Spurgeon’s readings are read a day at a time and not copied out in bulk; the limit is far above what anyone reads. Only today is kept: earlier days are deleted when you next open one. No date you read is recorded. They are deleted when the sign-in service erases your account. |
The day and how many calls the Help Advisor made
to the AI service that day (day, calls) |
To stop the Advisor at a fixed number a day, inside the AI service’s free allowance, apart from search by meaning’s. No question or reader is recorded. |
For each part of Help, a hash of its words and
the numbers describing their meaning (hash, vector) |
So the Advisor can match a question to Help’s pages. Help’s own words only; nothing about any reader. |
For each Bible shown through YouVersion, the
year and how many chapters were shown (version_id, year,
chapters) | Some publishers ask for a yearly count of the copies distributed under their licence. No reader, account or chapter is recorded. |
For a Bible shown through YouVersion whose publisher’s
terms Scrollwork does not hold: your account’s identifier, the Bible, each chapter you
opened in the last hour, how many verses it has, and when you opened it
(account_id, version_id, chapter, verses,
fetched_at) | So such a Bible is read a few chapters at a time, as its publisher may require. Only the last hour is kept: older rows are deleted when anyone next opens one. No verse is recorded. They are deleted when the sign-in service erases your account. |
The list of Bibles YouVersion makes available to
Scrollwork: each Bible's number, names, language, books and publisher, whether
Scrollwork has its publisher's terms, and when the list was last fetched
(id, abbreviation, title, localized_title,
language_tag, books, organization_id, serve,
terms, refreshed_at) | To offer every Bible in the Version sheet. It holds no verse of any Bible and nothing about any reader. |
The administrator’s key for Google’s
address search, and when it was set (api_key, set_at); one at most,
in the one row numbered 1 (id) |
So this site’s server can ask Google to find and check a billing address, as described under Who else is involved. It holds nothing about any reader, and is kept until the administrator replaces or removes it. |
The month, mail count and warning time
(month, sent, warned_at) |
To stop at the month's mail allowance and warn before it runs out. No recipient, subject or reader identifier. |
Each sign-in that did not complete: when,
where it stopped, why, how old the sign-in page was and how many were open,
each numbered (id, at, surface, reason,
flow_age_s, flows_held) | So a sign-in that fails can be found and fixed. No address, account, browser or anything you typed is recorded. Each is deleted after thirty days. |
The time up to which the sign-in service has
been asked which accounts it erased, and when it was last asked (since,
updated_at), in the one row numbered 1 (id) |
So the daily check for an erased account Scrollwork was not told about starts where the last one finished. It holds no account or anything about any reader, and is replaced each day. |
For an account the daily check found erased: where its
uploaded picture is stored, which is your account’s identifier, and when it was queued
(r2_key, queued_at) |
So the picture is deleted too, by the part of this site that holds the pictures. Each is deleted with the picture, normally the same day. |
For an account that has been erased: your account’s
identifier and when it was erased (id, erased_at) |
So a sign-in the Scrollwork iPhone app still held from before the erasure cannot bring the account back. Nothing else about you is kept with it, and it is deleted a day later. |
Companion tools, when they exist
Paid companions are planned, not on sale today: Scrollwork Table, the Henrichsen study companion, first; then Scrollwork Bible Analytics, Scrollwork Atlas and The Scroll of the Ages. Each is its own product with its own price; a donation or a gift never unlocks one.
A purchase would need a record of who bought which companion and what was paid, and the payment service would process the details needed to take that payment. A study companion would also need the study and group information you choose to put into it. None of that companion processing happens here today. Each companion will have its own privacy notice before it is offered, naming the actual fields, services, retention and deletion choices; those arrangements are not yet settled.
The Study Reader's notes, highlights, bookmarks and reading history are kept on your device and, while you are signed in, in your account, as described under What you keep in the Study Reader.
Pinterest: Scrollwork Pin Publisher
Scrollwork Pin Publisher publishes Scrollwork’s own Pins to Scrollwork’s own Pinterest business account through the tool Scrollwork uses to schedule its posts. It reads only Scrollwork’s own boards and Pins, to choose a board and confirm a Pin went out.
The access token is held by that tool, not by scrollwork.app. Scrollwork Pin Publisher collects, stores, sells or shares no Pinner’s data, and nothing from Pinterest is used for ads or for training AI.
If you use the iPhone or iPad app
Reading in the Scrollwork iPhone and iPad app is always free, in every translation, with a subscription or without one. The subscription pays for the app’s software, never for reading.
What stays on your device. Scrollwork’s own Bibles download whole to your device and stay there. A publisher’s Bible keeps only the chapters its limits allow, for at most 30 days, and those are cleared when you sign out. Your notes, highlights and bookmarks are kept on your device.
YouVersion’s Bibles. These need a free account in the app. Scrollwork’s server fetches each chapter from YouVersion, so your device does not contact YouVersion. To hold a Bible to its publisher’s limit, Scrollwork keeps the count described under If you make an account, against your account.
Listen. Listen streams recorded chapters from Scrollwork.
If you sign in. Your bookmarks and their folders, your notes and notebooks, your highlights and their categories, and your reading place and translation are stored with your account, so they follow you to your other devices and to the website. So is the version of the terms you accepted. Signed out, none of this leaves your device.
The subscription. It is billed yearly by Apple, after a free trial of 7 days for anyone who has not had one. Apple takes the payment under Apple’s privacy policy, and Scrollwork never sees your card. Cancel at any time in your App Store account settings.
Deleting your account. Delete it at scrollwork.app/app/delete, which the app opens from Settings. Your account and its synced bookmarks, notes and highlights are deleted from Scrollwork. A subscription is Apple’s, so cancel that in the App Store as well.
The app has no advertising, no tracking and no analytics kit.
What you can do
Delete your account, yourself, at any time. The sign-in service deletes it, behind a fresh sign-in. You are signed out here at once, and the service tells Scrollwork, which ends your sign-ins on your other devices at once too. The account is held for thirty days, and the deletion can be undone in that time. The service then erases the account, its linked providers, sessions, sign-in token records, second steps, and tells Scrollwork, so that Scrollwork can clear its own rows: your settings and avatar choice, your notes, highlights, bookmarks and reading history (deletion marks included, which are otherwise forgotten 90 days after they reach your account), your communication preferences and the record of your communication consent, your accepted terms, your daily search counts, your feature requests and their details, and any photo you uploaded. A donation or gift record stays, and stays linked to your account through the thirty days, so a restored account keeps them; at the erasure only that link is removed. Nothing here is cleared before the service erases the account. The address is free to register again.
A registration never confirmed is erased seven days after it was made. A donation or gift record is an exception to account deletion, described above, and so is the service’s log of administrator actions, kept 365 days. Your browser’s local choices remain until you clear the site's data there.
Write about a message, a donation or gift record or any question about this notice. The answer should be as specific as the question.