Privacy Policy

Who is responsible

Spritz Solutions, LLC, an Alabama limited liability company, of Mountain Brook, Alabama, is responsible for the information Scriptorium holds about you. Contact: support@spritzsolutions.com.

We process this information in order to provide Scriptorium to you. That is the basis for it.

What we collect, and why

When you sign up: your name, your email address, whether or not you are a student, and — if you choose to give them — your school and, if you are a student, the year you expect to finish.

Your name is so we know who is using Scriptorium, and so that when we write to you it is to a person rather than to an address. It is not shown to anyone else: shared comments carry no name at all. The email address is how you sign in. Whether you are a student decides one thing and nothing else: whether Scriptorium reminds you to add a second sign-in address before a school address stops working. School is optional and tells us which seminaries are actually using this. The year, if you give it, is how we know when to send that reminder. None of it is checked against anything, and none of it is ever shown to other users.

What you put in: your books, notes, comments, writing, and Scripture connections. This is the archive. We store it so you can use it, and for nothing else.

When you mark a shared comment: which comment you marked, and whether you marked it up or down. That record exists for one reason — so that one account cannot mark the same comment twice — and it is never shown to the comment's author or to other users. You can see and change your own marks.

When you add a friend: the email address you entered, that you asked, and when. If they accept, that the two of you are friends and when it began. If the address has no account, we send it one invitation to join, saying who asked.

When you sign in: the date you last used each of your sign-in addresses, so you can see which of them still works.

Server logs. Our hosting provider keeps standard server logs for a short period, including the address of each page requested and the IP address it came from. We do not use these for anything except diagnosing faults.

We do not collect analytics. There are no trackers, no advertising, no third-party scripts watching what you read. The only cookie Scriptorium sets is the one that keeps you signed in.

Where it lives

Your archive is stored in a PostgreSQL database hosted by Supabase in the ca-central-1 region, in Canada. The application runs on Vercel. Sign-in emails are sent through Supabase.

Those two companies process data on our behalf, under their own agreements. Nobody else has access.

Who can see it

You, through any sign-in address you have added; friends you have accepted, who can read your library as the Terms describe and never your writing; and nobody else — except for the comments you write on books, which other readers who have the same book can read, and so can the friends those readers have accepted. The Terms of Service say exactly what a friend and a comment reader are shown, and which comments that wider audience applies to.

Moderators at Spritz Solutions, LLC can read shared comments in order to moderate them. Moderation is granted to a named person rather than to a job, every grant is recorded, and every time a moderator reads a shared comment that is recorded too.

Moderators can read shared comments and nothing else — not your notes, not your writing, not your books. That is a rule the database enforces rather than a setting in the application: the application reaches the database through an account those rows are not visible to.

That rule covers Scriptorium. It does not cover the maintenance access described next, and we would rather say so than imply otherwise.

Spritz Solutions, LLC holds credentials to the database itself. Those credentials are not limited by the rule above — they exist so the service can be kept running, and they are not used to read anyone's archive. If fixing something ever required looking at your archive, we would ask you first.

How long we keep it

Until you ask us to delete it, or until we tell you we can no longer keep it.

That is deliberate. An archive of thirty years of reading is worth keeping, and someone who leaves and returns should find their books. Dormant accounts are kept rather than cleaned up.

We will not remove an archive without notice. If we ever cannot keep one, you will hear from us at least ninety days beforehand, at every address on your account, and be sent a copy of everything we hold before anything is deleted. You will be told; silence is never a deletion notice.

If you fill in the sign-up form and never open the link we send you, what you typed is kept with the invitation and deleted thirty days after it expires.

If you ask for deletion, it happens for real, and we will tell you what was deleted.

Your rights

You can ask us to send you a copy of everything Scriptorium holds about you, correct anything wrong, or delete it. Write to support@spritzsolutions.com and a person will answer — expect a reply within a few days rather than a few weeks.

If you are in the UK or the European Union, you also have the right to object to processing, to restrict it, and to complain to your data protection authority.

Security

Sign-in is by emailed link, so there is no password of yours to lose. The connection is encrypted. Each person's archive is kept separate from every other person's. A friend you have accepted reads part of yours through a control you operate; nothing is merged, and ending the friendship ends the reading.

No system is perfect. If something goes wrong that affects your data, you will be told what happened, what it affected, and what was done about it — promptly, and in plain words.

If this changes

If this policy changes, you will be told and asked to accept the new version. Old versions are kept so you can see what you agreed to and when.