Privacy Policy
Last updated: August 24, 2026.
Beta privacy note. Larkspin is still evolving. This page describes how the current beta handles your information, in plain language. If those practices change, we will update this notice.
This Privacy Policy explains what Larkspin (“Larkspin,” “we,” or “us”) collects, why we use it, when it is shared, and the choices you have. It applies to larkspin.com and the Larkspin beta service (the “Service”).
Who this applies to
Larkspin is only for people who are 18 or older. People under 18 may not use the Service, create an account, make a purchase, or submit information to Larkspin. We do not knowingly collect personal information from anyone under 18. If you believe a person under 18 has provided information to Larkspin, please contact us so we can remove it.
Information we collect
- Account information. If you create an account, Supabase handles your email address, password, and sign-in session. Larkspin does not receive your plaintext password.
- Your story content. Worlds, character details, choices, typed actions, and prior story text are sent through Larkspin’s server to our AI provider when a chapter is generated. If you use Larkspin without an account, your library is stored in that browser. If you sign in, stories you save or sync are also stored in your cloud library.
- Payment records. Stripe processes purchases. Larkspin does not receive or store your full card number. We keep the purchase identifiers, amount, currency, status, story balance changes, and related records needed to fulfill and reconcile purchases, handle refunds, and provide support.
- Product activity. We record limited events such as choosing a world, starting or finishing a story, and beginning or completing checkout. These events are associated with your account when signed in or a pseudonymous identifier otherwise. They do not include your story prose.
- Beta feedback. If you submit feedback, we keep what you send along with details such as your beta group, rating, reading progress, and whether you would consider paying. Story text is not automatically attached to feedback.
- Technical records. We process information needed to operate and protect the Service, including IP addresses, request details, rate-limit counters, error information, and abuse reports. Stored abuse-report identifiers use a salted hash of the reporter’s IP address.
- AI usage records. For each generation, we record operational details such as the request, account or story identifier when available, model, status, and token counts. These usage records do not include your story prose.
How we use information
- Generate stories, keep your place, save your library, and sync signed-in libraries across devices.
- Process purchases, grant stories, reconcile payments, issue eligible refunds, and provide support.
- Operate and secure Larkspin, including rate limiting, troubleshooting, fraud prevention, and abuse review.
- Understand how the beta performs and improve the reading experience.
- Meet legal obligations and enforce our Terms.
AI generation
Larkspin currently uses Anthropic to generate story text and, when enabled, cover art. The context needed for a generation—including your scenario, character, prior story, choices, and typed actions—is sent to Anthropic’s API. Please do not put sensitive personal information such as government identifiers, payment details, health information, or precise location data into a story.
Service providers and third parties
We use these providers to run the beta:
- Supabase for accounts, authentication, cloud libraries, purchase ledgers, product events, and operational records.
- Stripe for payment processing. Stripe handles card details under its privacy policy.
- Anthropic for AI story generation and optional AI-generated covers.
- Railway for application hosting and infrastructure.
We do not sell your personal information or use third-party advertising trackers. We may disclose information when required by law or when reasonably necessary to protect Larkspin, our readers, or others.
Cookies and local storage
Larkspin uses browser storage to keep you signed in, maintain an on-device library, and remember reading preferences. We do not use advertising or cross-site tracking cookies.
Sharing and published stories
Your cloud library is private to your account unless you choose to publish a story. Anyone with a published link can read that story until you unpublish it. Copies or search-engine caches may remain after a link is removed. Readers can report published stories, and we may remove them for safety, legal, or operational reasons.
Your choices and rights
The account menu lets you export your Larkspin data or permanently delete your account. Account deletion removes your account, cloud stories, and Larkspin-hosted public shares. You can clear stories stored only on your device through your browser’s site-data controls. Some payment, fraud-prevention, security, or legal records may be retained when required and separated from your active account where practical.
Depending on where you live, you may also have rights to access, correct, delete, or receive a copy of your information, or to object to or restrict certain uses. Contact us to make a privacy request.
Data retention
We keep account and cloud-library data while your account is active. Product activity and AI usage records are normally deleted after 180 days; rate-limit buckets after 48 hours; abandoned, uncharged generation sessions after 24 hours; and beta feedback and resolved abuse reports after 365 days. Open abuse reports remain until they are resolved. We retain payment records and the immutable story-credit ledger as needed for fulfillment, reconciliation, refunds, tax, fraud prevention, and legal obligations. Published stories remain available until you unpublish them or delete your account, subject to copies or caches outside our control.
International transfers
Larkspin’s providers may process information in countries other than the one where you live. Their privacy notices describe their locations and transfer practices.
Security
We use measures including encrypted connections, access controls, row-level database security, and server-held credentials to protect your information. No online service can guarantee perfect security. If a data breach requires notice, we will notify affected readers and regulators as required by law.
Changes to this policy
We may update this policy as the beta evolves. We will change the “Last updated” date and provide a prominent notice if a change materially affects how we use your information.
Contact
For privacy questions or requests, email readlarkspin@gmail.com.