App-user terms · Final legal review recommended

IOLResearch App terms of use

These terms govern authorized use of IOLResearch as a protocol-driven research application. They also explain the user’s responsibility for locally stored research data, backups, exports, and research governance.

Last updated: 9 September 2026

1. Provider and acceptance

These terms are an agreement between the person or organization using IOLResearch (the “User”) and INDALOFTAL S.L. (the “Developer”), Camino de Bobar, 1, 04007 Almería, Spain, Tax ID B04570446.

By downloading, accessing, or using IOLResearch, the User agrees to these terms and the IOLResearch Privacy Policy. A person using the App for an institution confirms that they are authorized to act within that institution’s policies. If the User does not agree, they must not use the App.

Distribution and payment through Apple are also subject to the applicable App Store and Apple Media Services terms. Unless the Developer publishes a custom end-user licence through App Store Connect, Apple’s Standard End User License Agreement also applies to the App.

2. Licence

The Developer grants the User a limited, revocable, non-exclusive, non-transferable licence to use IOLResearch on Apple-branded devices the User owns or controls, subject to these terms, the applicable Apple usage rules, and the access level assigned to the account.

IOLResearch is licensed, not sold. The Developer and its licensors retain all rights in the App, its design, code, documentation, trademarks, and supplied content. Except where applicable law expressly permits it, the User may not copy, redistribute, sublicense, rent, reverse engineer, decompile, circumvent access controls, create derivative versions, or use the App to infringe another person’s rights.

3. Research purpose and clinical limitations

IOLResearch is designed to organize protocol-based research observations and support visual-performance measurement and analysis. It is not intended to diagnose, prevent, monitor, predict, prognose, treat, or alleviate disease, and it does not select or recommend an intraocular lens or other treatment for an individual patient.

The App and its plots do not replace professional judgment, validated clinical instruments, protocol-specific calibration, independent statistical review, ethics oversight, or applicable regulatory requirements. The User must verify that the App, device, test setup, procedures, and outputs are appropriate and sufficiently validated for each study before relying on them.

4. Research-data and participant responsibilities

The App is designed to store research databases locally under the User’s control. The Developer does not receive those databases or act as their storage provider. The User or their institution determines why participant data are processed, which data are entered, who may access them, how long they are retained, and how the results are used.

The User and their institution are responsible for:

• obtaining any required lawful basis, participant information, consent, institutional authorization, and ethics or regulatory approval;
• collecting only data necessary for the approved research purpose and using non-identifying study codes wherever possible;
• treating pseudonymized information as personal data whenever re-identification remains possible;
• keeping any identity or re-identification key outside the App database, outside the same device, and outside any cloud account used to back up that database;
• controlling device, database, and export access; responding to participant rights; managing retention and deletion; and documenting any incident as required by law;
• checking the accuracy, completeness, interpretation, and statistical suitability of all data and outputs before research use, publication, or communication.

The User must not enter direct identifiers where the protocol does not require them, use the App for unlawful surveillance or discrimination, or attempt to use research outputs as an automated clinical decision for an individual.

5. Device security, backups, iCloud, and exports

The User is responsible for keeping the iPad, operating system, App, passcode, credentials, and local databases secure and current. Jailbreaking, disabling security controls, or using unsupported software may expose data or prevent the App from functioning correctly.

The Developer does not provide or control a cloud backup service for research databases. If the User enables device backup or iCloud, copies a database to external storage, sends an export by email, or uses another sharing service, that action creates a separate copy governed by the selected provider and the User’s institutional rules.

The User or their institution is solely responsible for approving each backup or export destination, configuring appropriate security and retention, limiting recipients, meeting cross-border transfer requirements, verifying successful recovery where backups are required, and deleting every copy when retention ends. The Developer cannot access, restore, supervise, or delete research files held on the User’s device or by a service the User selects.

6. Accounts and access roles

Sponsor and Key Evidence Leader access may require an invitation and account. The User must provide accurate account information, keep credentials confidential, use only their own account, and notify the Developer promptly of suspected unauthorized access. Sponsor functions, where enabled, must be used only to manage authorized KEL invitations and access assignments.

The Developer may suspend or limit an account where reasonably necessary to protect users or the service, investigate misuse, comply with law, respond to an organization’s authorized instruction, or enforce these terms. Account administration uses Supabase as described in the Privacy Policy; research databases are not stored in Supabase.

7. Plans, purchases, and renewals

Available features may depend on the Free, Lite, Pro, or Elite access level. Actual availability, price, billing period, trial conditions, and renewal terms are those shown to the User before purchase in the App Store or another authorized order process. Nothing on the preview website constitutes an offer to sell a plan.

If Apple processes a purchase, Apple manages payment, renewal, cancellation, and refund requests under its terms and the User’s App Store settings. The Developer does not receive full payment-card details from Apple. Mandatory consumer rights remain unaffected.

8. External services and connectivity

Account registration, sign-in, recovery, purchases, or user-selected sharing and backup features may require internet access and third-party services. The User is responsible for connectivity and provider charges. The Developer is responsible for selecting and configuring its own service providers with reasonable care, but does not control Apple, Supabase, an internet provider, or a storage or sharing service independently selected by the User.

9. Availability, updates, and changes to the App

The Developer aims to maintain the App but does not promise uninterrupted or error-free operation. Features may be corrected, improved, replaced, limited, or discontinued, and operating-system or device requirements may change. The User is responsible for assessing an update before using it in an active study and for maintaining a validated continuity and recovery plan appropriate to the research.

Planned changes do not remove rights already granted by mandatory law. Where practicable, material changes affecting an active service or paid access will be communicated through the App, website, account email, or App Store information.

10. Warranty and liability

To the maximum extent permitted by applicable law, the App is provided “as available” for the research functions described in its documentation. The Developer does not warrant that every procedure, output, or device configuration is suitable for a particular protocol, regulatory submission, publication, or clinical environment.

The Developer is not responsible for loss, disclosure, corruption, or unavailability caused by the User’s data-entry choices, failure to maintain an appropriate backup, sharing with an unintended recipient, an external service selected by the User, unsupported device modification, or use outside these terms.

Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited, including applicable consumer rights and liability arising from fraud, wilful misconduct, or other mandatory grounds. Any other limitation must be interpreted in accordance with the law applicable to the User.

11. Term and termination

The User may stop using the App at any time and may cancel a paid subscription through the service that manages the purchase. The Developer may terminate or suspend the licence for a material breach, unlawful use, security risk, or expiry of the relevant access right, subject to applicable law.

When the licence ends, the User must stop using the App where required. Ending an account does not automatically delete databases stored locally, in iCloud, in another backup, or in an export. The User remains responsible for retaining or deleting those copies according to applicable requirements.

12. Changes to these terms

The Developer may update these terms to reflect changes in the App, providers, or law. The revised terms will show a new date. Material changes will be communicated through an appropriate channel before taking effect when required. Continued use after the effective date constitutes acceptance only to the extent permitted by applicable law.

13. Governing law and disputes

These terms are governed by Spanish law, without depriving consumers of mandatory protections available under the law of their habitual residence. The parties should first try to resolve a dispute by contacting the Developer. Courts and venue are determined by applicable mandatory procedural and consumer law; these terms do not require a consumer to waive a forum that cannot lawfully be waived.

14. Contact

Questions about these terms may be sent to academy@qvision.es.

15. Language

The English and Spanish versions are intended to have the same meaning. If a discrepancy remains, the Spanish version prevails to the extent permitted by applicable law.