Privacy Policy
Last updated: {date}
This Privacy Policy describes how LabFlow (“App”) accesses, uses and shares information when you use GitLab management features, including offline mode and real-time notifications.
1. Who we are
Developer/Controller: SmarTi
Privacy contact: [email protected]
Privacy contact: [email protected]
2. Data the App accesses and processes
2.1 GitLab authentication data
- Personal Access Token you provide to authenticate to the configured GitLab instance.
- API URL of the configured instance (GitLab.com or self-hosted).
Note: the token is used for direct calls to your GitLab API and it is stored securely on the device.
2.2 GitLab content
- Data retrieved from your GitLab instance (projects, issues, merge requests, pipelines, wiki pages, groups, members, etc.).
- This data may be cached locally to enable offline usage and improve performance.
2.3 Real-time notifications
- Device push token (e.g., Firebase Cloud Messaging) to deliver notifications.
- Notification preferences and required metadata to operate notifications/webhooks.
2.4 Diagnostics and analytics
- By default, the App does not require analytics.
3. How we use data
- Authenticate and operate the app (GitLab API reads/writes).
- Display GitLab information and enable actions (create/edit issues, merge requests, etc.).
- Maintain local cache for offline usage and better performance.
- Send notifications (when enabled) about GitLab events.
4. Data sharing
The App may share data strictly to execute its features:
- With the GitLab instance you configure (authentication and operations).
- With push providers (e.g., FCM) to deliver notifications.
- With webhook/notification backends (when applicable) to process GitLab events and trigger pushes.
5. Local storage, retention and deletion
- Offline cache: GitLab data can remain on-device to enable offline usage.
- Local deletion: uninstalling removes local data; “Signing out” removes local token.
- Notifications: when disabled, the app unlink/remove push tokens and related config (when applicable).
6. Security
- Store tokens using OS-level secure/encrypted storage.
- Use HTTPS/TLS for network communications.
7. Your rights and choices
- You can disable notifications in the app and/or device settings.
- You can request clarification or deletion of backend data (if any) via the privacy contact above.
8. Children’s privacy
The App is not directed to children.
9. Changes to this policy
We may update this policy periodically. The date above indicates the latest update.
10. Contact
For privacy questions: [email protected]