Draft privacy notice

Last updated 7 November 2026. This draft describes the current Gabel implementation and requires review for the operator's jurisdiction before production use.

Operator and contact

Gabel is operated by Nyaknno Udofia. Privacy requests: confidoway@gmail.com. Support: confidoway@gmail.com.

Data Gabel processes

Purposes and sharing

Gabel uses this data only to connect the requested Buffer account, show scheduled content metadata, check media accessibility on request, prepare an explicitly authorized media edit, verify the result, secure the service, and record truthful technical evidence. It sends OAuth and GraphQL requests to Buffer and bounded requests to selected media hosts. Buffer, media hosts, and connected social platforms process data under their own terms. This implementation has no analytics, advertising trackers, marketing email, payment processing, or sale of personal data.

Cookies

Gabel uses two first-party, strictly necessary cookies: an HttpOnly signed session cookie and a signed CSRF cookie. Both are Secure, SameSite=Lax, host-only, and expire after seven days. The server extends the matching database session on activity. No analytics or advertising cookies are present. Whether local law requires a notice or consent mechanism for these necessary cookies must be reviewed for the deployment jurisdiction.

Choices, inactivity, and deletion

The Account page can delete local Buffer credentials/cache or delete all data tied to this browser account. After seven days without a valid browser session, Gabel removes the sessionless browser account and cascades its remaining local records, including encrypted Buffer credentials. Because the account is identified by a browser cookie, contact the privacy address if the browser is unavailable or a request needs identity verification. Revoking Gabel in Buffer settings invalidates the Buffer grant. Gabel does not knowingly seek children's data; appropriate age rules and any age gate require qualified review for the intended audience and jurisdictions.

Security and limits

Tokens are encrypted at rest with AES-256-GCM and sent only server-to-server. Media checks reject private and reserved destinations, pin a validated address, revalidate redirects, cap time and redirects, and inspect no more than a 64 KiB prefix for file signature and dimensions. No system is guaranteed secure. A media availability check cannot guarantee successful publication by Buffer or any social platform.