Add Stripe embedded checkout to book pages
Replaces the gumroad_url stub with an on-site embedded checkout (buy button -> POST to the bookshop backend -> mounted Stripe iframe), following the existing contact/submissions form's fetch/status-message pattern. Adds thank-you and resend-link pages, an example book template (draft), and updates the privacy policy and terms to honestly disclose Stripe as a third-party payment processor.
This commit is contained in:
+25
-10
@@ -14,34 +14,49 @@ use of twosquirrelspress.com, and what happens to it.
|
||||
- Your name, email address, manuscript file, author bio, a description of
|
||||
your submission, the title or call it's for, and a headshot if you
|
||||
provide one, when you submit the submissions form.
|
||||
- Your email address and order details, when you buy a book. Your payment
|
||||
details (card number and so on) go directly to Stripe, our payment
|
||||
processor — they never touch Two Squirrels Press's own servers. Two
|
||||
Squirrels Press only ever receives your email address, which book you
|
||||
bought, and confirmation that the payment succeeded.
|
||||
|
||||
That's it — this site doesn't run a newsletter, doesn't sell anything
|
||||
directly, and doesn't use third-party analytics, ad trackers, or tracking
|
||||
pixels.
|
||||
This site doesn't run a newsletter, and doesn't use third-party analytics,
|
||||
ad trackers, or tracking pixels. Checkout with Stripe is the one
|
||||
third-party service in the loop, and it's there because payment processing
|
||||
and tax compliance genuinely can't be handled responsibly by a small press
|
||||
running its own servers.
|
||||
|
||||
## Why Two Squirrels Press collects it
|
||||
|
||||
- To respond to messages sent through the contact form.
|
||||
- To evaluate submissions sent through the submissions form.
|
||||
- To fulfill book purchases (send your download link) and handle any
|
||||
refund requests.
|
||||
|
||||
## What Two Squirrels Press doesn't do
|
||||
|
||||
- Two Squirrels Press doesn't sell or rent your information to anyone.
|
||||
- Two Squirrels Press doesn't share it with third parties except the
|
||||
infrastructure providers necessary to run this site and deliver that
|
||||
email — none of whom get to use it for their own purposes.
|
||||
infrastructure providers necessary to run this site, deliver that email,
|
||||
and process a payment — currently: Stripe, for payment processing — none
|
||||
of whom get to use it for their own purposes.
|
||||
|
||||
## Your control over it
|
||||
|
||||
- **Deletion**: reach out through [the contact form](/contact/) and Two
|
||||
Squirrels Press will delete your information from these systems.
|
||||
Squirrels Press will delete your information from these systems. (Stripe
|
||||
keeps its own transaction records as required by law and its own
|
||||
policies — that retention isn't something Two Squirrels Press controls.)
|
||||
|
||||
## Security
|
||||
|
||||
Your information is stored on infrastructure Two Squirrels Press controls
|
||||
directly, not handed off to third-party SaaS platforms. That doesn't make
|
||||
it invulnerable — no system is — but it does mean there's exactly one place
|
||||
your data lives, and one party accountable for it.
|
||||
Most of your information is stored on infrastructure Two Squirrels Press
|
||||
controls directly. The one exception is payment processing: Stripe, acting
|
||||
as merchant of record, handles your card details and tax compliance
|
||||
directly, and Two Squirrels Press never sees or stores your card number.
|
||||
That doesn't make any of this invulnerable — no system is — but it does
|
||||
mean there's exactly one clearly accountable party for each piece of your
|
||||
data.
|
||||
|
||||
## Changes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user