Skip to content

Security, privacy and compliance

The questions procurement and legal teams ask before hiring a studio, answered plainly. Where we don't hold a certification, we say so, and explain what we do instead.

A straight answer first: Augere Labs does not hold SOC 2, ISO 27001, HIPAA or PCI certifications. We build products with the controls these frameworks expect, and we can support your own audit with documentation of how the system was built.

How we handle your data

Simple defaults that apply to every project, whatever its size.

  • Least-privilege access

    Each person gets access only to the systems their part of the work needs, and only for as long as they need it.

  • Access removed at handover

    When a project ends, we remove our accounts and rotate any shared credentials, unless you ask us to stay on for support.

  • No training on your data

    Client data, code and documents are never used to train AI models, ours or anyone else's.

  • Secrets stay out of code

    API keys and credentials live in a secrets manager or environment configuration, never committed to a repository.

  • Production data stays in production

    By default we work with seeded or anonymised data. Production data isn't copied to laptops unless you agree to it for a specific reason.

Ownership and confidentiality

Code, designs and accounts
Yours from day one. Repositories, cloud projects and services are created in your name or transferred to you.
Intellectual property
The contract assigns the IP in the work we produce to you.
Confidentiality
We'll sign your NDA on request, before you share anything sensitive.
Portfolio use
We only mention your product publicly with your permission.

Youownthecode.

Repositories, accounts and designs are yours from the start, not handed over at the end.

Building for regulated products

Compliance belongs to your organisation, not to a codebase. Our part is to make the software easy to defend: the right patterns, the right vendors and a clear record of how it works.

GDPR

GDPR-aware patterns

  • Collect only the data the product needs
  • Clear consent capture for analytics and marketing
  • User data export and account deletion built in
  • EU data hosting where your vendors support it

HIPAA

HIPAA-aware architecture for health data

  • Vendors that will sign a Business Associate Agreement
  • Encryption in transit and at rest
  • Audit logs for access to protected data
  • Health data kept out of analytics and AI prompts unless covered

PCI DSS

Card data handled by the payment provider

  • Hosted checkout or payment fields from the provider
  • Card numbers never stored by us or on your servers
  • Webhooks verified before orders are fulfilled

SOC 2

SOC 2-readiness practices

  • Audit logs for sensitive actions
  • Role-based access control in the product
  • Every change reviewed before it ships
  • Separate environments and documented deploys

AI-specific safeguards

AI features raise their own questions about where data goes and what a model is allowed to decide. These are applied per feature, based on the risk involved.

  1. 01

    Personal data redacted before prompts

    Where a feature doesn't need names, emails or identifiers, we strip them before anything is sent to a model.

  2. 02

    Provider retention settings

    We use API terms that exclude your data from training and set retention to the shortest option the feature allows.

  3. 03

    Evals and guardrails

    Test sets that check outputs against expected answers, plus guardrails on what a model can see, say and do.

  4. 04

    Human review for high-stakes outputs

    Anything with legal, medical, financial or customer-facing consequences gets a person in the loop before it takes effect.

  5. 05

    Cost and latency monitoring

    Every model call is tracked, so spend and response times are visible from the first day.

Third-party services

Services we commonly use, chosen per project. You can swap any of them for a vendor your security team has already approved.

Commonly used third-party services and what they are typically used for
ServiceTypically used for
VercelHosting and deploys for web apps
CloudflareDNS, CDN, bot protection and edge functions
SupabasePostgres database, auth and file storage
AWSInfrastructure, storage and BAA-eligible services
StripePayments and subscriptions; holds all card data
OpenAILanguage models via API
AnthropicLanguage models via API
PostHogProduct analytics and feature flags
Google AnalyticsMarketing site analytics
Cal.comBooking and scheduling
GitHubSource code, code review and CI

Security practices in delivery

  • Code review

    Every change is reviewed by another engineer before it merges.

  • Dependency updates

    Automated alerts for vulnerable packages, patched as part of normal delivery.

  • Environment separation

    Development, staging and production are separate, with separate credentials.

  • Backups

    Automated database backups with point-in-time recovery where the provider supports it.

  • Incident response

    A named contact for each project, and hello@augerelabs.com for anything urgent. We tell you promptly if something goes wrong.

Requests

Email hello@augerelabs.com and we'll reply with what you need. For how this website handles data, see our privacy policy and terms.

Compliance questions

Short answers to what security and legal reviewers usually ask.

7 questions

No. Augere Labs does not hold SOC 2, ISO 27001 or any other security certification. What we do is build your product with the controls those frameworks expect, such as audit logs, role-based access and reviewed changes, so your own audit is easier. We're happy to explain exactly what we do in a security questionnaire.

We can design a HIPAA-aware architecture: vendors that will sign a Business Associate Agreement, encryption in transit and at rest, audit logs and tight access control. HIPAA compliance itself is your organisation's responsibility and depends on your policies and agreements as well as the software, so we work alongside your compliance lead rather than certifying anything ourselves.

No. Card details are collected and stored by the payment provider, usually Stripe, using their hosted fields or checkout. Card numbers never touch our servers or yours, which keeps your PCI scope as small as possible.

No. We never use client data to train models. Where a product calls an AI provider, we use API settings and plans that exclude your data from training, configure data retention to the shortest option that fits the product, and redact personal data before it reaches a prompt where needed.

You do, from day one. Repositories, cloud accounts, domains and third-party services are set up in your name or transferred to you, and the contract includes an assignment of intellectual property for the work we produce.

Yes. We can sign your NDA before a first detailed conversation, and a Data Processing Agreement where we will process personal data on your behalf. Email us and we'll turn it around quickly.

Yes. Send it to hello@augerelabs.com and we'll complete it honestly, including the areas where a small studio does things differently from a large vendor.

Muhammad Qitmeer, founder of Augere Labs

Still have a question?

Ask Muhammad directly

A 30-minute call with the founder, no slides. We reply to email within one working day.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.