Like a movie trailer, but for books. Watch, listen, or read along, then go as deep as you want.
Great lessons shouldn't depend on spare time, money, or how you learn. Free in 8 languages, for everyone.
Last updated: November 5, 2026
StoryShots ("we", "our", "us") is committed to protecting your privacy. This Privacy Policy explains what information we collect, how we use it, and your rights regarding your data.
It covers everything StoryShots runs: the reader at app.getstoryshots.com, the website and blog at getstoryshots.com, and the StoryShots apps for iOS and Android. Where a section only applies to one of them, it says so. StoryShots is operated by Parsida AB, Sweden.
When you create an account, we collect your email address and display name through Google, Apple, or email sign-in powered by Firebase Authentication. We do not store your Google or Apple password. On getstoryshots.com, membership accounts are handled by MemberPress on our WordPress site and use the same email address.
If you buy StoryShots, we may send you a small number of service emails about your purchase and, at most once, ask you to rate the app. Every such email has an unsubscribe link.
If you use StoryShots, we may also email you about your own reading progress. Every such email has an unsubscribe link.
We collect information about how you use StoryShots, including:
Payments are processed by Stripe (web), Apple (iOS), and Google (Android). We never see or store your card number. We keep the transaction record: what you bought, when, the amount, and the email it belongs to, so we can grant access and handle refunds.
We use analytics to understand how our service is used: page views, general geographic region, device type, and referral source. We do not sell your data.
On the reader app at app.getstoryshots.com, we count arrivals on our own server: the campaign labels in the link you followed, the site that referred you, whether you are on a phone or a desktop, your country, and the day and hour. No cookie, no identifier, no IP address, and nothing is read from or written to your device, so this runs for every visitor and needs no consent. We use it to see which channels bring readers, for example how many people arrive from our podcast.
The reader app also uses PostHog, hosted in the EU, to see how the reader gets used: which pages people open, whether they start and finish a summary, and where they stop on the way to buying. If you're in Europe, it only starts after you press Accept in the cookie banner. Elsewhere it runs unless you turn it off with the Cookie settings link in the footer or on your Account page. PostHog receives the path of the page you're on (never the part of the address after a question mark, so codes and sign-in links stay out of it), named steps such as "summary opened" or "checkout started", a random id kept in your browser, and your StoryShots account number once you sign in. Never your email or your name. It also records sessions so we can see how pages behave for real readers: what's on the screen, and where people click and scroll. Anything you type into a form is hidden in those recordings, and so are email addresses shown on the page. Admin pages are never counted or recorded. PostHog keeps this data for the retention period of our PostHog plan. You can read how PostHog handles data at posthog.com/privacy.
On getstoryshots.com and on the reader at app.getstoryshots.com, Google Analytics and Google Ads run through Google Tag Manager, and the Meta Pixel measures whether our Facebook and Instagram ads lead to sign-ups and purchases. They wait for your choice in the cookie banner. On the reader, in Europe nothing loads until you press Accept, and elsewhere they run unless you turn them off in Cookie settings or your browser sends a Global Privacy Control signal. Meta receives the page you are on and the type of event (a page view, a sign-up, a purchase), never the text of what you read. On getstoryshots.com, a purchase or sign-up also sends Meta a hashed version of your email so the conversion can be matched to an ad. The reader never sends Google or Meta your email, your name or your account number: a purchase carries the plan, the amount and the order number, and a sign-up only says which sign-in method you used.
In the StoryShots app for iPhone and iPad, iOS asks once whether StoryShots may track you. If you allow it, two things happen. The app's Meta SDK may use your device's advertising identifier and tell Meta when you start a free trial, pay for Premium or renew, and our server reports the same events through Meta's Conversions API, so we can see which of our Facebook and Instagram ads lead to purchases. Meta receives the type of event, the plan, the amount and currency, the time, the store's order number, and hashed versions of your email, your StoryShots account id and your country. Never your name, your IP address or what you read. If you choose Ask App Not to Track, or change your mind later in your iPhone's Settings, the advertising identifier stays off, the app sends Meta none of the trial, purchase or renewal reports described above, and our server reports nothing. The app still sends Meta a few basic events with no identifier that could track you, for example that a paywall was shown or that a purchase went through, and the next update stops those too unless you allowed tracking. The Android app sends Meta only two basic events, opening the app and opening a book, with no advertising identifier.
On the free plan, the iOS and Android apps show ads from Google AdMob, which can also serve ads from Meta Audience Network. The ad networks receive your device type, your approximate location and which ads you saw and tapped. On iPhone they only get your advertising identifier if you allowed tracking, and in Europe Google's consent form asks you before the first ad is requested. Premium members see no ads.
We use the information we collect to:
StoryShots integrates with the following third-party services, each with their own privacy policies:
| Service | Purpose | Data Shared |
|---|---|---|
| Firebase Authentication (Google) | User sign-in on the app and the website | Email, display name |
| Stripe | Web payments and subscriptions | Email, amount, card details entered directly on Stripe's checkout |
| Apple App Store and Google Play | In-app purchases and subscriptions, managed through RevenueCat | Purchase receipts and an anonymous app user id |
| MemberPress (WordPress) | Membership accounts on getstoryshots.com | Email, name, membership status |
| Google Books API | Book metadata and covers | Book search queries |
| ElevenLabs | Text-to-speech audio generation | Summary text for narration |
| Cloudflare | Content delivery, security, and file storage (R2) | Request metadata (IP address, browser type, page URL) as it passes through; generated audio files and cover images |
| PostHog (EU cloud) | Product analytics and session recordings on the reader app at app.getstoryshots.com (in Europe only after you accept analytics; elsewhere until you turn it off) | Page paths without query strings, named events, a random browser id, your account number after sign-in, session recordings with form inputs and on-page emails hidden |
| Amplitude | Product analytics in the iOS and Android apps (only after you accept analytics) | Feature usage events, device type, country |
| Google Analytics, Google Ads and Google Tag Manager | Website analytics and ad measurement on getstoryshots.com and app.getstoryshots.com (in Europe only after you accept; on the reader elsewhere until you turn it off) | Page views, clicks, scroll depth, approximate location, device type, and the plan, amount and order number of a purchase |
| Meta Pixel and Conversions API (Meta Platforms Ireland) | Advertising measurement and remarketing for getstoryshots.com and app.getstoryshots.com (in Europe only after you accept advertising cookies; on the reader elsewhere until you turn them off), and, in the iPhone app, reporting of trials, purchases and renewals from the app's Meta SDK and from our server (only if you allow tracking) | Page URL, event type, browser and device information, the _fbp cookie, hashed email on sign-up or purchase; for iPhone app trials, purchases and renewals, the plan, amount, order number, the advertising identifier, and hashed email, account id and country |
| Google AdMob and Meta Audience Network | Ads on the free plan in the iOS and Android apps | Device type, approximate location, which ads were shown and tapped; on iPhone the advertising identifier only if you allowed tracking |
| Loops | Transactional and newsletter email | Email address, first name, which emails you open |
| Goodreads | Book list import (optional) | Your Goodreads reading list (when you initiate import) |
Google sign-in prompt: if you are signed out on app.getstoryshots.com in Chrome, Edge or another Chromium browser, we may show Google's own sign-in prompt, loaded from accounts.google.com. In the EU it only loads after you accept cookies. Google shares your email address and name with us only if you pick an account in it.
We run our own partner program for creators who recommend StoryShots, with no outside affiliate service. If you join it, we keep your name, the email you sign in with, your PayPal email, your country, your partner code, what you told us about how you'd promote StoryShots, and what you've earned and been paid. We use that to run the program and pay you. Commission and payout records are kept for 7 years because Swedish bookkeeping law requires it. The rest of your partner profile is deleted 12 months after you leave the program.
If you buy after clicking a partner's link, the record of your purchase notes that partner's code so we can pay them. Partners see the amount and the date of a sale, never your name or email. Until we close the old affiliate program on getstoryshots.com, its WordPress plugin, which runs on our own site, still records which affiliate referred a purchase made there.
Your data is stored on secure cloud infrastructure. We use industry-standard encryption for data in transit (HTTPS/TLS) and implement access controls to protect your information. While no system is perfectly secure, we take reasonable measures to protect your data from unauthorized access, alteration, or destruction.
We use essential cookies for authentication (session management) and local storage to save your listening progress for offline access. On getstoryshots.com, essential cookies also keep you logged in to your membership and remember your cookie choice.
Analytics and advertising cookies are only set after you accept them in the cookie banner (outside Europe, where the reader shows no banner, PostHog's, Google's and Meta's are set unless you turn them off in Cookie settings). Our own visit counting on the reader app sets none. On the reader, PostHog keeps a first-party cookie and a local storage entry, both named after our PostHog project (they start with ph_), holding the random id described above. Turning analytics off deletes them. We do keep one first-party cookie for 90 days that remembers which campaign first brought you to the reader, so a later purchase can be credited to it. It holds campaign labels only, never an identifier. If you arrive through a partner's link we also keep a second first-party cookie for 30 days that remembers that partner's code, so a purchase you make on the web can be credited to them. It holds the code and the date of the click, nothing about you. The Meta Pixel sets the _fbp cookie for 90 days once you accept advertising cookies. When you turn them off on the reader, it deletes the Google Analytics (_ga), Google Ads (_gcl_) and Meta (_fbp, _fbc) cookies. You can change your choice at any time from the cookie settings link in the footer of getstoryshots.com or the reader, or the Privacy section in the app's Settings, and you can control how Meta uses data from websites at facebook.com/adpreferences/ad_settings.
When you make a choice in the cookie banner on the reader, or change it in Cookie settings, we also write one line to our own server so that we can show that consent was given or refused. It holds a random reference that is stored together with your choice in your browser, the choice itself, which version of the cookie banner text you were shown, the language the banner was shown in, whether we treated you as a visitor from Europe, whether your device reported itself as an iPhone or iPad, an Android device or a computer, the time, and your account number if you were signed in. It never holds your IP address or a browser fingerprint. We keep these lines for three years and then delete them. If you delete your account, the account number is removed from them.
Depending on your jurisdiction, you may have the following rights regarding your personal data:
If you are in the EU or EEA, our legal basis is the contract with you for account and purchase data, your consent for the analytics and advertising tools that store data in your browser, and our legitimate interest in counting visits without identifying you and in keeping the service secure. You can complain to your local data protection authority; ours is the Swedish Authority for Privacy Protection (IMY).
To exercise any of these rights, please contact us at the email address below. We will respond to your request within 30 days.
We retain your account data for as long as your account is active. If you delete your account, we will remove your personal data within 30 days, except where we are required by law to retain certain information, such as purchase records for accounting. Anonymized usage data may be retained for analytics purposes.
StoryShots is not directed at children under the age of 13, or under 16 in the EU and EEA unless a parent or guardian has agreed. We do not knowingly collect personal information from children under these ages. If you believe we have collected data from a child under these ages, please contact us and we will promptly delete it.
Your data may be processed and stored in countries outside your country of residence, including the United States. Transfers from the EU rely on the providers' standard contractual clauses or their participation in the EU-US Data Privacy Framework.
We may update this Privacy Policy from time to time. We will notify users of material changes by posting the updated policy on this page with a revised "Last updated" date. Your continued use of the service after changes constitutes acceptance of the updated policy.
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us at support@getstoryshots.com.
Parsida AB, Sweden. Data controller for StoryShots.
