{
  "document": "CAIQ-Lite (self-assessment, not audited)",
  "vendor": "Orizn — Visa API",
  "service": "https://visa.orizn.app",
  "contact": "hello@orizn.app",
  "last_updated": "2026-08-12",
  "disclaimer": "Self-assessment by the sole operator of the service. No independent audit backs these answers. Prepared in good faith; not reviewed by a lawyer or an auditor.",
  "scope": "Read-only REST API over a public dataset of visa regulations. Inputs are ISO 3166-1 alpha-3 country codes only. No traveller personal data is accepted, processed or stored. Customer personal data is limited to account holders (email, name, optional company, API key, request logs including source IP).",
  "answers": [
    {
      "id": "GRC-01",
      "question": "Do you have a documented information security programme?",
      "answer": "no",
      "notes": "Single-operator service. Security decisions are made and documented in code review comments and this page, not in a formal ISMS."
    },
    {
      "id": "GRC-02",
      "question": "Do you hold SOC 2 Type I or Type II?",
      "answer": "no",
      "notes": "Not certified. Cost and duration are out of reach for a one-person vendor; we say so publicly rather than imply otherwise."
    },
    {
      "id": "GRC-03",
      "question": "Do you hold ISO/IEC 27001 or an equivalent certification?",
      "answer": "no",
      "notes": "No security certification of any kind."
    },
    {
      "id": "GRC-04",
      "question": "Do you carry cyber liability insurance?",
      "answer": "no",
      "notes": "To be completed — not currently held."
    },
    {
      "id": "GRC-05",
      "question": "Do you perform a formal annual risk assessment?",
      "answer": "no",
      "notes": "Risk is reviewed continuously and informally; there is no dated artefact to share."
    },
    {
      "id": "A&A-01",
      "question": "Are independent third-party audits performed?",
      "answer": "no",
      "notes": "None performed to date."
    },
    {
      "id": "A&A-02",
      "question": "Will you complete customer security questionnaires?",
      "answer": "yes",
      "notes": "This document, plus written answers to specific questions at hello@orizn.app."
    },
    {
      "id": "A&A-03",
      "question": "Do you permit customer-initiated security testing?",
      "answer": "yes",
      "notes": "Against your own account, with prior notice by email, excluding load and denial-of-service testing and excluding bulk extraction of the dataset."
    },
    {
      "id": "DSP-01",
      "question": "Is any end-user or traveller personal data processed by the API?",
      "answer": "no",
      "notes": "Data endpoints accept only ISO3 country codes and a language code; other inputs are rejected by the handlers."
    },
    {
      "id": "DSP-02",
      "question": "Is customer personal data processed?",
      "answer": "yes",
      "notes": "Account holders only: email, name, optional company, API key, signup IP, and request logs containing the source IP of API calls."
    },
    {
      "id": "DSP-03",
      "question": "Is data classified and inventoried?",
      "answer": "no",
      "notes": "The full inventory is short enough to be listed in prose on the trust page; no formal classification scheme exists."
    },
    {
      "id": "DSP-04",
      "question": "Do you sell or share customer data with third parties?",
      "answer": "no",
      "notes": "Never sold. Shared only with the subprocessors listed on the trust page, and with authorities where legally compelled."
    },
    {
      "id": "DSP-05",
      "question": "Is there a defined data retention period?",
      "answer": "yes",
      "notes": "API request logs: 12 months per the Privacy Policy, then deleted by a weekly automated job (scripts/purge-api-logs.sh). Account data: until account deletion. Billing records: as required by law."
    },
    {
      "id": "DSP-06",
      "question": "Can a customer request deletion of their data?",
      "answer": "yes",
      "notes": "By email to hello@orizn.app; account and associated logs are deleted, billing records retained as legally required."
    },
    {
      "id": "DSP-07",
      "question": "Can a customer export their data?",
      "answer": "yes",
      "notes": "Account data and request logs on request. The dataset itself is exported in full under the continuity commitment."
    },
    {
      "id": "DSP-08",
      "question": "Is GDPR applicable and addressed?",
      "answer": "yes",
      "notes": "Operator and infrastructure are in the EU. A draft Article 28 DPA is available at /trust/dpa.md, pending legal review."
    },
    {
      "id": "DSP-09",
      "question": "Are international transfers of personal data documented?",
      "answer": "yes",
      "notes": "Stripe (EU/USA) and Resend (USA) receive customer account data. Both publish standard contractual clauses. Data residency of the service itself is EU."
    },
    {
      "id": "CEK-01",
      "question": "Is data encrypted in transit?",
      "answer": "yes",
      "notes": "HTTPS only, TLS terminated at Cloudflare. HSTS max-age 31536000, includeSubDomains, preload, set on every response."
    },
    {
      "id": "CEK-02",
      "question": "Is data encrypted at rest?",
      "answer": "no",
      "notes": "To be completed. Disk-level encryption on the database host has not been verified and documented, so we do not claim it."
    },
    {
      "id": "CEK-03",
      "question": "Are API keys and secrets managed securely?",
      "answer": "yes",
      "notes": "API keys are 24 cryptographically random bytes, transmitted in the x-api-key header, and rotatable from the dashboard at any time. Application secrets live in the server environment file, never in the repository."
    },
    {
      "id": "CEK-04",
      "question": "Are API keys stored hashed?",
      "answer": "no",
      "notes": "Keys are stored as issued so the dashboard can display them, and appear in request-log rows. Treat a key as a shared secret and rotate it if exposed."
    },
    {
      "id": "IAM-01",
      "question": "Is production access restricted to authorised personnel?",
      "answer": "yes",
      "notes": "One person — the founder — has production access. No contractors, no support staff."
    },
    {
      "id": "IAM-02",
      "question": "Is multi-factor authentication enforced on administrative accounts?",
      "answer": "no",
      "notes": "To be completed. Deployment to the production server uses SSH key authentication; MFA status on the infrastructure provider accounts has not been documented here, so it is not claimed."
    },
    {
      "id": "IAM-03",
      "question": "Do customers authenticate with MFA?",
      "answer": "no",
      "notes": "Dashboard sign-in is by emailed magic link — possession of the mailbox is the factor. There is no password to phish, and no second factor either."
    },
    {
      "id": "IAM-04",
      "question": "Is access reviewed periodically?",
      "answer": "na",
      "notes": "One account holder; there is nothing to review."
    },
    {
      "id": "IVS-01",
      "question": "Where is the service hosted?",
      "answer": "yes",
      "notes": "One Hetzner Cloud server (Hetzner Online GmbH, Germany) in the Helsinki, Finland data centre — EU. Application and PostgreSQL run on that host in Docker."
    },
    {
      "id": "IVS-02",
      "question": "Is the environment segmented from other workloads?",
      "answer": "yes",
      "notes": "Container-level separation on a dedicated cloud instance. No shared tenancy with other companies' workloads."
    },
    {
      "id": "IVS-03",
      "question": "Is there multi-region redundancy or failover?",
      "answer": "no",
      "notes": "Single region, single host. An outage of that host is an outage of the API."
    },
    {
      "id": "IVS-04",
      "question": "Is DDoS protection in place?",
      "answer": "yes",
      "notes": "Cloudflare fronts every request; per-key and per-IP rate limits and anti-extraction guards are enforced in the application."
    },
    {
      "id": "BCR-01",
      "question": "Are backups performed and tested?",
      "answer": "no",
      "notes": "To be completed. A backup schedule and a tested restore procedure have not been documented; we will not claim them until they are."
    },
    {
      "id": "BCR-02",
      "question": "Is there a documented disaster recovery plan with RTO/RPO?",
      "answer": "no",
      "notes": "No RTO or RPO is committed. Do not design a system that assumes one."
    },
    {
      "id": "BCR-03",
      "question": "Is there a contractual uptime SLA?",
      "answer": "no",
      "notes": "Self-serve plans carry no SLA. GET /api/v1/visa/uptime publishes only checks that were actually run and returns measuring: true with null figures when there is nothing to report, rather than synthesising a percentage."
    },
    {
      "id": "BCR-04",
      "question": "Is there a vendor-failure / exit plan for customers?",
      "answer": "yes",
      "notes": "Yes, and it is the main control we offer: 30 days' notice, a full dataset export, and a perpetual internal-use licence on the final snapshot. See the continuity commitment on the trust page."
    },
    {
      "id": "LOG-01",
      "question": "Are application and access events logged?",
      "answer": "yes",
      "notes": "One row per API call: account, key, endpoint, country-code pair, language, status, latency, source IP, timestamp."
    },
    {
      "id": "LOG-02",
      "question": "Is there centralised log aggregation and alerting (SIEM)?",
      "answer": "no",
      "notes": "Logs are queried directly in PostgreSQL. Automated alerting exists for quota thresholds only, not for security events."
    },
    {
      "id": "LOG-03",
      "question": "Are logs protected against tampering?",
      "answer": "no",
      "notes": "Logs live in the same database as the application data and are not write-once."
    },
    {
      "id": "SEF-01",
      "question": "Is there a documented incident response process?",
      "answer": "yes",
      "notes": "Lightweight and published: report to hello@orizn.app with [SECURITY] in the subject, acknowledgement within 3 business days, customer notification without undue delay and within 72 hours where legally required."
    },
    {
      "id": "SEF-02",
      "question": "Is there 24/7 on-call coverage?",
      "answer": "no",
      "notes": "Best effort, European working hours. One person."
    },
    {
      "id": "SEF-03",
      "question": "Have you experienced a security incident affecting customer data?",
      "answer": "no",
      "notes": "No incident affecting customer personal data. In July 2026 the public regulatory dataset was extracted at scale through mass free-account creation; three anti-extraction guards were deployed in response. No customer data was involved."
    },
    {
      "id": "TVM-01",
      "question": "Are third-party penetration tests performed?",
      "answer": "no",
      "notes": "None to date."
    },
    {
      "id": "TVM-02",
      "question": "Are dependencies monitored for known vulnerabilities?",
      "answer": "no",
      "notes": "No automated scanning is configured. The dependency surface is deliberately small (a dozen production packages) and updated manually."
    },
    {
      "id": "TVM-03",
      "question": "Is a bug bounty programme offered?",
      "answer": "no",
      "notes": "No paid bounty. Good-faith reports are welcome and will not be met with legal action."
    },
    {
      "id": "CCC-01",
      "question": "Is there a change management process?",
      "answer": "no",
      "notes": "Changes are version-controlled and deployed by script with idempotent database migrations, but there is no separate approver: the author and the reviewer are the same person."
    },
    {
      "id": "AIS-01",
      "question": "Are inputs validated at the API boundary?",
      "answer": "yes",
      "notes": "Country codes are validated against a strict pattern and rejected otherwise; database access on the API path uses parameterised queries."
    },
    {
      "id": "AIS-02",
      "question": "Are security headers set on responses?",
      "answer": "yes",
      "notes": "HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy applied globally."
    },
    {
      "id": "AIS-03",
      "question": "Does the API disclose the provenance and the limits of the data it returns?",
      "answer": "yes",
      "notes": "Each response carries source, source_url and last_verified_at (null where no source is recorded — never a substituted value), requirement_status: \"uncertain\" with a note on legally unsettled regimes, and an X-Orizn-License header. POST /api/v1/visa/decision returns explicit unknown entries with a reason instead of defaults, and declares the granularity of each field."
    },
    {
      "id": "HRS-01",
      "question": "Are background checks and security training performed for staff?",
      "answer": "na",
      "notes": "No employees and no contractors. The vendor is one person."
    },
    {
      "id": "STA-01",
      "question": "Is the subprocessor list published and maintained?",
      "answer": "yes",
      "notes": "Published at https://visa.orizn.app/trust. Customers are notified by email before a new subprocessor begins processing their data."
    }
  ]
}