Access control
Central login, organisation and home context, role permissions and restricted-record principles are designed to keep visibility purposeful.
Trust centre
Know what the system does, how it is protected and what is still being built.
Residential care software holds sensitive information. ResiNotes therefore separates product claims, security principles, privacy responsibilities and development status instead of hiding them inside sales language.
Product transparency
Live, beta and planned mean different things.
ResiNotes is a working platform in active development. We use these labels so organisations can judge the product on what is actually available.
Live working and availableBeta working and actively refinedPlanned not yet released
MFA and verification
Multi-factor and one-time passcode controls support stronger authentication in live environments.
Audit trail
Important account, record, medication, rota, export and administrative actions can leave an evidence trail for review.
Restricted information
Sensitive safeguarding information can be separated from ordinary operational views and limited to authorised roles.
Account removal
Disabled users should no longer retain routine platform access while historical audit information remains preserved.
Evidence and exports
Export and evidence-pack activity can require purpose or reason information so managers can understand why information was produced.
Hosting and resilience
ResiNotes uses layered hosting protections rather than relying on one control to perform miracles.
- Encrypted HTTPS connections
- Backups and recovery arrangements
- Firewall and network protections
- Malware scanning and maintenance
- Availability and service monitoring
- Secure data-centre principles
Privacy and data handling
Live customer arrangements distinguish the organisation’s responsibilities from ResiNotes’ processing role. The public privacy notice explains how website enquiries and other public-site information are handled.
- UK GDPR principles
- Purpose-limited access
- Confidentiality expectations
- Retention and offboarding considerations
- Data export and transition planning
Procurement questions
Ask before you buy.
We expect organisations to ask about security, data, implementation, support, beta areas and offboarding. Those are sensible questions, not obstacles to a sale.
Where is my data?
Hosting and data-location arrangements should be confirmed as part of the organisation’s procurement and data-protection process.
What happens if we leave?
Exit arrangements should include agreed access to organisational information and an orderly offboarding process rather than trapping the customer inside the platform.
What is still beta?
The public roadmap identifies areas under active refinement and separates them from work that remains planned.
Security pages deliberately stay high level. Publishing internal routes, administrative screens or operational security details would be a remarkably efficient way of defeating the purpose of having them.