Tekno Sales

Privacy Policy

Applies to the Tekno Satış B2B mobile application. The iOS and Android versions follow the same data processing principles.

Last updated: June 2026

This Privacy Policy explains what information the Tekno Satış mobile application (the “App”) collects from its users, the purposes for which this information is used, with whom it may be shared, and how it is protected.

The App enables authorized sales representatives, managers, and related company users to manage B2B sales processes such as customer accounts, invoice tracking, stock information, quotation tracking, order and shipment reports, collection reports, in-app messaging, and product catalogs.

1. Data Collected

Depending on the user's permissions and the screen being used, the App may process the following data:

User Credentials

  • Username
  • Password
  • User ID
  • User role and permission information
  • Sales representative code

Customer and Commercial Data

  • Account code
  • Commercial title
  • Tax number and tax office
  • Contact information
  • Email and phone information
  • Balance, debt, and receivable status
  • Account transaction history

Financial and Transaction Data

  • Invoice information
  • Invoice series, number, date, and amount information
  • VAT, discount, and total amounts
  • Payment and transaction history
  • Collection reports
  • Cash, credit card, check, and promissory note information
  • Responsibility center balance information

Stock, Order, Quotation, and Shipment Data

  • Stock code, stock name, and unit information
  • Warehouse-based stock quantities
  • Stock movements
  • Quotation information and quotation line items
  • Pending orders
  • Pending waybills
  • Vehicle shipment report information
  • Report data such as license plate, shipment amount, shipment quantity, and number of waybills

Messaging, Communication, and Status Data

  • The contents of messages sent and received within the app
  • Conversation, sender, and recipient identifiers
  • Any image or PDF files attached to messages
  • Online / last-active (presence) status
  • Feedback and support request contents

Data Stored on the Device

  • Username and password are stored securely: on iOS using Apple Keychain, and on Android using Android's secure storage mechanisms.
  • Session and permission information may be kept securely on the device.
  • Downloaded product catalogs and PDF documents (invoices, waybills, receipts, etc.) may be kept in the device's local storage.
  • The Firebase Cloud Messaging device token used for push notifications may be stored on the device, linked to the user's session.
  • Certain filter, sorting, and screen preferences may be stored on the device to improve the user experience.

Technical and Usage Data

  • App version
  • Device model and operating system information
  • Crash and error logs
  • App performance information
  • Screen view and basic usage statistics
  • Online / last-active (presence) status
  • Firebase Cloud Messaging notification token
  • On Android, the Google Play Services advertising ID within the scope of Firebase Analytics

The App does not request access to or collect location, camera, microphone, contacts, or personal sensor data. The map screen in the App only displays fixed company showroom locations and does not access the device's location data.

2. Purposes of Data Use

The collected data is used for the following purposes:

  • Authenticating the user
  • Managing the session
  • Displaying customer, invoice, stock, quotation, order, shipment, and collection information that the user is authorized to access
  • Providing sales and collection performance reports
  • Downloading and viewing product catalogs
  • Enabling in-app messaging between authorized users
  • Showing online (presence) status to relevant users
  • Receiving and responding to feedback and support requests
  • Sending in-app notifications and important announcements
  • Detecting application errors and improving technical stability
  • Improving app performance and user experience
  • Enforcing permission-based access controls

Data is not used for advertising display, ad targeting, or unauthorized third-party marketing purposes.

3. Use of Advertising Identifier

On Android, the Google Play Services advertising ID may be used within the scope of Firebase Analytics. This use is limited to:

  • Usage analysis
  • App performance measurement
  • Technical improvement
  • Error and stability monitoring

only.

On iOS, the Apple Advertising Identifier (IDFA) is not collected and App Tracking Transparency permission is not requested. The App declares no tracking in its PrivacyInfo.xcprivacy file.

No advertising is displayed in the App. The advertising identifier is not used for ad targeting, user profiling, or marketing purposes.

4. Notifications, In-App Messaging, and Presence

The App may use Firebase Cloud Messaging for important announcements, app updates, and informational messages. Within this scope:

  • A notification token for the device may be obtained (on iOS, the APNs token is bridged to the FCM token via Firebase).
  • The notification token may be linked to the signed-in user's account.
  • The token information is transmitted to the company server (api.teknoiklimlendirme.com) via the /device-tokens endpoint.
  • When the user logs out or changes devices, the token is removed from the server.
  • Users can disable app notifications from the operating system settings.

The notification token is used only to send and manage app notifications.

In-App Messaging

The App provides in-app messaging between authorized users. The contents of sent messages, along with conversation, sender, and recipient identifiers (and any attached image/PDF files), are processed and stored on the company server (api.teknoiklimlendirme.com). New message alerts are delivered via Firebase Cloud Messaging. Messages are used only for in-app business communication.

Presence (Online Status)

While the App is in the foreground, a periodic signal indicating that the user is online (on average every 20–45 seconds) is sent to the company server. This information may be shown to relevant authorized users as online / last-seen status. When the App is backgrounded or closed, the user is considered offline shortly afterwards. This feature does not involve any location data.

Feedback and Support Requests

Users can submit feedback or support requests through the App. The request content and related messages are processed on the company server; updates about the request may be delivered via Firebase Cloud Messaging notifications.

5. Data Transfer and Sharing

The App transmits data to the company's own servers at api.teknoiklimlendirme.com over the HTTPS protocol.

Within this scope, basic usage events such as screen openings, button interactions, searches, and session start/end are also sent in batches to the company's own server (first-party analytics) to improve the App. These events are associated with a randomly generated session identifier and are not shared with third parties.

The following third-party services are used in the App:

Firebase Cloud Messaging

Used to send notifications. Within this scope, the device notification token may be processed. Used on both iOS and Android.

Firebase Analytics

Enabled on the Android version only. Used to analyze app usage statistics, screen views, basic interactions, and technical performance information. On Android, within the scope of Firebase Analytics, in-app analytics fields such as user ID, user type, and sales representative information may be processed.

On the iOS version, Firebase Analytics is disabled; instead, the anonymous first-party usage analytics described above (not linked to a user identity) is used.

Firebase Crashlytics

Used to collect technical information such as app crashes, error logs, device model, operating system, and app version. This data is used to detect errors and improve app stability.

App Updates

  • iOS:Apple's iTunes Lookup API is used to check the current version on the App Store. If a new version is detected, the user is notified and the App Store page is opened. This request is anonymous and contains no personal data.
  • Android: App updates are checked and offered to the user through Google Play In-App Updates.

No advertising network, social media tracking SDK, or third-party advertising platform is used.

6. Data Security

The following technical measures are applied to protect the data:

  • User credentials are protected using Apple Keychain on iOS and Android's secure storage mechanisms on Android.
  • Sensitive local data is protected using platform-specific secure storage mechanisms.
  • Server communication is performed over HTTPS.
  • API requests are authorized using the secure x-api-key header and validated on the server side.
  • For signed-in users, requests also carry a time-limited session token (Authorization: Bearer), which is validated on the server side.
  • In-app file sharing is controlled through the system share sheet (ShareLink / UIActivityViewController) on iOS and through the Android FileProvider mechanism on Android.
  • Clear-text HTTP connections are not permitted; all traffic is encrypted with TLS.

7. Data Retention

Credentials and session information stored on the device may be deleted when the user logs out of the App or uninstalls it.

Downloaded catalogs, PDF files, and local preferences may remain on the device. Users can clear local data on the device by uninstalling the App.

Commercial, financial, and operational data on the server side is retained in accordance with the company's internal data retention policies and applicable legal obligations.

Technical data processed within the scope of Firebase Analytics, Crashlytics, and Cloud Messaging may be subject to the data retention policies of the relevant service providers.

8. User Rights

Users may:

  • Delete credentials stored on the device by logging out from the App.
  • Remove local data from the device by uninstalling the App.
  • Contact the company administrator or data controller for data requests related to their accounts.
  • Manage notification permissions from the device settings.

9. Children's Privacy

This App is intended only for corporate and authorized users. Data is not knowingly collected from individuals under the age of 18.

10. Policy Changes

This Privacy Policy may be updated when necessary. Significant changes may be announced within the App, through the website, or through the company's official communication channels.

11. Contact

Company / Data Controller: Tekno İklimlendirme
Email: info@teknoiklimlendirme.com
Website: teknoiklimlendirme.com

Technical Developer: Mehmet Gümrah
Website: mgumrah.com