Security you can check.

How AuditGlass protects your organisation’s data, what is in place today and what is still in progress. Every line on this page maps to a control in our register.

Sub-processors

01Compliance status

Where we stand.

Stated plainly. We do not hold a certification today, and we will not say we do.

Preparing

SOC 2 Type I

Audit planned for Q2 2027. Our 65 controls are mapped to the Trust Services Criteria: security, availability, confidentiality, processing integrity and privacy. We will share the report here, under NDA, once it is issued.

55 controls are built into the platform. 10 depend on people and paperwork and are in progress.

In place

GDPR

  • Data Protection Officer: Kathy Horgan, privacy@auditglass.ie. DPC registration being filed. PRV-10
  • Data Processing Agreement available on request (solicitor review pending). PRV-07
  • Hosted in the EU. Transfers covered by the EU-US Data Privacy Framework or Standard Contractual Clauses. PRV-08
  • Records of processing, retention schedule and one queue for privacy requests with a one-month clock. PRV-04
Providers

Our providers’ reports

Our hosting, email, payments and AI providers hold their own SOC 2 Type II and ISO 27001 reports. We review them before onboarding and every year. These are their certifications, not ours.

See all 10 sub-processors

02Security overview

What is implemented.

Seven areas, each with the controls behind it. Items marked “In progress” depend on people or paperwork and are not finished yet.

Accounts and sign-in

  • Passwords of at least 12 characters, checked against known breached passwords.

    IAM-01

  • Two-step sign-in with an authenticator app and 10 one-time recovery codes. Required for AuditGlass staff, panel experts and console users; organisations can require it for their team.

    IAM-02

  • Five failed sign-ins in 15 minutes locks the account for 15 minutes and emails the account owner.

    IAM-03

  • Role-based access with least privilege. Every client record is scoped to its own organisation, and cross-organisation reads are blocked and logged.

    IAM-04 · IAM-05

  • Encrypted sessions with an idle time-out, and “sign out everywhere else” in Settings.

    IAM-08

  • Every staff, expert and console account is reviewed each quarter; leavers lose access within 24 hours.

    IAM-06 · IAM-07

Encryption

  • TLS 1.2 or higher on every connection, with HSTS.

    ENC-01

  • AES-256 encryption at rest, plus application-level encryption for answers, evidence and registers.

    ENC-02

  • Storage keys held in a key management service; the application key is rotated yearly.

    ENC-03

  • Integration secrets are stored encrypted and only ever shown as their last four characters.

    ENC-04

Hosting and backups

  • Hosted in the EU. Files are encrypted before they’re stored.

    PRV-08

  • Encrypted daily database backups, kept for 35 days in a second EU region (Frankfurt).

    AVL-01

  • A backup is restored to staging every quarter and timed against a 4-hour recovery target. In progress

    AVL-02

  • Uptime is checked every minute, with alerts on errors, queues and disk space, and a public status page.

    AVL-03

  • Security headers on every response, rate limits on sign-in and exports, and uploads scanned before anyone can open them.

    APP-01 · APP-03 · APP-04

  • Code changes go through reviewed pull requests; production is deployed only from tagged releases. In progress

    CHG-01 · CHG-03

  • Dependency checks on every build, monthly patching and a yearly external penetration test. In progress

    APP-05

Logging and monitoring

  • An audit log of who did what, when and from where. Each entry is chained to the one before, so a missing or altered entry shows up when the chain is checked.

    LOG-01

  • The audit log is kept online for 13 months, then archived for 6 years. Application logs are kept for 30 days.

    LOG-02

  • Alerts for impossible travel, bulk exports, repeated lockouts and privilege changes.

    LOG-03

  • Every view, download and share of evidence or vault documents is logged, and your organisation can see that log.

    LOG-04

People and policies

  • Eleven written policies covering security, access, encryption, logging, change, vendors, incidents, continuity, data protection and retention, reviewed every year. In progress

    POL-01

  • Staff, admins and panel experts accept the policies on their first sign-in and every year after.

    POL-02

  • Confidentiality terms are signed before access. Panel experts are vetted for qualifications, insurance and references.

    POL-03 · POL-05

  • Yearly security and privacy training for staff and experts.

    POL-04

  • Named owners: Rohab Brar for security and Kathy Horgan, our Data Protection Officer, for privacy. They review controls, risks and incidents every quarter.

    GOV-01 · GOV-02

AI and your data

  • Names, emails, phone numbers, PPSN and NI numbers, addresses and IBANs are replaced before any text is sent to the AI provider.

    AIX-01

  • Prompt logs are off by default. If switched on, they are deleted after 30 days.

    AIX-01

  • AI drafts are labelled, and a person has to accept them before they reach you.

    AIX-02

  • The AI provider (Anthropic) works under a data processing agreement with Standard Contractual Clauses. A DPIA covers AI drafting.

    RSK-03 · PRV-08

Incident response

  • A written incident plan with severity levels and named roles.

    INC-01

  • Personal data breaches are assessed against the 72-hour deadline for telling the DPC, and affected customers are told without undue delay.

    INC-01 · INC-02

  • Every security event is recorded and closed with lessons learned, whether or not it is reported.

    INC-02

  • A yearly breach exercise with the whole team. In progress

    INC-03

03Data and region

Your data stays in the EU.

The app and database run in Dublin. Encrypted backups are kept in Frankfurt. Providers outside the EU only receive what they need, under the EU-US Data Privacy Framework or Standard Contractual Clauses.

Primary region
European Union

Dublin

Backups
35 days

Encrypted, Frankfurt

Audit log online
13 months

Then archived 6 years

After you close
30 days

Then pseudonymised

04Documents

For your procurement team.

Ask for any document and we email it to you, usually within two working days.

Data Processing Agreement

Article 28 terms, Standard Contractual Clauses annex, security annex and the sub-processor list. You accept it when you create an organisation.

Version 1.0 · solicitor review pending · PRV-07

Security overview (PDF)

This page as a short PDF for your procurement or IT team, with the control IDs.

Updated 12 Oct 2026 · GOV-04

Policies summary

One page on each of our eleven policies: what it covers, who owns it, when it is reviewed.

Drafts awaiting sign-off · POL-01

Sub-processor list

Every provider that handles personal data for us: purpose, data, location and transfer safeguard.

10 active · VEN-01

Open

Privacy notice

What we collect, why, how long we keep it and your rights.

Solicitor review pending · PRV-01

Open

05Sub-processors

Who helps us run it.

We tell customers at least 30 days before a new sub-processor starts handling personal data. You can object in that time, and if we can’t resolve it you can end the contract without penalty.

  • ActiveCampaign LLC (Postmark)
  • Amazon Web Services EMEA SARL
  • Amazon Web Services EMEA SARL (SES)
  • Anthropic, PBC
  • Cloudflare, Inc.
  • Google Ireland Ltd
  • Microsoft Ireland Operations Ltd
  • Stripe Payments Europe Ltd
  • Twilio Ireland Ltd
  • Xero (UK) Ltd
Full list with locations and safeguards

Get sub-processor change emails

One email per change, sent at least 30 days ahead. Nothing else.

Unsubscribe from any email in one click. VEN-03

06Responsible disclosure

Found a weakness?

Tell us first. Email security@auditglass.ie with the steps to reproduce it. We confirm receipt and triage every report within 3 working days, and keep you updated until it is fixed.

We don’t run a paid bug bounty yet. APP-06

Please

  • Use your own test account and organisation.
  • Give us reasonable time to fix the issue before telling anyone else.
  • Stop and tell us straight away if you reach someone else’s data.

Please don’t

  • Access, change or keep other people’s data.
  • Run denial-of-service, spam or social engineering tests.
  • Test against customers, staff or our providers.

We won’t take legal action against good-faith research that follows these rules.

Questions about your data?

Our Data Protection Officer is Kathy Horgan: privacy@auditglass.ie. You can also complain to the Data Protection Commission (Ireland) or, in the UK, the ICO.