Data Processing Agreement

This English version is provided for convenience. In the event of any discrepancy, the Czech version prevails.

Effective from 1 November 2026. Previous versions can be found in the archive of this page.

Article 1 – Who we are and what this Agreement covers

  1. This Agreement governs the processing of personal data pursuant to Article 28 of Regulation (EU) 2016/679 (GDPR) in the use of the services HASIQ.app Intelligent Finance ("IF"), HASIQ.app Billing ("Billing") and HASIQ Cookie (the "Cookies service": records of consents of visitors to the customer's website, by default without the IP address – the website operator may enable a truncated IP address; the record is retained for the period set for the website, 1280 days for new websites, at least 30 days).
  2. You (the customer) are the controller of the personal data that you enter into the service or have loaded into it (e.g. from an accounting system). We – Ing. Petr Hasil, MBA, place of business Vyškov, Company ID (IČO) 17774225 (A natural person registered in the Trade Register maintained by the Vyškov Municipal Office), operator of the HASIQ.app services – are the processor.
  3. This Agreement does not apply to data that we process as a controller for our own purposes (your account with us, invoicing, communication, the hasiq.app website). These are described in the Privacy Policy.
  4. How this Agreement is concluded:
    • IF: by signing the order. The order states the version (effective date) of this Agreement that you have accepted.
    • Cookies service: by order, or by registration in the service's administration and activation of the account. The service records which version you have agreed to.
    • Billing: by registration, i.e. by ticking the box consenting to the General Terms and Conditions, of which this Agreement forms part. The application records which version you have agreed to.
  5. This Agreement remains in force for the period of use of the service and thereafter until the complete erasure of the data in accordance with Article 9.

Article 2 – What we process

IFBillingCookies service
Purposefinancial management, reporting, planning, consolidation, meetings; storage, calculations, backups, supportissuing and recording of documents, customer address book, payments, exports for accountants; storage, backups, supportdisplaying the banner, storing and demonstrating the visitor's choice, passing on the consent signal
Naturestorage, structuring, calculations, display, export, backup, erasurestorage, structuring, creation of documents, sending by e-mail, export, backup, erasurestorage, display, export, erasure
Data subjectsyour users; employees, customers, suppliers and other persons in the accounting and operational datayour users; customers, suppliers and contact persons on documentsvisitors to your website
Categories of dataname, e-mail, role; data from accounting documents (names, amounts, bank details, descriptions); payroll data, if you load them into the service; login and operational logsname or business name, address, Company ID (IČO) / VAT ID (DIČ), e-mail, telephone, bank details, content of documents; login and operational logsconsent identifier, categories, type of choice, banner version, language, page without parameters, GPC signal, time; truncated IP address only once enabled; aggregated counts of banner displays (1100 days) and website scan results (180 days); when the banner is loaded, temporarily the IP address and browser information in server logs and a short-term IP hash to limit the number of requests.

Do not enter special categories of personal data (Article 9 GDPR) or personal data relating to criminal offences into the service; the service is not intended for them. In IF, make payroll data available only to roles that need them – the application allows this to be configured.

Article 3 – Your instructions

  1. We process the data only on your documented instructions, including with regard to transfers to countries outside the EU/EEA (Article 8). Instructions consist of this Agreement, the General Terms and Conditions and the settings made in the service by you or your administrators (users, roles, connections, enabled add-ons). Otherwise, we will process the data only where required to do so by EU or Czech law. In such a case, we will inform you before the processing, unless the law prohibits this.
  2. Should we consider that an instruction infringes the GDPR or other legislation, we will inform you without undue delay.
  3. We do not use the data for our own purposes, we do not sell them, and we do not use them for development or for training AI. We develop and test exclusively on fictitious data.

Article 4 – Our obligations

  1. Persons who have access to the data are bound by confidentiality, including after the end of the cooperation.
  2. We maintain technical and organisational measures pursuant to Article 32 GDPR as described in the annex Technical and Organisational Measures at the end of this Agreement. We may change them only if the level of protection is not reduced.
  3. We assist you in handling data subject requests (access, rectification, erasure, portability). You can handle most of them directly in the service (user management, edits, export). We will forward any request that reaches us to you without undue delay.
  4. We assist you with your obligations under Articles 32 to 36 GDPR (security, notification of breaches, data protection impact assessment, prior consultation) to the extent corresponding to the nature of the service and the information available to us.

Article 5 – Service access

IF

  1. We have service access to your application and the data in it. We use it only for: support at your request (e.g. a helpdesk request), resolution of faults and security incidents, updates and migrations, and checking and restoring backups. Any other use, in particular our own analysis of your data, is excluded.
  2. Each access:
    • is created via a one-time link from our administration interface, valid for no more than 10 minutes;
    • has a mandatory stated reason (or a request number), which cannot be changed afterwards;
    • is visible in the application for its entire duration (the „Servisní vstup provozovatele“ ("Operator service access") bar);
    • is recorded in the audit log, which you can see (time, level – read-only / full, name of the person, reason);
    • triggers an e-mail with the same details to your users' administrators (and to the data protection officer, if you provide us with their e-mail). Repeated access by the same person within 15 minutes is combined into a single e-mail; in the audit log each access is recorded separately.
  3. Access may be performed only by our authorised persons bound by confidentiality, using two-factor authentication, and always with the lowest access level that suffices. We identify these persons by role; the name is stated in each notification and in the audit log.
  4. You cannot disable service access in the application. Without it, we would be unable to resolve faults and incidents, update the service and restore data. Instead of a switch, protection is ensured by the transparency and purpose limitation described above.
  5. If you believe that access has been used in breach of this Article, write to us (helpdesk or info@hasiq.app). Within 5 working days we will inform you who performed the access, when, why and to what extent, and we will substantiate this with the audit log.
  6. We retain records of service access for 10 years (Article 9.3).

Billing

  1. We do not see the data of the companies you keep in Billing without your service permission. You grant permission in the application when you need help; both the grant and each access are recorded and you receive an e-mail about it. This protection cannot be disabled entirely in Billing. The validity of the permission is governed by the access granted by the customer.
  2. Without permission, we work only with the data necessary for operation (account, plan, technical status, backups as a whole).

Article 6 – Personal data breach

  1. We will notify you of a personal data breach without undue delay, no later than within 48 hours of becoming aware of it.
  2. The notification contains what we know: what happened, which data and approximately how many persons and records are concerned, the likely consequences, what we have done and what we propose, and a contact point. We will supplement what we do not yet know on an ongoing basis.
  3. Notification to the supervisory authority and communication to the data subjects concerned are your obligation as controller; we will provide you with the supporting information.

Article 7 – Sub-processors

  1. You grant us general authorisation to engage sub-processors. We will provide you with their current list together with the order (for Billing, it is available in the application) and will send it by e-mail at any time on request.
  2. We will notify the addition or replacement of a sub-processor at least 30 days in advance (by e-mail to the administrators, with an updated list). You may object on legitimate grounds until the date of the change. If we do not reach agreement, you may terminate the service as of the date of the change without penalty.
  3. We impose on sub-processors the same data protection obligations as apply to us, and we are liable to you for their performance.
  4. Optional features (AI) engage a sub-processor only once you enable them. We store encrypted off-server backup copies on the operator's own backup device, so this is not a sub-processor. If you use your own key or your own agent for AI, the AI provider is your contractual partner, not our sub-processor – see the General Terms and Conditions, Part H.
  5. The payment gateway Comgate a.s. is not our sub-processor. Payments for our services do not concern the data you enter into the service, and Comgate is an independent controller of the payment data.

Article 8 – Transfers outside the EU/EEA

  1. We operate the services on the servers of a provider established in the Czech Republic; the data centre is located in Prague (Czech Republic).
  2. Data may leave the EU/EEA only in the case of optional features that you enable (in particular AI), and only subject to safeguards under Chapter V GDPR – an adequacy decision (e.g. the EU–US Data Privacy Framework) or standard contractual clauses. In the paid AI add-on, we therefore do not offer providers without these safeguards, nor services that forward queries to other providers without documented safeguards. These may be used only with your own key, in which case they are not our sub-processors. The specific providers and their countries are set out in the list of sub-processors (Article 7).

Article 9 – Termination

  1. After the service ends, you choose whether you want the data returned (export of all data in open formats) or deleted.
    • IF: export is available at any time during the contract and for 30 days after its termination. We then permanently delete the data, including cryptographic destruction of the encryption keys of your data; the exception is operational backups, which cease to exist in accordance with point 2.
    • Billing: after the plan ends, the account remains read-only and export works. After cancellation of the account or company, we automatically delete the data after 30 days, or after a longer period chosen by you in the settings (no more than 365 days).
    • Cookies service: you may export consent records and account data at any time. After termination, the data remain in the recycle bin for 30 days and are then irreversibly deleted; they disappear from the service's backups within 14 days. Switching to another provider is free of charge (Terms, clause G8).
  2. Backups: we do not delete data from backups individually; they cease to exist through the rotation of the backups. Daily IF backups are kept for 14 days (the customer's administrator may set 1–60 days), daily Billing backups for 7 days on the server, encrypted off-server copies of the backups of all applications for 14 days; monthly operational backups for up to 12 months. All copies will therefore cease to exist no later than 13 months after deletion. Until then, no one uses the backups except for disaster recovery.
  3. Audit: we retain records of who performed which action and when (without accounting or other data), and records of service access, after termination as a controller for 4 years for the establishment, exercise or defence of legal claims (Article 6(1)(f) and Article 17(3)(e) GDPR). This processing is described in the Privacy Policy (https://www.hasiq.app/en/ochrana-osobnich-udaju).
  4. We will confirm the erasure to you in writing on request. This does not apply to the extent that legislation requires us to continue retaining the data.

Article 10 – Inspection and audit

  1. On request, we will provide you with the information necessary to demonstrate compliance with this Agreement (e.g. this annex, a security review report, an extract from the audit log).
  2. You may carry out an audit or inspection at our premises yourself or through an auditor bound by confidentiality, by agreement at least 30 days in advance and no more than once a year. More frequently only in the event of a suspected breach or at the request of a supervisory authority. You bear the costs of the audit.

Article 11 – Final provisions

  1. Liability between us and you, including claims under this Agreement, is governed by the General Terms and Conditions (https://www.hasiq.app/en/obchodni-podminky), in particular clause A9. This is without prejudice to the rights of data subjects under Article 82 GDPR.
  2. We will notify changes to this Agreement 30 days in advance; if you do not agree with a change, you may terminate the service.
  3. This Agreement is governed by the law of the Czech Republic. In the event of a conflict with the General Terms and Conditions, this Agreement prevails in matters of personal data protection; the scope of liability is nevertheless governed by point 1.

Annex – Technical and Organisational Measures

Status as of 1 November 2026. We describe what the services actually do; where something does not apply, we say so.

1. Transmission and encryption

  • Transmission: exclusively HTTPS (TLS), enforced redirection and HSTS.
  • IF – encryption at rest (AES-256-GCM, a separate data key for each customer, stored separately from the data):
    • we encrypt: the application's data sets (accounting journal, receivables and payables, bank, plan…), settings, plans, mappings, comments and their history, uploaded files, snapshots of shared links, database backups; separately also access credentials for connections, the SMTP password, the AI key and two-factor authentication secrets;
    • we do not encrypt: row-level accounting data with which the database performs calculations (amounts, dates, accounts, cost centres, descriptions), settings metadata (name, version, who changed it and when), the audit log and the list of users. These are protected by the separation of customers, permissions enforced on the server and access control to the server. Disk encryption at the hosting provider.
    • upon permanent deletion of a customer, we destroy its key. Encrypted copies in the application backups can then no longer be opened. Operational backups also contain the keys and cease to exist through their rotation (Article 9.2).
  • Billing: data encryption. Daily Billing backups on the server are not encrypted; off-server copies (section 5) and manual backup downloads are encrypted.
  • Passwords are not stored, only their hash (PBKDF2-SHA256, 600,000 iterations).

2. Access

  • Personal accounts, roles and permissions enforced on the server (in IF by pages, companies, cost centres and periods); the „čtenář“ ("reader") user type cannot change anything.
  • Two-factor authentication (a code from an authenticator app or a passkey); the policy is set by the customer's administrator.
  • Limitation of login attempts, the same response for an unknown account and a wrong password, automatic logout after inactivity (IF 60 minutes).
  • Service access by the operator in accordance with Article 5 of the Agreement (reason, e-mail, audit log; in Billing only with permission).
  • The operator's administration interface: mandatory two-factor authentication, roles, shorter sessions.

3. Separation and development

  • Each customer's data are logically separated; production and test data are separated.
  • Development and testing only on fictitious data; updates only via signed packages, with an automatic backup before the update and rollback in the event of an error.

4. Audit and logs

  • Immutable audit log of changes and sensitive actions (hash chaining, signature, daily anchors outside the database); the database rejects any modification or deletion of a record.
  • The AI audit log contains only the tool, the number of steps and the consumption – not the text of the query or the response.
  • Retention periods (IF, default): operational audit 12 months, legal and security records 4 years, login attempts 30 days, verification codes 12 months, exports 90 days, imports 180 days. Clean-up runs automatically.

5. Backups and restoration

BackupEncryptionFrequency and retention
IF – automatic backup of the customer's databaseyes (AES-256-GCM, customer key)daily, kept for 14 days
Operational backup (all customers and the administration interface)yesdaily, kept for 14 days
Billing – daily backup on the servernodaily, no more than 7 days
Off-server backup copies (all HASIQ.app applications)yes (AES-256, encrypted before leaving the production server; the key is held exclusively by the processor)daily, kept for 14 days; the operator's dedicated backup device (operator's registered office, Czech Republic)
  • Backups: daily backups on the production server and encrypted copies (AES-256) on the operator's dedicated backup device separated from the production environment (operator's registered office, Czech Republic); the decryption key is held exclusively by the processor; the copies are kept for 14 days; recoverability is verified regularly.
  • Database restoration takes place in a single transaction with verification of counts and totals.
  • Recovery point objective (RPO): no more than 24 hours. Recovery time objective (RTO): 1 business day from discovery.

6. Operations and monitoring

  • Monitoring of availability, certificate validity and disk space; regular security and consistency checks.
  • Protection of the website and API: strict rules for scripts (CSP), protection against cross-site request forgery (CSRF), protection of outbound connections; uploaded executable files are not accepted.
  • There is no antivirus scanning of uploaded files on the server; files are served for download only.

7. Organisation

  • Only the operator's authorised persons have access to production data, only to the extent necessary and bound by confidentiality.
  • Incident procedure: detection, containment (logout, blocking, maintenance mode, key rotation), notification to the customer within 48 hours, evaluation. Contact for reporting: info@hasiq.app or in accordance with https://www.hasiq.app/.well-known/security.txt.