Privacy Policy

FieldBase Privacy Policy

This Privacy Policy explains how FieldBase handles information when users access the FieldBase website, progressive web app, Android app, cloud-connected features, subscriptions, AI tools, project tools, business directories, and related services.

Effective Date: May 6, 2026

Contact: [email protected]

Plain-English Summary

  • FieldBase stores user-created business and project records so the app can operate.
  • Some data may be stored locally in the browser or app, and some may be stored in Firebase/cloud systems.
  • Payments may be handled by Google Play Billing, Stripe, or another approved payment provider depending on where the purchase is made.
  • Users can request account or data deletion by contacting [email protected].
  • Business directory sharing is optional, and users control whether business details are shared beyond a limited listing.

1. Who We Are

FieldBase is a business operations and project-management application built for contractors, field teams, service businesses, owners, and related users.

FieldBase may include tools for projects, estimates, quotes, schedules, directories, receipts, documents, invoices, employees, roles, permissions, cloud sync, backups, AI assistance, business collaboration, subscriptions, and future marketplace-style features.

2. Information We Collect

The information FieldBase collects depends on how the user chooses to use the app.

Account information

We may collect account details such as name, email address, login identifiers, user ID, company/workspace ID, role, plan status, subscription status, invite status, and authentication metadata.

Business and project records

Users may enter projects, clients, estimates, quotes, materials, labor, equipment, tools, directories, vendors, schedules, receipts, documents, notes, invoices, payment records, financial summaries, and similar business information.

Local app data

FieldBase may store certain records locally using browser storage, local storage, IndexedDB, cache storage, or app storage so the app can load quickly, work offline where supported, preserve settings, and protect user workflow continuity.

Cloud data

When cloud features are enabled, FieldBase may use Firebase or similar cloud services for authentication, database storage, cloud sync, company workspaces, invites, roles, permissions, backup/restore features, and file storage.

Uploaded files

Users may upload receipts, photos, project documents, invoices, estimates, job images, or other files. Uploaded files may include personal, business, client, location, or financial information depending on what the user uploads.

Device, usage, and technical data

We may process technical information such as device type, browser type, app version, operating system, crash/error logs, security scan results, page activity, feature usage, timestamps, and diagnostic information needed to operate and improve FieldBase.

Notifications

FieldBase may use push notifications or app notifications for reminders, project updates, schedule alerts, account notices, subscription notices, support messages, and other user-requested or important app communications. Users can manage notification permissions through their device, browser, or app settings.

3. How We Use Information

FieldBase uses information to provide, secure, maintain, and improve the app.

Operate the app

We use saved information to display dashboards, projects, estimates, schedules, directories, invoices, receipts, business records, role-based tools, and user settings.

Authentication and access

We use account and role data to authenticate users, manage company/workspace access, apply owner/admin/employee permissions, support invites, and control Free, Pro, Business Pro, or add-on access.

Cloud sync and backup

We may use cloud data to sync records across devices, support backup/restore features, preserve account data, and help users recover or transfer information where available.

Payments and subscriptions

We use payment and subscription status to activate paid features, verify entitlement, manage subscription access, respond to billing support requests, and prevent unauthorized access.

Security and abuse prevention

We may use technical and account information to detect errors, prevent abuse, protect accounts, maintain logs, investigate suspicious activity, and enforce app rules.

Support and communication

We may use contact information and support messages to respond to questions, troubleshooting requests, account requests, subscription questions, data deletion requests, and user feedback.

4. Payments, Subscriptions, and Billing Providers

FieldBase may offer paid plans, subscriptions, one-time purchases, add-ons, or future paid services.

Purchases made through the Google Play version of FieldBase may be processed by Google Play Billing where required by Google Play policy. Purchases made through the FieldBase website or other permitted channels may be processed by Stripe or another payment provider. FieldBase does not intentionally store full credit card numbers on its own app servers. Payment providers may process payment method details, billing identifiers, receipts, subscription status, transaction history, fraud prevention signals, tax information, and related billing data under their own policies.

5. AI, FORGE, and Pricing Intelligence

FieldBase may include AI assistance and FORGE-related estimating or pricing tools.

Private user data

User questions, chat history, client names, private addresses, private project details, company-specific records, and private notes should remain private to the user/company workspace unless the user intentionally shares them.

Approved learning signals

FieldBase may use approved, anonymized, non-sensitive pricing or project-building signals to improve estimating, such as item names, categories, unit prices, units, region/state/city signals, source type, timestamps, and confidence.

No professional guarantee

AI and pricing tools are for assistance only. Users must verify prices, taxes, laws, permits, codes, labor, scope, measurements, materials, and contract details before relying on any answer or estimate.

6. Sharing and Disclosure

FieldBase does not sell personal user data as a contact list. We may share information only as needed to operate the app, comply with law, or provide requested features.

Service providers

We may use service providers such as Firebase/Google Cloud, Google Play, Stripe, hosting providers, analytics/diagnostic tools, email systems, storage providers, or similar vendors to operate FieldBase.

Workspace sharing

Information in a company workspace may be visible to owners, admins, employees, invited users, or other participants according to roles, permissions, sharing settings, and user actions.

Business directory sharing

FieldBase may include an optional shared business directory. If a user chooses to share business details, selected listing information may be visible to other users or the public depending on the feature. If a user does not choose to share full business details, FieldBase may only place a limited business name or minimal listing reference in the shared directory, without the full saved business details.

Anonymized pricing signals

Where approved or enabled, FieldBase may use anonymized, non-sensitive pricing signals such as item category, price, unit, region, state, city, source type, and confidence to improve FORGE pricing intelligence. These signals should not include private client names, private addresses, private notes, raw project files, or full private business records from another user.

Legal and safety reasons

We may disclose information if required by law, valid legal process, security needs, fraud prevention, abuse prevention, rights protection, or a merger, acquisition, financing, or business transfer with appropriate safeguards.

7. Data Safety, Security, Updates, and Retention

We use reasonable safeguards to protect user data, but no system is perfect.

FieldBase may use secure transport such as HTTPS, authentication controls, Firebase security rules, role-based access, local storage protections, update notices, backup tools, version checks, service workers, update flags, and security reviews. FieldBase is designed to avoid deleting user-created data during normal app updates, but software updates, cache changes, browser storage changes, user actions, third-party outages, sync conflicts, device failure, corrupted local storage, or unexpected bugs may affect access to data. Users should export or backup important business records before installing major updates, clearing local storage, changing devices, uninstalling the app, or deleting accounts. We keep information as long as needed to provide the app, comply with obligations, resolve disputes, support backups, enforce agreements, and maintain security, unless deletion is requested and legally/technically available.

7A. Diagnostic Telemetry and Support Troubleshooting

FieldBase may use limited diagnostic telemetry to improve app reliability and help troubleshoot user-reported issues.

FieldBase may collect limited app diagnostic information such as page navigation, session activity, app version, device/browser type, notification permission status, error reports, failed app actions, timestamps, and basic feature interaction events. This information is used to improve stability, troubleshoot bugs, verify app updates, support closed testing, and help resolve account-specific support issues.

FieldBase diagnostic tools are not designed to collect passwords, payment details, private message contents, typed form entries, receipt contents, project descriptions, client addresses, or private business record contents.

Users can choose whether to allow FieldBase diagnostic support from the Settings page where this control is available. Turning this option on allows limited troubleshooting diagnostics to help improve FieldBase and resolve app issues. Turning it off does not prevent basic app security, update, or account logs that may be needed to operate FieldBase.

8. User Choices and Controls

Users may have several ways to control their information.

Account settings

Users may update available profile, company, workspace, theme, role, or app settings inside FieldBase where those controls are provided.

Exports and backups

FieldBase may provide export or backup tools. Users should keep independent backups of important business records before deleting data, changing devices, clearing local/app storage, uninstalling FieldBase, or installing major updates.

Local storage

Clearing browser/app storage may remove local FieldBase data from that device. If cloud sync is enabled, some records may still exist in the cloud account unless deleted there as well.

9. Account and Data Deletion Requests

Users can request deletion of their FieldBase account data.

To request account deletion, workspace deletion, or deletion of personal data connected to your FieldBase account, email [email protected] with the subject line FieldBase Data Deletion Request. Include the email address used for your FieldBase account and a clear description of what you want deleted.

Some information may be retained when required for security, legal compliance, dispute resolution, backup integrity, fraud prevention, payment records, tax records, or legitimate business operations. If data is stored locally on your device, you may also need to clear local app/browser storage or uninstall the app to remove local copies. If you are part of a company workspace, deletion may depend on owner/admin permissions and records that belong to the company rather than only to one user.

10. Children and Age Limits

FieldBase is designed for business and professional use.

FieldBase is not intended for children under 13, and it is not directed to children. Users should not submit children’s personal information into FieldBase. If you believe a child has provided personal information, contact [email protected].

11. International Users

FieldBase is US-first but may be accessed from other locations.

If you use FieldBase outside the United States, your information may be processed in the United States or other locations where our service providers operate. Users are responsible for determining whether FieldBase is appropriate for their local business, privacy, tax, accounting, construction, employment, and recordkeeping requirements.

12. Data Incidents and Support Requests

Users should contact FieldBase support if they believe data was lost, exposed, incorrectly shared, or deleted by mistake.

If you believe your FieldBase account, workspace, shared business listing, project data, uploaded files, or local/cloud records were affected by an error, update, unauthorized access, or accidental deletion, contact [email protected] as soon as possible. Include your account email, approximate date/time, affected feature, device/browser if known, and a description of the issue. FieldBase may review logs, backup records, Firebase records, app versions, and support details where available to investigate and attempt reasonable recovery, but recovery is not guaranteed.

Users should avoid entering highly sensitive personal information unless it is necessary for their business workflow. FieldBase is designed for business/project operations, not for storing medical records, government identification numbers, children’s data, or other highly regulated personal data unless legally permitted and required by the user’s own business obligations.

13. Changes to This Privacy Policy

FieldBase may update this Privacy Policy as the app grows.

We may update this policy to reflect changes in features, cloud sync, AI tools, subscriptions, payment providers, app stores, legal requirements, or business operations. The effective date above will be updated when material changes are made. Continued use of FieldBase after updates means the user accepts the updated policy where permitted by law.

14. Contact

Questions, privacy requests, account deletion requests, billing support, and app concerns can be sent to FieldBase support.

Email: [email protected]

Important Notice: This Privacy Policy is a practical app policy template and not a substitute for professional legal advice. FieldBase should be reviewed by a qualified attorney before large-scale paid launch, advertising, or expansion into additional jurisdictions.