Privacy policy
Effective
Google Drive access
The integration requests Google Drive's drive.file permission. During authorization, you select the folder. OpenPost Drive checks that it can write to that folder and uses the permission to create and reuse copies of JPEG and PNG images attached to outgoing Threads posts. It uses the folder and file identifiers and technical metadata such as file type, size, and checksum to verify and reuse the copies.
Storage and sharing
The Google refresh token is kept in a restricted file on the self-hosted server so the integration can operate when the browser is closed. Image copies remain in the chosen Drive folder until you remove them. The integration checks that each copy is downloadable without signing in and sends its direct download URL to Meta Threads during publishing. Anyone with that URL can download the copy while link sharing remains enabled.
Managing access and copies
Remove OpenPost Drive from your Google Account connections to revoke access and stop future uploads. Remove copies from the selected Drive folder and manage published Threads posts in Threads. To request deletion of the local credential or ask a question about this policy, use the support email shown on the app's Google consent screen.
Google data policy
OpenPost Drive uses Google API data for the publishing workflow described above. Its use and transfer of data received from Google APIs follow the Google API Services User Data Policy, including its Limited Use requirements.