Commercial conversation data
We process the sales context required to generate a proposal: customer needs, product references, constraints, pricing inputs and approval notes.
Security and compliance
beCloser handles conversations, pricing, margins and proposal engagement. This page explains the beta posture honestly and marks the legal details that still need final validation.
We process the sales context required to generate a proposal: customer needs, product references, constraints, pricing inputs and approval notes.
beCloser is built from the EU and designed around data minimization, purpose limitation and human-controlled approval workflows. TODO: validate legal basis and DPA wording with counsel.
The production architecture should keep primary customer data in EU regions where supported by subprocessors. TODO: confirm final Supabase/project region.
Traffic is protected in transit with HTTPS/TLS. Data at rest relies on managed infrastructure encryption from the selected providers. TODO: document final provider controls.
TODO: publish the final list of subprocessors, including hosting, database, email and analytics providers.
Beta data should be retained only while needed for the pilot and support. TODO: confirm default retention windows and deletion workflow.
TODO: add DPO or privacy owner contact. Until then, contact hello@becloser.io for privacy requests.