Facebook Page integration
Privacy Policy
Effective 23 October 2026
This policy describes how Co za dzban handles data when you use the website or an administrator connects a Facebook Page to the app.
Website visits and sign-in
The website processes ordinary request information, such as the requested page, time, IP address, and browser information, to deliver the site and maintain its security. Administrators and other authorized users sign in with Google; the app receives their verified email address and uses it to check their account and role. A session cookie keeps the user signed in. The app stores the email address and role of authorized users in its database. Google handles sign-in information under its privacy policy.
The app counts browser visits to individual story pages in daily totals after filtering common automated requests. These counters store the article ID, UTC date, and number of views; they do not store visitor identifiers, IP addresses, or browser details.
Facebook Page data we access and store
During Meta authorization, the app receives a temporary authorization code and uses it to discover Pages available to the administrator. For those Pages it reads the Page ID, name, granted tasks, and access token. Discovered Pages are held in the administrator's server-side session while a Page is selected. The app stores the selected Page's ID, name, language and connection settings, and an encrypted Page access token in its database.
Why we use this data
The app uses the data to show and manage the selected Page connection. New connections start with publishing disabled. If Page publishing or engagement features are later enabled, the Page token may be used to carry out the enabled actions through Meta's API.
Facebook post import
The app can check posts from a configured public Facebook profile for links to articles. It may use Apify to fetch those posts. From the results, the app records candidate article URLs, associated Facebook post URLs, and import diagnostics so administrators can review proposed articles. This import does not use the saved Facebook Page token. Apify handles the requests under its privacy policy.
Where the data goes
The saved connection is held in the app's database. The Page token is encrypted there and is not sent to browser JavaScript. The app communicates with Meta to authorize and operate the connection. Meta handles data on its services under its own privacy policy.
Requests from public authorities
We use the following process for requests from public authorities for personal data, including data received through Meta:
- Legal review: Before responding, we verify the request and review its legal basis, scope, and jurisdiction.
- Challenge: We seek to challenge or narrow a request we consider unlawful or overly broad through an available legal process.
- Minimum disclosure: If disclosure is legally required, we provide only the information necessary to meet that requirement.
- Documentation: We record the request, review and legal reasoning, people involved, any challenge, the response, and what was disclosed.
Retention and deletion
The selected Page connection remains in the active application database until an administrator disconnects it. Disconnecting removes the saved connection, settings, and token from that database. It does not remove content already published on Facebook or delete Co za dzban articles. Anyone whose data is handled by the app can request its deletion by emailing the address below. See the user data deletion instructions for Page disconnection steps and request details.
Changes and contact
We may update this policy as the integration changes. The effective date above identifies the current version. Privacy questions can be sent to cozadzban+privacy@bnowakowski.pl.