Skip to content

Your information

Privacy Policy

This policy explains what information Runcina handles, why we handle it, who may receive it, and the choices available to account holders and other people whose information is stored in Runcina.

Effective 24 August 2026 · Updated 17 October 2026

1. Scope and responsibility

This policy applies to the Runcina website, web application, mobile applications, customer portals, and support interactions (together, the Service). Runcina provides business-management software for lawn care operators and their teams.

Runcina is responsible for account, service, support, billing, security, and usage information that we collect. A business account owner controls the operational records that they and their team enter about clients, properties, staff, jobs, quotes, invoices, payments, expenses, and communications. That business is responsible for having a lawful reason to enter and use those records.

2. Information we collect

Account and identity information

We collect information such as name, email address, email-verification status, authentication provider, account role, team membership, and account creation and update times. If you choose Google, Facebook, or Apple sign-in, we receive the account details that provider makes available with your permission.

Business and operational information

Depending on the features used, the Service may hold:

  • business name, contact details, logo, address, tax identifiers, invoice settings, and payment instructions;
  • client and site contacts, property addresses, access notes, job notes, schedules, assignments, and job history;
  • quotes, invoices, payments, expenses, reports, purchase orders, and customer portal submissions;
  • photos, receipts, imported files, exported records, and other content uploaded by users;
  • messages, delivery status, opt-out preferences, and support correspondence; and
  • team invitations, roles, ownership changes, and security or audit events.

Device, usage, and technical information

We may collect IP address, device and browser type, operating system, app version, session times, feature and screen usage, subscription state, diagnostic events, and identifiers used to secure and operate the Service. Runcina disables advertising identifier collection in its app configuration and does not use business records for third-party targeted advertising.

Optional website and web-app analytics

When optional analytics is enabled, we ask before loading Google Analytics on the website or web app. You can choose No thanks and keep using the service, or change your choice through Privacy choices. The website and web app save choices separately because they use different web addresses. A browser's Global Privacy Control keeps optional web analytics off.

If you allow analytics, we record selected page visits, signup actions and first steps such as creating a customer, importing records, setting up recurring work, completing a job and creating an invoice. We use approved campaign labels, counts and a random journey identifier to understand these steps across the website and web app. We do not include customer records, form text, account identifiers, full page addresses or referring page addresses in these events.

Your choice and, if allowed, the campaign and journey identifier are saved in this browser and expire after 30 days. Expired values are discarded when you return. Analytics cookies are set for up to 30 days. Choosing No thanks stops future optional events and removes this browser's saved journey and accessible analytics cookies; it does not erase events already received by Google. The journey identifier may be included in a signup link after you allow analytics on the website, and the web app requires its own choice before using it. Other devices, private browsing and blocked storage can break this connection.

Camera, photos, files, addresses, and weather

Runcina requests camera or photo-library access only when a user chooses to capture or upload an image. Weather-aware scheduling is planned after launch and is currently unavailable. When enabled, a property address may be geocoded into an approximate location and used to obtain a forecast. Opening a map sends the selected address to the map provider. Runcina does not currently use continuous background device-location tracking.

3. How we use information

We use information to:

  • create accounts, authenticate users, enforce team permissions, and keep records synchronised;
  • provide scheduling, field-work, quoting, invoicing, reporting, payment, accounting, and messaging features;
  • send service, security, billing, and user-configured customer communications;
  • provide support, investigate faults, prevent fraud or misuse, and protect the Service;
  • measure feature performance and improve reliability and usability; and
  • comply with legal obligations and enforce our Terms of Service.

4. When we share information

We disclose information only as needed for the Service, including to:

  • Google Firebase and Google Cloud for authentication, databases, storage, server functions, hosting, and analytics;
  • Expo for application delivery, updates, and related mobile infrastructure;
  • Google, Facebook, or Apple when a user chooses that sign-in method;
  • Stripe for Runcina subscriptions, connected payment accounts, checkout, and payment confirmation;
  • Xero when a business chooses to connect an organisation and export accounting records;
  • Resend for customer emails sent through Runcina. Automatic reminders and Twilio SMS delivery are planned after launch and are currently unavailable;
  • Apple or Google map services when you open a property address in a map. Open-Meteo is the planned forecast provider for weather-aware scheduling, which is currently unavailable; and
  • professional advisers, regulators, law enforcement, courts, or a successor business where disclosure is lawful and necessary.

Business owners, administrators, and authorised team members share visibility of business jobs, customer and property details, quotes, invoices, payments, expenses, and saved business settings. This visibility includes records beyond a member’s assigned visits. Roles govern which actions each person can take. See team roles and shared records before inviting staff. Some optional providers, such as Stripe, Xero, and sign-in or map providers, also process information under their own terms and privacy policies.

No sale of personal information. Runcina does not sell personal information or business records.

5. International processing

Runcina and its providers may process information outside the country where it was collected, including in the United States and other locations used by those providers. Privacy protections and government-access rules may differ between countries. We select established providers and use available contractual, technical, and organisational safeguards appropriate to the service involved.

6. Security and retention

We use access controls, authenticated requests, role permissions, encrypted network connections, server-side validation, and provider security controls. No online service can promise absolute security, so users should protect their credentials, devices, exported files, and team access.

We generally keep account and business records while the relevant account is active. Following a valid deletion request, we delete or de-identify active-service data unless it must be kept for legal, tax, payment, security, fraud-prevention, backup, or dispute-resolution purposes. Residual copies may remain in protected backups until they expire through normal provider backup cycles. Connected providers may retain information under their own legal obligations.

While deletion is pending, a restricted recovery record holds the identifiers and billing references needed to complete the request safely. After completion, those recovery details are removed. Minimal completion and retired-business markers remain to prevent stale sessions and delayed service events from recreating deleted records. See the deletion process for timing and retained information.

7. Your choices and rights

Depending on your location and relationship with Runcina, you may ask to:

  • access or correct personal information;
  • export business data if your role permits it;
  • withdraw an optional permission or disconnect an integration;
  • opt out of eligible messages; or
  • delete your account and associated data.

Account holders can use Settings > Data Management to export eligible data or start account deletion. Anyone unable to access the app can use our public account-deletion page. We may need to verify identity and authority before fulfilling a request. A client or employee whose information was entered by a Runcina business should normally contact that business first; they may also contact us for assistance.

8. Children, changes, contact, and complaints

Runcina is a business service and is not directed to children under 18. We may update this policy when our practices or legal obligations change. The effective date above identifies the current version, and we will provide additional notice when a material change requires it.

To ask a privacy question, request access or correction, or make a complaint, email admin@runcina.app. Describe the request and the Runcina account or business involved, but do not send passwords, full payment-card details, or unnecessary client records. We will review the request and explain any verification or next steps.

Free operator tools and quote drafts

Information entered in a public tool stays in memory and, where available, this browser tab's session storage for recovery for up to 24 hours. Clear your draft on shared devices. Printing does not upload your quote.

Saving a public-tool draft directly to a Runcina account is currently unavailable. If this feature is enabled, explicitly choosing to save transfers the details to a temporary server record. Unclaimed records expire after 24 hours. Claiming binds the draft to your account and extends its expiry to seven days. Saving creates a business quote and removes the temporary payload. Expired temporary data is queued for deletion; expiry prevents further access even before cleanup completes.

Quote content, customer contact details, addresses and transfer tokens are excluded from analytics. If enabled, functional transfer works without analytics consent. A short-lived hashed network bucket limits abuse; application records do not retain raw IP addresses.