LV RU EN

Privacy policy

Last updated: 02.09.2026

1. Controller and scope of this policy

komercriki.lv is the KomercRēķini product website. It provides product information, accounts, purchases, licensing, downloads, updates and communication. This policy covers visitors, account and licence users, purchasers, company representatives and people who contact us.

Website/server data and the desktop application's local business data are separate data flows. We do not receive the client and invoice database on your computer merely because you use KomercRēķini. Local processing and external exceptions are explained in section 5. A user processing their clients' or employees' personal data determines the purposes, legal basis and retention for that processing and provides information to the people concerned.

We receive data from you or your authorised company representative, automatically through browser/application activity, from Stripe payment notifications and from people sending us support requests. VIES results come from European Commission and national VAT systems and are stored locally in the application. If you send other people's data, include only information needed to resolve the issue and ensure you are entitled to provide it.

2. Website account, authentication and communication

2.1. Website registration

Registration typeRequired fields
IndividualUsername, email, phone number, password and password confirmation.
CompanyThe legal-form selection offered in the form, company name, 11-digit registration number, registered address, phone number, email, password and password confirmation. The username is generated.

A phone number is required for website registration. This is separate from the optional phone field in the application's company or client profile. The current form does not allow an account to be created without the required registration data. This is a service-form requirement, not a statement that the law requires a phone number in every case.

We use account data to administer and communicate about the account, verify the email address and link the account to a licence. Company details entered on the website are separate from the company profile entered locally in the application. We store passwords as hashes using a password-hashing function; we do not separately store the password confirmation.

2.2. Login and access recovery

Login uses an email address and password, together with account activation and email-verification status. For email verification and password recovery we process the email address, verification tokens, their validity and usage status, and email the relevant links. When a password is reset, we process the new password and store its hash.

Session and security records may include a session/account identifier, IP address, browser and operating-system information (User-Agent), requested address, activity time, last activity and login-attempt result. These records help provide access and detect unauthorised attempts. A verification check or access restriction may prevent login. Logging out ends the relevant session; it does not close the account or erase all associated data.

2.3. Contact form and support

The contact form requires a first name, surname, email address, phone number and message; the selected subject accompanies the submission. The form cannot be submitted without the required fields. The message is emailed to us, and a copy is sent to the address supplied by the sender. We also process the submission's IP address, time and anti-spam check results. Correspondence and materials voluntarily provided are used to resolve the relevant issue.

We use Cloudflare Turnstile for registration and contact to reduce bot and abusive-request risks. Cloudflare receives technical signals such as the IP address, browser information, connection characteristics and website origin. Our server submits the Turnstile response token and IP address for verification; the contact-message text is not a field in that verification request. A failed check may prevent form submission.

3. Purchases, Stripe and licence delivery

The seller of KomercRēķini and recipient of payment is SIA “Jurmala Invest”. Payments are processed by Stripe. For an order we use the selected plan, account email and identifier; the cardholder's name and data needed for payment are processed in the payment flow. Ordering requires login and an active application installation linked to the account email.

You enter the card number, expiry date and security code in Stripe payment components. Full card details are provided to Stripe, and we do not store them as ordinary website form data. Stripe may also process device, connection and risk-prevention information. Payment cannot be completed without the required payment data or authorisation.

We receive or store the order and payment identifiers, amount, currency, plan, status, time, customer/contact and billing references needed for fulfilment, insofar as they are included in the relevant payment, as well as technical Stripe notifications and processing logs. Technical notifications may contain more than a payment identifier alone. We use these data for licence issuance, payment records, security and dispute resolution.

After a Stripe payment notification (webhook) has been successfully verified, the system automatically creates a licence and initiates its delivery by email. Contact us if the licence has not arrived or its status appears incorrect. This description does not guarantee immediate email delivery or automatic reconciliation of refunds and licence status.

Depending on the activity, Stripe may act as our processor or as an independent controller, for example for its own fraud-prevention and legal obligations. Further information: Stripe Privacy Policy.

4. Trial, licensing and updates

The free trial lasts 14 days. It requires an active website account with a verified email address; the same email address must be used in the application.

Depending on the operation, licensing requests involve an email address, verification code or licence key, customer/licence/installation identifiers, a hash of the machine identifier, application version and, for the relevant requests, distribution channel. We also process the licence plan, status, start/end times, device association, activation/check times and HTTP metadata, including the IP address and application/operating-system information.

The machine hash and UUID identifiers are pseudonymous, not anonymous data: they can be linked to an account or licence. They help verify the device association, licence period, device limit and previous trial use. Without these data needed for licensing, licence activation or access to protected features may not be possible. We do not send the local profile password or local recovery code to the licensing server.

The application may automatically check for updates after local login during startup; a manual check and update download are also available. The server receives the requested resource address, IP address, time and application version/channel/operating-system metadata. These requests do not send the invoice or client database; update-request data do not include a licence identifier or email address.

5. Local application data and external exceptions

KomercRēķini uses a separate local username and password on your computer. Company profiles, bank details, client records, invoices, advance invoices, credit notes, delivery notes, PDF/XML files, diagnostic logs and local backups remain on your device or in your chosen storage location by default. The website account does not automatically synchronise them.

In the application's company profile, the name, registration number and email address are required; phone and address fields are optional. In a client record, the name and registration-number/personal-identification-code fields are required; the client's email, phone and contact person are optional. Preparing a document may require additional details. A field's presence in the software does not itself establish a legal basis for collecting a personal identification code: the user assesses the data needed for the particular transaction.

External data processing occurs in these cases:

  • Licensing and updates/downloads — within the scope described in section 4.
  • VIES VAT validation — the country code and VAT number are sent to European Commission and national VAT systems, and ordinary connection metadata arise. A check can be initiated by the user and may also take place during PDF/XML export of invoice/advance documents for relevant EU transactions. Invoice contents, amounts and the entire client list are not sent. The returned validity result and, where available, name/address and check time are stored locally. The absence of a required valid check may prevent the relevant export. Information about VIES.
  • Files or diagnostics voluntarily sent to support — we receive the contents of the materials you choose. Remove unnecessary third-party data, passwords and keys before sending them.
  • Transmission or storage you choose independently — for example, an externally synchronised folder or a file you send yourself; the relevant service's terms and your choices apply.

Google Drive backup and automatic invoice-email integrations are not currently active application features. Our server retention periods are not a deletion schedule for your local accounting documents.

6. Purposes and legal bases

We apply a General Data Protection Regulation (GDPR) basis to the particular purpose and relationship with the individual:

PurposeLegal basis
Creating and authenticating an individual's account, trial, purchase, licence issuance/delivery, contract-related support and application servicing, including delivery of updatesGDPR Article 6(1)(b) — performing a contract or taking steps at the individual's request before entering a contract, insofar as the processing is necessary for that purpose.
Company-representative contacts and account administration, general enquiries and communication not necessary for the individual's own contractGDPR Article 6(1)(f) — our legitimate interest in communicating, administering representation and business relationships, and responding to enquiries.
Payment/accounting documents and mandatory recordsGDPR Article 6(1)(c) — compliance with applicable accounting and tax obligations.
Secure website delivery, necessary technical logs, authentication protection, Turnstile, prevention of fraud and abusive repeat trials, integrity of licence historyGDPR Article 6(1)(f) — our and our users' interests in protecting accounts, data, service availability and legitimate licence use.
Establishing, exercising or defending claims and the associated evidenceGDPR Article 6(1)(f) — our interest in defending rights; Article 6(1)(c) where a specific legal obligation exists.
Handling data-rights requests and necessary identity verificationGDPR Article 6(1)(c) — compliance with GDPR obligations.
Session, language/theme and privacy-preference storage; external font deliveryGDPR Article 6(1)(f) — providing requested functions, preferences and a readable website; cookie-consent requirements apply separately, as explained in section 10.
Server backups for service recoveryThe legal basis of the underlying processing and the interest in continuity and recoverability under GDPR Article 6(1)(f).
Optional analytics or marketing, if introduced in futureGDPR Article 6(1)(a) — prior consent. GA/GTM analytics is not currently active.

We rely on legitimate interests after assessing necessity, proportionality and the impact on your rights; you have the right to object. The application user determines the legal basis for their processing of local client/invoice data and use of VIES. Acceptance of our policy is not blanket consent to all data processing.

7. Recipients and international processing

Authorised persons and service providers may access data to the extent needed for their tasks:

Recipient or categoryProcessing
AreaIT and hosting-associated email/IT infrastructureProvision of the website, database, technical logs, email and server backups. Data are processed on our behalf as part of the hosting service.
Stripe and payment service providers involved in the paymentPayment, transaction verification and relevant legal/security obligations; roles are explained in section 3.
Cloudflare TurnstileSecurity signals; Cloudflare acts as a processor for website protection and an independent controller for improving its bot detection under the Turnstile Privacy Addendum.
Google FontsExternal font HTTP requests; see section 10 and Google Fonts' explanation.
European Commission and national VAT systems (VIES)VAT-validation data exchange performed by the application within the scope described in section 5.
Authorised IT/support personnel, accountants, legal and other professional advisers; competent authoritiesOnly where needed for the relevant service, obligation or defence of rights. This does not mean automatic transfer of the invoice database to these recipients.

Your own email provider also participates in email delivery. When you follow an external link, including a social-media link, processing on that site is governed by its privacy information.

Global providers may process data outside the European Economic Area (EEA). Such transfers must rely on an applicable European Commission adequacy decision, standard contractual clauses and necessary supplementary measures, or another GDPR mechanism. The particular mechanism depends on the recipient and transfer. You may request information about the relevant recipients, countries and applicable safeguards, and a copy of those safeguards to the extent available for disclosure, at info@komercriki.lv. A provider's brand alone does not establish the country where data are stored.

8. Retention and deletion

We apply the following retention rules to server data under our management:

Data categoryPeriod or criterion
Contact and support correspondenceUp to 2 years after the relevant matter has been resolved.
Security logsUp to 12 months from creation of the record.
Raw/technical Stripe webhook dataUp to 90 days from receipt; necessary payment records are a separate category.
Server backupsUp to 30 days from creation of the backup before rotation/overwriting. This is not the retention period for local application backups.
Payment and accounting documentsFor the period required by applicable law for the document type. For example, other accounting source documents must be kept for at least 5 years and as long as needed to trace the transaction; accounting registers must be kept for 10 years. These periods do not automatically apply to all technical webhook contents.
Account, trial, installation, licence and activation recordsWhile needed to provide the service; afterwards only to the extent necessary for legal obligations, claims, fraud/repeat-trial controls and licence-history integrity. Necessity is assessed against licence/account status, outstanding obligations, a specific dispute/limitation period and an identified abuse risk. This is not a basis for keeping all data indefinitely.
Rights requests and evidence of their handlingTo the extent and for as long as needed to fulfil the request, demonstrate compliance with GDPR obligations or address specific claims; unnecessary identity-verification materials are not retained.
Cookies and browser storageThe periods stated in section 10.

If particular data are needed for a legal obligation or as evidence in a specific dispute, investigation or claim, the necessary copy may be kept longer only for that purpose and for the time required to fulfil it. This does not extend retention of all other data.

The account-verification link is valid for 24 hours, the password-reset link for 1 hour and the trial verification code for 15 minutes. Expiry is not the same as deletion of all associated records. Session and security records are subject to the above criteria appropriate to their purpose.

You may request account closure or data deletion at info@komercriki.lv. We assess how data relate to the account, licence, payments and retention obligations and, as appropriate, erase or anonymise data or restrict processing. We do not promise a self-service deletion function or immediate complete erasure. Data deleted from active systems may remain in rotating backups until they expire; they are not ordinarily restored except for disaster recovery. Recovery must take account of deletion and restriction requests already fulfilled.

You manage documents, backups and logs stored on your device. Data processed by independent controllers for their own purposes, such as Stripe, may have different periods under their policies and applicable law.

9. Your rights and review of licence decisions

Subject to the conditions for the relevant processing, you have rights to access your data and obtain a copy, correct inaccuracies, request erasure or restriction, and receive portable data in a structured, commonly used, machine-readable format where processing is automated and based on consent or a contract. These rights are not unlimited; for example, a legal retention obligation may restrict erasure.

You may object to processing based on legitimate interests on grounds relating to your particular situation. We then stop that processing unless there are compelling overriding legitimate grounds or a need to defend claims. Where processing is based on consent, you may withdraw it at any time; withdrawal does not affect the lawfulness of earlier processing.

Send requests, including account-closure requests, to info@komercriki.lv. If we have reasonable doubts about identity, we may request proportionate additional information. We inform you of action taken without undue delay and no later than one month after receiving the request; GDPR permits an extension of two further months due to complexity or the number of requests, with notice and reasons within the first month. We explain refusals. Requests are normally handled free of charge; GDPR allows exceptions for manifestly unfounded or excessive requests.

Technical licensing checks automatically assess the verified account, identifier/device match, previous trial use, licence status, expiry, device limit and signature validity. They may deny activation or restrict protected features. If you believe a trial/licence/device/expiry block is incorrect, write to info@komercriki.lv, describe the issue and request human review and correction. Do not send a password or full licence key. We do not automatically equate such technical checks with a decision under GDPR Article 22; the rights under that Article remain available where the particular processing meets its conditions.

You may complain about potentially improper processing to Latvia's Data State Inspectorate (Datu valsts inspekcija): how to lodge a complaint. You may also seek protection from another competent EEA supervisory authority or a court under applicable law. Contacting us does not remove those rights.

If a request concerns only your data stored locally by another company in its KomercRēķini application, contact that company. We cannot provide or erase a database that is not in our possession.

10. Cookies, browser storage and external resources

This section contains the website's cookie information. Cookies are data stored in the browser; localStorage is a separate form of local browser storage.

NamePurpose and storage
PHPSESSIDFirst-party session cookie for sessions and form security, including login. No persistent Expires/Max-Age period is set; session restoration may depend on the browser. This does not determine when server session records are deleted.
langFirst-party language preference; 365 days.
cookie_consentFirst-party privacy/cookie preference storage; 365 days.
kr_themeLight/dark theme preference in localStorage; no automatic expiry, until browser site data are cleared.

The browser may delete data earlier; saving preferences again may renew the period. The session is needed for the relevant website functions, while language and theme records store display preferences. Blocking or clearing site data in browser settings may require you to log in and choose settings again. The “remember me” checkbox does not itself mean there is a separate persistent-login cookie.

Google Analytics and Google Tag Manager (GA/GTM) are not currently active. The analytics option in the existing cookie controls only saves a preference and does not itself enable analytics. Before introducing future optional analytics or marketing, we will update this information and obtain the necessary prior consent, with rejection and withdrawal available. An earlier saved preference will not be treated as consent to new processing that has not yet been explained.

Stripe payment and Turnstile security components may use their own technical signals and browser technologies. Their particular use and durations depend on the service and settings; the first-party cookie periods in the table above do not apply to them. See Stripe cookie information and Turnstile privacy information. Turnstile security requests may occur before an analytics choice and after rejection.

The website currently loads Google Fonts externally from fonts.googleapis.com/fonts.gstatic.com. Google receives the IP address, requested font/resource address, browser/operating-system information and transmitted referrer. These requests also occur before an analytics choice and after rejection. According to Google's explanation, the Fonts API does not set or log cookies and does not use the information received for targeted-advertising profiles. This is nevertheless an external data request.

Where the law requires consent for cookies or similar technologies, it must be obtained before use. Publication of this policy is not itself consent and does not replace appropriate browser-choice mechanisms.

11. Security, minors and changes

We use HTTPS connections, access controls, password hashing, licence and payment-notification signature checks, and limits on data volume appropriate to the function. No system or data transmission is absolutely secure. You should also protect your computer, password, licence key and backups.

KomercRēķini is intended for business use and is not intended for people under 18 years of age. This audience restriction does not mean that we collect dates of birth or carry out age verification. Contact us if you become aware of inappropriate submission of a minor's data.

We will publish the updated policy on the website with its update date. We will communicate material changes through a website notice and, where the changes require it, also by account email before the relevant new processing begins. If new consent is required, we will request it separately. We will maintain aligned LV, EN and RU versions; the Latvian text is canonical, without affecting your right to clear information in the language provided to you.