Prameya Privacy

OmniBuild Privacy Policy

Effective date: August 8, 2026
Publisher: Prameya LLC ("Prameya", "we", "us"), a United States limited liability company
App: OmniBuild for iPhone and iPad
Contact: admin@prameya.legal

This policy covers the OmniBuild app only. 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


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 logs — projects you have worked on, recurring maintenance you have done, and decisions you have made — so you can see your own consistency over time.

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.


Information the app stores on your device

Everything in this table lives in OmniBuild's own storage area on your device. None of it is sent to Prameya.

What Examples Where it lives
Project logs Project name, date, how far along it is, your own notes, the method or framework you used, and any cost estimate you type in yourself App database on device
Maintenance and habit logs The kind of task, the date, how thorough you were, minutes spent, your notes App database on device
Decision entries A title, the framework you used, the options you considered, what you chose, and your later reflection App database on device
A small profile How many projects you are aiming for per quarter and which areas you are focused on App database on device
App preferences Light/dark appearance choice, which AI model you selected, which models you have already downloaded, and download resume information so an interrupted download can continue Device settings storage

The cost figures in your project and decision logs are numbers you type. They are your own estimates. The app does no lookup and no comparison against any pricing database.

Apple's normal device backup (iCloud Backup or an encrypted computer backup) may include app data, because that is how iOS backups work for every app. That is a setting you control in iOS, between you and Apple. Prameya has no access to your backups.


The one time OmniBuild uses the network

OmniBuild makes one, and only one, outbound internet connection of its own.

Downloading the AI model. The on-device AI is optional and off until you turn it on. When you tap to download and load the model in Settings, the app fetches the model files over HTTPS from Hugging Face (huggingface.co), which hosts open-weight models. Concretely:

The app also watches your device's own network status (for example, whether you are on a constrained or expensive connection) so it can pause a large download and not burn your data plan. That check happens entirely on the device and sends nothing anywhere.

All connections are made over HTTPS. The app is configured to refuse unencrypted connections.

That is the whole picture for the code we wrote. The model download is the only network call in Prameya's own source code, and no code path anywhere in the app transmits your content. Prameya operates no backend for this app. There is no endpoint that could receive your content, because we did not build one. The app also compiles in open-source libraries whose internal network behaviour we have not yet finished auditing; we say what we can and cannot vouch for about those under Third parties below.


Where the AI runs

The AI runs on your device, using Apple's MLX framework and the model file you downloaded. Your prompts, your logs, and the summaries the app generates are processed locally in the app's memory and storage. The app ships a single text-only model in its catalogue and calls no third-party AI service.

We want to be precise rather than flattering here:

So "nothing you write leaves your device" is true. "The app never touches the internet" would be false, and we are not going to tell you that.


Device permissions

OmniBuild asks for no device permissions in normal use.

Permission Does OmniBuild use it?
Camera No. There is no camera feature.
Photos No. The app does not read or write your photo library.
Location No. The app never asks for or uses your location, precise or approximate.
Microphone No.
Contacts, Calendar, Reminders No.
Health / HealthKit No. See the section below.
Notifications No. The app sends no push or local notifications.
Motion and fitness No.

A note about jobsite features. OmniBuild is described as jobsite support. That support is informational — reference content, citations, and your own logs. 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 permission purpose strings at all and contains no code that requests a permission, so no permission prompt can appear.


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.

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:


Accounts, sign-in, and cloud sync — none of them

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. There is no authentication code in the app at all.

OmniBuild also does no cloud sync. Your logs do not travel between your devices through the app, and they do not reach iCloud through anything the app does.

An earlier build shipped a dormant sync component and iCloud entitlements. It set a timestamp and wrote a log line; it transmitted no records to anywhere. It was never reachable from any screen — there was no working "Sync Now" button a user could press. That component has been deleted, along with the iCloud container and the CloudKit and CloudDocuments entitlements, and the unused Sign in with Apple import and keychain accessors. The current build declares only two entitlements: the iOS app sandbox and outbound network client access. If we ever build real sync, it will be off by default, it will be explained here before it ships, and this policy will say exactly what syncs.


Things OmniBuild does not do

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


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, no in-app purchases, and no social or messaging features.

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 off your device to us. There is therefore no children's personal information for us to hold, use, disclose, or delete.

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 for OmniBuild has not been filed yet. When we file it, the answers will match this section: with no health, wellness, or medical feature in the app, 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.

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 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 is governed by Apple's own privacy policy, not this one.


Deleting your data

Because your data is on your device, deletion is under your control and is immediate.

  1. Erase your logs: open Settings inside OmniBuild and tap Clear All My Logs & Decisions. This deletes your project logs, maintenance logs, and decision entries. It cannot be undone.
  2. Remove the downloaded AI model: deleting the app removes the model files, which live inside the app's own storage.
  3. Erase everything: delete OmniBuild from your device. 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 on-device data is retained for exactly as long as you keep it. Support correspondence is retained as described above.


Security

Honest, specific statements only:

No system is perfectly secure, and the strongest protection for your on-device data is your device passcode or biometric lock.


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 where you can see and erase it yourself.

California (CCPA/CPRA)

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

How this applies to OmniBuild:

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:

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 itself contains no third-party services that receive your data. For completeness, here is everyone in the picture:

Who What they get Why
Hugging Face An HTTPS request for a public AI model file, plus your IP address and standard HTTP headers It hosts the open-weight model the app runs on your device
Apple Your App Store activity, and your device backups if you enable them It operates the App Store and iOS
Our email provider Only what you send to our support address It carries our email

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

The app also builds on open-source software libraries — Apple's MLX machine-learning framework and the supporting Swift packages that load and download models. These are code compiled into the app, not services we have a relationship with, and nothing in our own code hands them your logs, your notes, or anything you typed. We have not yet completed an independent audit of the network behaviour of every one of those packages and their transitive dependencies, so we are not going to tell you flatly that none of them ever contacts a server. What we can tell you is what we have checked: in the code Prameya wrote, the Hugging Face model download is the only outbound connection, and no code path transmits your content anywhere. When that dependency audit is finished, we will update this paragraph to say what it found.


App Store privacy labels — a note on wording

The App Store privacy label answer we will file for OmniBuild is "Data Not Collected". The app has not been submitted yet, so that answer is not yet on the App Store listing; when it is filed, it will be that one. 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. Nothing about your content is transmitted, so nothing is collected. It also matches the privacy manifest shipped inside the app, which declares 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.

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/. 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.

Prameya LLC · Effective August 8, 2026