Claims data, handled accordingly.
An inspection brings together personal data, photos of homes and vehicles, and insurers' contract information. We design PeritOS and Teleperitagens so that every piece of that data is protected, traceable and kept in the European Union.
In the European Union.
Data is hosted within the EU.
Encrypted.
In transit and at rest.
Traceable.
Every access goes into an immutable log.
Minimal.
Each profile sees only what it needs to do its job.
Why inspection data deserves extra care.
A claim file is not just another customer record. It holds the policyholder's name, address and contact details, photos of the inside of a home or a vehicle's number plate, technical reports, policies and, in some lines of business, sensitive information about the people involved. It passes through many hands: the insurer, the loss-adjusting firm, the adjuster in the field, the supervisor who reviews the report.
Each of those hand-offs is a point where information can go missing, be copied where it shouldn't be or be seen by someone who doesn't need it. That is why, in PeritOS and Teleperitagens, security is not a layer added at the end: it is built into the way cases, profiles and files are designed from the start.
PeritOS
Hosting
European cloud, dedicated high-performance servers with SSD storage.
Availability
Active 24/7 monitoring and geographic redundancy, so a failure in one location does not stop the operation.
Backups
Daily, isolated from production and tested.
Access
Role-based profiles (adjuster, supervisor, coordinator, manager, insurer); immutable audit log.
Media
Cloud storage with scalable document management and CDN delivery.
Teleperitagens
Real-time video
Cloudflare Calls (SFU). The policyholder joins from a link, with no app to install.
Storage
AWS S3 within the EU.
Encryption
At rest and in transit.
Integrity
SHA-256 hash on every photo, video and PDF, to prove the file has not been altered.
Sharing
Signed URLs that expire: a forwarded link stops working once its time is up.
Audit
Full audit trail per session.
Who sees what, and how it is recorded.
The principle is simple: each person accesses only what their role requires, and every access leaves a trace. The full profile matrix is on the PeritOS page.
Role-based profiles
An adjuster sees the cases assigned to them; a supervisor, the reports they need to review; management, the KPIs. Nobody is given access “just in case”.
Insurer portal
Each insurer sees the status, photos and reports of its own cases, and only those. Find out more in PeritOS for insurers.
Immutable audit log
It records who opened which case and when. The log cannot be edited or deleted, and it is available for audit.
Backups and continuity.
We take daily backups and store them in isolation from the production environment. If a server fails, a file is deleted by mistake or an incident affects production, the backups are not dragged down with it. And a backup only counts if it can be restored, which is why our backups are tested.
The platform is monitored 24 hours a day, 7 days a week, by the same team that builds it, with geographic redundancy. When something looks wrong, whoever receives the alert knows the code and can act straight away, without handing the problem to a third party. Meet the team on our About page.
GDPR in a claims inspection: who is responsible for what.
The General Data Protection Regulation distinguishes two roles. The controller decides why and how personal data is processed: in a claims inspection, that is the loss-adjusting firm or the insurer. The processor handles the data on the controller's behalf and on its instructions.
CloudWorks acts as processor. That means the data in your cases is yours: we process it only to run the service. The relationship is set out in a data processing agreement (DPA), as Article 28 of the GDPR requires.
Data subjects, such as policyholders and third parties, have the right of access, rectification and erasure. The platform lets the firm or insurer respond to those requests without manual exports or spreadsheets.
GDPR
CloudWorks acts as processor; the loss-adjusting firm or insurer is the controller.
List of sub-processors available on request.
Data subject requests (access, rectification, erasure) supported by the platform.
What we send your security team.
Insurers assess their suppliers before trusting them with customer data, and the firms that work for them are assessed too. We make that assessment easier.
Technical documentation
Architecture, hosting and security measures for PeritOS and Teleperitagens.
Completed questionnaire
Answers to your vendor assessment questionnaire, in whatever format your team uses.
Security and GDPR questions
Where is case data hosted?
Within the European Union, for both PeritOS and Teleperitagens. Photos, videos and reports from remote inspections are stored in AWS S3 in the EU.
Is the data encrypted?
Yes, in transit and at rest. Information travels encrypted between the app, the browser and the servers, and is stored encrypted.
Can we find out who looked at a case?
Yes. Every access is recorded in an immutable audit log, which can be checked in the event of an audit or a complaint.
Who is the data controller?
The loss-adjusting firm or the insurer. CloudWorks is the processor and handles data only on your instructions, under a data processing agreement (DPA).
How do you show a photo has not been altered?
In Teleperitagens, every photo, video and PDF gets a SHA-256 hash when it is stored. Any later change to the file no longer matches that hash.
Have a security questionnaire? We'll answer it.
We send the technical documentation, the DPA and answers to your vendor assessment questionnaire. Direct email: info@cloudworks.pt (subject "Security")