Terms and Conditions

Last updated: [31/12/2025]

These Terms and Conditions (the “Terms”) govern access to and use of the Alexandria application, operated by Quipalup, S.L., commercially known as Code Sherpas.

1. Identity of the Service Provider

Quipalup, S.L., with Tax ID (CIF) B01672674, having its registered office at Mossèn Amadeu Oller 38, 5-2ª, and registered with the Commercial Registry of Barcelona, Volume 47363, Folio 214, Section 8, Sheet B549719 (“Quipalup”, “Code Sherpas”, “Alexandria” or the “Provider”).

• Support: support@code-sherpas.rocks
• Legal contact: quipalup@gmail.com
• Postal address: Mossèn Amadeu Oller 38, 5-2ª

2. Scope, Acceptance and Related Documents

2.1. By creating an account, accessing or using Alexandria, the user (the “User”) declares that they have read and accepted these Terms.

2.2. If Alexandria is contracted by a company or organisation (the “Client”), the Client accepts these Terms and authorises use by its end users (the “Authorised Users”). In such case, the Client is responsible for workspace administration and access management.

2.3. Applicable documents. The use of Alexandria is governed by these Terms and by the Privacy Policy.

2.4. Integration notices. For certain integrations with third-party services, specific data use notices (“Data Use Notices”) are published in the Legal Documents Hub. In particular:

(a) “Google Drive Data Use Notice”; and

(b) “Data Use Notice (Meta) Publishing”.

2.5. In the event of any inconsistency between these documents, these Terms shall prevail. The Privacy Policy and the Data Use Notices supplement these Terms and shall apply with respect to data processing and, where applicable, the relevant integration.

2.6. Languages. These Terms and the Data Use Notices are provided in Spanish and English. In the event of discrepancy, the Spanish version shall prevail.

3. Definitions

Service: The functionalities of Alexandria available under the applicable plan.

Workspace: The working environment of an organisation within the Service.

User Content: Any information, material or content that the User or the Client (as applicable) (i) uploads, incorporates, connects, imports or otherwise makes available through the Service; (ii) creates, drafts, configures or records directly within the Service; or (iii) results from the use of the Service by the User or the Client, including, without limitation: documents or files imported from third-party services; content extracted or derived from such documents or files; courses, lessons, resources, configurations, recordings, responses, outputs and/or results generated within the Service; as well as profile information and preferences associated with use of the Service.

Public Content: Content that the User explicitly configures as public.

4. Description of the Service

Alexandria is a platform for managing organisational knowledge and learning, which may include:

• Assessment of individual and team competencies (assessments);
• Creation of personalised learning paths (“paths”);
• Creation of courses and lessons, including content import from Google Drive;
• Streaming sessions, which may be recorded; and
• Publication options if the User decides to make content public (including potential connections with social media platforms).

Note: Certain functionalities may be labelled as “beta”.

5. Registration, Accounts and Eligibility

5.1. Access and authentication. Alexandria uses Auth0 and access via a Google email account.

5.2. Minimum age. Alexandria is not directed at minors. Only individuals aged 18 years or older may use the Service.

5.3. Shared accounts. Sharing credentials or using accounts concurrently by multiple individuals is prohibited.

5.4. Account responsibility. The User must maintain the security of their account. Any activity carried out through the account shall be presumed to have been performed by the User, unless proven otherwise.

6. Plans, Payments and Renewals

6.1. Plans. Alexandria may offer free and/or paid plans available on the Website.

6.2.. Billing and payment. The Client (in B2B) or the User (in B2C) shall be responsible for payment of the applicable amounts under the contracted plan. Charges shall be made through the configured payment method (e.g., card via a payment service provider). At the time of payment, the possibility of requesting an invoice shall be offered, which will be issued upon request in accordance with applicable regulations.

6.3. Renewals and cancellation. These shall apply in accordance with the contracted plan.

6.4. Taxes. Prices may include or exclude applicable taxes, as appropriate.

6.5. Consumer users (B2C). For plans contracted by consumers, mandatory consumer protection rights under applicable law shall apply.

7. Use of the Service and Limitations

7.1. Users must use Alexandria lawfully and in accordance with these Terms.

7.2. Technical limits. For performance, security or Service evolution reasons, Quipalup may define or adjust technical and operational limits applicable to the use of Alexandria (e.g., permitted formats and sizes, storage capacity, processing times, number of operations or concurrent users), as well as to specific functionalities or plans.

7.3. “Beta” functionalities. Functionalities identified as “beta” are experimental in nature. They may be modified, suspended or withdrawn at any time and may not operate in a stable or complete manner.

8. Integrations with Third-Party Services

8.1. General framework. Alexandria may allow the User to connect their account with third-party services to import, export or publish content only at the User’s request. Use of integrations is subject to the terms and policies of the relevant third party, which the User undertakes to comply with. Quipalup does not control such services and does not guarantee their availability, continued operation or any changes to their terms.

8.2. Google Drive. Integration with Google Drive is optional and is activated only when the User connects it and explicitly selects the files they wish to work with (e.g., via a selector such as Google Picker). Alexandria does not access the User’s entire Drive, but only the selected files, and uses them to convert their content into material within the Service. For details regarding scope, processed data, retention and revocation controls, please refer to the “Google Drive Data Use Notice” published in the Legal Documents Hub.

8.3. Publishing on platforms (e.g., Instagram/Meta). Alexandria may allow the User to publish content on third-party platforms only at the User’s request. To execute the requested operation, Quipalup may process and temporarily retain strictly necessary technical information and delete it once the process is completed or fails, in accordance with the Privacy Policy. For details regarding the scope and data processing of this integration, please refer to the specific notice published in the Legal Documents Hub: “Instagram (Meta) Data Use Notice”.

9. User Content and Intellectual Property

9.1. Ownership of software and trademarks. The software, design, trademarks “Code Sherpas” and “Alexandria”, and other elements of the Service belong to Quipalup, S.L. or its licensors.

9.2. Ownership of User Content. User Content belongs to the User or the Client (as applicable). Alexandria does not acquire ownership over content imported or created by the User.

9.3. Licence to operate the Service. The User/Client grants Quipalup a non-exclusive, worldwide, royalty-free, revocable (to the extent permitted by the nature of the Service) and limited licence to host, store, reproduce, process, transform (e.g., convert into lesson format or other formats), communicate and display the User Content, and to make technical or temporary copies, solely to the extent necessary to:

(i) provide, maintain and improve the Service in accordance with these Terms;

(ii) enable functionalities requested by the User/Client (including export or publication to third-party services when requested by the User);

(iii) protect the security and integrity of the Service; and

(iv) comply with legal obligations.

This licence does not authorise Quipalup to use User Content for purposes unrelated to the provision of the Service.

9.4. User/Client responsibility. The User/Client warrants that it holds the necessary rights and authorisations to import and process the content (including any third-party data).

9.5. Public Content. If the User makes content public, the User authorises its availability in accordance with the selected configuration.

10. Archiving, Deletion and Erasure Requests

10.1. Default archiving. Upon deletion of a course, content may by default be moved to an archived status (not visible to standard users), rather than permanently deleted.

10.2. Deletion upon request. The Client may request deletion of accounts, content or data associated with its workspace at any time. Such request shall be processed in accordance with the Privacy Policy and applicable regulations. Where feasible, active data shall be deleted and backup copies purged in accordance with technical backup retention periods, where applicable.

In the case of individual accounts outside a B2B environment, the User may request deletion of their account in accordance with the Privacy Policy.

11. Support and Access by Support

11.1. Support is provided through support@code-sherpas.rocks.

11.2. Minimum access. Where strictly necessary to resolve an incident, authorised personnel may access course content within Alexandria applying the principles of: (i) technical necessity; (ii) minimum access; (iii) confidentiality; and (iv) traceability, where technically feasible.

12. Acceptable Use (Prohibitions)

It is prohibited to:

a) use Alexandria for unlawful purposes or infringe third-party rights (including intellectual property);

b) introduce malware or attempt to compromise the security of the Service;

c) access or attempt to access other users’ data without authorisation;

d) interfere with the Service or its operation;

e) use the Service for spam or unsolicited communications; and

f) engage in any use that contravenes these Terms or applicable law.

13. Availability, Changes and Maintenance

Quipalup may modify, update or discontinue functionalities for technical, legal or product-related reasons. Where changes are material, notice shall be provided through the Service or by other reasonable means.

14. Limitation of Liability

14.1. Service operation. Alexandria is provided with the aim of operating securely and reliably. Nevertheless, the Service may be affected by technical incidents, maintenance, updates, operational limitations, third-party dependencies or causes beyond our control.

14.2. Indirect damages. To the fullest extent permitted by law, Quipalup shall not be liable for indirect or consequential damages, nor for economic or business losses, including, without limitation, loss of profits, revenue, data, opportunities or business interruption, arising from the use of or inability to use the Service, even if advised of the possibility of such damages.

14.3. Maximum cap. To the fullest extent permitted by law, Quipalup’s total aggregate liability for any claim relating to these Terms or the Service, regardless of its basis (contractual, tort or otherwise), shall be limited to the total amount effectively paid by the Client or User to Quipalup for use of the Service during the twelve (12) months preceding the event giving rise to the claim.

14.4. Third-party services. Quipalup shall not be liable for interruptions, failures, decisions or changes in third-party services or platforms chosen by the User (including integrations), nor for their availability or operation.

14.5. Mandatory legal limits. Nothing in these Terms excludes or limits Quipalup’s liability where such exclusion or limitation is not permitted under applicable law. In particular, this clause does not seek to limit liability for wilful misconduct or intentional wrongdoing and, where applicable, for personal injury to the extent such liability cannot legally be excluded.

15. Governing Law and Jurisdiction

These Terms shall be governed by Spanish law.

For any dispute arising out of or in connection with these Terms, the parties submit to the courts of Barcelona, without prejudice to mandatory applicable rules.