Privacy Policy

RANCHASSIST™ RANCH MAP BUILDER

PRIVACY POLICY

Effective date: August 31, 2026

This Privacy Policy describes how the standalone RanchAssist™ Ranch Map Builder (“Ranch Map Builder,” “the Tool,” “we,” “us,” or “our”) is designed to handle information when you use it.

This policy is written for the Ranch Map Builder product architecture described below. If a particular deployment adds analytics, advertising, authentication, cloud storage, or another data service, the operator of that deployment should update this policy before publication so it accurately describes the deployed service.

1. PRODUCT DESIGN AND PRIVACY MODEL

Ranch Map Builder is designed as a standalone, session-first ranch mapping utility.

The standard product architecture:

• Does not require a RanchAssist user account.

• Does not require a RanchAssist-hosted project database for standalone project data.

• Does not use localStorage as long-term project storage.

• May use browser sessionStorage to protect the active session from accidental refresh or same-tab interruption.

• Lets you save the complete editable project locally as a RanchAssist .ra project file.

• Lets you export files such as GeoJSON, CSV, PNG, or print/PDF output.

• Lets you explicitly initiate sharing actions such as Copy Summary or Email.

RanchAssist’s project-file principle is that you should be able to keep your work without requiring RanchAssist to keep your project data.

2. INFORMATION YOU ENTER OR CREATE

Depending on how you use the Tool, your project may contain information such as:

• Project or map name.

• Ranch boundaries, pasture polygons, fields, traps, no-graze areas, wooded areas, and custom area geometry.

• Fence, road, water-line, cattle-lane, electric-fence, creek, drainage, or custom line geometry.

• Gates, ponds, troughs, wells, pumps, structures, corrals, feeders, cattle guards, culverts, hazards, incidents, and custom point locations.

• Feature names.

• Notes.

• Optional dimensions or capacity information.

• Layer visibility, locking, ordering, and style settings.

• Map camera position and map preferences.

• Geometry-derived measurements.

Under the standard standalone architecture, this project information is handled in the active browser session unless you explicitly save, export, or share it.

3. SESSION STORAGE

The Tool may use sessionStorage to protect the current active project from accidental refresh, same-tab navigation, or temporary interruption.

sessionStorage is not presented as permanent cloud saving.

The exact lifetime of browser session storage depends on the browser and device. You should not rely on sessionStorage as your only long-term copy of important work.

If you want to continue later, save a RanchAssist .ra project file before leaving.

4. RANCHASSIST .RA PROJECT FILES

A .ra file is a user-controlled RanchAssist Project File.

When you choose Save Project, the Tool can serialize the editable project into a local file containing project metadata and state required to restore the work.

A standard .ra project may include:

• Project UUID.

• Project name.

• Ranch Map Builder tool ID and version.

• RanchAssist project-file format version.

• Creation and last-saved timestamps.

• Editable feature geometry.

• Feature attributes and notes.

• Layer order and visibility.

• Styles.

• Measurements and relevant settings.

• Map preferences and camera state.

The file is saved to your device or through your browser/device’s file-saving workflow. RanchAssist does not treat the existence of a .ra file as RanchAssist cloud storage.

You control where that file is kept and who receives it.

Do not share a .ra file with people who should not have access to the ranch information contained in it.

5. EXPORTS

You may choose to create outputs such as:

• GeoJSON.

• CSV feature inventory.

• PNG map image.

• Print or PDF report.

• Copied text summary.

• Email summary.

Once an export leaves the Tool and is stored on your device, attached to a message, uploaded elsewhere, or shared with another person, the receiving device, application, service, or person controls that copy.

6. EMAIL SHARING

If you use the Email sharing feature, you provide the destination email address and initiate the send.

The Google Apps Script version of Ranch Map Builder is designed to use server-side Google Apps Script MailApp for email sharing.

The deployment operator and Google may process information necessary to send the email, including recipient information and message content.

Do not use email sharing for information you do not want transmitted through email systems.

7. MAPBOX AND MAP SERVICES

Ranch Map Builder uses Mapbox GL JS for mapping functions such as map rendering and satellite imagery. A deployment may also use Mapbox services for place/address search and related map functionality.

When the Tool requests map tiles, imagery, geocoding/search results, or other Mapbox resources, Mapbox may receive technical information associated with those requests, such as IP address, browser/device information, requested map resources, and approximate interaction context, according to Mapbox’s own privacy practices and the configuration of the deployment.

RanchAssist users are not expected to provide Mapbox developer credentials. The application owner configures the browser-safe access token used by the deployment.

RanchAssist project files and standard exports should not contain Mapbox access tokens or other deployment credentials.

8. DEVICE GEOLOCATION

If you choose to use the geolocation feature, your browser or device may ask for permission to provide location information.

The Tool does not need device geolocation to function; you can navigate or search the map manually.

The precision and handling of device location depend on your browser, device, operating system, and map services involved.

Do not treat device geolocation as survey-grade positioning.

9. GOOGLE APPS SCRIPT AND HOSTING

The primary RanchAssist deployment target is Google Apps Script.

Google and the deployment operator may process technical information required to serve the web application and execute server-side functions.

If the Tool is adapted to another hosting platform, that platform may process similar technical request and operational data.

The operator should update this policy if the deployed hosting or logging configuration materially changes the information practices described here.

10. TECHNICAL LOGS

Hosting platforms and third-party service providers may generate standard technical logs for reliability, security, rate limiting, or error diagnosis.

The RanchAssist configuration standard prohibits intentionally logging private API credentials and requires private secrets to remain server-side.

Technical logs should not be treated as project storage.

11. API KEYS AND CREDENTIALS

RanchAssist users should never be asked to provide developer-level credentials such as:

• Mapbox secret tokens.

• Private API keys.

• OAuth access tokens.

• Service account keys.

• SMTP passwords.

• Webhook secrets.

Application-level credentials are configuration controlled by the deployment owner.

Credentials must not be serialized into .ra project files, browser project state, CSV/GeoJSON exports, map reports, or user notes.

12. COOKIES, ANALYTICS, AND ADVERTISING

The standard Ranch Map Builder product specification supplied for this build does not require user accounts, analytics, behavioral advertising, or long-term browser cookies for project persistence.

However, the hosting platform, mapping provider, or a later deployment may use cookies or similar technologies for their own service delivery, security, or functionality.

If the published deployment adds analytics, advertising, consent tools, account authentication, or other tracking technologies, this section must be updated before publication to accurately identify those technologies and the choices available to users.

13. DATA RETENTION

Project data:

• Active session data may remain in sessionStorage for the life of the browser session, subject to browser behavior.

• Saved .ra, GeoJSON, CSV, PNG, and PDF files remain under the control of the user/device or any service to which the user sends them.

• RanchAssist does not, by the standalone design, create a permanent RanchAssist-hosted project record merely because you use the Tool.

Email and infrastructure data:

• Retention by Google, Mapbox, hosting providers, or email systems is governed by their systems and applicable terms/policies.

14. CLEAR SESSION / CLEAR MAP

When you use Clear Session or Clear Map, the Tool is intended to clear the current browser-session Ranch Map Builder project state and related sessionStorage.

This action does not delete files you already saved to your device or shared elsewhere.

15. SECURITY

RanchAssist is designed to separate deployment credentials from user project data.

The project-file standard prohibits executable code in .ra files and requires import validation.

No internet-connected application or device can guarantee absolute security. Keep saved ranch project files in locations appropriate for the sensitivity of the information they contain, and share them deliberately.

16. CHILDREN’S PRIVACY

Ranch Map Builder is a ranch operations utility and is not designed as a service directed to children.

17. YOUR CHOICES

You can:

• Use the Tool without creating a RanchAssist account under the standard standalone architecture.

• Decline browser geolocation and navigate/search manually.

• Choose whether to save a .ra project file.

• Choose whether to export or share project information.

• Clear the current session.

• Control access to the local files you create, subject to your device and other services you use.

18. THIRD-PARTY SERVICES

Ranch Map Builder may depend on third-party services such as Google Apps Script and Mapbox.

Those providers operate under their own terms and privacy policies. RanchAssist does not control how an independent third-party service handles information outside the RanchAssist application.

19. CHANGES TO THIS POLICY

This policy should be updated when the product’s data practices materially change.

A published revision should include a new effective date.

20. CONTACT

For privacy or support questions, use the Contact or Help options published on:

https://ranchassist.com

21. OPERATIONAL MAPPING NOTICE

Mapped ranch boundaries, feature locations, and measurements may reveal sensitive operational or property information.

Consider who should receive exported project files, screenshots, reports, or GeoJSON.

Mapped boundaries and measurements are for operational planning and are not a legal survey.