Compliance Framework
Compliance Framework Document
Project:Project / Organization:BilkoALAI Holding AS —BalkanDropAccountingPaymentSaaSApp Policy Number: POL-COMP-FW-001 Version: 1.0 Date: 2026-02-23 Author:ComplianceSecurity Architect Status: Draft Reviewers: DPO, Legal Counsel, CEO Classification: Confidential
Document History
| Version | Date | Author | Changes |
|---|---|---|---|
| 0.1 | 2026-02-23 | Initial draft — |
1. Applicable Regulations
Compliance Owner: ComplianceSecurity Architect / DPO ([email protected])[email protected])
External Auditor:Company: ToALAI beHolding engagedAS (Phaseorg.nr 2)932 516 136), incorporated in Norway
Last Review:Domain: 2026-02-23 |getdrop.no
NextBusiness Review:Model: 2026-08-23PSD2 pass-through payment app — NEVER holds customer money; AISP reads bank balances, PISP initiates payments from user's bank account.
Service: Remittance to 30+ countries + QR payments in Norway
Users: All residents of Norway, 18+ years, with Norwegian BankID
Primary Jurisdiction: Norway
Drop is incorporated in Norway under Norwegian law. All primary regulatory obligations flow from Norwegian legislation and Finanstilsynet supervision.
| Regulation | ||
|---|---|---|
| PSD2 (Payment Services) | Betalingstjenesteloven (LOV-2018-11-23-85) | Core — legal basis for payment operations |
| AML/CFT | Hvitvaskingsloven (LOV-2018-06-01-23) + Hvitvaskingsforskriften (FOR-2018-09-14-1324) | Core — anti-money laundering obligations |
| GDPR | Personopplysningsloven (LOV-2018-06-15-38) | Core — personal data protection |
| Financial Enterprises | Finansforetaksloven (LOV-2015-04-10-17) | Licensing, governance, capital requirements |
| ICT Security | IKT-forskriften (FOR-2003-05-21-630) | ICT security for financial enterprises |
| Digital Operational Resilience | DORA (EU) 2022/2554 | Norway incorporation expected ~2026 H2 |
| Currency Registry | Valutaregisterloven (LOV-2003-06-06-39) | Cross-border payment reporting to SSB |
| Consumer Protection | Finansavtaleloven (LOV-2020-11-13-125) | Payment terms, user rights, fee transparency |
| Electronic Signatures | eIDAS / LOV-2001-06-15-81 | BankID as qualified electronic identification |
Remittance Corridor Jurisdictions
Drop sends remittances to 30+ countries. Regulatory obligations in these corridors:
| Destination Region | Key Regulations | Drop Obligations |
|---|---|---|
| EU/EEA (Eurozone, Croatia, etc.) | GDPR (free data flow), EU AML | Standard KYC; no SCCs needed for data |
| Serbia | ZZPL (Zakon o zaštiti podataka, LOV RS 87/2018) | Standard KYC; SCC + TIA for data transfers |
| Bosnia & Herzegovina | ZZLP (Zakon o zaštiti ličnih podataka, SG BiH 49/06) | Standard KYC; SCC + TIA for data transfers |
| Turkey | Turkish Personal Data Protection Law (KVKK 6698/2016) | FATF monitoring list — enhanced KYC |
| Pakistan | Pakistan Personal Data Protection Act | FATF monitoring — enhanced due diligence |
Note: Drop's obligations in corridor jurisdictions are primarily fulfilled by the receiving payment institution. Drop's direct obligations are Norwegian-law based, supplemented by GDPR requirements for cross-border data transfers.
2. Licensing
Current Status
Drop is an MVP-stage application. No Finanstilsynet license has been obtained. Live transactions with real money are NOT permitted until a license is in place.
Licensing Pathway
Recommended path: Agent model (Option C) for initial launch, then full license (Option B) for scale.
Option A: Begrenset betalingsforetak (Limited Payment Institution)
Law: Betalingstjenesteloven § 2-10c
| Requirement | Detail |
|---|---|
| Monthly transaction volume | Max 6 million NOK/month (12-month average) |
| Capital requirement | None |
| Application timeline | 3-6 months |
| EEA passporting | NO — Norway only |
| Fit & proper | Directors and beneficial owners |
| AML | Full compliance required |
Drop fit: Initial launch — allows ~3,000 remittances of 2,000 NOK average/month.
Option B: Ordinaert betalingsforetak (Full Payment Institution)
Law: Betalingstjenesteloven §§ 2-3 to 2-10
| Requirement | Detail |
|---|---|
| Initial capital | 125,000 EUR (~1.4M NOK) for remittance services |
| Application timeline | 6-12 months |
| EEA passporting | YES — enables Sweden/Denmark |
| Governance | Board, compliance officer, internal audit |
| Safeguarding | Client funds in segregated account or guarantee |
Drop fit: Target license for Scandinavian scale.
Option C: Agent Model (recommended for Phase 1)
Law: Betalingstjenesteloven § 2-12
| Requirement | Detail |
|---|---|
| Structure | Drop operates as agent of licensed payment institution |
| Capital | None required from Drop |
| Timeline | 1-3 months |
| Liability | Principal (licensed PSP) is responsible |
Target partners: Licensed Norwegian PSPs or BaaS providers (Swan, Modulr, Banking Circle).
3. PSD2 / Betalingstjenesteloven
Strong Customer Authentication (SCA)
Law: Betalingstjenesteloven §§ 4-28, 4-29; Delegated Regulation (EU) 2018/389
| Requirement | Section | Status | |
|---|---|---|---|
| Phase |
|||
| 90-day re-authentication | Art. 10 (Del. Reg.) | Phase 2 | |
| Phase 2 |
Current 2.state:SerbiaEmail + password only. SCA required for production launch.
Required implementation (RS)Phase —2):
- BankID OIDC for initial login (Level 4 eID)
- Transaction signing with BankID for all payment initiation
- Dynamic linking: display amount + payee in BankID signing dialog
- Session timeout and re-authentication after 5 minutes inactivity
2.1Open Data Protection — Zakon o zaštiti podataka o ličnostiBanking (ZZPL)AISP/PISP)
Full name:Law: ZakonBetalingstjenesteloven o§§ zaštiti4-40 podatakato o4-46
| Service | Law | Requirement |
|---|---|---|
| AISP (read bank balances) | § 4-41 | AISP license or agent arrangement; explicit user consent |
| PISP (initiate payments) | § 4-44 | PISP license or agent arrangement; no storing bank credentials |
| Dedicated interface | § 4-40 | Use banks' PSD2 APIs (Bits, Tink, or direct bank APIs) |
Consumer Information Requirements
Citation:Law: Sl.Betalingstjenesteloven glasnikkapittel RS br. 87/2018
In force: November 21, 2018
Description: Serbia's GDPR-aligned personal data protection law. Mirrors GDPR structure3 and principles.4; Supervisory authority: Poverenik za informacije od javnog značaja i zaštitu podataka o ličnosti (Commissioner for Information of Public Importance and Personal Data Protection)
Website: https://www.poverenik.rsFinansavtaleloven
| Requirement | ||
|---|---|---|
| Pre-contractual information | §§ 3-1 to 3-8 | Framework agreement (rammeavtale) |
| Per-transaction information | §§ 3-22 to 3-26 | Transaction receipts |
| Fee transparency before authorization | § 3-23 | Pre-auth disclosure screen |
| Exchange rate disclosure | § 3-24 | FX rate + reference rate shown before confirmation |
| Execution time (non-EEA) | § 4-15 | Max D+4 business days |
| Complaint handling | § 3-60 | Klagebehandling procedure |
4. AML/KYC — Hvitvaskingsloven
Customer Due Diligence (CDD)
Law: Hvitvaskingsloven §§ 10-18
| Requirement | Section | Drop Implementation |
|---|---|---|
BreachKYC
notification contact:
2.2 Accounting Law — Zakon o računovodstvuTiers
Full name: Zakon o računovodstvu
Citation: Sl. glasnik RS br. 73/2019, 44/2021
Description: Defines accounting obligations for all legal entities in Serbia.
| Requirements | Corridor Risk | |||
|---|---|---|---|---|
| BankID verification only | Lav (Low) — |
|||
| Up |
BankID + address verification | Middels ( | ||
| Full EDD: source of funds + senior management approval | Høy ( |
|||
| Sanctioned | ||||
2.3Transaction VATMonitoring Law — Zakon o PDVRules
Full name:Law: ZakonHvitvaskingsloven o§§ porezu24, na25
Transactions vrednostthat must trigger investigation:
Citation:StructuringSl.—glasnikmultipleRStransactionsbr.just84/2004,below86/2004,reporting61/2005thresholds- Rapid
al.movement — large in/out within same day - Unusual corridors — sudden change in destination country
- Volume spikes — significantly above customer's historical pattern
- FATF jurisdiction — any transaction to FATF grey/black list countries
- PEP match — customer or recipient on PEP list
Reporting: Suspicious Transaction Reports (consolidated)STR) Description:filed Serbia'swith VATEFE law.(Enheten for finansiell etterretning) via altinn.no. Tipping off the customer is prohibited (§ 28).
AML Risk Classification — Corridor Risk
| Bosnia & Herzegovina (BA) | Middels (Medium) | Enhanced monitoring; cash economy |
| Turkey (TR) | Høy (High) | FATF grey list (monitoring); elevated corridor risk |
| Pakistan (PK) | Høy (High) | FATF monitoring; common remittance corridor |
| OFAC/UN sanctioned countries | Blokkert | Transactions blocked entirely |
VAT registration threshold:Source: 8,000,000 RSD annual turnover
Return frequency: Monthly (>50M RSD) or Quarterly (<50M RSD)
Filing deadline: 15th of following month
Portal: ePorezi — https:~//www.poreskauprava.gov.rs
Penalties: 50,000 – 2,000,000 RSD for SEF non-compliance
2.4 E-Invoice — SEF (Sistem e-Faktura)
Platform: https://efaktura.gov.rs
Mandatory since:
B2G (suppliers to government): May 2022B2B (business-to-business): January 2023
Format: UBL 2.1 XML
Integration: API available — @bilko/country-rsALAI/products/Drop/legal/hvitvaskingsrutiner.md package (Phase 2)
Penalties: 50,000 – 2,000,000 RSD for non-compliance
2.5 Electronic Document Law
Full name: Zakon o elektronskom dokumentu, elektronskoj identifikaciji i uslugama od poverenja u elektronskom poslovanju
Citation: Sl. glasnik RS br. 94/2017
Description: Legal validity of electronic documents and digital signatures.
Bilko-generated invoices and reports constitute valid electronic documents when:
Generated by certified accounting softwareStored immutably with audit trailExportable in PDF/XML format
2.6 APR Filing
All Serbian legal entities must file annual financial reports with APR (Agencija za privredne registre). Bilko generates reports in APR-compatible format for export. API integration planned (Phase 3).
3.5. BosniaGDPR &/ Herzegovina (BA) — Regulatory CompliancePersonopplysningsloven
Complexity:
Legal BiHBases hasfor two entities (FBiH and Republika Srpska) with parallel legislation. VAT is unified at state level via UIO. Direct taxes are administered separately per entity.
3.1 Data Protection — Zakon o zaštiti ličnih podataka BiHProcessing
Full name:Law: Zakon o zaštiti ličnih podataka Bosne i Hercegovine
Citation: Sl. glasnik BiH br. 49/2006, 76/2011, 89/2011
Description: State-level personal data protection law. Pre-GDPR butArt. aligned6; in principles.
Supervisory authority: Agencija za zaštitu ličnih podataka Bosne i HercegovinePersonopplysningsloven (AZLP)
Website: https://www.azlp.ba
The same state-level law applies across both FBiH and Republika Srpska.LOV-2018-06-15-38)
| Contract performance | Personopplysningsloven § 5, GDPR Art. 6(1)( |
||
| Legal obligation | Personopplysningsloven § 6, GDPR Art. | § ||
| Error monitoring (Sentry) | Legitimate interest | GDPR Art. 6(1)(f) | |
| Marketing | Consent | GDPR Art. 6(1)(a) |
BreachData
notificationSubject contact:
3.2 FBiH — Accounting LawRights
Full name: Zakon o računovodstvu i reviziji Federacije Bosne i Hercegovine
Citation: Sl. novine FBiH br. 83/2009, 56/2023
Description: Accounting and audit law for Federation of BiH.
| Drop Implementation | ||
|---|---|---|
3.3 Republika Srpska (BiH Entity) — Accounting Law
Full name: Zakon o računovodstvu i reviziji Republike Srpske
Citation: Sl. glasnik RS BiH br. 96/2005, 74/2016
Description: Accounting and audit law for Republika Srpska entity of BiH.
3.4 VAT — Zakon o PDV BiH
Full name: Zakon o porezu na dodanu vrijednost Bosne i Hercegovine
Citation: Sl. glasnik BiH br. 9/2005, 35/2005, 100/2008 et al.
Description: Unified VAT law administered at state level. No reduced rates.
Administering authority: UIO — Uprava za indirektno oporezivanje (Indirect Taxation Authority)
Portal: https://www.uino.gov.ba
Registration threshold: 100,000 BAM annual turnover
Return frequency: Monthly
Filing deadline: Check UIO portal
3.5 E-Invoice — CPF (Central Platform for Fiscalisation)
Status: PENDING — technical specifications not yet published
Law adopted: January 2026 (FBiH only)
Expected availability: ~2027
Bilko decision: Do NOT implement CPF integration until technical specs are published. Monitor UIO and FBiH government portals for updates. BiH is Phase 3 launch.
3.6 Corporate Income Tax
Bilko provides CIT calculation support — separate fields for FBiH vs RS entity in organization settings.
4. Croatia (HR) — Regulatory Compliance
Note: Croatia is an EU member state. GDPR applies directly without separate national transposition law.
4.1 Data Protection — GDPR
Applicable law: GDPR — Regulation (EU) 2016/679 (directly applicable)
National implementing act: Zakon o provedbi Opće uredbe o zaštiti podataka (NN 42/2018)
Supervisory authority: AZOP — Agencija za zaštitu osobnih podataka
Website: https://azop.hr
| Right to access | Art. 15 | |
| Right to rectification | Art. 16 | Profile edit |
| Right to erasure | Art. 17 | |
| Right to restriction | Art. 18 | Manual processing by DPO |
| Right to portability | Art. 20 | |
| Art. |
||
| Art. |
||
BreachRetention notificationconflict: contact:
4.2vs. AccountingHvitvaskingsloven Law§ 30 (5-year AML retention). AML retention takes precedence — Zakon o računovodstvu
Full name: Zakon o računovodstvu
Citation: NN 78/15, 120/16, 116/18, 42/20, 47/20
Description: Croatian accounting law, aligns with EU Accounting Directive.
4.3 General Tax Law — Opći porezni zakon
Full name: Opći porezni zakon
Citation: NN 115/16, 106/18, 121/19, 32/20 et al.
Description: Framework tax law governing all Croatian taxes, including penalties for VAT non-compliance.
Relevant to Bilko: Defines document retention (11 years), electronic record acceptance, and obligations for digital accounting systems.years.
4.4 VAT Law — Zakon o porezu na dodanu vrijednost
Full name: Zakon o porezu na dodanu vrijednost
Citation: NN 73/13, 148/13, 143/14 et al.
Description: Croatian VAT law implementing EU VAT Directive.
Portal: ePorezna — https://www.porezna-uprava.hr
Registration threshold: 60,000 EUR annual turnover
Return frequency: Monthly
Filing deadline: Last day of following month
4.5 E-Invoice — HR-FISK / eRačun
Platform: https://hr-fisk.fina.hr
Operator: FINA — Financijska agencija
Status: Mandatory since January 1, 2026 (all B2B, B2G, B2C)
Format: UBL 2.1 XML with HR-CIUS (Croatian Implementation User Specification)
Protocol: AS4 (Peppol-compatible)
Certificate: FINA qualified certificate required
Integration: @bilko/country-hr package (Phase 2) — FINA API integration required
Penalties: Up to 500,000 EUR for non-compliance (severe)
Archive requirement: 11 years
4.6 FINA Reporting
All Croatian legal entities file annual financial reports via FINA RGFI portal. Bilko generates FINA-compatible XML/XBRL reports for export. Deadline: April 30.
4.7 HNB (Hrvatska narodna banka)
For organizations with foreign currency transactions, HNB reporting may apply. Bilko supports EUR (Croatia's official currency since January 2024), with historical HRK support for data migration.
5. Cross-Country Compliance Matrix
Bilko retention policy: Apply maximum retention across all markets — 11 years for all financial records. Financial data is never hard-deleted.
6. Data Classification Scheme
| Level | Label | Examples | |
|---|---|---|---|
| L1 | Public | Exchange rates, fee schedule, |
|
| L2 | Internal | ||
| L3 | Confidential | ||
| L4 | Restricted | sub |
Tax ID handling:
Serbia: PIB (Poreski identifikacioni broj) — 9 digits; JMBG (Jedinstveni matični broj građana) — 13 digitsBiH: JIB (Jedinstveni identifikacioni broj) — 13 digitsCroatia: OIB (Osobni identifikacijski broj) — 11 digits
All tax IDs treated as L4 Restricted data. Stored with access logging. Never included in JWT payloads or logs.
7. Data Subject Rights Implementation
Inventory
| Life of account | ||||
sub |
||||
| Legal obligation | ||||
| Transaction records | L3 Confidential | 5 years (AML) + accounting | Legal obligation | |
| Bank account balances | L3 Confidential | Session only — not persisted | Contract | |
| IP addresses / logs | L2 Internal | 90 days |
DPIA
Erasure exception: Financial records (invoices, expenses, transactions) are retained for the legally required period (10-11 years depending on country) even after user account erasure. Only PII (email, name, password hash) is anonymized.
8. Third-PartyA Data Processors
Protection Impact Assessment (DPIA) has been conducted. Document: data-protection-impact-assessment.md
DPIA trigger: Processing of fødselsnummer at scale, BankID integration, cross-border transfers to Serbia/BiH.
Cross-Border Data Transfers
| Standard GDPR protections | ||||
| Serbia (RS) | No adequacy decision | SCCs (Standard Contractual Clauses) + Transfer Impact Assessment (TIA) | ||
| Bosnia & Herzegovina (BA) | No adequacy decision | SCCs + Transfer Impact Assessment (TIA) | ||
| USA (AWS, Sentry, BetterStack) | No adequacy decision | SCCs + DPA signed |
Note: Serbia and Bosnia & Herzegovina do not have EU adequacy decisions. All data transfers involving these countries require SCCs and a documented TIA before data flows.
6. ICT Security — IKT-forskriften / DORA
IKT-forskriften (FOR-2003-05-21-630)
Currently applicable to financial enterprises in Norway.
| Requirement | Sections | Status |
|---|---|---|
| ICT security policy | §§ 5-6 | Document: ikt-sikkerhetspolicy.md — Draft |
| Incident handling | § 8 | Document: hendelseshaandtering.md — Draft |
| Business continuity | § 9 | Document: beredskapsplan.md — Draft |
| Outsourcing policy | § 10 | Document: utkontraktering-policy.md — Draft |
| Access control | § 5 | Implemented: RBAC, session revocation, JWT |
| Encryption | § 6 | Implemented: TLS 1.3, AES-256, bcrypt(12) |
DORA (EU) 2022/2554
DORA is expected to be incorporated into Norwegian law approximately 2026 H2 (via EEA Agreement).
| DORA Requirement | Article | Drop Plan |
|---|---|---|
| ICT risk management framework | Art. 6 | Mapped to IKT-forskriften currently |
| ICT incident classification | Art. 18 | Breach response plan covers this |
| Major incident reporting | Art. 19 | Finanstilsynet + Datatilsynet within 72h |
| Digital operational resilience testing | Art. 24-25 | Annual pentest planned (Phase 3) |
| ICT third-party risk management | Art. 28-44 | Outsourcing policy + DPAs |
| Encryption standards | Art. 9(4)(d) | AES-256-GCM, TLS 1.3 |
7. Valutaregisterloven
Law: Valutaregisterloven (LOV-2003-06-06-39)
All cross-border payment service providers must report transactions to Statistisk sentralbyrå (SSB) and Norges Bank.
| Requirement | Threshold | Reporting Recipient |
|---|---|---|
| Cross-border transactions | All (> 0 NOK) | SSB via Valutaregisteret |
| Aggregate statistics | Monthly | Norges Bank |
| Format | XML via SSB API | Valutaregisteret |
Implementation: Phase 2 — automated reporting pipeline to Valutaregisteret for all completed remittances.
8. Compliance Gap Summary
Overall compliance readiness: 8/100 (MVP stage — expected)
| Area | Readiness | Gap |
|---|---|---|
| Licensing (Finanstilsynet) | 0% | No license — no live transactions permitted |
| PSD2 / SCA | 10% | BankID not implemented; SCA not in place |
| AML/KYC | 5% | Mock KYC only; no real identity verification |
| GDPR | 15% | Privacy notice + DPIA drafted; no DPO appointed |
| ICT Security | 25% | Security hardened (post 2026-02-13); pentest pending |
| Valutaregisterloven | 0% | No SSB reporting pipeline |
| Consumer Protection | 20% | Terms drafted; no formal complaints process |
Phase 2 completion target: 60% (licensing + BankID + real KYC + GDPR implementation) Phase 3 completion target: 85% (pentest + Valutaregisteret + full GDPR + DPO)
9. Compliance Monitoring Plan
Monthly Checks
- npm audit — dependency vulnerability check
- Review Sentry errors for security-relevant issues
- BetterStack uptime + alert review
- Transaction volume check against license threshold (after licensing)
Quarterly Checks
- KYC data retention audit (5-year AML retention compliance)
- GDPR data subject rights fulfillment review
- JWT_SECRET rotation (quarterly per key management policy)
- Review of AML transaction monitoring rules effectiveness
- Security exceptions review
Annual Checks
- External security penetration test (required before Phase 3 launch)
- AML risk assessment review (Hvitvaskingsloven § 6)
- DPIA review (GDPR Art. 35 — when processing changes materially)
- All encryption keys rotation audit
- Regulatory change review — Finanstilsynet circulars
- DPAs review (AWS, Cloudflare, Sentry, BetterStack, Sumsub, BankID Norge AS)
10. Third-Party Compliance
All third-party processors of personal data require a signed Data Processing Agreement (DPA).
| Vendor | Role | DPA Status | Data Transferred | |
|---|---|---|---|---|
| AWS (Frankfurt, Ireland) | Infrastructure + hosting | |||
| Cloudflare (EU edge) | CDN, WAF, |
|||
| BetterStack | Required | Log data | ||
| Sumsub | KYC verification (Phase 2) | Required | Name, photo ID, fødselsnummer | |
| BankID Norge AS | eID authentication (Phase 2) | Required | Name, fødselsnummer, DOB | |
| Marqeta / Lithic | Card issuance (Phase 3) | Required | Payment data (PCI-DSS) |
DPA status:requirement source: AllGDPR DPAsArt. must28; bePersonopplysningsloven signed§ before first paying customer. Railway EU West region must be explicitly configured to ensure EU data residency.5
9.11. ComplianceDocument Roadmap
Phase 1 — Pre-Launch (GDPR baseline)
Privacy policy published (HR GDPR applicable immediately; RS/BA when launched)Terms of Service publishedUser consent mechanism at registrationData deletion workflow implemented and testedData export endpoint implementedDPAs signed with Railway, Vercel, Cloudflare, SendGridRailway EU West region confirmedBreach notification process documented
Phase 2 — Serbia Launch (3-6 months)
Legal review by Serbian lawyer (računovodstveno pravo + ZZPL)Serbian CoA seed data (Pravilnik 2021)VAT calculation at 20% / 10%SEF XML export (UBL 2.1)SEF API integration for B2B e-invoicingAPR financial report export (Bilans stanja, Bilans uspeha)ZZPL processing register documented
Phase 2 — Croatia Launch (concurrent or shortly after)
Legal review by Croatian lawyer (Zakon o računovodstvu + GDPR)Croatian CoA seed data (RRiF standard)VAT calculation at 25% / 13% / 5%FINA certificate acquisition for HR-FISKHR-FISK API integration (mandatory for all invoices Jan 2026+)FINA RGFI report exportAZOP processing register documented
Phase 3 — BiH Launch (12-18 months)
Legal review by BiH lawyer (FBiH + RS entity distinction)BiH CoA seed data (FBiH Pravilnik 2022)VAT calculation at 17% (UIO)Monitor CPF technical specs publication (~2027)FBiH vs RS entity distinction in org settingsAZLP breach notification process confirmed
10. Risk AssessmentRegister
personvernerklaering.md |
|||
dpia-vurdering.md |
|||
brukervilkar.md |
|||
hvitvaskingsrutiner.md |
|||
risikovurdering-hvitvasking.md |
|||
ikt-sikkerhetspolicy.md |
|||
| Incident |
hendelseshaandtering.md |
Draft | Security |
| Business continuity | beredskapsplan.md |
Draft | Operations |
| Outsourcing policy | utkontraktering-policy.md |
Draft | Legal |
| Internal control | internkontroll.md |
Draft | Compliance |
| Suitability assessment | egnethetsvurdering.md |
Draft | Legal |
| Complaint handling | klagebehandling.md |
Draft | Operations |
| Licensing preparation | konsesjonssoknad-forberedelse.md |
Draft | Legal |
| Gap analysis | drop-gap-analysis-v2.md |
Complete | Compliance |
| Regulatory map | drop-regulatory-map-v2.md |
Complete | Legal |
| Security architecture | security-architecture.md |
Draft | Security |
| Encryption policy | data-encryption-policy.md |
Draft | Security |
| Key management policy | key-management-policy.md |
Draft | Security |
| Breach response plan | data-breach-response-plan.md |
Draft | Security |
| Security testing policy | security-testing-policy.md |
Draft | Security |
Related Documents
Security Architecture:security-architecture.mdDPIA:data-protection-impact-assessment.mdBreach Response Plan:data-breach-response-plan.mdBilko Compliance:../../products/Bilko/docs/security/COMPLIANCE.mdSerbia Regulatory:../../products/Bilko/docs/regulatory/RS/README.mdBiH Regulatory:../../products/Bilko/docs/regulatory/BA/README.mdCroatia Regulatory:../../products/Bilko/docs/regulatory/HR/README.md
Approval
| Role | Name | Date | Signature |
|---|---|---|---|
| Author | 2026-02-23 | ||
| DPO | |||
| Legal Counsel | |||
| CEO |