Privacy Policy

1. Introduction

NearOps (“we”, “our”, “us”) operates a white-label, multi-tenant field service dispatch and booking management platform accessible at near-ops.com and its sub-domains. This Privacy Policy explains what personal information we collect, how we use it, with whom we share it, and the rights available to you as an organisation administrator, engineer, or end customer.

2. Information we collect

We collect information in the following categories:

• Account information — name, email address, role (admin / engineer), and organisation name provided during registration.
• Booking information — customer name, contact details, service address, service type, appointment date and time, booking status, and notes.
• Payment information — payment amounts, invoice records, and payout summaries. Full card numbers are never stored on NearOps servers; card processing is handled by Stripe.
• Operational data — engineer availability windows, coverage zones, job completion records, and platform usage logs.
• Google account data — when an engineer voluntarily connects Google Calendar, we access Google Calendar data as described in Section 4 below.

3. How we use information

We use collected information solely to operate and improve NearOps:

• Accept and manage bookings on behalf of organisations.
• Route bookings to the appropriate engineer based on availability and location.
• Sync booking events and availability with Google Calendar (only when authorised by the engineer — see Section 4).
• Process payments and calculate engineer earnings.
• Send transactional notifications (booking confirmations, reminders, updates).
• Provide administrators with reporting and analytics on their organisation's operations.
• Maintain security, prevent fraud, and comply with legal obligations.

We do not sell personal information, use it for advertising, or share it with third parties for their own marketing purposes.

4. Google API Services — Limited Use Disclosure

What Google scopes NearOps requests and why:

• https://www.googleapis.com/auth/calendar.events
  Used to create booking events on the engineer’s selected Google Calendar when a booking is confirmed, update those events if the booking is rescheduled, and delete or cancel events if the booking is cancelled.
• https://www.googleapis.com/auth/calendar.readonly
  Used to read existing events from the engineer’s selected calendar so that NearOps can automatically block availability during commitments already on the engineer’s calendar, preventing double-booking.

Google Calendar data obtained via these scopes is used only for the purposes listed above. Specifically, NearOps:

• Does not use Google Calendar data for advertising or marketing.
• Does not sell Google user data or share it with third parties for any purpose other than operating the calendar sync feature.
• Does not allow humans to read Google Calendar data except to provide or improve user-facing features or as required by law.
• Stores only the minimum Google Calendar data required to maintain booking-to-event references (event IDs). Raw calendar event content from the engineer’s personal calendar is not stored beyond the request lifecycle.
• Revokes access and deletes stored tokens when an engineer disconnects Google Calendar from their NearOps account settings.

Google Calendar integration is entirely opt-in. Engineers initiate the OAuth connection from their account settings and can revoke it at any time. Disconnecting removes NearOps’ access immediately; events previously written to Google Calendar are not automatically deleted from Google, but NearOps will no longer modify them.

5. Data sharing and third parties

We share personal data only in the following limited circumstances:

• Stripe — for payment processing. Card data is entered directly into Stripe-hosted fields and is not stored on NearOps servers. Stripe’s privacy policy is available at stripe.com/privacy.
• Google — when an engineer connects Google Calendar, NearOps acts as an OAuth client to Google APIs. Google’s privacy policy governs Google’s handling of that data.
• Infrastructure providers — cloud hosting and database providers who process data on our behalf under data processing agreements.
• Legal requirements — if required by law, regulation, or a valid legal process.

6. Data security

NearOps applies industry-standard security measures including encryption in transit (TLS), encrypted storage at rest, access controls, and regular security reviews. OAuth tokens obtained via Google are stored encrypted and access-controlled. Despite these measures, no system is completely secure; we encourage users to use strong, unique passwords and to report suspected security issues to support@nearops.com.

7. Data retention

Booking, invoice, and payout records are retained for the lifetime of the organisation account plus a period reasonably required for legal, tax, and accounting purposes (typically up to seven years). Account data is deleted on account closure on request. Google OAuth tokens are deleted immediately when an engineer disconnects Google Calendar.

8. Your rights

Depending on your location, you may have rights including:

• Access to the personal data we hold about you.
• Correction of inaccurate data.
• Deletion of your personal data (subject to legal retention obligations).
• Portability of your data in a machine-readable format.
• Objection to or restriction of certain processing activities.
• Withdrawal of consent (including revoking Google Calendar access) at any time.

To exercise any of these rights, email support@nearops.com. We will respond within 30 days.

9. Children's privacy

NearOps is a business platform and is not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us personal information, please contact us so we can delete it.

10. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email or an in-app notice. Continued use of NearOps after the updated policy is posted constitutes acceptance of the revised terms.

11. Contact

For privacy questions or to exercise your rights, contact us at support@nearops.com.