TRUST · SECURITY · COMPLIANCE

Trust, plainly stated.

The controls that exist today, the standards we align to, and the ones we are still preparing for. No certification claim we do not hold.

HOW YOUR DATA IS PROTECTED

Tenant isolation by default.

Row-level security on every table. Cross-tenant reads go through security-definer functions, never loosened policies.

Model keys never leave the server.

AI provider keys live in a sealed table with no client policies. The client sees a label and last four characters, nothing else.

Encrypted in transit and at rest.

TLS for every request. Data at rest is encrypted by the managed backend.

What we learn stays de-identified.

Patterns detected inside your account never leave it. What can travel to the shared library is a de-identified abstraction: a role family, a task family and counts, released only when at least three people across at least three companies show the same shape, and only after a human review. No text, no names, no company, no numbers you did not log.

AI runs server-side. Bring your own.

Every AI call is server-side and logged. Organizations can plug their own providers, including on-prem or local endpoints.

STANDARDS · CONTROL AND INDEPENDENT VERIFICATION

READ THIS FIRST

Two statuses on every row, never one.

Two separate things sit on every row. CONTROL is what ARK built and runs today. INDEPENDENT VERIFICATION is whether anyone outside ARK has checked it, and it reads PENDING until an outside party grants it in writing.

The percentage on a standard counts controls ARK built. It says nothing about certification, and it never will. Today no outside party has certified or reviewed any row on this page, so every verification chip reads PENDING with the party it needs named beside it.

GDPR
CONTROLS IN PLACE
CONTROLS 100% · IMPLEMENTED 7 · PARTIAL 0 · PLANNED 0
European data protection law for personal data.
INDEPENDENT VERIFICATIONPENDINGNEEDS · An EU privacy counsel to review the documents against the schema. Brief written and ready to send.
  • IMPLEMENTED
    PENDING
    Privacy notice and lawful basis
    Privacy policy published at /legal/privacy.
    NEEDS · Privacy counsel redlines.
  • IMPLEMENTED
    PENDING
    Data Processing Agreement
    DPA available at /legal/dpa.
    NEEDS · Privacy counsel redlines.
  • IMPLEMENTED
    PENDING
    Subprocessors disclosed
    Subprocessors list at /legal/subprocessors, with purpose and region.
    NEEDS · Privacy counsel completeness check.
  • IMPLEMENTED
    PENDING
    Data subject export
    One-tap GDPR data export in the app, as JSON.
    NEEDS · Privacy counsel to confirm the export reaches every table.
  • IMPLEMENTED
    PENDING
    Right to erasure
    Account and data deletion supported, honoured within 30 days.
    NEEDS · Privacy counsel to confirm deletion reaches every table.
  • IMPLEMENTED
    PENDING
    Tenant isolation and data minimization
    Row-level security on every table, owner or team-member scope only. No special-category data is collected or inferred.
    NEEDS · An application-security tester to attempt cross-tenant reads. Brief written and ready to send.
  • IMPLEMENTED
    PENDING
    Documented breach response
    Written runbook with the 72-hour clock, severity path, the Latvian lead authority named, and notification templates.
    NEEDS · Privacy counsel to review the notification path.
    DOC · docs/trust/breach-response-runbook.md
EU AI Act
CONTROLS IN PLACE
CONTROLS 100% · IMPLEMENTED 6 · PARTIAL 0 · PLANNED 0
European regulation on AI systems.
INDEPENDENT VERIFICATIONPENDINGNEEDS · No conformity assessment applies to a limited-risk system, and none is claimed. A notified body is not part of this path.
  • IMPLEMENTED
    PENDING
    Risk classification
    Limited-risk system, argued line by line against Article 5 and Annex III in the technical file.
    NEEDS · Counsel to confirm the classification argument.
    DOC · docs/trust/ai-act-technical-file.md
  • IMPLEMENTED
    PENDING
    Article 4 AI literacy
    Literacy is the product. Measures for learners, for organisational deployers and for the operator are documented with where each one's evidence sits.
    NEEDS · No outside party has checked this. ARK's own testing only.
    DOC · docs/trust/ai-act-article-4-evidence.md
  • IMPLEMENTED
    PENDING
    Transparency, Articles 13 and 50
    ARK System Generated content is labeled, projected figures read MODELLED NOT MEASURED, and every model call is logged in the MODELS USED report.
    NEEDS · No outside party has checked this. ARK's own testing only.
  • IMPLEMENTED
    PENDING
    Human oversight
    Guest-first, a person keeps or discards every output, no autonomous action on user systems.
    NEEDS · No outside party has checked this. ARK's own testing only.
  • IMPLEMENTED
    PENDING
    No prohibited practices
    No manipulation, no scoring of persons, no biometric use. Per-person use of a modelled read is a contract breach.
    NEEDS · Counsel to confirm.
    DOC · docs/trust/ai-act-technical-file.md
  • IMPLEMENTED
    PENDING
    Technical documentation
    Technical file covering purpose, classification, transparency, data governance, accuracy, logging and post-market monitoring.
    NEEDS · Counsel to review the file.
    DOC · docs/trust/ai-act-technical-file.md
SOC 2
CONTROLS PARTLY IN PLACE
CONTROLS 88% · IMPLEMENTED 7 · PARTIAL 0 · PLANNED 1
Trust Services Criteria for service organizations.
INDEPENDENT VERIFICATIONPENDINGNEEDS · A licensed CPA firm to run a Type I, then a Type II observation window. No examination has been performed, so no report exists.
  • IMPLEMENTED
    PENDING
    Access control and least privilege · CC6
    Row-level security plus managed auth. Cross-tenant reads go through security-definer functions. Provider keys sealed server-side with no client policy.
    NEEDS · CPA firm testing.
    DOC · docs/trust/soc2-information-security-policy.md
  • IMPLEMENTED
    PENDING
    Encryption in transit and at rest
    TLS in transit, encrypted at rest via the managed backend.
    NEEDS · CPA firm testing.
  • IMPLEMENTED
    PENDING
    Audit logging · CC7.1
    ai_call_log holds every model call, alert_events holds every alert firing, interaction_events holds product interactions as ids and enums.
    NEEDS · CPA firm sampling over an observation window.
    DOC · docs/trust/evidence-index.md
  • IMPLEMENTED
    PENDING
    Change management · CC8.1
    Every schema change is an ordered migration, tested against a clean environment. The deterministic eval suite gates every change. Full commit history retained.
    NEEDS · CPA firm to sample changes.
    DOC · docs/trust/soc2-information-security-policy.md
  • IMPLEMENTED
    PENDING
    Vendor management · CC9.2
    One provider registry for every AI vendor, bring-your-own keys including local endpoints, and a public subprocessor list kept current.
    NEEDS · CPA firm review.
  • IMPLEMENTED
    PENDING
    Monitoring and incident response · CC7.2 to CC7.4
    Alerting layer with six watches, dedupe and cooldown, mail at high severity. Nightly backups with a manifest and a tested restore. Written incident-response policy with a severity table.
    NEEDS · CPA firm to observe the response path over a window.
    DOC · docs/trust/soc2-incident-response-policy.md
  • IMPLEMENTED
    PENDING
    Security policies
    Information-security policy and incident-response policy written, scoped and versioned, with a risk register and an exception rule.
    NEEDS · CPA firm review.
    DOC · docs/trust/soc2-information-security-policy.md
  • PLANNED
    PENDING
    Independent penetration test
    Not run. The scope brief is written, naming tenant isolation and key containment as the first two questions.
    NEEDS · An application-security firm with multi-tenant Postgres experience.
    DOC · docs/trust/reviews/security-review-brief.md
ISO 42001
CONTROLS PARTLY IN PLACE
CONTROLS 100% · IMPLEMENTED 8 · PARTIAL 0 · PLANNED 0
AI management system standard.
INDEPENDENT VERIFICATIONPENDINGNEEDS · An accredited certification body to audit the management system in two stages. Nothing has been assessed, so nothing is certified.
  • IMPLEMENTED
    PENDING
    AI management system policy
    AIMS policy written against the clause structure: objectives with a measure each, the accountable person, operational controls and the improvement rule.
    NEEDS · Certification body, stage one.
    DOC · docs/trust/iso42001-aims-policy.md
  • IMPLEMENTED
    PENDING
    AI system inventory and risk classification
    Fourteen systems listed by capability, each with its input, its output, its human oversight and its deterministic fallback.
    NEEDS · Certification body, stage two.
    DOC · docs/trust/iso42001-ai-system-inventory.md
  • IMPLEMENTED
    PENDING
    Data governance for AI
    A table of what reaches a model and what never does, the identity strip, the private-lane exclusion, retention, residency and the ingestion rule.
    NEEDS · Certification body, stage two.
    DOC · docs/trust/iso42001-data-governance.md
  • IMPLEMENTED
    PENDING
    Model and provider governance
    Capability-based gateway, per-org provider chains, one file allowed to name a model, daily caps, BYO keys including local endpoints, full call log.
    NEEDS · Certification body, stage two.
  • IMPLEMENTED
    PENDING
    Transparency to users
    ARK System Generated content labeled, modelled figures marked, and this page splits what ARK built from what an outside party has checked.
    NEEDS · No outside party has checked this. ARK's own testing only.
  • IMPLEMENTED
    PENDING
    Human oversight
    A person keeps or discards every output, and that decision is the product's primary quality signal.
    NEEDS · No outside party has checked this. ARK's own testing only.
  • IMPLEMENTED
    PENDING
    AI impact assessment
    Seven assessed impacts across learners, teams, modelled occupations and named third parties, each with controls, residual risk and a verdict.
    NEEDS · Certification body to review the assessment.
    DOC · docs/trust/iso42001-ai-impact-assessment.md
  • IMPLEMENTED
    PENDING
    Continuous evaluation
    Three legs, all deterministic: the eval suite on every change, the calibration ledger for projections that were later checked, and the fairness invariance checks.
    NEEDS · An algorithmic-fairness practice for the bias leg. Brief written and ready to send.
    DOC · docs/trust/iso42001-aims-policy.md
FORESIGHT
CONTROLS PARTLY IN PLACE
CONTROLS 75% · IMPLEMENTED 3 · PARTIAL 0 · PLANNED 1
ARK's own standard for modelled workforce scenarios.
INDEPENDENT VERIFICATIONPENDINGNEEDS · An algorithmic-fairness practice for bias, and a measurement scientist for the level engine. Both briefs are written.
  • IMPLEMENTED
    PENDING
    Aggregate-only reads with a three-person floor
    Definer reads return roles at levels. There is no per-person projection to retrieve.
    NEEDS · Security tester to attempt a walk-around of the floor.
  • IMPLEMENTED
    PENDING
    Prohibited use clause in client contracts
    Versioned clause, published at /trust/prohibition, forbidding use against a named person.
    NEEDS · Counsel to review enforceability.
  • IMPLEMENTED
    PENDING
    Fairness method note
    Published on this page: the invariance check, its axes, its tolerances and its limits, with the internal-check label kept on it.
    NEEDS · An algorithmic-fairness practice. Brief written and ready to send.
    DOC · src/lib/fairness/method.ts
  • PLANNED
    PENDING
    Validation note, back-test accuracy
    Not written. It arrives with the validation pack, once the closed back-test count the selling gate asks for is reached.
    NEEDS · A measurement scientist, after the back-tests close.
PILOT-READINESS KIT · SECURITY, DPA, ORDER FORM ↓

THE DOCUMENT SET

Every policy behind those rows, written down.

These are ARK's own documents, versioned in the repository beside the code they describe. Buyers, auditors and counsel can ask for any of them, and the auditor index says where each control's evidence sits.

BREACH RESPONSE RUNBOOKGDPR

What happens in the first 72 hours: who declares it, how it gets contained, how the risk is judged, who gets told and when. The Latvian lead authority is named and both notification letters are already written.

docs/trust/breach-response-runbook.md
AI ACT TECHNICAL FILEEU-AI-ACT

The provider's own technical documentation. What ARK is, why it lands as limited-risk against Article 5 and Annex III, how transparency and human oversight work, and how the system is watched after release.

docs/trust/ai-act-technical-file.md
ARTICLE 4 LITERACY EVIDENCEEU-AI-ACT

AI literacy is the product, so the evidence is the product. Every measure is listed with the table or file it can be read from, for learners, for organisations deploying ARK, and for the operator.

docs/trust/ai-act-article-4-evidence.md
INFORMATION SECURITY POLICYSOC2

Scope, roles, access control, change management, logging, backup, vendors and the risk register, written against the Trust Services Criteria and mapped to the controls that already run.

docs/trust/soc2-information-security-policy.md
INCIDENT RESPONSE POLICYSOC2

Three severities with acknowledge and contain times, the seven-step response, the post-incident rule that every failure has to produce a migration, an eval or an alert, and the yearly test.

docs/trust/soc2-incident-response-policy.md
AIMS POLICYISO-42001

The AI management system policy: objectives with a measure each, the accountable person, the operational rules that constrain every model call, and how performance gets read quarterly.

docs/trust/iso42001-aims-policy.md
AI SYSTEM INVENTORYISO-42001

All fourteen AI systems ARK runs, described by the capability they ask for rather than a model name, each with its input, its output, who oversees it and its deterministic fallback.

docs/trust/iso42001-ai-system-inventory.md
DATA GOVERNANCE FOR AIISO-42001

A table of what reaches a model and what never does, the identity strip, the private lane, retention, where processing happens, and why ingested material is data and never instruction.

docs/trust/iso42001-data-governance.md
AI IMPACT ASSESSMENTISO-42001

Seven ways this could hurt somebody, from a level read wrongly to an aggregate used against a named person, each with its controls, the risk that stays, and a verdict with conditions attached.

docs/trust/iso42001-ai-impact-assessment.md
AUDITOR EVIDENCE INDEXAUDITOR

Where every SOC 2 and ISO 42001 control's evidence lives, criterion by criterion, so a CPA firm or a certification body can scope without a discovery call. It also lists plainly what is not there.

docs/trust/evidence-index.md

For a security questionnaire, write to hello@shift.studio and name the document.

INDEPENDENT REVIEWS · SCOPED, NOT YET COMMISSIONED

Four reviews ARK has written the brief for.

None of these has been commissioned, so none of them appears as a verification anywhere on this page. Each brief states the one question the reviewer answers, what ARK hands over, and which artifacts to open first. When a review lands, the reviewer's name, date and scope go up here, favourable or not.

PSYCHOMETRIC REVIEWNOT COMMISSIONED
Does an ARK level mean what ARK says it means, and does it mean the same for two people who did equivalent work?

The level engine and its thresholds, the evidence model, the fairness checks, the verified workflow proofs as an outside criterion, the calibration ledger, and de-identified level distributions with counts.

NEEDS · A measurement scientist with workplace-assessment practice.
docs/trust/reviews/psychometric-review-brief.md
SECURITY REVIEWNOT COMMISSIONED
Can anyone read or write a row they have no right to, and can any secret leave the server?

Full source and migration history, every policy and definer function with its grants, test accounts across two organisations plus a non-member, the public endpoint list, and a contact answering within a business day.

NEEDS · An application-security firm with multi-tenant Postgres practice.
docs/trust/reviews/security-review-brief.md
PRIVACY REVIEWNOT COMMISSIONED
Do ARK's documents match ARK's database, and is the processor position defensible?

The schema with retention per table, the migration history, the published notice, DPA and subprocessor list, the telemetry rule, the private-lane exclusion, and a live walkthrough of an export and a deletion.

NEEDS · An EU privacy counsel who reads schemas, not only policies.
docs/trust/reviews/privacy-review-brief.md
BIAS REVIEWNOT COMMISSIONED
Does ARK treat equal evidence equally, and are ARK's own fairness checks good enough to be believed?

Every fairness check with its axes and tolerances, the rigged-subject tests that prove it catches injected bias, the identity strip, the run register, outcome distributions with a minimum cell size, and new evidence sets built to the reviewer's design.

NEEDS · An algorithmic-fairness researcher or audit practice.
docs/trust/reviews/bias-review-brief.md

FORESIGHT · THE METHOD AND ITS LIMITS

What a FORESIGHT scenario is, and what it may never be used for.

FORESIGHT is organizational planning analytics on modelled scenarios. It is never to be used for decisions about an individual employee or candidate, and no individual-level output exists.

Roles at levels, never people.

A FORESIGHT run reads an occupation, a level band and a headcount. It never reads a person, a record, a capture or anything anybody wrote. The ability to look at one employee is absent from the path rather than switched off in a setting.

Aggregates only, with a floor of 3.

Any cell holding fewer than 3 people is withheld from every read, and the report prints how many cells were withheld. Small cells are dropped rather than blurred, because a blurred cell is still a cell about people.

MODELLED, NOT MEASURED.

Every figure is a projection over published occupational task data plus a headcount, moved by an epoch offset and by assumptions that are printed beside the number. Measured results live on the proof surfaces and carry the opposite label. The two never share a page.

Advisory, not evidence.

A scenario is planning input. It supports a decision about a program, a sequence or a budget. It does not support a finding about a person, and it is not offered as one.

The individual-use prohibition.

FORESIGHT is organizational planning analytics on modelled scenarios. It is never to be used for decisions about an individual employee or candidate, and no individual-level output exists.

The selling gate.

FORESIGHT scenarios are shown as a labelled preview; sold results are gated on at least 5 closed calibration back-tests. Until that ledger fills, what you see is labelled as a preview wherever it appears.

THE SELLING GATE

FORESIGHT scenarios are shown as a labelled preview; sold results are gated on at least 5 closed calibration back-tests.

VALIDATION NOTEIN PREPARATION

The back-test protocol, the closed calibration record, and the accuracy the ledger reports. Published alongside the 5 closed back-tests the selling gate asks for.

FAIRNESS METHOD NOTE

How we test FORESIGHT and the level engine for fairness.

INTERNAL CHECK · NOT AN INDEPENDENT AUDIT

We hold capability constant, change only the surface of the writing, and check that the outcome stays put. This is a modelled internal test on invented evidence, not a certified audit of ARK.

Same work, different wording, same answer.

We write evidence sets by hand, then render each one several ways: formal and casual phrasing, and the same content in English, Latvian and German. The level engine, the AI-exposure read and the voice gate run over every version. If a placement moves because somebody writes casually or writes in Latvian, that is a bug and the run fails on it. The tolerance is stated: a rung may not move at all, a share may wobble by one point.

Equal evidence buys an equal rung.

Across the set we report outcomes by occupation group, level band and locale, and check that identical evidence lands on the identical rung whichever occupation group it sits in. AI-exposure shares do differ between occupations, because the published task data differs. That is data, not bias, so only the rung is held to equality.

No sensitive attribute is collected, and none is guessed.

ARK holds no data on race, gender, age, health or belief, and the fairness harness does not infer any of it. The groups it reports on are occupation group, level band and language. Nothing in the harness touches a member's rows: every piece of evidence in it is invented for the test.

The name check is a check, not an assumption.

One variant plants name-shaped tokens into the evidence on purpose, so the run can prove the identity strip removed them before any engine read the text. A single surviving token fails the run.

What this is not.

It is a synthetic internal check that we run and read ourselves. It is not a bias audit, it is not certified, and no outside party has signed it. The independent review stays owner-side and we will publish it here when it exists, with whoever ran it named. Until then, treat this note as our own testing, openly described.

THE TRUST PACK

HAND IT TO YOUR IT TEAM

OBJECTION AND COMPLIANCE PACK

ADOPT A POLICY FOR THE PILOT

PILOT AI-USE POLICY

YOUR DATA RIGHTS

EXPORT

One-tap export of every record tied to your account, as JSON, from the app settings panel.

DELETION

Delete your account and its data at any time. Deletion is honoured within 30 days.

Report a vulnerability: security@shift.studio. Response within 48 hours.