Privacy · October 23, 2026
Meta connection privacy supplement
App-specific supplement to the Bielby Group Privacy Policy. The group policy remains separate with its original scope. Backup and security-record retention details still need operator confirmation before Meta review submission.
Read the Bielby Group Privacy PolicyScope and operator
This supplement covers the real Bielby Group AI account and Meta connection area. The product demo uses simulated data. Bielby Group AI is operated by Bielby Group LTD Oy. The group privacy policy lists hello@bielbygroup.com for privacy questions.
Information collected
App sign-in uses your email, account identifier and authentication session. Connecting Facebook provides an app-scoped user identifier, granted permissions, token expiry and an authorization token. Explicit inventory reads may display your Facebook name and optional email, business portfolios and business-user names and roles, owned or shared catalogs and product names, availability, prices and currencies, Page content and available comment-author identities, and the Threads identifier connected to a Page's Instagram professional account. The connection also reads ad account and Page identifiers, currencies, tasks, campaign states and delivery totals. A paused ad test uses your approved image, copy, destination, country and budget. Customer lists, submitted leads, health data and Threads posts are not requested.
Purposes and sharing
We use these data to authenticate you, inspect authorized assets and content, review business access and catalog readiness, display reporting, create explicitly approved paused ad objects, and retain limited activity outcomes for review preparation. Comment-author identities are displayed only for human content review, never for customer matching or ad targeting. Meta receives your authorized requests and approved test configuration. Lovable Cloud provides authentication and server-side storage. Google or Lovable receives a sign-in request if you choose that method. This flow does not install a Meta Pixel or upload conversion events.
Security and retention
Meta tokens are encrypted before storage and never returned to the browser. Stored connections, tests and activity are separated by app account. Connection and test records remain until deletion or a verified Meta deletion/deauthorization request. Authorization-start records expire after ten minutes and are single-use. Images are sent to Meta, not saved as an app image library. Inventories, profile details and comment identities are held in the current page session; the app does not persist those returned records. Reporting caching may last up to fifteen minutes. Activity records contain action names, success, status, timestamps and selected asset identifiers, not returned contact or comment data. Evidence exports contain read-outcome summaries only. Platform backup and security retention remain subject to operator confirmation.
Your choices and deletion
Meta connection and additional workflow permissions are optional. Facebook may omit an email or author identity; the app does not invent it. “Disconnect & delete Meta data” revokes permissions where possible and deletes stored connection, test metadata and related activity. It does not delete Meta-side objects or close your app sign-in account. Also remove the integration in Facebook if its token has expired. Meta may send a verified signed deletion request and receive a confirmation receipt.
Data deletion instructions