Skip to content
TNSTENNIS
NEVER STOPS
TNS — Tennis Never Stops
TNSTENNIS
NEVER STOPS
TNS — Tennis Never Stops
Inside the appTournament datesCourtsideYour questionsGet TNS
Terms of UsePrivacy PolicyFor iPhone · Android later
TNS / Fair play

YOUR DATA.
YOUR CALL.

02 / LEGAL

Privacy Policy / What helps us keep your tennis personal: the information we use, why we use it, and the choices you have.

Last updated: 11 November 2026ENGLISH
ON THIS PAGE
01Who we are02Information we handle03Why we use information04Advertising and purchases05YouTube videos and X posts06Service providers and sharing07Where information is processed08How long we keep information09Your choices and rights10Security11Children and younger users12Changes and contact
THE SHORT VERSION

No email sign-up is required. The iOS and Android apps save following with a guest profile; the website keeps follows in your browser. Both mobile apps use Firebase Analytics and Crashlytics. Subscriptions use the App Store on iOS and Google Play on Android; we do not receive your payment-card details. News uses YouTube API Services, and in-app embedded playback follows Google’s Privacy Policy. Here is what each service receives and the choices you have.

This summary is a guide. Please read the full document below.

01Who we are

This Privacy Policy explains how TNS (“we”, “us”) handles personal information in the TNS iOS and Android apps, including test versions, and on this website. Platform-specific practices are identified below: iPhone settings, Apple push services and App Store purchases apply to iOS; Google Play Billing applies to Android. Both mobile apps use Firebase Analytics and Crashlytics. The website has separate browser storage and opens news on the source platforms. The individual responsible for the service and for your information is identified in the contact details at the end of this policy.

02Information we handle

You can use TNS without giving us your name or email address. The mobile apps create a guest profile to save the players and tournaments you follow. This profile uses a random identifier, so it is not the same as anonymous use.

Using TNS on iOS

Information used by the iOS app
InformationHow we use it
Guest profile and followingIn the iOS app, a random guest identifier and the players, tournaments and matches you follow are saved on our servers. Your sign-in credential is kept in the iOS Keychain; our server stores a one-way hash of it to recognise authorised requests. Following is also cached on your device.
Settings on your deviceYour preferences, chosen avatar, recent views, alert choices and personal picks are saved on your device. Cross-device account sync is not available. Followed matches are also saved on our server, as described above.
Content you requestWhen you search, open a match or request your alerts inbox, we process the information needed to return it. This includes search text, filters, selected matches and alert types. Saving a choice on your device does not mean it is never sent with a request.
NewsTo choose news, the app sends our server the tours and platforms requested, your App Store country and, while a video is open, that video’s ID. The country and video ID are used for that request rather than stored. An authenticated request also identifies your guest profile so news can reflect the players and matches you follow. See YouTube videos and X posts.
App analyticsGoogle Analytics for Firebase receives events about use of the app: sessions, tabs, filters, follows, search-result interactions, news opens and playback, settings, alerts, Live Activities, ads and subscriptions. Events include a random app-instance identifier, event and session identifiers, device and app information, an approximate location derived from your IP address, and relevant choices, counts or content positions. Events do not include your name, email, guest credential or the ID of a YouTube video or X post you open. TNS does not collect IDFA or IDFV for this analytics. StoreKit purchase events include transaction and product information. During purchase synchronisation, our server receives the app-instance identifier so it can associate subscription activity with that installation for revenue analysis. These records are pseudonymous, not anonymous.
Live Activities and widgetsIf you start a Live Activity or add a TNS widget, the app sends us the update token that iOS creates for it, the match concerned and, for widgets, your time zone. We use them to send score updates through Apple’s push service. Tokens are stored encrypted.
Match alertsIf you allow notifications: your iPhone’s push token for TNS, and the players and matches you turned alerts on for, with the kinds of alert you chose. Used only to send those alerts. Kept on our server. Turning your alerts off removes the list. The token is deleted 90 days after the app last renewed it, or with your profile.
Crash reports and reliability sessionsFirebase Crashlytics collects crash diagnostics to help us find and fix faults: crash traces, the technical state of the app, device model, iOS and app version, and random installation identifiers. Reliability-session data helps measure crash-free use. We do not attach your guest credential. When Firebase Analytics is active, analytics events and their parameters from the session can also appear in a crash report as breadcrumbs.
PurchasesIf you subscribe to TNS Pro, we store App Store transaction information linked to your guest profile, as described below.
Age informationTNS can use an age range shared by Apple and, where needed in the EEA, the UK and Switzerland, your answer to a year-of-birth question. You can choose not to give a year. The year or age range stays on your iPhone; advertising requests receive the applicable age-protection settings, not your birth year. TNS also uses this information to restrict analytics and in-app YouTube playback where described below.
Technical informationOur infrastructure receives your IP address and request details to deliver content and protect the service against abuse. Hosting logs may also contain timestamps, requested paths and device or browser information. Log retention is set out below.
Messages you sendIf you contact us, we use your email address and message to answer your support or privacy request. Please include only what we need to help you.

We do not ask for access to your contacts, precise location, microphone or camera for these features. Information about advertising and purchases is set out below.

Using TNS on Android

Guest profile, following and searches. The Android app uses a random guest identifier and a credential to authorise requests to the TNS API. Your guest profile and followed players, tournaments and matches are saved on our server. The app also keeps local preferences and cached information. Searches send the text and selected scope to our API; requests for scores, player information, news and other features send the parameters needed to return that content. These records are not an email-and-password account, and are not anonymous. Device identifiers and the guest identifier are different identifiers.

App analytics and purchase activity. Google Analytics for Firebase receives app-use events, including interactions with features, ads and subscription screens. Purchase-result events include the product identifier, result, processing stage and timing. Analytics also handles an app-instance identifier, session identifiers, device and app information, and approximate location derived from the IP address. The Android app disables advertising-ID collection for Firebase Analytics. AdMob has separate advertising-data handling described below.

Crash reports. Firebase Crashlytics is included in the Android app and initialised at startup. It receives crash traces, technical app state, device and Android version, app version, installation identifiers and reliability-session information to help diagnose faults and measure stability. When Analytics is active, events can also be included as crash-report breadcrumbs. Crash reports and analytics follow the retention periods set out in How long we keep information; deleting the app does not erase information already sent to these services.

Google Play purchases. The Android app uses Google Play Billing to offer, recognise, restore and acknowledge TNS Pro purchases. Google processes the payment. The app receives information such as the product identifier, purchase token and purchase or acknowledgement state to determine whether ads should be removed. Subscription activity is also recorded in Firebase Analytics as described above. TNS does not receive payment-card details. The App Store server records described below apply to iOS purchases, not Google Play purchases.

Advertising and news. Google AdMob receives data needed to request, show and measure ads; see Advertising and purchases. News images and embedded third-party content can make requests to their providers, exposing your IP address, device or browser information and the requested content. YouTube and X handle information they receive under their own policies. The iOS-specific player storage and controls below do not describe Android storage.

Privacy and deletion. You can use the app’s Delete profile control or send a deletion request as described in Your choices and rights. Deleting a guest profile and cancelling a Google Play subscription are separate actions. You do not need to purchase Pro to make an available advertising privacy choice or request deletion.

Using the web portal

On this website, we create a separate guest profile to authorise requests to the TNS API. Its random identifier and sign-in credential are stored in your browser’s local storage. Your followed players, tournaments and matches and your score-visibility preference are stored in that browser, not synchronised with your iOS profile or saved as a following list on our server. Requests for scores, selected players and tournaments, search and news still reach our API with the guest credential. The website does not load Firebase Analytics or Crashlytics.

On this website, we offer optional Google Analytics 4 to understand page visits, navigation from scores and player pages to the app page, clicks to our App Store or TestFlight links, and interactions with the example score. Google’s analytics script loads only after you accept analytics. Rejecting it keeps Google Analytics off. You can change your choice or withdraw consent using Analytics settings in the footer; withdrawal reloads the page to stop the analytics script and removes this site’s Google Analytics cookies.

After consent, Google can receive a random browser identifier, your IP address as part of the connection, device and browser information, the page name, a page address without query strings or fragments, the referring website’s origin, and restricted campaign labels. We do not send your app guest credential, following list, email address, arbitrary URL parameters or search terms. Advertising storage and advertising personalisation are denied; Google signals, session recording and automatic interaction measurement are not enabled by this integration. Google may process information outside the European Economic Area; see Google’s privacy policy.

We store your analytics choice and its expiry in necessary browser storage for up to 180 days, including when you reject analytics. If browser storage is unavailable, the choice lasts only for the current page. Analytics cookies are restricted to the current hostname, expire after no more than 180 days and are not renewed on each visit. The Google Analytics property controls retention of data already received; withdrawing consent does not delete previously collected data.

The website’s interface assets and the app landing page’s photos, video, audio and fonts are served from this website. News thumbnails and post images load directly from YouTube’s and X’s image servers. The web portal opens videos and posts on their source platforms; it does not embed a YouTube player or X widget. Cloudflare, which delivers the published website, may set a strictly necessary security cookie (__cf_bm, valid for 30 minutes) and run a brief automated check to protect the site from bots.

03Why we use information

We use guest profiles, following, content and news requests and the Live Activity, widget or match alert updates you enable to provide the app features you ask for. Under the GDPR, this processing is necessary to perform our agreement with you.

We use crash diagnostics and technical information to find faults, keep the service working and prevent abuse; analytics events to understand how features are used, assess subscriptions and advertising revenue, and improve TNS; and correspondence to answer your questions. Our legal basis is our legitimate interest in running a reliable, secure and useful service and responding to users, balanced against your rights. Where information must be kept to meet a legal obligation, that obligation is the basis for keeping it. Advertising and purchase purposes and their legal bases are explained separately below.

App analytics and advertising choices are separate. Declining personalised ads, Apple’s tracking permission or sale/sharing of advertising data does not turn off product analytics. The current iOS app has no separate analytics switch. On iOS, TNS disables Firebase Analytics when its age information places a user in the under-16 treatment group. Where the initial Google advertising form is required, analytics waits until it is answered; either answer can start analytics. You can contact us about access, deletion or an objection as described in Your choices and rights.

Where processing requires consent, it must be obtained before that processing starts. You can withdraw consent without affecting earlier lawful processing. An iOS permission does not replace any separate consent required by law.

We do not use your information to make automated decisions with legal or similarly significant effects on you. Match predictions concern sporting events, not decisions about you.

04Advertising and purchases

Advertising

Android

The free Android app uses Google AdMob. The advertising SDK can collect your IP address and approximate location, device and app information, advertising or other device identifiers, ad interactions and diagnostics. Google uses these for ad delivery, measurement and analytics, fraud prevention, security and, where permitted by your choices and applicable law, personalised advertising. Google acts as an independent controller for its advertising data; see how Google uses information from apps that use its services.

The Android app uses Google’s User Messaging Platform to obtain and manage advertising privacy choices where required and checks whether ads may be requested. You can reopen the available ad privacy options in the app where Google requires this control. Android’s advertising-privacy settings can also limit or delete your advertising ID; available settings vary by Android version. These choices are separate from Firebase product analytics and crash reporting. Pro removes the ads served by TNS; it does not erase information already collected.

iOS

The free version of TNS shows banner and native ads inside screens and lists. They are served by Google AdMob; for users in the European Economic Area, the provider is Google Ireland Limited. AdMob can fill banner ad requests through its partner Unity Ads. These companies act as independent controllers for the advertising data they collect. TNS has no interstitial, rewarded or app-open ads.

When an ad is requested, these companies can receive your IP address (from which an approximate location can be derived), device and app information, ad-interaction data, your consent choices and, only if you allow tracking, your device’s advertising identifier. They use this information to deliver and measure ads, limit how often you see them, prevent fraud and, with consent, personalise ads. We receive aggregate network reports. Separately, the app records ad-impression, ad-delivery and revenue events in Firebase Analytics, linked to its random app-instance identifier, as described in Information we handle.

Users under 18. TNS uses an age range shared by Apple and, where needed in the EEA, the UK and Switzerland, asks for your year of birth. If you’re 16 or 17, you make your own choices in Google’s consent form, but TNS doesn’t show Apple’s tracking prompt, and it asks Google to apply its protections for teens: the ads you see aren’t personalized and don’t follow you from other apps. If you’re under 16, or prefer not to say, TNS doesn’t show Google’s consent form or Apple’s tracking prompt. It asks Google to apply its protections for children: the ads you see aren’t personalized, no third-party ad trackers run, and your advertising identifier isn’t used. Under 18, your ads come only from Google’s AdMob network: TNS doesn’t start its other ad partners’ software for you. If you change your year of birth in Settings to one under 18, the ads stop at once and TNS requests no more ads. Partner software that started while you counted as an adult can’t be stopped while TNS is open: it shows no ads, but it can still connect to its servers, for example when TNS goes to the background or comes back, until TNS is closed. It doesn’t start the next time TNS opens. Your year of birth or Apple-provided age range stays on your iPhone; Google receives only the applicable age-protection setting. An Apple-provided age range can apply these protections outside the EEA, the UK and Switzerland too. TNS asks only for the year, so it counts you as 16 or 18 from 1 January of the year after that birthday.

After initial set-up, Google’s consent message asks for your choices where required, including in the European Economic Area, the United Kingdom and Switzerland. We check the consent status on each launch and request ads only when Google’s consent system permits it. Declining personalisation can result in non-personalised or limited ads; non-personalised ads can still require consent for device storage or access. You do not need to buy Pro to decline optional advertising consent.

You can revisit the choices in Settings → Privacy → Ad privacy choices; this item appears where Google requires a privacy-options entry. iOS may also ask whether TNS may track you across other companies’ apps and websites if you have not already made that choice and the system allows the prompt. If you decline, the advertising identifier is not shared. You can change the iOS choice in Settings → Privacy & Security → Tracking. Changing one of these choices does not automatically change the other.

US state privacy choices: in some US states, such as California, personalized ads can count as selling or sharing personal data. To opt out, open Settings → Privacy → Ad privacy choices in TNS, choose “Don’t sell or share my data” and tap “Save and close”. Google and Unity Ads then stop using your data to personalize the ads you see in TNS on this iPhone. You can change the choice there at any time.

Personalised ads and storing or reading information on your device for ads rely on your consent where required. Other ad processing, such as fraud prevention and measurement, follows the purposes and legal bases shown in Google’s consent message. See how Google uses information from apps that use its services and Unity’s privacy policy. When an active TNS Pro subscription is recognised, TNS hides ads and skips the consent and tracking prompts on launch. Subscribing does not itself withdraw an earlier consent or delete information already collected by an ad provider.

Purchases

Apple processes App Store payments on iOS; Google processes Google Play payments on Android. We do not receive your payment-card details.

TNS Pro is sold through Apple’s App Store on iOS and Google Play on Android. On Android, Google Play Billing handles the purchase and supplies the product, purchase token and state to recognise, restore and acknowledge the subscription. Purchase-result and subscription events are also sent to Firebase Analytics. The Android-specific information is described in Using TNS on Android.

For App Store purchases, to provide Pro, restore it and prevent abuse, our server stores your App Store transaction and original transaction identifiers, the product, its environment and expiry date, the subscription status, and the signed transaction and renewal information Apple sends us. A purchase is linked to your guest profile: the app passes the random guest identifier to Apple with the purchase, and Apple returns it in later notifications. We do not receive your name, Apple Account email or payment details.

The legal basis is performing our agreement with you, and for keeping records, our legal obligations and our legitimate interest in handling refunds and disputes. Retention is set out in How long we keep information.

Managing a subscription and requesting deletion of personal information are separate actions. See payments and subscriptions for billing and cancellation information, and your privacy rights for data requests.

05YouTube videos and X posts

TNS uses YouTube API Services to show videos in its news section. Google’s Privacy Policy explains how Google handles information, and the YouTube Terms of Service apply. The news section can also show public posts from X. TNS does not ask you to sign in to YouTube or X and does not access your account on either platform.

News requests and public content

In the iOS app, our server uses the requested tours, platforms and your App Store country to select available news. While a video is open, its ID lets the server check that it may still be shown. Authenticated requests also let the server prioritise news about the players and matches you follow. The news service does not store or log your country or the open video ID, and does not keep a history of the videos or posts you open. Separate analytics counts interactions without the video or post ID, as described above. TNS does not send your guest identifier or followed-player list to YouTube or X.

The website requests news by tour. It does not send an App Store country or an open-video ID, record news-opening analytics or keep local news-read marks.

Our server fetches public titles, text, images, authors and publication times through YouTube API Services and the X API. Content is refreshed, removed or made unavailable when required by its source. A video or post can disappear from TNS when its author deletes it, the platform restricts it or its permitted display period ends.

What YouTube and X receive

Video thumbnails load from YouTube’s image servers; post images and profile pictures load from X’s image servers. Those requests expose your IP address and basic request information. The iOS app sends no guest identifier or cookies with these image requests. Website image requests do not include your TNS guest credential or the referring page address, but your browser may send cookies already set by the image provider, depending on its settings.

When a video plays inside the TNS iOS app, YouTube’s embedded player loads directly from Google. It receives the video ID and can collect device, playback, interaction and advertising information and use cookies or similar technologies under Google’s Privacy Policy. The player uses an in-memory website data store for the current app process. This limits local persistence; it does not prevent collection by YouTube or erase information already sent to Google. The player may show YouTube’s own ads, including for TNS Pro subscribers. TNS does not insert its own ads into the player or the news screens. YouTube and X act as independent controllers for information their services receive.

Your playback choice

In the iOS app in the EEA, the UK and Switzerland, TNS asks before loading the embedded player for the first video. You can allow playback in TNS or open the video in YouTube instead. The in-app choice requires confirmation that you are at least 16; it stays off where the app’s age information places you in the under-16 group. Elsewhere, in-app playback is enabled unless you turn it off.

Change this in Settings → Privacy → Play YouTube videos in TNS. Turning it off sends subsequent videos to YouTube and clears the local player store. Your choice and its date are stored on your iPhone. Deleting a guest profile clears the player store but preserves this device-level privacy choice.

Leaving TNS and local news marks

Open in YouTube opens the video in YouTube or your browser. A post, profile or external link opens in the app that handles it, or in Safari. X’s Privacy Policy or the destination’s policy applies there.

To mark new or previously opened news, TNS keeps the start time of your last Home visit and a one-way hash of each opened video or post ID on your iPhone, at most 200 entries for up to 7 days. These marks are not uploaded and are erased when you delete your profile. The iOS news feature does not save videos, posts or their images to persistent device storage. Website images may be cached by your browser.

06Service providers and sharing

Hosting, database and support providers process information needed to run the service and respond to messages. Providers acting on our behalf must follow appropriate contractual privacy and security requirements.

Production providers and their roles:

  • Render Services, Inc. hosts the TNS API and its database. Requests reach Render through its network edge, which uses Cloudflare.
  • Google receives crash reports and reliability sessions through Firebase Crashlytics, and app analytics through Google Analytics for Firebase. We use Google BigQuery to analyse exported analytics, diagnostics, subscription and advertising reports.
  • Apple distributes the app, processes App Store payments and delivers Live Activity, widget and match alert updates through the Apple Push Notification service.
  • Google Play distributes the Android app and handles its purchases. Google AdMob delivers ads in the free mobile apps; Unity Ads is also an iOS mediation partner, as described in Advertising and purchases.
  • Google (YouTube) supplies video information through YouTube API Services, plays videos in its embedded player and serves thumbnails. X supplies public posts and serves their images and profile pictures. See YouTube videos and X posts.
  • OpenAI hosts this website, and Cloudflare, Inc. delivers and protects it.
  • Google (Gmail) hosts the support mailbox.

Google processes Android app distribution and Google Play purchases under Google’s Privacy Policy. Apple separately processes information involved in distributing the app through the App Store under Apple’s privacy policy.

Sports-data providers supply match information. We do not need to send them your name or contact details to retrieve a score.

We may disclose information when the law requires it or when necessary and lawful to protect the service and the rights of others. If the service changes owner, any transfer of information must preserve applicable privacy protections and be communicated as required.

07Where information is processed

The TNS API and its database run in Render’s Frankfurt region (Germany, EU). Requests can pass through Cloudflare’s worldwide network on the way.

Our BigQuery datasets are in the EU. Google (including YouTube), Apple, X, OpenAI, Cloudflare and the ad networks named here are global companies and can process information in the United States and other countries outside the European Economic Area.

When a provider that works on our behalf (Render, Google for Crashlytics, Analytics, BigQuery and Gmail, OpenAI or Cloudflare) processes personal information outside the European Economic Area, the transfer relies on the European Commission’s adequacy decision for the EU-U.S. Data Privacy Framework if the provider is certified under it, and otherwise on the Standard Contractual Clauses in the provider’s data processing terms.

Google and Unity act as independent controllers for the advertising data they collect, as do YouTube and X for the information their player and servers receive. Their own policies describe the transfer mechanisms they use.

You can request details of the safeguards that apply to your information using the privacy contact.

08How long we keep information

We keep information only as long as needed for the purposes described here, including applicable legal obligations and resolving disputes.

Website browser data remains until you clear it or your browser removes it. Clearing it does not delete the server guest profile; see Your choices and rights.

Guest profiles do not expire automatically. Removing the app does not delete your guest profile or following from our servers; to delete them, use Delete profile in the app (see Your choices and rights). The guest credential stored by iOS may survive reinstallation.

You can remove followed players and tournaments in the app and clear your recently viewed history. These actions do not delete the whole guest profile.

How long information is kept
InformationHow long we keep it
Guest profile and followingUntil you use Delete profile in the app or complete a deletion request. On iOS, the control is in Settings → Account & Sync → Delete profile. Guest profiles do not expire automatically. Our server keeps your 64 most recent followed matches.
Live Activity tokensA Live Activity runs for at most 8 hours. Its encrypted update token is erased 24 hours after it ends. A record without the token, linking the activity to the match and your guest profile, stays with your guest profile.
Widget update registrationDeleted 72 hours after the app last renewed it.
Match alert registrationThe list of alerts is removed when you turn your alerts off. The push token is deleted 90 days after the app last renewed it, or when you delete your profile.
Match alert delivery recordsWe keep a short-lived record linking an alert to your device to manage delivery and prevent duplicate notifications. Records expire 30 minutes after the alert is created, or 6 hours for a final result. Expired records are removed by routine cleanup, normally within 5 minutes.
IP addresses for abuse protectionHeld in server memory only, and discarded at most 1 hour after your last request.
Hosting platform logsUp to 30 days at Render.
Crash reports90 days at Firebase Crashlytics.
Analytics in Google AnalyticsGA4’s retention setting for event-level and user-level data is 14 months. New activity can restart the retention period for user-level data; standard aggregated reports are not limited by this setting.
Analytics exports in BigQueryDaily GA4 event tables expire 420 days after they are created. BigQuery is a separate copy: changing or deleting data in GA4 does not automatically delete the export.
Other BigQuery exportsExported diagnostic and reliability-session records do not inherit Crashlytics’ 90-day period and currently have no automatic expiry. Server-side subscription exports follow the purchase-record purposes and retention below. Deletion requests must cover these separate copies too; contact us using the privacy contact.
News requestsYour App Store country and the ID of an open video are used to answer the request and are not stored or logged by our news service.
iOS video player cookies and storageIn memory for the current app process. Deleting your profile or turning off in-app YouTube playback clears the player’s local storage for subsequent playback. This does not delete data YouTube has already received.
News marks on your iPhoneA hash of each opened video or post for up to 7 days, at most 200 entries. The time of your last Home visit is replaced on the next visit. Deleted with your profile.
iOS YouTube playback choiceThe choice and when it was made stay on your device until changed or removed with the app’s local data. Deleting a guest profile preserves this device-level privacy choice.
App Store subscription and notification recordsWhile the subscription is active. Afterwards, records needed for refunds, disputes or statutory accounting obligations are kept for up to 7 years. This does not extend the retention of unrelated guest-profile information.
Google Play purchase activityPurchase and subscription events in Firebase follow the analytics periods above. Google keeps payment and subscription records under its own policies. Cancelling in Google Play stops future renewals; it does not delete existing analytics or Google payment records.
Support messagesUp to 2 years after your request is resolved.
Database backupsDeleted information can remain in Render’s database recovery backups for up to 7 days.
Information on your devicePersonal profile data stays until you clear it, delete the profile or delete the app. Device-level privacy choices can remain after profile deletion, as described above. The guest credential in the iOS Keychain can survive reinstalling the app.
Advertising dataAd-impression and revenue events sent to Firebase follow the analytics periods above. We also keep aggregate advertising reports for performance and revenue analysis. Google and the ad networks retain the data they collect under their own policies.

Delete profile removes the guest profile, its following and its links to Live Activities, widgets, match alerts and subscriptions from our database at once. Deleted information can remain in database recovery backups for up to 7 days. App Store purchase records are kept as described above, no longer linked to a profile.

09Your choices and rights

You can change your following in the app and clear recent views in Settings → Privacy → Clear recently viewed. Ad choices are described in Advertising and purchases. These controls do not delete all server records.

Age information: where the manual answer is available, use Settings → Privacy → Year of birth. Deleting your profile erases that answer; age information shared by Apple can still apply. YouTube playback can be changed separately in Settings → Privacy → Play YouTube videos in TNS.

Match alerts: turn them off for a player or match in its alert settings, or turn off notifications for TNS in iOS Settings.

Website data. You can remove individual follows or clear this site’s data in your browser to remove local preferences and the guest credential. Clearing browser data does not delete the guest profile on our server. The website currently has no Delete profile control; use the privacy contact for a server-side deletion request. Do not send your sign-in credential.

Deleting your Android profile or requesting Android data deletion. Use Delete profile in the Android app to remove the guest profile and its following from our server and clear the associated local profile data. To request deletion without the app, email novastarked@gmail.com with the subject “TNS Android data deletion”, identify the app as TNS and tell us whether the request covers your guest profile, analytics, crash reports or support correspondence. We will help identify the relevant records without asking for your password, purchase token or payment-card details. Contact us before deleting the profile if you also need help identifying existing analytics records. Server data may remain in recovery backups for up to 7 days; already collected analytics, diagnostics and legally required records have the separate retention periods stated in this policy. Google retains its payment records under its own policy. Deleting your profile does not cancel a Google Play subscription: cancel it separately in Google Play.

Deleting your iOS profile. TNS creates a guest profile on first launch, without registration. You can delete it at any time in Settings → Account & Sync → Delete profile. This removes your guest profile and following from our server, together with its Live Activity, widget and match-alert registrations, and clears the corresponding personal data on your device, including alerts, picks and recently viewed items. It also clears local news marks, cached news images and the video player’s store. Future analytics uses a new random app-instance identifier; resetting it does not delete events already received by Google or exported to BigQuery. The app then starts setup for a new, empty guest profile. Deleting your profile does not cancel a TNS Pro subscription; manage or cancel it in your Apple ID subscription settings. Records of App Store purchases that Apple sends us are kept for accounting and to let you restore a purchase, but are no longer linked to a profile.

To request access, correction or deletion of information already sent to analytics or linked to your guest profile, use Settings → Help & About → Contact support, or the privacy contact. The iOS app’s support email can include the current Firebase app-instance identifier to help identify analytics records; contact us before deleting your profile if you need a request to cover the current identifier. Do not send a session token, password or payment-card details. Since your guest profile has no email login, we may ask for limited additional information to identify the relevant record and verify your request. We ask only for information necessary for that check.

Under the GDPR, you may also have rights to restrict processing, receive portable data, object to processing based on legitimate interests and withdraw consent. These rights depend on the processing concerned. Requests are normally free. We respond without undue delay and within one month of receiving your request. If its complexity or the number of requests requires an extension, we tell you within that first month, explain why, and may take up to two additional months as permitted by law. If we cannot fulfil a request, we explain the reason and your complaint options.

You can complain to the Dutch data protection authority, Autoriteit Persoonsgegevens, or to the supervisory authority where you normally live or work, or where you believe a breach occurred. See the European data protection authorities.

10Security

The apps use encrypted HTTPS connections to the TNS API. Firebase Analytics, Crashlytics and the Google advertising SDK encrypt their network transfers. On iOS, the app protects its guest credential using the iOS Keychain; our server keeps a one-way hash rather than the original guest credential. We use technical and organisational measures appropriate to the information we handle. No method of storage or transmission guarantees absolute security.

11Children and younger users

TNS is for people aged 16 and over. Younger users need a parent’s or guardian’s permission. In the iOS app in the EEA, the UK and Switzerland, TNS doesn’t ask users under 16 for consent to personalized ads or tracking, and shows users under 18 only ads from Google’s AdMob network, with Google’s protections for children or teens (section 4).

Permission to use TNS is separate from consent to advertising or tracking. Where processing relies on consent and local law requires parental authorisation, that consent must come from the parent or guardian. In the Netherlands this applies to children under 16. An app-store age rating or an operating-system permission does not establish parental consent.

A parent or guardian can use the privacy contact to ask about a child’s information or request deletion. Please do not send identity documents or a child’s detailed personal information unless we explain why a limited verification check is necessary.

12Changes and contact

We may update this policy when features, data practices or legal requirements change. We will show the revised date on this page and give additional notice or seek consent where required. Changing this page alone does not authorise new processing.

For questions about this policy or your information, use the privacy contact.

KEEP READINGRead the Terms of Use
Data controller
Uladzimir Baranau
Country
Netherlands
Contact address
Hyacintenlaan 24-ZW, 2015 BC Haarlem, Netherlands
Privacy contact
novastarked@gmail.com

Analytics, your choice.

Allow Google Analytics to measure visits and app-link clicks on this website? It uses cookies and sends usage data to Google. No advertising signals or session recordings. Your choice lasts up to 180 days.

You can change your choice anytime in Analytics settings in the footer. Privacy details

TNSTENNIS
NEVER STOPS
TNS — Tennis Never Stops
MenuInside the appTournament datesCourtsideYour questionsGet TNSFollow playersHide scores
Fair playTerms of UsePrivacy PolicyPhoto credits
Stay in the matchTNS for iOSAndroid in closed testingApp supportnovastarked@gmail.com
© 2026 TNS · Tennis Never StopsBack to top ↑