3T Apps ("we", "our", "us") operates apps distributed through the Atlassian Marketplace. This Privacy Policy describes how we handle information in connection with our apps.
Our apps run on the Atlassian Forge platform. They process data within your Atlassian Cloud instance as needed to provide app functionality. This may include:
Our Forge apps use Atlassian-hosted storage (Forge KVS). Data processed by our apps remains within the Atlassian Forge infrastructure and is subject to Atlassian's security and data residency policies. We do not store your data on any servers outside Atlassian's Forge infrastructure. The Worktime app stores period snapshots, recuperation balances, an audit log and its configuration in Forge KVS, all within your data residency region. External data transfer occurs only in two optional cases: when a DispatchDesk admin explicitly configures a routing provider (GPS coordinates of admin-pinned technician locations and ticket job sites — and, when geocoding is enabled, the postal address composed from a ticket's configured fields — are sent to the customer's chosen provider using the customer's own API key), and when a Worktime admin enables a third-party worklog source or runs the holiday import (described in section 7). No other data is transmitted, and each transfer can be disabled by leaving the corresponding feature unconfigured.
App data stored in Forge KVS persists as long as the app is installed. When you uninstall an app, data is handled according to Atlassian's Forge data lifecycle policies.
As our apps operate within your Atlassian instance, you maintain control over your data through your Atlassian admin controls. Under GDPR and applicable EU data protection law, you have the right to access, correct, or request deletion of personal data. For any privacy-related requests, contact us at privacy@3t-apps.com. Customers requiring a Data Processing Agreement under Article 28 GDPR can request one — see our DPA page.
Our apps are built on Atlassian Forge, which provides enterprise-grade security including sandboxed execution, scoped permissions, and data encryption. We follow Atlassian's security best practices for Forge development. See our Security page for full details.
The TechDesk Schedule Map view and the DispatchDesk Map view load map tile images from OpenStreetMap (*.tile.openstreetmap.org). These are standard public map image requests made by the user's browser within the Forge iframe. No ticket data, user data, or authentication tokens are sent to OpenStreetMap — only standard HTTP requests for static map imagery at the coordinates and zoom level currently displayed. The Leaflet mapping library used to render the map is bundled with the app (not loaded from a CDN). Customers with strict data residency requirements who do not wish to load external map tiles can use the Schedule List view (TechDesk) or list views (DispatchDesk) instead.
TechDesk provides a per-ticket Navigate button that, when clicked by the user, opens Google Maps or Waze in a new browser tab with that ticket's GPS coordinates. The button appears on a ticket's detail view when (a) the linked asset has address or GPS attributes populated and (b) the ticket has reached the status configured as the Navigation Threshold.
This is a user-initiated action — the app does not transmit data to Google or Waze automatically. Coordinates are sent only when the user clicks the link, and only to the destination of the navigation. Google and Waze then process those coordinates according to their own privacy policies. Administrators who do not want technicians to use these external links can leave the Navigation Threshold setting empty, which suppresses the Navigate button entirely.
TechDesk's Schedule Map shows assigned tickets as pins on a map; it does not draw a planned route line across the day's tickets, and it does not hand off a multi-stop itinerary to any external service. Navigation in TechDesk happens one ticket at a time. Multi-stop route planning is a separate DispatchDesk feature — see DispatchDesk.
DispatchDesk's planning map supports real road routing — distance and travel-time estimates for the routes a dispatcher draws between admin-pinned technician locations and ticket job sites. Routing operates on a bring-your-own-key model:
api.openrouteservice.org) or Mapbox (api.mapbox.com) — and supplies their own API key in Settings → Routing.By default, Worktime reads worklogs from Jira via api.atlassian.com and contacts no other service. Two optional admin features add external egress, each off until you turn it on:
*.tempo.io), Clockwork (*.clockwork.report) or eazyBI (*.eazybi.com) as the worklog source, supplying their own API key for that provider. Worktime then reads worklog data from that provider using the customer's key. The key is customer-owned and never shared with 3T Apps; the provider is the data recipient, not us. Leaving the source set to native Jira worklogs means no third-party source is ever contacted.date.nager.at API with only a country code and year to fetch national public-holiday dates. No worklog data, user data or identifiers are sent — only the country and year. Holidays can also be entered manually, in which case this endpoint is never contacted.3T Apps does not hold a shared account for any of these providers, does not proxy their traffic, and does not aggregate or retain data across customers. Worktime stores only the computed results (period snapshots, balances, audit log) in Forge KVS within your data residency region.
We may update this policy from time to time. Changes will be posted on this page with an updated revision date.
For questions about this privacy policy: privacy@3t-apps.com