OmniBuild Privacy Policy

Effective date: 7 October 2026
Last updated: 7 October 2026
Publisher: Prameya LLC ("Prameya", "we", "us"), a United States limited liability company
App: OmniBuild for iPhone, iPad, Mac and Apple Vision Pro, with its Apple Watch app and its Apple TV app — bundle ID legal.prameya.OmniBuild (Apple Watch: legal.prameya.OmniBuild.watch)
Contact: admin@prameya.legal

This policy covers the OmniBuild app on every device it runs on, and nothing else. Other Prameya apps have their own policies, listed at https://prameyallc.github.io/privacy/. Their answers are different from this one — please do not assume they match.

The short version

• We never receive your data. Prameya runs no server that receives anything from OmniBuild. We have no user database and no user accounts.
• There is no account and no login. Every feature works the moment you open the app.
• Your projects and notes are stored on your device. iCloud sync is off until you turn it on. Only if you turn on More ▸ iCloud ▸ Sync with iCloud do your projects, notes, punch items and safety-reminder acknowledgements also go to your own iCloud private database, so your iPhone, iPad, Mac and Apple Vision Pro show the same records. Apple holds that database for you; we cannot open it. Decision entries from earlier versions and the app's small profile record stay on the device only, either way.
• Where you left off — which screen, which guide, and the random identifier of the last project you opened — goes to a small iCloud key-value store only while Sync with iCloud is on, so your other devices, Apple Watch and Apple TV can offer to continue. Handoff carries the same details to your nearby devices whether or not sync is on. None of it carries project names or notes.
• The only network traffic is Apple's and, on some Macs, one optional download. Apple's services (iCloud, only while Sync with iCloud is on; Handoff; the App Store for purchases; Apple's age-range check on iPhone and iPad; and the connection between iPhone and Apple Watch) are the only paths off the device, except that a Mac with 16 GB of memory or more can choose to download an on-device Ask model (about 6.8 GB) from Hugging Face. Everything else the app shows you ships inside the app.
• Ask answers on your device. Where Apple Intelligence is turned on and ready, Apple's on-device model answers your question. On a Mac that has downloaded the optional model, that model answers when Apple Intelligence cannot. Your question is not sent to us or to any server. iPhone, iPad and Apple Vision Pro are offered no download.
• No ads, no analytics, no tracking, no crash reporting service. There is no advertising SDK, no analytics SDK, and no third-party tracking code in the app.
• One optional permission. On iPhone and iPad, OmniBuild asks to send notifications only if you turn on More ▸ Notifications ▸ Job-log reminders, which is off until you turn it on. It uses no camera, photos, location, microphone, contacts or health data.
• Deleting is in your hands. More ▸ Your Data lets you open, export or remove each project, note, decision entry, punch item and safety-reminder acknowledgement (and correct a project's name or a note's text), and Clear All My Logs & Decisions erases them all. A few small items survive that button; they are listed under "Deleting your data".

Who we are and how to reach us

OmniBuild is published by Prameya LLC, a US limited liability company. For any privacy question, request, or complaint, email admin@prameya.legal. That inbox is monitored by a person. There is no phone line.

What OmniBuild does

OmniBuild is an educational reference app about construction, the skilled trades, and how construction work is regulated in the United States. It also lets you keep your own records — the projects you are working on and the notes you file against them — and export them.

OmniBuild is educational software. It is not contracting, engineering, architectural, legal, or code-compliance advice, and it is not a substitute for a licensed professional. That is a product statement rather than a privacy statement, but it matters here for one reason: because the app is not providing professional services, it never needs to know who you are.

What each device does.

Available tiers

There is one paid upgrade, OmniBuild Pro, sold as three products. Buying any one of
them grants exactly the same Pro — there are no separate feature tiers.

Family Sharing is enabled on all three. Subscriptions renew until you cancel (how, on each
device, is under Cancellation and refunds below); Lifetime is a one-time non-consumable. The prices, the trial and how to cancel are also shown on the paywall in the app and in the OmniBuild Terms of Use.

The knowledge layer is free and stays free. Without paying anything you get
the full standards library (every guide in the app), Ask, up to two projects with their notes, and an export of all your records, with no account and no time limit. Pro adds two things: keeping more than two projects, and a print-ready PDF of a project for the permit counter.

Pro does not change where your records go. Sync with iCloud works the same, paid or not, and there is no paid iCloud option. If a subscription lapses you keep every project and note and can still export them in their raw form; only the Pro tools stop.

Free vs paid tier data collection

Whether you buy Pro does not change what data Prameya collects from OmniBuild. Free and Pro alike:

• Your projects and notes stay on your device and, if you turn on Sync with iCloud, in your own iCloud private database
• No analytics, tracking, or telemetry
• No server of ours that receives your content
• No account or login

The difference is which tools you get, not data handling. The standards library, every guide in it, is free; Pro adds more than two projects and the permit-counter PDF. Neither unlocks data transmission.

Cancellation and refunds

Subscriptions are managed entirely through your Apple ID:

• To cancel: Open Settings on your iPhone or iPad → tap your name → Subscriptions → OmniBuild → Cancel Subscription. On Mac, open the App Store app → your name → Account Settings → Subscriptions → Manage. On Apple Vision Pro, open Settings → your name → Subscriptions → OmniBuild → Cancel Subscription.
• Refund requests: Handled by Apple, not Prameya. See reportaproblem.apple.com or contact Apple Support. We have no access to your payment information and cannot issue refunds ourselves.
• What happens to your data when you cancel: Nothing. Your projects and notes stay where they were. Canceling removes the Pro tools — adding a project beyond two, and the permit-counter PDF — but it does not delete anything, and the standards library stays fully available.

StoreKit transaction data

OmniBuild does not keep its own record of your purchase. Each time it needs to know whether you have Pro, StoreKit on your device answers from Apple's record of your purchases, and the answer stays on the device. Nothing about a purchase is sent to Prameya.

When you open the Pro screen (to show prices), buy Pro or tap "Restore Purchases", StoreKit talks to Apple's servers. That communication is between your device and Apple; Prameya is not involved and sees nothing from it.

Information the app stores on your device

Everything in this table is stored by OmniBuild itself. None of it is sent to Prameya.

The cost figures in older project and decision records are numbers you typed. They are your own estimates. The app does no lookup, no comparison against any pricing database, and never adds them up.

What you type into Ask is kept only in memory while the Ask screen is open; it is never saved. A file you export — the copy of your projects, notes, decision entries, punch items, safety-reminder acknowledgements and profile, or a Pro permit-counter PDF — goes wherever you choose to save or send it.

The app database is included in Apple's normal device backup (iCloud Backup or a computer backup) if you use one, under Apple's terms and your control. The downloaded Ask model is excluded from backups. Prameya has no access to your backups.

iCloud, Handoff and your other devices

Sync with iCloud is off until you turn it on, in More ▸ iCloud ▸ Sync with iCloud on your iPhone, iPad, Mac or Apple Vision Pro (on a Mac, the same settings are also in OmniBuild ▸ Settings…). It is off on a new install. It is also off after this update on a device that ran an earlier pre-release build, where sync ran whenever the device was signed in to iCloud: there was no switch then, so there is no earlier choice to carry over, and being signed in to iCloud is not a choice to sync. On such a device, the first time the updated app opens it also removes the key-value items the earlier build put in iCloud (the "where you left off" row of the table above), as turning the switch off does; the copy of your records in your iCloud private database stays, as described below. The switch is set on each device separately.

While Sync with iCloud is on (and the device is signed in to iCloud):

• Your projects, notes, safety-reminder acknowledgements and punch items sync through your own CloudKit private database (container iCloud.legal.prameya.OmniBuild) to OmniBuild on your other devices that have sync on. Prameya cannot open another person's private database. Decision entries and the profile do not sync. Turning sync on sends the records on this device to your iCloud private database and brings in the ones your other devices put there.
• A small iCloud key-value store holds the "where you left off" items and the appearance choice listed in the table above. OmniBuild on your other devices, Apple Watch, Apple TV and the Home Screen widget read it to offer to continue and to match your appearance choice. It does not hold project names, notes or anything you typed.
• A record you delete, one at a time or with Clear All My Logs & Decisions, is also deleted from your other devices that sync, when they next sync.

While Sync with iCloud is off:

• OmniBuild puts nothing in iCloud: the app database has no iCloud connection, and the app writes nothing to the key-value store and does not read it (it still removes the "where you left off" items there when you use Clear All My Logs & Decisions). Your records stay on this device, and anything you delete is deleted on this device only.
• Apple Watch, Apple TV and the Home Screen widget get no key-value items from this device, so they cannot pick up where you left off here, and your appearance choice is not shared. (Your iPhone still sends its Apple Watch the prompts and the last project's name directly, as described under "Apple Watch".) They cannot see this device's switch: if another of your devices has sync on, they can still show what that device puts in the key-value store. Otherwise the widget shows "Open OmniBuild".

Turning Sync with iCloud off stops sync at once: OmniBuild reopens its database without the iCloud connection. It also removes the "where you left off" items, the widget's guide and the appearance choice from the key-value store. Your records stay on the device. The copy of your projects, notes, safety-reminder acknowledgements and punch items already in your iCloud private database stays there for your other devices; to remove it, use Clear All My Logs & Decisions while sync is on, or delete OmniBuild's data in your device's iCloud storage settings. OmniBuild asks before turning sync off and says this.

Handoff tells your nearby devices that use the same Apple Account the same "where you left off" details — the screen, the guide, and the identifier of the last project you opened — whether or not Sync with iCloud is on. You can turn Handoff off in your device's settings (on iPhone and iPad, General ▸ AirPlay & Continuity).

All of this travels through Apple's services under Apple's terms. None of it reaches Prameya.

Apple Watch

The Apple Watch app lists the guides, shows a "Continue" link to the guide you last opened (read from the iCloud key-value store, which your devices write only while Sync with iCloud is on there), and shows three prompts: On site, Punch item done (which your iPhone withdraws when no punch item is open), and Safety reminder.

• Your iPhone sends the Watch the list of prompts and the name of the project you last opened, over Apple's connection between the two devices. The Watch keeps that name in its own storage to show it: in the Watch app and, if you add the OmniBuild complication to a watch face, on the watch face, where anyone who can see your watch can read it (with no name, the complication shows "Codes"). That storage is on the Watch and is shared only between the Watch app and its complication. When no project is open on your iPhone — for example after Clear All My Logs & Decisions — your iPhone sends no name and the Watch clears the one it had.
• Tapping Confirm on the Watch sends the tap to OmniBuild on your iPhone, which records it: an "On site" note on the project you last opened (or under "today's work" if you have not opened one), marking the open punch item done, or a safety-reminder acknowledgement. Snooze and Not now record nothing. None of these is a sign-off or an inspection result.
• The Watch app has no Ask and downloads nothing.

None of this reaches Prameya.

Apple TV

The Apple TV app shows the guides and a "Continue" link to the guide you last opened, and matches your appearance choice, both read from the iCloud key-value store, which your other devices write only while Sync with iCloud is on there. Its Ask screen answers by quoting the guide you pick; it runs no language model, downloads nothing, and does not save your question. Its About page shows the app's version, what OmniBuild is, the short version of this policy with the full-policy and contact addresses, and the terms line, all as text built into the app; it fetches nothing. The Apple TV app keeps no projects or notes.

Job-log reminders (iPhone and iPad)

The reminders are off until you turn them on in More ▸ Notifications ▸ Job-log reminders. Turning the switch on is the only thing in OmniBuild that asks for permission to send notifications. If you allow it, the app schedules a local reminder every day at 7:00 your local time titled "Open today's job log", and, while a punch item is open, a one-off "Punch item still open" reminder four hours after the app last started. iOS delivers them from the device; nothing is sent to us or to any server, and the reminder text names no project.

A plain tap on a reminder only opens the app. Only the Confirm action records anything (an "On site" note, or marking the punch item done). Turning the switch off removes the pending reminders. (If you allowed OmniBuild's notifications in a pre-release build, before this switch existed, the switch starts on; you can turn it off.)

Network access — Apple's services and one optional download

OmniBuild has no server of ours to talk to, no analytics endpoint, no update channel and no content feed. The guides and everything they cite ship inside the app, so the reference works with no signal at all.

What does use the network:

• Apple's services: iCloud (the private database and the key-value store, only while Sync with iCloud is on), Handoff, the connection between iPhone and Apple Watch, the App Store through StoreKit when you open the Pro screen, buy Pro or restore a purchase, and Apple's Declared Age Range service on iPhone and iPad (see "Children").
• Hugging Face, on a Mac only, only if you choose to download the Ask model (see the next section).
• Your browser or mail app, when you tap a link — for example "Read the full policy online", "Support", "Email support", or "Open the source" on a guide. That is an ordinary link; your browser or mail app handles it, and nothing about you is attached to it by us.

The macOS build declares the com.apple.security.network.client sandbox entitlement, because iCloud sync and the optional model download need it. The app's transport security settings do not allow unencrypted connections.

Ask, and the optional on-device model

Ask sends your question, together with the text of the guide you picked (or, if you picked none, up to three guides whose text shares a word with your question), to a language model that runs on your device, and shows the answer, labelled with where it came from. Before any model is asked, some questions — for example, whether work is up to code, or a structural calculation — get a fixed reply instead of an answer.

• Where Apple Intelligence is turned on and ready (iPhone, iPad, Mac and Apple Vision Pro), Apple's on-device model answers, and the answer is labelled Apple Intelligence. Your question is not sent to us.
• Where Apple Intelligence cannot answer and no downloaded model is ready, Ask cannot answer, and on those devices the Ask tab is hidden. The guides work without it.
• More ▸ Ask ▸ In-app answers turns Ask off entirely.

The optional model, on Macs only. OmniBuild offers one downloadable model: Gemma 4 E4B (instruction-tuned, quantization-aware 4-bit), from the Hugging Face repository mlx-community/gemma-4-E4B-it-qat-4bit at commit 0f35c6f, about 6.8 GB. It is offered by default on Macs with 24 GB of memory or more, and as an opt-in row on Macs with 16 to 18 GB. iPhone, iPad, Apple Vision Pro, Macs with 8 GB, Apple Watch and Apple TV are offered no download. The app shows the model as "Large on-device model"; its full name, licence and repository are listed under More ▸ Legal ▸ Acknowledgements & Sources.

The model is not part of the app download. It is downloaded only after you choose Download in the On-device model sheet (opened from Ask or from More ▸ Ask ▸ On-device model), and only after the app checks that the Mac has enough free memory and disk space for it. The downloaded files are the model weights, its tokenizer and its prompt-formatting template, pinned to one commit and checked against the size and SHA-256 checksum of each file: data the model reads, not code. The model is used only when Apple Intelligence cannot answer. Its answer is checked before anything is shown; an answer that is cut off at the length limit, or that fails the check, is withheld and Ask says why. Its answers are labelled On-device model.

Like any file download, the request to Hugging Face gives Hugging Face your Mac's IP address and standard request headers (including a user-agent naming OmniBuild), and names the model repository, the commit and the files requested; Hugging Face handles it under its own terms. It carries no account token, and it does not include your question, your records or anything you type. We do not receive that request. Remove the downloaded model, in the same sheet, deletes the files and withdraws your choice.

Files of a smaller model that pre-release builds of OmniBuild could download (Qwen3 0.6B) are deleted the next time OmniBuild opens past the first-run screen in this version, and by Clear All My Logs & Decisions. Nothing is sent anywhere.

Device permissions

OmniBuild asks for one permission, and only when you turn on a feature that needs it.

A note about jobsite features. OmniBuild is described as jobsite support. That support is informational — reference content, citations, your own records and a reminder you choose. It does not involve photographing a site, geotagging work, or tracking where you are. If that ever changes, this policy will change first and the app will ask for the permission at the moment it is needed.

An earlier version of the Xcode project injected unused camera and photo-library purpose strings into the app's build settings, left over from a template. Those strings have been removed. The current build declares no camera, photo, location, microphone or health purpose strings and contains no code that requests those permissions.

Health data — OmniBuild does not handle any

OmniBuild does not collect, receive, access, process, derive, store, share, or sell health data of any kind. It has no connection to Apple Health, it asks no health questions, and it produces no health, wellness, fitness, or medical output.

We are stating this bluntly because earlier builds of this app were misleading about it, and we would rather correct that in public than quietly.

• The app contains no HealthKit code at all. Not a partial implementation — none.
• Earlier builds nonetheless carried Apple HealthKit entitlements, including the restricted health-records entitlement, and a permission description about steps and sleep. Those describe a feature that does not exist and never existed.
• An earlier build also displayed a line of text about "activity context" containing step and sleep numbers. Those numbers were hardcoded placeholder values written into the source code. They were not your data, they were not anyone's data, and they should never have been shown.

All of that is gone from the current build: the HealthKit entitlements (including health-records and background delivery), the health permission descriptions in both the Info.plist and the Xcode build settings, the background-fetch mode, and the hardcoded step/sleep narrative have all been removed.

Because OmniBuild processes no health data:

• It does not process consumer health data as Washington's My Health My Data Act (RCW ch. 19.373) defines that term — a definition that is deliberately much broader than Apple's, and reaches data that is merely accessed, processed, or derived, not only data that is transmitted. Even under that broad reading, there is nothing here. For the same reason, OmniBuild does not publish a separate Consumer Health Data Privacy Policy: that duty attaches to apps that handle consumer health data, and this one does not.
• The same conclusion applies under Nevada SB 370 (NRS ch. 603A), which imposes comparable duties on consumer health data.
• HIPAA does not apply to OmniBuild. HIPAA covers health plans, health care clearinghouses, most health care providers, and their business associates. Prameya is none of those, and OmniBuild has no relationship with any of them. We are not saying OmniBuild is "HIPAA compliant" — that phrase would be meaningless here. We are saying the law does not reach this app, and no protected health information is involved.

Accounts and sign-in — none; iCloud sync — if you turn it on

OmniBuild has no account system. There is nothing to register, no password, no email address to hand over, no Sign in with Apple, and no profile held by us. OmniBuild has no sign-in feature of any kind, and nothing is stored in the device Keychain.

OmniBuild can sync through iCloud, as described above, if you turn it on: with More ▸ iCloud ▸ Sync with iCloud on, projects, notes, safety-reminder acknowledgements and punch items go to your own iCloud private database, and a small key-value store carries where you left off. That sync is Apple's, under your Apple Account; it is not an account with us, and we cannot read what it holds.

An earlier build shipped a dormant sync component that transmitted nothing, and an earlier version of this policy said that if real sync were ever built it would be off by default. The version of this page dated 23 September 2026 said the real sync was not off by default, because it ran whenever you were signed in to iCloud. Since 24 September 2026 it is off by default, as first promised: it runs only after you turn on Sync with iCloud, and turning the switch off stops it.

Things OmniBuild does not do

One line each, because each one deserves a plain answer.

• We do not sell your personal information. Not to anyone, not ever, and we never have.
• We do not share your personal information for cross-context behavioral advertising. There is no advertising in this app.
• We do not show ads. There is no ad SDK in the app.
• We do not track you across apps or websites. The app declares no tracking, contains no attribution or tracking SDK, does not use the advertising identifier, and never shows the App Tracking Transparency prompt.
• We do not use analytics. No usage events, no session recording, no telemetry.
• We do not collect crash reports ourselves. No crash-reporting SDK is present. The app reads the performance summaries Apple's MetricKit prepares on the device (launch time, hangs, disk writes, exit counts) and writes them only to the device's own log; it does not send them anywhere. When StoreKit reports an error on a purchase, a restore or loading the Pro prices, the app also writes which of the three failed and the error's type and code to that log, with no price or product name, and does not send that anywhere either.
• We do not build a profile of you. We have no user-profile database because we have no server.
• We do not use your content to train AI models. We never receive it.
• We do not knowingly collect anything from children. See below.
• We do not use dark patterns to obtain consent. The permission and consent choices in the app — turning on Sync with iCloud, turning on reminders, downloading the Ask model on a Mac, and Apple's own age-range sheet — are off or unanswered until you act.

Children

OmniBuild is a general-audience reference app about construction and the skilled trades, intended for adults and for apprentices and students in the trades. It is not designed for or directed to children, it is not offered in Apple's Kids Category, and it contains no advertising and no social or messaging features. It does offer one in-app purchase, OmniBuild Pro, described above.

The Children's Online Privacy Protection Act (COPPA) restricts the online collection of personal information from children under 13. OmniBuild collects no personal information from anyone, of any age, because nothing you enter is transmitted to us. There is therefore no children's personal information for us to hold, use, disclose, or delete.

Apple's age range (iPhone and iPad). Some state laws, such as Texas SB 2420, require apps to use the age range an Apple Account shares. After the first-run screen, OmniBuild asks Apple whether those rules apply to your account. Where Apple says they do, the app asks Apple once for your age range with a single age boundary, 18; Apple shows the choice and you decide whether to share. The app keeps only the result — "under 18", "18 or older" or "not shared" — on the device, shows it as "Age range" in More ▸ Legal, and never sends it to us. When a later update makes a significant change, Apple may show you a notice about it, or, for an account whose rules require a parent's or guardian's approval, OmniBuild waits for that approval before opening. The Mac, Apple Vision Pro, Apple Watch and Apple TV apps do not make this check.

If you believe a child has somehow provided personal information to us — for example by emailing our support address — write to admin@prameya.legal and we will delete it.

The App Store age rating is set in App Store Connect. OmniBuild has no health, wellness, or medical feature, so the honest answer on medical and wellness topics is "none".

When you contact us

If you email admin@prameya.legal, we receive your email address and whatever you choose to put in the message. That is the only route by which we ever hold information about a user of this app.

• We use it to answer you, and for nothing else.
• We do not add you to a mailing list.
• We do not sell it or share it for advertising.
• We keep support correspondence only as long as we need it to handle your issue and to keep a record of privacy requests we are required to log — generally no more than 24 months — then delete it.
• Our email is hosted by a standard commercial email provider acting on our instructions. It does not use your message for its own purposes.

Please do not include sensitive information in a support email. You do not need to tell us your address, your health information, your license number, or your client details, and we would rather not have them.

Information Apple gives us

Because OmniBuild is distributed through the App Store, Apple may provide us with aggregate, non-identifying reports about downloads, purchases and app performance. We cannot identify you from these reports, and we cannot connect anything in them to anything you did inside the app. Apple's handling of your App Store activity, your iCloud data and your Apple Intelligence use is governed by Apple's own privacy policy, not this one.

Deleting your data

Your records are on your device and, if you turn on Sync with iCloud, in your own iCloud, so deletion is under your control. It takes effect on the device at once, and, while Sync with iCloud is on, on your other devices when they next sync with iCloud. While sync is off, a deletion stays on this device.

1. Remove one record: open More ▸ Your Data ▸ Open your projects, notes and other records. There you can open each project, note, decision entry, punch item and safety-reminder acknowledgement and delete it (you are asked first); a project's name and a note's text can also be corrected. Punch items are listed only when you have one. The same screen prepares the export copy of your projects, notes, decision entries, punch items, safety-reminder acknowledgements and profile. While Sync with iCloud is on, a deleted record is also removed from your other devices when they next sync with iCloud.
2. Erase your records: in More ▸ Your Data, tap Clear All My Logs & Decisions, then Clear Everything. This cannot be undone. It deletes every project, note, decision entry, safety-reminder acknowledgement and punch item, and the profile, on this device — and, while Sync with iCloud is on, through iCloud, the synced ones on your other devices when they next sync; each of those devices then drops its own bookmark of the deleted project (and, on an iPhone, tells its Apple Watch) the next time OmniBuild opens or comes back to the foreground there. It also removes the "where you left off" bookmarks on this device; the "where you left off" entries in the iCloud key-value store (the screen, the guide, the identifier of the last project you opened, the widget's guide and a guide the widget asked the app to open); the details in the current Handoff activity, which then names only the screen you are on; the project name on Apple Watch, which clears it when it next receives your iPhone's update; a pending "Punch item still open" reminder; your stored age range; your answer about the Ask model; and any downloaded Ask model files.
3. What Clear All does not remove:
   • Your appearance choice (on the device and, while Sync with iCloud is on, in the iCloud key-value store), the Sync with iCloud, In-app answers and Job-log reminders switches, the date you accepted the first-run notice, and which update notice this install has been through.
   • As you keep using OmniBuild, it records where you left off again: the screen you are on and the guide you open, and a project's identifier only once you open a project.
   • With Sync with iCloud off, the copy of your records already in your iCloud private database from when sync was on. The confirmation says so; to remove that copy too, turn sync on and clear again.
4. Erase everything on one device: delete OmniBuild from that device. That removes that device's copy only. It does not empty your iCloud private database, which keeps any synced records until you use Clear All My Logs & Decisions on a device that still has OmniBuild with Sync with iCloud on, or delete OmniBuild's data from your iCloud storage in your device settings. It does not remove the iCloud key-value store entries either; turning Sync with iCloud off before you delete the app does.

If OmniBuild cannot open its database on a device, it says so and offers Reset local data. That button appears only then. It deletes the app database on that device, with every record in it, and opens an empty one; the screen says so before you tap it. It does not remove the copy in your iCloud private database; while Sync with iCloud is on, your synced projects, notes, punch items and safety-reminder acknowledgements come back from it into the new database. Decision entries and the profile, which never sync, do not.

Nothing survives on our side, because nothing was ever on our side. There is no request to file and no waiting period, because there is no account for us to look up, and no server-side copy for us to delete. If you want written confirmation of any of this, email admin@prameya.legal and we will send it.

Data retention

We retain nothing from your use of the app, because we receive nothing. Your records are kept on your device, and in your iCloud if you turn on sync, for exactly as long as you keep them, as described above. The Ask model files on a Mac stay until you remove them, use Clear All, or delete the app. Apple keeps its own record of any purchase, and Hugging Face keeps whatever it keeps about a model download request, under their own terms. Support correspondence is retained as described above.

Security

Honest, specific statements only:

• The app runs inside the operating system's application sandbox, so its data is isolated from other apps. On iPhone, iPad and Apple Vision Pro it is also protected by the device's file-level encryption and your passcode; on a Mac, by FileVault if you have turned it on.
• If you turn on Sync with iCloud, synced records are held in your iCloud private database under Apple's terms and security. Use a strong Apple Account password and two-factor authentication.
• OmniBuild has no server of ours to connect to. Its only network connections are Apple's services and, on a Mac, the optional model download from Hugging Face; the app's transport settings refuse unencrypted connections.
• The app does not store anything in the device Keychain. It has no passwords, tokens, or credentials to store, because it has no account system.
• Because we hold no copy of your data, there is no Prameya server that could be breached and expose it. That is the single largest security property of this design, and it comes from the architecture rather than from any product we bought.

No system is perfectly secure, and the strongest protection for your data is your device passcode or biometric lock and the security of your Apple Account.

Your privacy rights

We describe these rights fully, and we also tell you the practical reality: for almost every request, our honest answer will be "we do not hold anything about you", and the data you are asking about is on your device and in your own iCloud, where you can see, export and erase it yourself.

California (CCPA/CPRA)

If you are a California resident, you have the right to:

• Know what personal information we have collected about you, the sources, the purposes, and the categories of third parties we disclosed it to.
• Delete personal information we hold about you.
• Correct inaccurate personal information we hold about you.
• Opt out of sale or sharing of your personal information for cross-context behavioral advertising.
• Limit the use and disclosure of sensitive personal information.
• Not be discriminated against for exercising any of these rights.

How this applies to OmniBuild:

• Through your use of the app, we collect no categories of personal information. Nothing is transmitted to us. We therefore disclose no categories to anyone, we sell nothing, and we share nothing for advertising. Apple (iCloud, Handoff, StoreKit, Apple Intelligence) and Hugging Face (the optional model download on a Mac) are services you use directly; they are not a sale or sharing by us.
• We collect no sensitive personal information through the app. The app does not access precise geolocation, health data, biometric data, government identifiers, racial or ethnic origin, religious beliefs, union membership, contents of your mail or messages, or your account credentials.
• If you have emailed us, the only personal information we hold is your email address and your message. You can ask us to show it to you, correct it, or delete it.

To exercise any right, email admin@prameya.legal with the subject line "Privacy Request". We will respond within 45 days, and will tell you if we need the one permitted 45-day extension. Because we have no accounts, we verify a request by replying to the email address the request came from — that is the only identifier we have. An authorized agent may make a request on your behalf with written permission from you.

Washington (My Health My Data Act) and Nevada (SB 370)

These laws create duties for companies that handle consumer health data. OmniBuild handles none, as explained above, so those duties are not triggered and no separate consumer health data privacy policy is published for this app. Washington's law also allows individuals to bring claims through the state Consumer Protection Act (RCW 19.86.090); we mention it so you know the route exists, not because we believe there is anything here to claim.

Other US states

Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, and other states with comprehensive privacy laws have broadly similar rights to access, correct, delete, and obtain a portable copy of personal data, and to opt out of targeted advertising, sale, and certain profiling. We do not engage in targeted advertising, sale, or profiling. Use the same email address for any request. Some states provide a right to appeal a denied request — if we deny yours, we will tell you why and how to appeal.

If you are in the EU, the UK, or Switzerland

The App Store territories OmniBuild will be offered in are still being decided, so this subsection is written to cover the broadest case. Where the app is available to you and the GDPR or UK GDPR applies:

• Your use of the app does not result in Prameya processing your personal data, because nothing reaches us. For app usage, there is no controller-held dataset, no international transfer by us, and no automated decision-making about you.
• Apple runs iCloud, Handoff and the App Store checkout and decides for itself what it does with them; we do not direct it and receive nothing from them. If you download the optional Ask model on a Mac, Hugging Face receives that download request under its own terms; we do not direct it and do not receive it.
• The in-app "Read the full policy online" link opens this page in your browser. That request is made by the browser, not by OmniBuild, and we receive nothing from it.
• If you email us, we process your email address and message on the basis of our legitimate interests in responding to you (Article 6(1)(f)), or to comply with a legal obligation where a privacy request is involved (Article 6(1)(c)).
• Article 9 special-category data, including health data, is not involved. The app does not process it. We ask that you do not send it to us by email either.
• You have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to complain to your national supervisory authority.

Prameya LLC is a US company. We have not appointed an EU or UK representative, because our processing does not meet the threshold that would require one. If that assessment changes, this section will be updated.

Third parties

The app contains no third-party service that sends your data to us or to anyone else. For completeness, here is everyone in the picture:

Nobody else. No advertiser, no data broker, no analytics vendor, no hosted AI provider.

The app links these open-source packages for Ask's optional on-device model: Apple's mlx-swift and mlx-swift-lm, and Hugging Face's swift-huggingface, swift-transformers and swift-jinja, with their own dependencies. OmniBuild uses them on the device, and the only network request OmniBuild makes through them is the model download described above.

App Store privacy labels — a note on wording

The App Store privacy label answer we give Apple for OmniBuild is "Data Not Collected". It is accurate under Apple's definition, which treats "collect" as transmitting data off the device in a way that lets the developer or its partners access it beyond servicing the request in real time. If you turn on Sync with iCloud, your synced records go to your own iCloud private database, which Apple holds for you and we cannot read; the optional model download carries none of your content; purchases are Apple's. It also matches the privacy manifests shipped inside the app, its widget, its Apple Watch app and its Apple TV app, which declare no tracking, no tracking domains, and no collected data types.

We want to flag one thing about that phrase, because it is easy to over-read. Apple's definition governs the App Store label and nothing else. It does not narrow what any state or national privacy law requires of us, and several laws — Washington's My Health My Data Act most obviously — define "collect" far more broadly, reaching data that is merely accessed, processed, or derived. We are not using Apple's definition to dodge anything. In OmniBuild's case the answer is the same under either definition, because the app genuinely does not handle the categories those laws are aimed at.

Changes to this policy

If we change how OmniBuild handles data, we will update this policy and change the effective date at the top.

• For material changes — for example, adding an account system, adding any feature that sends your content to us or to a new party, adding advertising or analytics, or using a permission the app does not use today — we will not do it quietly. We will update this policy before the change ships where we can, describe plainly what changed, keep the previous version available, and where the change requires your consent, ask for it inside the app rather than assuming it.
• For minor changes such as clarified wording or a corrected contact detail, we will update the effective date.

7 October 2026 — what changed. Corrections and clarifications, so this page matches the app. None of them means anything new leaves your device.

• The free library. "Available tiers" and "Free vs paid tier data collection" said the free standards library included "every state pack". OmniBuild bundles no state pack, so both now say that every guide in the app is free. Nothing that was free became paid.
• The Home Screen widget. The "where you left off" row said the iCloud key-value store holds "the guide the Home Screen widget suggests". The widget no longer suggests a guide: it shows the last guide you opened, or "Open OmniBuild" until you open one. The row now says so. That entry carries nothing you typed and, as before, is written only while Sync with iCloud is on.
• One date. A line at the end of this page still said "Effective 24 September 2026" after the date at the top had moved to 27 September 2026. That line is gone, so the page states one effective date.
• Three things the app does that this page did not describe. "Deleting your data" now describes Reset local data, the button OmniBuild offers only when it cannot open its database, and what comes back from iCloud after it while Sync with iCloud is on. The crash-reports line now says that when StoreKit reports an error on a purchase, a restore or loading the Pro prices, the app writes which one failed and the error's type and code to the device's own log. The iCloud section now says that on a Mac the same settings are also in OmniBuild ▸ Settings….

Nothing is sent to Prameya, and that did not change.

27 September 2026 — what changed.

• No state picker. Earlier versions of this page described a More ▸ Your Location state picker, whose choice was neither saved nor sent. The picker did nothing and has been removed from the app, so this page no longer mentions it. OmniBuild has never asked for or used your location, and still does not.

• The project name on the watch face. OmniBuild's Apple Watch complication can now show the name of the project you last opened on your iPhone; until now it always showed "Codes". The Watch app keeps the name in storage on the Watch that only it and its complication share, and clears it when your iPhone sends no name, as before. Anyone who can see your watch face can read it. The "Apple Watch" section and the table of devices say so.

• Cancelling on a Mac or Apple Vision Pro. How to cancel now gives the Mac route (the App Store app → your name → Account Settings → Subscriptions → Manage), which a Mac uses instead of Settings, and the Apple Vision Pro route, as well as iPhone and iPad.

• The Apple TV About page. The Apple TV app's About page (what OmniBuild is, the short version of this policy and the terms, as text) is now described.

Nothing is sent to Prameya, and that did not change.

24 September 2026 — what changed.

• Sync with iCloud is now a switch, off until you turn it on. The 23 September version of this page said sync ran whenever you were signed in to iCloud and that OmniBuild had no switch of its own. OmniBuild now has More ▸ iCloud ▸ Sync with iCloud. It is off on new installs, and off after this update on devices that ran an earlier pre-release build (there was no earlier choice to carry over); on those devices the first launch after this update also removes the key-value items the earlier build put in iCloud. While it is off, OmniBuild puts nothing in iCloud: no synced records and no key-value items. Turning it off stops sync at once and removes the key-value items; the copy of your records already in iCloud stays until you delete it. This keeps the promise an earlier version of this page made, that any sync would be off by default.
• Punch items and safety-reminder acknowledgements in Your Data. Each one can now be opened and deleted on its own in More ▸ Your Data. Before, they were only in the export and in Clear All My Logs & Decisions.
• Clear All says whether it reaches iCloud. With Sync with iCloud off it deletes on this device only, and its confirmation says so.

Nothing is sent to Prameya, and that did not change.

23 September 2026 — what changed. The previous version of this page described an app that no longer exists. It said OmniBuild made no network requests, had no AI, no cloud sync and no notifications, and ran only on iPhone and iPad. None of that is true of the current app. This version says what the app does today:

• iCloud sync. Your projects, notes, safety-reminder acknowledgements and punch items sync through your own iCloud private database when you are signed in to iCloud. The earlier version said sync, if ever built, would be off by default; it is not. It runs whenever you are signed in to iCloud, and you can turn iCloud off for OmniBuild in your device settings. Decision entries and the profile stay on the device.
• Where you left off. A small iCloud key-value store and Handoff carry the screen, the guide and the identifier of the last project you opened to your other devices, Apple Watch and Apple TV.
• Ask. Ask answers on the device with Apple Intelligence, and on Macs with 16 GB of memory or more it can use an optional model (about 6.8 GB) that you choose to download from Hugging Face. The earlier version said the app had no AI feature and downloaded nothing.
• Reminders. On iPhone and iPad, an optional daily job-log reminder asks for notification permission when you turn it on.
• More devices. The policy now covers the Mac, Apple Vision Pro, Apple Watch and Apple TV apps, and says what each one does.
• Apple's age range. On iPhone and iPad the app asks Apple for your age range where Apple says the rules apply, and keeps only "under 18", "18 or older" or "not shared" on the device.
• Pro. Pro adds more than two projects and a permit-counter PDF. The earlier version said Pro added inspection packs and that canceling removed paid building codes; neither was true. It also said the app kept a StoreKit record in its database; it does not.
• Deleting. The deletion section now lists what Clear All My Logs & Decisions removes, including from your other devices through iCloud, and the small items it does not remove.
• Clear All now reaches further. It also removes the "where you left off" entries from the iCloud key-value store and from Handoff, clears the project name on Apple Watch, and withdraws a pending punch-item reminder. Your other devices drop their bookmark of a deleted project, and an iPhone tells its Apple Watch, once the deletion has reached them and OmniBuild next opens or comes back to the foreground. Earlier today this page listed those entries and the Watch name as things Clear All left behind.
• A complete export. The export copy now includes punch items and safety-reminder acknowledgements, which it used to leave out.
• Old model files. Files of the retired pre-release model are deleted when the app opens, not only when you open Ask.
• In-app wording. The privacy text inside the app no longer says we receive a transaction identifier when you buy Pro (we do not), and it now says that Clear All reaches your other devices through iCloud and that deleting the app leaves your iCloud copy.

Nothing is sent to Prameya, and that did not change.

This revision (August 8, 2026) corrected statements in this policy so that they match the code that actually ships. Internal review notes that had been left visible in the published text were removed. Where a removal described here has been completed in the shipping build — the HealthKit entitlements and hardcoded health narrative, the dormant sync component and iCloud entitlements, the unused camera and photo purpose strings — the wording was changed from "is being removed" to a statement of fact. Where a claim had not been independently checked, it was narrowed rather than left standing: the assertion that the bundled open-source libraries "do not phone home" was replaced with a scoped statement about our own code plus an open item for the dependency audit; the App Store label wording now says the answer has not been filed yet; the Keychain sentence now says plainly that the app stores nothing there; and the EU/UK section now says the distribution territories are still being decided.

The current version always lives at https://prameyallc.github.io/privacy/omnibuild/. Earlier versions remain in the public repository that publishes these pages: https://github.com/prameyallc/privacy. Policies for all Prameya apps are listed at https://prameyallc.github.io/privacy/.

Questions

Email admin@prameya.legal. If something in this policy does not match what the app actually does, tell us — we would consider that a defect and we would fix it.