What We Collect
Depending on how you use the site, PriceLens AI may collect account details, account creation details, newsletter signups, feedback form messages, chart or market-analysis inputs, and general product-usage information.
- Name and email address when you create an account or sign in.
- Passwords are processed for account access through the authentication service and are not shown back to us in plain text.
- Email address for newsletter signups.
- Messages you send through the Contact Us forms.
- Chart screenshots, ticker searches, timeframe selections, and analysis inputs.
- Trading-plan settings, manual journal entries, alert conditions, alert events, and delivery preferences you choose to save.
- Push-subscription details and a short device label when you explicitly enable Mobile App notifications on a device.
- Basic product usage and analytics events tied to your session or signed-in account.
- Subscription identifiers, purchase status, renewal dates, and plan information needed to verify paid account access across devices.
Cookies, Browser Storage, and Analytics
PriceLens AI currently uses cookies and similar technologies, including browser storage, to keep the workspace functioning, reduce abuse, and understand how the product is being used.
- Authentication and session tools help manage sign-in and account access.
- Security challenges and abuse-protection tools help detect spam or automated attacks.
- Product analytics tools help measure in-app behavior and feature usage.
- Website analytics tools help measure traffic and engagement.
- Session and local storage are used for workspace preferences and product state.
These technologies may store identifiers in the browser or process usage information such as page views, feature interactions, device/browser details, approximate location, and security signals.
Our Android and iOS apps also use PostHog to measure app launches, updates, first tracked launches, app version, installation source, and crashes. When you sign in, app activity can be linked to your account identifier. Crash messages and request content are removed from reports. Session replay masks inputs and private account content; it helps us understand how the app is used.
Third-Party Services
Chart screenshots are sent to OpenAI for image analysis. AI follow-up questions send OpenAI your question, recent chat messages, current analysis context and account plan to generate an answer. Remove personal or account details from images and messages before submitting them. The iOS app asks for permission before each of these requests; cancelling leaves the request unsent. OpenAI processes submitted content under its applicable service and retention terms; see OpenAI's privacy information.
PriceLens AI currently relies on third-party providers in categories like:
- Authentication and account-storage providers.
- Email delivery and newsletter providers.
- Browser and operating-system push-notification services for devices you enroll. Android app alerts use Google Firebase Cloud Messaging, which receives installation and registration identifiers and the alert content needed for delivery.
- Analytics and product-measurement providers.
- Bot, security, and abuse-protection providers.
- Market-data providers.
- Hosting and deployment infrastructure providers.
- Stripe for website billing, and Google Play or the App Store with RevenueCat for subscription processing and verification in supported native apps. RevenueCat receives your PriceLens account identifier and store subscription information to associate verified purchases with your account.
Specific providers may change over time as the product evolves, but the functions above describe the current categories of external services involved.
How We Use Information
- To operate the login, access-request, newsletter, and feedback workflows.
- To deliver analysis results, forecasts, and market-data responses.
- To verify subscriptions, restore purchased access, and apply one shared account usage allowance across devices.
- To evaluate enabled price-alert conditions, synchronize your manual trading workspace, and deliver the email or Mobile App notifications you request.
- To secure the product against spam, bots, and abuse.
- To understand product usage and improve reliability, clarity, and user experience.
- To communicate product updates, approvals, newsletters, or support responses.
Your Uploaded Charts and Content
If you upload charts, screenshots, or other materials, you remain responsible for making sure you have the right to use and submit that content. Third-party charts, market data, trademarks, and screenshots remain subject to the rights of their respective owners.
Contact
For privacy, newsletter, or support questions, contact support@pricelensai.com.
You can pause alert channels or remove an enrolled notification device from the Trading Dashboard. Browser and operating-system notification permissions can also be revoked in that device's settings.
Signed-in members can choose Account deletion in Account, or Delete account on the account-setup screen. After confirmation, PriceLens removes the login and associated saved forecasts, watchlist, usage records and trading workspace. A success message confirms completion; if a step fails, retry to finish the deletion. You can also contact support if you cannot sign in. Administrative accounts require a review of connected services before removal.
Website subscriptions are cancelled as part of deletion. App Store and Google Play subscriptions must be cancelled separately in the original store to stop future charges. Account deletion does not place or cancel broker orders. Newsletter subscriptions are separate and can be cancelled using the unsubscribe link in an email.
A minimal deletion marker prevents late requests from recreating removed account data. Signup security events are unlinked from the account and retained for the existing 35-day abuse-prevention window. Payment records, support correspondence and records held by service providers may remain subject to their retention requirements. Contact support for requests involving those records.
Last updated: September 27, 2026.