AEROX · SERVICE INFORMATION
Privacy notice
Updated October 6, 2026
Who operates AEROX
AEROX is operated by Amir Shchors, a sole proprietor trading as AEROX in Israel. For privacy questions and requests, contact aerox.asp@gmail.com.
Information processed
AEROX processes account details used for sign-in, including your email and the name you provide. Your saved workspace can contain client names and emails, account labels, transactions, cash movements, notes, prices, watchlists and valuations. Chat messages and support requests are stored when you submit them. Service logs and usage counters support troubleshooting and request limits.
Why the information is used
We use this information to authenticate users, keep each workspace separate, calculate portfolio results, provide the features you request, respond to support requests and manage subscription access. Upload client information only when you are authorized to do so. Do not put passwords, payment-card details or unnecessary identity documents into notes, chat or support messages.
Service providers
Authentication uses Supabase; transactional email uses Resend. The website and workspace storage run through Sites hosting infrastructure. Market-data requests can disclose requested stock symbols to the configured data provider. With your permission, embedded TradingView news and charts loads third-party content, which can receive browser and network information under its own privacy practices.
When AI is activated, messages and recent conversation history are sent to OpenAI. If portfolio context is enabled, calculated totals, holdings and dated valuations are included; the automatic portfolio context excludes client names, emails and internal notes. Anything you type into a message is still part of that message. Company research may retrieve public filings. Paid checkout, when activated, sends payment information directly to the payment provider; AEROX uses subscription and payment identifiers to manage access.
Cookies and optional content
Essential authentication cookies (aerox-auth and related session cookies) maintain sign-in and account security. Optional TradingView embeds are blocked until you select “Allow external market content.” These embeds may set their own cookies and receive your IP address and browser information. You can choose “Essential only” and continue using AEROX.
We remember your choice in browser local storage under aerox-privacy-v1 for 180 days. Use the Cookie settings button to change or withdraw permission. Withdrawal removes embedded news and charts and prevents new loads; it cannot undo information already sent or delete third-party cookies. You can clear those through your browser settings. If browser storage is blocked, the choice applies only to the current visit. We have not added advertising or analytics trackers to the application.
Retention
Authentication uses cookies to maintain your session. Workspace records, chat and support history are persisted so they remain available when you return. Automatic deletion after a fixed period is not currently implemented. Clearing chat removes that chat history from AEROX’s active chat store; it does not itself request deletion from infrastructure or service-provider records.
Your controls
You can download your workspace backup in Workspace settings, edit supported workspace records, and clear saved chat history from AI chat. To request account deletion or ask about your information, email aerox.asp@gmail.com or open the Support tab described in Help. Identity verification may be needed before access or deletion is handled. An account-wide self-service deletion button is not yet available.
Changes in ownership
If AEROX is incorporated, reorganized, merged or sold, relevant information may be transferred to the successor where lawful and necessary to continue the service. The successor must respect applicable privacy obligations and the disclosed purposes of processing. This is not permission to sell client records for unrelated advertising. Any due-diligence disclosure must be limited to what is necessary, subject to confidentiality and applicable law, and use aggregated or de-identified information where practicable. Affected users will be notified of a change of operator or material processing changes; consent will be sought where required.
Before sharing client information
Consider whether client names or other identifying details are necessary for your workflow. Exported files contain private information and should be protected. This notice describes the current implementation; features that are awaiting activation do not yet send requests through those integrations.