TickerRelay provides website tickers and publisher support. This policy explains how we handle information when you visit our website, contact us, use publisher access, or connect a hosted ticker. Optional features described below apply only when enabled for your site.
Publishers control their own websites, article sources and visitors’ information. Their privacy notices apply to those activities. Our policy covers the information handled by TickerRelay.
Use our privacy request form to contact us about your information. You do not need an account.
Information we collect
Requests and support. We collect the name, email, website details, product or plan, coverage preferences, and messages you submit. We also keep the request reference, status and timestamps needed to respond.
Publisher access. We use your invited email address to confirm access. A required session cookie keeps you signed in for up to 12 hours. It is unavailable to browser scripts and restricted to same-site requests. The access code itself is not stored by the site; we check it against a protected hash.
Account sign-in. Where a page uses ChatGPT sign-in, we receive your account identifier, email and display name, and your full name if supplied by the sign-in service. This connection does not give TickerRelay access to your ChatGPT conversations.
Connection and security information. Hosting providers process network addresses, requested URLs, browser information and operational logs to deliver and protect the service. Our support and setup records use temporary one-way network hashes for rate limiting instead of storing raw network addresses in the request record. Publisher access login attempts use a temporary one-way network hash for the same purpose. Hosting logs are separate from those records.
Payments, when enabled. Stripe handles checkout and payment methods. TickerRelay keeps your approved site, plan, trial and subscription dates, payment status, accepted terms version, and Stripe customer, subscription and transaction identifiers. We do not store complete card numbers or security codes. The ticker service receives the site’s access permissions and expiry, not card details.
Do not send a full license key, activation token, password, signing key or payment-card details through our forms. Some familiar credential formats are blocked automatically, but you should remove all secrets and unnecessary personal information before submitting a message.
Ticker content
Free native WordPress mode. The plugin reads public posts on your own WordPress installation. In this mode it does not send those posts to TickerRelay or contact our sports service.
Hosted Scores. A connected WordPress server sends a site-bound feed credential, the site URL and the previous response identifier to authenticate the installation and select its coverage. That credential is encrypted in WordPress storage and is not sent to readers’ browsers.
Hosted embeds. We keep the site URL, permitted installation origins, display settings and agreed public RSS or Atom sources. We fetch and temporarily cache headlines, dates and original links. Readers’ browsers connect to our embed host, which processes the connection information needed to return the ticker. The public embed identifier is not a feed credential.
Reviewed updates. An approved item contains its headline or summary, source credit and link, relevant timestamps, and correction or expiry information. These details may appear in the configured ticker and its update page. Following an original source link takes the reader to that publisher’s website and privacy policy.
How we use and share information
We use information to answer requests, configure and deliver tickers, manage access and billing, investigate problems, prevent abuse and meet legal obligations. We do not sell personal information or use it for cross-site targeted advertising.
Service providers receive information needed for their part of the service. These include Cloudflare for website infrastructure and storage, OpenAI for hosted site and account features, Stripe when payments are enabled, and Resend when request-notification email is enabled. Email notifications contain a request reference and information needed to direct the operator to the request.
You can read the providers’ policies at Cloudflare, OpenAI, Stripe and Resend. Other hosting or email providers may process connection information or correspondence needed to operate the service.
We may also disclose information where necessary to comply with law, respond to valid legal process, investigate fraud, protect people or the service, or carry out a business transfer subject to applicable privacy obligations. We do not give publishers another publisher’s private account or support records.
Cookies and similar technologies
TickerRelay does not add advertising pixels or advertising cookies to its marketing pages. Essential cookies support publisher sessions, sign-in and security. Our hosting, sign-in and payment providers may use their own cookies when you interact with their features.
You can block or clear cookies in your browser, although sign-in may stop working. Declining optional features does not prevent you from downloading and using the native Free Stories plugin.
How long we keep information
Our routine retention target for support tickets is up to 24 months. Unconverted setup requests have a target of up to 12 months. They become eligible for deletion after 730 and 365 days respectively. Cleanup runs when new requests are processed, so eligible records can remain longer between cleanup runs. Security rate-limit records become eligible after about 48 hours and are also removed during later request processing.
Customer, billing and accounting records have separate retention needs. We keep them while needed to provide the service, comply with law, resolve disputes or prevent abuse. Contact us about a particular record; we will explain any reason it cannot yet be deleted.
Hosted article feeds use a short working cache. Reviewed content stops appearing when it expires or is corrected or retracted. Expired text is cleared from the receiving store; minimal identifiers and hashes can remain for retries and correction references. This does not erase the original publisher’s content, upstream editorial records, backups or copies already received by a reader. Deleting a support ticket does not automatically delete separate email correspondence or provider logs.
Your choices and privacy requests
You can ask what personal information we hold about you, request a copy, or ask for correction or deletion. Where applicable law provides additional rights, including withdrawing consent, portability, an authorized agent or an appeal, you may use the same contact route. We do not use account or visitor information to make automated decisions with legal or similarly significant effects.
Use the privacy request form, or choose “Privacy request or appeal” in Support, and describe your request. Include your site or ticket reference if useful, but no password or license key. We may need limited information to verify your identity or authority before disclosing or changing records.
We will respond within the period required by applicable law. If we cannot fulfill a request, we will explain why. To appeal, reply to that response or send a support request marked “Privacy appeal.” You may also contact your relevant privacy regulator or attorney general. If your request concerns a publisher’s own website records, contact that publisher first.
Security, location and children
We use access controls, encrypted connections and other safeguards appropriate to the information handled. No system can guarantee absolute security. TickerRelay is operated from the United States; service providers may process information in other countries where privacy laws differ.
Our accounts and setup services are intended for adult website operators. We do not knowingly collect personal information directly from children under 13 through those services. Contact us if you believe a child has submitted personal information so we can investigate and remove it where appropriate.
Changes to this policy
We will update the date above when this policy changes. If a change materially affects how we handle your information, we will provide any additional notice or choice required by law.