THE DETAILS, IN THE OPEN
Privacy Policy
How information is handled on the God Plays Dice publishing website.
PRIVACY
This policy applies to officialgodplaysdice.com, the publishing and public-research home of GOD PLAYS DICE™.
The Question Library
- Asking for a question. If you use “Ask for it”, we store your question for editorial review. If you choose email follow-up, we also store your email and use it only to contact you about that question. Earlier requests permitted email only if their answer is published; that narrower permission still applies. Neither choice subscribes you to the newsletter. We cannot promise a reply or publication. To stop spam, we briefly keep a scrambled code made from your internet address; it changes every day, and we can’t turn it back into your address.
- Searching. Library searches run in your browser; your question is not included in the page request to our server. If you search from the homepage, your question briefly appears after # in the Library address. The Library then replaces it with #find.
- Reading count. If the monthly free-reading limit is on, a small signed cookie on your device remembers which long answers you’ve opened this month when you read without signing in. It holds no name or email. For signed-in free readers, we keep the month and long-answer IDs in the reader account instead.
Free reader accounts
- Sign-in. A free reader account uses your email address. There is no password: we email you a one-time sign-in link that works once and expires in 30 minutes. Opening the link sets a short-lived security cookie for the sign-in button. Completing sign-in sets the usual WordPress sign-in cookies.
- Account email. Sign-in links and membership messages are sent through our WordPress email service, currently Brevo. These account messages are separate from the newsletter, which uses Kit and requires its own signup. Creating a reader account or requesting a question does not subscribe you to the newsletter.
All Access membership
- Membership. We store your membership status, the date it is paid through, and Stripe’s customer and subscription numbers, so we know what you can read.
- Payments. Stripe processes payments under its own privacy policy. We never see or store your card number. Stripe tells us when a payment succeeds, renews or is cancelled.
- Email. We send sign-in links and membership notices. They are not marketing. The newsletter is separate: it uses Kit and needs your own opt-in.
Email updates
The launch-announcement form is provided by Kit, an external email service. When you subscribe, the information entered into that form is sent directly to Kit and is governed by Kit’s privacy practices as well as this notice. The main site does not save a second local copy of new Kit form submissions. We use the list for GOD PLAYS DICE™ book news, launch announcements, verified availability, selected public updates, and notice when the planned reader giveaway opens.
Planned 500-copy reader giveaway
A future promotion is planned for 500 digital copies of GOD PLAYS DICE™. The promotion is not open until eligibility, dates, prize details, entry method, selection process, and Official Rules are published. Joining the ordinary email list now keeps you informed but is not an entry. If the promotion opens, its dedicated form and Official Rules will explain the data used to administer entries, prevent duplicate or fraudulent entries, contact potential recipients, and deliver prizes.
Contact correspondence
If you contact the main site, the information you provide is used to respond to book, media, event, permissions, or public-research correspondence. Do not send passwords, payment-card numbers, API keys, security codes, confidential research, or unpublished material without prior agreement. For account or privacy questions, use the contact page.
Embedded Facebook content
The First Public Trace page contains a lazily loaded post supplied directly by Facebook. When the embed loads, the visitor’s browser connects to Facebook/Meta, which may receive ordinary network and device information and may use cookies under its own policies. A direct link is provided if the embed is blocked or you prefer to open the post on Facebook.
Routine site operation
The web host and security tools may process ordinary request data such as IP address, user agent, requested page, timestamp, and error or security events to deliver and protect the site. Any analytics or cookie tools enabled by the operator must be disclosed through the site’s active consent and cookie controls.
Reading history on your device
The site remembers which stories you have opened and where you stopped reading, so it can mark stories as read and offer “Pick up where you left off.” This list is stored only in your own browser (local storage). It is never sent to us or to anyone else. You can erase it at any time with “Forget my reading history” at the bottom of every page, or by clearing this site’s data in your browser.
Your choices
Kit sends a confirmation email before a new subscriber is fully added, and every email includes an unsubscribe link. You can unsubscribe at any time. Use the main-site contact page for privacy questions concerning this site or the email list. To delete your account and its data, write to us through the contact page.
Email-service dependency
Email signup and delivery depend on Kit being available and correctly connected. If the form is temporarily unavailable, try again later or use the contact page.
Reading settings on this device
This browser remembers the stories and answers you opened, where you stopped reading, the paths you started, the nights you stopped by and the answers you saved, so it can offer them back to you. These stay in this browser and are never sent to us. Answers about death, grief, crisis and questioning a faith are never recorded. A copy on your Home Screen keeps its own memory.
The Architect: AI processing
The Architect is an AI companion. When you consent and send a question, your question, conversation context and relevant source excerpts are sent to OpenAI for an AI response. The homepage draft field only carries an editable draft to the Architect page; it does not send an AI request.
AI can make mistakes. Research sources can include unchecked or outdated drafts. OpenAI may retain API data in abuse-monitoring logs. Read OpenAI’s data controls before sending personal information. The existing Architect conversation notice describes its retention and limits.
Ask the Architect
The Architect is a separate AI conversation for All Access members. Library search continues to run in your browser. When you agree and submit an Architect question, we send your question, limited follow-up context, and selected excerpts from published Library answers, the book or Ricardo’s research material to OpenAI. We do not send your account email or payment details in that request.
Short conversation context and completed answers are available on this site for follow-ups or request retries for 30 minutes. Expired data is removed during routine WordPress cleanup. The visible conversation clears when you reload or close the page. There is no permanent conversation archive. Usage records contain your account ID, timestamps, request identifiers and reserved or estimated cost, without the question or answer text.
OpenAI requests use store:false; OpenAI may nevertheless retain API data in abuse-monitoring logs under its own policies. Please do not submit confidential or sensitive personal information. Read OpenAI’s API data controls. Contact us through the website for questions about account data.