Legal
Privacy Policy
Effective date: UNAVAILABLE (to be published).
Page last edited 2026-09-21.
This text is a draft. It has not been reviewed by counsel, so it is not a final policy and not an asserted legal position. The section further down describes what this preview build actually stores and contacts.
Information We Collect
This preview collects what you type into its forms: your name, email address and the message or other fields each form shows. If you sign up, it also stores your account (email address, optional name and a protected form of your password) and signs you in with a session cookie. What else it stores or receives is listed in the section below.
How We Use Your Information
Purposes of use: UNAVAILABLE until the operator publishes them.
Pooled outcome records. If you choose to pool a project, Ferrum stores banded estimate-versus-actual figures for it (district, building class, size band, quarter, planned and actual per line and stage). They hold no name, plot, date, team or supplier. Nothing from pooled records is shown to anyone until enough consented projects exist, and then only as grouped figures. You can withdraw in Manage; the records are deleted at once. DRAFT PENDING COUNSEL REVIEW.
Data Security
Security statement: UNAVAILABLE until the operator publishes it.
Microphone / voice input
Where: the SUTRA AI dock and the start page composer have a Speak control. The microphone is used only while you have pressed it, for one spoken sentence at a time. There is no wake word and nothing listens in the background.
Data items: (1) your voice audio while Speak is on, (2) the transcript text, (3) a recogniser confidence number. Purpose: to turn what you say into text so you can edit your plan by speaking. The first time you use voice input on a device you are shown a notice in English or Hindi and must click Allow voice; the choice is recorded on your device (key ferrum-sutra-voice-consent) as a list of consent and withdrawal events, and withdrawing adds an event: it never deletes the record.
Who processes the audio: your browser. It sends the audio to its own speech service to turn it into text (Chrome and Edge use Google's service; Safari uses Apple's). Ferrum OS does not receive the audio and does not record it. How long the browser vendor keeps audio is the vendor's statement: UNAVAILABLE here.
What Ferrum OS receives: the text of what was heard, treated like text you typed. A confidence number from the browser is used on your device only, to decide whether a spoken “apply” is clear enough to count; it is not sent or stored. A spoken change to your plan is always shown first and applied only after you say or press Apply.
If you prefer not to use it: do not press Speak; typing the same words works the same way. You can also block the microphone for this site in your browser settings.
Retention: audio, none at Ferrum OS. Transcripts follow the rules for chat messages you type. The confidence number is not kept. Rights and complaints: data rights page (access, correction, erasure, including transcripts), the grievance page, then the Data Protection Board of India. Grievance Officer: Sharief · PLACEHOLDER (operator to supply) · PLACEHOLDER (operator to supply).
DRAFT PENDING COUNSEL REVIEW. The consent notice and the data-protection wording for audio are not final.
What this preview site actually stores and contacts
Derived from the code of this preview build, checked on 2026-10-19 against commit c5fa97b9e. Entries marked "Seen on build 981a13d2" were also observed in a real browser on the deployed build of that name; the others come from the code only. This section describes what the code does today. It is not a legal statement, and it will be out of date when the code changes.
Accounts
You can create an account on /signup and sign in on /login. Signing up stores an account record and signs you in with the ferrum_session cookie; both are described below under "Sign-in" and "Forms that store what you type". No verification or password-reset email is sent while no mail service is set up. /account shows your account and lets you sign out, which ends the session. Using the rest of the preview needs no account.
Stored in your browser
This site writes the keys below to your browser storage. The values stay in your browser, and the tools may use them when they make the requests listed further down. If your browser blocks storage, values are kept in memory for the page session only. Clearing site data removes them. The site itself removes a key only where its row says so; there is no "erase everything" control, and signing out removes nothing from this browser.
Interface and preference flags
ferrum-cookie-consentlocalStorage- "accepted" after you press "Got it" on the cookie bar.Seen on build 981a13d2
ferrum-preview-sessionlocalStorage- "active" once you open a product cockpit or the workspace. It is a preview flag only; it is not an account or a sign-in.Seen on build 981a13d2
ferrum-sutra-dock-statelocalStorage- Whether the SUTRA panel is minimised or open.Seen on build 981a13d2
ferrum-area-unitlocalStorage- Your area-unit preference.From the code only
ferrum-user-settings-v1localStorage- Your workflow settings: auto-save choice, start-up choice, display and workflow preferences, SUTRA AI switches. No project data.From the code only
ferrum.role-step.v1localStorage- Three yes or no notes about the work-view step: whether you skipped it, whether it was offered once more at your first Save, and whether you switched on Show all tools. No role name and no personal data. Account, Delete my role data resets it.From the code only
ferrum.design.v1localStorage- Saves your look settings on this device.From the code only
ferrum.termsAcceptedlocalStorage- Saves that you accepted the Terms, and which version, on this device.From the code only
ferrum.field.enabledlocalStorage- Whether the phone field app (attendance, pay records, outbox; device-only TEST MODE) is switched on in this browser; "1" is written when you open the address with field=1 and removed with field=0.From the code only
ferrum.field.densitylocalStorage- Whether the phone field app shows its list or its table layout; written when you change it.From the code only
ferrum-cockpit-view-v1localStorage- The model view (3D space, Plan, Front or Side) you last chose on a product cockpit, one entry per product; written only when you pick a view.From the code only
ferrum-map-view-v1localStorage- "2d" or "3d": the LandIntel parcel-map view you last chose; written only when you press "2D plan" or "3D context".From the code only
ferrum-build:package-filter:v1:<project>localStorage- Which packages (or All packages) you last chose to show on the execution tabs of a project (Site, Quality, Issues), one entry per project on this device. Written when you pick a package; removed when you pick All packages. No project data.From the code only
ferrum-facade-recent-v1localStorage- The catalogue ids of the last 8 wall materials you picked in the elevation Materials palette. Written when you pick a material. No project data.From the code only
ferrum-facade-favourites-v1localStorage- The catalogue ids of the wall materials you marked as favourites in the elevation Materials palette. Written when you add or remove a favourite. No project data.From the code only
ferrum-product-docks:v1:<scope>localStorage- Which dock tab each product had open in the cockpit (or that none was open), so it comes back when you return to that product. Layout only; no project data.From the code only
ferrum.beta-ribbon.dismissedlocalStorage- "1" after you close the Beta notice at the top of the page, so it stays closed on this device.From the code only
ferrum.view.choicelocalStorage- Only if you chose Desktop view or Phone view: "desktop" or "phone", so this device keeps your choice. Removed when you choose Use automatic. Read only by this browser. Nothing is sent.From the code only
ferrum.structura.drawn.autosave.v1.p.<project>localStorage- The structural model you are drawing in the Structura workspace, as you entered it, saved automatically on this device, one entry per project.From the code only
ferrum.structura.drawn.saved.v1.p.<project>localStorage- The structural models you saved by name in the Structura workspace, one list per project on this device.From the code only
ferrum.structura.livelocalStorage- Never written by this site. A developer switch that is read only in development builds; the live site does not read it.From the code only
ferrum-workspace-fullscreen-pendinglocalStorage- "true" while a full-screen request is pending; removed afterwards.From the code only
ferrum:workspace-panel-layout:v1:<product>localStorage- Panel widths, side and collapsed state for each product cockpit (one key per product).Seen on build 981a13d2
ferrum-design-engine:v1:<project>sessionStorage- The figures you typed on the design engine and the layouts it found, with your edits, so a reload on the phone view comes back to the same screen; written only by the phone view of the design engine, one entry per project, cleared when the tab closes. It never leaves this device.From the code only
ferrum-3d-wall-modelsessionStorage- "on" or "off" for the 3D wall-model toggle; cleared when the tab closes.Seen on build 981a13d2
ferrum-sutra-voice-notice-seenlocalStorage- Whether you have already been shown the one-time voice-input notice (see "Microphone / voice input" below).From the code only
ferrum-sutra-voice-consentlocalStorage- Only if voice-input consent is switched on and you use it: a list of your voice consent and withdrawal events on this device (granted or withdrawn, notice version and language, browser speech service named, browser family, time). Withdrawing adds an event and never deletes the earlier ones. No audio, no transcript text and no address is stored here, and nothing is sent.From the code only
ferrum.notice.once.v1:<notice>:<site>localStorage- Only on a phone, only after you close or answer a one-time note shown over the canvas (for example the question about a brief that differs from the plot): that you did, the time you did it, and which note and which site it was, so the note is not shown again on this device. No text of the note, no plot size, no name and no account number. Nothing is sent. Clearing this site's data removes it.From the code only
ferrum.designShell.tools.v1localStorage- Whether you left the Tools ribbon open or collapsed in the product cockpit on a desktop screen: the word open or closed. Written only when you press the Tools button. No project data. Nothing is sent. Clearing this site's data removes it.From the code only
ferrum.pricing.betaCard.closed.v1localStorage- Only if you close the Beta prices note on the pricing page: the digit 1 on this device, so the note stays closed. No name, no choice of plan and no account number. Nothing is sent. Clearing this site's data removes it.From the code only
ferrum:workspace-layout:v2:ribbon-cockpitlocalStorage- Where the SUTRA AI conversation, Properties, Project browser and Tools docks sit in the product cockpit and how wide each is (slot, order, width and collapsed state per dock). Written every time you move, resize, collapse or reset a dock on a product cockpit page while no local project is open; with a project open the same information goes to the ferrum-cockpit-legacy-docking key for that project instead. Not removed by "Reset layout".From the code only
ferrum-panel-layout:v1:<project id or local>:<desktop or phone>localStorage- The SUTRA AI panel layout you arranged in the product cockpit: which panels are open, grouped, collapsed or closed and their sizes, one key per local project (a random id made in this browser) and per desktop or phone mode. Only the layout itself is stored (no project, drawing, conversation or site data). Written when you change the layout, and once automatically when an older dock arrangement is carried over. "Reset layout" in the panel rail removes this project's key or all of them.From the code only
ferrum-cockpit-legacy-docking:v1:<desktop or phone>localStorage- The word true or false: whether the cockpit still shows the older dock arrangement for that mode. Set automatically when an older arrangement is found and carried over, and set to false when you use "Reset layout". Nothing removes it.From the code only
ferrum-cockpit-legacy-docking:v1:<panel layout key>localStorage- The same true or false flag for one local project (the panel layout key is part of this key). Nothing removes it.From the code only
ferrum-cockpit-legacy-docking:v1:<panel layout key>:placementslocalStorage- Dock positions and widths for one local project (slot, order, width and collapsed state per dock), written when you move or resize a dock while that project is open. Removed when you "Reset layout" for that project, provided the browser accepted the flag write that goes with it.From the code only
ferrum-cockpit-legacy-docking:v1:migration-disabledlocalStorage- The word true: do not carry an older dock arrangement over again. Written when you confirm "Reset all layouts". Nothing removes it.From the code only
ferrum:ribbon-layout-presets:v1localStorage- Up to 8 cockpit layouts you saved under a name you typed: the dock positions and widths and, since the panel workspace, the full panel layout and docking flag for desktop and phone. Written when you save or delete a named layout. Not removed by "Reset layout".From the code only
ferrum-cockpit-view-mode:v1localStorage- Whether you minimised the cockpit canvas.From the code only
ferrum-ribbon-cockpit:theme:v1localStorage- "light" or "dark": the cockpit theme you chose.From the code only
ferrum-ribbon-cockpit:site-map:v1localStorage- Whether the site map panel is collapsed and where it is placed.From the code only
ferrum:ribbon-quick-access:v1localStorage- Up to five ribbon features you pinned for quick access, per product (references only).From the code only
ferrum-cockpit-site-choice-v1localStorage- Your last answer in the "New tab or Replace" site dialog and whether to keep asking.From the code only
ferrum-cockpit-site-message-v1localStorage- In browsers without cross-tab messaging only: the last site saved from another tab (the pending site with its parcel) and a time, so the other tab can pick it up.From the code only
ferrum-nearby-context-v1localStorage- Whether you turned "Show nearby buildings and roads" on, and when.From the code only
ferrum-default-location-v1localStorage- How you answered the first-run "use my location" step (granted, dismissed, denied, unavailable or timed out) and when; never a position.From the code only
ferrum.analysis.assumptionReviews.v1localStorage- Which flagged assumptions you marked reviewed or dismissed, and when. Removed when you clear the last mark.From the code only
ferrum-cockpit-sites-owner-v1localStorage- The account id (or "anon") that the sites saved on this device belong to, so a shared device does not show one account's sites to another. Written when a cockpit opens after the sign-in check.From the code only
ferrum-designstudio-baseline-origin:v1localStorage- A small marker (the word baseline, the site key of the plot and the id of the layout, for example a Create layouts or Library choice) saying that the plan on this device was opened from a layout, so a reload knows where the design came from. No name or contact detail is stored. It is removed when you replace or clear the plan or clear this browser's data. FOR COUNSEL TO CONFIRM.Seen on build 981a13d2
Work you enter or open (kept only in this browser)
ferrum-project-state-v1localStorage- Workspace project parameters (plot width and depth, setback, floors), opening edits and wall offsets, with a revision number and time. When a layout from Create layouts is used as the plan, the record also names it as baseline.confirmedBy (and, one level deep, baseline.replaced.baseline.confirmedBy): for a guest this is the neutral label "This browser", never a typed name; for a signed-in person it is the name you typed. It stays until the plan is replaced, you clear the plan or you clear this browser's data. FOR COUNSEL TO CONFIRM.Seen on build 981a13d2
ferrum-parcel-context-v1localStorage- The active parcel: ULPIN, state, district, area, land use, the coordinates you entered or picked, how they were established, and provenance.Seen on build 981a13d2
ferrum-data-capture-v1localStorage- Only if the optional choice to pool a project's banded outcome figures is available and you make it: per project, whether you chose it, which wording version you saw, when, and the banded records (district, building class, size band, quarter, planned and actual per line group; no name, plot, date, team or supplier). Withdrawing deletes the project's records and keeps only the withdrawn status and time. Kept in this browser only; nothing is sent.From the code only
ferrum-cockpit-handofflocalStorage- Product parameters handed from a product page to the cockpit.Seen on build 981a13d2
ferrum.startIntent/v1localStorage- Your answers to the start questionnaire: the goal you picked (a purpose group and a product), what you said about it (the kind of building, the plot question or the kind of file you have) and your preferred units (metres or feet), with the time they were written. Answers saved by earlier versions may also hold a stage and a role. Never a file, a file name, file contents or a location. Written when you press the button that takes you on from the confirm screen (the units are also written when you tap the m / ft toggle); removed when you press "Forget my answers" on that screen, which keeps only your units. Read only by this browser, to preselect your answers on your next visit and to show your remembered goal on the project launcher; never sent anywhere.From the code only
ferrum.startComposer/v1sessionStorage- Only between pressing Start on the start page and the workspace opening your new project, and for at most ten minutes: the project name made from what you typed or chose, and the project details made from it (your sentence, a place name or the PIN code exactly as you typed it, plot size, budget, who, and the units). Written when you press Start on a destination that opens a new project; removed as soon as the workspace creates that project, and whenever the start page is opened again. It exists because a link can turn into a full page load on a slow connection, which would otherwise lose your answers. Kept in this tab only, never sent anywhere.From the code only
ferrum.homeStart/v1sessionStorage- Only between pressing "More choices" on the home page start form and the start page opening, and for at most ten minutes: the sentence you typed, the choices you made (need, place, plot size) and the units, so the start page can show them. Written only when the form holds something; removed as soon as the start page takes it. Kept in this tab only, never sent anywhere.From the code only
ferrum.startComposer.ticket/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on, and for at most ten minutes: a random one-use number, which identity the text was typed under (guest, a signed-in account number, or "unknown"), a short fingerprint of the text so a swap is noticed, and when it expires. Written when you press Start; removed when the workspace takes it or you discard it. Kept in this tab only, never sent anywhere.From the code only
ferrum.startComposer.consumed/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on: the random numbers (at most 64, no text) of hand-offs already used or discarded in this tab, so a duplicated tab cannot use one twice. Kept in this tab only, never sent anywhere; it ends when the tab closes.From the code only
ferrum.startComposer.fence/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on: one small counter that goes up each time the signed-in identity of this tab changes, so a hand-off from before the change cannot be used after a reload. No text, no account number. Kept in this tab only, never sent anywhere.From the code only
ferrum.startComposer.typing/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on: which identity (guest, a signed-in account number, or "unknown") your start-page text was last typed under, and a short fingerprint of that text, so the workspace only accepts it for the same identity. Removed with the hand-off. Kept in this tab only, never sent anywhere.From the code only
ferrum.startComposer.claim/v1localStorage- Only while the temporary start-page draft hand-off is switched on: the random numbers (at most 64, no text, no account number) of hand-offs already used in this browser, so a duplicated or second tab cannot use the same one twice. Written when the workspace takes a hand-off. Read only by this browser, never sent anywhere. Clearing this site's data removes it.From the code only
ferrum.startComposer.observed/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on: which identity (guest, a signed-in account number, or "unknown") this tab last saw confirmed, so a reload under the same identity does not discard a valid hand-off. No text. Kept in this tab only, never sent anywhere; it ends when the tab closes.From the code only
ferrum.startComposer.edit/v1sessionStorage- Only while the temporary start-page draft hand-off is switched on: which identity (guest, a signed-in account number, or "unknown") you were using the last time you edited the start-page text. No text. Removed when the hand-off is used or discarded. Kept in this tab only, never sent anywhere; it ends when the tab closes.From the code only
ferrum.newProjectEntry/v1localStorage- Only while a trial of the new start page is running: which version of the start page this browser was given ("legacy" or "c"), a number from 0 to 9999 worked out from a random value made on this device (the random value itself is not kept) and the day it was given, so you always see the same version. Written the first time you open /start during a trial; nothing is written while no trial runs. Never sent anywhere. Nothing removes it; clearing this site's data does. Read only by this browser.From the code only
ferrum.flowc.metrics/v1localStorage- Counts for the new start page on this device, kept only when your browser sends neither Do Not Track nor Global Privacy Control: how many visits reached each of its screens, the seconds to the first plan, the number of taps, how many characters were typed and whether the plot size was left unknown (up to the last 200 values of each). No text you typed, no location, no account or device id. Written as you use the new start page; never sent anywhere. Nothing removes it; clearing this site's data does. Read only by this browser.From the code only
ferrum.phoneNative/v1localStorage- Only while a trial of the new phone screens is running: which version of the phone screens this browser was given ("native" or "control"), a number from 0 to 9999 worked out from a random value made on this device (the random value itself is not kept) and the day it was given, so a phone always shows the same version. Written the first time a phone opens the cockpit during a trial; nothing is written on a computer, while the phone screens are switched off, or while no trial runs. A web address ending ?phone=native or ?phone=desktop shows one version for that visit only and writes nothing. The key itself is never sent. The anonymous trial counts (share of the screen the drawing fills, taps before the first edit, Back presses, error kinds) are held in page memory and carry only fixed words and the word native or control. They are not sent anywhere: their upload switch is off. Nothing is counted when your browser sends Do Not Track or Global Privacy Control. Nothing removes this key; clearing this site's data does. Read only by this browser.From the code only
ferrum-boq-revision-history-v1localStorage- The BOQ take-off revision history.From the code only
ferrum-designstudio-spaces-boq-v1localStorage- The facade, interior-finish and open-area quantity lines you chose to send from DesignStudio Spaces to the BOQ take-off (material ids and areas, no prices), with the plan fingerprint.From the code only
ferrum-designstudio-spaces-selections-v1localStorage- Your DesignStudio Spaces choices per project on this device (facade, room finish and open-area material ids, and the open-area zones you entered; no prices), so they survive closing the tab. Off by default and not used for guests: nothing is read or written unless a signed-in account turns it on later.From the code only
ferrum.imported-revisions.v1localStorage- Drawings you import as a hand-authored revision (DXF): its label, the file name, size and SHA-256 fingerprint, the import time, the units read from the file, the room outlines and areas read from it, outline counts, what was not mapped, and whether you marked it as an example.From the code only
ferrum-downstream-recorded-revision-v1localStorage- A recorded revision id and time, the governing span and a pass flag.Seen on build 981a13d2
ferrum-frozen-plans-v1localStorage- Up to 20 frozen (locked) versions of your plan you have explicitly confirmed, each with its inputs, derived geometry, metrics and a fingerprint; kept so the plan can be read back exactly as it was frozen, and so you can unfreeze a version to revise it.From the code only
ferrum-project-record-v1localStorage- One local project identity (an id, a revision number and a short change log) referencing your parcel and plan records; created on first use, or adopted from a parcel/plan already saved in this browser before this feature existed. Not synced to an account or other devices.From the code only
ferrum-independent-plan-draft:v2localStorage- The version 2 form of the independent drawing draft for the active project (project id, source case, plan revisions with authored heights in metres and feet; up to 4,000,000 characters); swapped with the project, and written only once version 2 saving is switched on.From the code only
ferrum-build-mediaIndexedDB- Photos you capture or pick in the Ferrum Build photo tool, kept on this device: each photo's record (project, package, what it is attached to, who took it, when, and a location only if the project turned location on), a compressed copy and a thumbnail. The original file, which can carry camera details and location, is held only until it is compressed and is then deleted; the compressed copy is re-encoded without that metadata. Photo storage is not connected yet, so nothing uploads and photos stay here until you choose "Remove from this device".From the code only
ferrum-declared-region-v1localStorage- The region you set in the header Region control: a two-letter country code, an optional state/subdivision code, and whether you typed it or it came from "Use my location". Never coordinates. Written only after you set a region (the no-prompt guess from your device time zone and languages is not stored). Removed when you press "Forget saved region" or clear both fields.From the code only
ferrum-site-analysis-v1localStorage- Site observations you enter per parcel (topic, basis, confidence, date, the observer name you type, source and note) and the reviewer entry.From the code only
ferrum-map-composer-metadata-v1localStorage- Map title, purpose, CRS, author, issue date, revision and layer list.Seen on build 981a13d2
ferrum-concierge-feedback-v1localStorage- Up to 200 entries: your SUTRA query, the answer, useful or not useful, and an optional correction.Seen on build 981a13d2
boqProEstimatelocalStorage- The materials list of the /boq-pro take-off tool. The phone BOQ page also writes and removes the same key.Seen on build 981a13d2
boqProjectKindlocalStorage- The kind of project (for example House or Warehouse) you picked in Cost > Start a BOQ from scratch. A label only.From the code only
boqCityRateslocalStorage- The per-city rates you type in Cost > City-wise pricing: BOQ line, city, rate, the source you name and its date.From the code only
boqRateQuoteslocalStorage- The quotes you type in Cost > Rate bands: amount, the source you name and its date.From the code only
ferrum-cockpit-sites-v1localStorage- The sites you saved to the cockpit: a label, the parcel as the search showed it (ULPIN, district, state, coordinates, area, land use, provenance), zoning status, where it was saved from, times, your test-fit inputs for it, and any site definition or envelope review. Written only when you are signed in: a signed-out visit keeps its sites in page memory only and writes nothing here (they are gone when the page is refreshed or closed). Removed only when the list is empty.From the code only
ferrum-cockpit-sites-stash-v1:<account id or anon>localStorage- Sites set aside for another account (or for a signed-out visit) on this device, with the same content as ferrum-cockpit-sites-v1. Removed when empty.From the code only
ferrum-cockpit-authored-properties:v1localStorage- Parcel evidence you typed yourself, per site: ULPIN, locality, region, latitude and longitude, land use, source, record date, recorded area, FAR limit, jurisdiction and limit source.From the code only
ferrum-ribbon-cockpit:preview:v1localStorage- Your cockpit test-fit inputs (plot width and depth, setback, floors), the shell you chose and when you saved. Written when you press Save and when a project is switched.From the code only
ferrum-ribbon-cockpit:archive:v1localStorage- Earlier test-fit workspaces kept, newest first, when you press "Start a project" so nothing is overwritten.From the code only
ferrum-local-projects:v1localStorage- The list of projects kept in this browser: each project's id (made here), the label you typed, times, setup, and a copy of that project's saved data (record, plan state, parcel, frozen plans, revisions, sites, test-fit inputs, hand-off, authored properties, independent plan draft) so projects can be switched.From the code only
ferrum-local-projects:transaction:v1localStorage- A short-lived undo record written just before a project switch and removed when the switch completes.From the code only
ferrum-project-revisions-v1localStorage- The revision history of your project (plan inputs, parcel, BOQ history and sites per revision, author "This browser") for undo and redo. Written only when you are signed in: a signed-out visit keeps its revision history, and the sites in it, in page memory only and writes nothing here.From the code only
ferrum-user-boundary-v1:<lat>:<lng>[:<scope>]localStorage- The outline you drew on the site map (its coordinates); the key holds the site centre. Replaced by the next outline you save; a cleared outline stays stored until replaced.From the code only
ferrum-map-skin-v1localStorage- Your base-map choice on the site map (Drawing sheet or Standard map). Nothing else; replaced when you choose again.From the code only
ferrum-independent-plan-draft:v1localStorage- The independent plan draft: the source plan case you admitted (geometry, source declaration including the reviewer name you typed, hashes) and the plans saved from it; refused above 4 MB; swapped with the project and removed when the project is closed or deleted.From the code only
ferrum:cde:v1:<project id>localStorage- The Ferrum Build document register you keep per project: titles, disciplines, revision labels, file names, notes and state changes you typed. No file is stored.From the code only
ferrum:output-comments:v1localStorage- Notes you write against saved outputs: the text and the time. No author is recorded. The phone app pages read and write the same key.From the code only
ferrum:vendor-offers:v1localStorage- Vendor offers you typed against BOQ lines: supplier name, rate, GST basis, valid-until and time.From the code only
ferrum:gov-watchlist:v1localStorage- Government tenders watchlist you typed: the notice link you pasted, the closing date, and the optional reference, organisation, work, value and note, plus the time you added each. Nothing is copied from the portal. Removed when you remove the last notice.From the code only
ferrum:proposal-bids:v1localStorage- Bids you typed against work packages: package name, bidder name, amount, GST basis, valid-until, scope note and time.From the code only
ferrum.materialPlan.v1localStorage- Your Procura material plan: the project name, buyer and site you typed, the alert window, the BOQ lines you typed (reference, description, quantity, unit, category), their task dates and buffers, the supplier options you typed for each line (supplier name, rate with its source, dates and link, GST basis, lead and transit days, freight, loading, unloading, credit terms and discount) and your order-earlier or order-later comparison. Written on every change; never sent anywhere. Nothing removes it; clearing this site's data does. Read only by this browser.From the code only
ferrum.procure.projectOrder.v1localStorage- Your Procura project order: the name or id and role you typed, the order terms and revision references, order lines, sub-orders, delivery batches and transport legs, payment points with their evidence, invoices and payments you recorded (amount, date and UTR), and a log of every entry including refused ones. Written on every change; never sent anywhere. Nothing removes it; clearing this site's data does. Read only by this browser.From the code only
ferrum.investflow.dashboards.v1localStorage- Investor ledger entries you typed or imported from a CSV: investor name, project, type, amount, date and commitment id. Written on every change.From the code only
ferrum-communitybuild-spv-v1localStorage- The TEST MODE SPV setup record you entered; for an uploaded file only its name, size and SHA-256. Removed by "Delete record".From the code only
boqProBrandSelectionslocalStorage- The brand choices per material category in the /boq-pro take-off tool.From the code only
ferrum-designstudio-workflow:session:v1sessionStorage- Where you are in the DesignStudio workflow in this tab: stage, household brief, building category, plot dimensions, chosen direction and preset, space selections, last command, project and parcel ids. Cleared when the tab closes.From the code only
ferrum-structura-member-forces-v1sessionStorage- Per-member force extremes of the last INDICATIVE structural analysis run in this tab, handed to the member-check view. Cleared when the tab closes.From the code only
ferrum-structura-analytical-model-v1sessionStorage- Read by the structural analysis panel for a model handed over in this tab. Written only when you press "Send to FEA analysis" in the Model importer: the imported model and its parse report. Cleared when the tab closes; never sent anywhere.From the code only
ferrum-guestIndexedDB- The guest workspace (one record, written 300 ms after your last change; kept in memory only above 20 MB). The same database also holds a second, separate record: the work view you chose on the "Which describes your work?" step (next row). Nothing is sent to a server.From the code only
ferrum-guest / account-rolesIndexedDB- Inside the ferrum-guest database: the work view(s) you chose (for example Contractor), which one is active, and the last ones used. A view only arranges which tools are in front of you first; it is not a permission and not a check of any registration. It stays on this device, nothing is sent to a server, and Account, Delete my role data clears it.From the code only
ferrum-sutra-parametric-history-v1IndexedDB- Plan revision histories for SUTRA AI plans, keyed by project, site fingerprint and plan id.From the code only
ferrum-field-v1IndexedDB- The phone field app records (people, attendance marks, pay and advance records, problem reports, settlement drafts, photos and voice notes, and the outbox), device-only TEST MODE. Nothing is sent to a server; nothing moves money.From the code only
ferrum-build-siteIndexedDB- Ferrum Build site records waiting to be sent (work orders, daily logs, measurements, receipts and stock counts), one queue per project.From the code only
Phone web app (pages under /mobile)
Written by the phone web app pages, which are static files served from /mobile. Everything stays in this browser until the page sends it.
ferrum-mobile-build-enquiry-attempt-v1localStorage- On the phone enquiry page: a copy of the enquiry you pressed Send on (including the phone number and name you entered) with a random retry id, so a lost response does not create a duplicate. Not removed after a successful send.From the code only
ferrum-mobile-build-enquiry-draft-v1localStorage- On the phone enquiry page: your whole enquiry draft as you type it, including your phone number, name, location and consent, restored when the page reopens. Not removed after sending.From the code only
ferrum-chat-intent:<project>:<member>sessionStorage- Phone chat: the message you are sending (text, attachment ids, work package, drawing reference) until the group confirms it; then removed.From the code only
ferrum-chat-support:<project>:<account>sessionStorage- Phone chat: a support request you typed until it is confirmed; then removed.From the code only
ferrum-chat-tool-intent:<project>:<member>sessionStorage- Phone chat: the kind and ids of one project update in flight (item, vote, pin, unpin or upload); no text.From the code only
ferrum-external-intent:v1:<project>:<account>localStorage- Phone chat: metadata of an external-conversation record being published (project and account ids, a mutation id and a hash of your selection), removed once recorded.From the code only
ferrum-view-intent:v1:<project>:<account>localStorage- Phone chat: a pending owner view-access decision (member id and version), removed once recorded or refused.From the code only
ferrum-f92-pending-v1sessionStorage- Phone proposals: receipts of proposal actions pending confirmation in this tab (project and account ids, the kind of action, a record id and a mutation id). Cleared when the tab closes.From the code only
ferrum-f92-marketplace-pending-v1sessionStorage- Phone marketplace: receipts of bids, quotes and openings pending confirmation in this tab (project and account ids, the kind, a record id and a mutation id). Cleared when the tab closes.From the code only
ferrum-f92-public-invite-pending-v1sessionStorage- Phone vendor invite: receipts of invite actions pending confirmation in this tab (an invite-token fingerprint, the account and proposal ids, a mutation id and the action). Cleared when the tab closes.From the code only
ferrum:photos:pending-confirmationsessionStorage- Phone photos: your user id, the project and a confirmation token while a photo action is recovering; removed afterwards.From the code only
ferrum-app-mr-drafts:<project>localStorage- Phone procurement: material-request drafts (id, saved-at, the request you typed) kept when you are offline, until sent or discarded.From the code only
ferrum-mobile-site-outbox:<project>:<member>localStorage- Phone site page: entries queued on this device until the server confirms them.From the code only
ferrum-app-sitelog-outbox:<project>:<member>localStorage- Phone site log: entries queued on this device until sent or discarded.From the code only
ferrum-mobile-outbox:<screen>:<project>:<member>localStorage- Older copy of the phone offline outbox for the Issues, Schedule and Closeout pages, written by earlier versions of those pages: the entries you typed that were waiting to be sent. The current pages only read it, to take its entries over into the on-device database ferrum-mobile-outbox-v2 listed below; they never change or delete it, so on a device that used the earlier pages it stays until you clear this site's data. No :lock entry is written any more.From the code only
ferrum-mobile-outbox-v2IndexedDB- Phone offline outbox for the Issues, Schedule and Closeout pages: one record per screen, project and member, holding the entries waiting to be sent (what you typed, a random id, the time, the number of send attempts, and the server's reference or its refusal text) and the ids of entries taken over from the older copy. An entry is sent to the project server only when you are online and a fresh check shows you are signed in as its author with permission for that project; until the server confirms it, it is marked PENDING ON THIS DEVICE. Sent entries leave when you clear them; a refused entry, or one that was never tried, leaves when you discard it.From the code only
Cached open-data responses
Responses from the open-data services listed further down, kept so a repeat lookup needs no new request; most keys contain the site latitude and longitude, and each entry has a stored-at time. None of these keys was seen on build 981a13d2: the site's Content-Security-Policy did not allow the requests that fill them.
ferrum-topo-slope-v1:<site>localStorage- Cached terrain-tile results for a site.
ferrum-landintel-soil-geotechnical-v1:<site>localStorage- Cached soil-property results for a site.
ferrum:landintel:drainage-flood:power:<site>localStorage- Cached climate results for a site.
ferrum-landintel-climate-normals-v1:<site>localStorage- Cached climate normals for a site.
ferrum-landintel-cost-fx-v1:<pair>localStorage- A cached exchange rate for a currency pair (no site data).
ferrum-landintel-sourced-v1:osm-context-v2:<lat>,<lng>:r<radius>localStorage- Cached OpenStreetMap building footprints and road centrelines around a site for the 3D site context (for roads: the road type, width and lane tags and the public street name, nothing else), with source, licence and retrieved-at time; the key holds the site latitude and longitude (5 decimal places) and the search radius in metres. Reused for up to 7 days. Replaces the earlier buildings-only osm-buildings: key, which this build no longer reads or writes. The prefix is written by lib/landintel/provenance.ts; this is the only call site in this build that writes it.
ferrum-geocode-nominatim-v1:<normalised query>localStorage- A cached OpenStreetMap Nominatim place-search result (coordinates and matches), with source, licence and retrieved-at time; the key holds the trimmed, lower-cased search text. Reused for up to 30 days. Written by the address search (ULPIN map explorer and the Site tab): each shorter form of an address that gets a result is cached, so the key can hold the address text you typed, the pincode and the city. It stays in this browser only and is not sent anywhere by the cache itself.
Service worker cache
ferrum-os-static-v2Cache Storage- Copies of this site's own static files (/_next/static/* and /favicon.svg).Seen on build 981a13d2
Sign-in (only if you sign up or sign in)
ferrum_sessioncookie- A random session id set by this site's server when you sign up or sign in, so you stay signed in. HttpOnly (page scripts cannot read it), Secure, SameSite=Lax, for up to 30 days. "Sign out" on /account deletes the session on the server and clears the cookie.From the code only
Set by Razorpay's script, not by Ferrum code
Seen in a real browser on build 981a13d2 when the /products/transact page, which requests Razorpay's script, loaded. What each one is for is defined by Razorpay: UNAVAILABLE from this repository.
rzp_checkout_anon_idlocalStorage- Set by Razorpay.
rzp_device_idlocalStorage- Set by Razorpay.
__rzp_risksessionStorage- Set by Razorpay.
rzp_unified_session_idcookie- Set by Razorpay.
Information you send to this site's server
Forms that store what you type
- Footer newsletter (every page)
- Sent: Email address; the name is set to the text before the "@".Stored as: A record in the site database (name, email, product, source page, state, message, time).
- /company#c-contact (General, Book a demo and Partnership)
- Sent: First name, optional last name, email address, optional subject and required message; the selected topic is also sent.Stored as: A record in the site database (combined name, email, selected topic/product, source page, subject folded into the message, and time).
- /dashboard and /project-workspace/projects (early access)
- Sent: Name and email address.Stored as: A record in the site database (name, email, product, source page, state, message, time).
- /products/transact waitlist
- Sent: Name, email address and state.Stored as: A record in the site database (name, email, product, source page, state, message, time).
- /products/transact case flow
- Sent: Role (buyer or seller), contact name and contact email; then, if you use those steps, KYC (full name, document type, last four characters of a document reference), a scheduling request (date and time window) and a file upload.Stored as: Records in the site database. A file upload returns an error unless a storage bucket is bound; whether one is bound on the deployed Worker: UNAVAILABLE from the repo.
- /signup
- Sent: Email address, password and an optional name.Stored as: An account record in the site database: your email address, the name if you gave one, a salted PBKDF2 hash of your password (the password itself is not stored), whether your email is verified, and the time. It also creates a sign-in session and a one-time email-verification code record. No verification email is sent while no mail service is set up; the Ferrum team verifies accounts instead.
- /login
- Sent: Email address and password.Stored as: A sign-in session record (session id, your account, expiry) when the password matches. Every attempt, successful or not, also stores a rate-limit record (see "Rate limiting").
- /forgot-password and /reset-password
- Sent: Email address; then a reset code and a new password.Stored as: While no mail service is set up the server refuses the request before looking up the email, and stores nothing. With a mail service, a one-time reset code record is created, and a completed reset replaces the password hash.
- /build/projects (Ferrum Build project workspace; signed-in project members only)
- Sent: What members record on a project: issues, schedule stages, QC checklists, inspections and sign-offs, site work orders, daily logs, measurements and material receipts, crew attendance (the name of the worker, an optional worker code, trade, check-in and check-out times, an optional device location that is added only when the person checking in taps for it, who entered the entry and which supervisor confirmed it), quote selections, contract and milestones, invoices, payments and certifications, variations, snags, handover and warranty records, and photo records.Stored as: Records in the site database, tied to the project and to the member who made each change, with a time. History tables are append-only (the database refuses edits and deletions). Worker names in attendance entries are personal data of crew who may have no account of their own; they are visible to project members with attendance access (never the client) and are not deleted by any job in this build. Attendance storage is set up on the server only after its database migration is applied: UNAVAILABLE on the deployed site until then. Photo files are not uploaded: photo storage is not set up, so the upload routes answer "storage not configured".
- /build/start (Ferrum Build project enquiry)
- Sent: Building type, your phone number, your optional name, an optional location (a place name and PIN code, and coordinates rounded to about 1 km, taken from your device only if you already allowed device location, shown to you as unverified and editable), and your consent to be contacted on WhatsApp or phone, with the wording version and the time you gave it. Other project details are asked later by the team on WhatsApp.Stored as: A record in the site database with a reference number, a status and a history of status changes. Ferrum staff read and update it in the Build staff console.
Tools that send your entries to be computed
The Worker computes a result from what you enter and returns it. Nothing from these requests is stored except the rate-limit record described below.
- IS check
- Sends: Structure type and parameters.
- IRR / NPV modeler
- Sends: Cash flows and discount rate.
- Ask-band estimator
- Sends: Base value and urgency.
- Stamp-duty estimator
- Sends: The state you choose.
- ULPIN lookup
- Sends: The ULPIN you type.
- CDE status (CommunityBuild page)
- Sends: A project id.
- Construction status (CommunityBuild tab and page)
- Sends: Nothing you type. With your session it asks this site for the chosen project's own schedule, quality, closeout, issue, RFI, site-log and photo records and, where the register is on for your role, its pour log, and shows counts and dates only. It keeps nothing in your browser and sends nothing to a third party.
- Investment fit (LandIntel)
- Sends: The looked-up parcel's state, district, area, land use and record status, plus the use, budget, asking price, growth assumption, holding period and target return you enter; no ULPIN, name or contact. When a judgment server is connected, the server sends a text summary of them to Ferrum's self-hosted judgment model; it stores none of them (only the rate-limit record below).
Views that need a session
In guest mode, supported workspace requests and Save to workspace are handled on this device rather than sent to the server. Saved guest projects and tool results are kept in this browser’s IndexedDB; if storage is unavailable they remain in memory and the interface says Not saved. When you are signed in, account workspace requests are sent to the server and saved items belong to your account. Creating a share link needs an account and is unavailable in guest mode.
Recorded automatically by the server
- Hosting
- This preview runs on Cloudflare Workers with a Cloudflare D1 database. Cloudflare handles every request to it, including your IP address.
- Rate limiting
- For every API route that is rate limited, the Worker stores your IP address (as Cloudflare reports it), the route name and a time in the site database. Sign-up and sign-in attempts are also limited per email address: each attempt stores a record of the email address with the word "signup" or "login" and a time. No job that deletes these rows, or the form submissions above, was found in the code. Retention: UNAVAILABLE.
- Request logs
- Cloudflare Worker logging is switched on and persisted, with query strings redacted. The code adds events with the route (ids removed), method, status, duration and a request id. What else Cloudflare logs, and for how long: UNAVAILABLE from the repo.
- Crash reports
- If a page crashes, the browser sends the error name, message, page path and component stack so it can be logged. Query strings, form contents and cookies are not included.
- Coarse region
- When the SUTRA AI panel loads (straight away on wide screens, where it is docked; on phones only after you open it), it asks the Worker for a coarse country, region and time zone that Cloudflare derives from your connection; the response is marked as not persisted.
- Payment demo
- The payment demo on /products/transact creates an order record with a fixed illustrative amount (no name or email). Without Razorpay keys the Worker simulates the payment. Whether keys are set on the deployed Worker: UNAVAILABLE from the repo.
- Email and payment providers
- The Worker code can call api.resend.com (email) and api.razorpay.com (payments) when the matching secrets are set. Whether they are: UNAVAILABLE from the repo.
Third-party origins your browser may contact
Every host below receives your IP address and standard browser request headers by virtue of the request. Requests are subject to this site's Content-Security-Policy: a request the policy does not allow is blocked by the browser before it is sent.
tile.openstreetmap.org- Map tile images for the parcel map.Carries: Tile coordinates of the area you view.Seen contacted on build 981a13d2
unpkg.com- Leaflet marker icon images on the parcel map.Carries: A static image request.Seen contacted on build 981a13d2
tiles.openfreemap.org- Map style and vector tiles for the 3D site map.Carries: Tile coordinates of the area you view.Seen contacted on build 981a13d2
checkout.razorpay.com- Razorpay's checkout script, requested from the /products/transact page (payment demo). On build 981a13d2 the script in turn contacted cdn.razorpay.com, lumberjack.razorpay.com (a beacon) and api.razorpay.com (a hidden frame).Carries: What Razorpay's script stores or sends is defined by Razorpay, not by this code: UNAVAILABLE.Seen contacted on build 981a13d2
nominatim.openstreetmap.org- Place and address search (ULPIN map explorer and the Site tab address box, only after you press Search address) and reverse geocoding in the ULPIN map explorer; if the full address finds nothing the search tries up to 7 progressively shorter forms of it, one request at a time at least 1.1 seconds apart, each limited to India, ending with only the pincode or city, one reverse lookup when you tap "Use my location" in the header Region control, and a reverse lookup for the first-run location step: nothing is sent before you tap Continue, and while its place-name box stays ticked (it is ticked by default) each coordinate you choose on that page during this visit is looked up; unticking it stops this, and Not now sends nothing.Carries: The place text you type (or a shorter form of it with the house number removed), or the coordinates you pick; for the Region control, your device position rounded to 2 decimals (about 1 km), sent once per tap (the first-run step and Site details send each chosen coordinate to 5 decimals, about 1 m, for as long as the box stays ticked during this page visit; nothing is stored beyond it). The page address is sent as the referrer.Not seen on build 981a13d2
power.larc.nasa.gov- NASA POWER climate data for a site.Carries: Site latitude and longitude.Not seen on build 981a13d2
rest.isric.org- ISRIC SoilGrids soil properties for a site.Carries: Site latitude and longitude.Not seen on build 981a13d2
s3.amazonaws.com- Terrain elevation tiles (AWS open data, elevation-tiles-prod).Carries: Tile coordinates around the site.Not seen on build 981a13d2
api.frankfurter.dev- Currency exchange rate for cost estimates.Carries: A currency pair only.Not seen on build 981a13d2
overpass-api.de- OpenStreetMap building footprints and roads around the site for the 3D site context (Overpass API, first endpoint tried).Carries: A bounding box around the site latitude and longitude. For a site that came from this device’s location it is sent only after you turn on Show nearby buildings and roads (off by default, remembered in this browser).Not seen on build 981a13d2
overpass.kumi.systems- The same OpenStreetMap buildings-and-roads query, tried only if overpass-api.de returns no usable answer. Both are the default endpoints; a build can replace them (NEXT_PUBLIC_OVERPASS_ENDPOINTS).Carries: A bounding box around the site latitude and longitude. For a site that came from this device’s location it is sent only after you turn on Show nearby buildings and roads (off by default, remembered in this browser).Not seen on build 981a13d2
static.cloudflareinsights.com- Cloudflare Web Analytics, a third-party processor: the beacon script (beacon.min.js) is loaded from here only if the site operator turns Cloudflare Web Analytics on. Purpose: aggregate site analytics and page-load performance. Cloudflare's documented dimensions are country, host, page path, referrer, device type, browser and operating system, plus page-load timing metrics. Cloudflare documentation read on 2026-10-20: https://developers.cloudflare.com/web-analytics/Carries: A static script request. Cloudflare states that Web Analytics does not log query strings. Whether it stores anything in your browser, and how it treats IP addresses: UNVERIFIED (not stated on the Cloudflare pages read), so not stated here. Sale of data: UNVERIFIED.Allowed by the Content-Security-Policy since release 14b; not observed in a browser. Whether the site operator has switched Cloudflare Web Analytics on: UNAVAILABLE from the repo.
cloudflareinsights.com- Cloudflare Web Analytics beacon endpoint (connect-src): the script above sends its measurements here. Purpose: aggregate site analytics and performance, shown to the site operator by country, referrer host, page path, device and browser class, with timing metrics. Cloudflare documents that it keeps unsampled beacon data for 7 days, after which the data is aggregated down to about 10%, and that the dashboard shows the previous six months. Cloudflare documentation read on 2026-10-20: https://developers.cloudflare.com/web-analytics/Carries: The page path and referrer host of the page you load, your country, device type, browser and operating system, and page-load timing metrics. Cloudflare states it collects the minimum information (timing metrics) and does not track individual end users across its customers’ Internet properties. Cookies and fingerprinting: UNVERIFIED (not stated on the Cloudflare pages read), so not stated here.Allowed by the Content-Security-Policy since release 14b; not observed in a browser. Whether the site operator has switched Cloudflare Web Analytics on: UNAVAILABLE from the repo.
Hosts marked "not seen" are requested by the code when you use the matching tool. On build 981a13d2 the site's Content-Security-Policy did not list them, so the browser blocked those requests before sending them. The two Cloudflare hosts are the exception: the policy now allows them, but they are used only if the site operator switches Cloudflare Web Analytics on, which this repository cannot show.
Device location
The "Use my location" button in the header Region control, the "My location" control and the device-location button in the site-observation form ask your browser for your position only when you press them; this site's server is never sent it. The Region control sends the position, rounded to about 1 km, once to OpenStreetMap Nominatim and keeps only the resulting country and state codes, never the position. The other two keep the position in this browser (the local parcel context or the site-observation record). Separately, without asking, the Region control guesses a country from your device time zone and languages; that guess is not stored or sent.
Not found in this build's code
Searched for on 2026-10-19; none was found:
- Analytics, advertising or tracking scripts in this repository's page code. Separately, if the site operator switches on Cloudflare Web Analytics, Cloudflare serves its own beacon script (see the Cloudflare rows above); that script is not in this code.
- Page code that sets a cookie. The sign-in cookie (ferrum_session) is set by the server, not by page code; the one other cookie seen on the live build, rzp_unified_session_id, was set by Razorpay.
Retention periods, deletion requests and access requests: UNAVAILABLE until the operator publishes a procedure.
For questions about this Privacy Policy: Email contact: UNAVAILABLE until the operator publishes the address.