NeraviseBack to homepage

Privacy information

Privacy Notice

This draft explains how Neravise Ltd may handle information connected with its website, enquiries, platform accounts and authorised clinical workflows.

Formal legal and data-protection review required: Controller and processor roles, lawful bases, retention periods, US healthcare terms, international-transfer safeguards and contact details must be confirmed for each processing activity before US clinical deployment.

1. Neravise Ltd

Neravise Ltd provides the Neravise platform. Its precise data-protection role depends on the activity and the applicable customer agreement. Neravise Ltd may be a controller for its own business contacts and a processor for some customer-managed clinical data. This must not be assumed without reviewing the relevant arrangement.

2. Information collected

Depending on how a person interacts with Neravise, information may include contact details, organisation details, account identifiers, authentication events, support communications and information submitted through authorised platform workflows.

3. Public website information

The public website may process basic technical request information needed to deliver and secure pages. Non-essential analytics must not operate before an appropriate consent choice is available.

4. Business and demonstration enquiries

When someone contacts Neravise about a demonstration, service or partnership, Neravise may use their name, business contact details, organisation and enquiry to respond and manage the relationship.

5. Account information

Account information may include a user's name, work email, organisation, role, access status and security-related activity. Customer organisations determine who should receive access and which permissions apply.

6. Healthcare and Clinical Information

Clinical information may include referral details, consent records, developmental history, assessment notes, recordings, transcripts, evidence, review decisions and reports. This information requires heightened protection and should be processed only through authorised clinical workflows for documented purposes.

7. United States Healthcare Data

Where Neravise is provided to a US healthcare organisation, handling Protected Health Information may require appropriate Business Associate Agreements, eligible vendor services, technical safeguards, organisational policies and customer authorisation. These requirements must be verified for the specific deployment before real US clinical information is processed.

8. Purposes and lawful bases

Purposes may include providing and securing the service, responding to enquiries, administering accounts, maintaining audit records and meeting legal obligations. The lawful basis for each purpose requires confirmation in the final reviewed notice.

9. Processors and service providers

Neravise may use authorised providers for hosting, database, authentication, storage, email or optional processing. The final notice should identify relevant providers or provide a current subprocesser link, together with the purpose of their processing. No provider should receive clinical information until its role, contract and service configuration are approved.

10. International transfers

If information is transferred outside the country in which it was collected, Neravise and the customer organisation must confirm the applicable transfer mechanism, contractual safeguards and service configuration.

11. Retention

Information should be retained only for documented business, clinical, contractual or legal purposes. Final retention periods must reflect the record category, customer instructions and applicable law.

12. Security

Neravise uses technical and organisational safeguards intended to protect information, including role-based access, organisation-aware controls and auditability. No system can guarantee absolute security. See Security and Data Protection.

13. Individual privacy rights

Depending on applicable law, individuals may have rights relating to access, correction, deletion, restriction, objection, portability or complaints. The appropriate contact and response route depends on whether Neravise Ltd or a customer organisation is responsible for the request.

14. Cookies and analytics

See the Cookie Notice for information about cookies currently used and how future non-essential technologies would be controlled.

15. Contact information

For general privacy enquiries, contact info@neravise.com. Do not send patient-identifiable information by ordinary email.