Trust

Security, data and continuity

Orizn is built and operated by one person. This page tells you exactly what that means before you put us in a procurement process: what the API touches, where it runs, who else is involved, which certifications we do not hold, and what you keep if we stop. Anything we have not verified is marked to be completed rather than guessed.

Last updated: 28 October 2026

1. What the API processes

The short version: public regulatory data in, public regulatory data out. No traveller ever touches this API.

InputsEvery data endpoint accepts ISO 3166-1 alpha-3 country codes and a language code (/changes is switched off for now and answers 503 unavailable). The pair endpoints reject any country code that is not /^[A-Z]{3}$/. There is no field for a name, a passport number, a date of birth or an itinerary. You cannot send us traveller identity data even if you wanted to.
MethodThe data endpoints (/api/v1/visa, /check, /bulk, /group, /changes, /score) are read-only GET requests over a public dataset of regulatory rules. Nothing you send is written into the dataset.
Not in scopeNo AI model sees API traffic: the API path performs a database lookup, not a generation. The LLM features that exist elsewhere on orizn.app are not reachable from /api/v1/visa.

2. What we hold about you as a customer

You are a company with an account, so there is some personal data — the people on your side who hold API keys.

AccountEmail, name, optional company, plan, API key, and the IP address the account was created from (kept to enforce the anti-abuse signup cap). Sign-in is by emailed magic link; the API key is 24 random bytes and you can rotate it from the dashboard at any time.
Request logsOne row per API call: account id, API key, endpoint, the country-code pair, language, HTTP status, response time, source IP, User-Agent header (truncated to 255 characters), timestamp. That is the complete list of columns. Rows older than 12 months are deleted by a weekly automated job, per our Privacy Policy.
BillingStripe Checkout is hosted by Stripe — card numbers never reach our servers. We store the Stripe identifiers and the subscription state needed to serve your plan.
Product analyticsPostHog runs in the browser on the website and dashboard only, never on the API request path. Autocapture, heatmaps and session replay are disabled, cross-subdomain cookies are off, and personal-data properties are masked before send.

3. Where it runs

HostingOne Hetzner Cloud server operated by Hetzner Online GmbH (Germany), in the Helsinki (Finland) data centre — EU. The application and its PostgreSQL database run on that single host as Docker containers.
EdgeCloudflare sits in front for DNS, TLS termination, caching and DDoS protection. Rate limiting and abuse guards trust Cloudflare's cf-connecting-ip as the client identity.
In transitHTTPS everywhere, with HSTS (max-age one year, includeSubDomains, preload) plus X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy set on every response — except the widget frames served on embed.orizn.app/frame/*, which are built to be embedded on other sites and drop X-Frame-Options for that reason.
At restTo be completed. Disk-level encryption and the backup schedule of the database host have not been documented here yet, and we will not claim a control we have not written down.
AccessOne person — the founder — has production access. Small blast radius, and a bus factor of one; the continuity commitment below is the answer to the second half of that sentence.

4. Subprocessors

The complete list. We do not sell data, and we share it with no one outside this table except where the law compels us.

ServicePurposeLocation
Hetzner Online GmbHServer and database hostingEU — Helsinki, Finland
CloudflareDNS, TLS, CDN, DDoS protectionGlobal, EU included
StripePayments and subscriptionsEU / USA
ResendTransactional email (verification, quota alerts)USA
PostHogProduct analytics on the website and dashboardEU

We will announce a new subprocessor by email to account holders before it starts processing customer data.

5. What we do not have

The section most vendor pages leave out. For a read-only API with no personal data below a few hundred dollars a month, this is usually accepted — and you should know it now rather than three weeks into a review.

  • We are not SOC 2 certified. A Type II report costs 30–50k$ and 6–12 months, and we would rather tell you that than imply an audit that never happened.
  • We are not ISO 27001 certified, and we hold no other security certification.
  • No third-party penetration test has been performed. No bug bounty programme exists.
  • There is no 24/7 on-call rotation. Support and incident response are best-effort during European working hours.
  • No plan carries a contractual uptime SLA: the Terms of Service attach no credit or remedy to availability. The Production plan card says "99.9% uptime SLA, measured on the status page"; until the Terms say otherwise, read it as a target with no remedy attached. Uptime is measured since 13 August 2026 by a real probe (GET /api/v1/visa/uptime) — the previous 99.9% badge was hardcoded, not measured, and was removed on 12 August 2026 rather than left to mislead a due diligence.
  • The service runs in a single region on a single host. There is no multi-region failover.

6. What you get instead of a certification

A certificate says a process was followed. These are properties you can verify yourself, in one API call, in ten minutes — and they are the ones that decide whether our data can be trusted in your product.

ProvenanceEvery response carries source, source_url and last_verified_at. Where we have not recorded a source for a pair, those fields are null — you get a null, never a plausible-looking date. A reviewer can tell verified data from unverified data without asking us.
Legal uncertaintyPairs whose regime is legally unsettled carry requirement_status: "uncertain" plus a note explaining why. Example: Burkina Faso, Mali and Niger left ECOWAS on 29 January 2025, so visa-free movement with the remaining member states now rests on revocable unilateral declarations rather than a treaty. The requirement still says what happens at the border today; the status says the right no longer exists.
Declared unknownsPOST /api/v1/visa/decision evaluates a whole itinerary and returns explicit unknown entries with a reason instead of a default value, and each field declares whether it was resolved at pair or destination granularity. A gap is reported as a gap.
Measured or nothingGET /api/v1/visa/uptime returns only checks that were actually run. With no measurements it returns measuring: true and null figures rather than synthesising a percentage — the same reason the hardcoded 99.9% badge was deleted.

7. Continuity commitment

The real question about a one-person vendor is not whether we are SOC 2 certified. It is what happens to you if the founder stops. Here is the written answer.

  • If the Visa API is discontinued, paying customers receive at least 30 days' written notice at the email on the account.
  • Within that notice period, and on request at any other time, we deliver a complete export of the dataset your plan covers — every passport × destination pair, all fields, all 15 languages — as JSON or CSV. This is not the metered /bulk endpoint: it is a one-shot full extract delivered out of band.
  • That final snapshot comes with a perpetual, irrevocable, worldwide, royalty-free licence to use it internally in your product, surviving the end of your subscription. Redistribution and resale of the raw data remain excluded, exactly as in the Terms of Service — the licence removes your dependency on us, it does not turn the dataset into a product you can sell.
  • Concretely: the worst case for you is a frozen dataset you keep forever, not a 404 and a rewrite.

8. Documents

Both documents are drafts prepared in good faith and not reviewed by a lawyer. Have your counsel read them before you rely on them.

CAIQ-Lite (JSON) ↓

A pre-filled vendor security questionnaire in the CAIQ-Lite shape: ~40 answers covering governance, data handling, infrastructure, incident response. Every answer is yes, no, or not-applicable with a one-line justification — no aspirational answers.

Data Processing Agreement — draft (Markdown) ↓

A GDPR Article 28 processor agreement covering the customer account data we hold. Send it back signed, or send yours and we will review it.

9. Reporting a security issue

Write to [email protected] with [SECURITY] in the subject. Include what you found, how to reproduce it, and the impact you think it has.

  • We acknowledge within 3 business days and tell you what we intend to do. There is no paid bounty — we are one person, and pretending otherwise would waste your time.
  • Test against your own account only. Do not run load or denial-of-service tests, do not access another customer's data, and do not exfiltrate the dataset. Research conducted in good faith within those limits will not be met with legal action.
  • If a breach affects your data, we notify you without undue delay and, where required, within 72 hours of becoming aware of it.