AxeBack to Axe

Privacy

Clear by default.

This policy explains what Axe processes, where it goes, and what stays on your device.

Effective August 30, 2026

Overview

Axe is a browser extension that helps people find public X posts worth replying to and develop their own responses. Axe is published by Axe and can be contacted at dev.ujjwal.mathur@gmail.com.

The short version: Axe uses public X data, never connects to your X account, never posts for you, and keeps your drafts in your browser.

Information Axe processes

Axe account and extension access

When you sign in with Google, Axe receives and stores your Google account identifier, email address, name, and profile image. Axe uses this information to create your account, recognize you when you sign in, and determine whether your account has access to paid features. Signing in to Axe does not connect or authorize your X account.

When you connect the browser extension, Axe creates a revocable extension session. The session token is stored in Chrome's local extension storage, while only a cryptographic hash of that token is stored in Axe's database. The session is used only to authenticate requests from the extension to Axe.

Creator searches and public X data

When you search for or track a creator, Axe sends the search text or public username to its backend. Axe retrieves public profile details, public posts, timestamps, and visible engagement counts through TwitterAPI.io.

AI processing

Axe ranks recent public posts and sends selected public post text, creator usernames, source-post identifiers, and engagement counts to OpenAI. OpenAI returns concise inspiration and possible directions for joining the conversation.

Information kept in your browser

Your tracked creators, generated results, selected Idea Slate, scroll position, drafts, and extension session token are stored locally in your browser. Draft text is not sent to Axe, TwitterAPI.io, or OpenAI. Clipboard access is used only after you press Copy post.

Operational information

Axe's hosting provider may process basic request information such as request paths, search parameters, IP address, user agent, timestamps, status codes, and error details. Axe uses this information only to operate, secure, and troubleshoot the service.

What Axe does not access

  • Your X password, authentication cookies, or account credentials.
  • Direct messages, private accounts, or other private X data.
  • The contents of your X feed or general browsing history.
  • Your draft text outside the local browser storage described above.

Axe does not post, reply, like, follow, or perform any other action on X automatically. No X OAuth connection is used.

How information is used

  • To search for public creators and display their public profiles.
  • To rank recent public posts and generate inspiration.
  • To authenticate your Axe account and enforce access entitlements.
  • To maintain, secure, debug, and improve Axe's core features.
  • To respond to support, privacy, or legal requests.

Axe does not sell information or use it for personalized advertising, retargeting, credit decisions, or unrelated profiling.

Service providers

Axe relies on the following providers to deliver its core service:

  • Vercel for website, API, and operational hosting.
  • Google for signing in to an Axe account.
  • Neon for account, entitlement, and extension-session records.
  • TwitterAPI.io for retrieving public X data.
  • OpenAI for processing selected public post content.

Axe does not persist tracked creators, generated results, or drafts in its database. These remain in your browser.

Information may also be disclosed when required by law, to protect the service and its users, or with your explicit consent. Axe does not allow people to read user data except when you request support involving that data, for security, or where legally required.

Storage and retention

Locally stored information remains in your browser until you remove it, clear the extension's storage, or uninstall Axe. Extension sessions expire after 30 days and can be revoked by disconnecting the account. Account and entitlement records remain while your Axe account exists, unless longer retention is required for security or legal reasons.

Infrastructure logs are retained according to the hosting plan and are generally available for no more than 30 days. OpenAI may retain API abuse-monitoring data for up to 30 days unless a longer period is legally required. Other providers process information under their own contractual and privacy terms.

Your choices and deletion

You can remove creators inside Axe, clear Axe's browser storage, or uninstall the extension to delete locally stored information. To ask about information held in operational systems, request access, or request deletion, email dev.ujjwal.mathur@gmail.com. Axe may need enough information to verify and complete the request.

Security and international processing

Production requests are transmitted using HTTPS. Axe limits data use to what is necessary for the product's stated purpose, but no online system can guarantee absolute security. Service providers may process information in countries other than your own, subject to their safeguards and applicable law.

Chrome Web Store Limited Use

Axe's use and transfer of information received through browser permissions complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is used only to provide or improve Axe's disclosed single purpose, maintain security, comply with law, or act with your consent.

Children and policy changes

Axe is not directed to children under 13. We may update this policy as Axe changes. Material changes will be disclosed through the website, extension, or Store listing before new processing begins where required.

© 2026 Axe

PrivacyTermsSupport
dev.ujjwal.mathur@gmail.com