Trust

How we handle your code, your data and our access to them

Everything on this page is either something we do on every project or a term we put in the contract. Where we don’t have something yet, SOC 2 for example, the page says so.

Status

Where we stand today

  • SOC 2 Type IPlannedNot yet. We’ll start it when clients ask for it, with 2027 as the target.
  • SOC 2 Type IIPlannedAfter Type I.
  • HIPAANot offeredNot yet, so we don’t take on projects that require it.
  • Security questionnairesIn placeAnswered in full, on request.
  • ContractsIn placeMSA, SOW and DPA on every project.

Ownership and IP

The contracts are the standard set: a master agreement, a statement of work per project, and a data processing agreement.

  1. 1.1

    MSA, SOW and DPA

    The master services agreement sets the terms once. Each project gets a statement of work with fixed scope, price and stages. The data processing agreement covers how we handle your data.

  2. 1.2

    Full IP transfer on payment

    The code, designs and documentation we write for you become yours once paid for. Open-source components keep their own licenses, and we list them.

  3. 1.3

    Your accounts from day one

    Repositories, cloud, domains and third-party API keys are registered to your company. We work in them as invited users.

  4. 1.4

    Bug warranty

    30 to 90 days of fixes after launch, set in the statement of work according to the size of the project.

  5. 1.5

    Source escrow

    If your policy requires it, we deposit the source with an escrow agent on request.

Data and access

  1. 2.1

    Your cloud, in a US region

    Production data lives in your own cloud account, in a US region you choose.

  2. 2.2

    Minimal access, with MFA

    Each person gets only the access their task needs, for as long as the project lasts, and always behind multi-factor authentication.

  3. 2.3

    Access log

    Who accessed what, and when, is logged in your account, where you can see it.

  4. 2.4

    Revoked when the project ends

    On the last day we remove our accounts and keys. If you take a Care plan, the care team keeps only the access support requires.

  5. 2.5

    Encryption

    Data is encrypted in transit and at rest.

  6. 2.6

    Backups

    Automated backups, plus a restore test before launch so you know they work.

Engineering practice

  1. 3.1

    People review the AI-assisted code

    AI helps us write code faster. A person reads and approves each change before it’s merged.

  2. 3.2

    Automated scanning

    Semgrep or CodeQL for the code, Dependabot for dependencies and gitleaks for secrets, on every repository.

  3. 3.3

    OWASP ASVS level 2

    We check web applications against level 2 of the OWASP Application Security Verification Standard, the level meant for apps that handle sensitive data.

  4. 3.4

    A pentest before launch

    When the system handles personal data, it gets a light penetration test before it goes live.

  5. 3.5

    Least privilege

    Services and integrations get only the permissions they need, and credentials never live in the code.

AI and your data

  1. 4.1

    Providers that don’t train on your data

    We use the Anthropic and OpenAI APIs, whose terms exclude training on customer data.

  2. 4.2

    Built to NIST AI RMF

    AI features in your software follow the NIST AI Risk Management Framework: a stated purpose, known limits, testing on your own cases, and a person in the loop where mistakes are costly.

  3. 4.3

    Texas TRAIGA

    The Texas Responsible Artificial Intelligence Governance Act has been in force since January 1, 2026. It treats following NIST AI RMF as a safe harbor.

  4. 4.4

    Personal data under TDPSA

    The DPA and the system design take the Texas Data Privacy and Security Act into account.

Team and location

  1. 5.1

    Headquartered in Israel

    We’re an international team headquartered in Israel. Each project is staffed by a named group of people.

  2. 5.2

    Who has access, and from where

    Before work starts you get the list of people who will have access to your systems and the countries they work from.

  3. 5.3

    Questionnaires answered truthfully

    We fill in your security questionnaire in full, including the questions where the answer is “not yet”.

Found a vulnerability?

How to report
Through the contact form, with a message that starts with “security”
What to include
What you found and how to reproduce it
While testing
Please don’t access other people’s data or disrupt live systems
Our reply
Within one business day, and we keep you posted until it’s fixed
Security address
None yet. When there is one, it will be listed here

Questions

Yes. We work in your cloud and your repositories, so your policies, single sign-on and logging apply to us as to any contractor. If a policy asks for something we don’t do yet, we tell you before signing.