Privacy Policy

Processing of accounting and personal data in the service in accordance with the Law of Ukraine “On Personal Data Protection”.

Version of 13 November 2026

This is a courtesy translation. The Ukrainian version is the legally binding text; in case of any discrepancy, the Ukrainian version prevails.

1. Controller and processor

BUSINESS OCEAN UA LLC, EDRPOU 46019321, 10 Solovianenka St., office 80, Kyiv, 02206, Ukraine. Data protection enquiries: fin@businessocean.com.ua, tel. +380 67 403 61 26.

For the Customer’s accounting data, the Customer is the controller of personal data and the Provider acts as a processor that processes the data only on the Customer’s instructions and within the functionality provided.

2. Data processed

Account data: full name, email address, sign-in data, role and permissions in the base, the user’s activity log.

Interaction history with the system: the user’s instructions (including the text of instructions to the assistant), system notices and whether they were viewed, decisions taken, and the revision of the agreement the user works under. On the user’s request a short summary of the course of events can be produced from it. The interaction history is kept for the term of the agreement and for at least 3 years after its termination.

History of conversations with AI Accountant: the text of questions and answers and the results of chat actions — so a conversation does not disappear after the page is reloaded. Only its author sees a conversation, and only within the base where it took place; the author can delete any conversation in the chat (“Conversations”).

Correspondence in the service: the accountant’s questions to the client (sent to the Telegram group connected to the base and/or by email) and the answers to them, messages and files of the base’s work chat, tasks and instructions — with the author and time of each record. Copies of deleted and edited messages and files and the history of changes to tasks and instructions are kept in the protected correspondence journal (section 8 of the Terms of Service).

Fingerprint or Face ID sign-in (a sign-in key, passkey) — only if the user adds a device themselves: the public key, the key’s name, and the dates it was created and last used are stored. The service never receives or stores a fingerprint or face image — they do not leave the user’s device. The key can be removed in “Account”.

QR-code sign-in: a sign-in request is valid for 2 minutes and can be used once; the browser and operating system of the requesting device, a hash of its IP address and the time are stored, while the request’s one-time secret stays only in that browser; after approval on the phone we send an email about the new sign-in.

The Customer’s company data: name, EDRPOU/RNOKPP, address, tax system, VAT status, bank details, accounting policy.

Data from primary documents: counterparty details, goods and services, amounts, employees’ names and positions, payroll and payment data, bank accounts for payments, vehicle and business trip data.

Register lookup: details of legal entities from the Unified State Register published as open data by the Ministry of Justice of Ukraine (data.gov.ua, CC BY 4.0) — name, legal form, EDRPOU code, status, director, founders (name only). Updated weekly and used only to suggest details when a user enters an exact code and for the service administrator’s check of a database access application; the register cannot be browsed or exported in the service.

Individual’s cabinet (a base of the “Individual” type): information on the person’s income by type and source (including foreign income, rental income, sale of property, inheritance, controlled foreign companies), taxes paid and withheld, expenses for the tax discount and supporting documents — only to prepare that person’s property and income declaration. This information is visible only to base members with access to registers or accounting; the person files the declaration personally.

Controlled foreign companies: ownership structure (shares, acquisition dates, country) and financial statement data of foreign companies entered by the user — only for CFC calculations and reporting.

Technical data: access time, IP address, sign-in events — for security and incident investigation; AI usage volume (type of action, model and number of tokens, without the content of requests and replies) — to calculate the cost of the service.

Signatures in the system: the signer’s name and position, an image of the drawn signature (or the typed name), date and time, browser and device information and a fingerprint of the signed document text. The signature is stored with the document and cannot be changed.

An access application (by the director, a person authorised by the director, or a founder): full name, position, phone, company code, comment and documents proving authority (an application signed with a qualified e-signature, the appointment order (decision), a power of attorney or the director’s authorisation order; for a founder — state register data, proof of the circumstance or a written explanation) together with an identity document. The documents are kept in a separate closed storage; only the service administrator sees them, for verification.

Handover protocol: a snapshot of the base’s books on a date (balances, trial balance, filed returns, work in progress, the list of base members with names, emails and roles), the names of the parties, remarks, and who accepted it and when. The protocol is kept unchanged together with the base.

3. Purposes and legal grounds

Data is processed to provide accounting services: document recognition, preparation of entries and registers, preparation of reports, billing for the services and user support.

The legal grounds are the concluded agreement (public offer), the consent given by the user at registration, and compliance with the laws on accounting and taxation.

The legal ground for processing correspondence in the service is the performance of the service agreement; for the journal of deleted and edited messages — the protection of the legitimate interests of the parties to the agreement (establishing the facts in a dispute). No separate consent is required for this; the rule is openly described in the Terms of Service (section 8).

4. Processing by artificial intelligence

Third-party text and image processing models are used for document recognition, draft entries and assistant replies, from the AI providers the service works with: Google, OpenAI and Anthropic — directly or through the Lovable gateway. Only the data necessary to fulfil the Customer’s specific request is transferred.

The Customer’s data is passed to AI providers only to process the specific request, is not used to train models and is not shared with other customers of the service. Assistant outputs are drafts and are not tax or legal advice.

AI Accountant memory and view (for bases where it is enabled): after changes in the books the system computes indicators by year and month from posted data and, using a text processing model, forms a view on the state of the company, its books and documents, alternative accounting approaches and advice. The view is stored in this base and visible to its members; it is the system's recommendation, not an audit opinion, and it does not change the books. This data is not used to train models.

In the correspondence, the Office assistant (AI) answers only from the base’s data and within the rights of the person asking; sensitive information (a particular person’s salary, personal data) is given only in a closed topic or privately. To answer, the text of the message is passed to the AI provider only to process that request. The assistant takes no accounting decisions: only the user (the accountant) posts documents and files reports.

Qualified electronic signature files stored in the protected section of the service are never sent to processing models and are not analysed automatically.

Voice input works only when the user turns it on: the recording is sent to a speech recognition service to be converted to text and is not stored in the service. For spoken replies, only the text of the reply is sent to a speech synthesis service.

5. Access to data and separation of bases

Each accounting base is isolated: only its owner and the team members they invite have access, within the permissions granted. Access restrictions apply not only in the interface but also on the server and in the database.

Data is not transferred to third parties except to infrastructure and data processing providers engaged to deliver the services, and in cases expressly provided by law (a request from a court or an authorised body).

Emails containing accounting data are sent only by the user’s action: reports — to the user’s own address; a reconciliation statement — to the counterparty’s address from its card after the user confirms. The service administrator may send base members (owner, accountants) a service note on the state of that base’s accounting. Every sending is recorded in the activity log.

Data from the Customer’s systems (accounting and CRM systems, electronic document exchange, bank) arrives through the API only with a key created by the Customer; the key is stored only as an irreversible hash, and requests act within the key author’s permissions.

The Customer connects the Santiago (electronic document exchange with QES) and РРОма (cash register) services itself, with a key it creates in those services for its company. The key is stored only in encrypted form and is used solely to receive that company’s data: fully signed documents with signer details (name, position, organisation, code, date of signature) and the signature package, and from the cash register — closed shifts (cashier, their RNOKPP, working hours, Z-report totals) and sales by item. No data from the base is sent to these services; the connection can be switched off at any time, and data already received stays in the base.

Users connect messengers (Telegram, Viber) themselves — only to their own chat, with a one-time code from the account. The chat identifier and the messenger display name are stored. Only reports the user sends to themselves arrive there; their text passes through the servers of the respective messenger. The chat can be disconnected at any time in “Account”.

A user with the right to upload documents may connect a working Telegram group with the client to the base with a one-time code (the “Documents from Telegram groups” module). The bot then receives that group’s messages via Telegram’s servers but stores only files (PDF, photos, spreadsheets, XML) — in the base inbox, as uploaded by the person who connected the group — together with the group name, the Telegram name and username of the sender, the file caption and the date. Message text is not stored, except answers to the accountant’s questions to the client (see “Correspondence in the service” in section 2). Group members should be told that files from the group go into the books. The group can be disconnected in “Company” or by removing the bot from the group; documents already received stay in the base.

Messages sent through Telegram are also processed by Telegram itself under its own terms; the service receives messages only from work groups or chats the user has connected, and only after they are connected. The bot sees all messages of a group only when it is a group administrator — this should be stated in the group rules. The bot sends sensitive replies privately, not to the group.

Correspondence in a base is visible only to its members — and only the topics their roles allow (director, HR officer, manager, accountant); the HR topic is visible only to the HR officer and the responsible accountant. The client does not see the accounting firm’s internal notes; other clients of the same firm do not see a client’s correspondence. The service administrator has no access to the correspondence by default: access is possible only with the base owner’s permission (in the manner described below) or under the dispute procedure in section 8 of the Terms of Service, recording who obtained it, when and on what grounds.

Employees of the accounting firm have access only to the bases assigned to them; the accounting firm removes access when an employee’s duties change or they leave. The non-disclosure obligation is set by a clause in the employment contract or the contractor agreement of the accounting firm; the service provides the accounting firm with a template of such a clause. Information from the correspondence is used only to provide services to the client.

If the Audit module is enabled for the company, the base owner may invite an external auditor. The auditor gets read-only access to the base’s accounting data and documents and can keep audit workpapers — for the term set by the owner; after that date the access ends automatically. The auditor does not post or change the books. HR data is visible only if the owner separately grants that right. The client company can follow the engagement, but only the invited auditor can change workpapers, risks and the opinion — this keeps the auditor’s opinion independent. Engagement files and the auditor’s working files (calculations, independence declarations, the risk matrix, the issued report) are stored in the service with the same protection as the books and are available only after the authenticated sign-in of the auditor or of a company member allowed to view the registers. An issued report does not change.

The books and returns belong to the company, not to an individual user. If the company’s director has no access to its base (the accountant changed, is unavailable or does not hand over), the responsible person applies: the director; a person authorised by the director (under a power of attorney or order of the director listed in the state register); in exceptional cases, when the director is unavailable (died, missing, dismissed with no successor, lacks capacity), a founder (member). The service administrator verifies identity and authority (qualified e-signature, state register data, order, power of attorney); then the base members (owner, administrator, accountant, director) receive an email and may agree or object within 5 working days. If no one objects or someone agrees, the director receives the base owner role and an authorised person the role under the power of attorney; if there is an objection, the administrator decides with a written justification. A founder’s application is decided only manually by the administrator: all base members are emailed and have 10 working days to object. Base members are not removed. Every step is recorded in the activity log. The applicant is not told whether the company keeps its books in the service until identity is confirmed.

Without the Customer's permission, service administrators do not see the data of its database — only usage statistics (number of documents and entries, file storage, service payments, last activity date) and the log. Support gets access to the database data only when the database owner (or a member with settings rights) opens it in “Companies and access” — view only, or view and fix, with a stated purpose and for up to 30 days; access can be revoked at any time, and every support access to the data is recorded in the “Support access log” the owner sees. Databases run by the service itself and test databases are open to support without separate access; marking a client database as “internal” or “test” is also recorded in that log. A service administrator cannot add themselves to a client's database. For supporting users and fixing failures, administrators have technical access to the operation of the service. Administrators receive a service email about each new support request (subject, category, author name, database name and an excerpt); the answer and a notice that a bug the author reported was fixed may be emailed to the author at the contact email given in the request or the profile email. To understand a request, the administrator sees the author's last five actions in the activity log before the request (in a client database without open access — only the kind of action and time, without details). Corrections to the Customer’s accounting data are made only with its consent and are recorded in the activity log and change history.

6. Security and retention

Encryption of data in transit, separation of access rights, change logging and regular backups are applied. The change history of entries and documents is retained.

Files of primary documents are kept in two copies — a primary one and a separate backup. Every month the integrity of both is checked by checksum (SHA-256); if the primary file is missing, it is restored from the backup. Both copies are hosted in the infrastructure of one cloud provider.

Document photos over 500 KB may be compressed in the browser before upload (this can be turned off in the device settings). PDFs, office files, XML/CSV, signed files and files in the protected section are not changed.

A company’s base is not deleted because of a change of accountant, a lapse in payment or termination of the agreement: it is moved to an archive and kept for the retention periods for accounting documents set by law, in particular by the List of Standard Documents approved by Order of the Ministry of Justice No. 578/5 of 12 April 2012. During this time the company’s owner or director can restore access and export the data. A base is deleted only at the company’s written request; in that case the company is responsible for observing document retention periods. Documents of directors’ access applications are kept for 3 years after the decision, to confirm that access was granted lawfully.

When service for a base stops, it receives the status “service stopped — read-only”: base members can still view and export the data under their rights, but changes to accounting data are not accepted (the database itself enforces this). The service builds a closure archive — a full copy of the base including document files, with a SHA-256 checksum of every file and of the whole archive — and keeps it with no expiry in a separate private storage, apart from the working files and their backup copy; the archive's integrity is checked by recomputing the checksums. Only the service administrator has access to the closure archive; a base is restored from it only at the company's request, and every such step is recorded in the activity log and in the support access log. Service can be resumed at the company's request.

Base data is not deleted except on the company's written request. After receiving such a request the service sends the company at least three warnings at least 30 days apart (about the option to export the data or receive the closure archive, about the restricted access and about the company's duty to keep accounting documents itself for the periods set by List No. 578/5); the final decision is confirmed by the service administrator no earlier than 30 days after the last warning. Until then the service does not offer to delete the base.

Correspondence and work chat files are part of the base archive: the same access rights, backups and activity log apply to them as to documents. The client may receive a full export of the correspondence together with the base archive. After the end of cooperation the correspondence is kept for 3 (three) years and is then deleted, except documents whose retention period is set by law. The correspondence journal is kept for 3 years from the date of the record, and records relating to an unresolved dispute — until the dispute ends.

7. Data security incidents

An incident is when the correspondence or files of a base were seen or obtained by someone who had no right to them. Examples: an outsider signed in with someone else’s password; a dismissed employee still had access and opened the base; because of a configuration error one client saw another client’s data; a document was sent to the wrong recipient. It is not an incident when a base member forwards something to a third party themselves.

The service notifies the base owner without delay, within 72 hours of discovering the incident: what happened, which data was affected, what has been done to stop the incident and what we recommend (change the password, revoke access, etc.).

The base owner decides whether to notify its employees or counterparties whose data was affected; the service helps prepare the notice. The service notifies a state authority only where the law expressly requires it, within the period the law sets.

Every incident is recorded in the incidents journal: the date, what happened, which data was affected and the measures taken.

8. User rights

Users have the right to know what data is processed and why, to obtain a copy, to demand correction of inaccurate data, restriction of processing or deletion, and to withdraw consent to processing.

The Customer may export a full archive of its accounting data from the service at any time. Deletion requests are sent to fin@businessocean.com.ua and are fulfilled subject to the mandatory retention periods for accounting documents.

After a document is deleted, its backup copy is kept for another 30 calendar days so that a file deleted by mistake can be restored, and is then deleted automatically.

The user moves unneeded files (not accounting, personal, another company's documents) to the Trash; the system may only suggest this. A file stays in the Trash for 30 calendar days and can be restored; it does not reach the books or reports, and after that period it is deleted together with its record. A posted document cannot be moved to the Trash. Documents of one base are never moved to another.

A person whose personal data entered the correspondence by mistake may request its deletion at fin@businessocean.com.ua. In that case the file is deleted permanently, including from the correspondence journal, and only a record of the deletion and its grounds remains in the journal.

9. Changes to this policy

A new version of the policy is published in the service. Continued use of the service after its publication means acceptance of the updated terms.

The use of cookies is described in a separate Cookie Policy.