← STZ LLC Privacy Policy

Argos IP — how we handle Facebook and Instagram data

Annex to the STZ LLC Privacy Policy · Last updated: November 2, 2026

Argos IP is a product of STZ LLC: a management platform for parliamentary offices. One of its features lets an office connect its own Facebook Page and the Instagram professional account linked to it, to publish posts and follow their performance from inside the platform.

This annex states specifically which Meta data we access, why, for how long we keep it, and how to revoke access or ask for deletion. It complements — and does not replace — the main policy.

The connection is optional and always initiated by the office. No Facebook or Instagram data is accessed before a person who administers the Page explicitly connects it through Meta's own authorization screen, and access can be revoked at any time.

1. Permissions requested, and why each one is required

Permission Why it is required
public_profile To identify the person who authorized the connection, so the office knows who connected the account.
pages_show_list To list the Pages the person manages so the office can choose which one to connect.
pages_read_engagement To read the Page's basic information and its published posts, so they can be shown alongside the office's other communication in the platform.
pages_manage_posts To publish, on the office's behalf, the posts the office itself prepared and approved in the platform. Nothing is published without an explicit action by the office's staff.
read_insights To show the Page's performance metrics (reach, engagement) to the office.
instagram_basic To identify the Instagram professional account linked to the Page and read its profile and media, so the office can see what is published.
instagram_content_publish To publish, on the office's behalf, the photo and video posts the office prepared and approved in the platform.
instagram_manage_insights To show the Instagram account's performance metrics to the office.
instagram_manage_comments To let the office read and respond to comments on its own posts.
business_management To access the Page and Instagram account when they are owned by the office's business portfolio rather than by an individual profile.

We ask only for what is needed to publish and measure the office's own content. We do not read private messages, and we do not access the personal profile, friends list or timeline of the person who connects the account.

2. What we store

Page and account data

Identifier and name of the connected Page and Instagram account, the posts we publish through the platform (text, media and publication status), the Page's and account's posts and comments we read for display, and aggregated performance metrics.

Comment authors

Comments on the office's own posts may include the public name of whoever commented. We keep them only while needed to show and answer them to the office.

Access credentials

We store the access tokens issued by Meta, needed to keep publishing and reading without asking for authorization every time. They live in a restricted table reachable only by the product's internal services — never exposed to the browser, to other offices, or to third parties.

3. How the data is used

Solely to serve the office that connected the account. Concretely:

Offices are isolated from one another: data from a connected account is only accessible to the staff of that office.

4. How we protect this data (security)

5. What we do NOT do

Our use of data received from Meta complies with the Meta Platform Terms and Developer Policies. In particular, data obtained from Meta is not:

6. Where it lives and for how long

Data is stored on Supabase infrastructure, on servers located in the United States. Because the office and the data subjects are in Brazil, this constitutes an international transfer, addressed in the main policy.

Data remains for as long as the account stays connected. On disconnect, access tokens are deleted immediately and the Page and account data we hold is deleted within 30 days, unless the office asks us to keep it or the law requires retention.

7. How to revoke access and request deletion

8. Contact

Questions, data subject requests or security incidents should be directed to our data protection officer, Irineu Claro Sturza, at company@stz.llc.