Account & service data
Information supports sign-in, membership access, orders and support.
Clear information about your account data, your choices and how to reach us.
Information supports sign-in, membership access, orders and support.
Published community contributions can be read and shared by other visitors.
Contact support@asurlabs.com for privacy questions and rights requests.
Privacy starts with knowing what happens to your information. This policy explains how Asurlabs handles information when you browse our website, create an account, use our research and learning services, purchase access or contact our team.
Asurlabs operates this website from Argentina. The company is owned by Joaquín López.
Business contact address: Córdoba, S2000KZB, Rosario, Argentina, 2206.
Privacy and support email: support@asurlabs.com.
For a question about your information, use the subject “Privacy request” and describe the account or service concerned. Third-party websites and embedded services have their own privacy policies.
The platform handles your name, email address, password hash, account role, membership status and related access records. Optional profile information may include an avatar, location or timezone. Do not put sensitive personal information in a public profile.
Sign-in records can include device or browser information, IP address and session timing. These support authentication, device limits, security and account administration.
To administer a purchase, payment records can include your account identity, plan or product, amount, currency, payment network, order status, invoice information and transaction reference. A manual payment submission can also include the note you provide. These records support payment verification, access delivery, enquiries and financial recordkeeping.
A blockchain transaction reference can connect to publicly visible wallet activity. Public blockchain records are outside our control and generally cannot be erased by us. Do not include a private key, recovery phrase or password in a payment or support message.
Contact and suggestion forms collect the name, email, subject, category and message you submit. Anti-abuse checks use a source identifier associated with the request. Support staff may review the information to respond or investigate a problem.
Forum posts, comments and other published contributions may be visible to other users and search engines. Saved watchlists and learning-related account records support the features you use. Submit only information you are entitled to share.
If the assistant is enabled, questions and responses can be recorded with an account identifier, email or visitor identifier for service operation and review. Avoid entering sensitive documents, passwords, private keys or unnecessary personal details.
When a configured external AI provider is used, your question and relevant platform context may be sent to that provider. The current integration supports OpenAI; an answer can also come from locally configured knowledge. Assistant output may contain mistakes and is not personalised financial advice.
Necessary session cookies help you sign in and stay authenticated. Browser storage remembers preferences such as the selected theme. Disabling necessary storage may prevent account features from working.
Where enabled, Google Analytics receives website usage and device-related information to help us understand visits. Google advertising, YouTube videos and TradingView charts may connect to their providers and use cookies or similar technologies. External providers apply their own privacy terms.
You can manage cookies and stored site data in your browser and choose whether to open optional videos or charts. Cookie settings can affect functionality. See our Cookie Policy for more information. Reading this policy is not a substitute for consent where consent is required.
Information is used to operate accounts and access, process orders, respond to support, moderate contributions, maintain security and understand service usage. Hosting, email, payment-verification, analytics, advertising and AI providers may handle relevant information when those integrations are used.
Authorised staff can access information needed for their role. Information may also need to be disclosed to meet applicable legal obligations. A public post or public blockchain transaction has a different visibility boundary from a private support enquiry.
Retention depends on the type of record and its purpose. Account records support your ongoing access; order and payment records support delivery, enquiries and financial obligations; support and security records help resolve issues and investigate misuse. Some information can remain in backups or records required by law after an account deletion request.
The platform uses password hashes, authenticated sessions and role-based administration. Protect your sign-in details and report suspected account misuse promptly. No internet service or transmission method can provide absolute security.
Hosting and external providers may process information outside Argentina or your country of residence. Ask our privacy contact for information about the providers and processing relevant to your account, or about the retention criteria for a particular record.
Contact support@asurlabs.com to ask what personal information is held about you, request correction of inaccurate information, or request deletion where applicable. Specify the account email and the record or issue concerned. We may need proportionate verification before providing private information or changing an account. Do not send identity documents unless a suitable verification process has been agreed.
Argentina’s personal-data rights include access, rectification, updating and deletion, subject to applicable conditions. The Agencia de Acceso a la Información Pública (AAIP) publishes guidance on exercising these rights and submitting complaints: AAIP personal-data rights.
Our trading-related services are intended for adults. If you believe a minor has provided personal information, contact us. This policy’s published update date identifies the current version; a policy update does not replace a required consent request.