These pages may still change
Gelex has not launched yet. We may still adjust these pages before launch, for example once we have appointed our data protection officer. Every change is dated in the changelog at the foot of the page.
1. The corpus
- No scraping, crawling or systematic downloading, through the app, the API or the MCP connector, beyond what your own research needs.
- No using the service or its output to train, fine-tune or distil a machine-learning model.
- No rebuilding the corpus, its grades or its index as a product of your own.
2. The service
- No sharing sign-ins or API keys, also not with colleagues in your own organisation: each person has their own seat. No getting around allowances, seats, jurisdictions or rate limits.
- No reverse engineering the service, its grading or its index, except as far as the law allows despite this rule.
- No probing, scanning or testing our security without written permission. To report a vulnerability, write to security@gelex.eu.
- No interfering with the service or other customers' use of it, and no automated traffic designed to overload it.
3. What you put in
- Nothing you have no right to upload, and no content that is unlawful where you or we are.
- No personal data of others unless you have a lawful basis to process it. Take particular care with health, genetic or biometric data, criminal records and other special categories (GDPR Articles 9 and 10): upload them only where your matter needs them, and remember that a question you ask is also sent to the AI provider you connected.
- No use of templates or signing to deceive, impersonate someone, or forge a signature.
4. What happens if this is broken
We may limit, suspend or end access, starting with the least that stops the problem, and we tell you why unless the law or an investigation prevents it. You can ask us to review the decision at support@gelex.eu.
Changelog
- , version 1: First version.