Skip to content
BAYHOCA IT
Home BayhSoft Pricing FAQ Contact
EN
FrançaisFRNederlandsNLEnglishENDeutschDELëtzebuergeschLBTürkçeTRRomânăROБългарскиBGItalianoITРусскийRULietuviųLTEspañolES
Home BayhSoft Pricing FAQ Contact

BAYHOCA IT / Legal information

Privacy policy

How information is used when you visit this website, contact Bayhoca IT or use BayhSoft on the Web and Android.

This translation follows the French document. The terms of your service remain those set out in your contract.

In this document
01Data controller 02Visiting the website 03Display preferences 04Form and email enquiries 05Information processed 06Information that is needed 07Purposes and bases for enquiries to Bayhoca IT 08Recipients and providers 09Providers and transfers 10Retention periods 11Exercising your rights 12Complaints 13Automated decisions and marketing 14Data in BayhSoft 15BayhSoft and responsibilities 16Accounts and activation 17Business data viewed and recorded 18Device and technical logs 19Photos, signatures and permissions 20Purposes and bases of the BayhSoft service 21Security and storage 22Providers, connected services and region 23Retention, deletion, logs and backups 24Advertising and analytics 25Rights and deletion requests 26Personnel and time tracking 27Shared attendance terminal 28Retention of personnel data
All documents↗
01

Data controller

BAYHOCA Apdurahman, trading as Bayhoca-IT, has its business address at Rue Large Voie 141/R1, 4040 Herstal, Belgique and is responsible for processing enquiries sent to Bayhoca IT. For questions or requests about your data, contact contact@bayhoca-it.com.

02

Visiting the website

This website includes no advertising tracker, audience analytics or fonts loaded from an external service. The hosting server may process technical data, including your IP address and request details, to deliver and secure the website.

03

Display preferences

The page address determines the language and the theme is passed in the URL. The contact form uses a strictly necessary session cookie to protect submissions against abuse. It expires when the browser closes and is not used for advertising tracking. You can remove this cookie in your browser settings. The form protection may then need to load again before submission.

04

Form and email enquiries

The form sends your name, email address, company, subject and message. A confirmation is sent to the address provided. You may also write directly by email and choose the information you send. If you choose an offer, its name and the selected period are suggested in the message, which you can edit. This does not create an order or contract.

05

Information processed

When you use the form or write to Bayhoca IT, the information processed may include your identity, contact details, company, subject, message and data needed to manage the relationship. Form protection processes a session identifier and IP address to limit abuse. Technical server logs may also contain a date, requested page and browser information.

06

Information that is needed

Your name, email address, company name, subject, message and confirmation that you have read the privacy policy are required to send the form. Without this information, Bayhoca IT cannot handle the enquiry or prepare an offer.

07

Purposes and bases for enquiries to Bayhoca IT

We use enquiries to reply and, at your request, prepare an offer or service. Necessary preparatory work and service delivery rely on steps before a contract or on the contract. Retention may meet a legal obligation. Security and administration rely on legitimate interests assessed for the situation. The form checkbox confirms that you have read the policy. It is not consent to marketing and is not the general basis for all processing.

08

Recipients and providers

Only people handling your enquiry and providers needed for hosting, email or the service may access data needed for their work. We do not sell contact data. Services involving other recipients or international transfers are described in their specific context.

09

Providers and transfers

Combell provides website hosting. Email, infrastructure and support providers may process only the information needed for their work. If processing involves a transfer outside the European Economic Area, Bayhoca IT checks that a mechanism provided by the GDPR protects the transfer. Information about that mechanism may be requested by email.

10

Retention periods

An enquiry that does not result in a contract is kept for no more than twenty four months after the last useful exchange, unless deletion is requested or a specific need applies. Contract, billing and accounting documents are kept for the periods required by law, generally ten years for accounting records. Technical logs are kept for the period needed for security, diagnosis and hosting obligations. A longer period may apply when needed to establish, exercise or defend a legal claim.

11

Exercising your rights

A request about your rights may be sent to contact@bayhoca-it.com. It must allow the relevant data to be identified. Proof of identity may be requested only where reasonable doubt exists. Bayhoca IT responds within the period set by the GDPR and explains any refusal. We respond without undue delay and no later than one month after receipt. Any necessary two month extension is explained and notified within that first month.

12

Complaints

Contact us if you have a concern. You may also complain to the Belgian Data Protection Authority or the authority competent for your situation. The Belgian authority’s official website is autoriteprotectiondonnees.be.

13

Automated decisions and marketing

The website makes no automated decision that produces a legal effect. Contact details are not used for electronic marketing without a legal basis. You may object to marketing messages at any time.

14

Data in BayhSoft

This policy covers the public website, enquiries, BayhSoft ERP services and the Android application. It describes the common processing activities that have been verified. Depending on the client configuration, the service documents also specify the roles of the client and provider, access rights, retention periods and the conditions for processing on the client’s behalf. Hosting included in a plan does not make Bayhoca IT responsible for all client records. Where the client determines the purposes of its business data, its instructions and the processing agreement govern the provider’s work.

15

BayhSoft and responsibilities

BayhSoft is an ERP available on the Web and Android. An iOS version is planned but is not yet distributed. When a customer business uses BayhSoft to manage its activities, it determines the business data recorded and the access granted to its users. It generally acts as the controller for that data. BAYHOCA Apdurahman, trading as Bayhoca-IT, processes that data on the customer’s instructions. Bayhoca IT remains responsible for processing needed to create and secure accounts, provide support and meet its own obligations.

16

Accounts and activation

An account may be created when an invitation is activated in the mobile application. The account may include the name, email address, internal user, company and environment identifiers, and information needed for authentication. Depending on the account, sign in uses a password, stronger authentication or an opaque QR code. The account email address is required for password sign in. Authenticated requests send a protected session token linked to the user. On Google Play, the application is intended for professional use by people aged sixteen or over. The declared age groups are sixteen to seventeen and eighteen or over. Depending on the country, Google Play may consider some users aged sixteen or seventeen to be children under its rules. Access to BayhSoft is based on an invitation and the permissions granted in the customer business environment. No independent age verification or parental consent flow was found in the product reviewed. The same privacy and deletion rules apply to these accounts.

17

Business data viewed and recorded

Depending on the modules and permissions granted, BayhSoft processes professional directories of customers, suppliers and contacts, entered contact details and notes, vehicles, appointments, schedules, workshop operations, time records, statuses, prices, invoices, documents and attachments. BayhSoft planning events may include a title, notes, dates, participants, assignments, a vehicle and a linked repair order. The application does not access the Android calendar. When a supplier record, which may concern an individual, is updated, the mobile application may transmit bank details already on record, including the IBAN, BIC and bank name, even though these fields cannot be edited in the compact form. Repair orders may contain quotations, amounts, line prices, approval limits and an invoice reference linked to the customer. Associated free content, signatures and business audits are persisted. The application does not access the Android address book.

18

Device and technical logs

During authentication, the application automatically obtains or creates an installation identifier in GUID format and a public key fingerprint, then sends them to the service. Activation may also send the public key, platform and device name. The private key remains in local secure storage and the reviewed flows do not transmit it. Session information is used to recognise an authorised device and revoke its access. Server side operational diagnostics record the endpoint, HTTP method, result with its status code, duration observed by the server and the resolved environment, company and user context. This duration is measured on the server and is not a device performance metric. The services may also record the IP address, date, audited actions and technical errors to provide security, traceability, diagnostics and operation of the service. In the TEST environment inspected on October 9, 2026, active IIS logs include UriQuery, ClientIP, UserAgent and Referer. Search terms sent in address parameters must therefore be treated as potentially persisted. This inspection read configuration and file metadata without reading user log lines. Daily rotation creates new files but is not a purge.

19

Photos, signatures and permissions

A user can choose to take a photo from an appointment linked to a repair order. If the capture is cancelled, no photo is uploaded. The application requests metadata removal before the transfer. The selected photo is then sent to the server and kept with the relevant record. The verified Android flow stores the content in a private file under the root configured by the ControlPlane, with no photo content in SQL. File size and integrity were checked from upload to the ERP preview, and anonymous access was rejected with status 401. Signatures and drawings linked to operations confirm a business step and are not used for biometric recognition. The application uses Internet and network status. The camera is used for QR codes and workshop photos. It does not request access to Android contacts, location, microphone, SMS or an advertising identifier.

20

Purposes and bases of the BayhSoft service

Data is used to provide requested features, manage accounts and permissions, synchronise records, secure the service, prevent abusive access, assist users and meet applicable obligations. Depending on the processing, the legal basis is the contract with the customer, that customer’s instructions, a legal obligation or the legitimate interest in security and operation of the service.

21

Security and storage

Connections to BayhSoft services use HTTPS. Tokens and the installation private key are kept in secure storage on the device. The local cache is encrypted, restricted to the active account and company, and cleared when the session is removed. The server processes received data, so this is not end to end encryption. Photos are placed in a private server directory and only their metadata is stored in SQL.

22

Providers, connected services and region

BayhSoft infrastructure is hosted by Contabo in a European Union region. Combell provides the website and some outgoing email services. Microsoft 365 receives support emails. After an explicit user action, VIES receives the country and VAT number through the European Commission service. The Belgian company register receives the company number and language through the FPS Economy service with a technical account. No internal identifier, complete record or IBAN is sent to these two checks. Suggestions are shown before they are applied and applied data becomes persistent in the ERP. Other connected services such as OVH for SMS or Peppol receive data only when they are enabled and used for the relevant feature. The Android application distributed through Google Play may include the automatic installer check provided by Google Play. This check runs in particular when the application opens, works offline under the conditions described by Google and may periodically require a connection to Google Play. It concerns application distribution and licence verification and remains separate from the ERP business processing described in this policy.

Official information about Google Play automatic protection↗

23

Retention, deletion, logs and backups

Data remains available for as long as needed for the account, requested service and applicable obligations. A deletion request immediately disables the mobile account and revokes its sessions. The erasure procedure verified in the TEST environment for mobile and web flows removes access, clears authentication secrets and anonymises the user profile. Business documents, anonymised authorship and legally required audit references may be retained when justified by the contract, accounting, security, evidence or the establishment, exercise or defence of legal claims. For ordinary TEST environment backups, the approved rule aims for deletion no later than thirty days after creation. A separate rule uses the same target for TEST technical logs. Their operational application and the complete inventory of the copies concerned have not yet been demonstrated. No active or automatic purge has been proven. The thirty day period therefore describes the approved rule and target for TEST. It is not a guaranteed operational maximum and does not describe production. A backup may be retained longer only for a documented incident or rollback need. A technical log may be retained longer only for a documented incident. The items concerned must be identified and kept separately. Until their operational handling is qualified, the period actually applied depends on continuity, security, diagnostic and incident response needs and on applicable legal obligations.

24

Advertising and analytics

No advertising SDK, advertising identifier or public analytics tool is integrated into the mobile version reviewed. The review did not establish the presence of a client crash reporting SDK or the collection of battery or frame rate metrics. BayhSoft does not sell personal data. Any change to components or uses must be checked before a new release of the application and this policy.

25

Rights and deletion requests

Requests for access, correction, restriction, objection, portability or erasure may be sent to contact@bayhoca-it.com. When data is managed for a customer business, Bayhoca IT may forward the request to that business or assist it with the response. The external procedure for deleting a BayhSoft account is described on the Delete a BayhSoft account page.

26

Personnel and time tracking

When the Personnel module is enabled, BayhSoft processes employee identities and employee numbers, their work site, configured time zone, work pattern and work calendar, as well as clocking times, breaks, activities, reasons, comments and related reports. This data supports time tracking and internal management according to the permissions granted by the customer business. The employer or customer business determines the purposes, authorised access and applicable basis for this processing as data controller. Bayhoca IT processes the data under the contract and the customer’s instructions. This module adds neither GPS location tracking nor biometric recognition.

27

Shared attendance terminal

A shared terminal lets employees identify themselves with their employee number and a PIN. The PIN is sent over HTTPS and checked on the server against a hash. It is not retained in mobile storage and the information entered for a passage is cleared when that passage is reset. The dedicated cookie authorises the terminal and remains separate from the employee account and the administrator session. On mobile, this credential is kept in the device’s secure storage, SecureStorage, with its HTTPS origin and expiry date. It serves only terminal operation and security until expiry or revocation. It is not used for advertising tracking.

28

Retention of personnel data

Clocking history, corrections and their audit records are retained on the server for time tracking and for checking and documenting corrections. Retention periods and criteria for personnel data must be defined with the employer or customer business according to the purposes, applicable duties and contract. This policy does not guarantee a maximum operational retention period in production. The thirty day rule described for TEST backups and technical logs does not apply to personnel records in production. Deleting an account does not automatically erase these records and histories where retention remains justified. Requests are reviewed with the data controller, who identifies the data to erase, anonymise or retain and the reason for retention.

Updated on November 2, 2026

Back to top↗All documents↗
BAYHOCA IT

Herstal, Belgium

© 2026
PricingFAQLegal informationLegal noticePrivacyService termsWebsite termsSoftware and BayhSoftDelete a BayhSoft account