Privacy policy
What the platform collects, why it is held, who can see it and how long it stays. Written to match what the software actually does rather than to cover every eventuality. Last updated 1 September 2026.
Two things are worth knowing before the detail. Each client company sits in its own separate data store, so one building operator's records are never held alongside another's. And camera footage never leaves the building it was recorded in — only the events a rule was written for ever reach the portal.
01Who this policy is from
360SafeOps builds and operates the 360SafeOps platform: a mobile app for residents, a mobile app for building staff, a web portal for administrators, and on-premises camera services.
Two different relationships are covered here, and they matter. Where a building operator uses the platform to run their property, that operator decides what data is collected about their residents and staff, and we process it on their instructions. Where you deal with us directly — through this website, or as a client company — we decide, and this policy is our own.
02What is collected
The platform holds the information a building needs to deliver a service and prove it was delivered. Nothing is gathered because it might be interesting later.
- Account details: name, email address, phone number, and the unit or building you are attached to.
- Requests you make: the service, the time, any notes or photographs you attach, and the status history of the job.
- Work records: who was assigned, when each step started and finished, and the completion photograph.
- Money: invoices, receipts, outstanding balances and any payment proof you upload.
- Visits: guest passes you issue, and the entry and exit times recorded at the desk.
- Messages: which notifications were sent to you and whether they were delivered.
- Website enquiries: whatever you type into a form on this site, which reaches us as an email.
03Sensitive information
Medical requests and incident records are treated differently from everything else in the platform, because they should be.
They are visible only to staff whose building has explicitly cleared them for that kind of work, and every single time one of those records is opened, the access is logged with the name of the person and the time. Your building's administrators can read that log.
04Camera services
Where a building uses the camera services, the analysis runs on a machine physically inside that building.
Video footage does not leave the premises and is not sent to us. What travels to the portal is an event — what was detected, at which camera, at what time, and with what confidence — and only for the detection rules the operator has configured. Those events become service requests in the ordinary way.
05Why it is held
Each of these has a purpose attached to it, and the data is not used for anything else.
- To deliver the service you asked for, and to show you its progress.
- To calculate what is owed and to raise and settle invoices.
- To prove what was done, when, and by whom — which protects residents and staff equally.
- To let building operators run and staff their property, and to report on it.
- To send you the notifications you have chosen to receive.
- To answer the enquiry you sent us through this website.
06Who it is shared with
Your building operator sees the data belonging to their own buildings. Their staff see only what their role and building scope allow — there are twenty-one separate permissions behind that, set per person.
Each client company sits in its own separate data store. Your building's data is not held in a shared table alongside another operator's, which is both a privacy measure and the reason a handover on exit is clean rather than an extraction.
We use service providers for email and SMS delivery and for hosting. They process only what is needed to perform that function. We do not sell personal data, and we do not share it for advertising.
07How long it is kept
Request records, invoices and work proof are kept for as long as the building operator's own retention policy requires, because those records are what settle disputes and satisfy audits — sometimes years after the event.
When an account is closed, the account details are removed within 30 days of the request being verified — write to support@360safeops.com from the address on the account, or ask from inside the app. Records that must be retained for legal or accounting reasons are kept, but are disconnected from the closed account where that is possible.
08What you can ask for
You can ask for a copy of the personal data held about you, ask for something inaccurate to be corrected, ask for your account to be deleted, or object to a particular use of it.
Write to privacy@360safeops.com. If your data is held by a building operator using the platform, we will pass the request to them and help them answer it, because it is their record rather than ours.
09Keeping it safe
Passwords are stored hashed, never in a readable form. Access to the platform is authenticated on every request, and administrative actions are recorded in an audit log.
No system is beyond reach. If a breach affecting your data occurs, we will tell the affected operators and, where the law requires it, the individuals and the regulator — without waiting to establish the full extent first.
10Changes to this policy
This page carries the date it was last updated. Where a change materially affects how your data is used, we will tell client operators directly rather than relying on you noticing a new date.
Questions about any of this go to privacy@360safeops.com.
Ask us the question directly
Privacy questions get an answer from a person rather than a link back to this page. If the answer is that your building operator decides, we will say that and tell you who to ask.
Written to · privacy@360safeops.com