Privacy Policy

This Privacy Policy explains how LIORA may collect, use, disclose and protect personal information when you visit its website, contact LIORA, or use account and payment features that are made available. It distinguishes current website and API behavior from features or service arrangements that still require confirmation.

This policy does not mean that registration is currently open. Creating an account remains subject to LIORA publishing all required legal documents and to the live availability checks shown on the website.

The person or legal entity responsible for personal information (the data controller, where that concept applies) has not been verified for this publication. Before treating this policy as final, LIORA must replace this configurable item: [CONFIRM AND INSERT THE FULL LEGAL NAME OF THE DATA CONTROLLER, REGISTRATION DETAILS IF APPLICABLE, AND BUSINESS ADDRESS]. Do not infer a company name, registration, licence or regulatory status from the LIORA brand.

LIORA has not confirmed a dedicated privacy email address or appointed privacy contact for this policy. Before relying on the policy as final, replace this configurable item: [CONFIRM AND INSERT A MONITORED PRIVACY EMAIL ADDRESS OR OTHER APPROVED PRIVACY REQUEST CHANNEL]. General contact options are listed on the LIORA contact page, but they are not represented here as a verified privacy-response process.

The effective and last-updated dates appear above. LIORA has not specified the privacy-request handling process, identity-check process or response-time requirements in this policy. Do not send passwords, authentication codes or full payment-card details when making a request.

Visit LIORA’s contact page for currently listed general contact options.

The current registration flow asks for your full name, username, email address, international phone number, country and password. The account service also stores account status, registration amount and currency, payment status, welcome-bonus amount and credit status, and the times at which the account was created or activated.

If you submit the website contact form, it asks for your name, email address, subject and message. If registration and checkout are available, the payment flow may create a transaction reference and record a provider transaction ID, amount, currency, status and timestamps. A password is stored as a salted scrypt hash, not as readable password text. Session and password-reset tokens are stored as hashes.

The site and its infrastructure may process technical information needed to deliver requests and limit abuse. The exact access-log fields, logging providers and retention periods have not been confirmed.

Information may come directly from you when you fill in a form, sign in, request a password reset, or contact LIORA. If registration and payment are available, LIORA’s server also receives payment-status and transaction information from the payment provider to verify a transaction. The current code includes a Flutterwave checkout and verification integration; whether it is enabled for a particular transaction depends on the live configuration.

Some technical information may be generated when your browser or device communicates with the website. Any additional sources, such as identity-verification services or data obtained from partners, must be confirmed before LIORA relies on them.

Depending on which features are enabled, LIORA may use information to:

• create and maintain accounts, authenticate members and provide account recovery;
• check registration availability, process checkout and verify payment status;
• record registration details, payment references and any configured welcome-bonus status;
• answer contact requests and provide service-related communications;
• protect the website, limit abusive requests, troubleshoot errors and meet legal obligations;
• operate, evaluate or improve a feature only where that feature and its data use have been explained to you.

The legal ground for each processing purpose depends on the laws that apply to you and on LIORA’s confirmed legal identity and operations. Depending on the circumstances, a ground could include steps you request before an agreement, performance of an agreement, a legal obligation, consent, or a legitimate interest that does not override your rights. LIORA must confirm and document the applicable legal ground for each activity and jurisdiction; this policy does not assert that one ground applies to every use.

The registration endpoint validates and saves the account details listed above and records timestamps showing acceptance of the Terms & Conditions and Privacy Policy. Those records currently store acceptance times; a specific accepted-document version is not recorded in the account schema identified for this policy.

The server checks whether an email address or username is already in use. It applies rate limits to registration attempts. Account creation is blocked by a server-side legal-document publication setting until the required documents are published. The presence of a registration form should not be read as confirmation that registration is open.

Passwords are processed to verify your sign-in and are stored using a salted scrypt hash. LIORA’s code does not store the password in plaintext. Session cookies are marked HttpOnly and SameSite=Lax; the Secure setting is enabled in production. Session tokens are stored in hashed form, and the code gives ordinary sessions a 12-hour lifetime and remembered sessions a 30-day lifetime.

Password-reset tokens are also stored as hashes and are designed to expire after 60 minutes. Password-reset email delivery uses Resend only if the relevant service configuration is present. These technical controls do not guarantee that every security risk can be eliminated.

Where registration payment is enabled, LIORA creates a checkout request with a payment reference and the configured amount and currency. The integration sends registration-related details, including the account name, email address and phone number, to Flutterwave for checkout and verification. The payment provider may collect payment credentials directly from you under its own privacy notice.

The LIORA application code reviewed for this policy does not collect or store full card numbers or security codes. The exact payment methods shown and the data processed by the provider can vary by checkout configuration, country and provider terms. Confirm the provider’s current data handling and payment flow before relying on this description.

The API checks payment information with the payment provider before marking a registration payment successful and activating an account. It records a transaction reference, provider transaction ID when available, amount, currency, payment status, checkout URL and relevant timestamps. A browser redirect or receipt by itself does not activate an account.

If you contact LIORA about a payment, information you choose to provide may be used to locate and review the transaction. Do not send your password, one-time verification codes or full card details in a support message. Any additional payment-review intake or tracking feature is not confirmed by the current code.

The registration flow may display a welcome-bonus amount. The account record includes the configured amount and a credit status, and the API can record a bonus credit and confirmation state. A displayed amount is not proof that a credit has been issued. Eligibility, conditions, timing and any further data uses must be confirmed in the applicable published terms before a bonus is offered.

LIORA describes opportunities, AI training and data contribution, and community features as areas of its ecosystem. The current code reviewed for this policy does not establish which such activities are live, what information an activity might collect, or which external recipient could receive contributed material. If an activity becomes available, LIORA should provide a specific notice describing its data, purpose, recipients, retention and choices before asking you to participate.

The account system uses a first-party session cookie named liora_session to keep a signed-in session. It is HttpOnly and SameSite=Lax, and is marked Secure in production. The code also includes a sidebar preference cookie in a user-interface component. Their use depends on which part of the site you access.

A cookie-consent banner, consent-management tool, complete cookie inventory and cookie-specific retention schedule have not been confirmed. LIORA should confirm whether any other cookies or similar technologies are enabled and provide any notices or choices required by applicable law.

No analytics, behavioral-advertising or cross-site tracking provider has been confirmed in the code reviewed for this policy. LIORA does not make a claim here that such tools are or are not active in every hosting or deployment configuration. Confirm the production configuration and update this section before enabling analytics, advertising pixels or similar tracking.

Information may be shared where needed to operate a feature you request, for example with a payment provider during checkout or with an email-delivery provider for a configured password-reset message. It may also be disclosed when required by law or necessary to protect the service, its users or another person, subject to applicable law.

The complete recipient list, roles of each recipient, processing locations and any other sharing arrangements have not been verified. LIORA must confirm them before making a complete final disclosure. This policy does not claim that personal information is sold, used for targeted advertising, or shared with an AI provider.

The code contains integrations for Flutterwave checkout/payment verification and, when configured, Resend password-reset email delivery. The site also links to third-party social and messaging services. A code integration or link is not proof that a provider is active for every user or that LIORA has a particular partnership.

The full list of hosting, database, security, support, payment and communications providers, their contractual roles, and their privacy terms must be confirmed. When you follow an external link, the third party’s own privacy notice and practices apply to its service.

The application uses password hashing, hashed session and password-reset tokens, HttpOnly session cookies, request-origin checks for browser mutations, payment verification and rate limits on selected endpoints. These are specific controls visible in the current code; they are not a certification or a guarantee that a system is immune from unauthorized access, loss or misuse.

LIORA should confirm its operational security practices, access controls, incident response process and any additional safeguards before making broader security claims.

The account and payment records include creation, expiration, activation or verification timestamps, but the code reviewed does not establish a complete retention or deletion schedule for account records, contact submissions, payment attempts, logs or backups. LIORA must determine and publish the applicable periods and deletion process, including any legal, accounting, dispute or security reasons for keeping information longer.

Session and password-reset records have expiration data, but the cleanup schedule for expired records has not been confirmed. Do not treat the presence of an expiry timestamp as proof that a record is automatically deleted on that date.

The countries where LIORA’s hosting, database, support, payment and communications providers store or access information have not been confirmed. If information is transferred across borders, LIORA must identify the relevant destinations and safeguards and explain them as required by applicable law. This policy does not claim a particular server location.

Depending on the law that applies, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to object to or restrict certain processing; to withdraw consent where processing relies on consent; or to complain to a relevant authority. These rights may have limits and are not identical in every country.

To make a request, use the privacy contact details in section 2. LIORA must confirm the identity-check process, response times, applicable exceptions and any available appeal or complaint route before describing them as guaranteed procedures.

If account or payment features are available, LIORA may need to communicate about account access, password recovery, registration, payment verification or support. The code supports password-reset email only when the email provider is configured. A marketing email or messaging programme, its consent basis and an unsubscribe process have not been confirmed.

LIORA should provide a clear choice and required unsubscribe method before sending promotional communications. Messages sent through a third-party channel are also subject to that provider’s terms and privacy practices.

LIORA’s published Terms describe membership eligibility as 18 or older. The registration form itself does not establish an age-verification method. LIORA does not intend this service to be used by children under 18, and anyone who believes a child has provided information should contact LIORA using the details in section 2 so the request can be reviewed.

The process for verifying age and handling a child-data request must be confirmed before LIORA makes more specific claims about deletion or statutory timelines.

The website may link to payment, social, video, messaging or other external services. LIORA does not control those third-party websites or their privacy practices. Review the relevant third party’s privacy notice before submitting information there. The appearance of a link does not establish that LIORA endorses or has a partnership with that service.

LIORA may update this policy when its practices or legal requirements change. The effective and last-updated dates shown above identify the current version. If a change materially affects how information is handled, LIORA should provide any notice required by law and explain whether renewed consent is needed.

The current version will be made available on this page. A version-history or individual notification process has not been confirmed.