We do not lend.
Advanta originates, verifies and services. It does not lend, set the price, decide credit or hold the money.
Fact · company.role
Security, evidence and data, as they are.
How the platform protects data, keeps evidence your auditor can recompute and stays up. Every statement comes from our facts register.
Every statement on this page comes from our facts register and is checked against the live platform before each release.
[01] Who we are
Advanta is software, not a lender.
[02] Security
Rules the database enforces, not the screen.
Row-level security on every table.
Every table in the platform database has row-level security. The two roles a browser can use can write to a table only where a row-level rule lets them, and no trigger function can be called from outside. A nightly self-check asks the database for exceptions and must find none.
Fact · security.least_privilege
Two-factor sign-in for funders.
A funder signs in with a password and an authenticator app. The database refuses funder data to a session that has not entered a code, and the server functions that act for a funder check the same, asking the database as the caller.
Fact · security.mfa
Funding rules held in the database.
The funding rules apply on every app, API and staff-console path. No screen and no API call can go around them.
Fact · gate.db_session
Each funder sees only its own requests.
A funder sees only the requests routed to it or that it has already acted on. This is row-level security on requests, offers, invoices and certificates, not a screen filter.
Fact · funder.isolation
[03] Where your data lives
In the EU, in Ireland.
Each sub-processor, what it does and where, is on our sub-processors page; how we use personal data is in our privacy policy.
Hosted in the EU.
All platform data is stored in the EU: Supabase on AWS in Ireland (eu-west-1), with each company’s data separated by row-level security.
Fact · hosting.region
[04] Evidence
Logs your auditor can recompute.
The published roots and their timestamps are on the evidence page.
A hash-chained evidence log.
Each entry in the cession evidence log carries the SHA-256 of its own payload and the hash of the entry before it. Your auditor can recompute the whole chain.
Fact · evidence.cession_chain
Sealed every night.
Every night the day’s entries are sealed into a root that carries the previous day’s root, every day since 17 September 2026.
Fact · evidence.cession_anchors
The buyer programme too.
The buyer-programme audit log is hash-chained as well, one chain per buyer, and sealed each night into a root that carries the previous day’s.
Fact · evidence.buyer_audit_log · evidence.buyer_anchors
Timestamped by two outside authorities.
Every day the roots sealed that day are published, with no company or personal data in them, and timestamped by DigiCert and Sectigo (RFC 3161). Anyone can check a token with openssl ts -verify.
Fact · evidence.external_timestamp
Read-only certificates.
Acceptance certificates are read-only for sellers, buyers and funders: no path in the platform inserts, edits or deletes one. Their status changes only through the notice lifecycle, and each change is written to the evidence log.
Fact · evidence.certificates_read_only
[05] Resilience
Rehearsed, watched and on record.
A full restore, rehearsed.
On 26 September 2026 we restored a full copy of the production database into an isolated container with no network. It took 7.1 seconds, all 284 tables matched the source, and both evidence chains verified on the copy. The drill is scheduled to repeat on the 1st of each month.
Fact · ops.restore_drill
Every service checked every 5 minutes.
8 checks cover the company app, the funder portal, the debtor pages, the assignment notices, the funder API and the website. Two failed checks in a row open an incident and alert our operations team; the public status page shows 6 components and the incident history.
Fact · ops.monitoring
Every switch, with who and why.
Our operations team sees every switch of the platform on one page, with who changed it last, when and why. A change made there needs a written reason and is recorded on the evidence chain.
Fact · ops.switches_board
[06] Privacy
A retention rule for every personal record.
Retention by rule.
A retention engine holds 63 policies, covering every kind of record with personal data, and a test fails if a table with personal data has none. Logs, sessions, analytics and temporary files are deleted on schedule, and what reaches a company’s invoice inbox is deleted 90 days after it arrived.
Fact · privacy.retention
Holds and erasure.
A legal hold stops any deletion. An erasure request keeps only the records the law requires, for anti-money-laundering and accounting, with restricted access.
Fact · privacy.retention
[07] Compliance screening
Checked against the official lists, every day.
Sanctions screening, refreshed daily.
Each company, its representative and beneficial owners, the debtors of its requests and a buyer programme’s suppliers are screened against the official EU, UN, UK and US sanctions lists (4 lists), downloaded every day into our own database. A list not refreshed for 48 hours counts as unavailable, so screening fails closed, and a possible match stops routing, offers and funding until a person decides it with a written reason.
Fact · kyc.sanctions_screening
Identity documents stay with people.
Identity documents and selfies are never sent to an AI provider: a person at Advanta checks them. Company documents are read by an AI model to help the reviewer, who decides.
Fact · kyc.identity_documents_not_ai
Credit and price are never the AI’s call.
Advanta does not decide credit or set prices, and neither does its AI. Every invoice and company file is checked automatically and explained; anything doubtful goes to a person, and approval always stays with a person.
Fact · company.role · engine.autonomous_ops
Every score names its version.
Each stored score records the model version that produced it, and each version records who approved it and why.
Fact · score.versioned
[09] DORA vendor pack
The vendor pack, for your risk team.
A technology due-diligence pack for a funder’s risk team: the DORA third-party vendor pack, covering the provider, the services and data, sub-processors, security controls, resilience, incidents, audit and exit, and a register-of-information extract, with every statement tagged with its status. Available to a funder’s risk team on request, under NDA.
Fact · security.dd_pack · company.contact
Ask for the vendor pack →
Or write to diogo@advanta.pt. The pack goes to a funder’s risk team; it is not a public download.