This policy explains what information ArbLense collects, why it is used, when it may be shared, and how users can contact support.
This Privacy Policy applies to ArbLense accounts, scanner pages, Pro checkout, personalized early-access links, support interactions, and optional product analytics.
Account, security, early-link opening, and confirmed-payment records are needed to operate the service. Optional analytics and detailed page-view tracking stay off until you expressly allow them.
ArbLense may collect account identifiers such as email address, Google account identifier, display name, internal account ID, and Telegram username when you provide it for support.
ArbLense records successful registration submission and completion, authentication-method linking, password set/reset, successful login, explicit user logout, checkout and payment status, and the opening of a personalized early-access link. The authentication audit does not store email, Google subject, passwords, authentication tokens, raw IP addresses, or user-agent strings.
Password setup and reset use purpose-bound, single-use token hashes that expire after 15-30 minutes. Raw password tokens and pending plaintext passwords are not stored. Privacy-safe keyed request buckets are retained briefly to limit abuse without retaining the source address in the password-request record.
After optional analytics consent, ArbLense may collect referrer, page events, scanner usage, and a Google Analytics client identifier. Personalized early-access links may associate allowed page views with an invite journey and later with an account; an email mismatch is marked as assisted rather than treated as verified identity.
A paid AdsGram landing link may contain an opaque advertising click record. ArbLense may retain that record in first-party browser and account storage for up to 30 days so a completed new-account registration can be attributed. The record is removed from the visible URL and is not included in Google Analytics events.
ArbLense does not require passport data, government identity documents, company registration documents, photos, seed phrases, private keys, or venue credentials to use the public scanner or start Pro checkout.
Information is used to operate accounts, maintain scanner access, process Pro checkout and reminders, provide support, send service notices, prevent abuse, analyze product reliability, and improve ArbLense.
Payment-related information, where applicable, is used only to provision a 2328 Static Wallet address, reconcile signed deposit webhooks and weekly invoices, handle card-payment interest events, paid access, support, refunds, provider requirements, fraud prevention, accounting, and consented aggregate purchase analytics.
When analytics consent and a valid Google Analytics client identifier are both present, ArbLense may send a server-side purchase event containing transaction ID, amount, currency, and product name. Email, ArbLense account ID, invite ID, and other direct personal identifiers are not sent in that event.
When a new account carrying an AdsGram click record completes registration, ArbLense may send AdsGram that opaque record and registration goal number. The request does not contain the account email, ArbLense account ID, Google identifier, password, or session token. Ordinary sign-in is not reported as a registration.
Google Analytics, Google Tag Manager, and Ahrefs Analytics are not loaded before optional analytics consent. You can reject them initially or withdraw consent later through Analytics preferences in the site footer.
While your analytics choice is undecided, landing campaign parameters may be held only in temporary first-party session storage so they survive navigation in the current tab. They are not sent to analytics services or product-event APIs before consent, and they are deleted if you reject analytics.
Withdrawing consent stops new optional analytics, removes accessible Google Analytics cookies and stored campaign attribution from this site, and clears analytics permission from unpaid checkout intents associated with the signed-in account. It does not erase first-party account, security, early-link opening, or confirmed-payment records needed to operate and audit the service.
AdsGram registration attribution is separate from optional product analytics: rejecting Google Analytics does not delete an active AdsGram click record before its 30-day expiry or prevent a one-time registration confirmation.
ArbLense does not sell user data. Information may be shared only when required by law, when needed to operate the service, when needed for approved payment or support workflows, or when the user has consented.
Third-party venues, analytics tools, hosting providers, authentication providers, and payment providers, including 2328, have their own rules and policies. Users should review those third-party terms before using them.
AdsGram receives only an opaque click record and a registration goal number for AdsGram-attributed new accounts; it does not receive the ArbLense account profile through this integration.
Successful registration, login, and explicit logout audit events are retained for 365 days. Consented early-access page-view events are also limited to 365 days; account, entitlement, payment, invoice, and legally required records may be retained for the period needed to operate the service and meet legal obligations.
Expired password-request records and token hashes are retained only as needed for abuse prevention, security audit, and safe single-use enforcement. Security notices may be sent when a sign-in method is added or a password changes.
ArbLense uses reasonable technical and organizational measures to protect information, but internet transmission and third-party systems cannot be guaranteed to be absolutely secure.
Users are responsible for keeping their account credentials, venue credentials, wallets, devices, and communication channels secure.
Do not send seed phrases, private keys, venue passwords, or other sensitive credentials to ArbLense support.
ArbLense may update this policy. The current version is published on this page, and continued use of the service after an update means acceptance of the updated policy.
Privacy and support questions can be sent to info@arblense.com or to the direct Telegram bot username @arblense_bot.