Privacy, export, and deletion

Authorized account settings provide export and deletion controls. Review the confirmation and consequences before acting. An interrupted deletion leaves the workspace unavailable; contact support to finish it. Help cannot delete accounts, reveal another user's data, or change ownership. Security concerns, suspected unauthorized access, or unintended publication should go to support with minimal necessary detail. Never paste secrets or sensitive personal material. Ask support for data-request help.

Google Drive in Add post uses only drive.file for the photos and videos the user selects in Google's picker. The picker lets the user browse Drive folders, but a folder is not an automatic import grant. Google's permission includes editing and deleting selected files; ShootFeed only reads the originals and imports copies. The temporary token stays in memory, with no saved refresh token or new persistent Drive connection. Imported media is used only for the requested publishing workflow, including caption drafts through Google Gemini and optional face suggestions through AWS Rekognition. Google Drive data is not sold, used for advertising, or used for an unrelated purpose. Google Workspace API data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models. Users can revoke access through Google or delete imported content or their ShootFeed account. Previously stored watch-folder credentials remain encrypted; their folders and imported posts are preserved.

Google Drive watch-folder setup remains hidden from public and beta onboarding. Add post selected-file imports have a separate availability gate. If that button is absent, use Dropbox or direct upload. Do not promise automatic Drive synchronization.

When enabled, client review stores profile invitations and discussion notes. Workspace exports include invitation metadata, shared-post records and notes, but exclude invitation tokens and encrypted links. Removing a workspace deletes its related client-review records. Revoking an invitation blocks future access but preserves the conversation history.

The Privacy Policy section Sharing Google user data names the providers involved in Google-data processing and explains the purpose of each transfer. It covers application hosting/storage, Google/YouTube publishing, optional Drive caption/face processing, and user-requested help or notification handling. Connected-account credentials are not automatically supplied to Help or notification content; do not type secrets into a support message. This disclosure does not enable a new platform feature or expand an OAuth permission.

For X accounts that opt in to shared authorization, ShootFeed stores one encrypted rotating authorization with a separate consent record for each workspace. Every workspace must complete its own X authorization for the verified account. Disconnecting removes that workspace’s binding after its final profile connection is removed. The shared authorization is retained only while another explicitly authorized workspace needs it; the final removal requests provider revocation and clears the active stored authorization. A failed revocation follows the existing bounded encrypted retry queue. Old cleanup retries cannot revoke a newly authorized shared account. Account exports include only the requesting workspace’s X consent records, never tokens or another workspace’s bindings.