Blog

How we keep your users’ data safe, and our road to SOC 2 Type II

Guidely runs inside your product, so it sees how your users use it. Here’s how we protect that data today, and where we are on the way to a SOC 2 Type II report.

Gurp Parmar4 min read

Guidely runs inside your product. It sees which pages people open, what they click and, if you turn on session replay, a masked recording of their screen. That's a lot of trust to ask for, so we want to be specific about how we protect it, and honest about what's still ahead.

The short version

  • Your data is encrypted in transit and at rest, in AWS, with the database in private subnets.
  • You decide what's collected. Replay masks what people type before anything leaves the browser, sensitive-looking properties are dropped, and you set retention per project.
  • Every AWS API call is recorded in a tamper-evident trail, and GuardDuty watches for threats around the clock.
  • We don't have a SOC 2 report yet. We're working towards SOC 2 Type II, and this post explains where we are.

Only the data you choose

The safest data is data we never collect. The SDK only sends what your app passes it, and properties that look like passwords, tokens or card numbers are dropped in the browser and again on the server. Session replay is off until you turn it on, and form inputs are always masked before they leave the page. You can mask or block any element, or all text.

You also decide how long we keep things: events for 365 days and recordings for 30 by default, deleted automatically after that. When one of your users asks to see or delete their data, you can export or erase everything about them in one step.

Encrypted and locked down

Everything travels over TLS 1.2 or higher. The database, recordings and backups are encrypted at rest, and storage buckets block public access and refuse connections without TLS. API keys you give us for connected tools are encrypted with AES-256-GCM and never shown back in full. Passwords are hashed with bcrypt, and session tokens are stored only as hashes.

Access you control

Your team signs in with a password plus two-step verification, GitHub, Google, or your own identity provider over SAML, with SCIM to add and remove people. Four roles and per-member permissions decide who can do what, publishing to production is a permission of its own, and significant changes land in your workspace's audit log.

We hold ourselves to the same standard. Every action a Guidely admin takes, such as granting admin access, changing a workspace or turning HIPAA mode off, is written to a platform audit log that nothing in the app can edit or delete. The admin console needs a second factor, and who has admin access is reviewed every quarter as part of our SOC 2 program.

Watched around the clock

One CloudTrail trail records every AWS API call in every region, with log file validation, so any change to or deletion of a log file shows. Amazon GuardDuty looks for threats in that trail, in network flow and DNS activity, in access to recordings and in database sign-ins. Network flow logs are kept for a year.

Built to stay up

The database has a standby in a second availability zone with automatic failover, point-in-time restore for 35 days and monthly backups kept for a year. Our SDKs are designed so your app keeps working if Guidely doesn't: they cache configuration, queue events and back off when we're unreachable.

Where we are on SOC 2 Type II

A SOC 2 Type II report is an independent auditor's opinion on whether a company's security controls worked over a period of months. It isn't a certificate, and it can't be bought. You have to run the controls and keep the evidence. Here's our progress:

  1. Controls mapped to the Trust Services Criteria (done). Every Security, Availability and Confidentiality criterion is mapped to a Guidely control, with an owner, a frequency and the evidence it produces.
  2. Written policies (in progress). Information security, access control, change management, incident response, business continuity, vendor management, risk assessment and more: written, kept in version control, and now being approved.
  3. Recurring controls recorded as they run (in progress). Access reviews, log reviews, vulnerability reviews and restore tests are recorded in Guidely's admin console with who did them, when and a link to the evidence, and we get a reminder when one is due.
  4. Continuous monitoring (in progress). Automated alerts for suspicious account activity and outages, configuration checks against AWS security best practices, and a web application firewall.
  5. Independent penetration test (next).
  6. The SOC 2 Type II audit itself (next). An auditor examines our controls over an observation period and issues the report.

We'll post here when each step is done.

Ask us anything

If you're evaluating Guidely, email security@guidelytech.com. We'll share our policies, the control matrix and readiness assessment, our system description and subprocessor list, and fill in your security questionnaire. We also sign a DPA with the Standard Contractual Clauses, and a Business Associate Agreement for teams that handle health data.

If you find a vulnerability, please tell us at the same address. We reply within two business days.

Read the details on our security page.