Appropriate access
Permissions should reflect the user's role, responsibilities and the services available to their organisation.
Data & Security
Enterprise property intelligence, built with security and control in mind.
Saber Intel is designed to connect sensitive property, operational, compliance and security information without losing sight of access control, traceability, data ownership and responsible use.
Enterprise trust principles
Security across the intelligence layer
Access should reflect responsibility.
Information should only be available to authorised users with an appropriate business need.
Important activity should be traceable.
Changes, actions and source information should support operational accountability.
Connected does not mean uncontrolled.
Integrations should bring relevant information together without removing the controls of source systems.
AI should operate within clear data boundaries.
AI-assisted features should be designed around purposeful, controlled use of property information.
Trust by design
Property intelligence can include sensitive operational information. Security cannot be an afterthought.
Saber Intel is designed around the principle that data protection, permissions, evidence traceability and operational resilience should support the intelligence layer from the outset.
01 — Security principles
Control who can see, change and act on information.
Enterprise security is not one feature. It is the combination of access control, secure infrastructure, traceability, data handling and governance across the platform.
Client boundaries
Customer information should remain logically separated and accessible only within authorised organisational contexts.
Auditable activity
Important administrative changes and operational actions should leave a traceable record.
Controlled data use
Information should be processed for defined operational purposes rather than exposed more broadly than necessary.
02 — Security across the platform
Protect the property intelligence layer at each point of use.
The controls below describe the areas Saber Intel is designed to address. Detailed implementation and deployment controls should be confirmed as part of enterprise due diligence.
User access
Authenticated user access and role-based permissions help restrict platform functions and information to appropriate users.
Secure workflows
Security controls should protect sensitive actions, inputs, sessions and application workflows against unauthorised use.
Protected evidence
Property documents and evidence require controlled storage, authorised retrieval and appropriate access boundaries.
Controlled connections
External systems should exchange only the information required for the agreed integration purpose.
Monitoring & resilience
Operational controls should support system health, error visibility, recovery and reliable service delivery.
Accountability
Policies, responsibilities and review processes should support the technical controls across the platform.
03 — Access & permissions
Access should follow the organisation, the user and the responsibility.
Saber Intel separates service entitlement from user-level permissions so platform availability and individual access can be managed independently.
Client entitlementsControl which top-level services and sub-services are available to a client organisation.
User rolesDefine what individual system users can see and do within the services available to their organisation.
Experience controlPortal experience and publishing controls can further determine what is exposed to different user groups.
Administrative controlSensitive account and service changes remain restricted to authorised administrative users.
ReviewAccess should be reviewed when responsibilities, organisations or service requirements change.
04 — Your data remains your data
Connected intelligence should not weaken ownership or control.
Saber Intel is designed to operate as a secure intelligence layer around customer property information — not as a mechanism for repurposing that information outside the agreed service.
Specific contractual terms, retention arrangements and data-processing responsibilities should be documented for each customer deployment.
Data handling principles
Purposeful, controlled use
Customer informationUsed to provide the contracted platform services and connected intelligence functions.
Property documentsStored and retrieved within controlled application workflows and associated with authorised property records.
Operational recordsProcessed within the customer's authorised organisational and property context.
Integration dataShould be limited to the information required for the agreed source-system connection.
Retention & deletionShould follow documented customer requirements, legal obligations and agreed platform processes.
Important:
Detailed data-processing terms, controller/processor responsibilities and customer-specific retention requirements should be agreed contractually rather than inferred from this website.
Detailed data-processing terms, controller/processor responsibilities and customer-specific retention requirements should be agreed contractually rather than inferred from this website.
05 — Infrastructure & documents
Secure infrastructure supports the intelligence layer underneath.
Saber Intel uses cloud infrastructure and controlled document storage as part of the application architecture. Exact deployment, networking, backup and resilience arrangements should be documented for production environments.
Cloud hostingThe platform is built to operate on managed cloud infrastructure with environment-specific security controls.
Document storageBuilding documents are stored in Amazon S3 with corresponding application records linking them to the relevant property.
Controlled retrievalDocument access should be mediated through authorised application workflows rather than broad public access.
Environment separationDevelopment, test and production environments should be managed with appropriate separation of configuration and credentials.
ResilienceProduction hosting should include documented backup, recovery, monitoring and service-continuity arrangements.
06 — AI & customer data
AI should operate inside clear data and decision boundaries.
Saber Intel uses AI to help interpret connected property information. That makes source control, purpose limitation and human oversight especially important.
Purpose-limited promptsOnly information required for the relevant intelligence task should be provided to an AI service.
Source contextAI-assisted answers should remain connected to the underlying property records, documents and operational context where possible.
Human oversightAI output supports understanding and decision-making; it should not replace accountable human judgement in security, compliance or risk decisions.
Provider boundariesUse of third-party AI providers should be governed by the applicable service terms, configuration and customer data requirements.
Training claimsSaber Intel should make provider-specific statements about model training or data retention only where they are contractually and technically verified.
07 — Auditability & accountability
Trust depends on being able to understand what changed and why.
Administrative and operational traceability helps organisations review changes, investigate issues and understand the history behind the current property intelligence picture.
Configuration changesImportant settings and administrative changes should be recorded where operational accountability requires it.
ActionsProperty and compliance actions should retain ownership and status history where appropriate.
Source evidenceIntelligence should remain traceable back to the documents and records supporting it.
ExceptionsFailures, quarantined items or unusual conditions should be visible to authorised operators for review.
Operational reviewLogs and audit information should support investigation without exposing sensitive information unnecessarily.
08 — Enterprise due diligence
The questions we expect enterprise customers to ask.
Security and procurement teams should be able to examine the controls behind the platform. Where a control or certification is not yet in place, the answer should be explicit rather than implied.
Where is customer data hosted?
Document the production hosting region, infrastructure boundaries and relevant cloud services for the customer deployment.
How is user access controlled?
Explain authentication, user roles, client entitlements, administrative privileges and access-review processes.
How is client data separated?
Describe the application and data-layer controls that prevent one customer from accessing another customer's information.
How are property documents protected?
Explain storage, retrieval, permissions and any temporary access mechanisms used for document delivery.
How are integrations secured?
Describe authentication, authorisation, data minimisation, transport security and operational monitoring for connected systems.
What happens to data sent to AI services?
Provide provider-specific answers on processing, retention, training use and contractual controls rather than generic assurances.
How are backups and recovery handled?
Document backup schedules, recovery objectives, restoration testing and incident procedures for production environments.
Which certifications does Saber currently hold?
State only certifications actually achieved. Where Saber aligns to a standard or is working toward certification, describe that separately and accurately.
09 — Governance & continuous improvement
Security is an operating discipline, not a launch milestone.
Technical controls need supporting policies, ownership, review and ongoing improvement as the platform, integrations and customer requirements evolve.
PolicyMaintain documented security, privacy, access and incident-management expectations.
OwnershipAssign responsibility for application security, infrastructure, data protection and operational response.
ReviewReassess permissions, dependencies and controls as the platform and customer estate evolve.
TestingContinue application, infrastructure and deployment testing before material production changes.
ImprovementUse incidents, audits, customer due diligence and engineering reviews to strengthen controls over time.
Enterprise due diligence