Security and privacy
Verified security and privacy controlsTrust, made visible.
Property operations contain personal, financial and tenancy information. Landwide describes the controls we can verify and connects privacy guidance to the people responsible for using it.
A responsible data flow
- 01Authenticate the person
- 02Scope organisation access
- 03Record and improve controls
Security foundations in the product.
These are the controls visible in the current system. They are not presented as a certification and may be supplemented by infrastructure controls and contractual measures.
Authenticated access
Accounts use managed authentication flows for sign-in, password recovery and session handling.
Organisation-scoped data access
Application requests carry organisation context and the interface applies role-aware permissions.
Browser security headers
The application configures controls including content security policy, HSTS and frame protection.
Session visibility
Users can review active session information and remove other sessions from the security settings.
Auditable operational records
Changes across operational records preserve the actor, time and organisation context needed for accountable review.
Transaction histories
Payment and rent transactions retain a chronological history of amounts, statuses, references and reconciliation activity.
Self-service and evidence, built in.
Landwide connects policy language, product controls and the evidence customers need to assess the platform responsibly.
Two-factor authentication
Authenticator-based 2FA adds a second verification step to account access.
Data-rights request workflows
Authenticated workflows support access, portability, correction and deletion requests with status tracking.
Retention automation
Evidence-based retention rules and deletion behaviour are organised by data category and legal purpose.
Documented security controls
Each public security commitment is connected to an accountable owner, implementation evidence and a review date.
The trust model
Access. Isolate. Observe. Improve.
Security is a continuing operating practice. The system, organisation and customer each have responsibilities that need to be understood and reviewed.
- 01 / ACCESS
Authenticate intentionally
Use managed identity and session flows before exposing organisation or tenancy information.
- 02 / ISOLATE
Keep organisation context explicit
Authorise requests against the intended organisation and apply role-specific permissions.
- 03 / OBSERVE
Retain useful security evidence
Review sessions, relevant audit fields and operational signals without collecting data without purpose.
- 04 / IMPROVE
Close control gaps openly
Keep policy wording aligned with the product and review controls and supporting evidence regularly.
GDPR responsibility
Compliance is a relationship, not a badge.
GDPR responsibilities depend on the facts: who decides the purposes and means, who processes data on instructions, and what contracts and controls apply.
Controller and processor roles
Property operators and Landwide may have different roles for different processing activities.
Data-subject rights
Access, rectification, erasure, restriction, portability and objection require usable response paths.
Appropriate security
Technical and organisational measures should reflect the data, purpose, threats and likely impact.
Purpose-based retention
Personal data should not be kept longer than the purpose and applicable legal obligations require.
Official data-protection sources
Guidance from Ireland’s DPC.
These sources explain the responsibilities and principles used to frame this page. They do not certify Landwide.
Reviewed 31 July 2026
This page provides general information about Landwide’s approach and current controls. It is not legal advice, a security certification or a guarantee of GDPR compliance for a customer’s own processing.
Trust and operations
Put security context beside the data it protects.
Trust should be easy to inspect.
Explore Landwide’s security and privacy controls and talk to us about your organisation’s requirements.
