Sign inRegister

PoolIndex Privacy Notice

Version 2026-11-01.2. Effective 2026-10-11. Last updated 2026-10-28. © 2026 PROSYS SOUTH, Israel. All rights reserved. This document is not a legal certification.

Who operates PoolIndex

PoolIndex is operated by Lior Ziv Elbaz, an Israeli sole proprietor (Osek Murshe) trading as PROSYS SOUTH (Prosis Darom), Israel. Lior Ziv Elbaz is the controller (owner of the database) of the personal data described in this notice. Privacy questions and requests: privacy@poolindex.app. General contact: support@poolindex.app. This notice covers the PoolIndex website, the Windows desktop application, and the Android application, and describes what they actually store. It is not a claim of certification under any privacy statute.

Information you must provide

To create an account you must give an email address, a password and a display name (2 to 40 characters; it can be a nickname, not your real name), confirm that you are 18 or older, and accept the Terms of Use and this notice. Without them we cannot open an account or provide the Service. Everything else (the public wallet addresses you choose to check, search and Deep Hunt queries, feedback, support messages) is optional, although some features need it. No law requires you to give us any of this information.

Automated decisions

PoolIndex does not make decisions about you based solely on automated processing that have legal or similarly significant effects on you. Scan results and safety checks are information for you to assess; they do not decide anything about your account.

Account data

WHAT: email, password hash (not the password), display name, unique user ID, invite code (if you registered with one), role, plan, account status, created/last-login timestamps. WHY: authenticate you, keep accounts separate, and enforce plan limits. WHERE: isolated account files on the operator host. RETENTION: while the account exists, then as described in this notice. WHO: you (your own record) and PoolIndex operators/admins. THIRD PARTIES: an external email provider (Resend) that delivers account email, when one is configured on the server.

Consent records

WHAT: user ID, Terms version, Privacy version, acceptance timestamp, and the site language at the time of acceptance. WHY: prove you accepted the documents you were shown; support later re-acceptance when versions change. WHERE: your account record on the operator host. RETENTION: with the account. WHO: you and operators. Checkboxes in the UI are not sufficient by themselves; the server rejects registration without acceptTerms and acceptPrivacy.

Public wallet addresses

WHAT: the public wallet address you check in the Windows or Android application, stored in a wallet slot of your plan; for older access codes on an account, if any, a fingerprint (hash) and the last 4 characters. WHY: the address is recorded with the account so the plan's wallet limit can be enforced and your device can check it. The record shows only that the address was checked or is monitored with this account. It is not proof or a claim of ownership, and PoolIndex does not verify ownership. WHERE: the address is stored on the server, and so are the hash and last 4 of any older code, with an encrypted copy that only support can use. In the Windows and Android applications, wallet check results stay on the device that ran the check: on your PC in the Windows application, and in the Android application's storage on your phone (the latest results for each address you checked, and the address you are typing). They are not uploaded to the operator host. The website itself has no wallet check. A Windows application without the on-device check (older versions) sends it to the operator host, which holds the result in memory for up to 30 minutes after the check ends so the application can collect it, and does not save it to a file on the server. Daily monitoring and Deep Hunt wallet research also run on the operator host and save their results there (see Scan activity and telemetry). For searches that run on the operator host, the account's scan records keep the type of query (wallet, link, code or text search), the sources, the outcome and the duration, not the query text or the URL. Deep Hunt keeps its query text (see Deep Hunt and leads). RETENTION: the address stays in its wallet slot until an operator releases it or the account is deleted. Files on your device remain until you delete them. In the Android application, clearing the application's data or uninstalling it also removes them. Uninstalling the Windows application downloaded from poolindex.app does not remove them: they stay in the PoolIndex folder in %APPDATA% until you delete that folder. Scan records on the operator host: see How long we keep data. WHO: the operator host for the binding and scan records; you, on your device, for local results. PoolIndex never asks for your seed phrase or private key. Secret-shaped input is rejected.

For Solana addresses, the Windows application reads the address's public on-chain data directly from a public Solana RPC endpoint (by default api.mainnet-beta.solana.com). That endpoint receives the address and your device's IP address. To show token names and prices, the application sends the token mint addresses it found, never the wallet address, to Jupiter's public token service (lite-api.jup.ag), which also receives your device's IP address. These services are independent third parties with their own privacy terms; PoolIndex does not send them your email or account details.

The PoolIndex phone applications (Android and iPhone) check Solana addresses the same way: directly from your phone to a public Solana RPC endpoint and to Jupiter's token service, as described above.

Plan usage

WHAT: your plan, the end date of a running Pro month, the calendar month and the number of link checks used in it, a reference for each Pro month applied to the account, and your PayPal subscription id and its status. PoolIndex does not receive or store your card number or PayPal login; PayPal processes the payment under its own terms and privacy notice. The checked URL is not stored in this counter. WHY: enforce plan limits and renew Pro on the server. WHERE: your account record on the operator host. RETENTION: with the account. WHO: you and operators.

Sessions and tokens

WHAT: HMAC-signed session cookies, session IDs, email-verify and password-reset token hashes, expiry times, and hashed read-only MCP tokens (name, scopes, created/last-used/revoked). WHY: keep you signed in, complete verification/reset, and let you connect your own agent. WHERE: HTTP-only cookie plus isolated account files on the operator host. RETENTION: sessions expire (after about one week) or are revoked on logout/disable; unused tokens expire; MCP tokens until you revoke them or the account is closed. WHO: the operator host. The raw MCP token is shown once and is not stored. IP addresses are not stored in the session record.

Agent connection logs

WHAT: MCP tool name, timestamp, optional public wallet address, success/failure. WHY: you can see what your connected agent requested. WHERE: an isolated per-user log on the operator host. RETENTION: a short rolling log (about 200 rows). WHO: you (your log) and operators. PoolIndex does not send these calls to a language model.

IP and security events

WHAT: security log lines may include event type, user ID, email, optional IP (login attempts), and a short detail code. WHY: detect abuse, lockouts, and admin actions. WHERE: operator security logs. RETENTION: see How long we keep data. WHO: operators. Rate limiting also keeps short-lived in-memory IP counters that are not written as a user profile.

Scan activity and telemetry

WHAT: search, Deep Hunt and resource events (event type, hunt id, sources used, duration, item counts, blocked counts, source failures, resource-limit events), application errors with a short technical description, app version, user ID. These logs do not keep the text of a search or a Deep Hunt query; search records keep only the type of query. Wallet checks that run on your device (Windows or Android application) are not written as scan history on the operator host. WHY: debug product quality and host protection, not advertising. WHERE: isolated operator logs for website, hunts, and crashes you submit. RETENTION: see How long we keep data. WHO: operators for host logs. Daily monitoring (PoolIndex Pro, and operator admin accounts) checks bound wallets on the operator host and keeps the latest result and a short history (the last 30 checks, as counts) for each monitored address there, to detect changes and send alerts; the free plan has no daily monitoring.

Signup statistics: when an account is created, PoolIndex counts it by country (from Cloudflare, as a two-letter code), by kind of client (website, Windows, Mac, Android or iPhone application) and by where the visit came from (for example google, x.com or direct). Only these counts are kept. They are not linked to your account, and the IP address is not stored for them.

Deep Hunt and leads

WHAT: hunt records (the query text you typed, up to 120 characters; plan, progress counters, public URLs seen, lead cards, evidence snippets from public sources, optional public wallet used for research, pause/stop state). A query can contain personal information, so do not type anything you do not want stored. WHY: persist an investigation you started so it survives refresh. WHERE: isolated per-user hunt files on the operator host. RETENTION: until your account deletion is processed; they are then deleted. WHO: you (your hunts) and admins (stop/stats). Continuous Hunt, if enabled later on Pro, re-reads stored public leads. PoolIndex does not access private blockchain information.

Feedback

WHAT: feedback type, optional short note, source name, claim/lead id, result host, app version, status. WHY: judge whether results help users. WHERE: isolated operator records. RETENTION: until you ask us to delete it or your account deletion is processed. WHO: you and operators. Notes that look like seed material are rejected.

Email / outbox

WHAT: verification, password reset, hunt-notification, and (on PoolIndex Pro) monitoring alert mail (recipient, subject, body/link, timestamp). The free plan does not include email notifications. Wallet addresses in the stored copy are shortened. WHY: operate the account and alerts. WHERE: the external email provider (Resend) that delivers the mail, when one is configured on the server; a copy is kept in the operator outbox only when sending fails or no email provider is configured. RETENTION: the outbox copy, see How long we keep data; when Resend is used, it keeps email and its logs for 30 days and its own backups for 7 days, under its own terms. WHO: operators and, when used, Resend. Terms acceptance is not marketing consent. PoolIndex does not send promotional mail.

Support messages

WHAT: messages you send to support from the support page while signed in, email replies you send to your personal support reply address, our replies, and short internal notes by operators about your request, with the date, the channel (website or email) and whether an email reply came from your account email address. WHY: answer your questions and handle your account requests. WHERE: the operator host, one conversation per account, with the message text encrypted at rest. Our replies are emailed to you through the external email provider (Resend) when one is configured, and email replies to your support reply address are received through Resend. Operators get an email alert with your customer number only, not the text. When an operator asks for a suggested reply, the conversation text (without internal notes), your plan and your account state are sent to Anthropic, an AI provider, which returns a draft under its own terms; an operator reads and edits every reply before it is sent, and your email address, name and wallet addresses are not sent. RETENTION: until your account deletion is processed. WHO: you (your messages and our replies, on the support page) and operators (everything, including internal notes). Never send a seed phrase, recovery phrase or private key; such text is rejected.

Admin actions

WHAT: invite creation, user status/plan/role patches, kill-switch changes, feedback status, hunt stops, deletion processing. WHY: operate the service. WHERE: operator state and security logs. WHO: operators with the admin role.

How long we keep data

  • Account data, consent records and plan data: while the account exists. When your account deletion is processed they are deleted, except a minimal record (a random id and dates, marked as deleted).
  • Sessions: about one week, or until you sign out. Verification and password reset links expire.
  • Agent connection log: the latest 200 or so rows.
  • Search scan records, Deep Hunts, monitoring results and feedback: until your account deletion is processed. Results kept for a wallet address that another account still uses stay for that account.
  • Support messages, our replies and internal notes: until your account deletion is processed.
  • Security events, telemetry, error rows and the outbox copy of email, while the account is active: no fixed automatic deletion period has been set yet. When a period is set, it will be published here.
  • After your account deletion is processed: the outbox copies of email sent to you are deleted; telemetry, error and download rows are kept without your account id; security events are kept without your email address, still with the random account id and IP addresses, for 90 days, and are then deleted with the minimal record and the deletion request.
  • Database backups: they can contain your data until they are deleted. The backup deletion period has not yet been confirmed on the server; it will be published here once it is.
  • Resend (email delivery, when it is used): 30 days for email and its logs, 7 days for its own backups.
  • Files on your device: until you delete them.

An account whose email is not verified within 24 hours of sign-up is deleted, together with its sessions, verification tokens and security log lines.

International hosting and APIs

The operator host is the machine running PoolIndex; it is located in Israel (confirmed by the operator). Website and application traffic reaches it through Cloudflare, which processes network data such as IP addresses to deliver and protect the connection. Searches and hunts on the operator host query public services (GitHub, Internet Archive and Wayback Machine, Reddit, Bitcointalk), and prices are read from CoinGecko. Wallet checks in the Windows and Android applications send the public address you check directly from your device to public blockchain RPC endpoints and block explorers; they also download published airdrop data from GitHub and jsDelivr, which see your device's IP address and, for some checks, the first characters of the address; the Android application also looks up host names through DNS-over-HTTPS (Cloudflare or Google). Email can be sent through an external email provider (Resend) when one is configured on the server. Israel is the location of PoolIndex's own server only: these providers process data in their own locations, which can be outside Israel and outside your country, under their own terms.

Solana checks in the Windows application also contact a public Solana RPC endpoint and Jupiter's public token service, as described in "Public wallet addresses".

Cookies and device storage

Cookies (first party only; no advertising or analytics cookies): poolindex_session keeps you signed in (HTTP-only, about one week); poolindex_entitlement is a signed record of your plan and the public wallet addresses on it (HTTP-only, up to 180 days); pi_locale remembers the language you chose (one year); poolindex_desktop marks the Windows application; poolindex_admin_mfa is set for admins after the authenticator check. Device storage: the website keeps display preferences (text size, high contrast) in browser storage; the Windows and Android applications do not have these two settings. The website and the applications keep the address you are checking and wallet check results in the browser or application storage on your device. PoolIndex does not use third-party analytics or advertising trackers.

Until the browser tab is closed, the website and the applications keep in session storage where the visit came from (the utm_source of the link or the name of the referring website, never the full page address), and send it once when you create an account.

Security

Connections to PoolIndex use HTTPS. Passwords are stored only as scrypt hashes. Session and plan cookies are signed and HTTP-only. Sign-in and other sensitive actions are rate limited. Admin accounts can require an authenticator code. Seed phrases and private keys are rejected in input fields. No system is perfectly secure; report a security problem to support@poolindex.app.

Your requests

You may request account deletion, access to your personal data, a correction, or a privacy question from the account page (on the website; in the Windows application, select your email address at the top of the window; in the Android application, open Account) or by emailing privacy@poolindex.app. Access is not limited to your account record: you may ask for the personal data we hold about you, including scan records, Deep Hunts, log rows linked to your account id or email address, and your privacy requests, subject to the law and to other people's rights. The steps, and what deletion removes and keeps, are on the public page /delete-account. You confirm with your password and by typing DELETE, and an operator then processes the request in accordance with applicable law, within 30 days of the request. Sending a deletion request signs you out on every device and stops the account at once, but it does not delete the data yet: the data is deleted when an operator processes the request. To cancel the request before it is processed, email the privacy address. Processing deletes your email address, display name and password, the public wallet addresses linked to the account, scan records, Deep Hunts, agent tokens and logs, sessions, feedback and privacy requests, plan data, and PoolIndex's copies of mail sent to you; the account record keeps only a random id and dates, marked as deleted. Kept for 90 days after processing and then deleted automatically: that minimal record, the deletion request, and security events without your email address (they still contain the random account id and IP addresses), to protect the service against abuse. Database backups can contain your data until they are deleted; they are used only to recover the service after a failure, and their deletion period will be published once it is confirmed on the server. When email is sent through Resend, Resend keeps email and its logs for 30 days and its own backups for 7 days. Telemetry, error and download rows are kept without your account id. User A cannot request deletion of User B.

Users in Brazil

If Brazil's General Data Protection Law (LGPD) applies to you, you may ask us to confirm whether we process your data; give you access to it; correct incomplete, inaccurate or outdated data; anonymize, block or delete data that is unnecessary, excessive or processed unlawfully; port it to another provider; tell you which public and private entities we share it with; tell you about the possibility of not giving consent and its consequences; and revoke consent. You may also petition the Brazilian data protection authority (ANPD). Our channel for data protection matters: privacy@poolindex.app.

Changes

If collection practices change, we publish a new Privacy version. You may be asked to accept it before continuing.