Privacy policy
Last updated 2026-11-16
GridTicker shows you scores, prices, headlines and flights. To do that it needs very little about you, and this page says exactly what. It covers the GridTicker website, the web app, the Android and iPhone apps and GridTicker LED panels.
Who we are
GridTicker is run by GridTicker LLC, organized in South Carolina ("we", "us"). You can write to us at support@gridticker.com or at PO Box 85954, Lexington, SC 29073.
What we collect
Your account
- Your username (which may be an email address) and display name.
- Your password, stored only as a one-way hash. We can't read it.
- When you last signed in.
- That you agreed to our terms of use and this privacy policy: when, which version (the date at the top of each), and where - the signup form, or checkout when you subscribe - so we can show what you agreed to. It goes when your account does.
- The email address you signed up with, if you signed yourself up. We send it a welcome with a link to confirm it, a note with a few tips a couple of days into your free trial, and a reminder in the trial's last day. If you haven't been back by the day after you sign up, we send one note with ideas for where to put it; and on up to two days a team you follow plays, if you haven't had your ticker open that day, a note before the game. Never more than one of these a day. If your trial ends without a subscription, we write once more, two weeks before we remove the account. You can sign in with it too, and if you ask for a password reset before you've confirmed it, we send it a link to confirm it first.
- A recovery email address, if you add one, so a forgotten password can be reset by email. It only counts once you follow the confirmation link we send to it.
- News about GridTicker itself, now and then - a new app, for instance - sent to your recovery address, or to the address you signed up with if you have no recovery address.
- Every email we send has an unsubscribe link at its foot. It stops everything we would write to you unasked - the trial's notes and the news. What you ask for yourself, like a password reset, still arrives.
- The links we email you to confirm that address or reset your password, and the address each was sent to, while each link can still be used.
If you pay
- The reference Stripe gives you as its customer, and the date your service is paid up to. Your card and billing address go to Stripe, not to us: we never see or store a card number.
- If you subscribe in the iPhone app, through the App Store: what Apple signs about your subscription, which the app and Apple's servers both send us - its App Store reference, the product, when it was bought and when its current period ends, whether it will renew, any refund, the country of the store and the price, and a code standing for the GridTicker account it was bought for. We keep the reference, the date it is paid up to, whether it renews, when Apple last told us, and whether it was a test purchase. Apple takes the payment: we never see your card or your Apple Account.
- If signing up asks for a card first, the username, email address and password (as a one-way hash) you chose wait until the payment goes through, and then become your account.
If you buy an LED panel
- Your order: what you bought, what you paid and anything refunded, and where it has got to - with the email address, and the name and address it ships to, that you give on Stripe's checkout page, and the carrier's tracking number. You don't need an account to buy a panel; if you are signed in when you do, the order is tied to your account as well.
- The code that comes with each panel for its free months, and which account used it.
If you join the launch list
The front page offers to tell you when LED panels go up for sale. If you leave an address there, we keep that address and nothing else — no name, no IP address, no record of which pages you looked at. We write to it once, when panels go up for sale, and you can remove it at any time with the link at the foot of our email, or by writing to support@gridticker.com.
Your settings
- The leagues, teams, feeds and outlets you follow, and how and when each ticker appears.
- Stock symbols on your watchlist, and any aircraft you choose to follow.
- Your home location, if you give one, so the flights ticker can show the planes over you. It comes from an airport you pick, or from your device's location if you press "use my location" (your device asks you first). It is stored to about 11 meters, which is precise enough to find a house.
- The link to your photo folder, if you add one, so your browser, your phone and your LED panels can show the photos in it: the Google Drive folder you shared with "Anyone with the link". We keep the folder's ID from the link, and how many photos to show - never the photos themselves.
If you share a household
- Who is in it: which account asked which into its household, whether each said yes, and whether each member's teams and lists show on the household's panels.
- An email address a household invitation was sent to, when no account has it: so the link in the email can make the account; and whether that address declined it, or asked its sender to send no more.
Modes
- The modes saved for your panels: each one's name, the panel settings in it, where and when it comes on, whose teams it shows, who made it, and who turned it on and when.
Your LED panels
- Each panel's name, time zone, software version and how its display is wired.
- What a panel reports when it is set up: its device name, model and address on your home network.
- Hardware readings, stored about once a minute: temperature, memory, storage, processor load, Wi-Fi signal strength, time since it started, and power warnings.
- If you ask us for help, we may ask a panel for its recent log or a network diagnostic. The diagnostic includes the name of the Wi-Fi network it is on, the addresses of your router and of other devices your panel can see on your network, and connection timings.
Technical records
- Our servers log each request: your IP address, the address requested, your browser or device type, and the time. A phone widget's address includes its access code, so that ends up in these logs too.
- To slow down password guessing, we count sign-in attempts by username and by IP address for 15 minutes.
- When your account last had its ticker open, in a browser or the app, and on how many days it has been open, so we can tell whether it is still working for you. Only the latest time and the number of days are kept.
- When your account first asked the support chat a question, if it has, so we can tell how many people find it. Never what you asked.
- A count of visits for each day: how many times our front page, the sign-in page and the sign-up form were opened, from how many different addresses, how many people signed up, and how many questions the support chat was asked, by how many accounts. Only the totals are kept. The same goes for trials: how many started on each day, and how many of those became subscriptions — a number for each day, which is kept when an account is deleted. To count an address or an account once a day it is held as a scrambled code — never the address or the account itself — for two days, and then deleted. When you arrive through a link we shared with a tag on it, such as
?ref=reddit, the same totals are also kept under that tag, so we can tell which places bring people. When you arrive without one, the tag is the kind of site your browser says sent you, such as a search engine, YouTube or Facebook, and never the page itself. The tag is part of the link you followed; nothing is stored in your browser for it. - If you were invited, the invitation has a private note from the person who sent it, which may include your name or email address.
We don't use advertising or anybody else's analytics — the daily count above is our own, and totals only — we don't track you across other sites, and we don't collect anything we haven't listed here.
If you tell us how you heard about us
The sign-up form asks when the link you followed doesn't already tell us, and you can leave it blank. If you answer, we keep the answer on its own — no name, no address, nothing joining it to your account — because counting what brought people is all it is for, and it is what we use instead of analytics. We won't pretend it is untraceable: on a quiet day an answer written a second after an account could be lined up with it by somebody reading both. It is simply not joined up, and nothing we do joins it.
How we use it
Only to run GridTicker for you: to show your ticker, sign you in, keep your panels working and updated, protect the service from abuse, and fix problems, including the ones you ask us to look into. We don't sell your information, and we don't use it for advertising or share it for anyone else's.
Who else receives it
The people in your household
If you're in a household, everybody in it sees who else is in it, by username, and its owner sees the username or email address of each person they asked. Its panels receive and show each member's favorite teams, watchlist, tracked flights and weather places, unless that member switches them off. Nobody in a household sees another person's settings page, password, email address or phone, and nothing is shared with anybody before they accept.
The companies that run our infrastructure
- Akamai (Linode) hosts our servers and database.
- Cloudflare carries all traffic between you and our servers, hosts this website, and forwards mail sent to our support address.
- Zoho sends our email, so it receives the address and each message we send to it.
Payments
Stripe takes our payments. When you subscribe, it receives your email address, and the card and billing address you give on its checkout page; it also uses that address to work out any sales tax. When you buy a panel, it also receives the address it ships to, which is what the sales tax on the panel is worked out from. The carrier we ship a panel with receives the name and address on its label. Stripe handles these under its own privacy policy. If you delete your account, we delete you as a Stripe customer too, which cancels your subscription; Stripe keeps its record of past payments.
Apple takes the payment when you subscribe in the iPhone app, under its own privacy policy. The purchase carries a code that stands for your GridTicker account - a random identifier that means nothing to Apple - so that what Apple signs says whose subscription it is. Apple bills, renews and refunds that subscription, and you cancel it with Apple, in your iPhone's Settings under your name, then Subscriptions. Deleting your GridTicker account doesn't cancel it.
Services our servers ask on your behalf
These see a request from our servers, not from you, but some requests include your information:
- adsb.lol receives the area around your home location, if you set one, and the aircraft you follow.
- hexdb.io and adsbdb.com receive airport codes you look up, and the flight numbers of planes near your home location, so we can find their routes.
- ESPN, Yahoo Finance, NASCAR and news outlets supply scores, standings, prices and headlines. What we ask them isn't about you, but the stock symbols on our watchlists are sent to Yahoo Finance.
- Anthropic answers the questions you ask the support chat. With each question it receives the conversation so far, your username and your settings, with your home location rounded to about 11 kilometers.
- Google Drive receives the photo folder you share, if you add one: our servers ask it for the list of files in that folder - each file's ID, type, date and checksum - so your browser and your phone know which photos to show, and your panels which to keep. They never ask it for the pictures.
Images and fonts your browser loads directly
When you use the web app, your browser fetches some images and fonts from other companies, which then see your IP address:
- ESPN: team and league logos, and player photos.
- flagcdn.com: country flags.
- Google: the web app's fonts (Google Fonts), and the small icons of news outlets (Google's icon service, which learns which outlets appear on your ticker).
- parqet.com: company logos beside stock prices.
- Google Drive: when Photos is on for your browser or phone, it loads small copies of the photos in your shared folder straight from Google, which then sees your IP address; nothing passes through our servers.
- YouTube, using its no-cookie player, for the setup video - only once you press play.
What your panel contacts
A panel talks to our servers. While it is being set up it checks it's online using Google's connectivity check. If it can't reach our servers, it gets scores straight from ESPN until it can, and ESPN then sees your home's IP address. Panels also set their clocks from public time servers.
A panel with Photos on downloads small copies of the photos in your shared Google Drive folder straight from Google, which then sees your home's IP address. The copies are kept on the panel's own SD card, never on our servers.
When the law requires it
We may disclose information if the law requires it, or to protect people from harm. We'll tell you if we're allowed to.
Cookies and storage on your device
- One cookie, which keeps you signed in. It lasts 30 days and renews while you use GridTicker. Scripts can't read it, and it is only sent to GridTicker.
- The web app keeps a copy of your last ticker on your device so it still works offline. Signing out removes it.
- While you link a new panel, a note about it is kept in that browser tab until the tab closes.
This website sets no cookies, and apart from the blog's articles and their pictures, it loads nothing from anyone else - except the setup video on the front page, and only once you press play: then YouTube's no-cookie player plays it, YouTube receives your IP address, and it may keep data in your browser under its own privacy policy.
How long we keep it
| Information | Kept |
|---|---|
| Your account, settings and panels | Until your account is deleted: when you delete it, or 90 days after a free trial that ended without a subscription. |
| When your account last had its ticker open | Until it is next open, or your account is deleted. |
| On how many days your account's ticker has been open | Until your account is deleted. |
| When your account first asked the support chat a question | Until your account is deleted. |
| Your Stripe customer reference and paid-up date | Until your account is deleted. |
| Your App Store subscription's reference, paid-up date and whether it renews | Until your account is deleted. |
| Your panel orders: what was bought, paid and refunded, and where it was sent | Seven years after the sale, as tax and warranty records - including after your account is deleted, when the order no longer names your account. |
| A signup that was never paid for | It expires after 24 hours, and is deleted the next time anyone starts a signup. |
| An address left on the launch list | Until we write to say LED panels are for sale, or until you ask us to remove it — whichever comes first. |
| The email address you signed up with | Until your account is deleted. |
| Modes | Until the person who made one, or the panels' owner, deletes it, or either account is deleted. One made in somebody else's household goes when you leave it. |
| Who is in your household, and what each person answered | Until you leave it or are removed, or either account is deleted. |
| An email address a household link was sent to | Until the link is used. One that runs out after 7 days is deleted the next time its sender sends a link, and a declined one when its sender clears it or sends that address another. One whose address asked its sender to send no more is kept until the sender's account is deleted, so none is sent. |
| Your recovery email address | Until you remove it or delete your account. |
| Links we email you, and the address each went to | Until the link is used. An expired link is deleted the next time any link is sent. |
| Panel hardware readings | 7 days. |
| The list of files in a photo folder you share | At most a day. |
| Your photos | Never stored on our servers. Your panel keeps its copies on its SD card until they leave the folder, you remove the folder, or the panel is reset or moved to a new owner. A browser or a phone keeps nothing beyond its usual cache of pictures it has shown. |
| A panel's diagnostic or log | Until the next one replaces it, or your account is deleted. |
| Server request logs | Replaced as they fill up: usually about two weeks, and less when we're busier. |
| Sign-in attempt counts | 15 minutes. |
| Daily visit, trial and support chat counts | Kept. They are totals, with nothing in them about you. |
| The scrambled codes that count an address or an account once a day | 2 days. |
| Support chat conversations | Not kept. A conversation exists only in the page you have open, and is gone when you close or reload it. If you ask the chat to pass something on, it emails us a summary, which we keep like any other email you send us. |
| Database backups | 30 days, then deleted. |
If you signed yourself up and your free trial ends without a subscription, we keep your account 90 days after its trial ends, in case you come back, and then delete it and everything in it. We write to the address you signed up with 14 days before, unless you've asked us not to email you; subscribing keeps it. An account with a panel, one that has been to our checkout, or one in somebody's household is never removed this way.
When you delete your account, it is removed from GridTicker right away. Copies in our backups are deleted as those backups reach 30 days old, and entries in our server logs as the logs are replaced.
Your choices and rights
- See and change your information in Settings, including removing your home location.
- Delete your account under Settings → Account, or see other ways.
- Ask us for a copy of your information, to correct something, or anything else about your data, at support@gridticker.com. We answer everyone, wherever you live, within 30 days.
Depending on where you live, you may have legal rights to access, correct, delete or move your information, to object to how we use it, and to complain to your data protection authority.
Children
GridTicker isn't meant for children, and we don't knowingly collect information from anyone under 13. If you think a child has an account, write to us and we'll delete it.
Security
Everything between you and our servers is encrypted. Passwords and access codes are stored only as one-way hashes. Only the people who run GridTicker can get into its servers. No system is perfectly secure, but we work to keep yours safe, and we'll tell you if something happens to your information.
The Android app
The GridTicker Android app shows the same web app as a browser does, so everything on this page applies to it. It keeps you signed in by storing the same cookie inside the app. It asks for no access to your location, contacts, photos or files: to give the flights ticker a home location from the app, pick an airport.
The iPhone app
The GridTicker iPhone app shows your ticker and your settings with the same pages as the web app, so everything on this page applies to it. Only its widgets and its living room switch are drawn by the app itself, and subscribing in it opens the App Store's own sheet. On top of that, it keeps a few things on your phone:
- The cookie that keeps you signed in, the same one the web app uses. The app's pages keep it in the app's web storage, as a browser does, and that is part of your phone's backups. Its widgets and living room switch use a second copy, kept in the iPhone's keychain for this device only: that copy isn't in your backups and doesn't move to a new phone.
- A widget link, which is how the app and its widgets read your scores. It is an access code the app asks our servers for once you're signed in, it can read your ticker and nothing else, and it is kept in the keychain the same way. We keep the code only as a one-way hash, with the link's name and when it was last used. Deleting your account stops it working.
- Your last scores and whether living room mode is on, where only the app and its widgets can read them, so they appear right away and still show something when you're offline. Your username is kept with them, so the app can say whose account it is.
Signing out deletes all of these from the phone, except the widget link's identifier (never its code), which the next sign-in uses to switch the old link off.
The app shows no team, league, news or company logos, flags or player photos - teams appear by name in their colors - so it doesn't fetch the images from ESPN, flagcdn.com, Google's icon service or parqet.com that the web app does. With Photos on for your phone, it loads your own photos from Google Drive, as the web app does.
The app asks for no access to your location, contacts, photos or files, and doesn't send notifications: to give the flights ticker a home location from the app, pick an airport. It contains no advertising or analytics code. If you subscribe in the app, you do it through the App Store: what that sends us is under If you pay, and what Apple does under Payments. If you have chosen to share analytics with app developers in your iPhone's settings, Apple sends us its crash reports and usage totals for the app, with nothing that names you.
Changes to this policy
If we change this policy, we'll update this page and the date at the top. If a change affects how we use information we already have, we'll tell you in GridTicker before it takes effect.
Contact
Write to support@gridticker.com, or to GridTicker LLC, PO Box 85954, Lexington, SC 29073.