Know where your field records go.

The demonstration and your team

WellRelay is built by Westcode, an independent studio in British Columbia. The 3D and 2D demonstration uses fictional wells, tanks and simulated readings. Its mobile notebook stays on the device unless you choose to share a copy.

The optional Team workspace lets you create a named account, configure your own asset register and share manually entered records with your team across the phone and website. Demo notebook entries are not automatically copied into a team. Neither workspace connects to live equipment, collects telemetry from a field or controls equipment.

Information saved in a Team workspace

Account information includes your name, email address, account identifier and email-verification status. Firebase Authentication handles sign-in and password verification. Team information includes the team name, membership, roles, invitations and access status.

Your team records can include asset names, site references, units and operating limits; manual measurements and notes; observation and save times; collection volumes, units, ticket references, carrier and destination; ticket photos, extracted text and human-review details; issue owners, next actions, due times and completion evidence; and handovers and receipt acknowledgments. Records identify the person who created or updated them. Only enter information you are authorized to share with the team.

Cloud storage and who can see records

Team accounts and shared records use Google Firebase Authentication and Cloud Firestore. When you sign in or synchronize, information is sent to those services for authentication, storage and retrieval. Current members can read their team’s records and member names, emails and roles. Owners manage invitations and access; owners and supervisors can configure assets. Westcode administers the service and can access service records when needed to operate it or investigate a problem.

Removing team access stops future authorized reads and writes. It does not recall exports, screenshots or copies already stored on someone’s device. Firebase is provided by Google; see Firebase privacy and security information.

Ticket photos and text recognition

You choose whether to attach a photo. Camera access is used only when you choose to take a ticket photo. WellRelay compresses the chosen image to a JPEG and runs printed-text recognition on your device. The scanner downloads public engine and language files when needed; it does not send the photo to an external OCR or AI provider. Text suggestions can be wrong and require your review before the record is saved.

In a Team workspace, the reviewed image, extracted text and collection record are saved on the device first and synchronized to Cloud Firestore with your team access. Current members of that team can open the photo. Ticket photos are retained as shared operational records, including after the author leaves or deletes their account. The public ticket sample is separate, uses fictional data and keeps changes in that browser only.

Device storage and pending changes

The app keeps a local copy of team records and saves pending changes on the device before trying to synchronize them. A pending change is not yet confirmed in the shared team record. The mobile app stores its record archive in AsyncStorage and ticket photos in its private document files; the web workspace uses browser storage and IndexedDB. WellRelay does not add encryption to these local copies.

The demo notebook also stores manual observations, notes, collection tickets, alert acknowledgments and handovers locally. Westcode does not automatically receive that separate mobile demo notebook. Signing out does not necessarily erase cached records. Removing app or browser storage can permanently lose unsynchronized drafts.

Sharing and exports

When you use a native share sheet, the record or archive is passed to the app or destination you choose. A downloaded team archive includes the records cached on that device and pending changes. Ticket photos are stored separately: JSON archives and CSV reports contain photo references, not image copies. Keep original photos separately if you need your own image backup. Reports exclude pending records by default; including them adds a visible sync-status column. Native CSV exports create a temporary file in the app cache for the share sheet. Review the contents and store exports privately. The recipient handles a shared copy under their own settings and policies; deleting an account or local notebook does not recall that copy.

Retention and account deletion

The updated beta retains notebook and team records without the earlier demo’s 100-observation, 100-collection and 40-handover limits. Records already removed by an older build cannot be recovered by updating. Resetting the demonstration after 24 hours changes its scenario, not the saved notebook archive. Team records have no automatic expiry in this pilot.

Use Account settings in the mobile Team workspace or manage your account on the web to delete your sign-in account. You must confirm your password. If you own a team with other active members, transfer ownership to another active member first. A team where you are the only active member closes and becomes inaccessible when you delete your account; its records remain stored. The deletion flow removes your active access and clears that device’s cached team records and unconfirmed drafts. It does not delete the separate demo notebook or copies on other devices.

Authored observations, tickets, issues, handovers and historical membership information remain with the team, including the recorded author name. Deleting your sign-in account does not erase those shared operational records. For a question or request concerning retained information, contact hello@westcode.io and identify the team without emailing confidential field records.

Uninstalling removes local app data; offloading or device backups may retain it. Your operating system or backup provider controls those copies. Uninstalling does not delete cloud team records. Keep an export of records you need before removing local storage; cloud synchronization is not a promise of recovery for an unsaved or unsynchronized draft.

Analytics and beta diagnostics

The mobile app does not include advertising or product-analytics tracking. Authentication and cloud providers process the information needed to run their services. The Westcode website has its own analytics and contact handling, described in the website privacy page.

If you test an iOS build through TestFlight, Apple collects beta usage and crash information and shares information with the developer. Feedback you submit may also include screenshots, comments and contact details. We use the diagnostic information and feedback available to us to investigate problems and improve the app. Apple describes this in TestFlight & Privacy. Operating-system diagnostics, backup services and apps you share to follow their providers’ settings and policies.

Questions or support

Write to hello@westcode.io and mention WellRelay. If you send us a support message, we receive the information you choose to include so we can reply. The Westcode website privacy page describes contact-form, email and website handling; it also covers our separate studio app.

WellRelay support · About the demonstration