Privacy Policy

MolinaTec LLC is responsible for personal data collected directly by Riqzz to provide its personal finance application.

Riqzz is intended for people aged 18 or older. If we learn that an account belongs to someone under that age, we may suspend it while addressing the situation.

We may collect data provided by the user, such as name, email address, phone number, country of residence, identity document when they choose to provide it, preferences, support inquiries, and uploaded files or documents.

To provide financial features, we process information the user records about accounts, cards, balances, budgets, expenses, income, transfers, loans, subscriptions, goals, notes, reconciliations, and reports. The Financial Inbox processes only emails forwarded by the user and permitted attachments.

Using Riqzz may also generate technical data such as IP address, browser or device, session information, security events, features used, and aggregate usage and performance metrics.

Payment instruments are processed directly by an external provider. Riqzz does not store full card numbers.

We use data to provide and protect the service, organize user-entered financial information, generate reports, manage plans and payments, send transactional communications, provide support, prevent fraud or abuse, improve the product through aggregate analytics, and meet applicable obligations.

Depending on the purpose, processing relies on performance of the contract, compliance with legal obligations, consent for optional features, and legitimate interests in protecting and improving the service.

Riqzz does not sell personal data, use financial information for targeted advertising, perform credit scoring, or make automated decisions that produce legal effects for the user.

Riqzz may use automated controls to prevent fraud, abuse, or security risks. These controls do not independently make decisions that produce legal effects for the user.

Users who need information or review about a measure applied to their account may contact contact@riqzz.com.

The Financial Inbox is optional and requires explicit consent. Forwarded emails are used only to prepare expenses for review that the user decides to save or discard.

When the user chooses to connect an email integration, Riqzz uses limited authorization to configure the selected rules. Riqzz does not request access to read, send, or delete messages from the personal inbox.

Riqzz use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Rules created in the email provider remain there and may continue forwarding messages until the user pauses or deletes them there.

Personal data is shared only with providers needed to deliver, protect, or support the service and that appear in the Subprocessor List when applicable.

Providers must be subject to protection and confidentiality terms appropriate to the service they provide. Riqzz does not sell personal data.

Some providers may process information outside the user’s country. Where applicable, Riqzz uses available terms and safeguards to protect those transfers and limits data to what is needed for each purpose.

We keep data while the account or related feature remains active and for as long as necessary to provide the service, address requests, resolve disputes, or meet legal obligations.

When a purpose is no longer necessary, data is deleted or kept only for the applicable period.

Users may request access, correction, update, objection, or deletion by contacting contact@riqzz.com. We may request reasonable information to verify identity and protect the account.

Riqzz applies technical and organizational measures intended to protect the confidentiality, integrity, and availability of data. No system can guarantee absolute security.

For questions or requests related to data protection, contact contact@riqzz.com.

When a material change affects data processing, Riqzz may provide notice and request renewed acceptance where appropriate. The current version and effective date will remain visible on this page.