LSKS TEAM
Privacy Policy
Version 2026-11-01.1 — effective November 1, 2026.
Privacy and cookies: information by feature
This policy brings together general information about your data. The cookie policy details technologies and preferences; the Creator Suite privacy annex describes that application's features. Reading this information does not enable optional cookies, promotional communications or permissions to use likeness and voice.
Audio, camera, screen and files
When you use an enabled audiovisual feature, content from the sources you choose to share is processed for delivery to that feature's participants or recipients, together with technical data needed to establish and protect the connection. Review the room's audience and a post's destination before sharing. Connection and activity data differ from audiovisual content; recording participation does not itself mean recording a conversation.
A live transmission, an uploaded file and a recording involve different processing. Files you choose to upload are retained according to their purpose and the periods described in this policy. Creating an account does not authorize recording: if offered, its purpose, access, retention and exercise of rights will be disclosed in advance. A copy downloaded or recorded by a recipient may fall outside LSKS's technical control; that does not grant permission to make or distribute it.
The technical providers involved and transfer conditions are described in this policy and its applicable annexes. A regional preference does not guarantee a storage country. You can send requests about your data or content to the Help Center and the institutional email provided.
1. Controller and contact channels
Operator: Marcos Clainberg Salomon. CUIT: 20-40727353-3. Contact address: Junin 321, PB, oficina 1, San Miguel de Tucumán, Tucumán, Argentina. Tax status: Responsable Monotributo — Categoría H — Locaciones de servicios.
Contact: Monday to Friday, 8:00 a.m.–4:00 p.m. Argentina time (UTC−3). Forms can be submitted 24 hours a day. Official email: soporte@lsksteam.com. No account required: Legal requests.
This policy describes LSKS's processing. Sharing an operator with ClainsTech does not permit combining accounts, marketing lists or information for unrelated purposes. Creator Suite also has a specific policy.
2. Data and purposes
Depending on the features used, we process registration and contact details, account and game identifiers, roles, memberships, preferences, requests and interactions necessary to manage access and the community. Registrations require the data announced in the listing, teams and results. Messages and content someone posts are used for that feature and to handle reports; visibility depends on the chosen space.
We also process technical connection and security data, errors, access events and evidence of acceptance of terms. Legal requests contain a contact email, type, reference and optional description, date, status and handling record. Those forms do not request complete identity documents, passwords or card information.
If commercial transactions are enabled, the order, payment and billing data necessary to fulfill the transaction and applicable obligations will be processed. This provision does not enable sales. Legal request data is not used for advertising.
3. Basis and required information
We process data needed to manage the relationship and requested services, comply with legal obligations and address rights and security within the bases permitted by Argentine Law 25,326. Where processing requires consent, it is requested specifically, with information, and can be withdrawn. Required fields are identified: without them, registering the account or handling the request may be impossible. Optional advertising and promotional likeness permission are not conditions of accepting the general terms.
4. Posts, messages, images and voice
Posting in a public space may make content accessible to visitors, search engines and third parties. Do not publish another person's data without a basis and permission where required. Text messages may be retained to deliver the conversation and manage security and reports; they should not be considered anonymous or absolutely confidential. Internal access must be limited to authorized people on a need-to-know basis.
The community's ephemeral voice feature is not intended to retain recordings, transcripts, content analysis or audio conversation history. This differs from an expressly announced event or broadcast: an official recording requires specific information and permissions. External platforms, including Discord, apply their own policies. Participants are not authorized to record or distribute private conversations without permission.
5. Recipients and integrations
Hosting and technical operation rely on Hostinger and WordPress components. Enabled features may communicate necessary data to Discord and authentication providers, creator platforms or payment gateways identified in the corresponding flow. Authorized staff access data only as needed for support, security, administration or compliance; authorities may receive information where there is a legal basis.
An external integration requires the action and permissions shown on its screen. Only necessary permissions should be granted, and they can be revoked through the provider and available settings. Being named in this policy does not promise that an integration is active. Each provider's role as a technical service provider or controller of its own services must be distinguished.
6. International transfers
Some providers and platforms operate outside Argentina. Before international processing is enabled, the destination, service and safeguards must be identified under Argentine regulations, including adequacy or contractual instruments where applicable. This policy does not replace those checks or constitute blanket consent to any country or use. You can ask about the destination and basis applicable to a specific integration through the stated channels.
7. Retention
There is no single retention period for all data. Account and service information is retained as needed for the relationship; orders and receipts for applicable statutory periods; reports and sanctions only as needed for security, review or justified defense. Rights requests are retained with restricted access for handling and evidence of compliance and must be reviewed upon closure and periodically to delete or anonymize anything no longer necessary.
The identity system has audit log rotation configured at 90 days and cleanup of expired codes or renewals at 7 days; these periods apply to those specific records, not the entire account. Backups do not mean indefinite storage: they must follow their retention cycle and restoration controls. Deletion must cover the relevant systems, with justified exceptions and without promising instant deletion from backups or third-party services.
8. Rights and verification
You can request access, correction, updating or deletion and ask questions about your data through Legal requests or the support email without signing in. Under Argentine Law 25,326, access requests are answered within ten calendar days and correction, updating or deletion within five business days, subject to legal requirements. Free access can be exercised at the intervals provided by law or earlier if a legitimate interest is established.
Only proportionate verification will be required to avoid disclosing or altering another person's data. Passwords or excessive documentation will not be required. Deletion may affect access and history but does not mean waiving claims; if certain data must be retained, its basis and scope will be explained and its use restricted. Marketing acceptance or new terms are not required to exercise rights.
Argentina's Agency for Access to Public Information (AAIP) is the supervisory authority for Law 25,326 and receives complaints about failures to comply with data protection requirements. Information and channels: AAIP — Personal data.
9. Minors, security and changes
We apply the Code's age rules and enhanced safeguards. Legal representatives may inquire about minors' data with appropriate verification. Do not submit intimate images or sexual material involving minors through a form: provide the location or reference without redistributing it.
We limit access by role and respond to incidents; no system can guarantee absolute security. Report suspicions through support without publishing credentials or exploiting vulnerabilities. Material changes to processing will be disclosed and will require additional consent where applicable.
