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.
- No cookies. The site sets none, which is why you are not asked to dismiss a banner.
- No analytics and no tracking. No analytics script, tag manager, advertising pixel or session recorder is loaded.
- No third-party fonts or images. Fonts, images and the demonstration film are served from getfixity.com itself, so loading a page does not announce your visit to anyone else.
Two things still happen, because they have to:
| Who | What they receive | Why |
|---|---|---|
| Cloudflare | Standard 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 |
| Formspree | Whatever 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.
| Category | What it contains |
|---|---|
| Staff accounts | Full name, username, work email, phone number, employee code, role, a cryptographic hash of the password (never the password), last sign-in time. |
| Tickets | The 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 files | Images attached to tickets, compliance certificates, contracts and invoices, and anything that happens to appear in them. |
| Contractors and vendors | Company name, contact email, telephone number, out-of-hours emergency number, region and service categories. |
| Escalation records | Who was telephoned about a critical problem, at what time, whether they answered and which key they pressed. |
| Sites and organisations | Site names and addresses, the structure of the organisation, and its subscription and billing records. |
| Technical records | Mobile device tokens for push notifications, session tokens, and an audit trail of who did what and when. |
| AI records | Generated 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
| Purpose | Basis we rely on |
|---|---|
| Answering an enquiry you sent us | Your request, and our legitimate interest in responding to it |
| Providing the platform to a customer organisation | Performance of our contract with that organisation, and their instructions as controller |
| Keeping an audit trail of who did what | Legitimate interest in accountability, and our customers' own compliance obligations |
| Billing, invoicing and tax records | Performance of the contract, and legal obligation |
| Keeping the service secure and available | Legitimate interest in security |
| Telephoning a contractor about a critical problem | Performance 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.
- Uploaded documents are not sent to the model at all. Certificates, contracts, invoices and similar files stay on our servers. A text filter cannot redact the contents of a scanned document, so the files are excluded rather than filtered.
- Telephone numbers are removed from text before it is sent. Every outbound request passes through a single filter that replaces them with a marker, and the markers are removed again before anyone reads the result.
- What does reach the model is minimised ticket text: the description of the problem, the category, the site and room name, and the status. Enough to be useful, and no contact details.
- What the model provider may keep. We send through a commercial API rather than a consumer product, and such terms ordinarily forbid training on customer content. We would rather point at what we control than repeat a promise we have not re-read: the three points above are ours and are enforced in code. The provider's own retention period will be stated here once we have confirmed the terms in force.
- AI output is assistance, not advice. It can be wrong. Nothing in Fixity acts on an AI suggestion without a person, and you should not treat a generated summary as a professional, legal or safety judgement.
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.
- Do not photograph people. Photographs should show the fault, not the room's occupants. A photograph of a broken radiator should not have a child in it.
- Do not describe individuals in a ticket where describing the fault will do.
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.
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Amazon Web Services | Hosts the application, database and uploaded files | All platform data | Mumbai, India |
| Amazon Web Services | Holds the encrypted off-site backup copy | All platform data, encrypted before it leaves the main server | Frankfurt, Germany |
| Anthropic | The AI features | Minimised ticket text only; no uploaded documents and no telephone numbers | United States |
| Twilio | Automatic escalation calls | Numbers dialled, the spoken message, call outcome | Global |
| Google (Firebase) | Push notifications to the Android app | Device token, notification title and text | Google global infrastructure |
| Google (consumer Gmail, SMTP) | Outbound email | Recipient address and message content | Google 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 dictate | The 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 recognition | Set by the provider of that service |
| OpenStreetMap | Map tiles when an administrator places a site pin | The administrator's IP address and the map area viewed | Global |
| Cloudflare | Serves the public website | Website request logs | Global edge network |
| Formspree | Delivers the website demo form | The contents of that form | United States |
| Let's Encrypt | HTTPS certificates | Domain names only, no personal data | Global |
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
- All traffic is encrypted in transit with HTTPS, with HTTP Strict Transport Security enabled.
- Each customer organisation's data is isolated from every other organisation's, and that isolation is enforced in the database and covered by automated tests.
- Access inside a customer organisation is limited by role, and administrative, financial and owner actions are written to an audit trail.
- Passwords are stored only as cryptographic hashes.
- Third-party credentials, such as our AI and telephony keys, are encrypted at rest with a key held outside the database.
- Backups are encrypted before they leave the server, kept in three separate places including one outside the hosting region, and restoring them has been tested rather than assumed.
- Uploaded files are identified by their actual contents rather than by the name the browser claims.
Three limitations we would rather state than let you discover:
- Multi-factor sign-in is available. TOTP and one-time recovery codes are supported for enrolled users, including the platform owner. Customer enrollment is presently staged and is not mandatory for all users.
- Uploaded files are not scanned for malware. They are stored and served back to users of the same organisation.
- The audit trail is not a tamper-proof record, and it does not cover everything. It records who did what and when across administrative, financial and owner actions, including creating, changing and suspending an organisation and handling support messages. It does not cover every action in the product, and it is an application log held in the product's own database rather than an append-only or externally anchored store.
15. How long data is kept
We will describe what actually happens rather than a schedule we do not run.
- Platform data is kept for as long as the customer organisation's subscription continues. The organisation decides what to delete and when, and deletion today is carried out administratively on request rather than by an automatic timer.
- After a subscription ends, ask us for an export and for the workspace to be removed. Both are now done with a tool rather than by hand. We run it for you on request: it is not something you carry out yourself in one step. An erasure is first produced as a plan that reports exactly what would be removed and deletes nothing, and that plan has to be approved explicitly before it can run. At the moment it runs we check the plan still matches the data, so a plan that has gone stale is refused rather than applied, and a workspace under a legal hold is refused until the hold is released. We have run no export and no erasure for any customer to date. We have not fixed a number of days, and would rather say so than publish one the product cannot yet keep. Ask us and we will tell you where your workspace stands
- Encrypted backups are rotated after 14 days on the production host and 35 days for the Frankfurt off-site copy. A founder-held PC archive has no defined retention period at present, so we cannot promise deletion from every copy within 35 days. Records removed from the live system may remain in backups, and restoration of an older backup may reintroduce them until erasure is re-applied.
- Website enquiries are kept until the opportunity is closed and for a reasonable period afterwards. We have not set a fixed period; ask us and we will delete your enquiry
- Billing and tax records are kept for the period UAE law requires. We will state the period here once it is settled
- The audit trail is kept for the life of the workspace, because its purpose is to show what happened.
16. Your rights
Subject to the law that applies to you, you can ask to:
- know what personal data is held about you, and get a copy;
- have inaccurate data corrected;
- have data deleted, where it is not needed for a legal obligation or an evidence trail;
- restrict or object to a particular use;
- withdraw a consent you gave, without affecting what was done before;
- complain to the relevant supervisory authority.
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.
- Camera, to photograph a fault and to scan a QR sticker. Scanning is done by Google Play services on the device; the picture of the code is not sent anywhere.
- Microphone, only to dictate to the AI assistant instead of typing, and
only while you are holding the dictation control. We want to be exact about this one, because
it is the permission people most reasonably worry about.
- Fixity's own servers never receive audio. There is no endpoint that accepts a recording, and the app has no code that stores one. What our servers receive is the text that came back.
- Your speech may leave the device while you dictate, and we do not ask for it not to. The app hands the microphone to whichever speech recognition service is installed as your phone's recogniser, and tells it not to limit itself to offline recognition, because a recogniser that can reach the network is markedly better at accented English, which matters in the buildings Fixity is used in. Whether your speech is then actually sent anywhere is decided by that service and the mode it is running in, not by Fixity: some phones and some languages recognise entirely on the device, and others send the audio to the provider's servers. On most Android phones the recogniser is Google's, and where it transmits, the audio is handled under that provider's terms rather than ours. We are telling you this because we cannot promise the audio stays on your phone, not because we know that it leaves.
- While a recogniser is listening, the app also gives it, in the same request, a list of words to expect - your organisation's site codes, site names, rooms, areas and contractors, up to 200 of them - so that "vendor" is not heard as "wonder". They are sent to the recognition service with the dictation, on phones running Android 13 or later, and they travel exactly as far as the audio does: if that service recognises on the device, the list stays on the device too.
- Nothing obliges you to use it. The assistant is fully usable by typing, and the microphone is never opened unless you start dictation.
- Notifications, to alert you about a ticket. The app works without it; the alerts simply stay inside the app.
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:
- No location permission, of any kind. The app requests none and contains no location code, so it cannot ask your phone where you are. One honest caveat, because it is the kind of thing that should not be discovered later: a photograph can carry the place it was taken in its own metadata. Fixity shrinks and re-encodes every photo before it is uploaded, which discards that metadata entirely. If a photo cannot be processed - an unusual format, a damaged file - the app sends the original instead, and whatever the camera recorded travels with it.
- No advertising identifier, and no advertising or marketing software. There is no ad network in it and nothing in it profiles you.
- No analytics and no crash reporting. There is no analytics or crash-reporting library in the app, so no record of which screens you open, what you tap or how long you stay is collected by anyone.
- No access to your contacts, calendar, call log, messages or files beyond the photograph or document you choose to attach.
- No request logging in the released build. Request contents are logged only in development builds, which are never published.
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.
- If the data is inside a customer's workspace - tickets, photographs, reporter details, contractor records, staff accounts - we pass the request to that organisation, tell you we have done so, and help them carry it out.
- If the data is ours as controller - a demo enquiry from the website, a support message you sent us - we act on it directly.
- If you only want a device to stop receiving notifications, signing out of the app asks our server to forget it. That request is sent once and is not retried, so if the phone had no connection at the time, alerts can continue until it is registered to another account. Sign in and out again with a connection, or ask us.
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..