Privacy Policy
What we collect, and what we do with it
This policy describes the personal information Greensburg Times actually collects. The site is published by Offsides Entertainment LLC. We do not sell personal information.
Event email alerts
The event alerts form asks for your email address. Your name is optional. You also choose a frequency (as soon as an event is published, once a day, or once a week) and which event types you want. If you leave the types blank, the alerts cover every type.
We store that in our database, in the subscribers table. A new signup is not active until you confirm it. We email you a confirmation link from events@greensburgtimes.com through Resend. The alert starts only after you click that link. If you were already unsubscribed and sign up again, we send a new confirmation. If a confirmation is still waiting, we send the same link again.
Why: you asked for the alerts. Every alert email has an unsubscribe link and a link to change frequency and event types. Unsubscribing marks the row unsubscribed. We keep the row so we know not to email you again. The link in the email is the key to that subscription. Do not forward it.
Account-page newsletter
If you are signed in, the account page can show a separate newsletter box. That form sends your email address to Buttondown, which runs that list. We do not copy that signup into our subscribers table. Buttondown handles unsubscribe for that list. The box says so on the form.
Why: you submitted the form.
Corrections
The corrections form asks which page is wrong and what is wrong. A suggested fix, your name, and your email are optional. A hidden field is there to catch spam. If that field is filled in, we mark the submission as spam and do not treat it as a correction. A link in the description, the suggested fix, or the name is saved as spam the same way. Submissions that arrive too fast, or too often from the same network, are counted and not stored.
Corrections we accept, and ones marked spam, are stored in the corrections table. Only signed-in editors can read them through the admin tools. We do not automatically email you back, and spam is not sent to editors as a new correction. The network count is a hash of the address, not the address itself. Why: you sent the note so we can correct the site.
Event submissions
The event form asks for the event name, dates, place, and description. Organization, your name, your email, a link, a cost, and event types are optional. The same kind of hidden spam field applies. If it is filled in, we reject the submission. A link in any field other than the event link is saved as rejected. Submissions that arrive too fast, or too often from the same network, are counted and not stored.
We store the submissions editors review, including ones saved as rejected. If an editor approves a pending submission, we publish an event. Your name stays on the submission. A contact email may be copied onto the event record for editors. Visitors cannot read event contact emails or phone numbers from the public events API, and the event page does not show them. Why: you asked us to consider listing the event.
Directory contact
A published directory listing can show a contact form only after an editor records that the person or organization agreed, when they agreed, and that the method is email. The default is no form. The form asks for your name, your email, and a message. A hidden field is there to catch spam. Messages that arrive too fast, too often from the same network, too often for that listing, or with more than two links are counted and not stored.
A message we accept is stored in the contact messages table: your name, your email, the message, which listing it was for, and a hash of your network address. We do not store the network address itself. We email the listing through Resend from events@greensburgtimes.com. That email does not include your email address, and the page you used does not show theirs. If they reply, the reply is emailed to you from the same address and does not include their email address. The reply link, the stop link, and the takedown link in their email are signed. They do not contain an email address. Stopping messages or taking the listing down happens when they submit that page, before another message is accepted.
A report is stored in the contact reports table. Editors can block a sender. The block list stores a hash of the email or network, not the address itself. We do not turn directory addresses into a mailing list, and we do not send one message to more than one listing. Why: you asked us to pass a message along, or the listing asked us to stop.
Accounts
You can sign in with Google or Apple. We store your email, name, profile image URL, which provider you used, and that provider's account id. The account record also holds a random password you never see. You sign in with Google or Apple, not with that password. You can change your display name on the account page. You cannot change the email here. It stays the one from the provider.
Signing in sets an essential session cookie so you stay signed in, plus short-lived cookies used during the Google or Apple handoff. Editors who use the admin get a separate Payload session cookie. Why: you created an account so we can keep your name and, if you vote, your votes.
If Google gives us a profile photo URL, your browser loads that photo from Google when you open your account page.
Fish-fry votes
If you vote in the fish-fry bracket, we store your account id, the matchup, and your pick. The bracket page shows vote totals. The vote rows, including the account id, are not on the public API. Account records are not public.
Why: you signed in and voted.
Daily game scores
If you finish Tapped Out and post a score, we store your account id, the puzzle day, the score our server calculated, a public display name, and the move log that produced the score. The leaderboard shows that display name, the score, and the words you played. It does not show your email. The move log is not on the public leaderboard.
Why: you signed in and posted a score.
Information we publish
We also publish information we gathered from public sources, such as school board names and official contacts, and phone numbers for fish-fry listings. That is not information you typed into a form. If a listing about you or your organization is wrong, use the corrections form.
Analytics and logs
Every page loads Vercel Web Analytics and Vercel Speed Insights. They record pages people open, referrers, browser and device type, and performance timings such as how fast a page loads. We use them to see which pages are used and whether the site is slow. They do not use cookies, and we do not use them to build an advertising profile.
We do not use Sentry or another error-tracking service. The host, Vercel, keeps request logs, which can include your IP address, browser, the page you requested, and a search term you type on the home page. We use those logs to run and protect the site. Vercel keeps them on its own schedule. We do not copy them into a separate log store.
Why: we need this to operate the site.
Cookies and on-device storage
We do not use advertising cookies or analytics cookies. The cookies we set are the sign-in cookies described above.
Your browser stores two preferences in local storage, not in cookies: the theme (gbt-theme) and whether the sidebar is open (gbt-sidebar-open). They stay on your device. We do not receive them as form fields.
Maps, weather, and fonts
When you open the county map, the fish-fry map, or the Christmas lights driving-tour map, your browser loads map tiles from OpenStreetMap. OpenStreetMap sees your IP address and the tiles you request. We do not send your account or email with those requests.
The weather page loads a radar image from the National Weather Service at radar.weather.gov. Your browser requests that image, so the Weather Service sees your IP address. The forecast text is fetched by our server from api.weather.gov. That request comes from our host, not from your browser.
The typefaces are included with the site. Your browser does not contact Google Fonts, or any other font host, to read a page.
Christmas light nominations
The lights nomination form is open November 16 through 11:59 p.m. Eastern Time on December 10, 2026. It asks for your name and email, the municipality, a street or neighborhood, an optional exact address, optional viewing hours, whether you own the display, whether you have permission to show the exact address, a photo you took, and a checkbox that you grant Greensburg Times a license to publish that photo.
The street or neighborhood can be shown publicly if an editor approves the display. The exact address is shown publicly only if you check the permission box. Otherwise editors keep the address, and the public map uses a pin about 150 meters from the house. Pending and rejected nominations are not on that map. Your name and email stay with the nomination for editors. They are not published, and we do not email you a receipt.
The photo is stored privately until an editor approves the nomination. Before we store it, we remove the photo's metadata, including GPS. An approved photo is copied into the public media library. A pending photo is not served on the public media address. Why: you asked us to consider the display for the bracket.
Photos and files
Files uploaded by editors, such as photos, are stored in Vercel Blob. A published image can be loaded by anyone who opens the page that uses it. The lights nomination form is the only public form that accepts a file. The other public forms do not.
Who receives personal information
We share it only with the services that do the jobs described above:
- Neon, which hosts the Postgres database (accounts, subscribers, corrections, event submissions, light nominations, votes, and the rest of the site data).
- Vercel, which hosts the site, stores uploaded media, keeps request logs, and provides Analytics and Speed Insights.
- Resend, which sends event-alert, confirmation, and directory relay email.
- Buttondown, if you use the newsletter box on the account page.
- Google and Apple, when you sign in with them, and Google again if your browser loads a Google profile photo.
- OpenStreetMap, when you open a map.
- The National Weather Service, when you open the radar, and when our server fetches the forecast.
If a law, court order, or other legal duty requires it, we may have to share the information that duty covers.
How long we keep it
We do not automatically delete subscriber rows, including ones that never confirmed or that unsubscribed. We also do not automatically delete corrections, event submissions, directory messages, light nominations, accounts, or votes. We keep them until we no longer need them to run the site, or until you ask us to delete them and we can do that without breaking a record we are required to keep.
Access and deletion
Email contact@gbgtimes.com to ask what we have about you, to correct it, or to delete it. Tell us the email address you used so we can find the row. There is no self-serve download button. We will respond to the address you write from, or the address on the record.
Unsubscribing from event alerts is separate from deletion. Use the link in an alert email for that. Buttondown has its own unsubscribe for the account-page newsletter.
We do not sell personal information
We do not sell personal information. We do not share it for cross-context advertising. The site does not run third-party ad trackers.
Children
The site is a general-audience local news site. It is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe we have, email us and we will delete it.
Do Not Track and Global Privacy Control
We do not detect the Do Not Track browser setting or the Global Privacy Control signal. Analytics and Speed Insights still load. They do not use cookies, and we do not use them to follow you across other sites or to advertise to you.
Changes
When this policy changes, we update the date at the top. We do not email the subscriber list about a policy change unless we decide to, separately, and say so.
Contact
Offsides Entertainment LLC
contact@gbgtimes.com
Questions: contact@gbgtimes.com