What Thornwork receives, where it goes, and what it does not keep.
Thornwork collects information when you join an email list, leave follow-up interest on the request page, send a working request, complete a paid intake, or use the site. The short version: I use it to send what you asked for, make and deliver the work, take payment through Stripe, follow up on expressed interest, and understand whether the site is working.
The site can receive your email address, an optional name, and a source tag showing where you signed up (such as the homepage, guide, book page, or blog). A signup can trigger a welcome or follow-up email through Polsia's email service. The book form is for one notification about Venēnum; it uses the subscribers list. The separate request-page lead form is not an email-list signup. If you voluntarily enter the optional email near the start of the /request form, Thornwork stores a partial request-page lead and may send up to three brief request-related follow-ups. You can stop or ask about those messages through the contact path below.
The request form receives your name, email address, selected tier, and optional description of what you need. It creates an access-code record and stores payment status and amount so the request can move through payment, status checking, and delivery. The email near the start of the form is optional while you explore; if you voluntarily enter it and leave before submitting, Thornwork stores a partial request-page lead and may send up to three brief request-related follow-ups. That capture does not submit a booking or start payment, is not the general email list, and is distinct from subscribers. The separate request-page lead form also stores an email for Dana to follow up about your interest.
The post-payment spell form stores your answers in a JSONB submission record. Those answers cover your intent, timing and urgency, experience and background, tradition preferences, budget and materials, scheduling and time zone, ritual space and privacy, safety and support, desired success and results, documentation, and delivery preferences. Please only share what you want Dana to use for the work.
Card numbers and payment credentials are entered into Stripe's checkout. They do not touch Thornwork's servers. Thornwork does not collect or store payment card details, and it does not create password-based accounts. Thornwork receives the request's payment status and amount, along with the access-code records needed for the request and delivery flow.
The site records analytics events such as page views, form starts, form steps, form submissions, payment clicks, email captures, and Substack clicks. For those events, the server may store the page URL, referrer, user agent, event type, and timestamp. The site also uses the Meta Pixel. The tw_ab_sid cookie supports the request-page A/B test, and browser storage can hold request access details and tier information plus a Polsia visitor ID in polsia_vid.
Server-side records are stored in the site's Neon/PostgreSQL database, including the subscribers, leads, requests, spell_form_submissions, and analytics_events tables. Browser storage stays in your browser. Dana Batista and Thornwork use request and intake information to respond, craft, document, and deliver the work, and may use a request-page lead to follow up about the working you are considering. Stripe handles the relevant payment flow. Polsia's email and analytics services handle the relevant email and measurement flows. The Meta Pixel is a separate analytics tool on the site.
Thornwork does not collect your card number or payment credentials itself, and it does not ask you to create a password-based account. This page does not promise a fixed retention period or a deletion schedule because those practices are not documented here.
Questions about what the site receives or how a submission is used? Email thornwork@polsia.app.