Privacy Policy
This policy covers niuX at niux.win, its API at api.niux.win, and the task-focused niuX Chrome extension. It explains the data used for your account, X creator tasks, verification, and virtual credits. The task-focused extension described here is version 0.2.8 and later; older installed versions may retain legacy workspace, post-reading, and draft features until updated.
Operator: niuX Team
Last updated: October 22, 2026
Account and Service Information
When you sign in with Google, niuX receives account identifiers and profile information such as your name, email address, and avatar. We store niuX account and sign-in session records, including session tokens, IP addresses, and browser user-agent information. We also process the profile details, preferences, uploads, promotion plans, task records, invitations, virtual-credit balances, rewards, and transaction history you provide or create through the service. Public X profiles retrieved by the server may include a display name, biography, self-reported location, avatar, account identifiers, follower and following counts, post counts, and verification status. IP addresses, user-agent information, and device identifiers may also be processed into keyed hashes for signup-reward abuse prevention. Service requests generate technical logs, including request paths, response status, timing, and errors.
Data Read on X
The task-focused Chrome extension reads the current signed-in X handle and page safety signals to match your niuX account with the X account in use. For a claimed follow or reply task, it checks the designated X profile or post, follow-button state, author handles, post IDs, permalinks, and publication times. During an active reply-task observation window, it also reads selected X post responses and extracts only the reply post ID, parent post ID, author handle, and publication time for that task. These observations support account matching, task execution, and completion verification. The extension does not extract or store post bodies or reply drafts from X, read private direct messages or X passwords, export X authentication cookies, or collect browsing history from unrelated websites.
Data Sent by the Extension
The niuX website passes your niuX sign-in token to the extension so it can make authenticated requests to api.niux.win. The extension sends the X handle used for invitation and account matching, task claims and execution handoffs, and task reports containing a task ID, observed action status, an action or reply post ID when available, and observation timing where supplied. niuX stores these reports with the task and account records and uses server-side checks for verification and virtual-credit accounting. The extension receives account and public X profile details, task targets and status, virtual-credit balances, reward summaries, and trust ratings from the niuX API to display your task workspace. The website reads the extension ID and version to check installation and compatibility. Opening a task navigates to its designated X profile or post; you perform the follow or reply yourself on X. The extension does not prepare, enter, or publish reply text. The extension also sends its installed version and task-protocol number with API requests for compatibility decisions; this metadata is not proof of account identity or completed actions.
How We Process Information
We use account and session information to authenticate you and control access. X profile information, language preferences, and creator interests support account binding and task matching. Task targets, action observations, and verification results support task execution, duplicate prevention, virtual-credit accounting, task trust ratings, and abuse investigation. IP, browser, and device-related records support session security and signup-reward abuse prevention. Request and error records help operate and troubleshoot the service.
Storage on Your Device
The task-focused extension uses Chrome local storage for the niuX authentication token and interface language. Chrome session storage holds active and paused task context and page display state; reply observation evidence is held temporarily in memory. The task-focused extension does not create new IndexedDB workspace, post-body, or draft records. Upgrading from older releases does not automatically erase their existing IndexedDB data, saved model credentials, or legacy settings. The current task interface does not read or use these legacy records. They may remain in your browser profile until you remove the extension or its stored data through Chrome. The niuX website uses cookies for sign-in and browser storage for preferences, device identification, and extension discovery. Clearing website cookies does not by itself clear the extension's separate storage.
Server Storage and Data Sharing
Cloudflare hosts the niuX website and API. Account, profile, task, verification, and credit records are stored in Cloudflare D1; uploaded files use Cloudflare R2, and service diagnostics use Cloudflare logging. Google processes sign-in under its own privacy practices. To retrieve public X profiles and verify follow or reply actions, our server sends the relevant public handles, X account IDs, or post IDs to TwitterAPI.io (api.twitterapi.io) and processes the returned profile and action information. Public creator profile and promotion target details are shown to other niuX users as part of task discovery and execution; relevant task results are available to the users involved. We do not sell personal information. When profile images are displayed, their image hosts, such as X or Google, receive normal image-request metadata, including your IP address.
Optional Service Providers
If server-side language classification is configured, niuX may send a newly retrieved public X display name and biography to JEV at TypeSafe.ai (api.typesafe.ai) to suggest a primary content language. The task-focused Chrome extension has no personal API-key settings or direct requests to external AI model providers. The niuX website uses Google Analytics to measure page visits, navigation, browser/device information and referral sources. Our page tracking omits URL query strings and fragments, and disables Google signals and advertising personalization. Google Analytics can use cookies. If Tawk.to support chat is configured, it receives the name and email supplied to the widget and the messages you send.
Retention and Account Closure
Server account, profile, task, verification, and virtual-credit records persist to support ongoing service, task obligations, accounting, and abuse review. Closing an account ends its active promotion plans, detaches X bindings, and removes niuX server sessions. It is a logical closure: it does not automatically erase the stored user record, sign-in provider records, financial history, or task and verification history. The task-focused extension retains its sign-in token and language preference in Chrome local storage, while active task context uses session storage. Older releases' local workspace data and credentials are not automatically cleared during upgrade, and the current interface has no legacy-history clearing control. You can remove the extension or its stored data through Chrome. We do not specify a fixed deletion period for persistent server records.
Limited Use
niuX’s use and transfer of user data comply with the Chrome Web Store User Data Policy, including its Limited Use requirements. We apply these restrictions to raw, aggregated, anonymized, de-identified, and derived data. Human access is limited to explicit consent for specific data, lawful internal use of aggregated and anonymized data, necessary security investigations, or legal compliance. Transfers are limited to providing or improving the disclosed purpose, legal compliance, preventing abuse, or a merger, acquisition, or asset sale with the user’s explicit prior consent. We do not use or transfer data for personalized advertising, transfer or sell data to advertising platforms, data brokers, or information resellers, or use data for creditworthiness or lending. These restrictions also apply to staff, contractors, and service providers.
Security
We apply reasonable technical and organizational safeguards to protect your data, but no system can guarantee absolute security. Production niuX API requests use HTTPS and authenticated requests use niuX session credentials. Extension storage is separate from website storage and remains part of your browser profile.
Cookies and Similar Technologies
Sign-in cookies keep your niuX session active. Browser storage remembers preferences and the extension installation selected by the website. You can manage cookies and site data through your browser. If enabled, Google Analytics and Tawk.to may also use their own cookies or browser storage for the analytics and support functions described above.
Your Choices and Requests
You can stop using the extension, manage its site access or remove it in Chrome, and sign out of niuX to synchronize sign-out to a reachable extension. Chrome controls can remove extension storage, including local data left by older releases. These actions do not delete niuX server records or posts and follows already made on X; manage X content and relationships on X. Account closure is available in account settings and has the retention limits described above. Depending on your region, you may request access, correction, deletion, portability, or restriction of your personal information by contacting support@niux.win.
Contact Us
If you have privacy questions or requests, contact the niuX Team at support@niux.win. Identify the niuX account and the data or request concerned; do not send passwords, sign-in tokens, or API keys.
