Fixity

Privacy Policy

This explains what personal data Fixity handles, why, who else sees it, and what you can ask us to do about it. It covers both the getfixity.com website and the Fixity maintenance platform.

Version 1.0 · Last updated 13 October 2026

1. Who we are

Fixity is a maintenance platform operated from the United Arab Emirates by its founder, and is referred to below as "Fixity", "we" or "us". It is not yet a registered company. When one is registered, this page will name it, its legal form, its trade licence number and its registered address.

Contact for anything in this policy, by email: hello@getfixity.com. It is the address published on our website, and it is read.

We have not appointed a data protection officer; a message to the address above reaches the person responsible.

2. Our two roles, which matter for your rights

Fixity handles personal data in two different capacities, and which one applies changes who you should approach.

We are the controller for the website, for enquiries you send us, and for the accounts and billing records of the organisations that buy Fixity. We decide why and how that data is used, and this policy governs it.

We are a processor for everything inside a customer's Fixity workspace: tickets, photographs, site records, vendor contacts, staff accounts and the rest. The organisation that bought Fixity, typically your employer or the operator of the building, decides what goes in and why, and we act on their instructions.

What this means in practice: if you are a member of staff, a visitor who reported a problem, or a contractor, and you want your data corrected or removed from a Fixity workspace, the organisation that runs that workspace decides. Write to them. You can also write to us and we will pass the request on, tell them, and help them act on it, but we will not delete or alter their records on our own initiative.

3. If you only visit the website

getfixity.com is deliberately quiet.

Two things still happen, because they have to:

WhoWhat they receiveWhy
CloudflareStandard web server request logs, which include your IP address, the page requested, your browser's user agent and the time. Cloudflare serves the site and filters malicious traffic.Hosting and security
FormspreeWhatever you type into the demo request form, when you submit it: your work email and phone, which are required, and your name, company, number of sites and message, which are optional.Delivering the form to us

We use what you send through that form to contact you about a demonstration and to answer your questions. We do not sell it, we do not share it for advertising, and we do not add you to a marketing list you did not ask to join. If you ask us to delete your enquiry, we will.

4. Data in the Fixity platform

The categories below exist in a Fixity workspace. The customer organisation controls them; we list them so everyone can see what the system actually holds.

CategoryWhat it contains
Staff accountsFull name, username, work email, phone number, employee code, role, a cryptographic hash of the password (never the password), last sign-in time.
TicketsThe description of the problem, the location, the priority, who raised it and when, and the name and phone number of the person who reported it where they gave one.
Photographs and filesImages attached to tickets, compliance certificates, contracts and invoices, and anything that happens to appear in them.
Contractors and vendorsCompany name, contact email, telephone number, out-of-hours emergency number, region and service categories.
Escalation recordsWho was telephoned about a critical problem, at what time, whether they answered and which key they pressed.
Sites and organisationsSite names and addresses, the structure of the organisation, and its subscription and billing records.
Technical recordsMobile device tokens for push notifications, session tokens, and an audit trail of who did what and when.
AI recordsGenerated summaries, translations and monthly analyses, and a record of how much AI processing each site used.

Accounts in the Fixity platform are created by the customer organisation. You cannot sign yourself up, and we do not create accounts for individuals.

5. If you reported a problem by scanning a QR code

You can report a problem in a building without having a Fixity account. If you do, and you give your name or a telephone number so somebody can get back to you, those details are stored on the ticket and are visible to the staff and contractors handling it.

You do not have to give them. A report without a name or number still reaches the people responsible; it simply means nobody can call you back about it.

The organisation that operates the building controls that record, not Fixity. If you want it removed, ask them, or write to us and we will pass it on.

The form does not yet show a notice beside those fields. We are adding one

6. If you are a contractor working through Fixity

Your company's contact details, including an emergency number if one was given, are held so that work can be assigned to you and so that you can be reached when something urgent happens at a site you cover. If a critical job is not accepted, the system may telephone the number on file automatically. Section 9 explains that.

Records of jobs you accepted, attended and completed, and of calls placed to you, are kept as the evidence trail of the work. The customer organisation controls those records.

7. Why we process personal data, and on what basis

PurposeBasis we rely on
Answering an enquiry you sent usYour request, and our legitimate interest in responding to it
Providing the platform to a customer organisationPerformance of our contract with that organisation, and their instructions as controller
Keeping an audit trail of who did whatLegitimate interest in accountability, and our customers' own compliance obligations
Billing, invoicing and tax recordsPerformance of the contract, and legal obligation
Keeping the service secure and availableLegitimate interest in security
Telephoning a contractor about a critical problemPerformance of the customer's instructions and their legitimate interest in keeping their premises safe

A note on the language above. It uses the controller, processor and legitimate-interest vocabulary most readers will recognise. The terminology that applies to us under UAE law, and under the regime of whichever free zone the company is registered in, will be settled with a lawyer and corrected here if it differs

8. Artificial intelligence features

Fixity uses a large language model from Anthropic to triage tickets, summarise, translate and produce monthly analyses. We have deliberately narrowed what reaches it, and we would rather describe that precisely than reassure you vaguely.

AI processing can be switched off for a customer organisation on request.

9. Automatic telephone calls

When a critical problem is not accepted in time, Fixity can telephone the people responsible, in an order the customer organisation configures: typically the contractor first, then the facilities manager, then a senior manager. The call states the site, the location and the problem, and offers keys to accept the job, decline it, or hear the message again.

Calls are placed through Twilio, which receives the numbers dialled, the spoken message and the outcome of the call. Calls are not recorded. What is stored is the fact of the call, its time, and what the person did.

Fixity is not an emergency service. It telephones the people your organisation nominated about a maintenance problem. It does not contact the police, civil defence, an ambulance or any public emergency number, and it must never be relied on in place of them.

10. Push notifications and email

If you use the Android app, a token identifying your device is stored so notifications can reach you. Notifications are delivered through Google's Firebase Cloud Messaging, which receives the token and the title and text of the notification. That text can name a site and summarise a ticket, so please treat it as data leaving to Google.

Email, including scheduled reports and one-time sign-in codes, is sent through a standard SMTP provider, which receives the recipient address and the content of the message. Today that provider is Google's consumer Gmail service: production sends through smtp.gmail.com from a Gmail account, using an app password. A consumer Gmail account is not the same thing as a Google Workspace account, and we would rather say so than imply a commercial arrangement we do not have. We are moving this to a dedicated sending service, and this paragraph will change when we do.

11. Children and other sensitive settings

Fixity is built for facilities management, including sites such as nurseries and clinics where children or patients may be present. It is a maintenance system and it is not designed to hold information about children, patients or any other vulnerable person, and we ask customers not to put it there.

We have no way to stop a photograph being taken, so the responsibility sits with the customer organisation and the person using the app. Where we are told that such content exists, we will help the customer remove it promptly.

We are adding a line to the same effect on the photo upload screen

12. Service providers who process data for us

Verified against the running system rather than copied from an older document.

ProviderWhat it doesWhat it receivesWhere
Amazon Web ServicesHosts the application, database and uploaded filesAll platform dataMumbai, India
Amazon Web ServicesHolds the encrypted off-site backup copyAll platform data, encrypted before it leaves the main serverFrankfurt, Germany
AnthropicThe AI featuresMinimised ticket text only; no uploaded documents and no telephone numbersUnited States
TwilioAutomatic escalation callsNumbers dialled, the spoken message, call outcomeGlobal
Google (Firebase)Push notifications to the Android app Device token, notification title and textGoogle global infrastructure
Google (consumer Gmail, SMTP)Outbound emailRecipient address and message contentGoogle global infrastructure
Your phone's speech recognition service (on most Android phones, Google's)Turns dictation into text for the AI assistant, when you choose to dictateThe audio you speak, and a list of your organisation's site, room and contractor names so they are recognised correctly. Not Fixity's servers: this is the recogniser built into your phone, and the app asks it not to restrict itself to offline recognitionSet by the provider of that service
OpenStreetMapMap tiles when an administrator places a site pinThe administrator's IP address and the map area viewedGlobal
CloudflareServes the public websiteWebsite request logsGlobal edge network
FormspreeDelivers the website demo formThe contents of that formUnited States
Let's EncryptHTTPS certificatesDomain names only, no personal dataGlobal

We do not use any advertising network, data broker, analytics service or crash-reporting service. We do not sell personal data, and we have never done so.

We will tell customer organisations before adding a provider that handles their platform data, so they have an opportunity to object.

13. Where data is held, and transfers out of the UAE

We state this plainly because customers assume otherwise: the Fixity platform runs on servers in Mumbai, India, not in the United Arab Emirates. The encrypted backup copy is held in Frankfurt, Germany. AI processing takes place in the United States, and telephone, notification and email providers operate internationally.

If where your data is held matters to your organisation, raise it with us before you subscribe rather than after

14. How personal data is protected

Three limitations we would rather state than let you discover:

15. How long data is kept

We will describe what actually happens rather than a schedule we do not run.

16. Your rights

Subject to the law that applies to you, you can ask to:

Write to hello@getfixity.com. We will acknowledge promptly and respond within a reasonable time, and we will tell you how long the rest will take when we acknowledge it.

Remember section 2: if the data is inside a customer's workspace, the customer decides, and we will route your request to them and support it.

17. If something goes wrong

If a security incident affects personal data, we will investigate immediately, inform affected customer organisations without undue delay, tell them what we know and what we are doing, and notify the authorities where the law requires it. We would rather tell a customer about an incident that turned out to be minor than be discreet about one that was not.

18. Changes to this policy

If we change it materially we will update the version and date at the top and, where the change affects customer organisations, tell them directly. Older versions are available on request.

19. Contact and complaints

Email hello@getfixity.com, There is no postal address to write to yet; email reaches us. If you are not satisfied with our answer you may complain to the data protection authority with jurisdiction over you.

20. The Fixity app on Google Play

This section describes the Android app specifically, because Google Play asks for it and because an app is the part of Fixity most people actually touch. Everything in it was read from the released build rather than from a design document.

You cannot create an account in the app. There is no sign-up screen. An administrator at the organisation that bought Fixity creates accounts and issues the first password. The app signs you in; it does not enrol you.

What the app sends to our servers. Your account details, which your organisation entered: name, username, work email, telephone number, employee code and role. The tickets you write, including the description of the problem and where it is. Photographs you attach. Invoices and documents you attach to a cost. Messages you send to Fixity support. What you type to the AI assistant. If you report a problem by scanning a QR sticker without signing in, the name and telephone number you choose to give, which are optional.

The three permissions the app asks for, and why.

Notifications. A token identifying your installation is stored so alerts can reach you, and alerts are delivered through Google's Firebase Cloud Messaging. The text Google carries names a ticket number, a site, and sometimes the contractor assigned. It does not carry the description somebody typed, nor the name or telephone number of whoever reported the problem. Signing out removes the session from the device and asks our server to forget the device, so alerts stop. That request is sent once and is not retried: if the phone has no connection at the moment you sign out, the server can keep the registration and alerts can continue to arrive until the device is registered to another account or the notification service reports the registration as dead. If that happens to you, sign in and out again with a connection, or tell your administrator.

What the app does not do. We would rather list these than let you assume them, and each was checked in the released build:

On the device, and in transit. The session is held in Android's encrypted storage. Tickets are cached locally so the app is usable on a weak connection. All traffic is HTTPS, and the released build refuses to connect over plain HTTP at all.

21. Asking for data to be deleted

There is no delete button in the app, and the honest reason is section 2: for anything inside a workspace, the organisation that bought Fixity decides, not us. One thing to know before you ask: an account can only be erased outright if the person never recorded anything. Once somebody has raised a ticket, logged a step, decided a cost or uploaded a file, the records refer to them, so their account is deactivated instead and their name stays on that history. That is how a maintenance record remains a true account of who did what. We will not delete an employer's maintenance records because an individual asked us to. What we will do is make the request reach the right people and help them act on it.

How to ask. Write to the address in section 19, or use the request page at getfixity.com/data-deletion. Tell us what you want removed and enough to find it, such as the organisation, the site, and roughly when. You do not need an account to ask, and you do not need to explain why.

What happens next.

What we cannot promise, and why. Deleting a record from the live system does not reach every copy at once. Encrypted backups are rotated after about fourteen days on the production server and about thirty-five days on the off-site copy, and a third archive held by the founder has no defined retention period yet, so we cannot honestly name a date by which a record is gone from everywhere. Restoring an older backup after a legitimate failure can also bring a deleted record back until the deletion is applied again. Some records are kept because they are evidence: who was telephoned about a critical fault and whether they answered is the proof trail the customer relies on, and the audit log exists precisely so that actions cannot be quietly undone..