T Tiebra

Tiebra Mobile Application Privacy Policy

This Privacy Policy explains how Tiebra collects, uses, stores, and protects data in connection with field operations, shift tracking, service execution, and checkpoint verification.

Effective Date 16.06.2026
Application Tiebra
Developer / Company Uc Faktoriyel ArGe ve Yazilim Ltd. Sti.
Contact support@3faktoriyel.com

Tiebra is an enterprise application. Users cannot create their own accounts in the mobile application; accounts are created and managed by authorized administrators.

1. Introduction

This Privacy Policy explains how the Tiebra mobile application collects, uses, stores, and protects personal and operational data.

Tiebra is a business-oriented mobile application used by authorized employees and company users for field operations, shift tracking, service execution, checkpoint verification, and related operational workflows.

The application is not intended for public consumer use. Users cannot create their own accounts in the mobile application. User accounts are created and managed by authorized administrators through the Tiebra administration panel.

2. Data We Collect

2.1 Account and User Information

Tiebra may process account and user-related information such as:

  • Name and surname
  • User ID or employee ID
  • User email address
  • Username
  • Company, project, region, service, or workplace assignment information
  • User role and permission information
  • Login and authentication-related data

This data is used to authenticate users, manage access rights, and ensure that users can only access the functions and data assigned to them.

2.2 Location Data

Tiebra may collect location data during specific operational actions if this feature is enabled by the company administrator.

Location data may be collected during actions such as:

  • Starting a shift
  • Ending a shift
  • Starting a service
  • Ending a service
  • Scanning or confirming a checkpoint

Location collection is not always mandatory. It depends on the configuration defined in the administration panel. If location data cannot be obtained, the application may still allow the user to continue the operation, depending on the company’s configuration.

Tiebra does not use continuous background location tracking. Location data is collected only in connection with specific user-initiated operational actions.

Location data may include:

  • Latitude and longitude
  • Date and time of capture
  • Accuracy information
  • Related shift, service, task, or checkpoint record

This data is used for operational verification, field activity control, reporting, and audit purposes.

2.3 Camera, Photos, and Media

Tiebra may request access to the device camera for specific operational processes.

Depending on the configuration, users may be asked to take photos during actions such as:

  • Starting a shift
  • Ending a shift
  • Starting a service
  • Ending a service

These photos may include:

  • A selfie photo of the user
  • A photo of the surrounding work area or service environment

Photos are captured directly through the camera at the time of the operation. Tiebra does not allow users to upload existing photos from the device gallery for these processes.

Captured photos are used for operational verification, work documentation, quality control, and audit purposes.

2.4 NFC and Checkpoint Data

Tiebra may use NFC-based checkpoint verification where this feature is enabled.

When a user scans an NFC checkpoint, the application may collect and process:

  • NFC tag or checkpoint identifier
  • Scan date and time
  • Related shift, service, task, or project information
  • User performing the scan

This data is used to verify field presence, checkpoint visits, service progress, and operational activity.

2.5 File and Media Access

Tiebra may request file or media-related permissions when required for application functionality, operational documentation, or secure handling of captured files.

The application primarily uses media captured directly through the device camera for the relevant business process. Existing gallery uploads are not used for shift and service start/end photo requirements.

2.6 App Activity and Operational Data

Tiebra may collect operational activity data generated through the use of the application, including:

  • Shift start and end records
  • Service start and end records
  • Task, cleaning, inspection, or checkpoint records
  • Form answers submitted by users
  • Date and time of performed actions
  • Synchronization status of offline records
  • Project, region, service, and assignment-related activity

This data is used to provide the core functionality of the application, support operational reporting, verify completed work, and maintain business records for the company using Tiebra.

2.7 Device and App Information

Tiebra may collect limited device and application information, such as:

  • Device model
  • Operating system version
  • Application version
  • Device language or regional settings
  • Synchronization and connectivity status

This data is used for security, compatibility, troubleshooting, and application maintenance.

2.8 Diagnostics and Analytics

Tiebra does not currently use third-party analytics tools.

Tiebra does not currently send crash reports or diagnostic data to external crash reporting services. Technical errors may be logged within the Tiebra system for maintenance, troubleshooting, security, and support purposes.

2.9 Push Notifications

Tiebra does not currently use push notifications and does not collect push notification tokens.

3. How We Use Data

We use collected data for the following purposes:

  • To authenticate users and manage secure access
  • To provide shift tracking and service tracking functionality
  • To verify field activities, checkpoints, and operational actions
  • To support photo-based operational documentation
  • To enable NFC-based checkpoint verification
  • To synchronize offline records with Tiebra servers
  • To generate operational reports and dashboards
  • To support quality control, audit, and service verification processes
  • To maintain system security and prevent unauthorized access
  • To troubleshoot technical issues and maintain application reliability
  • To comply with contractual, operational, legal, or administrative obligations where applicable

4. Offline Use and Synchronization

Tiebra may allow certain operations to be performed while the device is offline.

When offline mode is used, operational data may be temporarily stored on the device and synchronized with Tiebra servers when an internet connection becomes available.

This may include shift records, service records, checkpoint records, form answers, photos, and related operational data.

Offline data is used only for completing the relevant business process and is transmitted to Tiebra servers during synchronization.

5. Data Storage and Hosting

Tiebra stores application data and provides API services through cloud servers located in Frankfurt, Germany.

The current infrastructure is hosted on DigitalOcean droplets located in Frankfurt.

Data is stored and processed for the purpose of providing the Tiebra service, supporting business operations, maintaining system security, and fulfilling contractual or legal obligations.

6. Data Sharing

Tiebra does not sell personal data.

Data may be accessed or shared only in the following limited cases:

  • With the company or organization that provides Tiebra access to the user
  • With authorized administrators, managers, or responsible personnel within that organization
  • With infrastructure or hosting service providers required to operate the application
  • When required by law, regulation, court order, or authorized public authority
  • When necessary to protect the security, rights, or integrity of Tiebra, its users, or its infrastructure

Tiebra does not currently share user data with third-party analytics, advertising, push notification, or external crash reporting providers.

7. Data Security

We apply appropriate technical and organizational measures to protect data against unauthorized access, loss, misuse, alteration, or disclosure.

These measures may include:

  • Secure communication between the mobile application and servers
  • Authentication and authorization controls
  • Role-based access management
  • Server-side access restrictions
  • Operational logging and monitoring
  • Secure infrastructure configuration
  • Regular maintenance and technical improvements

However, no method of electronic transmission or storage is completely secure. We continuously work to improve the security and reliability of the system.

8. Data Retention

Data is retained for as long as necessary to provide the Tiebra service, support business operations, comply with contractual obligations, maintain security, resolve disputes, and meet legal or administrative requirements.

Retention periods may vary depending on:

  • The type of data
  • The company using Tiebra
  • Operational reporting needs
  • Legal, contractual, accounting, or audit requirements

When data is no longer required, it may be deleted, anonymized, or securely archived according to applicable retention rules.

9. Data Deletion and User Requests

Users cannot create their own accounts in the Tiebra mobile application. User accounts are created and managed by authorized administrators through the Tiebra administration panel.

Users who want to request access to, correction of, or deletion of their personal data should contact their employer, company administrator, or the Tiebra privacy contact.

Requests may be sent to: support@3faktoriyel.com

Because Tiebra is used as a business application on behalf of organizations, some data may need to be retained for legal, contractual, operational, accounting, or audit purposes.

10. App Permissions

Location Permission

Used to capture location during specific operational actions such as shift start/end, service start/end, or checkpoint verification.

Camera Permission

Used to capture real-time photos, such as user selfies or surrounding area photos, during specific operational actions.

NFC Permission

Used to scan NFC checkpoints for field verification.

File and Media Permission

Used where required for handling operational media or files related to the application’s business processes.

Users may control permissions through their device settings. Disabling permissions may limit some application features, but the exact behavior may depend on the configuration defined by the company administrator.

11. Children’s Privacy

Tiebra is intended for enterprise and business use. It is not directed to children and is not designed for use by individuals under the age required by applicable law.

We do not knowingly collect personal data from children.

12. International Data Processing

Tiebra data is currently hosted on servers located in Frankfurt, Germany.

Depending on the location of the company using Tiebra and its users, data may be accessed or processed from different countries for support, administration, or operational purposes, subject to applicable data protection requirements.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in the application, infrastructure, legal requirements, or operational practices.

The updated version will be made available through the application and/or the relevant website.

14. Contact

For privacy-related questions or requests, please contact:

  • Company: Uc Faktoriyel ArGe ve Yazilim Ltd. Sti.
  • E-mail: support@3faktoriyel.com
  • Address: Gulbahce Mah. Gulbahce Cad. IYTE Sitesi No:1/40/29 Urla / Izmir / Turkey
  • Website: https://www.3faktoriyel.com