One platform worldwide: languages, formats and local rules
Phoeniks is built for customers in every country, from the start, with no single launch country or segment. That means more than translation: languages and right-to-left scripts, local formats and area units, currencies, and data and backups kept in the jurisdiction they belong to.
- The Phoeniks team
Worldwide by decision#
The platform is designed for customers in every country. Its multi-region design covers data residency, languages and right-to-left scripts, local formats, currencies, taxes, payment methods and round-the-clock support. Coverage of land data still varies by country, because it depends on what each country publishes; where data is missing, the platform says so.
Languages, published after review#
The application is complete in English and French: navigation, footer, breadcrumbs, empty and error states. Other interface languages are prepared and published only after review. When a string is not yet translated, the English fallback is shown and marked as a partial translation rather than left blank.
Formats and units that follow the user#
- Numbers, dates and currencies formatted for the user's locale.
- Area units that follow local practice.
- Foundations for right-to-left scripts in the design system.
- A listing title keeps its real source language, with its language tag.
Data that stays where it belongs#
Data and backups are kept in the jurisdiction of the data. Text sent for translation is stripped of personal data first and processed inside the data's region. These rules come before any convenience of operation.
Sources#
- Phoeniks release notes: https://phoeniks.org/en/release-notes
Related pages
Method
How Phoeniks makes a farmland figure testable: sources, evidence levels, reproducibility.
Regulation
What the texts ask of land and agricultural data, read at the source and dated.
Product
What the platform does for its users, and why it is built that way.
Proof before prediction: why every farmland figure must carry its source
Why every Phoeniks figure carries its count, coverage, method, date and confidence, and shows Unavailable with the reason rather than a guess.
EUDR: what the revised dates and geolocation rules ask of land evidence
EUDR applies from 30 December 2026 (30 June 2027 for micro and small enterprises). What the geolocation, polygon and retention rules ask of land evidence.
The Data Act and agricultural data: what changes for platforms in 2026 and 2027
Data Act (EU) 2023/2854: applicable since 12 September 2025, no switching charges from 12 January 2027, and what it says about crop-yield data.
Four eyes, a reason and an audit trail: what a governed record brings
What a governed record brings: one person creates, another approves, every sensitive step carries a reason, and the trail can be verified.
Reproducing a result six months later: versions, snapshots and fingerprinted exports
Versions, snapshots and fingerprinted exports: how Phoeniks lets an auditor rebuild a figure, and the EU AI Act dates that make it matter.
See also
Request access
Institutional access. No self-serve trial.