Legal
Privacy Policy
Last updated: June 24, 2026
This privacy policy explains the information AstraQore AI may collect for early access, AstraQore Market Library orders, digital delivery, support, analytics, and future account workflows. It is prepared for review and editing and is not legal advice.
Published by J&V Wealth Holdings OPC through Luminara Media and Publications. Developed by Formastra Platforms, the IT division. Educational market research only. No investment advice, brokerage services, crypto trading services, managed funds, trade commands, guaranteed signals, or profit promises.
Operator
AstraQore Market Library is operated by J&V Wealth Holdings OPC. Order, support, payment reference, and delivery records are maintained for the digital educational market research shop.
What information we collect
AstraQore may collect information you submit through early-access forms, shop checkout, support forms, product-interest forms, and future account workflows, plus basic technical data needed for security, abuse prevention, payment operations, and service reliability.
Early-access lead information
Early-access registration may collect email, optional name, trader or investor type, primary markets, plan interest, biggest research pain, consent flags, UTM or campaign fields, user agent, and hashed IP or similar technical metadata if implemented.
How we use information
We may use information to manage the early-access list, process shop orders, provide secure digital delivery, respond to support requests, verify discount or product eligibility, protect the service from abuse, improve the product experience, and maintain operational records.
Payment provider processing
The early-access page does not collect payment information. AstraQore Market Library checkout uses provider-hosted payment handling when configured. PayMongo may process payment details according to its own terms and privacy practices. AstraQore does not store raw card data on its servers.
Future account and subscription data
Future logged-in features may collect account details, authentication status, subscription state, usage limits, watchlists, alerts, AI analysis history, feedback, and billing identifiers. Raw payment card data should not be collected by AstraQore servers.
Shop order data
AstraQore Market Library may collect buyer email, optional buyer name, purchased product IDs and snapshots, order status, payment status, fulfillment status, delivery email status, PayMongo checkout or payment identifiers, secure order access metadata, download grant status, analysis request details if submitted, support request links, and technical metadata for security and fraud prevention.
Shop product interest leads
AstraQore Market Library may collect product-specific interest leads before checkout is available, including email, optional name, digital research product interest, primary markets, optional message, consent records, UTM or campaign fields, hashed IP, user agent, and technical metadata for abuse prevention.
Payment handling
AstraQore stores order and provider reference records needed to reconcile payment, delivery, support, refund review, and webhook processing. Raw card details are handled by the payment provider, not AstraQore servers.
Cookies and local storage
The Market Library cart and saved-product preferences may be stored on your device so your cart can remain available locally. Future logged-in app features may use necessary cookies or similar technologies for authentication, security, and session management.
Analytics
AstraQore uses a centralized analytics event utility for product and checkout operations. Events may include product views, preview opens, add-to-cart actions, cart opens, checkout validation errors, provider redirects, purchase success, search and filter use, related-product clicks, bundle views, and support page opens. Analytics should avoid unnecessary sensitive data such as full buyer email, support message text, order access tokens, or payment details.
Abandoned cart foundation
If a buyer enters an email while products are in the cart, AstraQore may store a pending checkout record with the email, cart product IDs, timestamps, and technical metadata. Recovery emails are not sent by default and require a specific feature flag and configured email provider. AstraQore does not use this foundation for aggressive or unsolicited messaging.
Support requests
Contact Support may collect issue type, order or reference ID if provided, buyer email, message text, technical metadata, and notification status. Support requests may be linked to matching order records only when the buyer email and order reference match.
Data sharing and service providers
Information may be processed by service providers that support hosting, database infrastructure, authentication, email delivery, security, payments, support, or product operations. We do not sell early-access registration data.
Data retention
Order, payment, fulfillment, support, and security records may be retained as needed for accounting, delivery, fraud prevention, support, policy compliance, and dispute handling. Early-access and product-interest data may be retained for campaign management, launch communications, discount eligibility, security, and product research unless deletion is requested where applicable.
User choices and opt-out
Users may request to opt out of launch updates, ask about their submitted information, or request privacy review through the Contact Support page. Some operational records may need to be retained where required for payment, tax, security, legal, or dispute reasons.
Security measures
AstraQore AI is built with server-side secrets, authentication controls, row-level security, validation, and abuse controls. No security measure can guarantee absolute protection.
International processing
Data may be processed in jurisdictions where service providers operate. Region-specific privacy notices should be reviewed before relying on this policy for a particular jurisdiction.
Contact
Privacy questions can be submitted through the Contact Support page. Do not include card numbers, passwords, private keys, or unnecessary sensitive information in support messages.