VEKTOR

Privacy policy

Effective 7 October 2026. VEKTOR is operated by Vectorcrypte, not a registered company. Support: support@vectorcrypte.com. Privacy, access, correction or deletion requests: support@vectorcrypte.com.

Information we use

Wallet sign-in stores your public Ethereum-compatible address and links it to saved predictions, monthly usage, exchange preferences, demo trades and payment invoices. A wallet address is not anonymous. Existing ChatGPT accounts use the platform account identifier and email; email-code accounts store a verified email address. These sign-in methods are separate accounts unless explicitly linked through a supported ownership-verification process. We do not request seed phrases, private keys, trading keys or sign-in token approvals.

Why we use it

Account and subscription data are necessary to provide your requested service. Security records help prevent replay, abuse and payment fraud. Payment records support accounting, disputes and applicable legal obligations. Optional analytics and marketing operate only with your separate consent; withdrawing it does not prevent use of your account. Where data-protection law requires particular lawful bases or safeguards, the operator remains responsible for satisfying them.

Sign-in and essential storage

A one-time wallet message proves account control; it does not authorize payment or trading. Challenges expire after five minutes and sessions after 24 hours or sign-out. When enabled, email-code login sends a six-digit code in your selected language through Resend. Codes expire after ten minutes, have at most five attempts, and are bound to the requesting browser. Codes are stored as keyed hashes, never in plaintext; sessions expire after 24 hours or sign-out. Sending is rate-limited per network, recipient and daily operator budget. Only session-token hashes are stored. Essential HttpOnly cookies bind sign-in to a browser. Short-lived hashed network identifiers rate-limit attempts. Expired security records are removed in bounded batches during later sign-ins, not necessarily at their exact expiry time.

Reown/WalletConnect uses connection infrastructure and pairing storage. Language and manual timezone choices are remembered in essential first-party cookies for up to one year. Automatic language uses the hosting platform’s approximate IP country, then browser language; it can be overridden. We do not store the raw IP address for language selection or send it to a separate geolocation service. Automatic timezone uses your device setting, with platform location metadata or UTC as a fallback. Theme, notification and cookie choices, recent-alert deduplication and a pending-payment hash may be stored on your device. A pending hash is a recovery aid, not proof of payment.

Optional Google Analytics, Meta Pixel and X Pixel

Google Analytics measures consenting visits and verified new-account/approved-subscription events. Meta and X pixels, when enabled, measure consenting marketing visits and confirmed conversions. Analytics and marketing are separate choices, initially off. Optional libraries load only after corresponding consent. Use “Cookie preferences” to reject or withdraw permission at any time.

Browser conversion payloads contain opaque event identifiers and product/event type, not wallet addresses, emails, signatures, transaction hashes or investment amounts. With marketing consent, X server-side conversions additionally use an X ad click ID (twclid), a SHA-256 hash of a normalized verified email, or the hosting platform’s connecting IP address together with browser user-agent details. A hashed email is still personal data, not anonymous data. Wallet addresses and transaction hashes are never sent as advertising identifiers. An HttpOnly attribution cookie and the corresponding server attribution records last up to 30 days. Expired identifiers are removed in bounded batches during subsequent attribution requests. Unsatisfied requests are retried with the same opaque conversion ID to avoid counting twice; they are not proof of a sale until the account or payment has been confirmed by the server.

We do not invent USD revenue from crypto payments. Administrative, profile and API pages do not initialize optional tracking or send explicit page/conversion events. Account and subscription pages may send verified conversions after consent. Public campaign parameters and token symbols can appear in marketing page URLs; unknown or sensitive current URL parameters suppress initialization. Third-party libraries can process IP addresses, browser details and navigation information under their own policies after loading. Marketing-consent withdrawal clears this browser’s attribution, removes signed-in account attribution and prevents further pending server retries; previously transmitted data may remain with the provider.

External services and international processing

The site uses Sites and Cloudflare-backed storage, Reown, TradingView, exchange APIs, DEX Screener and news providers. When configured by the operator, shared X API collection stores short public post excerpts, source links and timestamps for up to seven days. Provider credentials are encrypted server-side. Ethereum verification queries a public blockchain RPC provider (PublicNode by default). Resend processes the destination email address and localized sign-in message when email login is enabled. Sending-domain verification and a configured provider are required. This is transactional email, not marketing consent. Optional tracking uses Google, Meta and X. Providers may process data outside your country under their own terms and safeguards. Trading links leave VEKTOR. On-chain transfers and submitted hashes are public; VEKTOR cannot erase blockchain records.

Watchlists, support records and sharing

Your watchlist is saved to your account and synced across signed-in devices. The operator can see account usage, invoice status and private support notes to help resolve access problems. Share buttons generate images on your device, without automatically publishing your saved record or account details. You choose whether to download the image or share it through your device’s share sheet. Shared images may reveal the token, scenario, result or demo trade that you chose to share. Demo cards are marked as virtual funds.

Retention and your requests

Account records and saved research remain until an authenticated deletion request or operator cleanup. There is no automatic inactivity-deletion timer. Email the privacy contact to request access, correction, deletion or restrictions where applicable. We may ask you to prove account control with a sign-in message, never a seed phrase. The operator reviews and performs deletion manually. Necessary payment, dispute or legally required records may be retained for the applicable period; the reason and expected period should be explained in the response. Third-party and public-chain records are outside our direct control.

Depending on applicable law, you may have rights to access, correction, erasure, restriction, portability, objection and complaint to a data-protection authority. Contacting us first does not remove a right to complain directly. We aim to acknowledge requests within seven days and meet binding legal response deadlines.

Research and notifications

Predictor is a rules-based research tool, not a validated trained forecasting model. A configured analysis gateway may process public events, not private profile data. Browser notifications require permission and currently work while the terminal is open. Email signup is available only after the operator connects a verified sending provider. Email-code login is a single sign-in factor, not wallet-plus-email two-factor authentication. Email 2FA, background push and features marked “Coming soon” are not active.

Changes

Material changes are dated here. A new optional tracking purpose requires an updated consent choice. This policy describes the implemented service; it is not a legal-compliance certification.