At a glance
The short answers: what is collected, why, and who sees it.
- Who it’s for
- Annotators the project has authorized by name. Adults only. It is not offered to the public and is not intended for children.
- What triggers collection
- A deliberate action by a signed-in annotator: labeling a post, adding it to the queue or flagging it. Apart from that, only setup information: installing or removing the extension, and your getting-started progress (see What we collect).
- What we receive
- The post you act on, the labels you apply, your account identifier and your one-time setup answers.
- What we never receive
- Your bookmarks, direct messages, passwords or cookies; your activity on any site you didn’t ask the extension onto; or any conversation you didn’t flag or annotate.
- Where it goes
- Only to the project’s own service at
api.address-hate-dashboard.org, hosted on Google Cloud in the United States. - Who reads it
- Reviewers on your own team, and the project administrators who run the service. Organizations can’t see each other’s data; see Who can read your work.
- Where we name you
- We may say publicly that your organization uses the extension. We never use your name, annotations or judgments without your explicit consent in a separate agreement. See Where we name you.
- Getting it removed
- Delete your account in the extension, or email us. See Data deletion.
Who can use it
Authorized annotators only. Adults, not the public.
The extension works only for annotators the project has authorized by name: project staff and vetted research partners. It is not a consumer product. We don’t market it to the public, and without an authorized account it does nothing. Annotators must be adults; it is not intended for children.
What we collect
Only what you choose to annotate or flag, plus a little setup information.
We receive post content only when a signed-in annotator takes a deliberate action: labeling a post, adding it to the queue or flagging it. The extension runs on the sites listed below. On any other site it runs only when you ask it to, by pressing “Annotate this page” in the toolbar popup or using the keyboard shortcut, and then only on that page.
To label a post accurately, the extension reads what the site’s own app has already loaded as you browse: the posts and comments in the feed, thread, search results or conversation you are viewing. That material is held briefly in memory on your device and discarded when you reload or leave the page. It is never written to disk or sent to us unless you annotate or flag a specific post. The extension does not read your bookmarks, direct messages, account settings, passwords or cookies, or anything on a site you didn’t ask it onto, and it never modifies the requests those sites make.
Articles and other web pages. When you ask the extension onto a page that isn’t one of the sites above, you can label a passage you highlight, the article itself, or a reader comment under it. What we receive depends on your choice:
- a highlight sends only that passage;
- labeling the article sends its text (up to 12,000 characters) and, as context, the first few reader comments on the page;
- labeling a comment sends its text, the name shown with it (and the profile link, if the name is a link), when it was posted and the like count the page shows, along with the comments it replies to and the article’s headline.
Each of these also includes the page’s address, title, publisher, byline and date. Comments that a site loads from another service (such as Facebook’s comments plugin) are never read. The record notes only that they were there and which service they came from (its address without the query string). The one exception is Disqus, and only with your permission: on a page whose comments are a Disqus thread, Chrome asks you once whether the extension may use disqus.com. If you agree, it reads that thread the same way whenever you ask it onto the page. Images on these pages are counted, never copied, and the extension stops running on the page when you leave it.
- Content you choose to annotate: the text, author handle and permalink of the post or comment you label, plus any nearby thread comments you select as context.
- Your annotations: your answers to your organization’s question set. Depending on how the set is written, an answer can be a choice from a list, a yes or no, a rating, text you type, or a mark on a passage you highlighted in the post. A highlight is stored as the position of the passage in the post text we already hold, not as a second copy of it. Your organization writes the questions, not us, so the fields vary from study to study. The editor shows every question it will record, and you see your answers before you submit.
- Which work it belongs to: the team you were annotating for and the project you filed the work under, so a study’s material can be gathered and reviewed together. These are labels on your submission, not extra content taken from the page.
- Media in annotated posts: images or video attached to a post you annotate are archived with it, so the annotation can be checked against what was actually posted. Images and video that an AI assistant generated in your conversation are handled differently: their addresses work only in your browser, so when you annotate one, the extension reads the file from the page and uploads it with your annotation. Nothing else on the page is read this way, and nothing is uploaded unless you annotate that image.
- Authentication data: your account identifier and a session token. If you sign in with Google or Microsoft, the email address and name the provider gives us, used only to authenticate you. Sign-in times are kept on your account as a security record. If a team lead invited you (rather than an administrator creating your account directly), we hold your email address, the date of the invitation and who sent it from the moment the invitation is issued, before your first sign-in, so the seat can be shown as waiting to be claimed. If you don’t accept, the seat stays unclaimed, and an administrator can remove it.
- Setup questionnaire: the one-time questions every annotator answers at first sign-in (education level, field of study, organization), used to describe the annotator pool in research. Deleted when you delete your account.
- Mailing list, only if you ask: the setup screen has an optional, unticked box to join the AddressHate mailing list. If you tick it, your email address, your name and the organization you entered on that screen are sent to Mailchimp and tagged as an extension sign-up. Your answer, either way, is recorded on your account with the date. If you leave it unticked, nothing is sent and nothing about your account changes. The list is a newsletter only: joining is never a condition of using the extension, it receives no annotation data, and every message has an unsubscribe link. Leaving the list is separate from deleting your account (unsubscribe from any message, or write to us), because the same list holds sign-ups from our website and we won’t guess which one you mean.
- Annotation-status lookups: to show the “already annotated” badge, the extension sends the platform IDs of the posts on screen (on supported sites, while you are signed in) to the project’s service, which replies with the ones that are annotated. Only IDs are sent, never post content. They are used only to show the badge and are not kept as a browsing history.
- Optional coverage counts (off by default): post-view counting is off unless you turn it on in Settings. If you do, the extension counts the posts you scroll past on supported sites and sends the total (numbers only: no content, post IDs or URLs) for annotation-coverage statistics. You can turn it off at any time.
- Setup and activity information: to help the people who run your organization’s workspace support you as you get started, the extension 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.
Flagging or annotating a conversation with an AI assistant
What flagging or annotating a private AI chat sends, and who sees it.
Flagging works differently on AI assistants (ChatGPT, Claude, Grok, Gemini, DeepSeek, and Qwen) than on public platforms. A public post can be flagged by its link, because a reviewer can open it. A conversation with an AI assistant is private to your account: nobody else can open it, and you can delete it at any time. So a flag there has to carry the content itself, or a reviewer would have nothing to look at.
Only when you flag content in such a conversation do we receive:
- the assistant response you flagged, and the passage you selected in it;
- the prompt that produced it, because a response usually can’t be judged without knowing what was asked;
- up to six immediately preceding turns, for context;
- which assistant it was, timestamps, and any citations that match our reviewed-source list.
Annotating an assistant response also sends it to us, because an annotation has to include what it is about. Only when you submit an annotation of a response in such a conversation do we receive the response (or the passage you selected), up to twenty immediately preceding turns of that conversation (your prompts and the assistant’s replies), which assistant it was, and timestamps. They are stored with your annotation in your organization’s archive.
Unlike a flag, an annotation carries your name. The people in your organization who may read your annotations (teammates allowed to see each other’s work, and the leads who review it) see the response together with the prompt that produced it: your opening request in that conversation and the prompt the response answers (and, if you annotated an excerpt, the full response it came from), each cut to 2,000 characters. They don’t see the rest of those turns, and nobody else can open the conversation itself.
We don’t collect any conversation you didn’t flag or annotate, we don’t collect more of a conversation than the turns described above, and we don’t monitor your use of AI assistants in the background. Deleting your account deletes the conversation evidence you contributed.
Images and video the assistant generated can be annotated on their own. When you annotate one, the extension reads the file from the page (nobody else can open it) and uploads it with your annotation, along with the prompts you wrote before it but not the assistant’s text around it. Each file is stored once, in your organization’s own archive. An image you don’t annotate is never read.
Permissions and the sites it runs on
Each Chrome permission and why we ask for it, and the sites the extension runs on.
Chrome shows you what an extension can access before you install it. This is the full list, and what each item is for.
Permissions#
| Permission | Why we ask for it |
|---|---|
storage | Keeps your settings, your recent work and an outbox of submissions on your own device, so queued annotations survive a closed tab or a dropped connection. |
alarms | Wakes the extension on a schedule to retry delivering queued annotations after a network or service outage, so nothing you submitted is lost. |
identity | Runs the optional “Sign in with Google” and “Sign in with Microsoft” flows. Signing in with a username and password does not use this permission. |
downloads | Saves the spreadsheet when you export your own annotations. It is used only for that export, and only when you ask for it. |
activeTab | Lets you annotate an article or any other web page you choose. Nothing runs on that page until you press “Annotate this page” in the toolbar popup or use the keyboard shortcut. Access covers only that tab and ends when you leave the page. The extension has no standing access to any other site. |
scripting | Loads the extension’s own annotation script into the page you just asked to annotate (see activeTab). It is the same script the extension runs on the supported platforms, loaded on demand, and it is never loaded into a page you didn’t ask for. |
https://disqus.com/* (optional; requested only when needed) | Lets you annotate reader comments when a page’s comment section is a Disqus thread. Disqus shows its comments in a frame served from disqus.com, which access to the page alone can’t reach, so the first time you annotate such a page Chrome asks whether to allow it. If you allow it, the extension reads the thread only when you ask it onto the page, as it does with the page itself. If you don’t, nothing changes. |
Sites it runs on#
The extension requests one host permission: our own service (api.address-hate-dashboard.org). That is where your submissions go and where the shared work queue and your history come from, and it is the only server the extension contacts.
The platforms below are the extension’s content-script match list: the sites where it can add the Annotate button and read the post you choose to label, which is why Chrome lists them at install. The extension runs on no other site and sends nothing from these pages to anyone but us.
Social platforms#
- X (Twitter)
- x.com, twitter.com
- YouTube
- youtube.com
- reddit.com, old.reddit.com
- instagram.com
- TikTok
- tiktok.com
- Rumble
- rumble.com
- facebook.com
- 4chan
- boards.4chan.org, boards.4channel.org, archive.4plebs.org
- 8kun
- 8kun.top
- Bluesky
- bsky.app
- linkedin.com
- Mastodon
- mastodon.social
- Truth Social
- truthsocial.com
AI chat assistants#
- ChatGPT
- chatgpt.com
- Claude
- claude.ai
- Grok
- grok.com
- Gemini
- gemini.google.com
- DeepSeek
- chat.deepseek.com
- Qwen
- chat.qwen.ai
On X (Twitter) and YouTube the extension reads the site’s own API responses within the page, because that is the only way to capture exactly the post an annotator labeled rather than a re-rendered copy. On every other supported site it reads only the rendered page. In both cases it never modifies requests, never reads credentials or cookies, and sends nothing until you act.
How it’s used and shared
Research only, never sold, and the four service providers we use.
The extension sends the data it collects only to the AddressHate project’s own annotation service (the same service that hosts this page), and we use it only for hate-speech research.
Service providers#
Four service providers process data on our behalf. The first three do so only for this research purpose. The fourth handles one thing, and only for people who ask for it:
- Infrastructure: data is hosted on Google Cloud (Cloud Run, Cloud SQL and Cloud Storage) under the project’s own accounts.
- AI processing: when someone uses the project’s AI second-opinion or “Explain” feature, the text of the annotated post, plus limited thread context such as earlier comments or a video title, is sent to a third-party AI provider, which returns a suggested label or a plain-language explanation. We send post content only, never your name, email address, account details or usage data. The provider handles that content under its own terms, which govern whether it is retained.
- Email: emails the service sends you (such as invitations, email verification, password resets and security notices) are sent from extension@addresshate.org through Google Workspace. The install-link email you can request at addresshate.org is sent through Resend, which tells us whether it was delivered and opened. Our emails show the AddressHate logo, which your email app loads from addresshate.org, and our website logs that request like any other visit (the IP address, the email app or browser, and the time). The image is the same in every email, so it can’t tell us who opened which message. Some email apps load images automatically or through their own servers, and most let you turn images off.
- Mailing list: only if you opted in at setup. Mailchimp holds the name, email address and organization you gave there so we can send the newsletter. Nothing else is shared with Mailchimp: no annotations, post content or usage data. You can unsubscribe from any message.
Who can read your work
You, your team’s reviewers and project administrators. Organizations are kept apart.
Your work is not published, and it is not open to annotators generally. It is read by:
- You: everything you have submitted, in your own history, wherever you are working from.
- Reviewers on your own team: a team lead approves your work or sends it back with a note asking for changes. Where two people have judged the same item differently, both answers are shown side by side so the disagreement can be settled, and your name is shown with your answer.
- Project administrators, to run the service and meet our legal obligations.
Organizations are kept separate. An organization’s annotations, queue, flags and archived media can be read within that organization and not by any other, and several organizations keep their material in a database of their own. Overseeing several teams is a permission within one organization and does not extend to other organizations. Only project administrators have access across organizations, and that access exists to operate the service.
Content you flag from a private conversation with an AI assistant is shown to reviewers without your identity attached.
Where we name you
We may name your organization as a user, but never you without separate consent.
One use of your account details happens outside the extension, so it is described here as well as in the Terms of use. We may state publicly (on our website, in presentations, in funding and grant reports, in academic publications and in press materials) that your organization, institution or lab uses this extension.
You give this permission when you accept the Terms of use at first sign-in, and we record which version you accepted. You can withdraw it by writing to ksaiki@addresshate.org, and we will stop naming your organization in anything we publish from then on. Material already printed, published or submitted to a funder can’t be recalled. The full clause is Being named as a user in the Terms of use.
Google user data (Limited Use)
How Google and Microsoft sign-in data is used.
If you sign in with Google, the extension’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Your Google email address and name are used to authenticate you to the project’s service. They are never sold, used for advertising or used to build a profile of you, and no one reads them unless you ask us to, it is necessary for security, or the law requires it.
If you sign in with Microsoft, the same applies to the email address and name your organization’s Microsoft account provides: they are used to authenticate you to the project’s service and for nothing else. We request only the standard sign-in scopes (openid, profile and email). We can’t read your mail, files, calendar or anything else in your Microsoft account, and we never receive your password.
Where it’s stored
On Google Cloud, in the United States.
Annotations and account data are stored on the project’s own Google Cloud infrastructure (Cloud Run, Cloud SQL and Cloud Storage) in the United States, and only project staff have access to that infrastructure. Annotators confirm at setup that they are located in the United States, so we don’t routinely transfer personal data across borders. If that changes, we will update this page first.
What stays on your device
Your session, settings and outbox. Removing the extension deletes them.
The extension keeps your session, your settings and an outbox of submissions on your computer. Anything waiting to be delivered stays until it is delivered. After that, the local copy is kept for up to 30 days so you can review and export recent work, then removed. Signing out ends your session but leaves undelivered work in place so nothing is lost. Removing the extension from Chrome deletes all of it.
How long we keep it
Account data until you delete it; annotations for the life of the project.
Account data (your identifier, sign-in history and setup answers) 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. If you delete your account, your annotations remain but are detached from you and attributed to a random pseudonym (see Data deletion, which also explains how to ask for full erasure).
Server logs are kept for a short period for routine operations and contain no annotation content.
Security
HTTPS, hashed passwords, and notice if a breach affects you.
Data is sent over HTTPS, the service can be reached only with an authenticated project account, and passwords are stored as hashes, never in readable form. Your session is kept in the extension’s own private storage, where the websites you visit can’t reach it. No system is perfectly secure, so we also limit what we collect and who can read it. If a breach affects your personal data, we will notify you, and any regulator we are required to notify, without undue delay.
Your choices and rights
Access, correct, delete, object or withdraw consent by emailing us.
To exercise any of these rights, email ksaiki@addresshate.org. We will not treat you differently for doing so.
- Access a copy of the personal data we hold about you, and find out what we collect and who we share it with. You can also export your own annotations to a spreadsheet from the extension at any time.
- Correct anything inaccurate, including your setup answers.
- Delete your account and data. You can do this yourself in the extension; see Data deletion.
- Object to a particular use of your data, or ask us to restrict it.
- Withdraw consent you have given. For example, post-view counting is off unless you turn it on, and you can turn it off again in Settings at any time. Permission to name your organization as a user can also be withdrawn; see Where we name you.
- Sign out to end your session and stop collection.
We do not sell your personal information or share it for cross-context behavioral advertising, as those terms are defined in the California Consumer Privacy Act. We have never done either.
If you live where there is a data protection authority and believe we have mishandled your data, you have the right to lodge a complaint with it. We would welcome the chance to put things right first, so please contact us.
Changes to this policy
We update the date, and tell you about material changes.
When we change this policy, we update the “Last updated” date at the top. If a change materially affects you, we will also tell annotators directly.
Contact
Questions or requests: ksaiki@addresshate.org
Questions or requests: ksaiki@addresshate.org. To delete your data, see Data deletion.