Overview
Viral Feed is a Chrome extension that sorts, exports, downloads and gets scripts on Instagram, TikTok, X, Threads, LinkedIn and YouTube, and downloads and gets scripts on Pinterest. This policy explains what it collects, what it deliberately does not, and what you can ask us to delete.
It covers the extension, this website, and the customer portal at viralfeed.cloud/cuenta.
The short version: almost everything Viral Feed does happens inside your browser and we never see it. Three things leave, and only when you click them: a video's audio when you ask for its script, a note of how many files you're about to download and, when you export more than 25 posts, how many there are. The last two are so your credits can be counted. And one goes without a click: if you're signed in or have a key set, the extension asks our server which plan you have — once a day, or when you open it if your account is free. That question carries only the key.
And if you switch on Claude and ChatGPT, what you ask the app you connected for —sorted posts, a post's numbers or comments, an account's followers and bio, a script or a post analysis— passes through our server on its way to it, and isn't stored there. Every script you ask for from the chat is also saved, verbatim, as a .txt file in your downloads folder. To analyze a post, its videos and photos also pass through our server and Google Gemini (see «Claude and ChatGPT»).
What we collect
Without an account and without Pro we collect nothing: sorting, YouTube scripts and exporting up to 25 posts never touch a server of ours.
If you create an account — free or paid — we keep what «Your account» says below. And with Pro, your licence also carries a counter. This is everything that gets stored:
- Your account
- If you sign in with your email — on the website or from the extension: your email, when you signed up and when you last signed in, your language, which subscription or free trial it has and when you first paid. And for each browser where you sign in, a fingerprint of its key — not the key —, when it connected and when it was last used, so «Sign out» can revoke it. It's used to give you access to your account and your plan and, added up across everyone, for internal statistics: how many free and paid accounts there are and how long it takes to go paid.
- Licence identifier
- The one of your subscription at Stripe, which handles payments for us. It's the key the credits are recorded against.
- Your subscription
- The email and name you gave when paying, the plan, whether it's up to date and until when it's paid. It's used to give you your key, let you into your account with your email and know whether you still have Pro. Of your key we keep only a fingerprint, not the key.
- Your payments
- What was charged on each invoice and whether it was refunded, for our accounts. Never your card details.
- Credits used this month
- One number per licence per cycle, which runs from the day you paid to the same day the next month: when the new cycle starts, it's back to zero. And another per calendar month, for our accounts.
- History
- The last 50 entries: when, what kind (script, download, export, promo code or refund) and how much. The detail is short and carries no personal data: the type of media, the minutes or the number of posts.
- Charged downloads
- How many credits were charged for downloads and when, for 24 hours, so they can be refunded if a download is cut off or your browser doesn't accept it. After that they're deleted.
- Exported sorts
- If you export more than 25 posts, a random number for that sort, for 7 days, so the same export is never charged twice. It's created with each sort and says nothing about you or what you exported.
- Promo credits
- Which code you redeemed, how many credits it gave, when, how many of them you have left and until when they're good.
- Trial keys
- If you came in with a promo code and no plan, we store a fingerprint of your key — not the key — which promotion it came from and until when it's valid. It carries no email and nothing that identifies you.
- Email address
- Your account's, to send you the access code and, when you buy, your key. It's not used for advertising and not shared with anyone.
- Connected apps
- If you connect Claude or ChatGPT: which app it is, the email you gave it permission with, when, and when it last used it, so we can show it in your account and you can take it away. The app's access keys are stored only as a fingerprint, never in full.
We do not collect your browsing history, your feed, your messages, or anything from your own accounts on any network. The extension carries no install identifier, no telemetry and no usage analytics (what this website does is under «Cookies and tracking»).
What stays in your browser
Sorting means reading what the network had already sent your browser to draw the page, and putting it back in a different order. That content lives in the tab while the tab is open and is gone when you close it. It's never uploaded and we cannot see it.
The same goes for almost everything else:
- Downloads go from the network to your disk. The file never passes through a server of ours.
- Outlier scores are worked out in your browser, from the posts on screen.
- CSV, JSON and Excel exports are built by the extension and saved by your browser. Nothing from the posts leaves it (see «Exports»).
- «Copy for Google Sheets» is a clipboard copy, with tabs between the columns. We don't connect to your Google account, we ask Google for no permission at all, and nothing is created in your Drive: you paste it yourself.
- YouTube scripts are fetched by your own tab from YouTube, without cookies and without passing through us. That's why they're free and unlimited.
- The extension's history (what you've sorted and downloaded, and what you've asked for from Claude or ChatGPT) is stored on that computer only, up to 500 rows. It keeps what was done, when and what it cost, never the text of a script, an analysis or comments. It's never synced and never uploaded.
- Your plan's confirmation: the last thing our server said about your key — whether it's Pro, when it said so and, if you're signed in, your account's email — next to a fingerprint of the key, not the key. That way the extension doesn't have to ask on every page.
- On Pinterest, for a media download from a pin the extension asks Pinterest for its page with your session, as if you opened it yourself. That page doesn't pass through us.
The script
Getting a script outside YouTube is the only thing that sends content, because a speech model has to hear it.
When you press the script button, the extension separates the audio from the video in your own tab and uploads only that track to our server, along with the media file's address on the network's CDN and the name of the network. The video does not travel, nor the post's address, nor the account name. If your browser can't separate the audio, you're told and nothing is uploaded.
Our server sends that audio to Google Gemini, which returns the text. The audio is written to a temporary folder only while the job runs and is always deleted at the end, whether it worked or not. The text comes back to your browser and we don't store it.
What remains is one entry in your counter: the date, «script» and the minutes of audio. It exists to deduct the credits and so you can check them in your account.
Downloads
The file goes straight from the network to your disk. The only thing that reaches our server is what type of media it is and how many files there are, so the credits can be deducted before the download starts.
If the browser tells us a download was cut off, or that it didn't accept it, those credits are refunded automatically. That round trip is two numbers too, nothing more.
Exports
The file or the copy is built by your browser, from the posts on your screen: nothing from them leaves it. With 25 posts or fewer, nothing is sent at all.
The first time you export more than 25 posts from a sort, two things reach our server: how many posts there are and a random number for that sort. They're used to deduct 1 credit only once, even if you export it again in another format. The number is kept for 7 days and then deleted.
Claude and ChatGPT
It comes switched off. Only if you switch it on in Settings does the extension keep a connection open to our server, so the app you connect can ask it for sorts. With it off, that connection doesn't exist.
When the app asks for a sort, our server passes your browser the network, the account, what to sort by and how many posts. Your browser sorts it with your session on that network and sends back the sorted posts —the same columns as an export: link, type, numbers, date and text—, which pass through our server to the app. They aren't stored: the server keeps them in memory only while it hands them over, and your browser keeps them for 15 minutes in case the app asks for them again.
Each sort of more than 25 posts leaves one entry in your history, like an export: the date and how many posts. Not the account you sorted.
The app can also ask for things from a post by its link —its script, its numbers, its comments or downloading it— and, from an account, its stories, its followers and its bio. Your browser opens that page with your session, does the same as the usual buttons and closes it. What the app receives —text and numbers— passes through our server without being stored. What gets downloaded goes from the network to your disk, as always, and the script follows the path described in «The script»; your browser also saves it verbatim as a .txt file in your downloads folder, which doesn't go through our server.
Comments are read by your browser from the network itself, as you'd see them, and reach the app with the username of whoever wrote them, the text, their likes and their date. They aren't stored on our server. Your movements keep the date and how many were charged.
Analyzing a post is the only thing that sends whole videos and photos. Our server fetches the post's videos and photos from the network —on TikTok your browser uploads the video—, measures how long the videos are and counts the photos to charge for it, and sends them to Google Gemini, which returns a text with the analysis. Videos are kept in a temporary folder and photos in memory only while the job runs, and are always deleted at the end; videos are uploaded to Google separately and deleted from there too when done. The app only gets the text. For 7 days we keep that post's identifier and a fingerprint of its videos and photos —not the files—, so it isn't charged twice if you ask again; then they're deleted. Your movements keep the date, the minutes and how many photos.
What the app does with those posts —keeping them in the conversation, using them to answer you— is covered by its terms, not ours: Anthropic for Claude and OpenAI for ChatGPT. You can take its access away from your account whenever you like.
Browser permissions
Chrome shows you an extension's permissions when you install it. Viral Feed asks for five, and here they are:
- storage
- Keeping your settings, your key and your history in the browser itself.
- downloads
- Saving the file you asked for into your downloads folder, and the .txt of every script you ask for from Claude or ChatGPT.
- activeTab
- Knowing which page you're on — only when you click the Viral Feed icon — so it can tell you whether sorting works there, and send the command to that tab.
- alarms
- Reconnecting to our server if the connection drops. Only with “Claude and ChatGPT” switched on.
- Site access
- Instagram, TikTok, X, Threads, LinkedIn, YouTube and Pinterest. No other site you visit. There is an eighth domain on the list, cdn.syndication.twimg.com: it is the public card X serves to any site that embeds a tweet, and it is only requested when the page did not give us the video you asked to save. It carries no session and no cookies.
Viral Feed does not request the identity permission and doesn't read your Chrome profile. Your email only reaches us if you type it in when signing in to your account. When you sign in from the extension, your account page hands the extension a key for that browser, and nothing else.
How we use it
To run the product, and for nothing else:
- Tell whether a licence is valid and still paying, including in the once-a-day check.
- Count the month's credits and show them in your account.
- Refund the credits of a download that fails.
- Run your account: signing in with your email, your plan and the browsers where you're signed in.
- Send you the access code for your account.
- Internal statistics, always added up across everyone: how many accounts there are, how many pay and how long it takes to pay. Never for advertising.
- Hand the app you connected what you ask it for: sorts, numbers, comments, scripts and video analyses.
- Understand how this website is used and which parts are harder to follow, only if you accept the analytics cookies. Never for advertising.
- Answer your support messages.
We don't sell your data, we don't rent it, and we don't use it to train models.
Viral Feed's use of the information it receives adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Who else processes it
Four companies process data on our behalf, and each gets only what its job needs:
- Stripe
- Charges the subscription, holds your card and sends you the invoices. We never see your card. It tells us who has paid and whether they're still paying, so we can give you your key and keep it active.
- Google (Gemini)
- Receives the audio of the videos you ask a script for and, if you ask Claude or ChatGPT to analyze a post, its videos and photos. Nothing else: not the post URL, not your key, not who you are.
- Resend
- Sends the email with your account access code and, when you buy, the one with your key. It receives your address and what that email carries.
- Hostinger
- Hosts the server. Like any host, its web server keeps access logs with the IP address of whoever requests a page.
Besides those four, if you accept this website's analytics cookies, Microsoft receives the data from your visit through Clarity (see «Cookies and tracking»). It doesn't process it on our behalf: Microsoft handles it as a controller, under its privacy statement.
Other than that, we share your information with no one else.
Separately, if you connect Claude or ChatGPT, the posts sorted for you go to Anthropic or OpenAI because you ask for it: they don't process anything on our behalf and are governed by their own terms (see «Claude and ChatGPT»).
Cookies and tracking
The extension sets no cookies and reports nothing about your browsing.
This website only uses analytics cookies if you accept them. When you arrive, a notice lets you accept or reject them. If you reject, or if you don't choose, no third-party script is loaded and no request goes out to them. You can change your mind whenever you like with the «Cookies» button in the footer of any page: if you reject, any cookies that were set are deleted.
If you accept them, the website loads Microsoft Clarity, an analytics tool from Microsoft. Clarity records how the website is used: which pages you visit, where you move the mouse or your finger, where you click and how far you scroll, and it can record the session to play it back later. To estimate where you're visiting from it uses your IP address. What's typed into a text field is hidden in the recording. That's how we see which parts of the website are clear and which aren't. We don't use it for advertising.
- _clck, set by this website, lasts 1 year: it keeps an anonymous identifier for the browser so you're recognised as the same visitor.
- _clsk, set by this website, lasts 1 day: it joins the pages you visit into a single session.
- According to Microsoft's documentation, Clarity may also use cookies of its own, from a third party: CLID, ANONCHK, MR, MUID and SM.
Microsoft stores that data in its Azure cloud: recordings for 30 days, and aggregated click data for 9 months. More on what Microsoft does with it in its privacy statement.
Apart from the analytics cookies, the only things your browser stores on this website are your language choice and your cookie choice, so we don't ask you again. The fonts are hosted on our own server.
The customer portal does use one cookie, the one that keeps your session open for 30 days when you sign in with your email. It's signed, it's strictly necessary, and it can't be used to follow you anywhere.
Storage, security and retention
The counters live on our server, hosted in France, and every request runs over HTTPS.
We hold no passwords and no card details: there's no password to create, and payment is handled by Stripe.
History is kept to the last 50 entries per licence; the server's error log keeps the last 500 and carries no customer data. Monthly counters are kept while the account exists, because they're the record of what you used. Your account is kept until you ask us to delete it. When you ask us to delete your data, we delete it.
Your rights
You can ask for a copy of your data, a correction, or its deletion. Email us and we'll act on it within 30 days at most.
Some of it you can do yourself: cancel the subscription from your account, and uninstall the extension to clear everything it kept in your browser.
If you're in the European Union or the United Kingdom: we process your account data to provide the service you ask for when you sign up and, if you subscribe, to perform that contract; the internal statistics, added up across everyone, on our legitimate interest in knowing how the product is doing; and this website's analytics cookies, on your consent, which you can withdraw whenever you like with the «Cookies» button in the footer. You have the right to access, correct, export and delete it, and to complain to your country's supervisory authority.
Children's privacy
Viral Feed isn't intended for anyone under 14 and we don't knowingly collect information from children. If you believe a child has given us data, email us and we'll delete it.
Changes to this policy
This policy is updated as the product changes. The current version is always at this address and the date at the top says when it last moved. If a change is significant, customers are told by email.
Contact
For anything about this policy or the data we hold:
- Data controller
- Focus Services LLC
- Address
- 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, USA
- support@viralfeed.cloud