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.
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.
3. Where it runs
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.
| Service | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Server and database hosting | EU — Helsinki, Finland |
| Cloudflare | DNS, TLS, CDN, DDoS protection | Global, EU included |
| Stripe | Payments and subscriptions | EU / USA |
| Resend | Transactional email (verification, quota alerts) | USA |
| PostHog | Product analytics on the website and dashboard | EU |
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.
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.
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.
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.