Trust Center

Trust, security, and compliance in one place

One self-serve home for how Permafrost handles your data and proves it. Privacy, terms, sub-processors, data residency, security posture, and live certification status — no scavenger hunt.

Download our security overview

A one-page summary — architecture, tenant isolation, data handling, sub-processors, and certification posture. Read it or save it as a PDF for your procurement review. No form, no gate.

Certification status

Dates instead of silence. We state what we hold, what is underway, and what is inherited from the infrastructure provider. We never list a certification we do not hold as held.

Permafrost's own certifications

Attestations of Permafrost's product, processes, and controls.

  • SOC 2 Type 2Permafrost's own audit of its security controls over an observation window. In progress.
    In progressExpected H2 2026
  • ISO 27001Information-security management certification for Permafrost. On the roadmap after SOC 2 Type 2.
    PlannedPlanned
  • ISO 42001AI-management-system certification covering Permafrost's analysis and AI governance. On the roadmap.
    PlannedPlanned

Inherited from the infrastructure provider

Substrate certifications that attest the hosting layer beneath Permafrost, not Permafrost's own controls.

  • SOC 2Attested at the hosting layer by Permafrost's infrastructure provider. Covers the substrate, not Permafrost's own controls.
    InheritedCurrent
  • ISO 27001Inherited from the infrastructure provider's certified hosting platform.
    InheritedCurrent
  • ISO 27018Cloud-PII protection, inherited from the infrastructure provider's certified platform.
    InheritedCurrent

Policies & resources

Hosted access and riskThree sign-in methods, standing read access, and what to review before choosing hosted.Sub-processorsThe versioned register: each processor's purpose, data categories, region, and transfer basis, with change-notification.Data residency & data flowWhere data is stored and processed, the UAE controller entity, and the transfer basis for every cross-border hop.International transfer mechanismThe named instruments behind every cross-border transfer: the EU SCCs (2021/914), the UK IDTA / Addendum, the DPF where certified, and the PDPL Art. 22/23 basis.What we read & whyEvery data category we read from a connected tenant, the purpose and retention for each, and what we never read.Retention schedulePer data category: how long we keep it and the deletion trigger, reconciled with the 30-day deletion window.Breach notificationOur commitment for notifying you of a personal-data breach, the channel, and how it maps to the UK 72-hour ICO obligation.Data continuityWhat happens to your data if Permafrost is breached, acquired, or wound down — and why a Permafrost compromise is not a compromise of your clouds.Trust FAQ & questionnairePre-answered security and privacy questions, plus a downloadable CAIQ-style questionnaire pack for your procurement review.Records of processing (RoPA)Each processing purpose mapped to its lawful basis, data categories, recipients, retention, and transfer basis.Data Processing AgreementThe processor commitments we make: instructions, confidentiality, sub-processing, breach notification, and deletion.Privacy policyWhat we collect, how we use it, and your rights under the UAE PDPL, EU and UK GDPR, and CCPA/CPRA.Terms of serviceThe agreement that governs use of Permafrost, including cancellation and the deletion window.Cookie policyEvery cookie we set, why, and how long it lives. Analytics is off until you opt in.Security postureRead-only by default, zero standing write access, the operator boundary, and tenant isolation.Certification statusPlain, dated status for ISO 27001, ISO 42001, and SOC 2 — what Permafrost holds, what is underway, what is inherited, and the controls in place today.Compliance & AI governanceHow Permafrost's agent-identity controls map to the EU AI Act, NIST AI RMF, CSA AICM, and OWASP AI Exchange — raising your AI-governance maturity.Vulnerability disclosureHow to report a security issue in good faith — scope, safe harbor, how to reach us, and our response commitment.Service levels & availabilityThe availability we target, what a degraded or outage state means for your monitoring, and how we notify you during an incident.Data rights requestExercise your access, rectification, erasure, portability, restriction, objection, and consent-withdrawal rights, with a documented SLA.

Procurement & security review

The questions a security team asks before connecting a tenant, answered up front. For a completed questionnaire or evidence under NDA, reach us through your account team or the contact form.

Where is our data stored, and in which region?
Permafrost is operated by DuneCodeForge Ltd, a UAE entity, and runs on certified cloud infrastructure. The data residency page in this Trust Center names the hosting regions and the transfer basis for every cross-border hop, and the sub-processor register lists each processor's region. We read only what is needed to measure entitlement risk; we are not a log-retention destination.
What credentials do you hold for our tenant?
Microsoft collection uses read-only access. Workload identity federation uses no stored customer credentials; the optional client-secret connection stores its secret in Vault. Supported remediation uses a delegated token you authorize. It travels through your browser in a sealed session only the server can open. Permafrost accepts it once within ten minutes and stores no credential.
How long do you keep our data, and how is it deleted?
Each data category has a stated retention on the Trust Center retention schedule. When you cancel, your account enters a 30-day deletion window during which it is recoverable; after that window the data is purged. You can also request immediate deletion at any time through a data-rights request: we do not hold your data hostage to a notice period.
What is your breach-notification commitment?
If a personal-data breach affects data we process for you, we will notify the affected customer's account administrator by email without undue delay after we confirm the breach.
Can your staff see our data, and is that access bounded?
Permafrost operators can view your data only through a time-limited, audited support session. Permafrost's internal audit log records the operator identity, the customer scope, the stated reason and the timestamp for each start and end. Your audit log shows that a support session started and ended, and when. Operators have no write capability against your tenant under any circumstance, and your dashboard shows a banner whenever a support session is active. There is no hidden mode that conceals this.
How is our data isolated from other customers?
Every dataset is partitioned by customer, and every query is scoped to a single customer's connected clouds. The isolation is structural and enforced in code, not a policy promise, and it is guarded by tests that block a release if a query could read across that boundary. We do not aggregate, sample, or benchmark across customers.
Do you run penetration tests and security reviews?
Yes. Permafrost maintains an ongoing security-review and vulnerability-management practice, and we welcome good-faith reports through the vulnerability-disclosure page in this Trust Center. The cadence of formal third-party testing and the evidence available under NDA are part of the certification-status conversation your security team can open with us.
Can we get a security questionnaire completed or evidence under NDA?
Yes. The certification-status page states plainly what we hold, what is underway, and what is inherited from the infrastructure provider. For a completed questionnaire, the current control evidence, or a longer review, reach us through your account team or the contact form and we will route it to the security-review process.