Legal

Privacy Policy

What Kloro LLC collects, why we collect it, and what we never do with it.

Last updated October 6, 2026Kloro LLC · Minnesota, United States
On this page

Kloro LLC ("we," "us," or "our") operates the Kloro platform at kloro.ai and the Kloro mobile application (together, the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service. By using Kloro, you agree to the collection and use of information in accordance with this policy.

01Information We Collect

Account information

When your employer creates an account for you, we collect your name, email address, role, and phone number. Account credentials are stored using industry-standard bcrypt hashing — we never store plaintext passwords.

Operational data

As you use Kloro, we collect data necessary to operate the service, including:

  • Property information (addresses, plant inventories, zones, care records)
  • Visit records (scheduled dates, arrival/departure times, form data, activity logs)
  • Time entries (clock in/out, break tracking, activity types)
  • Photos you upload during visits
  • Notes, observations, and client preferences
  • Invoice and payment records

Weather data

We use Open-Meteo weather data to calculate Growing Degree Days (GDD) and generate horticultural advisories. For site forecasts, Open-Meteo receives property coordinates rounded to four decimal places. These coordinates can identify a property's approximate location.

Address geocoding

The US Census geocoder receives a property's street address, including its city, state, and postal code when available, to find its coordinates. If Census cannot locate it, OpenStreetMap Nominatim may receive the street address and available locality information as a fallback.

Device information (mobile app)

When you use the Kloro mobile app, we may collect device identifiers for push notification delivery. We access your camera and photo library only when you explicitly choose to take or attach photos during a visit — we do not access these in the background.

Usage data

We collect standard server logs (IP addresses, request timestamps, browser/device type) for security monitoring and service reliability. We also use Sentry for error monitoring: when something in the app fails, Sentry receives the error and its stack trace, the address of the page it happened on, and browser and device detail — plus a sampled share of requests as performance traces. Authorization headers, passwords, and payment and estimate links are stripped before any of it is sent, and we do not attach your name, email address, or firm to those reports. We do not use advertising trackers, and we never share this data with advertising networks.

Feedback you send us

While you are signed in to the web app, your browser holds a rolling recording of roughly the last minute of your session in memory. It is discarded when you sign out or leave the app, and it reaches us only if you submit the in-app feedback form with that option left on. The same is true of the screenshot the form offers — you can switch either one off before you send.

A feedback report carries your message, name, email address, role and firm, the page you were on, and whichever attachments you left selected. The recording and the screenshot are not masked, so they show whatever was on screen at the time — which can include client names, addresses, schedules, and notes. Screenshots are held in a private bucket that is never publicly readable, and are deleted after 365 days.

Website enquiries and Field Notes

When you ask about Kloro through the get started form, we collect your name, your firm and your email address, and — if you choose to give them — your city or region, your number of crews, and what you run on today. We keep the enquiry so we can answer it and follow up, and Resend delivers a copy to the founders. An enquiry does not subscribe you to anything.

When you subscribe to Field Notes, we collect your email address and the page you subscribed from. Resend sends the emails, with an unsubscribe link in every one. To have an enquiry or a subscription deleted, email privacy@kloro.ai.

02How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve the Service
  • Generate phenology advisories and weather information for planning visits
  • Process invoices and facilitate payment between firms and their clients
  • Send transactional emails (visit summaries, invoice notifications, account invitations)
  • Deliver push notifications for visit assignments and schedule changes
  • Ensure security and prevent unauthorized access
  • Respond to support requests

We do not sell your data. We do not use your data for advertising. We do not build profiles for purposes unrelated to the Service.

03How We Share Your Information

We share your information only in the following circumstances:

  • Within your organization: Data you enter is visible to other users in your tenant (firm) according to their role permissions. Managers can see crew member activities.
  • Client portal: Property owners who access the client portal can view visit summaries, photos, invoices, and property information related to their properties only.
  • Service providers: We use the following third-party services to operate Kloro:
    • Google Cloud Platform (hosting, database, file storage)
    • Stripe (payment processing)
    • Resend (transactional email delivery)
    • Expo (mobile push notification delivery)
    • US Census geocoder (street addresses for geocoding)
    • OpenStreetMap Nominatim (street addresses for fallback geocoding)
    • Open-Meteo (property coordinates for site weather forecasts)
    • Sentry (error monitoring, and the session recording attached to a feedback report you choose to send)
    • Notion (our internal triage of feedback reports, including any screenshots you attach)
    • Anthropic (the AI model behind the client portal's garden assistant — it receives the question asked and the property information needed to answer it)
    We share the data described above to operate these features. Each provider's terms and privacy practices govern its handling of that data.
  • Legal requirements: We may disclose your information if required by law, court order, or governmental regulation.

04Data Storage and Security

Your data is stored on Google Cloud Platform infrastructure in the United States (us-central1 region). We implement industry-standard security measures including:

  • Encryption in transit (TLS/HTTPS for all connections)
  • Encryption at rest (Google Cloud SQL managed encryption)
  • Bcrypt password hashing with salt
  • JWT-based authentication with short-lived access tokens (30 minutes)
  • Role-based access control with multi-tenant isolation
  • Rate limiting on authentication endpoints
  • Automated database backups with point-in-time recovery

Photos are stored in Google Cloud Storage with access controlled by signed URLs. Mobile app authentication tokens are stored in your device's secure keychain (iOS Keychain / Android EncryptedSharedPreferences).

05Data Retention

We retain your data for as long as your organization maintains an active Kloro account. Operational data (visits, time entries, invoices) is retained as business records for the duration of the account. If your organization cancels its subscription, we will delete all associated data within 90 days, unless retention is required by law.

Individual user accounts can be deactivated by your organization's administrator at any time. Deactivated accounts cannot access the Service but associated records are retained for business continuity.

06Your Rights

Depending on your jurisdiction, you may have the right to:

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your personal data
  • Object to or restrict certain processing
  • Request data portability

Because Kloro is a business tool provided by your employer, some requests may need to be directed through your organization's administrator. To exercise your rights, contact us at privacy@kloro.ai.

07Children's Privacy

Kloro is a business application not intended for individuals under 16 years of age. We do not knowingly collect personal information from children. If we learn that we have collected data from a child under 16, we will delete it promptly.

08Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new policy on this page and updating the "Last updated" date. Your continued use of the Service after changes constitutes acceptance of the updated policy.

Kloro LLC

Minnesota limited liability company · Minnesota, United States

Questions about this Privacy Policy or our data practices? privacy@kloro.ai