Privacy policy

Who we are

Calcoolate.io is run by CIOBO bv, Heirweg 1A, 9840 De Pinte, Belgium, enterprise number BE1031.311.918. We are the controller of the personal data this policy describes.

Questions about this policy or your data go to viktor@ciobo.be.

What we store about you

When you register, we store your email address and a hash of your password. We never store the password itself.

In Account settings you can add your name and your company's name. We also store your language, your units and decimal separator, how your changes are saved, your default calculation and bill of materials profiles, and the version of the terms of use you accepted and when.

To run your account we store whether your email address is confirmed and your account approved, when the account was created and last changed, and one-time tokens for confirming your email address and resetting your password.

An account can be logged in on one device at a time. For that we store an identifier for the browser you're logged in on and when it was last active.

Your project data

The locations, installations, lines, consumers, operating conditions, profiles and calculation results you enter are stored with your account. We use them only to run the calculations and exports you ask for and to show them back to you. We don't sell them or share them with anyone.

Problem reports and error reports

When you send a report with the "Report a problem" button, we receive your description, your email address, the page you were on, the location or installation you had open, your browser's user agent and the app version. We store the report as an issue in our private issue tracker on GitHub and get a copy by email.

When the app runs into an error in your browser, it sends us the error message, its technical trace, the page, the app version and, if you're logged in, your user number. The server logs its own errors with the same details. We use these reports only to find and fix bugs.

Who processes the data for us

Hostinger runs the server the app lives on and sends the app's emails.

Neon hosts the database, in Frankfurt, Germany.

GitHub, Inc. hosts our issue tracker in the United States, so problem reports leave the EU. GitHub takes part in the EU-US Data Privacy Framework.

Each of them processes the data only on our instructions.

Cookies and local storage

We set two cookies, and only when you log in: a login cookie valid for 15 minutes and a renewal cookie valid for 7 days. Both are needed for the app to work, and scripts on the page can't read them.

Your browser also keeps your theme, your language, the identifier of your browser and which sections you folded open or closed. This stays on your device.

We use no analytics, no tracking and no third-party cookies.

Why we may process the data

We process your account and project data to provide the app you signed up for. We process problem reports, error reports and server logs because we have a legitimate interest in keeping the app working and secure.

How long we keep it

We keep your account and project data for as long as your account exists.

When you delete your account in Account settings, we close it straight away and nobody can log in to it. We keep its data for 30 days in case you want the account back, then delete it. Our database backups lose their copy 6 hours after that. Ask us and we delete it sooner.

Problem reports stay in the issue tracker for as long as we need them to follow up the problem. We keep server logs for 14 days.

Your rights

You can ask us which data we hold about you and get a copy of it. You can correct your details yourself in Account settings, and export your installations to Excel to take them elsewhere.

You can delete your account yourself, or ask us by email to erase your data for good. You can also object to how we use your data, or ask us to restrict it.

Send any of these requests to viktor@ciobo.be. If you think we handle your data wrongly, you can complain to the Belgian Data Protection Authority (www.dataprotectionauthority.be).

Changes to this policy

When what we store or why changes, we update this policy and the date at the top.