Privacy Policy
Last updated: 2025-08-16
This page explains how Benly HLG SAS ("Benly", "we", "us") collects, uses, shares, stores and protects personal data for our websites and products, and includes our Data Processing Agreement (DPA) and our Sub-processors list.
If you do not agree with this Policy, please do not use the Service.
Who we are
- For website, product telemetry, support and billing, Benly acts as a Data Controller.
- When a customer connects third-party advertising/e-commerce/analytics platforms (e.g., Facebook Ads, Google Ads/YouTube, TikTok Ads, GA4, Shopify), Benly acts as a Data Processor of the data pulled from those platforms on the customer's behalf. The DPA below applies to that processing.
Personal data we collect
1) You provide it
Name, email, organization, role; SSO (Google/Microsoft) identifiers; workspace names; report recipients (emails, Slack/Teams channels); support messages.
2) From connected sources (customer-directed)
When you authorize connections to ad/analytics/e-commerce platforms, we sync campaign/ad metadata, performance metrics (spend, impressions, clicks, conversions, revenue), product and creative metadata, and configuration needed to operate.
3) Collected automatically
Device/browser, IP address, timestamps, feature usage, error events; minimal website/product analytics via Plausible (privacy-friendly, cookieless).
How we use personal data (purposes & legal bases)
- Provide and operate the Service (authenticate users, connect sources, generate and deliver reports). (Contract)
- Maintain and secure the Service (monitoring, anti-abuse, incident response). (Legitimate interests / legal duties)
- Improve features and UX with privacy-preserving analytics. (Legitimate interests)
- Communicate (onboarding, product updates, billing/transactional notices). (Contract / legitimate interests)
- Marketing (B2B) with appropriate consent or soft opt-in; you can unsubscribe anytime. (Consent / legitimate interests)
AI / Model usage controls
By default, we do not use Customer Data or user prompts to train foundation models.
An Organization-level opt-in is available in Settings → Privacy; it can be changed at any time.
Sharing and disclosures
We share personal data only with:
- Sub-processors needed to run the Service (see list below).
- Third-party tools you connect (e.g., Slack/Teams for report delivery).
- Professional advisors and authorities when required by law.
- Successors in a corporate transaction under appropriate safeguards.
We do not sell personal data.
International data transfers
We support storage/processing in the EEA and the US (see Hosting & Sub-processors). For transfers outside the EEA/UK/Switzerland, we rely on EU Standard Contractual Clauses (SCCs 2021) and, where applicable, the UK Addendum and Swiss Addendum.
Security
We apply appropriate technical and organizational measures: encryption in transit/at rest, RBAC and least privilege, SSO, audit logging, secure SDLC, monitoring and incident response. See the TOMs in the DPA below.
Retention
- Account data, product logs, and generated artifacts (dashboards, report PDFs/CSVs/PNGs, insights): kept for the life of the account.
- Invoices: kept 10 years (legal requirement).
Deletion:
- On explicit request or account deletion, we permanently delete data promptly (immediately).
- After a subscription ends, we permanently delete data within 30 days.
- We may retain data strictly required by law (e.g., invoices for 10 years).
Your rights
Depending on where you live (e.g., EEA/UK), you may have the right to access, rectify, erase, restrict, object, port your data, and withdraw consent.
Contact privacy@benly.ai. If we act as Processor (connected platforms), please contact your Organization admin first; we support them under the DPA.
Cookies & analytics
We use Plausible Analytics in cookieless mode for aggregated usage. If we deploy any non-essential cookies or similar technologies, we will request consent via a banner and provide a Cookie Settings link to change choices anytime.
Children
Our Service is B2B and not intended for minors. If a minor's data is provided, contact us for prompt deletion.
Changes
We may update this page; material changes will be communicated to Organization admins.
Data Processing Agreement (DPA)
This Data Processing Agreement (DPA) forms part of the agreement between Benly HLG SAS ("Benly", Processor) and the customer that accepted the Terms of Use or an Order referencing this DPA ("Customer", Controller) (together, the "Parties").
1. Roles & scope
- For Customer Data from connected advertising/analytics/e-commerce platforms and generated outputs derived from those data, Customer is Controller and Benly is Processor.
- Benly processes Customer Data only to provide the Service: ingesting, normalizing, storing, analyzing, generating dashboards/reports/insights, delivering them (email/Slack), support, security, reliability, and as otherwise documented by Customer.
2. Instructions
Benly processes Customer Data only on documented instructions (Agreement, this DPA, in-product settings, written directions). If an instruction seems unlawful, Benly will inform Customer.
3. Confidentiality
Benly ensures authorized personnel are bound by confidentiality and receive privacy/security training.
4. Security (TOMs)
Benly implements appropriate technical and organizational measures, including:
RBAC, least privilege, SSO (Google/Microsoft); MFA for admin access; periodic access reviews.
TLS 1.2+ in transit; AES-256 at rest; managed keys; secrets management.
Data processing on OVHcloud infrastructure in France; network segmentation; firewalls/WAF.
Secure SDLC, code reviews, dependency scanning, rate limiting, input validation.
5. Sub-processors
Customer authorizes Benly to engage the sub-processors listed in the Sub-processors section below (and as updated). Benly imposes obligations no less protective than this DPA and will notify Customer at least 30 days before changes.
6. Assistance
Benly will assist Customer (where reasonable) with data-subject requests, security obligations, breach notifications, and DPIAs, taking into account the nature of processing and information available to Benly.
7. Personal Data Breach
Benly will notify Customer without undue delay after becoming aware of a breach affecting Customer Data and share available information to support Customer's obligations.
8. International transfers
Where personal data is transferred outside the EEA, the UK, or Switzerland, Benly ensures a valid transfer mechanism:
- Adequacy / DPF: Where available, Benly relies on an adequacy decision (e.g., the EU-US Data Privacy Framework and its UK/Swiss extensions) for certified recipients.
- Standard Contractual Clauses: In other cases, Benly implements the EU Standard Contractual Clauses (2021) in the appropriate module(s).
9. Return & deletion
- On explicit request or account deletion, Benly permanently deletes Customer Data promptly (immediately).
- After a subscription ends, Benly permanently deletes Customer Data within 30 days.
- Benly may retain data required by law (e.g., invoices for 10 years) and minimal logs strictly needed to evidence compliance.
10. Audits
With 30 days' prior notice, once per 12 months, Customer may audit Benly's compliance via third-party reports when available, security questionnaires, or a reasonable site/remote audit during business hours.
11. Liability & precedence
Liability follows the Agreement's limits. If there is a conflict, this DPA prevails over the Privacy Policy; the SCCs prevail over this DPA where they require stricter terms.
Sub-processors
The vendors below act as sub-processors when Benly processes Customer Data as a Processor. Tools used when Benly acts as Controller (e.g., Plausible analytics, identity providers) are listed for transparency but are not Customer-Data sub-processors.
A) Sub-processors (Processor role — Customer Data)
| Vendor | Purpose | Region | Transfer mechanism |
|---|---|---|---|
| OVHcloud (OVH Groupe SAS) | Data processing infrastructure (compute/network/db) | France (EEA) | EEA hosting |
| Amazon Web Services (AWS S3) | Storage of account/media/customer data and artifacts | EEA or US (per customer region) | EEA hosting or SCCs/UK Addendum |
| Brevo (Sendinblue) | Transactional email (invites, report links, billing notices) | EEA | EEA hosting |
B) Other providers (Controller context — transparency)
| Provider | Purpose | Region | Notes |
|---|---|---|---|
| Plausible Analytics | Privacy-friendly, cookieless analytics | EEA | Used for analytics; not a sub-processor of Customer Data |
| Google Identity (OAuth/SSO) | User authentication | EU/US | Identity provider; customer-directed sign-in |
| Microsoft Entra ID (OAuth/SSO) | User authentication | EU/US | Identity provider; customer-directed sign-in |
Change notice: We will notify Organization admins at least 30 days before any change to this list.