Privacy Policy
Fabora Privacy Policy
Last updated: 17 November 2026
This page explains, in plain English, how Fabora handles information on the public Fabora website at faboraplatform.com, in the Fabora Steel Tools mobile app (see section 10), in LEV Ready, our extraction records service on the web and on the phone (see section 12), and in Fabora RAMS, our risk assessment and method statement service on the web and on the phone (see section 13).
1. The short version
We keep data collection to a minimum. We don't sell your details. Analytics cookies and advertising cookies for Meta and OpenAI only go on your device if you agree to them, and you can change your mind at any time with the Cookie settings link at the bottom of every page. The only personal information we actively gather is what you choose to send us when you get in touch or start a trial. If you agree to advertising cookies, the Meta Pixel also tells Meta which pages you view here and which download links you click (see section 2). For Fabora RAMS, we also use consented ad-click identifiers and confirmed trial and payment events to measure our ChatGPT ads, as explained below.
2. What we collect, and when
- When you use the contact form: we receive what you type, usually your name, company, email address, the type of enquiry and your message.
- When you email us at info@faboraplatform.com, we keep your message and address so we can reply.
- When you start a paid trial: our payments provider, Stripe, handles your card and billing details. We never see or store full card numbers ourselves.
- When you browse: Ahrefs Web Analytics counts page visits for every visitor. It sets no cookies and stores nothing in your browser. If you agree to analytics cookies, Google Analytics also shows us which pages get visited and where visitors come from. We look at both in aggregate and do not use them to identify you personally.
- When you browse, only if you agree to advertising cookies: the Meta Pixel tells Meta, the company behind Facebook and Instagram, each page you view on this site, and when you click an App Store or Google Play download link, send the contact form, or go on from a trial signup form to checkout. We send only which page, link or form it was. We never send your name, email address, phone number or anything you type into a form. Like any web request, each one also carries your IP address, your browser details, the page address and the page you came from, along with the Meta cookies described in section 5. If you are signed in to Facebook or Instagram in the same browser, Meta may be able to link these events to your account.
- For Fabora RAMS, only with advertising consent: we record an OpenAI ad-click reference from the link you followed, and an existing OpenAI browser reference if present. After Stripe confirms a completed trial checkout and your RAMS account is set up, our server can report the completed trial to OpenAI with a value of £0. Confirmed payments are separate events containing the amount actually paid, currency, event time and a repeat-safe event identifier. We do not send your name, email address, card details, RAMS documents or your IP address in these server reports. A free trial is not reported as paid revenue.
- On the contact form: a quick spam check runs in the background to confirm the request is from a real person, not a bot.
3. Why we use it
We use this to reply to your enquiry, set up a trial when you ask for one, keep the site and form free of spam, and work out which pages are useful so we can improve them. If you agree to advertising cookies, we also use the Meta Pixel to measure and improve our ads on Facebook and Instagram: to see whether they lead to visits, app downloads, enquiries and trial signups, to help Meta show them to people likely to find them useful, and to show Fabora ads to people who have visited this site. For ChatGPT ads, consented RAMS trial and payment reports help us check whether advertising brings paying customers. We don't sell it or use it for anything else. Meta's own use of the Meta Pixel data is covered in section 4.
4. The providers we rely on
Running a website takes a few specialist services. Here is who they are and what each one does. Meta also uses the data it receives for its own purposes, as described below:
- Vercel: hosts the website
- Resend: sends and delivers our contact emails
- Stripe: handles trial checkout and payments
- Google Analytics: website analytics, used only if you accept analytics cookies
- Ahrefs: cookie-free counts of page visits, for every visitor
- Meta Platforms Ireland Limited: the Meta Pixel, for measuring and improving our Facebook and Instagram ads and showing them to people who have visited this site, used only if you accept advertising cookies. Meta is jointly responsible with us for collecting this data on our site and sending it to Meta. Meta then also uses it for its own purposes, under its own terms. Meta may transfer this data to Meta Platforms, Inc. in the United States. Meta explains what it does with it in its own privacy policy at facebook.com/privacy/policy.
- Cloudflare Turnstile: the spam check on the contact form
- OpenAI: receives consented Fabora RAMS conversion reports to measure our ChatGPT advertising. We request that these events be excluded from future user-level personalisation. OpenAI explains its handling of conversion data in its Conversion Terms and Privacy Policy.
5. Cookies
Your cookie choice and your light or dark theme are remembered in your browser's own storage for this site, so the banner does not ask again on every page. Your light or dark theme is not sent to us. When you start a RAMS checkout with advertising consent, we also save that consent and its date with the checkout so later trial and payment reports can respect it. The optional cookies and storage items below only go on your device if you say yes in the banner. Say no and the site still works exactly the same. You just won't show up in our analytics or ad measurement.
- Analytics cookies: Google Analytics sets
_gaand_ga_cookies, which last up to 2 years, to tell visits apart. Our ownfabora_first_touchcookie, which lasts 180 days, remembers where you first arrived from (the campaign tags on the link you followed, the site that sent you, your first page and the date), so a Fabora RAMS trial signup can record which of our marketing brought you. - Advertising cookies: the Meta Pixel sets
_fbp, a random identifier for your browser that lasts about 90 days. When you arrive from a link on Facebook or Instagram, such as one of our ads, it also sets_fbc, which records that click and also lasts about 90 days, and Meta may set_fbleid, which lasts 7 days, when you then click a download link or send a form. - Advertising storage items:the Meta Pixel also keeps a few small items in this site's browser storage.
lastExternalReferrerandlastExternalReferrerTimerecord whether you came from Facebook, Instagram or somewhere else, and when. After you follow a link from Facebook, Instagram or a Meta ad,multiFbcandaemSourcerecord details of that click. Browser storage has no expiry date of its own, so these items stay until you withdraw or clear your browser data, although the pixel ignores referrer and click details older than about 90 days. - ChatGPT ad measurement: our
fabora_openai_adscookie remembers your advertising consent and any available OpenAI ad-click or browser reference for up to 30 days. We preserve the actual reference; campaign tags alone are not treated as proof of an ad click. A separate secure cookie links this browser to its checkout consent records so a withdrawal can also stop later server reports. This link cannot be read by page scripts. Checkout consent records are held with Stripe's billing records; we use ad references for measurement only while the consent record is current and within its 30-day period. - Meta's own cookies:if your browser allows it, each Meta Pixel event also carries Meta's own facebook.com cookies, such as
fr, and the cookies that keep you signed in to Facebook. Those belong to Meta and are covered by Meta's own cookie policy, so you manage them in your Facebook settings or your browser, not here.
Changing your mind:use the Cookie settings link at the bottom of every page to change or withdraw either choice at any time. When you withdraw a choice, the browser stops optional measurement and deletes the matching advertising cookies. For RAMS server reports, the website also sends a withdrawal to our server for the checkouts linked to this browser. If the connection fails, it shows that confirmation is pending and retries; later payment reports stop once the server receives the withdrawal. To withdraw across other browsers or devices, contact us using section 9. Meta's own facebook.com cookies are not ours to delete, but nothing from this site carries them once you have withdrawn.
6. Our lawful basis (UK GDPR)
Where we handle personal data, we rely on your consent for analytics cookies and for advertising cookies, the Meta Pixel and OpenAI conversion measurement, our legitimate interest in answering enquiries, protecting the site and counting page visits without cookies, and, for trial sign-ups, taking steps you have asked for before any contract. You can withdraw consent at any time with the Cookie settings link; that does not affect anything sent before you withdrew. In the Steel Tools phone apps (section 10), ad measurement also relies on your consent, which you can withdraw in the app's Settings, reading a photo or comparing two drawings with Fabora Max relies on the contract you have with us for Fabora Max, and sharing your Goods In Count counts relies on your consent, which you can withdraw in the app at any time. Marketing emails from Fabora RAMS (section 13) rely on your consent too, which you can withdraw at any time in Company Settings or with the unsubscribe link in any marketing email.
7. How long we keep it
We hold enquiry emails and form messages only as long as we need them to deal with your query and keep sensible business records, then we remove them. Stripe keeps billing records for as long as tax and accounting rules require. The cookies and storage items in section 5 last as long as described there, and the ones this site set go straight away when you withdraw your choice. Meta keeps the Meta Pixel events it receives under its own privacy policy, and OpenAI handles the conversion events it receives under the terms and privacy policy linked in section 4. For the Steel Tools app, Fabora keeps no photo, drawing or reading from Fabora Max (section 10) unless you choose to share a Goods In Count count, and its monthly read counts are deleted three months after the month ends. Goods In Count counts you choose to share are kept for up to two years, or until you delete them in the app or ask us, and our working copies of them go with them.
8. Your rights
Under UK data protection law you can ask to see the data we hold about you, have it corrected or deleted, or object to how we use it. Where we rely on your consent, you can withdraw it at any time with the Cookie settings link or, for Goods In Count sharing in the Steel Tools app, in the app (section 10). Email us and we'll sort it out. If you are not happy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk.
9. Asking us about privacy
For anything about your data, or a message you sent through the website, email us at info@faboraplatform.com.
10. The Fabora Steel Tools app (mobile)
Fabora Steel Tools is our offline calculator and reference app for steel fabrication, available on the App Store and Google Play. It is separate from this website and works very differently: your calculations, saved jobs, photos and preferences stay on your device, unless you choose to send a photo to be read, compare two drawings or share a Goods In Count count. Every calculation runs offline on your device. The app has no accounts or logins and shows no ads. It sends these things and nothing else: anonymous counts of which tools and screens get used and when the app hits an error, which you can switch off; a subscription check with RevenueCat when the app opens and when you buy or restore Fabora Pro or Fabora Max; an access code if you enter one in the Android app or the web version; a sign-in link if you use your subscription on a computer; on the phone apps, a registration with Google's Firebase Cloud Messaging so our notifications can reach you; only if you say yes, ad measurement to TikTok and Meta; with Fabora Max, a photo you choose to have read by AI, only after you agree, and two drawings you choose to compare; and, only if you switch it on in Goods In Count, the counts you check there with their photos, to train our own counter. All of these are described below. The website analytics, cookies and providers described above do not apply to the app.
- On-device storage:everything you enter or save is stored only on your device, in the app's own storage: calculations, quotes, invoices, delivery notes (with the receiver's name and signature and any photo of the goods), weld procedure sheets, welder certificates (with their photos and dates), bend jobs, pipe offsets, photo markups, your company details and logo, your customer book, the bank details and pay link you add for invoices, the Workshop Board's jobs, crew, timesheets and drawings, your recent photo readings, and your unit and region preferences. None of it is uploaded, synced or shared, apart from your region and the app's language, which go with the usage data and the notification groups described below, a photo you choose to have read, two drawings you choose to compare, and the Goods In Count counts you choose to share (all below); deleting the app removes it.
- Camera and photos:the Photo Markup tool lets you take a photo or pick one from your library to add measurements and notes, and you can save the marked-up image to your camera roll or share it yourself. Quotes and invoices can include a logo you pick from your library. A job on the Jobs tab can hold photos you take or pick, and with Fabora Max a delivery note can hold a photo of the goods and a welder certificate a photo of the certificate; these are kept in the app's own storage on your device and removed with the record. The Colour Matcher reads a photo you take or choose; the photo stays on your device (in the web version, inside your web browser) and is not uploaded. The Digital Angle Finder uses the camera on your device. Use Pro on a computer uses the camera to read the sign-in code the web version shows on your computer screen; the picture is not saved or sent anywhere, and the app reads only the text inside the code. The app never scans, indexes or uploads your photo library, and only receives the single image you choose or capture. The only photos that leave your phone are the ones you send to be read and the Goods In Count counts you choose to share, described next.
- Reading a photo with AI (Fabora Max). Four Fabora Max tools read a photo with AI: Drawing Check (a photo or PDF of a drawing, read into a cut list), reading a parts list in Stock Cutting, Goods In Count (a delivery counted from a photo of the ends) and, from version 1.0.23, reading a drill's size in Drill Finder (the size stamped on a drill bit, read from a photo of it into the Size box). They are offered where Fabora Max is sold. Drawing Check is in the iPhone and Android apps and in the web version, where you choose a PDF or a photo on your computer. Reading a parts list, Goods In Count and reading a drill's size are in the phone apps only. The first time you open one (in Drill Finder, the first time you tap Read the size from a photo), it tells you the photo is sent to a third-party service to be read and asks you to agree; "Not now" sends nothing, and after that a photo is sent only when you ask for a reading. The photo goes to our own server, hosted by Vercel in London, with a random identifier for that tool on your phone or in your browser, the app's version, platform, language and region, and the app's anonymous RevenueCat identifier, so the server can check with RevenueCat that you have Fabora Max. Like any internet request, every photo the app sends to our server, and each comparison or shared count described below, also comes with your phone's or computer's IP address. Our server does not store it; Vercel, our host, may keep it for a short time in its request logs. The app removes the photo's location and other metadata first, and the server removes them again. For a PDF drawing, the server draws the page you choose as a picture and sends it back, keeping nothing. The server then sends only the picture and any close-ups, with a short instruction such as the language to answer in, to OpenAI to be read, and sends the reading back to your phone or browser. OpenAI never receives your identifier. It reads the photo for us under its API terms and data processing addendum, does not use it to train its models, may keep it for up to 30 days to detect abuse before deleting it, and handles it in the United States under the standard contractual clauses, with the UK Addendum, in that addendum, which you can ask us for. Fabora keeps no photo or reading from Fabora Max, unless you choose to share a Goods In Count count (below). To hold each subscriber to a monthly number of reads and a cost limit (100 reads in the UK, Ireland, the US, Canada, Australia and New Zealand, and fewer in some other countries, as the app shows before you subscribe), our server asks RevenueCat which country your subscription is paid in, or failing that where RevenueCat last saw the app, uses it only to set your limit and does not keep it, and records each read as a count with the date and its cost, filed under a one-way scrambled form of the app's identifier, and deletes each month's counts three months after the month ends. Your phone keeps your recent readings with their photos so you can look back at them (the last 30 drawings on a phone and the last 10 in a web browser, and the last 20 parts lists and counts; Drill Finder keeps no list of drill readings, as the size read goes into its Size box); deleting the app removes them. In the web version they are kept inside the browser's own storage on your computer, and clearing this site's data in the browser removes them. Most test builds we give our own testers through Apple's TestFlight carry these tools and others still being tested, and keep the photos, readings and corrections testers save privately in Vercel's storage in London to check and improve the tools; the people working on them may look at them, they are never published or sold, and they are deleted on request. The store version keeps nothing, also when it is tried out on TestFlight, unless you switch on sharing in Goods In Count. Please keep people, faces, number plates and your clients' names out of the photo, and check every reading before you cut, order or sign. The photo tools are for people aged 18 or over.
- Sharing your Goods In Count counts (only if you switch it on). Goods In Count is still learning, and says so under every count. If you switch on "Share my counts to help it learn" on the Goods In Count screen (it is off until you do; the switch says what goes, where, who may look and for how long, with a link to this policy), each count you check and save is sent in the background to our own server with the photo it was read from: the photo, with its location and other metadata removed by the app and again by the server; for each shape, its name, the size if there is one, how many, and where each dot sits on the photo after any you added or took away; whether you changed the count; the photo's width and height; when the count was made; whether the phone is set to metric or imperial units; a random identifier for the count (in TestFlight test builds, the identifier of the test reading, which includes that tool's random identifier for your phone); the app's version and whether it is the iPhone or Android app; and the app's anonymous RevenueCat identifier, so the server can check you have Fabora Max and file what you share under a one-way scrambled form of it (the identifier itself is not kept). Nothing is sent before you have checked and saved a count or while the switch is off, the order quantities you type stay on your phone, and a count that cannot be sent is not sent later. It is kept privately in our own storage, hosted by Vercel in London; the people working on Goods In Count may look at it; it is never sold, never published and never given to anyone else for their own use, and it is not sent to OpenAI or any other AI company for this. To check and train the counter we copy shared counts to Fabora's own computer; those copies follow the same rules, and before every check or training run we bring them in line with our storage, so a count deleted there, or two years old, is deleted from the copies too. We use it to check how well Goods In Count counts real deliveries, to improve it, and to train a counter of our own, which could one day count on your phone without sending the photo anywhere; a counter trained before you deleted your counts keeps what it learned from them, but holds no photo and no count. We keep each shared count for up to two years (each month's shares are deleted two years after the month it was shared began), or until you delete them: "Delete my shared photos" on the Goods In Count screen deletes everything that phone has shared at once and switches sharing off, and if Goods In Count is locked on your phone, because your Fabora Max has ended or is not sold in your phone's region, the same button, "Delete my shared Goods In Count photos", is in Settings, under Privacy. Switching sharing off stops anything more being sent, but what you already shared stays until you delete it, and the app says so. You can also ask us, with roughly when you counted and what, and we will find and delete them, or send you a copy. Deleting the app does not delete what you shared, so press Delete my shared photos first. TestFlight test builds already keep every count for testing, shared or not; there, Delete my shared photos deletes what you shared, and we delete the test copies when you ask. This relies on your consent, which you give with the switch and can withdraw at any time in the app.
- Comparing two drawings (Fabora Max). Compare drawings, which you open from Drawing Check with "Compare with an earlier version", finds the changes between two versions of a PDF drawing saved from CAD. Like Drawing Check, it is in the iPhone and Android apps where Fabora Max is sold, and its screen says where the drawings go before you pick them. Compare drawings is in the web version too, where you choose the two PDFs on your computer. When you ask for a comparison, the app sends each PDF you pick to our own server, hosted by Vercel in London: the whole file, every page in it (just the one file when you compare two pages of the same PDF), with which pages to compare, Drawing Check's random identifier for your phone or browser and the app's anonymous RevenueCat identifier, so the server can check with RevenueCat that you have Fabora Max. The server compares the drawings itself, from their own lines and words, and sends them to no other company, OpenAI included. It sends back a picture of each page and the list of changes, and keeps nothing: not the drawings, not the pictures and no count, so a comparison does not use any of your monthly reads. The pictures of the pages stay on your phone, or in the browser on your computer, only while the comparison is open (or, if the phone app is closed during a comparison, until you next open Compare), unless you export the report.
- Notifications:while a job timer runs, the app can show a notification on your lock screen with the running time and a Pause button, and with Fabora Max it can remind you before a welder certificate's next confirmation or retest. Both are created on your device. From version 1.0.19 the phone apps can also receive notifications from us: news of new tools and updates, and offers only if you switch "Offers and discounts" on (it is off until you do). Google's Firebase Cloud Messaging delivers them. For that, the app registers with Firebase, which gives this installation a random token: not your name, email or phone number, and nothing about your work. The app adds the token to a few groups, so a message can be aimed without us keeping any list of people: your region, the app's language, whether you have Pro, app news while it is on, and offers while you have them switched on. We send each message to groups, never to a person. On iPhone, news arrives quietly in Notification Centre until you allow alerts. Switch either kind off in the app (Settings, then Notifications) or in your phone's settings; deleting the app ends the token.
- Files you export(PDF and DXF, including invoices, delivery notes and weld procedure sheets) are created on your device and handed to your phone's share sheet, or with Save PDF or Save DXF on Android saved to a folder you pick; where they go next is your choice. DXF import, part of Fabora Max, reads only the one file you pick in your phone's file picker, on your device, and adds the parts it finds to your nest. The file stays on your phone and is not uploaded or sent anywhere.
- Anonymous usage data, from version 1.0.8, and you can switch it off. So we can see which tools are worth building on and where people get stuck, the app records a small fixed list of events: the app was opened; a tool screen was opened, and which tool, and, from version 1.0.20 (1.0.21 on Android), whether it was opened from the free tools suggested after you closed the subscription screen; the subscription screen was shown or closed, which locked tool led to it, and which version of the screen it was; a purchase or free trial was started, and which plan; a purchase or free trial completed; from version 1.0.15, a purchase or free trial that was cancelled at the store's checkout, and which plan, and one the store refused, with the plan and the store's error code and message (a billing response, never anything about you), and that a job was created on the Jobs tab or a job timer was started, only that each happened; and, from version 1.0.19, how the opening animation ended, which region was chosen on the first screen and whether it was changed, which tab was opened, that the app hit an error (where it was caught and whether it closed the app, never the message or what you were doing), the answer to the notifications question, and that a notification was opened, with the label we gave that message; and, from version 1.0.20 on iPhone and 1.0.21 on Android, the answer to the phone's own notifications question (Allow or Don't allow, and whether it came after Turn on or a switch in Settings), that a notifications switch in Settings was turned on or off (which one, and whether your phone allowed notifications at the time), that the ad measurement question was shown (and whether it was asked again because Meta was added) and how it was answered, from the question or the switch in Settings; and, from version 1.0.22, where notifications stand when the app starts (allowed, delivered quietly, blocked or not yet answered on your phone) and whether app news is switched on. That list does not grow without this policy changing. Alongside each event we record the app version, whether you use the iPhone, Android or web version, and your screen size. The same data and the same switch cover the web version, where the random identifier lives in your browser.
- Ad measurement, only if you allow it. On a new install, once the first screen is done, the app asks once whether it may tell TikTok and Meta (the company behind Facebook and Instagram) when you install the app, open it, and start a free trial or subscription. That shows us which of our TikTok, Facebook and Instagram ads bring people to the app. On iPhone, Apple's own tracking prompt then asks as well, and both have to say yes. Saying no, or closing the question, changes nothing else in the app, and one answer covers both companies. If you said yes before Meta was added (version 1.0.20 on iPhone, 1.0.21 on Android), the app asks once more; until you answer, TikTok carries on as you allowed and nothing goes to Meta. If you allow it, the app starts TikTok's App Events SDK and Meta's app events SDK. TikTok receives: that the app was installed, opened, or opened again on a later day; that a free trial or subscription started, with the plan's price and currency and the store's transaction number; and your phone's advertising ID (Google's on Android, Apple's on iPhone), on iPhone also Apple's identifier for apps from the same developer, a random identifier the SDK creates on your phone, your phone's model, system version and language, on Android its network type, its IP address, the time, and on Android the install referrer Google Play keeps (which ad or link led to the install). Meta receives: that the app was installed, opened, or opened again after more than a minute away, and on iPhone how long each visit lasted; the same trial and subscription details; and your phone's advertising ID, a random identifier the SDK creates on your phone, your phone's model, system version, language and time zone, its mobile network name, screen size and number of processor cores, the app's version, its IP address and the time, on Android also its total and free storage and, when the install came from a Meta ad, the install referrer Google Play keeps, on Android phones older than Android 11 that have the Facebook app the attribution identifier the Facebook app keeps, and a report if Meta's SDK itself fails. Never your name, your email, or anything you type or save in the app. The app does not let either SDK record which screens you open or what you tap or type, or read your store purchase history; for Meta it turns off automatic event logging, automatic matching of what you type, reading of button text, screen titles and screen layouts, and Meta's handling of the app's links. If you do not allow it, neither SDK is started and nothing goes to TikTok or Meta. Whatever you answer, the iPhone app tells Apple's SKAdNetwork once that it has been installed; if the install came from an ad, Apple itself tells that ad network, later and without any identifier. TikTok uses this data under its own privacy policy, and Meta under its own privacy policy and Business Tools Terms. Besides measuring our ads, TikTok and Meta also use it to choose who sees ads, ours and others', and to improve their own ad systems, under their own terms. For collecting and sending it to Meta, Fabora and Meta are jointly responsible (Meta Platforms, Inc. for people in the UK, Meta Platforms Ireland Limited in the European Union), and Meta may handle it in the United States. If you have a Facebook or Instagram account, Meta may connect this to it; you can see it and disconnect it under "Your activity off Meta technologies" in your Facebook or Instagram settings. To change your mind, open Settings in the app, find "Usage data", and switch "Ad measurement" off: sending to both stops straight away. On iPhone you can also turn tracking off for the app in the iPhone's Settings, under Privacy & Security, then Tracking, and on either phone you can reset or delete your advertising ID in its settings.
What the usage data never includes: your name, your email, your company, anything you type into a calculator, any dimension, material, price, quote, photo or file name, your street or precise location, and any advertising identifier from Apple or Google. Events are attached to a random identifier generated on your device, which is not linked to you and is not used to build a profile of you.
This is processed on our behalf by PostHog, on servers in the European Union. As with any internet request the server receives your IP address. It is used to work out which country you are in and is then discarded, never stored, and the finer location an IP can suggest, meaning your city, region, postcode, timezone and approximate coordinates, is deliberately deleted the moment the event arrives. Country is the level of detail we keep: an approximate location, which we use to see which countries the app is useful in. The app has no location permission and never asks where your phone is. None of it is used for advertising, sold, or combined with data from any other app or website.
To switch it off:open Settings in the app, find "Usage data", and turn off "Help improve the app". That stops collection immediately and it stays off. Because the events are anonymous we cannot tell which ones are yours, so we cannot retrieve or delete them individually; switching it off stops any further collection, and everything else the app holds is on your device, where deleting the app deletes it.
Apart from the anonymous usage data, the notifications registration, the ad measurement you can allow, the photos you choose to have read, the drawings you choose to compare, the Goods In Count counts you choose to share and the subscription flow in section 11, the app gathers nothing. The only tracking-permission prompt the iPhone app shows is Apple's, for ad measurement. It is a professional tool for people in the metal trades; its content is suitable for all ages, and the photo tools in Fabora Max are for people aged 18 or over. Questions about the app's privacy? Email us at info@faboraplatform.com.
11. Fabora Pro and Fabora Max subscriptions in the app
Fabora Steel Tools offers two optional paid subscriptions, bought through Apple's App Store or Google Play: Fabora Pro, and Fabora Max, which includes everything in Pro and is sold in some countries only: the UK, Ireland, the US, Canada, Australia and New Zealand, and in the phone apps in 46 more countries; the app shows whether it is sold where you are. From version 1.0.23 the phone apps read the country of your App Store or Google Play account, on the phone, to decide whether Max and each of its tools is offered there; the app does not save it or send it to us. Payment is taken by Apple or Google, not by us. We never see your card details.
To unlock your subscription across reinstalls and devices, the app uses RevenueCat, a subscription management service. RevenueCat processes your purchase history for this app, a randomly generated anonymous user ID, and basic device information needed to validate purchases. This identifier is not your name, email address or Apple or Google account, and we do not link it to you, with two exceptions: a phone code from a web subscription, described below, links the phone to that subscription, and our server files the Fabora Max read counts and the Goods In Count counts you choose to share under a one-way scrambled form of it (section 10). With Fabora Max, the same identifier goes to our server with each photo you send to be read, each pair of drawings you compare and each count you share, so it can check with RevenueCat that Max is active and, for a read, which country the subscription is paid in, to set your monthly reads.
This information is used only for these things: starting your free trial, unlocking Pro or Max features, moving you from Pro to Max, checking Max before a photo is read, two drawings are compared or a count is shared, restoring purchases, handling renewals and refunds, comparing versions of the subscription screen (described next), and, in its scrambled form, keeping the Fabora Max read counts and filing the Goods In Count counts you choose to share, so that Delete my shared photos, which sends the same identifier, can find and delete them. To compare versions of the subscription screen, RevenueCat may show different people different versions, and when one of those screens opens the app tells RevenueCat it was shown, with the same anonymous identifier; switching usage data off in Settings stops that too. It is not used for advertising, it is not used to track you across other apps or websites, and it is never sold.
RevenueCat's own privacy policy is at revenuecat.com/privacy. You can manage or cancel your subscription at any time in your App Store or Google Play account settings.
On the web version of Steel Tools, checkout is handled by RevenueCat and Stripe using the email address you give at checkout, and your access is tied to the browser you bought it in. To use it in another browser, Settings in that browser gives you a restore link, which carries the anonymous RevenueCat identifier your subscription belongs to, so keep it private: opening it makes any browser use your subscription. You can also paste the Manage subscription link from RevenueCat's receipt email into Restore a subscription; the browser then sends that link to our restore service, hosted by Vercel, which asks RevenueCat which identifier it belongs to and stores nothing. A web subscription also comes with one phone code for the Android app. The web version asks our phone code service, hosted by Vercel, for it, and RevenueCat keeps it with your web subscription. When an Android phone redeems it, that phone's anonymous identifier is recorded against your web subscription, so Pro on the phone, or Pro and Max for a Fabora Max web subscription, renews and ends with it, and RevenueCat tells our service when the web subscription renews. From version 1.0.20 the iPhone app has no code entry: if you bought on the web and use an iPhone, email us at info@faboraplatform.com and we will send you an App Store code, which you redeem in the App Store. If you enter an access code in the Android app or the web version, it sends that code and its anonymous RevenueCat identifier to our redeem service, hosted by Vercel, so the code can be honoured on one device. Nothing else is sent, and nothing about you is stored there.
From version 1.0.16 you can use a subscription bought in the app on your computer. The web version shows a sign-in code; when you scan it with Use Pro on a computer, the app sends its anonymous RevenueCat identifier and the scanned code to our sign-in service, hosted by Vercel. The service checks with RevenueCat that your subscription is active and hands the identifier to that browser, which then uses the same subscription. The browser proves it showed the code with a secret that never leaves it, so a photo of the code is not enough to collect anything. The link is kept with RevenueCat, can only be collected within ten minutes, and is deleted when the browser collects it. Nothing else is sent.
On iPhone, when the app opens, RevenueCat collects Apple's ad attribution token, which iOS makes on your phone, and asks Apple whether the install came from one of our Apple Ads adverts and from which campaign, so we can see which of our Apple Ads lead to subscriptions. Apple's answer names the campaign, not you, and this is not tracking across other companies' apps.
12. The LEV Ready app
LEV Ready is our record keeping service for local exhaust ventilation, used on the web at lev.faboraplatform.co.uk and through the LEV Ready phone app. It works differently from Steel Tools: it keeps your records for you, so it needs an account and it stores what you enter on our servers.
- What we store: your name, email address and workspace name; your sites, areas and extraction assets; routine check, service and thorough examination records; corrective actions; and any photos and documents you attach to them.
- Where it is stored: in the European Union. Records sit in a database hosted by Render in Frankfurt, and the files you upload sit in Cloudflare R2 storage under its EU jurisdiction. Account and reminder emails go out through Resend. Those three companies process the data for us under contract, and for nothing else.
- Camera and photos: the app uses your camera only to scan the QR labels you print for your own assets, and to take photos you choose to attach to a record. It never scans, indexes or uploads your photo library.
- Your team:a workspace owner can add colleagues as users. Everyone in a workspace can see that workspace's records, which is the point of it. Nobody outside it can.
- No adverts, no tracking.The app carries no advertising and no advertising identifier, and nothing is sold or shared for anyone else's purposes. So we can see which parts of LEV Ready get used, our server records a few steps, such as a workspace being created or a check being recorded, with PostHog, an analytics service, on its servers in the EU. Those records carry a random workspace ID and no names, email addresses, record contents or device details, and nothing is stored on your device for it.
- Paid plans:these are bought on the web version only, through Stripe. There is no purchasing inside the phone app, and we never see your card details. So we can follow how LEV Ready is doing, each subscription is also recorded with RevenueCat, a subscription management service: we send it a random workspace ID and the Stripe subscription reference, and it reads the plan, trial, payments and any cancellation from Stripe. It never receives the records you keep in LEV Ready. RevenueCat's own privacy policy is at revenuecat.com/privacy.
- How long we keep it: for as long as your workspace exists, because the records are the point of the service. Thorough examination records in particular are ones you may need to produce for several years. When you delete your account, see below, we delete them.
Deleting your LEV Ready account
You can delete your account yourself at any time. Sign in, open the Account page (in the phone app that is the Account tab) and use Delete account. It removes your user record, and where you are the only owner of a workspace it removes that workspace too, with its sites, areas, assets, check, service and examination records, corrective actions, photos and documents. The confirmation step tells you which of those will happen before you commit, and any paid plan on the workspace is cancelled at the same time. Deletion cannot be undone.
If you would rather we did it for you, email info@faboraplatform.com from the address on the account and we will delete it within 30 days.
13. The Fabora RAMS app
Fabora RAMS is our risk assessment and method statement (RAMS) service, used on the web at app.faboraplatform.co.uk and through the Fabora RAMS app for iPhone, iPad and Android. Like LEV Ready, it keeps your records for you, so it needs an account and it stores what you enter on our servers. A company account is created when a company signs up on faboraplatform.com or, from version 1.1 of the app, in the app itself: you give your company name, your name and your email address, and we email you a 6-digit code to check the address.
- What we store: your email address, and your password as a one-way scrambled code (a hash), never the password itself. Your company details as they appear on your RAMS: company name, the signatory or contact name, address, postcode, phone, email, website, company registration and VAT numbers, and your logo if you upload one. The RAMS you write, including job and site details, method steps, hazards and risk scores, PPE, COSHH items and the names, roles and phone numbers of the operatives on the job, and the PDFs you issue. Your libraries of customers (with their sites and contacts), operatives, equipment, hazards, PPE, method steps and COSHH items. When your company signs up on faboraplatform.com, the website sends us your company name, email address and name so we can create the account and send your welcome email, and, if you told us, how you heard about us. When you create an account in the app, we keep what you typed into the sign-up form, a scrambled copy of the code we emailed and the network address the request came from, to finish the sign-up and stop the form being misused. We delete them once they are 2 days old, when the sign-up form is next used.
- People you add: when you add operatives, customer contacts or RAMS authors, your company decides what goes in and is responsible for telling those people. We store it for you and use it for nothing else.
- Activity in your account: we record a short list of events against your account in our own database: when you sign in, finish setting up your company, open the RAMS builder, save a new RAMS, issue a PDF or open checkout on the web, and your answer if you reply to the one-question prompt we show accounts that have not made a RAMS yet. We use them to see where people get stuck. Separately, we count the PDFs issued each month where a plan has a monthly limit. No analytics company receives any of it.
- Signing in: sign-in codes and password links are emailed to you. A sign-in code works once, for 10 minutes, and we keep only a scrambled copy of it. You can also sign the phone app in by scanning a code shown on your computer while you are signed in there: that code works once, for 2 minutes, and we keep only a scrambled copy of it too. The app keeps you signed in with a cookie, the same way a web browser does, until you have not used it for 90 days.
- Marketing emails, only if you ask for them:when you create an account in the app there is a box, unticked to start with, that reads "Email me occasional tips and offers from Fabora. You can unsubscribe at any time." If you tick it, or later switch on Emails from Fabora in Company Settings, we may email you now and then about Fabora's products at the email address on your account. We keep a record of when you agreed, where, and the exact words you saw, and of when you switched it off. Switch it off at any time in Company Settings (in the phone app, the Account tab) or with the unsubscribe link in any marketing email, and we stop. Sign-in codes and other account emails are not marketing and still come.
- Where it is stored:in the European Union. Records and issued PDFs sit in a database hosted by Render in Frankfurt, Germany, and uploaded logos in Render's storage in the same place. Account emails, such as sign-in codes and password links, and marketing emails if you asked for them, go out through our email provider. These companies process the data for us under contract, and for nothing else.
- Ask Fabora: in the phone app, Ask Fabora, the help assistant, answers from our own help articles only and sends nothing to anyone else. On the web it can use OpenAI to write its answers. When it does, we send OpenAI the question you type, the last few messages in the same help panel, the name of the screen you asked from and extracts from our help articles. We do not send your name, email address, company or your RAMS, but anything you type into a question goes with it, so please leave personal details out. OpenAI is a US company and handles this outside the UK and the EU.
- On your phone:every PDF you export or print in the app is also saved on the phone, in the Issued tab, so it opens with no signal. Those copies stay on the phone until you remove them there or delete the app; deleting your account cannot reach them. App lock uses your phone's own Face ID, Touch ID, fingerprint or passcode check, and we never receive any biometric data. The app also remembers, on the phone, your light or dark theme and whether you last chose a site or workshop RAMS.
- Camera: the app uses your camera only to scan the sign-in code on your computer, and to take a photo when you choose Take Photo to add your company logo. A scan is read on the phone: the picture is never kept or sent, only the code it finds is used to sign you in. A logo photo is uploaded as your logo.
- App updates:when the app opens it asks Expo, the service we use to deliver updates to the app, whether a newer version of the app's code is ready. That request carries a random code the app creates when it is installed, the app's version and whether the phone runs iOS or Android. It is not linked to your account.
- Your team and share links:everyone signed in to your company's account sees the same RAMS and libraries, and nobody outside it can, unless you send them a share link. A share link opens that RAMS as a PDF for anyone who has the link, without an account, until the link expires.
- No adverts, no tracking.The app carries no advertising, no advertising identifier, and no third-party analytics or crash reporting. Nothing is sold, and nothing is shared for anyone else's purposes.
- Paid plans:on the web, Fabora RAMS Pro is bought on faboraplatform.com through Stripe. In the app, from version 1.1, it is bought through Apple's App Store or Google Play as a monthly subscription that starts with a 7-day free trial, and Apple or Google takes the payment. We never see your card details either way. For subscriptions bought in the app we use RevenueCat, a US company that runs in-app subscriptions for us: it receives the purchase from Apple or Google, a code that stands for your company account (not your name), and the email address and company name on the account, so a subscription unlocks the right account and we can help if a purchase goes wrong. RevenueCat handles this outside the UK and the EU, for us and for nothing else; its privacy policy is at revenuecat.com/privacy. Fabora RAMS keeps your plan, the status of your subscription, where it was bought, and Stripe's or the store's reference numbers for it.
- Technical logs: our hosting provider keeps short-lived logs of requests to the service, such as the time, the page asked for, and the network address and browser or app that asked, so we can keep it running and secure.
- Why we use it: to provide the service your company signed up for, and, for the activity events and technical logs, our legitimate interest in keeping the service working, secure and useful. Marketing emails rely on your consent, which you can withdraw at any time.
- How long we keep it:for as long as your company's account exists, because the records are the point of the service and you may need to show an old RAMS long after the job. Sign-in and sign-up codes expire after 10 minutes and password links after 2 hours (72 hours for a new account's setup link). When you delete your account, see below, we delete the rest. Deleted records can stay in our hosting provider's backups for a short time before they are overwritten.
Deleting your Fabora RAMS account
You can delete your company's account yourself at any time. Sign in as the company's admin, open Company Settings (in the phone app, the Account tab), go to Delete this company account, type DELETE and confirm. That deletes the company and every user on it, all of its RAMS and issued PDFs, its libraries, its activity events and its logo, straight away, and any share links you sent stop working. It cannot be undone. If the company pays through Stripe on the web, deleting the account sends us a notice and we cancel the subscription in Stripe. A subscription bought in the app through Apple or Google is not cancelled by deleting the account: cancel it first in your App Store or Google Play subscriptions, as the app reminds you, or the store keeps charging. PDFs already saved in a phone's Issued tab stay on that phone until you remove them there or delete the app.
If you cannot sign in, or you are not your company's admin, email info@faboraplatform.com from the address on the account and we will delete it within 30 days. We keep the deletion notice (the company name, the admin's email address and Stripe's reference numbers) with our billing records.
14. Updates
If the website, the contact form, the cookies or the providers above change, we'll update this page and change the date at the top.

