PolyHour

PolyHour Privacy Policy

Effective from 22 October 2026 · Home page · Open PolyHour

PolyHour is a work-time tracking app for 3D artists (a Windows version and a browser version). This policy describes what data the app processes and for what purpose.

Data controller and contact

The data controller is Dominik Pańko, Gdańsk, Poland, the creator of the PolyHour app. Contact in all matters concerning data: support@polyhour.app.

What data we process

What we use data for

Solely to make the app's features work: displaying your data and synchronising it between your devices, synchronising tasks with the “PolyHour” calendar, and switching on the Pro version after a purchase. We do not sell data, we do not use it for advertising, profiling or training models, and we do not share it with anyone other than the infrastructure providers (Google Firebase / Google Cloud), which store it on our behalf, and Stripe as regards payments.

Data from Google APIs

PolyHour's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Synchronisation is performed by the PolyHour server (Google Cloud Functions), so it works on every device. The refresh token for access to Google Calendar is stored in Firestore in a location accessible only to the server and is deleted (and revoked at Google) when you disconnect the calendar or delete your account.

Retention and deletion

Your rights

You have the right to access your data, to have it rectified, erased or transferred (CSV export in the app), and to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych). The legal basis for processing is the performance of a contract, i.e. providing the app service (Art. 6(1)(b) GDPR); we also keep data about purchases for as long as tax and accounting laws require (Art. 6(1)(c) GDPR). The data is stored on Google Cloud servers; it may be processed outside the EEA on the basis of Google's standard contractual clauses.

Security

Data in Firestore is accessible only to the signed-in account owner (Firestore security rules). Connections are encrypted (HTTPS).

Changes

We will announce significant changes to this policy on this page.