Meta-specific document

Privacy for a deliberately narrow Page workflow.

This notice describes the RAIgence Growth Hive Facebook Page connection and publishing-verification workflow operated by ETZ ENTERPRISES LLC.

Effective date: September 8, 2026

1. Information processed

When an authorized administrator uses Facebook Login, the service processes authorization status and a visible list of eligible non-production Pages they manage, including Page identifiers, names and granted tasks. The protected production Page is excluded. User and Page access tokens are encrypted and stored server-side; they are not stored in browser storage, page source or verification evidence.

2. Permissions and synthetic lifecycle

The service requests exactly pages_show_list, pages_manage_posts, pages_read_engagement and business_management. The business permission enables discovery of portfolio-managed Pages. Meta grants broader portfolio administration capabilities, including access management; this service uses the permission only for Page discovery. Select only the current portfolio and Page needed for verification. After the administrator explicitly selects one eligible Page, the service processes fixed server-owned original and updated messages, an approval record and a one-use idempotency key to create, read, edit, read and delete one synthetic post, verify that it is unavailable, and revoke authorization.

3. Purpose and evidence

Information is used to list and select an authorized Page, bind every action to that Page and browser session, prevent duplicate writes, verify each result and secure the connection. The service retains a limited non-secret tombstone and lifecycle receipt that may include Page and post identifiers, status, hashes, trace identifiers and timestamps; it does not contain post text, access tokens, the App Secret or passwords.

4. Sharing

Information is sent to Meta only as needed for the administrator-requested Page connection and supervised synthetic lifecycle. Necessary infrastructure providers may process information to operate and secure the service. RAIgence does not sell personal data or Meta platform data.

5. Retention and deletion

On credential expiration, or when the verification workflow completes a successful disconnect or revocation, reusable user and Page token values are purged or replaced with encrypted empty values so they cannot authorize future access. A non-secret tombstone and final receipt may remain as reasonably necessary for security, auditability, legal compliance and dispute resolution; disconnecting therefore does not erase all evidence. A deletion request for retained information may be submitted through the published Meta data-deletion process.

6. Choices and contact

You may disconnect the selected Page connection, revoke platform authorization through the verification workflow or Meta settings, or request access, correction or deletion by contacting [email protected]. Do not email passwords, access tokens or government identification.