Privacy policy

Who operates the service

Appsweet is operated by Blendable. This policy covers the Appsweet website and the AppSweet-managed OAuth broker used by invited private-beta installations. Each self-hosted Appsweet installation has its own operator, who remains responsible for the product data in that installation.

Website data

The website can save your language and light or dark theme preference in your browser's local storage. These preferences stay on your device.

The current beta website does not use advertising trackers or analytics cookies and does not require an Appsweet account. Normal hosting security logs may contain technical request data such as an IP address, time, requested path, and browser information.

Google and YouTube permissions

Appsweet uses YouTube API Services and accesses Google or YouTube data only after a workspace administrator chooses to connect a channel and completes Google's consent screen.

• Google's publishing permission allows viewing, editing and permanently deleting YouTube videos, ratings, comments and captions. Appsweet requests it to identify the selected channel, upload videos, apply the chosen title, description and visibility, confirm the result, and read basic video statistics.
• Advanced analytics is a separate, optional connection. If enabled later, it allows Appsweet to read channel and YouTube Analytics data for user-facing statistics. Refusing or removing analytics permission does not disable publishing permission.
• Appsweet never asks for or stores your Google password. Google issues OAuth access and refresh tokens for the permissions shown on its consent screen.

How the managed connection works

The managed OAuth broker temporarily receives Google's authorization code and token response because it performs the OAuth exchange. It immediately encrypts the resulting grant for the specific customer installation. Tokens and Google response bodies are not written to broker logs or its durable database.

The encrypted handoff can be claimed only by the customer installation. That installation decrypts the grant and stores the durable OAuth tokens in its own secret store. The broker handles later token refreshes because the managed Google client secret is not distributed to customer systems.

Channel discovery, video uploads, publishing, and optional statistics requests go directly between the customer installation and Google or YouTube. The broker does not receive video files, post content, channel analytics, channel names, user profiles, or email addresses.

Storage and retention

The managed broker deliberately keeps only bounded operational data:

• OAuth attempts and pseudonymous workspace bindings expire within 15 minutes.
• A deployment-encrypted token handoff is deleted when claimed and otherwise expires within 5 minutes.
• Secret-free operational audit and aggregate metrics are retained for up to 30 days; redacted logs and traces for up to 14 days.
• An opted-in installation's opaque identifier and public encryption or signing keys remain for the registration lifetime; a secret-free deletion record may remain for up to 30 days.
• Durable tokens, channel data, schedules, uploaded content, and statistics remain in the customer installation under that operator's retention and backup policy.

Use and sharing

Data is shared with Google or YouTube only to perform the actions the user requested. Infrastructure providers may process the bounded hosting, database, secret-management, and security-log data needed to operate the managed broker.

Appsweet's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. Google or YouTube data is not sold, used for advertising, credit decisions, surveillance, or unrelated profiling.

People are not permitted to read Google or YouTube user data unless the user gives specific permission, access is necessary to investigate security or abuse, or access is required by law.

• Google Privacy Policy
• Google API Services User Data Policy

Your choices and deletion

A workspace administrator can disconnect a YouTube channel in Appsweet. This removes the stored connection grant when it is no longer used by another connected destination. You can also revoke Appsweet's access at any time from your Google Account.

After a channel is disconnected in Appsweet, related Google or YouTube API data under Appsweet's control is deleted as soon as possible and no later than 7 days. After access is revoked through Google Account settings or authorization can no longer be verified, deletion occurs as soon as possible and no later than 30 days. For product data in a self-hosted installation, contact that installation's operator.

Managed OAuth is optional. An operator can instead configure its own Google project and use Appsweet's bring-your-own OAuth path; that path does not contact the managed broker.

• Review or revoke connected applications in Google Account security settings

Security

Appsweet uses encrypted transport, deployment-specific encryption, signed requests, short-lived single-use capabilities, restricted service identities, and secret-free diagnostics to protect OAuth material. Customer private keys and durable grants are not available to the hosted management plane.

This is a private beta. The managed connection remains limited to invited test users while security, privacy, provider verification, quota, retention, and operational controls are completed. No system can eliminate all risk, so use the beta only with channels and content appropriate for testing.

Children

Appsweet and its managed Google or YouTube connection are business productivity features and are not directed to children.

Changes and contact

This policy will be updated before Appsweet uses Google or YouTube data for a new purpose. Where required, affected users will be asked to consent again.

For questions or deletion requests about the private beta, use the support contact supplied with your beta invitation or the developer contact shown on Google's consent screen.