Privacy Policy

Last updated October 9, 2026

StoryScreen LLC (“StoryScreen”, “we”) makes software that churches use to show lessons and signage on their TVs. This policy explains what information we collect when churches and their teams use StoryScreen, how we use it, and the choices you have. It applies to the StoryScreen admin app, the players for TVs and computers, and the phone remote. Our Terms of Service also apply.

The short version: we collect what we need to run StoryScreen for your church, we don’t sell it, we don’t show ads, and the TVs collect nothing about the people watching them.

What we collect

Account information. Your email address and the name you give us when you set up your account. If you sign in with Google, we receive only your email address from Google. We also keep which churches and campuses you belong to, your role, who invited you, and when you last signed in.

Your church’s information. Your church’s name and logo, its campuses, rooms, screens, playlists and schedules, and the videos, images and YouTube links your team adds. We store this to run the Service for your church, and we don’t use your content for anything else.

Billing information. When an owner subscribes, Stripe collects the payment card and billing address. We never see or store full card numbers. We keep your subscription, its status and your Stripe customer reference, and if your church is tax-exempt, a note that its exemption is on file.

Screen information. Each paired screen tells us its app version, platform and device model, what it is showing, whether it is online, and how much of its content is downloaded. When you pair a screen, we briefly keep the IP address it connected from, to stop abuse of pairing codes. Screens have no cameras or microphones in StoryScreen, and collect nothing about the people in the room.

Product usage. We record actions in the admin app, such as signing in, adding a file, pairing a screen or subscribing, along with how many minutes each screen was on and playing each day. These records hold ids, counts and dates, not names or messages. We keep them in our own database to understand how StoryScreen is used and to fix problems. We don’t use third-party analytics or advertising tools.

Phone remote. The phone remote needs no sign-in. We record that a button was pressed and for which room, nothing about the person or their phone.

Feedback and support. When you send feedback or a bug report, we keep your message, email address, the page you were on and your browser type. If you let our staff sign in to your account to help you, we keep a record of what they viewed and changed.

Technical information. Like most websites, our servers and hosting providers log technical details such as IP addresses, browser type and the pages requested. When something breaks, an error report goes to our error-tracking provider and may include similar details.

Cookies

We use only the cookies StoryScreen needs to work: to keep you signed in, to finish signing in with an emailed code or Google, to remember which campus you chose and whether the sidebar is collapsed, and to run a support session you allowed. We don’t use advertising or tracking cookies. Because we don’t track you across other websites, we don’t respond differently to “Do Not Track” signals.

How we use information

  • To run StoryScreen: sign you in, store and convert your media, and keep your screens playing the right things.
  • To send the emails the Service needs, such as sign-in codes, invitations and notices about your account or subscription.
  • To bill subscriptions and calculate sales tax.
  • To answer support requests and feedback.
  • To keep StoryScreen secure, prevent abuse, and find and fix problems.
  • To understand how StoryScreen is used, so we can improve it.
  • To meet legal obligations.

Who we share it with

We don’t sell personal information or share it for advertising. We share it only with:

  • Service providers that run parts of StoryScreen for us, under contracts that limit how they use it: Railway (application hosting), Neon (database), Cloudflare (network, file storage and backups), Resend (email), Sentry (error reports), Stripe (payments and sales tax) and Google (sign-in with Google).
  • YouTube. When a screen plays a YouTube link your church added, it loads YouTube’s player, and Google may collect information such as the screen’s IP address under Google’s Privacy Policy. We use YouTube’s privacy-enhanced mode.
  • Your church. Owners and admins of your church can see their team’s names, email addresses, roles and activity in the account.
  • When the law requires it, or to protect the rights, property or safety of StoryScreen, churches or others.
  • A new owner of StoryScreen, if the business is sold or merged, who must keep protecting the information as this policy describes.

Where it's stored and how it's protected

StoryScreen stores data in the United States. We encrypt data in transit, store sign-in codes and screen tokens only as hashes, keep each church’s data separate from every other church’s at the database level, and limit who at StoryScreen can access it. We back up our database nightly and keep each backup for 30 days. No system is perfectly secure, but we work to protect your information and will notify you if a breach affects it, as the law requires.

How long we keep it

We keep your church’s information while its account is open. When an account is closed, we delete its content and data within 30 days, and backup copies expire within 30 days after that. We keep billing records as long as tax and accounting law requires. For people whose account closes with it, we keep only a one-way hash of their email address (which can’t be turned back into the address), with when they agreed to our terms and whether they had the free trial, so the trial stays one per person. Sign-in codes expire within minutes, and IP addresses from screen pairing are kept only briefly.

Children

StoryScreen is for the adults who run church ministries. It isn’t meant for children under 13 to use, and we don’t knowingly collect personal information from them. Children may watch the screens, but the screens collect nothing about who is watching. If your church uploads photos or videos of children, your church is responsible for having permission to show them, and we store them only to play them on your screens. If you believe a child has given us personal information, contact us and we’ll delete it.

Your choices

  • A church’s owners and admins can remove you from its team at any time.
  • You can ask us for a copy of your personal information, or ask us to correct or delete it, by emailing [email protected]. If your information belongs to a church’s account, we may involve the church’s owner.
  • Owners can close their church’s account in the admin app, under Church & rooms, or by emailing us.
  • We won’t treat you differently for using these rights.

Changes to this policy

If we change this policy in a way that matters, we’ll tell account owners by email or in the admin app before the change takes effect, and update the date at the top.

Contact

StoryScreen LLC, Oklahoma City, Oklahoma. Email [email protected] with any privacy question or request.