Privacy Policy — TaskFlow Helper
Last updated: 2026-09-30
TaskFlow Helper ("the extension") is a browser extension for authorized
users to automate repetitive payout-processing actions on a specific
trader dashboard (the "supported site"). This policy comprehensively
explains what data it collects, how it's used, where it's stored, and
every party it's shared with.
What the extension collects and why
- Login credentials (email + password): entered in the
extension and sent directly to our authentication provider (Supabase) to
sign you in. They are not stored by the extension after sign-in.
- Session token: returned on login and stored locally in
your browser to keep you signed in. Refreshed as needed. Sent to
Supabase to authenticate each request the extension makes on your
behalf (see below).
- Trader account identifier (username): the extension
reads your username from the supported site's own authentication token
to lock your account to a single identity (anti-sharing). Sent to and
stored in Supabase for your account.
- Device identifier: the extension generates a random
identifier (not derived from hardware, IP, or browser fingerprint) and
stores it locally. It's sent to Supabase to enforce a single active
device per account and is stored there against your account.
- Transaction/payout activity log: each time the
extension accepts (or attempts and fails to accept) a payout on the
supported site, it sends the payout ID, amount, outcome, failure reason
(if any), and retry count to Supabase. Used to enforce your account's
transaction limit and to keep an audit trail.
- Payout payment details ("requisites"): as payouts
appear on the supported site, the extension reads the payment details
already shown there — payout ID, amount, status, payment method, and
the associated payee's bank/payment account name, account number, and
bank routing code (IFSC) — and sends them to Supabase for
record-keeping and dispute resolution. This data describes the payment
counterparties of transactions carried out through the supported site
under your account; it is collected only because it is shown on
payouts the extension processes there, not collected about you
directly.
- Extension version: sent with each authorization
request so the operator can gate outdated builds. Not linked to any
other identifying data beyond your account.
- Settings and local activity log: limits, timers, and
the recent activity feed shown in the popup are stored locally in your
browser only; never uploaded.
Where data goes / who it's shared with
Supabase (our authentication
and database backend) is the only party any of the data
above is sent to — it is the extension's sole backend for sign-in,
per-account configuration/binding, transaction/audit logging, and
payout-requisite storage described above. Nothing is sent to any other
third party. There is no analytics, tracking, advertising, or sale of
data, and no remote code is loaded — all code ships in the extension
package.
Data retention
Local data (session, settings, logs) stays in your browser until you
clear it or uninstall the extension. Account, configuration, binding,
transaction-audit, and payout-requisite records remain in Supabase until
deleted by the operator or upon a deletion request (see Contact below).
Permissions
The extension requests only what it needs to function: local storage
(settings, session, logs), access to the active tab to start/stop the
automation, and network access to the supported site (to read payout
data and submit accepts) and Supabase (authentication, configuration,
and the logging described above).
Contact
Questions or data-deletion requests: chandrajeetbij@gmail.com