How Kloro looks after your firm’s data

Kloro runs on Google Cloud in the United States. The application, its database and the files it stores are all in Google’s us-central1 region.

Every signed-in request belongs to one firm, and a firm’s clients, properties, visits and invoices each carry the firm they belong to.

The plant catalog Kloro curates is shared by every firm. No other firm can see or change the plants a firm adds on its own.

Kloro’s tests set up a second firm to check that one firm cannot see or change another’s records.

When a firm takes payments through Kloro, its clients pay invoices on Kloro’s pay page by bank transfer (ACH) or card, and Stripe processes each payment.

The amount charged comes from the invoice itself, never from the payer’s browser, and each pay link opens only the invoice it was sent for.

Kloro’s website, app and API (kloro.ai, app.kloro.ai and api.kloro.ai) are served over HTTPS with TLS 1.2 or newer, through a Google Cloud load balancer. Google Cloud Armor in front of it limits how many requests any one address can make.

The servers behind kloro.ai, app.kloro.ai and api.kloro.ai take outside traffic only through that load balancer.

Every account in Kloro carries one of four roles: owner, manager, crew lead or crew member. The server enforces those roles, and only owners and managers can open invoices, user accounts or firm settings.

Passwords are stored only as bcrypt hashes, and repeated failed sign-ins lock the account for a while.

Owners and managers can download their clients, properties, employees and materials as CSV files from those pages in Kloro.

To ask for a copy of your firm’s data or for its deletion, email privacy@kloro.ai. When a firm cancels, its data is deleted within 90 days unless the law requires it to be kept.

If you think you have found a security problem in Kloro, email hello@kloro.ai with what you found and the steps to see it.