Back to Syncbase Publisher

Syncbase Publisher

Privacy Policy

Operated by Syncbase · Last updated October 23, 2026

This policy explains how Syncbase Publisher accesses, uses, stores and deletes Google and YouTube account information. Syncbase Publisher is an internal tool operated by Syncbase and is not a public service. It does not govern our separate product, Shiftly Hiring Copilot, which has its own privacy policy.

1

Google account access and OAuth permissions

Syncbase Publisher connects to Google using OAuth. Access is granted by the owner of the Google account being connected; nothing is accessed until that authorization is given. Publisher requests only the permissions below.

  • https://www.googleapis.com/auth/youtube.uploadRequired for uploads

    Upload videos to the YouTube channel the owner authorizes.

  • https://www.googleapis.com/auth/analytics.readonlyOptional

    Read-only access to Google Analytics data, used only if an analytics account is connected for reporting.

  • emailOptional analytics connection

    The connected Google account email address, used to identify which account is authorized.

When the optional analytics connection is authorized, the email permission means Syncbase Publisher does receive the connected Google account's email address, which is used to identify which account has been authorized.

2

Information processed from YouTube

When a video is uploaded or scheduled, Syncbase Publisher processes upload metadata:

  • Video titles, descriptions and tags
  • Visibility settings and scheduled publish times
  • YouTube video IDs and video URLs returned after an upload

It also keeps scheduling records, publishing statuses and error information so that uploads can be tracked and failures investigated.

3

Information not currently stored

YouTube channel names and channel IDs, and other Google profile information, are not currently stored in Syncbase Publisher's application records.

4

Optional Google Analytics data

If an analytics account is connected using read-only access, Syncbase Publisher retrieves Google Analytics data in order to produce reports. That data is not persistently stored in Syncbase Publisher's application database.

5

Where Google credentials are stored

Google OAuth credentials and refresh tokens are held in server-side Base44 Secrets. They are not stored in the application's database.

6

Uploaded video and image files

Video and image files uploaded through Syncbase Publisher may be stored at publicly accessible URLs. These files should not be treated as private or access-restricted.

7

How we use this information

Information is used only to provide the publishing features that were authorized:

  • Uploading and publishing scheduled videos to the authorized YouTube channel
  • Recording scheduling status, results and errors for the operator
  • Producing optional analytics reports for connected accounts

The application's code does not use Google user data for advertising, for profiling, or for training AI models.

8

Service providers and sharing

Base44 provides application hosting, storage, authentication and infrastructure for Syncbase Publisher. Base44's own handling of data on its platform is governed by its agreements and policies.

Syncbase Publisher also integrates with social platforms, including Meta and LinkedIn, for their respective publishing features. When content is published to one of those platforms, that content and related information are sent to that platform, and the platform's own terms and privacy policy apply to it.

We do not sell Google user data.

9

Retention

Syncbase Publisher currently has no automatic data-retention expiration and no automated cleanup process. Application records and stored files may remain until they are manually removed.

10

Deletion and disconnection

Syncbase Publisher does not currently provide a working in-app control for disconnecting a YouTube account. Removing a stored Google OAuth credential requires manual removal from the server-side Secrets where it is held, which the operator carries out.

To request deletion of records or help with disconnection, email shiftly.helpsupport@gmail.com. We do not currently operate an automated deletion schedule, and we cannot commit to a fixed completion date for such requests.

11

Revoking Google access

You can revoke Syncbase Publisher's access to your Google account at any time from myaccount.google.com/permissions or the Google security settings page. Revoking access stops future access to that account; it does not by itself delete records that were already created, which remain until removed as described above.

12

Google API Services User Data Policy

Syncbase Publisher's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

13

YouTube API Services

Syncbase Publisher uses YouTube API Services.

By authorizing a YouTube account, you are subject to the YouTube Terms of Service and the Google Privacy Policy. You can review and remove Syncbase Publisher's access to your YouTube data through the Google account permissions page linked in the section above.

14

Cookies and website analytics

This website uses Google Analytics 4 to measure how the site is used. Google Analytics may use cookies or similar technologies, and you can limit or block them through your browser settings.

This website analytics is separate from the optional Google Analytics account connection described above: the connection uses read-only access to reporting data for an analytics account, and is not used to track visitors to this site.

15

Changes to this policy

This policy may be updated when Syncbase Publisher's data practices change. The date shown at the top of this page reflects the most recent update.

16

Contact

Syncbase Publisher is operated by Syncbase. For any question about this policy, or to request deletion or disconnection, contact shiftly.helpsupport@gmail.com.