How Guidely keeps your data safe

Infrastructure

• Guidely runs on Amazon Web Services in us-east-1 (N. Virginia). Application containers run on AWS Fargate behind a load balancer.
• The PostgreSQL database sits in private subnets with no public address. Only the application can reach it, over TLS.
• Credentials and keys are kept in AWS Secrets Manager, never in code or container images.
• All infrastructure is defined in code and deployed from version control, so every change is reviewed and repeatable.

Encryption

• In transit: TLS 1.2 or higher for the dashboard, APIs, SDK and media. Plain HTTP redirects to HTTPS.
• At rest: the database and file storage are encrypted. Storage buckets block all public access and refuse connections without TLS.
• API keys and tokens you give us for connected services (Anthropic, Slack, Linear, Jira, Confluence, Intercom) are encrypted with AES-256-GCM and never shown back in full.
• Passwords are hashed with bcrypt. Session tokens are random 256-bit values stored only as hashes.

Access and sign-in

• Sign in with a password, GitHub or Google. Each workspace decides which methods its members may use.
• Two-step verification for password sign-in, with an authenticator app and one-time recovery codes. New workspaces require it, and admins of any workspace can turn the requirement on. GitHub and Google sign-ins use those providers' own two-step verification.
• You're emailed whenever two-step verification is turned on or off for your account, or new recovery codes are made, with the time, browser and IP address.
• Google Workspace domains and GitHub organizations can join a workspace automatically, controlled by your own identity provider.
• Four roles (Owner, Admin, Editor, Viewer) plus per-member permissions, and production publishing needs its own permission.
• Every request is checked against the workspace that owns what it touches. A non-member gets a 404.
• Publishing, permission changes, deletions and other significant actions are recorded in the workspace audit log.
• Sessions last 30 days, show their IP address and browser, and can be revoked from account settings.

Application security

• Guide and article HTML is sanitized on the server and again in the browser, so guide content can't run scripts.
• Uploaded files are checked by their contents and served from a separate domain that never receives dashboard cookies.
• Dashboard changes must come from the dashboard's own origin (CSRF protection).
• Logins, signups, the SDK API and Scout are rate limited on the server.
• The one feature that fetches a URL you type refuses private and internal addresses, and re-checks every redirect.

Your users' data

• The SDK only sends what your app passes it. 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. Form inputs are always masked before anything leaves the browser, and you can mask or block any element, or all text.
• Consent mode buffers analytics until the user agrees. Page URL collection can be switched off per project.
• You set retention per project: events 365 days and recordings 30 days by default. Expired data is deleted automatically.
• Delete an end user's profile, events, recordings and responses in one step from the dashboard or the API.

AI

• Scout writes replies with Anthropic's models, only when you turn Scout on.
• Anthropic receives the conversation, the help content Scout reads, and the person's first name and page path. Never their email, other traits or events.
• Anthropic's commercial terms don't let it train on this data, and Guidely doesn't train models on Customer Data either.
• Projects can use their own Anthropic API key instead.
• AI assistants you connect to Guidely (Claude, ChatGPT, Cursor and other MCP clients) act as you, with your permissions. They're read only unless you allow changes, only reach workspaces whose admins allow them, and can be disconnected at any time. What they read goes to the assistant's provider under your own terms with them.

Backups and availability

• The database is backed up automatically every day, with point-in-time restore, and backups are kept for 7 days.
• Application and database logs go to Amazon CloudWatch, and containers are monitored with CloudWatch Container Insights.
• Guides keep working when a metered product reaches its limit, because only that product pauses.

Subprocessors

The companies that process data for us. Under the DPA, workspace owners hear about a new one by email at least 30 days before it starts. Services you connect yourself, such as Slack or Jira, act on your instructions and aren't listed.

Compliance

• Our Data Processing Agreement covers the GDPR, UK GDPR and Swiss law, with the Standard Contractual Clauses built in. Email legal@guidelytech.com for a copy to sign.
• Guidely doesn't hold a SOC 2 report yet. Until it does, we'll answer your security questionnaire and walk your team through anything on this page.
• How we handle personal information is in the Privacy Policy, and the technical detail behind this page is in the security documentation.