Get in touch

What we collect

Last updated: 2026-10-14 · describes the current release, v1.0.10

A plain-language account of what the AddressHate Annotator can see, when anything leaves your browser, what never does, and where it goes. It is written for the people who approve a study before it starts: reviewers, ethics boards and partners’ data protection officers. It describes the product. The Privacy policy is the binding statement and covers your rights and how to contact us. This page is not legal advice.

What the extension can see

What is on screen on the supported sites, and nothing else.

The extension is a content script: it runs inside the page you are viewing, on the sites below and nowhere else, and reads what the site has already displayed for you. That means the posts, comments or chat turns on screen, with their authors, timestamps, permalinks and references to attached media. It reads the page much as you do. It doesn’t open other pages, follow links, or run in the background on a site you aren’t viewing.

On any other website it runs only when you call it up (“Annotate this page” in the toolbar popup, or its keyboard shortcut), on that one page, to label the article, a passage you highlight, or a reader comment under it.

The sites#

X (Twitter)
x.com, twitter.com
YouTube
youtube.com
Reddit
reddit.com, old.reddit.com
Instagram
instagram.com
TikTok
tiktok.com
Rumble
rumble.com
Facebook
facebook.com
4chan
boards.4chan.org, boards.4channel.org, archive.4plebs.org
8kun
8kun.top
Bluesky
bsky.app
LinkedIn
linkedin.com
Mastodon
mastodon.social
Truth Social
truthsocial.com
ChatGPT
chatgpt.com
Claude
claude.ai
Grok
grok.com
Gemini
gemini.google.com
DeepSeek
chat.deepseek.com
Qwen
chat.qwen.ai

When anything is sent

Only when you annotate, flag or share a post.

Nothing you read or browse leaves your browser until you act. Your work is sent by three actions only:

  • Annotate: you label a post and press Submit.
  • Flag: you mark a post for someone else to review.
  • Share: you add a post’s link to your team’s queue.

Scrolling, reading, searching and opening pages send nothing. The only request the extension makes on its own is a lookup of the IDs of the posts on screen, to show which are already annotated. It sends IDs only, never content, and they aren’t kept as a history. An optional coverage counter (off unless you turn it on in Settings) sends the number of posts you scrolled past.

Setup and activity information. To help the people who run your organization’s workspace support you as you get started, the extension also sends a small amount of setup information. It never includes anything you read or browse.

  • Installing and uninstalling. When you install the extension, it creates a random install number and opens our welcome page. The number is linked to your account only after you sign in. If you uninstall, Chrome opens a short page asking why; answering is optional.
  • Getting-started progress. After you sign in, the extension records which in-app walkthroughs you start, how many of their steps you complete, and whether you finish or skip them.
  • Activity dates. The service records when you first sign in, when you first annotate or flag a post, when you last annotated, and when you last used the extension.

Admins and leads in your organization can see this information on their Users page. If you asked for the install link by email at addresshate.org, we link that request to your account, including whether the email was delivered and opened and whether you clicked the link.

What is sent

The post, its author, any context you chose, and your answers.

When you annotate, flag or share, one record goes to the project’s service. It contains:

  • The post: its text, URL, platform ID and timestamp.
  • Its public author: the handle and display name shown on the page.
  • The context you selected: any replies above it that you chose to attach, so a label on a reply can be read against what it answers.
  • References to its media: the addresses of images or video on the post, so a reviewer can see what was posted. For an image or video an AI assistant generated, the file itself, read from the page when you annotate it, because its address works only in your browser.
  • Your annotation: your answers to your organization’s question set, and any note you typed.
  • Your account identity: who made the record, the team and project it was filed under, and the version of the extension used.

You see all of it before you submit: the editor shows the post it captured and every question it will record.

What is never sent

Cookies, passwords, browsing history and private messages.
  • Your cookies, sessions or passwords for any site.
  • Who you follow, your feed, your bookmarks or your account settings.
  • Your browsing: which pages you visit, or when.
  • Private messages. The extension doesn’t run in DMs or inboxes, and it refuses to be called up on them.
  • Your own prompts to an AI assistant, unless you flag or annotate a response in that conversation. Only then do the response and the prompts before it go with the flag or annotation, because nobody else could open the conversation to see them. A flag shows you what it will send first.
  • Anything from a site you didn’t ask it onto.

Where it goes and who reads it

Your organization’s own tenant. Leads review it; administrators operate the service.

Records go to one place: the AddressHate project’s own service, in your organization’s own tenant, a separate database partition that other organizations using the tool can’t read. Within it:

  • You see your own work, and your team’s if your organization lets annotators see each other’s.
  • Reviewers and leads in your organization see the team’s work so they can review, compare and export it.
  • AddressHate administrators run the service and can access every tenant for support and maintenance. They don’t annotate or publish your organization’s data.

A lead can also create an API token (Schedules → Exports → API access) so a script or scheduler run by their own organization can fetch the same exports without a browser. A token acts as the lead who created it and can reach the export routes and nothing else: it cannot annotate, change or delete anything, and it cannot create another token. It expires automatically, and its owner or an AddressHate administrator can revoke it at any time, which takes effect the next time it is used. It moves the organization’s own data to wherever the organization chooses to keep it, and that destination is the organization’s responsibility rather than ours.

Nothing is sold, shared with a data broker or used for advertising. How research findings are published is covered in the Terms of use.

AI features

Two optional buttons that send one post to an AI model.

Two optional features send a post to an AI model: Explain (a plain-language reading of why a post might be hateful) and Pre-annotate (a suggested label to compare with your own). Each runs only when you press its button, on that one post, and its answer is shown to you as a second opinion. Neither fills in your annotation or submits anything.

On this deployment, the model behind them is HateAPI and claude-sonnet-5. We use providers under settings that exclude your submissions from model training, and we send only the post’s text and its selected context, never your account identity.

Retention and deletion

Kept for the project, and de-identified when you delete your account.

Account data is kept while your account is active and deleted when you delete your account. Annotations are kept for the life of the research project, because removing them afterwards would invalidate published findings. When you delete your account, they are detached from you and attributed to a random pseudonym, and you can ask for full erasure. All the options are on the Data deletion page, and the details are in the Privacy policy.

Annotator accounts and ethics review

Setting up accounts for a study, and what an ethics board needs to know.

The extension annotates in place, so it sees whatever the platform shows the account you are signed into on that site, and the platform sees that account viewing the posts. For a study, that should be the study’s account, not the annotator’s personal one. We recommend:

  • One institutional platform account per study, registered to the lab or department rather than a person and used only for annotation, so what the platform records is a research account’s activity.
  • A dedicated browser profile for that account, with the extension installed there and nowhere else, so the annotator’s personal sign-ins, history and cookies are in a different profile the extension can’t see.
  • An annotator account with us under an institutional email address, created by your organization’s lead. That identity appears on your records, and your organization decides who else may see it.

For ethics review: the material collected is public posts and the annotator’s own judgments of them, plus, only when an annotator flags or annotates a response in an AI conversation, that response and the turns before it. No platform account credentials are read or stored, no private messages are collected, and annotators are adults who have accepted the Terms of use and completed a short setup questionnaire (education level, field, organization) that describes the annotator pool in aggregate.

The same setup screen has an optional, unticked mailing-list box. Ticking it sends the annotator’s name, email address and organization to Mailchimp for a newsletter; leaving it unticked changes nothing. It is never a condition of annotating, it shares no study data, and the answer is recorded with the account so consent can be audited.

Methods, in one paragraph

How annotations are captured, reviewed and measured for agreement.

Annotators label posts in situ: the extension captures the post as displayed, with any thread context the annotator selects, and the annotator answers the organization’s question set in an on-page editor. Any number of annotators can annotate a post independently. Each keeps one current annotation per post, and annotating again replaces it rather than adding a duplicate. Reviewers see disagreements post by post and approve or return annotations with feedback, and every annotation is kept rather than reduced to a single winner. The service computes inter-rater reliability from the current annotations (Cohen’s κ for two raters, Fleiss’ κ for a fixed number of raters, and Krippendorff’s α where some raters are missing for an item) and reports it for each field in the question set. A statistic that can’t be computed is reported as undefined, not as zero.