Security

Current controls, stated with limits.

How Bolb handles and protects data.

This page describes the product controls and service providers currently used for customer feedback. It distinguishes implemented controls from contractual and operational work that is still being completed.

Last updated: September 2026

Built for trust

Privacy and security are part of the product — not an afterthought.

Data protection approach

Bolb is documenting its processing, contracts, and operational controls against GDPR requirements. This page describes current product controls; it is not a compliance certification.

Infrastructure locations

Primary database and file storage are configured in Supabase's eu-west-1 region. Bolb also uses Cloudflare, OpenAI, Resend, and enabled integration providers, so the service is not represented as EU-only.

AI processing

Bolb uses OpenAI APIs for transcription and analysis. Bolb does not train its own AI models on customer feedback.

Access boundaries

Authenticated application and database controls are designed to limit data by store, role, and department. These controls are tested locally and require deployment verification for each release.

Data handling

Sensitive feedback requires layered protection.

Customer voices can contain personal details. New recording processing omits text-bearing segments, and public feedback is redacted before downstream follow-up generation. Older recordings may still contain plaintext segments, and redaction does not guarantee anonymisation.

Encrypted sensitive fields

Full transcript text and supported integration tokens are encrypted by the application before database storage using AES-256-GCM and dedicated secrets.

Restricted recording access

Recording access requires an authenticated, authorised request. Playback uses a short-lived signed URL after server-side checks.

PII redaction

Automated controls attempt to mask personal details before redacted transcripts are displayed or analysed. Redaction reduces exposure but does not guarantee anonymisation.

Audio retention

Recordings receive an audio-expiry date 30 days after upload. Maintenance controls process scheduled deletion, and authorised users can request removal from the active service.

Platform security

Access controls apply at multiple layers.

Authenticated sessions and server and database checks apply store, role, and department boundaries to protected operations.

Role-based access

Store owners, managers, and staff have different product permissions. Server and database checks apply store, role, and department boundaries to protected operations.

Encrypted credentials

Supported integration tokens, including Gmail and Microsoft OAuth refresh tokens, are encrypted with AES-256-GCM before database storage.

Support access

Privileged support access and customer approval procedures are being documented. This page does not promise a control that has not yet been operationally verified.

Data categories

Depending on enabled features, Bolb processes feedback, store structure, team accounts, recordings, derived insights, integration data, and operational logs.

Retention and instructions

Deletion and offboarding need a defined scope.

Data retention

Retention differs by data category. Audio has a 30-day active-storage schedule; broader retention, backup, and offboarding periods remain subject to documented customer instructions.

Deletion scope

Product controls can remove supported records from the active service. Backup expiry, provider-held copies, and complete store offboarding are separate processes and are not described as immediate deletion.

Controller and processor roles

For customer feedback, the intended model is store as controller and Bolb as processor. The applicable agreement and collection notice must define the roles and instructions for each deployment.

Service providers

Core providers include Cloudflare, Supabase, OpenAI, and Resend. Google, Microsoft, or Meta also process data when the corresponding integrations are enabled.

FAQ

Common questions about security and data handling

Questions about security?

We're happy to walk through our data handling in detail — especially during pilot onboarding.