This policy describes how Debit Technologies OOD processes personal data when you visit debitbg.com, register an account, use the Platform, or communicate with us.
Version 1.0 · Effective: 1 September 2026
Section 1.
Who we are
The controller of the personal data described in this policy is Debit Technologies OOD, UIC 208881012, registered seat: 16 Gen. Gurko Street, Sofia, Bulgaria, operator of debitbg.com.
For any data protection matter, write to privacy@debitbg.com. We respond within one month.
We are not required to appoint a data protection officer under Art. 37 GDPR, as our core activities involve neither large-scale systematic monitoring nor large-scale processing of special categories of data.
Section 2.
What this policy covers — and what it doesn't
This policy describes data for which we determine the purposes and means — website visits, account registration and use, payments, and communication with us.
It does not govern the accounting documents our customers upload. For that data the customer is the controller (or a processor acting for its own clients), and we are a processor or sub-processor. That processing is governed by Article 5 and Annex 1 of the Terms of Service.
If you are an individual whose data appears on an invoice or payroll document processed through the Platform, your contact point is the company that uploaded it, not us. If you approach us, we will redirect you without undue delay.
Section 3.
What we don't do
We do not sell or rent personal data — under any circumstances.
We do not use your document content to train AI models unless you expressly enabled that option.
We place no Meta, Google Ads or LinkedIn pixels and build no retargeting profiles.
We take no automated decisions with legal effects for you — every output is subject to human review.
Billing details, VAT number, subscription history, payment status. We do not store card numbers.
Invoicing, collection, accounting and tax reporting.
Art. 6(1)(b) + 6(1)(c)
Support
Enquiry content, attachments and screenshots, correspondence.
Answering enquiries, resolving problems.
Art. 6(1)(b) — contract
Website chat
When the chat loads: a visitor identifier (cookie), IP address, browser and device type, language. If you write to us: your messages, your name and email address if you give them, and the page you write from.
Answering visitors' and customers' questions, routing them to the right team.
Art. 6(1)(b) + 6(1)(f)
Service notices
Email address, account status.
Outages, changes to terms, expiring subscriptions.
Art. 6(1)(b) + 6(1)(c)
Audience measurement
Visitor/device identifier (cookie), pages viewed, session length, approximate country — see Section 5.
Understanding site usage.
Art. 6(1)(a) — consent
Marketing
Email address, name, consent history.
Newsletter — only if subscribed. One-click unsubscribe.
Art. 6(1)(a) — consent
Section 5.
Cookies and analytics
We use strictly necessary cookies — session, language preference, CSRF protection. These require no consent under Art. 4a of the Electronic Communications Act.
The site chat sets a cw_conversation cookie holding a random identifier, so your conversation carries over when you change page or come back later. It is set when the page loads so the chat is ready, lasts 12 months and is not used for analytics or advertising. We treat it as strictly necessary, because the chat cannot work without it.
For audience measurement we use Google Analytics (GA4), which sets cookies (e.g. _ga, _ga_*) to distinguish visitors and sessions. Google processes this data as an independent controller under its own privacy policy — see Sections 7 and 8.
Because these cookies are not strictly necessary, we load them only after you consent via a cookie banner. You can withdraw consent at any time from the cookie settings in the site footer.
We use no third-party cross-site tracking cookies and place no advertising pixels (see Section 3).
Section 6.
Artificial intelligence
The Platform uses AI systems to read, classify and structure accounting documents.
Outputs are always preliminary. Every extracted value is subject to human review before posting or filing. The system finalises nothing on its own.
Training is opt-in and off by default. We do not use customer document content to train or fine-tune models unless the account administrator has expressly enabled the "Model Improvement Programme". Enabling it does not affect price or scope of service and can be withdrawn at any time.
We use third-party models. See our sub-processor list at debitbg.com/subprocessors. We have a data processing agreement with each.
Transparency. AI-generated or materially altered fields are identified as such in the interface, per Art. 50 of Regulation (EU) 2024/1689 (AI Act).
Classification. We have assessed the Platform as not high-risk under Art. 6 and Annex III of the AI Act.
Section 7.
Who else sees this data
Recipient
For what
Processed in
Amazon Web Services (AWS)
Application hosting, databases, backups
EU/EEA (eu-central-1, Frankfurt)
Stripe
Payment processing, card data storage
EU / third country — to be confirmed
Resend
Service and product notices
[region — to be confirmed]
Google Analytics (Google Ireland Limited / Google LLC)
Aggregated audience measurement, with your consent
EU / US — see Section 8
Accountant and auditor
Bookkeeping and tax reporting
Bulgaria
Public authorities
Only under legal obligation or competent authority request
Bulgaria / EU
Support is handled directly by our team via email (support@debitbg.com) and the site chat. The chat runs on Chatwoot, open-source software installed on our own server (support.debitbg.com) in [hosting and region — to be confirmed].
AI model providers processing uploaded document content are listed separately at debitbg.com/subprocessors, since for that data we act as a processor, not a controller.
Section 8.
Transfers outside the EEA
Our infrastructure — application servers, databases and backups — sits entirely within the European Economic Area (AWS, Frankfurt region). Your account data does not leave the EEA in normal operation.
Some providers we use (including Google Analytics and some AI model providers used for document reading) are established outside the EEA. Even where processing takes place in a European region, the possibility of the provider's personnel gaining remote access from a third country constitutes a transfer under Chapter V GDPR. For those cases we rely on:
Standard Contractual Clauses under Commission Implementing Decision (EU) 2021/914;
the EU–US Data Privacy Framework adequacy decision, where the provider is certified;
a transfer impact assessment and supplementary measures — data minimisation, zero retention, encryption in transit and at rest.
The current list of which provider processes where, and on what basis, is kept at debitbg.com/subprocessors. Copies of applicable SCCs are available at privacy@debitbg.com.
Section 9.
How long we keep data
Data
Period
Why
Account data
Subscription term + 90 days
Renewal and restoration of access
Access and security logs
12 months
Incident and abuse investigation
Accounting and tax records
Per Art. 12 Accountancy Act — 10 years for registers and financial statements, 5 years for other records
Legal obligation
Support correspondence (email and chat)
24 months from case closure
Tracking recurring problems
Chat cookie (cw_conversation)
12 months
Continuing the conversation on a later visit
Marketing consent
Until withdrawal + 3 years
Evidencing lawfulness under Art. 7(1)
Analytics cookies (Google Analytics)
Up to 14 months, or until consent is withdrawn
GA4's user/event-level retention ceiling
Aggregated analytics
Indefinitely, aggregated
Contains no personal data
Section 10.
Security
encryption in transit (TLS 1.2+) and at rest;
least-privilege access control with an in-Platform role model;
mandatory MFA for administrative access by our staff;
separation of development, staging and production;
backups with restore testing;
access logs and an audit trail of actions;
written confidentiality undertakings for all personnel with data access.
No measure makes a system absolutely secure. On a personal data breach we notify the CPDP within 72 hours where there is a risk to your rights, and notify affected individuals where the risk is high.
Send requests to privacy@debitbg.com. We respond within one month; for complex or numerous requests the period may be extended by two further months, of which we will inform you with reasons. Exercising rights is free, except for manifestly unfounded or excessive requests.
We may ask for further information to verify your identity — not to complicate the process, but to avoid disclosing someone else's data to the wrong person.
Section 12.
Complaint to a supervisory authority
Commission for Personal Data Protection
2 Prof. Tsvetan Lazarov Blvd, Sofia 1592, Bulgaria. Email: kzld@cpdp.bg · cpdp.bg
Complaints must be lodged within 6 months of learning of the infringement and no later than 2 years after it occurred (Art. 38(1) PDPA).
Section 13.
Automated decision-making
We take no decisions based solely on automated processing producing legal effects or similarly significantly affecting you (Art. 22 GDPR). The Platform proposes values and postings; these have no legal effect until a person reviews and confirms them.
Section 14.
Children
The Platform is for commercial and professional use only and is not offered to persons under 18. We do not knowingly collect children's data.
Section 15.
Changes
We may update this policy. For material changes we notify registered users by email at least 30 days before they take effect.
Previous versions are available at privacy@debitbg.com.