Oxofolio outside India — what travels and what is a local pack

The three layers

What travels, what is already localised, and what ships as a local pack.

Drawn here explicitly, because the alternative is that you find it yourself, in a demo, at the worst possible moment.

Layer	Where it applies
The document engine Inventory, unlock, compress, combine, extract, OCR, sample, protect, organise, assemble, convert, images, mark-up, the viewers	Anywhere No part of this knows what country it is in. A PDF, a locked bank statement and a scanned invoice are the same problem in every market.
The evidence layer Processing log, file seal, duplicate detection, sampling certificate, erasure certificate	Anywhere The standards behind it are international — ISA 530, ISA 230, ISQM 1, GDPR Articles 30 and 32, NIST SP 800-88. National numbering is one country’s adoption of the same text.
Dates and numbers	Already localised Date order and decimal separator are a per-folder setting — India, UK, EU, US or ISO. It is the difference between reading 03/04/2026 and guessing at it.
Personal-data detection	Partly universal IBAN, e-mail and labelled account numbers work anywhere. The rest of the shipped set is Indian.
The client-mixing check	Signal universal, numbers Indian A checksummed registration number recurring across a folder identifies the entity the folder is about. The numbers it looks for today are GSTIN and PAN.
The retention clock	Six Indian presets, plus your own A period you set, with your own citation and anchor date, is a first-class option rather than an escape hatch.

Data residency

There is no server, so there is no residency question.

A claim that rests on there is no server needs no hosting region, no sub-processor list, no cross-border transfer mechanism and no data-processing addendum about infrastructure that does not exist.

Nothing to host in your region, because nothing is hosted
In a market with a data-localisation rule, satisfied by construction
In one without, the question simply leaves the conversation
Licensing is offline too — Ed25519, verified on your own machine, no activation call from any country

This is the rare claim that gets stronger the further from home it is sold. Ask your IT team to run netstat while the app is open — that is the whole demonstration.

What a firm’s IT usually asks

Where is our data processed? On the machine in front of you, and nowhere else.
Who are your sub-processors? For the application, none. There is no pipeline for a document to enter.
What is the transfer mechanism? There is no transfer.
What happens if your company disappears? The licence file on your machine keeps working; it was never checked against anything of ours.

Standards

The international instrument first, the local adoption after it.

What the tool produces, stated plainly. Your own adviser maps output to obligation — this is a description of software, not legal advice, and nothing here is a compliance guarantee.

Standard	What Oxofolio produces	Adopted in India as
ISA 530 Audit sampling	A reproducible selection with a certificate stating the algorithm, plus a fingerprint of the population it was drawn from	SA 530
ISA 230 ¶15–16 Documentation	A seal taken at the report date, and an exact added / removed / altered difference afterwards	SA 230 ¶15–16
ISQM 1 (formerly ISQC 1) File assembly	Evidence of what the engagement file held on the report date	SQC 1 ¶82
GDPR Article 30	A draft record of processing activities, with the gaps printed as outstanding rather than left blank	Comparable duties under the DPDP Act
GDPR Article 32 Security of processing	AES-256 encryption of every copy that leaves the firm, re-opened and verified before the file is handed to you	Comparable duties under the DPDP Act
NIST SP 800-88	Erasure certified honestly at the “Clear” level, with the disk-encryption state recorded, because that is what overwriting on modern storage can actually claim	Cited directly; it is not a national standard

Personal data

What the scanner finds anywhere, and what ships as the Indian pack.

Every match is validated rather than pattern-matched, so a twelve-digit invoice total is not mistaken for an identity number — and once something is found, removing it is the same operation everywhere.

◍

Works in any country

IBAN — checksum-validated, roughly 80 countries
E-mail addresses
Bank account numbers sitting next to a label that says so
Document metadata — author, producing software, old titles, revision history

◈

The Indian pack, shipped

Aadhaar, with UIDAI-style masking
PAN and GSTIN, checksum-validated
IFSC codes
Indian mobile numbers

＋

Adding your country

A detector is one row: a pattern, a validator, and whether a nearby label is required. A UK National Insurance number, an EU VAT number, a US SSN, EIN or ABA routing number is that row plus its check rule.

The redaction itself, the read-back verification, the page rectangles and the severity ordering are already format-agnostic — they never knew which country the number came from.

We would rather describe the mechanism than the coverage. The validator is per-format and the table is open is checkable. Supports any country is a sentence you would test with your own national identifier in the first ten minutes, and rightly.

Retention

Six Indian statutes, or the period your own regulator sets.

Set how long a folder should be kept, list what is due for deletion, and get a certificate naming everything that was destroyed. The clock is a preset — and one of the presets is yours.

Six statutory presets citing Indian law, for firms working here
A firm-defined period elsewhere: a label, an authority, a number of years and an anchor date, all of them yours
The certificate names the authority you cited, not one we assumed
Erasure is reported at the level it can honestly claim, never as more

See the evidence log

Dates and numbers, per folder

Chosen, never inferred. The same string means different dates in different markets, and a tool that guesses is a tool that quietly mis-reads a bank statement.

India — DD/MM/YYYY, 1,00,000.00
UK — DD/MM/YYYY, 100,000.00
EU — DD.MM.YYYY, 100.000,00
US — MM/DD/YYYY, 100,000.00
ISO — YYYY-MM-DD

Straight about the gaps

What is not there yet, in the same words we would use internally.

A list you would otherwise discover during a trial. If one of these matters to you, tell us — it is the fastest way to move it up the queue.

The interface is English only

There is no translation layer at all. English is the working language of the profession in most of the markets we are talking to, which makes this a market-entry decision rather than a blocker — but it is not a small change and we will not pretend otherwise.

OCR ships with English only

The recognition engine is bundled with the app rather than fetched, so an additional language is a build change on our side, not a download on yours.

File assembly assumes sixty days

Sixty days is the IAASB deadline and it is currently a constant rather than a setting. Firms under PCAOB rules have forty-five, and would need it made configurable before the assembly clock is useful to them.

The mixing check looks for Indian registrations

It flags a folder that appears to contain more than one client’s papers by spotting a checksummed registration number that recurs. The signal is universal; the numbers it knows today are GSTIN and PAN.

No national identifier pack outside India has shipped

IBAN, e-mail and labelled account numbers already work everywhere. A NINO, VAT, SSN, EIN or routing-number pack is a table row and its check rule — small, but not yet written, and we would rather say so than let you find out during a trial.

Buying from outside India

Prices are quoted in rupees or US dollars, and you can switch between them on the pricing page. Dollar purchases go through Dodo Payments as merchant of record, so whatever sales tax or VAT applies where you are is worked out and collected there rather than left to you. Nothing about where you are changes the software or the licence — it is the same offline file either way.

Built for one profession, not for one country.