TisRadar

Privacy Policy

Last updated: 25 October 2026

A Polish version is at tisradar.pl/prywatnosc; if the versions differ, the Polish version prevails.

This policy explains what data the TisRadar application collects, why it collects it, who else may process it, how long it is kept and what rights you have. It applies to the TisRadar web application at https://tisradar.pl, the TisRadar app for iPhone from the App Store, and this website.

1. Who is responsible for your data

The data controller is TiS AI sp. z o.o., a limited liability company with its registered office at Kłębowo 242, 11-100 Kłębowo, Poland, entered in the Polish National Court Register kept by the District Court in Olsztyn, 8th Commercial Division of the National Court Register, under number 0001082897, NIP 5833499345, REGON 527518453. You can reach us at kontakt@tisradar.pl for any privacy question or request; we answer in Polish and English.

2. Who uses TisRadar

TisRadar is used by people who manage social media accounts – creators, brand owners and social media managers. New accounts are opened only with an invitation from us: the invited person creates the account themselves, accepts our Terms and the data processing agreement, then connects their own social media profiles and sees only their own data. Accounts and plans are governed by our Polish terms (tisradar.pl/regulamin), translated at tisradar.pl/terms. For an account created before 16 October 2026 they apply 30 days after our email about the change (§ 31 of the terms). If you download TisRadar from the App Store, the store processes the download data under its own terms as a separate controller; we receive no personal data about you from the store, only aggregate statistics without personal data (such as download numbers).

In the Zespół plan, team members also use an account: people whom the account owner (Główna osoba, the person who created it) adds to work in their account. Each team member signs in with their own Google or Apple account or their own email address and sees only what the role given by the account owner allows. Where this policy speaks of team members, it concerns their data; the other sections describe the data of the account owner and their account.

3. What data we collect

We do not collect payment data, we do not buy data about you from third parties, and we do not build advertising profiles.

4. What we do with it

• Show you how your own accounts and posts are performing, over time and against your own history.
• Suggest topics and publication times, based on your past results, calendar events and public trend data. Holidays in your calendar are weighted by the topics the application recognises, by fixed rules and without AI, in the profile description you gave in the set-up interview; this only changes how an occasion is ranked and labelled for you and which Google search phrase is shown with it.
• Show a line chart under each daily idea on your start screen: how often people in Poland searched Google for its phrase (for a holiday, how many times a month it was searched this season and in the same months of earlier years; for another occasion with a date, last year's season; for a topic outside the holidays, how many times a month it was searched in recent months and in the same months of earlier years), the weather forecast for the coming week, or how your own content with that occasion performed. The sentence under the chart is put together by the application from the same numbers, not written by AI; when there is a content angle for a holiday or topic (below), its explanation, written by AI, stands next to it.
• Before upcoming holidays and for topics people in Poland are searching for on Google right now outside the holidays, three times a week and once after a profile is set up, the AI model in the “AI model for comments, emails and texts” category (section 9) looks for a content angle for each of your profiles: one concrete idea that links what people in Poland search for on Google around that holiday or topic with your profile's topics. When no angle really fits, we show nothing, and a topic outside the holidays without an angle does not appear for you at all. Those topics come from public search data shared by all accounts, not from your account's data; your profile's topics only decide which of them we check for you first. An angle is only a suggestion on the start screen, in the calendar and for the assistant: it publishes nothing, changes none of your settings and decides nothing for you. An occasion with an angle the model is most confident about can rank higher for you, and for a holiday where no angle fits we do not show the sentence about searches (the chart stays). Public search data can only raise a holiday's weight in your calendar. When you hide an occasion with an angle in the calendar (the “Nie dla mnie”, “Not for me”, button), we take it into account: after three such hides within 30 days, for 60 days we show only the angles the model is most confident about.
• Publish content to the accounts you connected, when you or a member of your team with the right to publish click “Opublikuj” (Publish). When a platform does not confirm the result at once, check the status of that publication on the platform for up to 24 hours and tell you whether it went out (sections 6, 7 and 8); the same content is never sent a second time on a guess.
• Collect comments on your posts into one inbox and propose replies for your approval. To choose which comments to propose a reply to, the application combines the assessment of what the comment says (section 9) with signals calculated only on our server and only within your account: how many likes the comment has, how soon after the post it was written, under how many of your other posts the same person commented on that platform in the last 60 days and whether they have already received a link from you in a private message. The signals themselves are not sent to any AI provider; a request for a reply suggestion carries only a short note on tone chosen from them (for example, to keep the reply brief because many people will read it, or to answer warmly).
• Send the private messages and public replies set out in a rule you created, and hide comments with a link to another website, as described in section 7.
• Give each of your profiles, if you ask for it and have the Pro or Zespół plan, a trial or a pilot, its own address (for example name@wspolpraca.tisradar.pl) for offers from brands: receive the emails sent to it, show them in the inbox, and, within the daily limits in § 20 of the Terms, send a copy of each to your sign-in email so that nothing is lost if TisRadar is unavailable. Only if you separately allow it, every email that arrives is read by the AI model in the “AI model for comments, emails and texts” category (section 9) to recognise collaboration offers, pull out their terms and write one sentence of advice; before that, the email addresses, phone numbers, bank account numbers and links that the application recognises in the text are replaced with markers. The comparison with your reach and your past rates is calculated by the application, not by the AI model. The content of these emails is used only to provide this service to you. TisRadar does not send emails from your collaboration address.
• Send notifications to the devices on which you turned them on: the result of a scheduled publication (one that went out in full arrives without sound), the progress of a publication while the application is in the background (one notification for each platform and a summary at the end), the result of checking a publication that a platform did not confirm at once (when Instagram, Threads or YouTube says it did not go out, the notification can offer to send it again; that happens only when you tap it), that a text the AI was writing for you is ready, an upload of a video that stopped, comments worth a reply (at most twice a day, at 12:00 and 19:00), the number of new comments under a post or video you published from TisRadar during the first three hours after it is published (grouped, at most once every 30 minutes, or once an hour if you choose fewer; never during quiet hours or while the application is open on your screen), how a post or video is doing compared with your usual results (an hour after it is published, when it does at least one and a half times better than usual, and once when your first publication from the application has 48 hours of results), a new collaboration offer in your collaboration emails, a round number of followers on a platform (at most once a month), people asking for a link under one of your posts or videos on Facebook or Instagram when no message keyword works there (from two different people, at most once in 60 days for each post or video; the application counts only the comments that the assessment of comments already marked as a request for a link and that you have not skipped or answered), a monthly payment for your plan that did not go through (once for each invoice, with the last day of access), a reminder to upload fresh statistics files (on the first Monday of the month, or after about two weeks if you choose, only for the platforms from which you uploaded a file before and only when the newest one is older than 30 or 14 days), a reminder about an unfinished draft (only if you turn it on, once for each draft after three days without changes), an occasion from your calendar whose window opens in the middle of the week, or weather or a trend that is going on, only when your posts or videos about it did better than usual (at most one such notification a day and once in 14 days for each occasion), your weekly plan on Mondays from 9:00 (occasions of the week, scheduled publications and your best post or video of the month after its first week), a connection to a platform that has expired and, if you turned on a character's daily training, a reminder once a day that a training sample is waiting. If you do not open five notifications in a row about how a post or video is doing, or about new comments under a fresh post or video, the application switches that kind to fewer by itself and says so in Settings, with a button to bring it back. A notification contains only numbers, dates, episode codes (or, when a post has none, whether it is a post or a reel and the time it was published), platform names, the names of your profiles and characters in TisRadar, the names of occasions from your calendar, the amount of a collaboration offer (only when the assessment of the email found it and its sender was verified; never the name of the brand or of the sender) and a small chart of how a post or video is doing compared with your usual results, without numbers of people; never the text of a comment, of an email or of your draft, or the name of the person who wrote it. The chart is drawn on your device from a few numbers carried inside the encrypted notification.
• Tell you by email about your account's plan: when a pilot or a trial starts and three days before it ends (or on its last day when it lasts seven days or less), when a monthly payment for the plan did not go through (once for each invoice, with the last day of access), when the account becomes read-only, seven days before its data is deleted, when you ask to delete the account and when it has been deleted. These emails are information only.
• Tell you by email and in the app about a change of the terms (§ 29 of the terms).
• In an account with a team we process team members' data so that each member signs in on their own and works in the account owner's account only within the role given, so that the account owner knows who did what in their account, and to protect the account: we send a member's scheduled publication only if, at the moment of sending, the member still has the right to it, we end a member's sessions after they are paused or removed, and after a member is added or given the right to publish on their own we email the account owner a notice with the member's name, without their address.
• If the weekly plan by email is turned on in Settings, send it on Mondays to the address you sign in with: the same weekly plan as the notification, plus unfinished drafts and statistics files that are getting old. It contains only the kinds of information listed above for notifications (numbers, dates, episode codes and the names of occasions, platforms and your profiles), never the text of a comment or of your draft. When there is nothing to say that week, no email is sent. Every such email has a link that stops it without signing in, and email programs that support it show an unsubscribe button. The weekly plan never advertises a plan or a service.
• Answer your emails, including complaints, statements of withdrawal from a contract and requests about your data.
• Prepare a file with all your data when you ask for it, and delete your account when you ask for it or when its read-only period ends (sections 10 and 13).
• Keep you signed in, keep the application secure and diagnose technical problems.

We do not use your data to train machine-learning models, and we do not sell or rent it to anyone.

5. Legal basis

Where the General Data Protection Regulation (EU) 2016/679 applies, we process this data on the basis of the contract with the user of the application (Article 6(1)(b)) and our legitimate interest in operating and securing the service (Article 6(1)(f)). Connecting a social account is always a voluntary, explicit act performed by the user in the platform's own authorisation screen.

We process correspondence with us to handle your matter, to perform the contract for your account or plan and to meet our legal obligations, for example to answer a complaint or a request about your data on time (Article 6(1)(b) and (c) GDPR), and we keep emails about money also on the basis of our legitimate interest in defending against claims (Article 6(1)(f) GDPR).

We process team members' data on the basis of legitimate interests (Article 6(1)(f) GDPR): ours, in operating and securing the service, and the account owner's, who wants to work in their account with a team and to know who did what in it. The account owner is the controller of their viewers' data (§ 28 of the terms), and a team member processes it on the account owner's instructions (Article 29 GDPR). Without the statement that the member is at least 18 years old and without a sign-in method, a person cannot join the team.

For emails sent to your collaboration address, you are the controller of the senders' personal data and we process it on your behalf under the data processing agreement in § 28 of our Terms. The content of these emails is also covered by the confidentiality of communications under the Polish Electronic Communications Law: we process it only as part of the service you use and, for the AI rating, on the basis of your consent as the recipient, which you can withdraw in Settings at any time.

Do you have to give us data. An email address and a sign-in method are needed to create an account and use the application; without them you cannot create one. Connecting accounts on platforms and the other data depend on you: without them some functions do not work.

Automated decisions. We do not make decisions about you based solely on automated processing that produce legal effects for you or similarly significantly affect you (Article 22 GDPR). The automations described in sections 7 and 8 act on your audience's comments according to the principles described in sections 7 and 8 and the rules you set.

6. What TisRadar accesses on TikTok

You connect TikTok to TisRadar in two ways, each with its own consent in TikTok's window: “TikTok” for publishing and video results, and “TikTok: comments and statistics” for comments and detailed statistics (TikTok API for Business). We are switching on the second connection gradually: you see it under Connections only once it covers your account. When you connect a TikTok account for publishing, TisRadar can, with the permissions you grant:

• read your basic profile information and your public profile fields, to identify the connected account;
• read your account statistics (followers, likes, video count);
• list your own most recent videos with their title, description, publication time, length, share link and cover image, together with their view, like, comment and share counts, so performance can be reviewed; these counts are recorded during the first 48 hours after publication, then every six hours until seven days after publication and once a night until 30 days after publication. Once after you connect the account, and again when you ask for it in the application (at most once a day), TisRadar also lists your public videos from the last 180 days with the same fields and their counts at that moment, so its suggestions can draw on your earlier videos from the first day;
• publish a video to your own TikTok profile – only at the moment you click publish or at a time you scheduled yourself, with the privacy level, interaction settings and commercial-content disclosure that you chose on that screen;
• check the publishing status of a video TisRadar has just sent, by the reference TikTok returned for it, for up to 24 hours when TikTok does not confirm at once whether it was published, so the application can tell you the result. Such a video is never sent again automatically.

When you connect “TikTok: comments and statistics”, TisRadar can, with the permissions you grant:

• read the account name and whether it is a personal or a business account, the follower, like and video counts, and the account's daily figures for the last 60 days (video and profile views, likes, comments, shares, followers);
• read the breakdown of followers by age, gender, country and city, as percentages, which TikTok provides from 100 followers;
• read detailed results of your videos from the last 30 days: reach, saves, average and total watch time, the share of views watched to the end, new followers, audience retention second by second, impression sources, and the shares of new and returning viewers and of followers, as percentages;
• read the comments and replies under your videos from the last 30 days, with the author's display name, the time, the number of likes and whether the comment is hidden, so you can review and answer them from one inbox;
• receive a notification from TikTok when someone adds, deletes or hides a comment under one of your videos, or a hidden comment becomes visible again, and fetch a new comment at once when it is under a video TisRadar already knows;
• reply publicly to a comment, like it, hide it and show a hidden comment again, only when you click that in the inbox.

TisRadar reads the information in the first three points once a day, right after you connect the account (if you connect it before 6:00 Polish time, with the morning reading at 6:00) and again whenever you ask for a refresh in the application.

On TikTok, TisRadar does nothing to comments without your click: it does not reply to them, like them or hide them on its own (for a comment that is only a link, the inbox only suggests hiding it), and it sends no private messages. We do not pass TikTok comments to any AI provider (section 9): TisRadar does not assess them or draft replies to them, and the assistant does not receive their text or their authors' names. You write replies to TikTok comments yourself. TisRadar does not access TikTok direct messages, does not access other people's accounts, and never publishes automatically. Data obtained from TikTok is used solely to provide these features to you and is not sold, rented or used for advertising.

7. What TisRadar accesses on Facebook, Instagram and Threads

When you connect a Facebook Page (with its linked Instagram professional account) or a Threads profile, TisRadar can, with the permissions you grant:

• read the list of Pages your account manages, to identify the Page you choose to connect;
• read the statistics of your Page and Instagram account (followers, daily views) and the audience demographics the platform provides, to power the analytics screens;
• read your own posts, reels and stories together with their results (views, reach, likes, comments, shares, watch time), so performance can be reviewed in one place; the results of posts and reels are recorded during the first 48 hours after publication, then every six hours until seven days after publication and once a night until 30 days after publication, and the results of a story while it is available. Once after you connect the Page or the Threads profile, and again when you ask for it in the application (at most once a day), TisRadar also reads your posts and reels from the last 180 days with their results at that moment, so its suggestions can draw on your earlier content from the first day; older stories are no longer available and are not read;
• read the comments viewers leave under your posts, together with the number of likes on each, so you can review and answer them from one inbox;
• publish a post, reel or story to your own Page or Instagram account – only at the moment you click publish, or at a time you scheduled yourself;
• check whether a post, reel or story TisRadar has just sent to Facebook, Instagram or Threads went out, for up to 24 hours when the platform does not confirm it at once: by reading the status of that upload (the Instagram or Threads container, the Facebook video) or by finding the post among the recent posts of your Page or account. When Instagram or Threads says the post did not go out and the upload can still be used, Send again (in the application or in the notification) publishes that same upload, only when you tap it;
• reply publicly to a comment or like it when you approve that in the inbox, or automatically with the ready answers you set for that post when publishing it (described below), hide a comment you chose to hide, and show again a comment that was hidden;
• send a single private reply to the author of a comment – either when you click it, or automatically when a rule you created for a chosen post applies to their comment (described below and in § 18 of the Terms of Service);
• keep the Page subscribed to the application, so new comments reach the inbox in real time.

What happens without a click. On your accounts, TisRadar replies, likes, hides or sends a message without a click only in the following cases, each because of how the application or a rule you created is set up:

• A comment written in the last seven days that contains a link to another website is hidden when TisRadar processes it. “Another website” means any address TisRadar does not know as yours; your own addresses are those from your product cards, message rules, connected Instagram and Threads profiles, your Facebook Page, your posts (also under another form of their address) and the list of addresses in Settings. A comment that consists of nothing but such a link is hidden. A comment with text next to such a link is hidden only once TisRadar knows where you send viewers, that is from your product cards, message rules or the list in Settings. Before that, and also when the link leads to another page of a website from your product cards or message rules that is not yet on the list in Settings, the inbox only suggests hiding it and waits for your click. A comment on Facebook or Instagram whose whole text or first line your message rule for that post recognises as its keyword, and a comment you have already replied to, are never hidden automatically. TisRadar hides at most 20 comments this way per profile in an hour; above that, and for a shortened or shared platform link (for example fb.watch) that may lead to your own post, the inbox only suggests hiding it and waits for your click. No AI model takes part in this: the application compares the addresses. The inbox marks a hidden comment as hidden automatically, and one click on Show again (“Pokaż z powrotem” in the Polish interface) brings it back. This applies on Facebook, Instagram and Threads, and on YouTube only if you switch it on, as described in section 8.
• When a rule sends a private reply on Facebook or Instagram, TisRadar also posts a short public reply under the comment, so the viewer knows to check their messages. Of the replies an AI model proposes, only the ones you approved are posted. An AI model proposes such replies only when you ask for them, for a given post and keyword (from the post's description, episode code, keyword and product names) or for a character, in that character's voice (from its writing portrait and your own earlier replies, never from your viewers' comments). You read each proposal and approve, edit or reject it one by one; the application stores who approved each reply, when, and a fingerprint of its exact text. Under a comment it posts an approved reply word for word, never the same one twice under the same post: first the replies approved for the post tied to the rule that sent the message and for that rule's keyword, then the ones approved for its character. A rule is tied to the post it was created with or, the next time you open your rules in TisRadar, to the post it points to; a rule set only by an episode code is tied only when every post with that code is one post (copies of one post made in TisRadar, or copies of the same type published within an hour of each other) and that post was published no later than an hour after the rule was created. Editing a rule's post or episode code unties it. A reply approved for a post is used only if the rule was already tied to that post when it sent the message, and only while that post has the same episode code and products as when you approved it; otherwise only the replies approved for the character are used. When none is left, the fallback text saved in the rule is used (the application fills in a default wording that you can change), and if the rule has no fallback text, no public reply is posted. No AI text is posted under a comment without your approval. If a reply of yours is already under the comment, no public reply is posted. No public reply is posted either when the AI model in the “AI model for comments, emails and texts” category (section 9), while classifying the comment, recognises that the viewer asks why the link comes in a private message, or complains about or distrusts that message: the message with the link is sent as usual, and the comment waits in the inbox for your reply. On Facebook the comment is also liked, unless you switched that off in the rule or the AI model recognises such a question or complaint; a comment the model has not assessed yet is liked only once the model has assessed it.
• If a person who has already received the message from a rule writes its keyword again, TisRadar posts at most one short reminder a day under that comment, in one of a few fixed sentences, and on Facebook likes it if the rule says so, but only when the comment is the keyword alone or the AI model has already assessed it and found no question or complaint about the private message; later repeats are liked on the same terms. Nothing is hidden for this reason.
• Ready answers, only for a post where, when publishing or scheduling it, you switched on sending them without asking (the switch is off by default, and the moment you switch it on is recorded). You write answers to questions viewers are likely to ask, and you can choose to thank comments that are plainly praise with sentences from your own list. When a comment under that post asks exactly what one of your answers covers, TisRadar posts your answer under it, word for word, on Facebook, Instagram or Threads; a thank-you sentence is picked at random by the application from your list, and on Facebook the praised comment is also liked. The comment is matched by the same AI model that classifies comments (section 9); the model never writes these replies. They are not posted under hate or spam, under a comment that asks for a link or is covered by a keyword rule, or under a comment that already has your reply; each comment gets at most one, each person at most once per answer, and they stop after the daily limit (30 by default) and after the number of days you set (7 by default) from publication. Uncertain matches and replies within a thread wait in the inbox with your answer filled in. You can edit the answers or stop them at any time in the inbox or on the Content screen.
• Threads has no private messages through its API. There, a rule attached to content that also has a copy on Threads works only for comments written in the last seven days that clearly ask for the product: TisRadar posts a public reply under such a comment, containing the link from the rule in one of a few fixed sentences, unless a reply of yours is already under the comment. Uncertain cases wait in the inbox for your click.

On Threads, TisRadar reads your profile, your posts and their statistics and replies, publishes a post only when you click publish or at a time you scheduled yourself, and replies to or hides a comment as described above. TisRadar never publishes on its own initiative, does not access other people's accounts, and uses data obtained from these platforms solely to provide the features above – it is not sold, rented or used for advertising.

8. What TisRadar accesses on YouTube

TisRadar uses YouTube API Services (the YouTube Data API and the YouTube Analytics API, operated by Google). You connect a YouTube channel in Google's own consent screen, and Google's handling of your account is governed by the Google Privacy Policy. TisRadar asks for four permissions and uses each of them only as described here:

• Upload videos (youtube.upload) – to upload a video to your own channel, only at the moment you click publish or at a time you scheduled yourself. TisRadar sends the video file, the title and description you wrote, and marks the video as public, not made for kids and in a default video category (People & Blogs) that you can change in YouTube Studio. If you mark the video as a paid partnership in TisRadar, the upload also sets YouTube's paid product placement flag. Whether YouTube shows it as a Short or as a regular video depends on the video itself. If an upload is cut off, TisRadar asks YouTube at the same upload address, for up to 24 hours, how much of the file arrived and whether the video was created; Send again (in the application or in the notification) sends the rest of the same file to the same address, only when you tap it.
• Read your channel (youtube.readonly) – to identify the connected channel (its id and name), to read its statistics (subscribers, total views, number of videos) once a day and again whenever you click Refresh next to the connection, and to read the view, like and comment counts of the videos you published through TisRadar during their first 48 hours, then every six hours until seven days and once a night until 30 days after publication, together with each such video's privacy and processing status, so the application can notice that a video was made private or unlisted, was rejected, failed to upload or was removed, and, once a night, the privacy and processing status of every video published through TisRadar that you have not removed from your statistics, also after the first 30 days, so the application knows whether it is still public.
• Read YouTube Analytics reports (yt-analytics.readonly) – to read channel-level audience reports for the last 90 days (age and gender as percentages, views by country and city, average watch time and watch percentage, traffic sources), once a day and again whenever you click Refresh next to the connection, and for each video published through TisRadar its retention and traffic sources on the same schedule for 30 days after publication.
• Manage comments (youtube.force-ssl) – used only for comments: to read the public comments and replies under videos published through TisRadar, to post a reply you approved in the inbox, to hide a comment, which sets it to “held for review” in YouTube Studio, and to show again a comment that was hidden, which sets it back to published. So that only published replies are stored, when TisRadar finds a reply it has not stored before under one of its videos, or when a stored reply is due to be read again (see below), it may also read the comments held for review or marked as likely spam under that video, only to leave out or delete the replies YouTube has not published. When a comment TisRadar hid is due to be read again, TisRadar may also read the comments held for review under that video, only to find out whether that comment is still hidden, so that it can still be shown again. TisRadar does not store or show any other held comments. Although the permission would technically allow it, TisRadar never deletes videos or comments, never permanently rejects a comment, never edits captions and never rates anything.

Automatic actions on YouTube: only if you switch this on in the inbox, after a window that explains it, a comment written in the last seven days that contains a link to another website is set to “held for review” when TisRadar processes it, under the conditions described in section 7 (a comment with text next to the link only once TisRadar knows where you send viewers, and with the exceptions listed there). Until you switch it on, such a comment waits in the inbox with a suggestion to hide it, and once it is on, it applies to comments written after you switched it on. TisRadar records, for each profile, when you switched this on or off and which version of the explanation you agreed to, and keeps that record until the account is deleted. You can switch it off at any time; it then stops for comments processed afterwards. The inbox marks a comment hidden this way as hidden automatically, and one click on Show again (“Pokaż z powrotem” in the Polish interface) publishes it again. Ready answers (section 7) do not work on YouTube. Every other hide and every reply on YouTube happens only after your click.

What TisRadar does not do on YouTube: it does not list or read the other videos on your channel (a video is known to TisRadar only if it was published through TisRadar), it does not read comments that YouTube holds for review or marks as spam (apart from the checks described above), it does not change channel settings, and it never publishes or replies on its own initiative. YouTube offers no private messages through its API, so the rule described in section 7 does not exist on YouTube.

What we store from YouTube: your channel id and name, the id of the channel's uploads playlist, the Google access token and refresh token together with the permissions you granted and the token's expiry time, the statistics and audience percentages listed above, the id, title, description, results, privacy and processing status as last read and thumbnail picture of each video published through TisRadar, the upload address YouTube gives for each upload while the file is being sent (deleted as soon as the result is known; when an upload was cut off and the rest of the file can still be sent, after 24 hours at the latest), and the comments under those videos (comment id, author display name, text, time, number of likes, and whether it is your own reply). Comments, video results and channel measurements are read on a schedule: new comments every 20 minutes for videos up to two days old, every hour up to seven days and every four hours up to 30 days; the view, like and comment counts of each such video during its first 48 hours, then every six hours up to seven days and once a night up to 30 days; channel statistics and audience reports once a day and again whenever you click Refresh next to the connection. After 30 days only a video's privacy and processing status is read, once a night; its counts are not re-read. YouTube allows this kind of data to be kept for at most 30 days unless it is refreshed, so while the channel is connected the text and author name of every stored comment are read again from YouTube about every 25 days; a comment YouTube no longer returns, or one that could not be read again within 30 days, is deleted entirely. A video's privacy and processing status not read again within 30 days is removed, and the thumbnail picture is fetched again after 25 days or removed.

Tokens and refreshing: the Google access token is valid for about one hour and is renewed automatically with the refresh token when needed. If you revoke TisRadar's access at Google, the next renewal fails and the application asks you to connect again; it never tries to work around a revoked grant. The comments, video results and status, channel statistics, audience reports, thumbnails and video IDs and links from that channel are then deleted 7 days after TisRadar notices the revocation, unless you connect the same channel again before then. If renewing the token keeps failing for any other reason, the same data is deleted after 28 days.

Sharing: information received from YouTube is stored on our server together with the data from the other platforms and used only for the features above. The original text of YouTube comments goes to the provider in the “AI model for comments, emails and texts” category (section 9) for classification and for drafting a reply proposal, like comments from the other platforms, but unlike them it never reaches the assistant: the assistant receives only how many YouTube comments there are, their categories and the video they are under, never their text or author. The results and channel statistics listed above can also reach the provider in the “AI model for the assistant and product research” category (section 9) when you use the assistant: in your questions and in the short morning overview it prepares when you open it. No provider receives your Google tokens, YouTube data is not sold, rented or used for advertising, and TisRadar does not pass it to any other application. TisRadar’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting: in the application, under Connections, you can disconnect YouTube at any time. This deletes the stored Google tokens from our server at once and revokes TisRadar's access at Google right away. The one exception: when the same channel is also connected in another TisRadar account, or we cannot tell whether it is, access at Google is not revoked, because Google would end it for that account too; the application tells you so. If Google does not accept the revocation, the tokens are deleted anyway and the application tells you where to revoke access yourself. The comments, video results and status, channel statistics, audience reports and thumbnails from that channel are deleted 7 days after disconnecting, unless you connect the same channel again before then; connecting a different channel does not stop the deletion. Until then the application shows the channel's name next to the pending deletion, and the name is deleted together with the data. What remains is our record of each video you published through TisRadar, which is part of your publishing history: the title and description you wrote in TisRadar and when it was published. The video's YouTube ID and link are deleted together with the data, and the channel's ID is replaced with a number of our own that cannot be traced back to YouTube. You can also revoke access yourself at https://myaccount.google.com/permissions (Google Account → Security → Third-party apps with account access) by removing TisRadar; the tokens we hold stop working at once and the data listed above is deleted as described. Deleting the account (section 13) deletes everything at once.

9. Who else processes the data

We keep the circle as small as possible. Besides the social platforms themselves, data may be processed by:

• Public authorities – only where we are legally required to disclose information.
• The account owner (only data of the members of their team): sees the member's name, roles, profiles and level, sign-in method, the time they last used the application and the “Kto co zrobił” record, and in the “Pobierz swoje dane” (Download your data) file also the email address the member signs in with, their age statement with the time it was made and the dates of their joining codes;
• Our service providers, in the categories described below, each for one clearly defined task.

We will give you the list of providers in each category by name, with the country of each, on request sent to kontakt@tisradar.pl.

We do not authorise any of these providers to use your content for their own purposes. Where a provider's free tier is used, that provider's own terms may nevertheless allow it to use submitted content to improve its services, and we cannot override those terms on your behalf. None of these providers receives your access tokens.

10. How long we keep it

• Performance measurements and your own content records: for as long as the account is connected and the application is in use, because their value lies in long-term comparison.
• Comments received on your posts and the private replies sent to them: for as long as the account is connected and the application is in use, because together they form the record of your conversations with your audience. They are deleted on request – see section 13. YouTube is stricter: a YouTube comment is kept only while it is read again from YouTube at least every 30 days, and the YouTube comments, video results and status, channel statistics, audience reports, thumbnails and video IDs and links are deleted 7 days after you disconnect the channel or revoke access at Google (section 8).
• Access tokens (including the Google tokens for YouTube): until you disconnect the account in the application, at which point they are deleted; for YouTube, disconnecting also revokes TisRadar's access at Google right away (section 8). Revoking access at the platform – for YouTube, in your Google account – makes them useless immediately.
• The token from Apple (only with Sign in with Apple): for as long as you have the account, also after you remove Sign in with Apple in Settings. The token then stays with the account, because revoking access at Apple would stop Apple from forwarding emails to a hidden Apple address, and when the account is deleted we need it to revoke that access. When you delete the account, we ask Apple to revoke TisRadar's access and delete the token once Apple confirms, at the latest 30 days after the account is deleted; until then it waits encrypted, without the account number. A token from a sign-in after which no account was created is passed on for revocation the same way within 2 hours of the sign-in, unless it is the Apple ID of an account from which Sign in with Apple was removed: then it stays with that account. You can also revoke TisRadar's access yourself in your Apple ID settings; the token then becomes useless.
• Sign-in links and codes: stored only as hashes, valid for 15 minutes and usable once; the record, with the address it was sent to, is deleted one day after it expires.
• Your sign-in methods and the invitation you used: for as long as the account exists. A sign-in method you remove in Settings is deleted at once (the token from Apple stays until the account is deleted, see above). The record of accepted documents (which document, which version, when), the record of emails about a change of the terms (which version, when it was sent and from when it applies) and the record of the in-app notice about it (when it was shown and when “Rozumiem” was tapped) remain after the account is deleted, without your email address and name, as evidence in case of a dispute, until the end of the sixth calendar year after the year of deletion, or until the end of a dispute still open then (section 13).
• Team members: we keep a member's data while they are in the team. When the account owner removes them or they leave the team, we delete their sign-in methods, email address and rights at once and end their sessions; their name stays with the “Kto co zrobił” record, and 12 months after the member's removal we delete it together with their age statement and the hashes of their joining codes. We delete “Kto co zrobił” entries after 12 months. The account owner removes a person who has not joined in Settings. Deleting the account owner's account deletes the whole team (section 13).
• Your account's plan: when a pilot, a trial, a paid period or a period agreed with us ends and no new payment arrives, the account becomes read-only for 30 days. You still see your data, can download it, disconnect your accounts and delete the account, but nothing is published, sent or replied to. After those 30 days the account and its data are deleted as described in section 13.
• Correspondence with us: for as long as needed to handle the matter; emails about money (complaints, withdrawals from the contract, refunds, invoices) until the end of the sixth calendar year after the year in which we closed the matter, emails about personal data for 3 years after the matter was closed, and other emails for one year after the matter was closed.
• A file with your data prepared for download: it can be downloaded for one hour and is deleted from our server within a few minutes after that.
• The record of each publication attempt (the platforms, the reference each platform returned and the result): 30 days. The text of the publication kept with it, so the steps after publishing can finish when a result arrives later, is deleted as soon as every platform has a result, or after 24 hours at the latest when a publication can still be sent again.
• Content angles for holidays and for topics outside the holidays: at most one per holiday or topic for each profile, until the next angle round for that holiday or topic or until the account is deleted; an angle that a new round has not confirmed for 7 days, or one for a topic people are no longer searching for, is no longer shown, and an angle for a topic outside the holidays is deleted 30 days after its last confirmation. The record of your recent hides of occasions with an angle (“Not for me”, at most 20, with dates) is kept for as long as the account exists.
• Characters and their training: for as long as the character exists. Deleting a character in Settings deletes its portrait, its training settings and the replies you wrote in its training at once.
• Public replies proposed for keyword rules: for as long as the character they were written for exists; deleting the character deletes them. The record of each reply you approved (who approved it, when, its exact text and its fingerprint) is kept until the account is deleted, as evidence of your approval.
• Hiding comments on YouTube without asking: the current setting of each profile and the record of each time you switched it on or off (when, by which account and which version of the explanation) are kept until the account is deleted, as evidence of your consent.
• Notification devices: until you turn notifications off for that device in Settings, sign out on it, or the push service (in the app for iPhone: Apple) reports that the device no longer accepts them; at that point the entry is deleted. "Sign out of all devices" also stops notifications on every device turned on before it, and their entries are deleted. Your notification settings are kept for as long as the account exists. The record of each notification sent (kind, text, when it was sent and opened) is deleted after 90 days. The note about which comments under a fresh post or video you were already told about is deleted after 2 days. The note that you were already told about a result is deleted after 7 days, about an offer after 30 days, about people asking for a link under a post or video, about a payment that did not go through, and about a weekly plan or a reminder about statistics files, a draft or an occasion after 60 days; the follower milestones already announced and the note about your first result are kept for as long as the account exists.
• Emails to your collaboration address: a conversation is deleted 90 days after you close it; a conversation with no new email for 90 days closes by itself and is deleted 90 days later; a conversation in the Spam folder is deleted 14 days after its last email or after you moved it there, whichever is later. You can delete a conversation at once. The daily count of emails that were not stored because the address received too many is kept for 30 days. The copies sent to your sign-in email are in your own mailbox and are not affected. The collaboration address itself works until you switch it off or change it; after a change the old address still accepts emails for 6 months. After a change, after switching it off and after the account is deleted, the name cannot be taken by anyone else for 12 months; for that we keep only a one-way hash of the name, not the name itself.
• Server logs (errors and the record of background tasks): about a month (up to five weeks), then deleted.
• Backup copies of the database: a copy is made every night and kept on our own server for up to 8 weeks, and an encrypted copy is kept for up to 90 days with our backup provider in the European Union (section 9); it is encrypted on our server before it leaves, with a key that only we hold, so the provider cannot read it. A copy made just before an update of the application is kept on our own server for up to 30 days. The copies are used only to restore the application after a failure. Data you ask us to delete, and data deleted under the rules above (for example YouTube data after disconnecting), disappears from these copies when they expire, at the latest after 90 days. If a copy ever has to be restored, these deletions are carried out again before the application resumes work.

11. Security

The application is served only over encrypted connections (HTTPS). Access requires signing in to an existing TisRadar account, depending on the options shown on the sign-in screen: with Google, with Apple, or with a one-time link or code sent to the account's email address. Sign-in links and codes expire after 15 minutes, work once, are stored only as hashes and are protected by limits on attempts; five wrong codes invalidate the code. When a new sign-in method is added to an account, a notice goes to the account's email address. A team member signs in with their own sign-in method, never with the account owner's details; the one-time joining code works once and for 24 hours, we store only its hash and limit the number of codes issued per day, and pausing or removing a member ends their sessions. Team members never see access tokens. Access tokens are stored on the server, never sent to the browser and never shared with third parties. The database is not exposed to the public internet.

12. Your rights

You have the right to access your data, to have it corrected or erased, to restrict its processing and to receive it in a portable form, and the right to withdraw your consent at any time, without affecting the lawfulness of processing before the withdrawal. You also have the right to object to processing based on our legitimate interest (Article 21 GDPR); we then stop processing it unless we show compelling legitimate grounds that override your interests, or the data is needed to establish, exercise or defend legal claims. You also have the right to lodge a complaint with a supervisory authority – in Poland, the President of the Personal Data Protection Office (UODO). To exercise any of these rights, write to kontakt@tisradar.pl. We reply without undue delay and at the latest within one month. A team member can also leave the team at any time themselves (“Opuść zespół” in Settings).

Two of these rights you can use yourself in the application, on the Plan screen (Plan i płatności), also while the account is read-only. Pobierz swoje dane (Download your data) prepares one ZIP file with the data of your account from our database: each table as a CSV file that opens in a spreadsheet, the same data as one JSON file, the photos you uploaded and the thumbnails of your posts, and the list of your connected platforms. Access tokens are never included. Usuń konto (Delete account) is described in section 13.

13. Data deletion

You can delete your account yourself in the application: on the Plan screen (Plan i płatności) choose Usuń konto (Delete account) and confirm. From that moment the account publishes, sends and replies to nothing, and scheduled publications are stopped. For seven full days after the day of the request, or until the end of the account's read-only period if that comes sooner, you can still download your data and cancel the deletion on the same screen; after that the account is deleted permanently. An account whose read-only period of 30 days (section 10) has ended is deleted in the same way.

You can also send an email to kontakt@tisradar.pl with the subject Data deletion and the name of the account concerned. We then start the same deletion, confirm it by reply to the same address, and the data is deleted no later than 30 days after your request.

When the account is deleted, we sign it out on every device; remove your Facebook Page's subscription to the application, unless the same Page is connected in another TisRadar account; revoke our access at Facebook and Instagram, TikTok and YouTube (Google), and at Apple if we have a token from Apple (section 10); and delete the stored access tokens, your content records, statistics, comments and replies, rules, drafts, scheduled publications, the photos you uploaded, thumbnails, imported statistics files, notification devices and settings, and your collaboration address with the emails received on it; the address stops accepting emails at once. We also delete the team: team members, their sign-in methods, joining codes and the “Kto co zrobił” record. If the same platform account is also connected in another TisRadar account, or we cannot tell whether it is, we do not revoke that platform's access, because it would disconnect the other account; we only delete our stored tokens. Threads gives applications no way to revoke access: we delete the stored token, which then expires on its own, and you can remove TisRadar in the Threads settings. If a platform refuses the revocation, the stored token is still deleted. We delete the token from Apple once Apple confirms the revocation, at the latest 30 days after the account is deleted (section 10). What remains, without your email address or name, is the account number and the numbers of its profiles in TisRadar (so that they are never given to anyone else), a one-way hash of the name of your collaboration address for 12 months (so that no one else receives emails meant for you), the date the account was created, the account's plan history, the record of which documents were accepted and when, the record of emails about a change of the terms without the address and the record of the in-app notice about it (these five until the end of the sixth calendar year after the year of deletion, or until the end of a dispute still open then, section 10), the cost records of the AI requests made for the account, without their descriptions (linked to the account until the same date as the plan history, then without that link), and a record of the deletion itself (dates, numbers of removed items and the result at each platform; until the same date as the plan history). Your posts on the platforms themselves are not affected.

Backup copies made before the deletion (on our own server and, encrypted, with our backup provider in the European Union) may still contain that data; they are never used for anything other than restoring the service after a failure, and they expire automatically no later than 90 days after they were made.

You can also revoke our access yourself at any time in the platform's settings – on Facebook and Instagram under Settings → Apps and websites, on TikTok under Settings and privacy → Security and permissions → Manage app permissions, and for YouTube in your Google account at https://myaccount.google.com/permissions. Revoking access immediately invalidates the tokens we hold.

14. Cookies

This website uses no tracking or advertising cookies and no analytics scripts. The application sets only cookies needed for signing in:

• a signed session cookie with your account number, email address, display name, a link to your profile picture and the session's expiry date. It is valid for 30 days and is extended while you use the application, but never beyond 90 days from signing in;
• short-lived cookies used only while signing in: during a Google or Apple sign-in (10 minutes), while adding a sign-in method in Settings (10 minutes), while waiting for a sign-in link or code (15 minutes), while you connect an account on a platform (up to 15 minutes), and while you finish creating an account (30 minutes, holding the data received from the sign-in method and, if you signed in with a link from an email sent after opening an invitation, which invitation it was, until you create the account or leave);
• if you open an invitation link, a cookie with that invitation until it expires (at most 14 days);
• after you sign in with a link or code, a signed cookie with hashes of the addresses used on this device, so that limits on sign-in emails aimed at your address by others do not lock you out. It lasts 400 days;
• a cookie without personal data that only records that someone has signed in on this device, so the installed application can say that your session has expired. It lasts one year.

The session cookie and the sign-in record are removed when you sign out. "Sign out of all devices" in Settings ends every session of your account at once.

The application also stores in your browser's storage (localStorage and sessionStorage) data it needs to work, which stays on your device and is not used for tracking, for example: the theme you chose, the number of the active profile, a hash of the account's email address, working texts (a draft question to the Assistant, a draft of the interview and of training), a marker of a publication in progress, the address of your device for notifications, postponed hints and, while you sign in with a link, the address the link was sent to, as well as the progress of a video being uploaded. When you open the application, your browser runs a background script (service worker) that keeps the "no internet" page and some of the application's files and receives notifications, and keeps the photos and videos you share to TisRadar from your phone's gallery until they are used. You can remove all of this by clearing the site data for tisradar.pl in your browser settings.

The TisRadar app for iPhone keeps in its own storage on the phone the same cookies and data as the browser, plus a file you upload in the background and the files you share to TisRadar from another app (in a folder shared by the app and its “Share” extension), while they are sent or used. The app deletes an unused share after an hour and a finished upload after a day, the next time it starts. A file you download in the app (for example your data) is placed in a temporary folder, from which you choose where to save it, and the app deletes it from there the next time it starts. You can remove all of this by deleting the app from the phone. If you turn on notifications in it, the app keeps the keys for reading them in the phone's keychain; they never leave the phone, and the iPhone may keep them even after the app is deleted, although nothing uses them then.

When you dictate text (for example a question to the Assistant or an answer in the profile interview), your device's system or browser (Apple on iPhone, Google in Chrome) turns speech into text under its maker's terms; we receive only the finished text.

15. Children

TisRadar is a professional tool for managing social media accounts and is not directed at children. Creating an account and joining a team require confirming that you are at least 18 years old, and we do not knowingly collect data from anyone under 18.

16. International transfers

Our servers are located in the European Union. Some of the providers in section 9 process data outside the European Economic Area, in particular in the USA (the “Where” column in section 9); where that happens, the transfer relies, depending on the provider, on the European Commission's adequacy decision (the EU-US Data Privacy Framework), on the European Commission's standard contractual clauses or on another legal transfer mechanism. You can get a copy of the safeguards a transfer relies on by request sent to kontakt@tisradar.pl.

17. Changes to this policy

If we change this policy we will update the date at the top of this page. The date at the top is the day that version was published on this page, and when a new version has the same date as the previous one, its number stands next to the date (for example “version 2 with this date”). One exception: some versions published on this page between 15 and 18 October 2026 bear later dates, from 16 to 23 October 2026. Material changes affecting users of the application will additionally be communicated to them directly.

18. Contact

TiS AI sp. z o.o., Kłębowo 242, 11-100 Kłębowo, Poland – kontakt@tisradar.pl