Privacy & Required Data Notice

Scope and operator

The operator who supplied your dashboard access controls this deployment. Contact that operator at tvtinh.official@gmail.com for privacy questions and requests. Customer work is separated by authenticated account. Authorized administrators may access account details, saved groups, saved posts and reported posting history for support, security and operations. Administrative detail access is recorded in a server-side audit log.

What is processed and why

• Dashboard authentication: Google authenticates your account and supplies a verified identity identifier, email address and profile name. Tinifb does not receive your Google password or request access to Gmail or Drive. Secure HttpOnly cookies and database sessions identify your account and active browser session. Google processes the sign-in under its own policies.
• Facebook connection: the extension reads relevant Facebook session cookies and obtains request tokens in your browser to execute your chosen actions. These are sensitive credentials. The intended cloud flow does not require uploading these secrets; never paste them into drafts, settings, or support messages.
• Facebook identity and groups: profile identifiers, name/avatar references, and group identifiers/names are used to show the acting identity and select destinations. Group selections and related work state may be stored in the cloud.
• Your content: drafts, saved posts, selected groups, settings, schedules, queue data, reported posting events, and results are stored in PostgreSQL. Images uploaded through the dashboard are stored in configured S3-compatible/R2 storage with media metadata in PostgreSQL; time-limited URLs provide access. Local extension/browser storage can also contain work state and images.
• Acceptance: accepted terms/privacy versions, acceptance time, account ID, and session ID are recorded server-side at login. Server-side attempt counters limit repeated authentication and MFA requests.
• Operational metadata: the hosting, database, and storage providers may process connection and service logs under the operator's configuration. Raw customer content and credentials should not be included in support reports.

Administrator authentication

Administrators must verify an Authenticator code or a single-use recovery code before accessing administration APIs. Authenticator secrets and recovery codes are stored encrypted. Temporary replay-prevention records use a keyed digest. Never send these secrets or codes to support.

Who receives data

Facebook receives the posts, images, and requests you send. The configured hosting, PostgreSQL, and object storage providers process the data needed to run this deployment. The intended workflow does not sell your data or send it to an AI service for training. Do not submit unredacted customer data to an external AI reviewer.

Retention and deletion

The current code does not implement automatic expiry for saved work, images, or acceptance records, or a self-service deletion endpoint. They remain until the operator deletes them. Signing out invalidates the dashboard session but does not erase saved work, uploaded images, local browser storage, provider backups, or posts on Facebook.

Request access, export, correction, or deletion by emailing tvtinh.official@gmail.com. The operator must verify the request and cover database rows, media objects, extension/browser storage, applicable logs, and backup retention. Facebook content must be managed separately on Facebook.

Your choices and limits

Required processing is necessary to execute the posting actions you request. You can decline acceptance, stop posting, sign out, and disable or uninstall the extension. You choose the groups, text, and media; avoid supplying unnecessary sensitive personal data. Acceptance does not waive privacy rights or authorize processing unrelated to this service.