Digital Contract
Clause 1 — Nature, purpose and scope
This instrument establishes the general framework for the electronic relationship between NEVORA ECOSYSTEM SL and the people who access the features of its ecosystem. Its purpose is to set out the rules of access, the options available and the mechanisms that record the decisions made through the platform.
1.1. Purpose of the framework contract
Regarding the purpose of the framework contract, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
1.2. Scope of the digital relationship
The management of the scope of the digital relationship will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
1.3. Coordination with the particular conditions
As regards the coordination with the particular conditions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The main purpose is to avoid needlessly duplicating lengthy contracts when one person uses several features. The general text stays stable as a reference and the particular facts remain linked to identifiable records.
1.4. Interpretation of linked documents
In matters involving the interpretation of linked documents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
1.5. Accessibility and later consultation
Questions concerning the accessibility and later consultation may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
1.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the purpose of the framework contract must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 2 — Identification of the entity
Identifying the responsible entity makes it possible to tell institutional services apart from content or communications outside the official channels. The corporate and contact information must stay consistent with the registry data and with the communications offered to the user.
2.1. Legal name and public data
Regarding the legal name and public data, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
2.2. Identification in the digital environment
The management of the identification in the digital environment will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
2.3. Institutional communication channels
As regards the institutional communication channels, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The corporate details provided for this draft are NEVORA ECOSYSTEM SL, Tax ID (NIF) B05751904, Madrid, Spain, and www.nevoratech.io. The complete registered address and a valid address for notices must be verified before being published.
2.4. Updates to corporate information
In matters involving the updates to corporate information, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
2.5. Verification before publication
Questions concerning the verification before publication may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
2.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the legal name and public data must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 3 — Contractual terminology
So the clauses can be read together, the defined terms keep the same meaning on the contracting screens, in the operational records and in the institutional communications. Where a feature carries an additional definition, it must be shown in the corresponding context.
3.1. Account, holder and credentials
Regarding the account, holder and credentials, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
3.2. Activation and option
The management of the activation and option will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
3.3. Results and sharing
As regards the results and sharing, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
"User" identifies the account holder; "activation" designates one confirmed individual decision; "option" refers to the chosen term; "result" refers to amounts recorded under the operating rules of the product.
3.4. Platform and features
In matters involving the platform and features, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
3.5. Documents, versions and records
Questions concerning the documents, versions and records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
3.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the account, holder and credentials must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 4 — Scope and document structure
The contract applies to the general use of the NEVORA environment, without replacing the particular conditions presented for a specific product or activation. The documents are to be interpreted together and in a manner compatible with whichever mandatory rules apply.
4.1. Services covered by the framework
Regarding the services covered by the framework, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
4.2. Functions subject to their own conditions
The management of the functions subject to their own conditions will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
4.3. Hierarchy of contractual texts
As regards the hierarchy of contractual texts, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Informational materials, operating screens and specialized policies serve different functions. The applicable documentation must identify when a condition is merely descriptive and when it forms part of a contractual acceptance.
4.4. Territory and functional availability
In matters involving the territory and functional availability, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
4.5. Consistency of the information shown
Questions concerning the consistency of the information shown may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
4.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the services covered by the framework must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 5 — Registration and account ownership
The account is the personal space from which the holder consults information, manages their decisions and reaches the services enabled. Opening one requires providing adequate data and accepting the corresponding general conditions.
5.1. Opening and verifying the account
Regarding the opening and verifying the account, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
5.2. Accuracy and updating of data
The management of the accuracy and updating of data will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
5.3. Personal nature of access
As regards the personal nature of access, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Opening an account does not in itself involve making deposits or activating an option. The user keeps the possibility of reviewing the features and later choosing whichever options are enabled.
5.4. Tools available after opening
In matters involving the tools available after opening, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
5.5. Handling of registration issues
Questions concerning the handling of registration issues may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
5.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the opening and verifying the account must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 6 — Acceptance and electronic evidence
Electronic acceptance makes it possible to document knowledge of, and agreement with, an identifiable version of the contract. The recording procedure must give access to the full text before confirmation and keep sufficient technical evidence of the act performed.
6.1. Affirmative act of acceptance
Regarding the affirmative act of acceptance, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
6.2. Version accepted and date of the act
The management of the version accepted and date of the act will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
6.3. Prior access to the full text
As regards the prior access to the full text, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The acceptance record may include a version identifier, the date and time, an account identifier and technical evidence supplied by the system. Acceptance of the contract must be kept distinct from any privacy consent that legally requires a separate act.
6.4. Separation of specific consents
In matters involving the separation of specific consents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
6.5. Retention and consultation of evidence
Questions concerning the retention and consultation of evidence may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
6.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the affirmative act of acceptance must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 7 — Framework contract and individual activations
A single framework contract may govern successive activations made by one user. Each activation nevertheless keeps its own operational identification, with the specific conditions that were presented and confirmed at that time.
7.1. Unity of the general document
Regarding the unity of the general document, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
7.2. Separate record of each activation
The management of the separate record of each activation will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
7.3. Coexistence of amounts and terms
As regards the coexistence of amounts and terms, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
For example, one account could hold a three-month activation and a twelve-month one with different amounts. Both are linked to the same framework contract, but each keeps its own dates, amounts and percentages.
7.4. Consultation of historical conditions
In matters involving the consultation of historical conditions, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
7.5. Effects of later changes
Questions concerning the effects of later changes may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
7.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the unity of the general document must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 8 — Technological description of NEVORA TECH
NEVORA TECH is described as an automation solution directed at identifying price differences for crypto assets across markets and at managing arbitrage operations according to technological and operational criteria. The contractual description refers to the functioning announced and must match the actual implementation.
8.1. Function of the arbitrage software
Regarding the function of the arbitrage software, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
8.2. Observation of prices and markets
The management of the observation of prices and markets will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
8.3. Technical criteria for execution
As regards the technical criteria for execution, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Price arbitrage consists of analyzing observable differences for an asset across trading platforms. The existence of an automated tool does not change the need to describe the calculation rules correctly and how results are recorded.
8.4. Development and improvement of the system
In matters involving the development and improvement of the system, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
8.5. Communication of actual characteristics
Questions concerning the communication of actual characteristics may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
8.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the function of the arbitrage software must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 9 — Options, duration and time counting
NEVORA TECH's options are organized into periods of three, six and twelve months. The choice belongs to the user, who must be able to consult the duration and the reference date of each activation before confirming their request.
9.1. Three-month option
Regarding the three-month option, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
9.2. Six-month option
The management of the six-month option will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
9.3. Twelve-month option
As regards the twelve-month option, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
As a presentational reference, three, six and twelve months may correspond to conventional periods of ninety, one hundred and eighty, and three hundred and sixty days, where that equivalence is expressly communicated at the time of contracting.
9.4. Start date and maturity date
In matters involving the start date and maturity date, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
9.5. Information shown before confirming
Questions concerning the information shown before confirming may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
9.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the three-month option must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 10 — Criteria for sharing in results
The options described carry percentages of participation in the operating results: sixty per cent for three months, seventy per cent for six months and eighty per cent for twelve months. Those percentages express rules for splitting results actually determined in accordance with the service.
10.1. Split applying to three months
Regarding the split applying to three months, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
10.2. Split applying to six months
The management of the split applying to six months will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
10.3. Split applying to twelve months
As regards the split applying to twelve months, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The split indicated for each option is, respectively, 60% to the user and 40% to NEVORA; 70% and 30%; and 80% and 20%. The basis of the split and the items deducted must be understandable before accepting the activation.
10.4. Basis of calculation and distinct items
In matters involving the basis of calculation and distinct items, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
10.5. Understandable presentation of percentages
Questions concerning the understandable presentation of percentages may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
10.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the split applying to three months must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 11 — Calculation, recording and availability
The platform must distinguish between operating results, allocated amounts, available transactions and entries awaiting processing. Presenting these in an orderly way makes the progress of each activation easier to follow.
11.1. Identification of the operating result
Regarding the identification of the operating result, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
11.2. Procedure for recording
The management of the procedure for recording will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
11.3. Information on account transactions
As regards the information on account transactions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
A figure shown by the simulator is not in itself an accounting entry in the account. An illustrative projection must be distinguished from the result actually recorded through the mechanisms of the service.
11.4. Availability under the service rules
In matters involving the availability under the service rules, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
11.5. Review of discrepancies in records
Questions concerning the review of discrepancies in records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
11.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the identification of the operating result must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 12 — Amounts and multiple activations
Activations may carry different amounts and dates, even when they belong to the same account. The framework contract does not fix a single amount for the whole relationship; it refers instead to the individual information of each confirmed decision.
12.1. Minimum amount and entry conditions
Regarding the minimum amount and entry conditions, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
12.2. Possibility of multiple activations
The management of the possibility of multiple activations will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
12.3. Autonomy of each option
As regards the autonomy of each option, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The minimum amount communicated in the reference materials is US$ 10 per activation, subject to confirmation in the interface. Holding several activations does not merge their terms or replace the history of each one.
12.4. Identification of individual amounts
In matters involving the identification of individual amounts, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
12.5. Consolidated view of the account
Questions concerning the consolidated view of the account may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
12.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the minimum amount and entry conditions must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 13 — Allocation and tracking of funds
The amounts linked to an activation are shown according to their operational state and the conditions of the chosen option. Digital tracking must make it possible to distinguish the sums belonging to each individual record.
13.1. Allocation tied to an activation
Regarding the allocation tied to an activation, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
13.2. Operational state of each amount
The management of the operational state of each amount will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
13.3. Display of dates and conditions
As regards the display of dates and conditions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The capital allocated to an option and the sums available for other operations must appear separately. The end date and the conditions for returning capital are governed by the individual record and by the applicable rules.
13.4. Tracking of simultaneous contracts
In matters involving the tracking of simultaneous contracts, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
13.5. Information at the end of the period
Questions concerning the information at the end of the period may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
13.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the allocation tied to an activation must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 14 — Reinvestment and new decisions
Reinvestment means putting available sums into a new activation, where the feature is enabled and its conditions are met. It does not automatically change the dates or the conditions of earlier activations.
14.1. Voluntary nature of reinvestment
Regarding the voluntary nature of reinvestment, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
14.2. Minimum amount for a new activation
The management of the minimum amount for a new activation will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
14.3. Difference between reinvesting and withdrawing
As regards the difference between reinvesting and withdrawing, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Creating a new activation out of available sums requires an identifiable decision by the user. Each new option begins its own period and keeps its own participation parameters.
14.4. Recording of new options
In matters involving the recording of new options, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
14.5. Independent duration of each activation
Questions concerning the independent duration of each activation may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
14.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the voluntary nature of reinvestment must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 15 — Deposits and payment channels
The means of payment in may include bank transfers and certain digital assets, according to the options actually enabled on the platform. The specific payment instructions are presented in the corresponding interface.
15.1. Bank channels and digital assets
Regarding the bank channels and digital assets, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
15.2. Sending instructions and networks
The management of the sending instructions and networks will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
15.3. Identification of incoming operations
As regards the identification of incoming operations, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Earlier materials mention IBAN/SEPA, USDT, USDC and PIX as possible channels. Whether each is actually available, the currencies admitted and the compatible networks must be checked at the time of the operation.
15.4. Reconciliation and effect on the balance
In matters involving the reconciliation and effect on the balance, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
15.5. Information on enabled methods
Questions concerning the information on enabled methods may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
15.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the bank channels and digital assets must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 16 — Withdrawal requests
Withdrawal requests are made through the tools enabled and in accordance with the operational requirements communicated. The user must be able to identify the amount requested, the destination method and the processing state.
16.1. Submitting requests
Regarding the submitting requests, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
16.2. Minimum amount and stated fee
The management of the minimum amount and stated fee will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
16.3. Processing time communicated
As regards the processing time communicated, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The operational parameters provided indicate a minimum withdrawal of US$ 20, a 5% fee and a processing time of up to 72 hours. These figures must be verified before the final version is published and must be shown in the interface.
16.4. Destination details and verification
In matters involving the destination details and verification, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
16.5. Follow-up and support for requests
Questions concerning the follow-up and support for requests may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
16.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the submitting requests must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 17 — History, statements and traceability
The account history gathers the information needed to reconstruct the relevant actions taken by the user. Traceable records help in answering queries and in verifying the conditions of each operation.
17.1. Consultation of the personal history
Regarding the consultation of the personal history, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
17.2. Minimum data for each transaction
The management of the minimum data for each transaction will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
17.3. Documentation of acceptances
As regards the documentation of acceptances, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Relevant records may include registrations, acceptances, activations, transactions, withdrawal requests and operational communications. Their retention must answer to legitimate purposes and legally appropriate periods.
17.4. Correction of inconsistencies
In matters involving the correction of inconsistencies, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
17.5. Retention of contractual information
Questions concerning the retention of contractual information may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
17.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the consultation of the personal history must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 18 — Secure access and protection of credentials
Protecting access combines authentication tools with guidance on the responsible use of personal credentials. The measures available will be adapted to the characteristics of the platform and to the services actually implemented.
18.1. Safekeeping of keys and passwords
Regarding the safekeeping of keys and passwords, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
18.2. Authentication mechanisms
The management of the authentication mechanisms will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
18.3. Protection of personal access
As regards the protection of personal access, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The recommended practices include keeping the password confidential and using the authentication functions available. The platform must never ask the user to disclose secret keys in support conversations.
18.4. Reporting of incidents
In matters involving the reporting of incidents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
18.5. Evolution of the technological measures
Questions concerning the evolution of the technological measures may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
18.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the safekeeping of keys and passwords must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 19 — Support, notifications and communications
The purpose of institutional communication is to offer guidance on using the platform, answer requests and provide relevant operational information. Users must have adequate means of identifying the official channels.
19.1. Official support channels
Regarding the official support channels, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
19.2. Relevant operational notices
The management of the relevant operational notices will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
19.3. Recording of requests
As regards the recording of requests, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Communications may concern changes to conditions, follow-up on requests, functional updates and notices relating to the account. The official means and addresses must be available for consultation.
19.4. Languages and clarity of communication
In matters involving the languages and clarity of communication, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
19.5. Handling of contractual queries
Questions concerning the handling of contractual queries may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
19.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the official support channels must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 20 — Privacy and information management
The processing of personal information is tied to the administration of accounts, the operation of the services and other legitimate purposes duly communicated. The Privacy Policy supplements this contract in the matters that belong to it.
20.1. Categories of personal data
Regarding the categories of personal data, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
20.2. Purposes tied to the service
The management of the purposes tied to the service will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
20.3. Relationship with the privacy policy
As regards the relationship with the privacy policy, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The specific privacy policy must describe categories of data, legal bases, recipients, retention periods and the ways to exercise rights, according to the processing the entity actually carries out.
20.4. Rights and requests of data subjects
In matters involving the rights and requests of data subjects, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
20.5. Organization of protective measures
Questions concerning the organization of protective measures may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
20.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the categories of personal data must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 21 — Powers and rights of the user
Users keep the powers recognized by the conditions accepted and by the applicable law. Contractual information must be available for consultation in a clear manner, without the digital format reducing legally established rights.
21.1. Access to contractual information
Regarding the access to contractual information, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
21.2. Consultation of operations and records
The management of the consultation of operations and records will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
21.3. Requests for rectification
As regards the requests for rectification, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The user may consult the conditions applying to their activations and ask for clarification of entries in their account. Mandatory rights of information and complaint are not conditioned on general waivers.
21.4. Communication with support
In matters involving the communication with support, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
21.5. Mandatory rights recognized by law
Questions concerning the mandatory rights recognized by law may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
21.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the access to contractual information must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 22 — The user's undertakings
Responsible use of the platform calls for truthful information, care of credentials and respect for the functional rules of the service. The user's cooperation makes it possible to process their requests properly and keep the records up to date.
22.1. Personal use of credentials
Regarding the personal use of credentials, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
22.2. Accuracy of instructions and data
The management of the accuracy of instructions and data will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
22.3. Respect for the features
As regards the respect for the features, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The holder must review the amount, the option, the destination details and the instructions before confirming each operation. Requests for correction must be submitted through the official channels wherever that is possible.
22.4. Cooperation with reasonable verifications
In matters involving the cooperation with reasonable verifications, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
22.5. Use of official channels
Questions concerning the use of official channels may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
22.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the personal use of credentials must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 23 — The entity's management obligations
The entity organizes the resources needed to offer the features described and to administer the electronic relationships established. Its specific obligations are determined by this contract, the particular conditions and the applicable rules.
23.1. Provision of the services described
Regarding the provision of the services described, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
23.2. Information on operating conditions
The management of the information on operating conditions will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
23.3. Administration of records
As regards the administration of records, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The entity must seek to present information on options, fees, terms and procedures consistently. The specific conditions must match what the user can verify when contracting.
23.4. Attention to incidents
In matters involving the attention to incidents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
23.5. Improvement of processes and tools
Questions concerning the improvement of processes and tools may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
23.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the provision of the services described must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 24 — Continuity, maintenance and evolution
Technological evolution may call for maintenance work, interface improvements or updates to the system's components. Organizing that work must aim at appropriate communication and at preserving the relevant contractual information.
24.1. Maintenance of the infrastructure
Regarding the maintenance of the infrastructure, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
24.2. Technical updates
The management of the technical updates will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
24.3. Communication of relevant changes
As regards the communication of relevant changes, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Updates may cover interface changes, performance improvements and infrastructure adjustments. Where a change materially affects the contractual conditions, it must be handled separately.
24.4. Organization of interruptions
In matters involving the organization of interruptions, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
24.5. Continuity of essential information
Questions concerning the continuity of essential information may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
24.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the maintenance of the infrastructure must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 25 — Complementary products and developments
The NEVORA ecosystem covers several lines of technological development. Mentioning a future project does not mean all of its functions are available at the time this document is accepted.
25.1. Distinction between current and future products
Regarding the distinction between current and future products, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
25.2. NEVORA TOKEN
The management of NEVORA TOKEN will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
25.3. NEVORA WALLET
As regards NEVORA WALLET, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
NEVORA TOKEN and NEVORA WALLET have been described as asset-integration and digital-wallet projects; NEVORA GAMES as a digital-experiences initiative. The availability of each product will be communicated separately.
25.4. NEVORA GAMES and other initiatives
In matters involving NEVORA GAMES and other initiatives, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
25.5. Particular conditions of new services
Questions concerning the particular conditions of new services may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
25.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the distinction between current and future products must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 26 — Partner program and rewards
The collaboration and rewards programs, where available, are governed by specific conditions and their own participation criteria. Joining such programs is distinct from activating NEVORA TECH options.
26.1. Optional nature of the program
Regarding the optional nature of the program, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
26.2. Rules for direct referrals
The management of the rules for direct referrals will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
26.3. Distribution levels communicated
As regards the distribution levels communicated, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The reference materials describe direct rewards by level of 10%, 5%, 3%, 2% and 1%, alongside possible recognition. Their application depends on specific rules and on the eligibility requirements communicated.
26.4. Residual rewards and recognition
In matters involving the residual rewards and recognition, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
26.5. Separation from NEVORA TECH activity
Questions concerning the separation from NEVORA TECH activity may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
26.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the optional nature of the program must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 27 — Document review and version control
Contract versions will be identified so the user can recognize the text applying to their acceptance. Changes will be communicated and handled according to their scope and to the corresponding legal requirements.
27.1. Identification of the version in force
Regarding the identification of the version in force, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
27.2. Communication of relevant changes
The management of the communication of relevant changes will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
27.3. Archive of earlier versions
As regards the archive of earlier versions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The version identifier makes it possible to reconstruct which text was accepted on a given date. Changes must not silently alter the conditions of activations already confirmed.
27.4. Fresh acceptance where appropriate
In matters involving the fresh acceptance where appropriate, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
27.5. Protection of conditions already accepted
Questions concerning the protection of conditions already accepted may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
27.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the identification of the version in force must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 28 — Term, withdrawal and account closure
The general relationship begins with a valid acceptance and may continue for as long as an account or outstanding contractual ties exist. Closing the account must be coordinated with the specific conditions and with the records that must be retained.
28.1. Effects beginning on acceptance
Regarding the effects beginning on acceptance, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
28.2. Continuation of activations in force
The management of the continuation of activations in force will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
28.3. Request to close the account
As regards the request to close the account, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Withdrawing from an account and closing a relationship do not mean the immediate disappearance of records that must be retained. Pending operations require handling in accordance with the specific conditions and the corresponding rules.
28.4. Settlement of outstanding obligations
In matters involving the settlement of outstanding obligations, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
28.5. Legal retention of records
Questions concerning the legal retention of records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
28.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the effects beginning on acceptance must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 29 — Applicable law and handling of disputes
The interpretation and performance of the contract follow the legal provisions corresponding to the specific relationship. User support is a first channel for clarification, without excluding the legal resolution mechanisms available.
29.1. Interpretation in accordance with law
Regarding the interpretation in accordance with law, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
29.2. Applicable consumer rights
The management of the applicable consumer rights will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
29.3. Initial resolution through support
As regards the initial resolution through support, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The reference to an entity incorporated in Spain does not remove the application of mandatory consumer-protection rules that may apply. Matters may be taken to the competent authorities or courts.
29.4. Competent legal channels
In matters involving the competent legal channels, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
29.5. Validity of the remaining provisions
Questions concerning the validity of the remaining provisions may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
29.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the interpretation in accordance with law must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 30 — Final provisions and institutional record
This document is the general reference text for registration and for consultation from the Legal Center. Applying it definitively requires completing the corporate details, confirming the features described and approving the version in force.
30.1. Integrity of the general document
Regarding the integrity of the general document, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
30.2. Consultation from registration and the legal center
The management of the consultation from registration and the legal center will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
30.3. Linking of electronic evidence
As regards the linking of electronic evidence, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The corporate identification at the foot of the document is not in itself a certified electronic signature. An institutional electronic signature must only be presented as such where an authentic, authorized and verifiable procedure exists.
30.4. Corporate identification at the close
In matters involving the corporate identification at the close, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
30.5. Review and approval before publication
Questions concerning the review and approval before publication may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
30.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the integrity of the general document must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
NEVORA ECOSYSTEM SL · NIF B05751904 · Madrid, Spain · www.nevoratech.io
Institutional identification. Not equivalent to a certified electronic signature.
Digital Contract
Clause 1 — Nature, purpose and scope
This instrument establishes the general framework for the electronic relationship between NEVORA ECOSYSTEM SL and the people who access the features of its ecosystem. Its purpose is to set out the rules of access, the options available and the mechanisms that record the decisions made through the platform.
1.1. Purpose of the framework contract
Regarding the purpose of the framework contract, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
1.2. Scope of the digital relationship
The management of the scope of the digital relationship will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
1.3. Coordination with the particular conditions
As regards the coordination with the particular conditions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The main purpose is to avoid needlessly duplicating lengthy contracts when one person uses several features. The general text stays stable as a reference and the particular facts remain linked to identifiable records.
1.4. Interpretation of linked documents
In matters involving the interpretation of linked documents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
1.5. Accessibility and later consultation
Questions concerning the accessibility and later consultation may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
1.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the purpose of the framework contract must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 2 — Identification of the entity
Identifying the responsible entity makes it possible to tell institutional services apart from content or communications outside the official channels. The corporate and contact information must stay consistent with the registry data and with the communications offered to the user.
2.1. Legal name and public data
Regarding the legal name and public data, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
2.2. Identification in the digital environment
The management of the identification in the digital environment will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
2.3. Institutional communication channels
As regards the institutional communication channels, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The corporate details provided for this draft are NEVORA ECOSYSTEM SL, Tax ID (NIF) B05751904, Madrid, Spain, and www.nevoratech.io. The complete registered address and a valid address for notices must be verified before being published.
2.4. Updates to corporate information
In matters involving the updates to corporate information, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
2.5. Verification before publication
Questions concerning the verification before publication may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
2.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the legal name and public data must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 3 — Contractual terminology
So the clauses can be read together, the defined terms keep the same meaning on the contracting screens, in the operational records and in the institutional communications. Where a feature carries an additional definition, it must be shown in the corresponding context.
3.1. Account, holder and credentials
Regarding the account, holder and credentials, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
3.2. Activation and option
The management of the activation and option will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
3.3. Results and sharing
As regards the results and sharing, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
"User" identifies the account holder; "activation" designates one confirmed individual decision; "option" refers to the chosen term; "result" refers to amounts recorded under the operating rules of the product.
3.4. Platform and features
In matters involving the platform and features, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
3.5. Documents, versions and records
Questions concerning the documents, versions and records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
3.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the account, holder and credentials must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 4 — Scope and document structure
The contract applies to the general use of the NEVORA environment, without replacing the particular conditions presented for a specific product or activation. The documents are to be interpreted together and in a manner compatible with whichever mandatory rules apply.
4.1. Services covered by the framework
Regarding the services covered by the framework, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
4.2. Functions subject to their own conditions
The management of the functions subject to their own conditions will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
4.3. Hierarchy of contractual texts
As regards the hierarchy of contractual texts, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Informational materials, operating screens and specialized policies serve different functions. The applicable documentation must identify when a condition is merely descriptive and when it forms part of a contractual acceptance.
4.4. Territory and functional availability
In matters involving the territory and functional availability, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
4.5. Consistency of the information shown
Questions concerning the consistency of the information shown may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
4.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the services covered by the framework must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 5 — Registration and account ownership
The account is the personal space from which the holder consults information, manages their decisions and reaches the services enabled. Opening one requires providing adequate data and accepting the corresponding general conditions.
5.1. Opening and verifying the account
Regarding the opening and verifying the account, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
5.2. Accuracy and updating of data
The management of the accuracy and updating of data will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
5.3. Personal nature of access
As regards the personal nature of access, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Opening an account does not in itself involve making deposits or activating an option. The user keeps the possibility of reviewing the features and later choosing whichever options are enabled.
5.4. Tools available after opening
In matters involving the tools available after opening, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
5.5. Handling of registration issues
Questions concerning the handling of registration issues may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
5.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the opening and verifying the account must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 6 — Acceptance and electronic evidence
Electronic acceptance makes it possible to document knowledge of, and agreement with, an identifiable version of the contract. The recording procedure must give access to the full text before confirmation and keep sufficient technical evidence of the act performed.
6.1. Affirmative act of acceptance
Regarding the affirmative act of acceptance, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
6.2. Version accepted and date of the act
The management of the version accepted and date of the act will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
6.3. Prior access to the full text
As regards the prior access to the full text, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The acceptance record may include a version identifier, the date and time, an account identifier and technical evidence supplied by the system. Acceptance of the contract must be kept distinct from any privacy consent that legally requires a separate act.
6.4. Separation of specific consents
In matters involving the separation of specific consents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
6.5. Retention and consultation of evidence
Questions concerning the retention and consultation of evidence may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
6.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the affirmative act of acceptance must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 7 — Framework contract and individual activations
A single framework contract may govern successive activations made by one user. Each activation nevertheless keeps its own operational identification, with the specific conditions that were presented and confirmed at that time.
7.1. Unity of the general document
Regarding the unity of the general document, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
7.2. Separate record of each activation
The management of the separate record of each activation will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
7.3. Coexistence of amounts and terms
As regards the coexistence of amounts and terms, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
For example, one account could hold a three-month activation and a twelve-month one with different amounts. Both are linked to the same framework contract, but each keeps its own dates, amounts and percentages.
7.4. Consultation of historical conditions
In matters involving the consultation of historical conditions, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
7.5. Effects of later changes
Questions concerning the effects of later changes may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
7.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the unity of the general document must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 8 — Technological description of NEVORA TECH
NEVORA TECH is described as an automation solution directed at identifying price differences for crypto assets across markets and at managing arbitrage operations according to technological and operational criteria. The contractual description refers to the functioning announced and must match the actual implementation.
8.1. Function of the arbitrage software
Regarding the function of the arbitrage software, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
8.2. Observation of prices and markets
The management of the observation of prices and markets will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
8.3. Technical criteria for execution
As regards the technical criteria for execution, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Price arbitrage consists of analyzing observable differences for an asset across trading platforms. The existence of an automated tool does not change the need to describe the calculation rules correctly and how results are recorded.
8.4. Development and improvement of the system
In matters involving the development and improvement of the system, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
8.5. Communication of actual characteristics
Questions concerning the communication of actual characteristics may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
8.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the function of the arbitrage software must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 9 — Options, duration and time counting
NEVORA TECH's options are organized into periods of three, six and twelve months. The choice belongs to the user, who must be able to consult the duration and the reference date of each activation before confirming their request.
9.1. Three-month option
Regarding the three-month option, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
9.2. Six-month option
The management of the six-month option will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
9.3. Twelve-month option
As regards the twelve-month option, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
As a presentational reference, three, six and twelve months may correspond to conventional periods of ninety, one hundred and eighty, and three hundred and sixty days, where that equivalence is expressly communicated at the time of contracting.
9.4. Start date and maturity date
In matters involving the start date and maturity date, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
9.5. Information shown before confirming
Questions concerning the information shown before confirming may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
9.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the three-month option must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 10 — Criteria for sharing in results
The options described carry percentages of participation in the operating results: sixty per cent for three months, seventy per cent for six months and eighty per cent for twelve months. Those percentages express rules for splitting results actually determined in accordance with the service.
10.1. Split applying to three months
Regarding the split applying to three months, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
10.2. Split applying to six months
The management of the split applying to six months will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
10.3. Split applying to twelve months
As regards the split applying to twelve months, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The split indicated for each option is, respectively, 60% to the user and 40% to NEVORA; 70% and 30%; and 80% and 20%. The basis of the split and the items deducted must be understandable before accepting the activation.
10.4. Basis of calculation and distinct items
In matters involving the basis of calculation and distinct items, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
10.5. Understandable presentation of percentages
Questions concerning the understandable presentation of percentages may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
10.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the split applying to three months must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 11 — Calculation, recording and availability
The platform must distinguish between operating results, allocated amounts, available transactions and entries awaiting processing. Presenting these in an orderly way makes the progress of each activation easier to follow.
11.1. Identification of the operating result
Regarding the identification of the operating result, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
11.2. Procedure for recording
The management of the procedure for recording will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
11.3. Information on account transactions
As regards the information on account transactions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
A figure shown by the simulator is not in itself an accounting entry in the account. An illustrative projection must be distinguished from the result actually recorded through the mechanisms of the service.
11.4. Availability under the service rules
In matters involving the availability under the service rules, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
11.5. Review of discrepancies in records
Questions concerning the review of discrepancies in records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
11.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the identification of the operating result must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 12 — Amounts and multiple activations
Activations may carry different amounts and dates, even when they belong to the same account. The framework contract does not fix a single amount for the whole relationship; it refers instead to the individual information of each confirmed decision.
12.1. Minimum amount and entry conditions
Regarding the minimum amount and entry conditions, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
12.2. Possibility of multiple activations
The management of the possibility of multiple activations will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
12.3. Autonomy of each option
As regards the autonomy of each option, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The minimum amount communicated in the reference materials is US$ 10 per activation, subject to confirmation in the interface. Holding several activations does not merge their terms or replace the history of each one.
12.4. Identification of individual amounts
In matters involving the identification of individual amounts, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
12.5. Consolidated view of the account
Questions concerning the consolidated view of the account may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
12.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the minimum amount and entry conditions must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 13 — Allocation and tracking of funds
The amounts linked to an activation are shown according to their operational state and the conditions of the chosen option. Digital tracking must make it possible to distinguish the sums belonging to each individual record.
13.1. Allocation tied to an activation
Regarding the allocation tied to an activation, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
13.2. Operational state of each amount
The management of the operational state of each amount will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
13.3. Display of dates and conditions
As regards the display of dates and conditions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The capital allocated to an option and the sums available for other operations must appear separately. The end date and the conditions for returning capital are governed by the individual record and by the applicable rules.
13.4. Tracking of simultaneous contracts
In matters involving the tracking of simultaneous contracts, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
13.5. Information at the end of the period
Questions concerning the information at the end of the period may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
13.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the allocation tied to an activation must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 14 — Reinvestment and new decisions
Reinvestment means putting available sums into a new activation, where the feature is enabled and its conditions are met. It does not automatically change the dates or the conditions of earlier activations.
14.1. Voluntary nature of reinvestment
Regarding the voluntary nature of reinvestment, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
14.2. Minimum amount for a new activation
The management of the minimum amount for a new activation will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
14.3. Difference between reinvesting and withdrawing
As regards the difference between reinvesting and withdrawing, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Creating a new activation out of available sums requires an identifiable decision by the user. Each new option begins its own period and keeps its own participation parameters.
14.4. Recording of new options
In matters involving the recording of new options, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
14.5. Independent duration of each activation
Questions concerning the independent duration of each activation may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
14.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the voluntary nature of reinvestment must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 15 — Deposits and payment channels
The means of payment in may include bank transfers and certain digital assets, according to the options actually enabled on the platform. The specific payment instructions are presented in the corresponding interface.
15.1. Bank channels and digital assets
Regarding the bank channels and digital assets, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
15.2. Sending instructions and networks
The management of the sending instructions and networks will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
15.3. Identification of incoming operations
As regards the identification of incoming operations, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Earlier materials mention IBAN/SEPA, USDT, USDC and PIX as possible channels. Whether each is actually available, the currencies admitted and the compatible networks must be checked at the time of the operation.
15.4. Reconciliation and effect on the balance
In matters involving the reconciliation and effect on the balance, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
15.5. Information on enabled methods
Questions concerning the information on enabled methods may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
15.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the bank channels and digital assets must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 16 — Withdrawal requests
Withdrawal requests are made through the tools enabled and in accordance with the operational requirements communicated. The user must be able to identify the amount requested, the destination method and the processing state.
16.1. Submitting requests
Regarding the submitting requests, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
16.2. Minimum amount and stated fee
The management of the minimum amount and stated fee will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
16.3. Processing time communicated
As regards the processing time communicated, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The operational parameters provided indicate a minimum withdrawal of US$ 20, a 5% fee and a processing time of up to 72 hours. These figures must be verified before the final version is published and must be shown in the interface.
16.4. Destination details and verification
In matters involving the destination details and verification, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
16.5. Follow-up and support for requests
Questions concerning the follow-up and support for requests may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
16.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the submitting requests must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 17 — History, statements and traceability
The account history gathers the information needed to reconstruct the relevant actions taken by the user. Traceable records help in answering queries and in verifying the conditions of each operation.
17.1. Consultation of the personal history
Regarding the consultation of the personal history, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
17.2. Minimum data for each transaction
The management of the minimum data for each transaction will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
17.3. Documentation of acceptances
As regards the documentation of acceptances, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Relevant records may include registrations, acceptances, activations, transactions, withdrawal requests and operational communications. Their retention must answer to legitimate purposes and legally appropriate periods.
17.4. Correction of inconsistencies
In matters involving the correction of inconsistencies, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
17.5. Retention of contractual information
Questions concerning the retention of contractual information may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
17.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the consultation of the personal history must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 18 — Secure access and protection of credentials
Protecting access combines authentication tools with guidance on the responsible use of personal credentials. The measures available will be adapted to the characteristics of the platform and to the services actually implemented.
18.1. Safekeeping of keys and passwords
Regarding the safekeeping of keys and passwords, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
18.2. Authentication mechanisms
The management of the authentication mechanisms will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
18.3. Protection of personal access
As regards the protection of personal access, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The recommended practices include keeping the password confidential and using the authentication functions available. The platform must never ask the user to disclose secret keys in support conversations.
18.4. Reporting of incidents
In matters involving the reporting of incidents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
18.5. Evolution of the technological measures
Questions concerning the evolution of the technological measures may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
18.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the safekeeping of keys and passwords must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 19 — Support, notifications and communications
The purpose of institutional communication is to offer guidance on using the platform, answer requests and provide relevant operational information. Users must have adequate means of identifying the official channels.
19.1. Official support channels
Regarding the official support channels, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
19.2. Relevant operational notices
The management of the relevant operational notices will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
19.3. Recording of requests
As regards the recording of requests, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Communications may concern changes to conditions, follow-up on requests, functional updates and notices relating to the account. The official means and addresses must be available for consultation.
19.4. Languages and clarity of communication
In matters involving the languages and clarity of communication, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
19.5. Handling of contractual queries
Questions concerning the handling of contractual queries may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
19.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the official support channels must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 20 — Privacy and information management
The processing of personal information is tied to the administration of accounts, the operation of the services and other legitimate purposes duly communicated. The Privacy Policy supplements this contract in the matters that belong to it.
20.1. Categories of personal data
Regarding the categories of personal data, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
20.2. Purposes tied to the service
The management of the purposes tied to the service will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
20.3. Relationship with the privacy policy
As regards the relationship with the privacy policy, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The specific privacy policy must describe categories of data, legal bases, recipients, retention periods and the ways to exercise rights, according to the processing the entity actually carries out.
20.4. Rights and requests of data subjects
In matters involving the rights and requests of data subjects, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
20.5. Organization of protective measures
Questions concerning the organization of protective measures may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
20.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the categories of personal data must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 21 — Powers and rights of the user
Users keep the powers recognized by the conditions accepted and by the applicable law. Contractual information must be available for consultation in a clear manner, without the digital format reducing legally established rights.
21.1. Access to contractual information
Regarding the access to contractual information, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
21.2. Consultation of operations and records
The management of the consultation of operations and records will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
21.3. Requests for rectification
As regards the requests for rectification, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The user may consult the conditions applying to their activations and ask for clarification of entries in their account. Mandatory rights of information and complaint are not conditioned on general waivers.
21.4. Communication with support
In matters involving the communication with support, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
21.5. Mandatory rights recognized by law
Questions concerning the mandatory rights recognized by law may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
21.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the access to contractual information must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 22 — The user's undertakings
Responsible use of the platform calls for truthful information, care of credentials and respect for the functional rules of the service. The user's cooperation makes it possible to process their requests properly and keep the records up to date.
22.1. Personal use of credentials
Regarding the personal use of credentials, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
22.2. Accuracy of instructions and data
The management of the accuracy of instructions and data will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
22.3. Respect for the features
As regards the respect for the features, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The holder must review the amount, the option, the destination details and the instructions before confirming each operation. Requests for correction must be submitted through the official channels wherever that is possible.
22.4. Cooperation with reasonable verifications
In matters involving the cooperation with reasonable verifications, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
22.5. Use of official channels
Questions concerning the use of official channels may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
22.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the personal use of credentials must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 23 — The entity's management obligations
The entity organizes the resources needed to offer the features described and to administer the electronic relationships established. Its specific obligations are determined by this contract, the particular conditions and the applicable rules.
23.1. Provision of the services described
Regarding the provision of the services described, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
23.2. Information on operating conditions
The management of the information on operating conditions will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
23.3. Administration of records
As regards the administration of records, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The entity must seek to present information on options, fees, terms and procedures consistently. The specific conditions must match what the user can verify when contracting.
23.4. Attention to incidents
In matters involving the attention to incidents, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
23.5. Improvement of processes and tools
Questions concerning the improvement of processes and tools may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
23.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the provision of the services described must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 24 — Continuity, maintenance and evolution
Technological evolution may call for maintenance work, interface improvements or updates to the system's components. Organizing that work must aim at appropriate communication and at preserving the relevant contractual information.
24.1. Maintenance of the infrastructure
Regarding the maintenance of the infrastructure, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
24.2. Technical updates
The management of the technical updates will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
24.3. Communication of relevant changes
As regards the communication of relevant changes, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Updates may cover interface changes, performance improvements and infrastructure adjustments. Where a change materially affects the contractual conditions, it must be handled separately.
24.4. Organization of interruptions
In matters involving the organization of interruptions, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
24.5. Continuity of essential information
Questions concerning the continuity of essential information may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
24.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the maintenance of the infrastructure must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 25 — Complementary products and developments
The NEVORA ecosystem covers several lines of technological development. Mentioning a future project does not mean all of its functions are available at the time this document is accepted.
25.1. Distinction between current and future products
Regarding the distinction between current and future products, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
25.2. NEVORA TOKEN
The management of NEVORA TOKEN will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
25.3. NEVORA WALLET
As regards NEVORA WALLET, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
NEVORA TOKEN and NEVORA WALLET have been described as asset-integration and digital-wallet projects; NEVORA GAMES as a digital-experiences initiative. The availability of each product will be communicated separately.
25.4. NEVORA GAMES and other initiatives
In matters involving NEVORA GAMES and other initiatives, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
25.5. Particular conditions of new services
Questions concerning the particular conditions of new services may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
25.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the distinction between current and future products must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 26 — Partner program and rewards
The collaboration and rewards programs, where available, are governed by specific conditions and their own participation criteria. Joining such programs is distinct from activating NEVORA TECH options.
26.1. Optional nature of the program
Regarding the optional nature of the program, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
26.2. Rules for direct referrals
The management of the rules for direct referrals will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
26.3. Distribution levels communicated
As regards the distribution levels communicated, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The reference materials describe direct rewards by level of 10%, 5%, 3%, 2% and 1%, alongside possible recognition. Their application depends on specific rules and on the eligibility requirements communicated.
26.4. Residual rewards and recognition
In matters involving the residual rewards and recognition, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
26.5. Separation from NEVORA TECH activity
Questions concerning the separation from NEVORA TECH activity may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
26.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the optional nature of the program must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 27 — Document review and version control
Contract versions will be identified so the user can recognize the text applying to their acceptance. Changes will be communicated and handled according to their scope and to the corresponding legal requirements.
27.1. Identification of the version in force
Regarding the identification of the version in force, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
27.2. Communication of relevant changes
The management of the communication of relevant changes will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
27.3. Archive of earlier versions
As regards the archive of earlier versions, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The version identifier makes it possible to reconstruct which text was accepted on a given date. Changes must not silently alter the conditions of activations already confirmed.
27.4. Fresh acceptance where appropriate
In matters involving the fresh acceptance where appropriate, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
27.5. Protection of conditions already accepted
Questions concerning the protection of conditions already accepted may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
27.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the identification of the version in force must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 28 — Term, withdrawal and account closure
The general relationship begins with a valid acceptance and may continue for as long as an account or outstanding contractual ties exist. Closing the account must be coordinated with the specific conditions and with the records that must be retained.
28.1. Effects beginning on acceptance
Regarding the effects beginning on acceptance, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
28.2. Continuation of activations in force
The management of the continuation of activations in force will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
28.3. Request to close the account
As regards the request to close the account, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
Withdrawing from an account and closing a relationship do not mean the immediate disappearance of records that must be retained. Pending operations require handling in accordance with the specific conditions and the corresponding rules.
28.4. Settlement of outstanding obligations
In matters involving the settlement of outstanding obligations, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
28.5. Legal retention of records
Questions concerning the legal retention of records may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
28.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the effects beginning on acceptance must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 29 — Applicable law and handling of disputes
The interpretation and performance of the contract follow the legal provisions corresponding to the specific relationship. User support is a first channel for clarification, without excluding the legal resolution mechanisms available.
29.1. Interpretation in accordance with law
Regarding the interpretation in accordance with law, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
29.2. Applicable consumer rights
The management of the applicable consumer rights will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
29.3. Initial resolution through support
As regards the initial resolution through support, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The reference to an entity incorporated in Spain does not remove the application of mandatory consumer-protection rules that may apply. Matters may be taken to the competent authorities or courts.
29.4. Competent legal channels
In matters involving the competent legal channels, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
29.5. Validity of the remaining provisions
Questions concerning the validity of the remaining provisions may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
29.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the interpretation in accordance with law must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
Clause 30 — Final provisions and institutional record
This document is the general reference text for registration and for consultation from the Legal Center. Applying it definitively requires completing the corporate details, confirming the features described and approving the version in force.
30.1. Integrity of the general document
Regarding the integrity of the general document, the relevant information will be presented in an identifiable manner within the corresponding digital environment. The user will be able to review the elements bearing on their decision before confirming an action with contractual effects. Where particular conditions exist, they will be associated with the specific record and interpreted together with this instrument.
30.2. Consultation from registration and the legal center
The management of the consultation from registration and the legal center will be organized through procedures appropriate to the nature of the service. For consultation and follow-up, the available data must make it possible to distinguish the decisions taken, the operational states and the related communications. The platform may use internal references or identifiers to maintain that distinction.
30.3. Linking of electronic evidence
As regards the linking of electronic evidence, any description offered on screens, in documents or in communications must be consistent with the features actually enabled. The presentation of general information does not replace the particular instructions needed to complete an operation or exercise a recognized right.
The corporate identification at the foot of the document is not in itself a certified electronic signature. An institutional electronic signature must only be presented as such where an authentic, authorized and verifiable procedure exists.
30.4. Corporate identification at the close
In matters involving the corporate identification at the close, the account must preserve the conceptual separation between the respective conditions of each activation or product. That organization makes it easier to follow terms, amounts, states and requests without turning every action into a new, complete framework contract.
30.5. Review and approval before publication
Questions concerning the review and approval before publication may be directed to the official support channels, providing whichever account or transaction reference is relevant. The review of a query will consider the available data, the contract version accepted and the conditions shown when the operation was carried out.
30.6. Application and record
The provisions of this clause will apply in coordination with the remaining stipulations of the General Digital Contract, the particular conditions of each activation and the procedures actually enabled. All essential information that must be confirmed individually will be presented before the corresponding action and may be linked to the account history for later consultation.
As a matter of document administration, the reference to the integrity of the general document must remain understandable and verifiable for the account holder. The entity will seek to ensure that the instructions, notices and records relating to this matter can be identified in the relevant area of the platform. Any operational clarification will supplement the general framework without replacing the specific information presented to the user at the moment of confirming a decision.
NEVORA ECOSYSTEM SL · NIF B05751904 · Madrid, Spain · www.nevoratech.io
Institutional identification. Not equivalent to a certified electronic signature.