Privacy

SecureObs Privacy Policy

Last updated: 9 June 2026

Prototype Status

SecureObs is currently a prototype and demonstration application. Demo builds may use local sample data so the workflow can be reviewed before a production backend is connected.

Clinical Data

The intended production model is for observation records and patient information to be stored on Trust-controlled infrastructure through a secure backend API connected to Trust-hosted SQL databases. The mobile app should not connect directly to SQL databases.

Staff Identification

SecureObs can use NFC staff card data to identify a staff member by a staff code. The app should use that code to match a staff record held by the Trust or authorised backend service.

Website Data

The website collects organisation and billing contact details when you register a package, together with your order, account credentials stored as a password hash, and records of your acceptance of the order terms and activation date. We use these to administer your account, implementation and billing. Stripe processes and stores payment details; we store Stripe references rather than card numbers. Do not enter patient information into signup forms.

Security Approach

• Clinical data should be transmitted over HTTPS.
• Production access should be controlled by staff role, ward, and site.
• Observation history should be auditable.
• Data retention should follow Trust policy and applicable clinical governance requirements.

Contact

Privacy and support contact details should be confirmed by the Trust or SecureObs implementation lead before wider testing or production release.