Privacy policy

1. Information Outpost handles

• Workspace information: member email addresses, display names, roles, and access status; workspace name, header label, logo, and publishing defaults.
• Content and review records: titles, descriptions, thumbnails, source-file references, file metadata and versions, audience and visibility settings, playlist choices, review comments, approval history, and publishing status.
• Connected Google accounts: the account and channel identifiers, names or email addresses returned during authorization, granted access, and access and refresh tokens used to call the Google APIs.
• Technical information: service diagnostics and request information processed by our hosting and security providers to operate and protect the service.

2. Google Drive access

Outpost requests read-only Google Drive access to validate and stream videos and images selected by your team. The Drive permission can cover more files than the publishing workflow needs; Outpost checks that selected source files belong to the team folder configured by an administrator.

Original videos and Drive-linked images remain in Google Drive. Outpost reads them for preview and approved publishing; the application does not move or delete your original Drive files.

3. YouTube access

Outpost uses YouTube API Services to identify the connected channel, list and validate its playlists, upload approved videos, and set video metadata, custom thumbnails, playlist membership, and visibility.

Submitting a video for review does not start a YouTube upload. Explicit approval starts the upload, which is initially private while publishing steps complete. Outpost then applies the approved visibility, which can make the video public.

4. How information is used and shared

Information is used to provide workspace access, previews, review and approval, publishing, support, and service security. Authorized workspace members can view shared content; roles control changes and administrative actions.

Cloudflare provides hosting, access control, database, and private image storage. Google provides the connected Drive and YouTube services. Approved media and metadata are sent to YouTube for publishing. Public YouTube content is available according to the visibility you approve.

Outpost does not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. We use and transfer information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

5. Storage and security

Workspace settings, account records, content references, metadata, and review history are stored in Cloudflare D1. Uploaded thumbnails and workspace logos are stored in a private Cloudflare R2 bucket and served through authenticated application endpoints. Google tokens are encrypted before database storage. The workspace uses Cloudflare Access and application role checks.

Original videos remain in Drive. Approved copies are stored on the selected publishing platform. Instagram delivery can temporarily copy approved media to private R2 storage. Public information pages do not have access to the workspace database, stored images, or Google tokens.

6. Retention and deletion requests

Workspace records, saved images, publishing history, and connected-account credentials are retained while needed to operate the workspace and maintain its review history. Archiving content does not erase it. Deleting a draft hides it from normal use but can retain database records, attachments, and audit history.

You can request deletion of your Outpost data or connected-account credentials by contacting sastranababan@gmail.com. Identify the workspace and account involved so the administrator can verify the request. Deletion of Outpost records does not automatically delete original Drive files or videos already uploaded to YouTube; those can be managed separately in Google Drive or YouTube Studio.

7. Your choices and Google authorization

You can revoke Outpost’s Google authorization at any time through your Google Account’s third-party connections. Revoking authorization prevents subsequent Google API access using that authorization; it does not by itself erase previously stored Outpost records. Contact us if you also want those records deleted.

Workspace administrators manage member access and connected accounts. Publishing can fail if a source changes, access is revoked, or a provider limit is reached. Google services are also governed by Google’s Privacy Policy and the YouTube Terms of Service.

Instagram connections and data deletion

When an administrator connects Instagram, Outpost stores the professional account ID, username, encrypted access token, and token expiry. Outpost uses the instagram_business_basic and instagram_business_content_publish permissions to identify the account and publish approved images, ordered carousels, and Reels. Captions, approved media, container identifiers, published-post identifiers, and publishing status are processed for this workflow. No Instagram password is collected.

Draft uploads and previews are private. After approval, Outpost copies selected media to private Cloudflare R2 storage and gives Meta signed, temporary links valid for up to 24 hours. Anyone holding a valid link can fetch that specific approved file until it expires. Temporary delivery objects are scheduled for deletion after 48 hours; cleanup runs periodically. Failed cleanup is retried by later runs. Multipart uploads that are never completed require the bucket lifecycle cleanup described in deployment setup. Uploaded source images and workspace review records remain under the retention policy above.

Instagram posts are public after approval. Disconnecting Instagram removes its stored access token from Outpost and prevents future use of that connection. You may also revoke access through Instagram’s connected-app settings. Disconnecting or archiving content does not delete published Instagram posts; manage those in Instagram.

To request deletion of Instagram-related Outpost data, contact sastranababan@gmail.com, identify the connected Instagram username and workspace, and state which data should be deleted. The operator verifies ownership before processing the request and responds with the request status. This does not automatically delete posts held by Meta. Meta handles data under its privacy policy.

8. Cookies, changes, and contact

The public pages do not use advertising or analytics trackers. The private workspace uses security and session mechanisms needed for Cloudflare Access and request protection. Hosting and security providers may process technical request information.

We may update this policy as the service changes. The date above identifies the current version. Material changes to Google-data use will be disclosed before introducing the new use, with consent where required.

For privacy questions or requests, contact Outpost Team: sastranababan@gmail.com.