Start free

How we protect the service.

The standards we follow, where your data lives and how we handle it.

Stored in the EU

Analytics data is stored and backed up in ISO 27001 certified data centers in Finland.

Encrypted in transit

Every connection to GrainQL uses modern TLS. Backups are encrypted too.

Workspaces kept apart

Each workspace's data is kept separate, and every request is checked against it.

Access you control

Sign-in runs through Auth0, and every teammate has their own role. We never store passwords.

Hardened infrastructure

Production systems are kept patched, monitored and open only to the people who run them.

Built for GDPR

A data processing agreement, EU Standard Contractual Clauses and a public list of every provider.

Running a security review?

We answer security questionnaires and share more detail with your team on request. GrainQL does not hold its own SOC 2 or ISO 27001 certificate yet.

Found a vulnerability?

Email security@grainql.com with what you found, how to reproduce it and the impact you expect. A proof of concept or screenshots help.

We confirm your reportWithin 48 hours
We assess itWithin 5 days
Critical fixWithin 7 days
High fixWithin 14 days
Medium fixWithin 30 days
Public disclosure, agreed with youUp to 90 days

In scope

  • grainql.com and the dashboard
  • api.grainql.com and queryapis.grainql.com
  • The GrainQL tag and tag.grainql.com
  • Sign-in, roles and workspace access
  • Any way to read another workspace's data

Out of scope

  • Social engineering and phishing
  • Physical attacks
  • Denial of service and load testing
  • Services we use, such as Auth0 or Stripe
  • Spam or content injection with no security impact

Safe harbor.

We will not take legal action against research that follows these rules.

  • Report in good faith, and as soon as you find the problem
  • Do not destroy data or disrupt the service
  • Read or change no more data than you need to show the problem
  • Keep the details private until we have fixed it

Thanks to.

With your permission, we credit you here and in the release notes for the fix.

No reports yet.

For how we handle personal data, read the privacy page and the privacy policy.