Skip to main content
GITiempoBack to home

LEGAL

Privacy Policy

This policy explains how ITSUA handles personal data when you use GITiempo, including its Chrome extension.

Last updated: 13 October 2026

1. Controller and contact

ITSUA is responsible for the processing described in this policy. For privacy questions or requests, emailadmin@itsua.com.

2. Information we process

  • Account and profile information, including your email address, authentication identifier, name, and profile image when supplied by your sign-in provider.
  • Workspace, project, task, and time-entry information, including the timers you manually start and stop. Records are available to authorized workspace members according to their roles and project access.
  • GiTiempo access and refresh tokens in the extension’s chrome.storage.local. Google and email/password sign-in also use Firebase Authentication, which stores authentication state in extension-local IndexedDB. Your email and password are submitted to Firebase for email/password sign-in; GiTiempo receives a Firebase identity token to establish its own session.
  • A local, token-free status flag when Firebase sign-out needs to be retried. This flag survives reopening the extension and is removed after provider cleanup succeeds.
  • When you start a timer from a supported GitHub issue page, the repository name, issue number, visible issue title, and canonical direct issue URL sent to GITiempo to create or start the linked time entry.
  • Service access and diagnostic logs used to investigate errors and protect the service. Error messages may include information related to the account or operation involved.

The extension reads the current issue context to recognise a supported GitHub surface and show its control. When you choose to start a timer, it sends the repository name, issue number, issue title, and canonical direct issue URL. Query parameters, fragments, and the Projects board URL are not sent. For managed projects, GiTiempo verifies access and retrieves issue information through the workspace GitHub App installation. For external-reference projects, it records the context you supply without retrieving it through the GitHub API or verifying your GitHub access. This integration does not monitor your general browsing history or passively record your activity.

A workspace can reuse the same external project and issue task for multiple members. Tracking alone lets you see your own time and the projects and exact tasks containing your entries, including a running entry. It does not expose other members’ time or tasks. Workspace administrators and people with separately granted project access can see records according to their permissions. Removing or moving your last entry removes the access derived from it; shared records and separate project access may remain.

3. How we use information

We process this information to authenticate you, maintain your session, provide time tracking and workspace features, link a timer to GitHub issue context when you choose to start one, protect the service, and meet legal obligations. We do not sell personal data or use GitHub page content for advertising.

4. Sharing and authentication services

We share information with the following providers that help operate GITiempo, with authorized workspace members for time tracking, or where required by law.

  • Hetzner Online (Germany, European Union) — primary hosting for the GITiempo API and database.
  • Cloudflare (global edge network) — content delivery and DNS for the GITiempo web applications.
  • Firebase / Google — Google and email/password authentication. Firebase processes authentication identifiers and the credentials you submit for email/password sign-in.
  • GitHub — if you choose GitHub sign-in, GitHub provides identity information through the GiTiempo authentication service. GitHub also supplies repository and issue information for managed tasks and separately authorized browsing or imports. External-reference timer starts do not request this information from GitHub. GitHub account linking is optional and separate from signing in to GiTiempo.
  • Backblaze (European Union) — encrypted backup storage for the GITiempo database.
  • Google (Gmail) — transactional email delivery for account invitations and service notifications.

We also use Slack for operational error notifications. These notifications do not contain users’ personal data.

Our handling of all extension user data, including GitHub-derived data and information received from Google APIs, follows the Chrome Web Store User Data Policy and its Limited Use requirements. We use this data only to provide or improve the extension’s disclosed time-tracking purpose. We do not sell it or use or transfer it for advertising, creditworthiness assessment, or lending.

Transfers are limited to supporting that purpose, meeting legal requirements, preventing abuse, or a business transfer with your prior explicit consent. Human access is limited to your explicit consent for specific data, security needs, legal obligations, or aggregated and anonymized data for internal operations.

Primary hosting and database storage are located in Germany (European Union). Encrypted backups are stored in Backblaze B2’s EU-Central region. The other providers listed above may process information outside your country, including outside the European Union. These hosting locations do not mean that all processing takes place within the European Union. Contact the privacy email above for information about international processing and the safeguards applicable to your data.

5. Retention and security

Storage and deletion depend on the type of information:

  • Account, workspace, project, task, and time-entry data: these records currently remain in the service until manually deleted. Becoming inactive or leaving a workspace does not automatically delete your account or its related records.
  • Encrypted database backups: the backup schedule keeps 90 daily and 52 weekly snapshots, normally covering approximately three months and one year respectively. Older snapshots are removed when scheduled backup pruning runs. Backup data is encrypted before it is sent to the storage provider.
  • Service logs: our monitoring log store is configured for 30-day retention. This does not apply to every copy: application and access logs on the service host currently have no fixed automatic deletion period. Operational notifications sent to Slack do not contain users’ personal data.
  • Authentication and invitation records: access tokens are valid for 15 minutes; refresh tokens and unaccepted workspace invitations expire after 7 days. Expiration prevents further use but does not itself delete the associated stored records. There is currently no scheduled cleanup of expired refresh-token, OAuth-state, or invitation records.

We use authentication controls and encrypted database backups to protect information. Human access to extension user data is subject to the Limited Use restrictions described above. No method of transmission or storage is completely secure, so please protect your account credentials and keep your browser up to date.

You can report a suspected security or privacy incident through the privacy contact above. Applicable data-protection law determines our obligations to notify affected individuals and supervisory authorities.

6. Your choices and rights

Successful extension sign-out clears its GiTiempo session and extension-local Firebase authentication state. If provider cleanup fails, use Retry sign-out in the popup, including after reopening it. Backend session revocation is attempted but may fail when the service is unavailable. Signing out does not sign you out of the GiTiempo web apps or Google/GitHub websites.

Signing out or uninstalling the extension does not delete server-held account, workspace, or time-entry records and does not stop a running timer. To request access, correction, deletion, or a portable copy of your personal data, contact the privacy email above and describe your request. Applicable data-protection law determines the response deadlines and any permitted limitations on these rights.

Account deletion requests. Account deletion is not currently available as a self-service action. ITSUA receives requests through the privacy email above, and a technical administrator handles deletion manually. This process covers your profile, related personal records, and your Firebase authentication account where one exists, subject to applicable legal limitations. Removing your workspace membership alone does not perform this deletion. Records shared with a workspace are considered separately when handling your request.

Removing information from the live service does not immediately remove copies already included in encrypted backups. Those copies may remain until the relevant snapshots are removed under the backup schedule described above.

Depending on where you live, you may also have rights to restrict or object to processing, to data portability, and to complain to your local data-protection authority.

7. Optional landing-page analytics

When Google Analytics 4 is configured for our homepage, it loads only after you choose Allow analytics. It measures page views and clicks on the entry buttons for the user and admin apps. Page views contain the page title and a page location limited to its origin, path, and approved campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, dclid, gbraid, and wbraid). Button events contain only fixed button-location and destination-app labels. We exclude URL fragments, other query parameters, form values, and account, workspace, project, task, or repository data from these events.

Google processes these measurements and may use analytics cookies and browser or network information. Your consent choice is saved in this site’s local storage. Advertising consent remains disabled. These measurements are separate from the browser extension, which does not collect analytics, and this Privacy Policy page runs no analytics scripts.

You can decline analytics or change your choice through Analytics settings in the homepage footer when analytics is configured. Declining stops subsequent analytics events from our integration and attempts to remove accessible analytics cookies. Cookie removal is best effort; withdrawing consent does not delete information already received by Google. When analytics is not configured, the homepage emits no analytics controls or Google tag.

8. Changes to this policy

We may update this policy when our service or legal obligations change. We will publish the updated version on this page and revise the date above.