Named ownership
Each policy domain is designed to carry an owner and escalation route when the admin layer is connected.
Compliance Center
Financing with explicit accountability.
The compliance centre separates product communication from regulated responsibility and organises the control domains that matter across onboarding, financing, servicing, data and customer treatment.
Control library
The perimeter is part of the product.
These summaries are a navigation layer, not legal advice and not a substitute for the underlying policies, licences or customer disclosures. The future admin panel can attach controlled documents and effective dates to each domain.
Regulated financingBRSA perimeter
Financing activity is carried out by Team Finansman A.Ş.; product, application and financing communications should remain attributable to that licensed entity.
AML / KYCCustomer due diligence
Identity, business verification, screening and ongoing review form part of the financial-crime control environment.
Data protectionKVKK & privacy
Customer and business data needs defined purpose, retention, access and disclosure controls, together with clear privacy notices and rights routes.
Responsible financingCustomer treatment
Product information, fees, obligations, application outcomes and complaint routes should be presented clearly and consistently.
Operational controlsAccess & change
Privileged access, changes to decisioning logic and production operations should be governed, logged and reviewable.
PartnersThird-party oversight
Dealer, embedded and service-provider relationships require documented responsibilities for data, customer experience, security and compliance.
Publication architecture01 02 03
Every policy needs an owner, version and route.
Versioned publication
Effective dates, superseded versions and controlled attachments can be managed from the future admin panel.
Audience separation
Public disclosures, customer notices and controlled diligence evidence stay separate rather than being mixed into one download folder.