pickerino

Privacy

Comments go from the post to your browser and no further; we never see them.

Last updated: October 31, 2026

Introduction

This privacy policy covers the Pickerino Chrome extension and the Pickerino web application. Both are built so that the comments you collect are never sent to us, and this page explains exactly what each one touches.

Data collection

We do not collect or keep any personal data, except in the two cases described at the end of this section. Outside those two cases, this includes but is not limited to:

  • Instagram or YouTube usernames and profile information
  • Comment data or text content
  • Passwords or authentication credentials
  • Browsing history or activity
  • Personal information of any kind

The two exceptions:

  • Profile pictures: winners' profile pictures are loaded through our server, and our web host keeps a cached copy of each one for up to a day.
  • Share links: if you make a share link, the winners' usernames and entry counts are part of its address, so they reach our web host whenever someone opens it.

How the extension works

The Pickerino extension:

  • Only runs against a post or video you have open, and only when you start a collection from pickerino.com
  • Reads comments using your own logged-in session, on your own connection — it never asks for, sees, or stores your password
  • Holds the collected comments in local extension storage on your device, and sends them only to the pickerino.com tab you have open
  • During the move from the old address, runs a tiny script on luckypick.win pagesthat only tells the page the extension's ID, so the page can connect to it. It reads nothing from the page, and it does not run on pickerino.com
  • Does NOT send any data to us or to any external server

How the web app works

The Pickerino web application:

  • Processes all giveaway data client-side in your browser
  • Does NOT store comment data or giveaway results on any server
  • Receives comments directly from the extension in your browser; they are never uploaded
  • Saves a CSV of the collected comments when you ask for one; your browser writes the file straight to your device
  • Shows winners' profile pictures, after a pick, by loading them through our server, because Instagram and YouTube won't serve them directly to another page. That request carries the picture's address. Our host caches each picture for up to a day so it loads quickly next time. Shared results pages show no profile pictures, so opening a share link loads none
  • Does NOT require an account, a login, or any connection to your Instagram or Google account. The site itself has no login of any kind

Share links and pick records

If you make a share link, the winners' usernames and entry counts are written into it, along with the giveaway's totals, the pick's seed and the comments' fingerprint (a hash, from which no comment can be read back). Anyone with the link can see them. The link is made in your browser, but because all of this is part of its address, it reaches our web host whenever someone opens the link, as any address does.

A pick record holds every collected comment — including comments that didn't count as entries and comments from people you left out — with each commenter's username and account ID when it's known, what they wrote, when, and the comment's ID. It also holds the entry list built from those comments, the post's address and its owner's username and account ID when they are known, the rules (including any bonus entries and the usernames you left out), the seed, when the pick was made, whether the collection was still running, the winners and any alternates, and the comments' fingerprint. It is downloaded to your device and goes nowhere else: you decide whether to publish it. The verifier reads a record in your browser and uploads nothing.

Permissions explained

Chrome extension permissions

  • scripting: Runs the comment request inside the Instagram or YouTube tab you already have open, so it uses your session rather than ours.
  • storage / unlimitedStorage: Saves progress on your device after every batch, so a long collection survives being interrupted. Large giveaways can exceed the default storage limit, which is why the unlimited variant is requested.
  • alarms: Wakes the extension back up to resume a collection if the browser has paused it.
  • notifications: Tells you when a collection finishes or stops, so you do not have to watch it.
  • host permissions (instagram.com, youtube.com): Limits the extension to those two sites. It cannot read any other site.
  • externally connectable (pickerino.com): Lets this site — and only this site — ask the extension to start a collection and receive the results.

The extension does not request activeTab, and it has no side panel. It has no content script on Instagram or YouTube; its only content script is the small one on the old address described above. Everything it collects stays on your device.

Third-party access

We do NOT share, sell, or transmit any data to third parties. All giveaway processing happens locally on your device.

The only request our server makes to anyone else is for a winner's profile picture, which it fetches from the Instagram or YouTube image server that issued the picture's address. The preview image a share link shows in chats and social posts is made on our server using only fonts bundled with the site, so the winners' names are never sent to a font or emoji service. Characters those fonts can't draw appear in the preview as a dot.

Children's privacy

Our extension and web app do not knowingly collect information from children under 13. The tools are designed for content creators and social media managers.

Data security

Apart from the two exceptions under Data collection, we don't collect or keep any giveaway data, so there is none to be compromised. Collected comments live in your browser's local extension storage until you clear them, and you maintain full control over any exported CSV files.

Open source

This project is open source. You can review the code for the web app and the extension to verify our privacy practices at any time.

Changes to this policy

If we make changes to this privacy policy, we will update the "Last updated" date at the top of this page.

Contact

If you have questions about this privacy policy, please contact us through our GitHub repository.