Privacy Policy

Wiramo is a field-service workspace application for managing jobs, clients, estimates, invoices and schedules. It is offered as a web application at app.wiramo.com and as Android and iOS applications using the identifier com.wiramo.app.

Wiramo is operated by LBNV LLC, a limited liability company organised under the laws of North Carolina, USA.

Wiramo is used by businesses, which produces two distinct groups of people, treated differently wherever the difference matters.

Workspace users

The staff of a business who sign in and use the application.

Business contacts

The customers, leads and job recipients whose details a workspace's own staff enter into the application.

An account can come into existence in one of four ways: where the deployment you are using offers it, you register yourself on the sign-up page, which records the versions of the Terms of Service and this Privacy Policy you accepted; an authorised user inside a workspace creates it; a workspace invitation is issued and accepted; or the platform operator issues an owner activation. No trial, pricing or billing is active in this release.

Invitation and owner-activation links are valid for 168 hours (7 days). The product does not itself email them; they are distributed outside the product.

From workspace users, in order to operate the account and the workspace:

• Account record: email address, full name, phone number, role, an active or inactive flag, and a password stored only as a bcrypt hash. Your password itself is never stored.
• Workspace business profile: business name, logo, timezone, currency, language, phone, email, website, legal business name, address, licence number and region, accepted payment methods, and estimate settings.
• Audit log: which user performed which action on which record, the recorded change, and the time.
• Presence and session data: a session identifier generated by your device, the workspace, the user, session start, last-seen time, cumulative foreground seconds, and session end.
• Product events: an event identifier, workspace, user, event type, an optional record identifier, a short source label, and a timestamp. This carries a source label only; it is not used to carry customer content.
• Device registration, in the Android and iOS applications: when you sign in, an installation identifier generated by the application, the platform and the environment; if you enable notifications, also the notification token issued by the platform's push service; and a deactivation time if the registration is retired.

About business contacts, entered or imported by a workspace's own staff: client name, email, phone, street, city, state, ZIP, source and free-text notes; job records including the linked client, assigned staff, type, status, title, description, customer and internal notes, scheduled date and time window, estimated and final price, service address, and arrival, start and completion times; job notes, additional items and photos; payment records entered as bookkeeping; leads, including any AI-generated summary and extracted fields; estimates and invoices with their versions, line items, events and delivery records; and the workspace's service catalogue, price list and pricing rules.

Wiramo does not process payments and has no card-entry form. A payment record in Wiramo is a bookkeeping note that a workspace's staff typed, not a processed transaction; like the payment instructions and payment QR images a workspace chooses to show on its invoices, it contains whatever that workspace enters.

• No location. Neither the Android nor the iOS application requests location permission, and the application code contains no geolocation call. Addresses in Wiramo are typed by a person, never sensed from a device.
• No contacts, calendar, SMS, telephone or Bluetooth access.
• No third-party analytics, advertising or crash-reporting library. A repository-wide search of the application source, the Android and iOS projects and every dependency manifest found no such integration, and neither mobile application bundles one. Wiramo shows no advertising. Wiramo's own first-party usage data is described in section 4.
• No raw IP address for reset abuse control. Where a rate limit has to recognise a repeat attempt, the address is stored as a keyed HMAC-SHA256 digest and the email address as a SHA-256 digest, never in the clear.

The Android application declares exactly four permissions: internet access, notifications, the microphone, and an audio-settings permission that the platform requests together with the microphone. The list is enforced as an allowlist by a build check, so a fifth permission arriving through a dependency fails the build rather than shipping unnoticed.

The iOS application declares three permission prompts: the microphone, the camera and the photo library. It declares no location, contacts or calendar permission and no tracking permission. iOS shows a prompt only when you act, never at launch.

• Notifications are requested only after you tap to enable them.
• The microphone is used only for Voice Import, and only from the moment you press Record. Nothing at launch, on resume or at sign-in opens the microphone. If you decline, you can upload an audio file instead.
• The camera is used only when you choose to take a photo for a job, through your device's own camera.
• The photo library is used only when you choose an existing image to attach, such as a job photo, a workspace logo or a payment QR image, through your device's own picker. Wiramo does not read your photo library in the background.

To operate your workspace and its records; to authenticate you and keep the session secure; to produce estimate and invoice documents; to deliver notifications you have enabled; to generate reviewable drafts when you invoke an AI feature; to maintain an audit trail of changes; and to understand aggregate product usage through the first-party session and event data described above.

Several features produce a draft for a person to review: extracting a job from a screenshot, parsing a lead message, turning a voice note into a job draft, and suggesting a reply. Each one runs only when you invoke it, and each one produces something you read and correct before it becomes a record. Nothing in Wiramo makes an automated decision about a person.

When you invoke one of these features, the content it needs is sent to the configured provider for that feature — the message text and any extracted text, the screenshot image, or the recorded audio — together with context assembled from your workspace's own service catalogue. Which providers are active in a given deployment is a configuration fact stated in the section below.

Wiramo sells no data and shares none for advertising. The service providers that can receive data, each only when the corresponding feature is enabled in the deployment you are using, are:

AI text and image processing

Lead message text, extracted text, screenshot images, voice transcripts and job context, when you invoke an AI feature.

Audio transcription

The audio of a voice note you record or upload, when you use Voice Import.

Transactional email

A recipient address and message body, for password reset and for sending an estimate to a customer.

Object storage

Job photos, the workspace logo, payment QR images and other uploaded files. The bucket is private; files are read through signed links that expire after 15 minutes.

Push notification delivery

A notification title and body, a document number, what happened to it, and your device's registration token. A push from Wiramo never carries a customer name, contact detail, address, free text, money amount, token or arbitrary link; the payload is an allowlist.

Database and application hosting

Everything described in section 4 is stored in Wiramo's own database.

Each of these is configured per deployment and is inert unless it is configured. This policy does not yet name the providers active in the production service, or the region and retention terms that apply to each; that list has not been published yet and will be added to this policy.

An estimate or invoice can be shared with a customer as a link. The link carries an access token with a limited lifetime, and the page it opens is marked so that search engines do not index it. Anyone holding the link can read the document until the token expires, so treat the link itself as confidential. A link belonging to another workspace answers as though the document does not exist, rather than as an access error.

• Every workspace's data is separated at the record level, and uploaded files are stored under keys scoped to one workspace.
• Passwords are stored only as bcrypt hashes.
• In the Android and iOS applications, the main in-app web view loads one HTTPS origin only. A link to anywhere else, such as a map destination or an external website, opens outside that view, in the system browser or in the navigation app you choose. Cleartext traffic and WebView debugging are disabled in the shipped builds, and mixed content is disabled in the Android application.
• The application data of the Android app is excluded from cloud backup and from Android device-to-device transfer.
• Every provider endpoint the service calls is HTTPS, and browser access to the API is restricted to an allowlist of origins.

No security measure is perfect, and Wiramo does not claim that one is.

Your workspace's records are kept for as long as your workspace exists, unless a user with the right permission deletes them. Wiramo runs no automatic expiry or purge of your content, with one exception you start yourself: an account or workspace whose deletion you confirm is erased 30 days later, as the account-deletion page describes. The only other automatic deletions are of short-lived rows used for abuse rate limiting.

Users with the appropriate permission can delete individual records: clients (refused while dependent records still exist), jobs, leads and lead screenshots, job notes, additional items and payments, job photos, estimates, invoices, price rules, services, and the workspace logo.

Tokens expire on their own: a password-reset token after 30 minutes, an invitation or activation link after 7 days, a signed file link after 15 minutes, and a sign-in session after its configured lifetime. Expiry stops a token being usable; it is not by itself the erasure of a record.

You can see and correct most of your own account and workspace data inside the application, and users with the right permission can edit and delete business records directly.

A workspace owner can download a limited export of the workspace's operational records from Settings: a JSON file of the business profile, team, clients, leads, services and price rules, jobs with their items, notes, payments and photo details, and estimates and invoices with their lines. It does not include the photos, logos or other files themselves, sign-in credentials, audit records, or device data, and a very large workspace can exceed its size limit. Estimates and invoices can also be downloaded as PDFs. You can delete your own account - or, as the last owner, your whole workspace - yourself in the app under My account; it is erased 30 days after you confirm unless you cancel before then. The account-deletion page describes exactly what happens and what remains. Other requests, including a broader copy of your data, are handled by a person.

Wiramo is a workplace tool intended for business use by adults. It is not directed at children.

This policy may be updated. When it is, the revision date at the top of this page changes.