Privacy Policy
What the website processes, why it is used and which providers are involved.
salesEnabled before those details are filled and verified.Controller
The data controller for processing carried out directly by the Notwen website is the website operator identified in the Legal Notice. The operator's full legal identity and contact email must be completed before live checkout is enabled.
Data processed by this website
- Language preference: stored locally in the browser.
- Tebex basket identifier: stored in session storage while a basket exists.
- CFX identity display data: username/identifier and, when available, avatar data used to show the linked account and validate the Tebex basket.
- Discord identity display data: identifier/name/avatar information returned through the account-linking flow and stored locally so the header can show the linked account.
- Contact form content: the current contact form prepares/copies a brief locally and does not submit it to Notwen.
This site currently does not include advertising pixels, behavioural advertising or third-party analytics scripts.
Purposes and legal bases
- Operate navigation, language and session features requested by the visitor.
- Prepare and manage a purchase flow requested by the user and connect it to Tebex/Cfx authentication.
- Protect the service, diagnose technical failures and prevent misuse where necessary for legitimate security and operational interests.
- Comply with legal obligations that apply to the operator.
Where a provider asks the user to authorize an external account, that authorization is handled on the provider's own authentication surface.
Recipients and service providers
Depending on the feature the user chooses, data may be sent to or received from:
- Tebex: basket, checkout, account authentication and payment/digital-goods commerce.
- Cfx / Rockstar services: FiveM/Cfx identity and asset-entitlement related functionality.
- Discord: Discord account identity assets and the community link.
- Hosting/CDN provider: Cloudflare Pages is the planned production host and may process standard network/security logs when the site is deployed there.
No public CORS proxy is used to resolve Cfx profiles. The website has been changed to query only official Cfx endpoints for that enrichment.
Payments
Payment is completed on Tebex Checkout. This static site does not collect or store payment card credentials. Tebex acts as the payment/commerce provider on its own checkout and applies its own privacy and buyer terms.
Retention
Browser-side identity/preferences remain until the user unlinks the account, clears site data or the relevant session storage expires. Notwen should keep any future support or legal records only for as long as needed for the stated purpose and applicable legal claims/obligations. Tebex, Cfx, Discord and the hosting provider keep data under their own retention policies.
International transfers
Some service providers may process information outside the visitor's country. Their own privacy notices describe the transfer mechanisms and safeguards they use. Notwen should verify the final provider/account configuration before live launch.
Your rights
Where the GDPR or equivalent law applies, users may have rights of access, rectification, erasure, restriction, objection and portability, and the right to complain to the competent supervisory authority. The operator must publish a working privacy contact before production so these requests can be exercised directly.
Política de privacidad — resumen
La web guarda localmente preferencias de idioma e información visual de las cuentas que el usuario decide vincular, y utiliza almacenamiento de sesión para la cesta de Tebex. El formulario de contacto actual no envía datos. No hay píxeles publicitarios ni analítica de terceros.
Según la función elegida pueden intervenir Tebex, Cfx/Rockstar, Discord y el proveedor de hosting/CDN. El titular deberá completar sus datos reales de contacto antes del lanzamiento comercial para poder atender los derechos de protección de datos.
Discord OAuth: Discord OAuth access tokens are not stored in browser storage. The server-side callback reads the basic identify profile and keeps only a signed first-party session cookie for the linked profile.