Terms of use
Applicable to the tools hosted on parishla.team.
Research use only. These tools are not in-vitro diagnostic medical devices. Their output replaces neither the interpretation nor the validation of a qualified biologist, and supports no allocation or treatment decision on its own.
1. What you may do
- Use the tools interactively, for research, teaching, or as an interpretation aid in the laboratory.
- Publish results obtained with them, citing the tool and its version.
- Use the public API within the published quotas, with or without a key.
2. What is not allowed
- Automated extraction (scraping, robots, headless or driven browsers, scripted request loops) of the pages or of the compute routes, by any technical means.
- Reconstructing all or part of the reference frequency databases through repeated queries.
- Circumventing quotas: rotating IP addresses, obtaining multiple keys, sharing or reselling a key, or using a key issued to someone else.
- Any load likely to degrade the service for other users.
- Commercial redistribution of the results or of the reference data without prior written agreement.
If your work needs more than the published quotas, or the underlying data rather than the computation, the intended route is the API key request form: describe your use case and we will size the quota accordingly. It is faster than working around the limits.
3. Quotas and technical measures
Per-IP and per-key limits apply to the compute routes, both in the API and in the web
interface. Requests beyond them get an HTTP 429 response. We may suspend a
key or restrict an address in case of clearly automated or abusive use.
4. Data we process
No patient data is retained. The MFI values and antigens you submit are used for the computation and then discarded: they are never logged nor written to disk. Do not enter any identifier — patient name, record or sample number: the tool does not need one, and MFI values alone identify neither you nor a patient.
Running the service does however require keeping a small amount of technical data, listed here with its exact retention:
| Data | Why | Retention |
|---|---|---|
| IP address, timestamp, requested route, User-Agent header | Detect automated extraction and enforce the caps | 7 days |
| IP address linked to a recorded breach of the caps | Spot repeat offences spread over time | 90 days |
| Daily counter per IP address or per key | Enforce quotas and measure usage | 60 days |
| API key request: name, e-mail, institution, intended use, IP address | Review the request and size the quota | As long as the associated key stays active |
| Message sent through the contact page | To reply to you | As long as the exchange remains useful |
These are the retentions the service actually applies: purging is automatic. To exercise your rights of access, rectification or erasure over this data, reach us through the contact page.
5. No warranty
The tools are provided “as is”, without warranty of accuracy, availability or fitness for a particular purpose. Interpreting the results remains the user’s responsibility. The service may change or be discontinued without notice.
6. Contact
Questions, reports, collaboration requests: contact page.