01
Aurevia Investment processes account information so the application can authenticate users, display portfolio activity, manage requests and provide administrative controls. Typical profile data can include name, email, mobile number, country, address, language, avatar and verification status. When KYC is enabled, users may upload supporting documents for administrator review. The application should collect only information needed for the configured workflow and should not request passwords, private wallet keys or unrelated sensitive information through support channels.
02
Transaction records are used to maintain an auditable history of deposits, withdrawals, investments, returns and administrative adjustments. Records can contain a reference number, type, amount, currency, payment method, fee, status, timestamps and limited metadata needed for reconciliation. Promotional rewards and referral task credits are also recorded separately so they can be distinguished from cash wallet funds and settled income. This separation supports accurate balance calculations when the site currency changes or when an administrator reviews account history.
03
The platform may store uploaded images and files such as avatars, plan media, payment logos, payout QR images, page images and KYC documents. Public branding and plan media can be served to visitors, while KYC material should be treated as restricted account information available only to authorized administrative workflows. Administrators are responsible for configuring server permissions, access controls, retention practices and backups that are appropriate for their deployment environment and applicable law.
04
Basic technical information may be processed by the hosting environment when a user accesses the site. This can include IP address, browser type, device characteristics, request time, page address and server logs needed for security and diagnostics. Third-party services such as payment providers, social platforms or messaging links may process additional information under their own privacy terms when a user leaves Aurevia or completes an external payment flow. The platform administrator should review those providers before enabling them.
05
Users should be able to correct their profile information through the available profile controls or by contacting support when a field is locked for verification. Administrators can update account status and KYC review information from the User Control Center. Financial history may need to be retained for audit, dispute resolution or legal obligations even when other profile information is changed. Deletion or retention requests therefore depend on the administrator’s legal responsibilities and the nature of the records involved.
06
Privacy is also an operational practice. Use strong passwords, protect administrator accounts, keep framework dependencies updated, review enabled gateways and avoid storing secrets in public page content. The application provides settings and system tools, but secure deployment remains a shared responsibility between the software operator, hosting provider and enabled external services. Users should contact the site operator for the policy that applies to the deployed service and should not assume that a demo or template configuration represents the final production policy.
