Privacy Policy for NgDinhNhaStudio
1. Data and Permissions We Access
Google. The App requests only the Google OAuth permissions needed for its publishing functions:
https://www.googleapis.com/auth/blogger— used to create and manage Blogger content that the authorized user intentionally chooses to publish through the App.https://www.googleapis.com/auth/youtube.upload— used to upload videos that the authorized user intentionally chooses to publish to YouTube.
The App does not request access to Gmail, Google Drive, Google Contacts, or unrelated Google services.
The App may also prepare content and metadata for manual publication to other social platforms. Under the current workflow, those manual destinations are not connected to NgDinhNhaStudio through their account APIs or OAuth authorization, and the App does not request their account credentials or tokens.
2. How Data Is Used
Data obtained through Google authorization is used only to provide actions initiated or explicitly authorized by the user, including:
- authorizing access to supported Google publishing capabilities;
- creating or publishing Blogger posts requested by the user;
- uploading YouTube videos requested by the user;
- checking non-secret publication or upload status when needed to confirm the result of an authorized action; and
- refreshing Google OAuth authorization so the user does not have to sign in again for every authorized action.
Google user data is not used for advertising, profiling, unrelated analytics, data brokerage, or AI model training.
3. How Credentials and Data Are Stored
Google OAuth client configuration and user authorization credentials are stored locally on the authorized user’s device in private credential locations excluded from source control. Credential values are not intentionally committed to GitHub, included in public source files, embedded in publication content, or written to public logs.
Access and refresh tokens are used only as needed for authorized Google API requests and token renewal.
Non-secret operational information, such as Blogger post IDs, YouTube video IDs, granted scope names, publication or upload status, and sanitized error status, may be retained where necessary to verify or audit an authorized action.
NgDinhNhaStudio does not operate a separate cloud database for storing Google OAuth tokens or Google user data used by these publishing integrations.
4. Sharing of User Data
The App communicates directly with Google’s official APIs and authorization systems for the supported Google integrations. Google credentials or user data are not routed through third-party social-media publishing services or cross-posting intermediaries.
We do not sell, rent, license, or share Google user data with advertisers, data brokers, or other third parties for their independent use.
Information is transmitted to Google only as required to perform the API actions authorized by the user.
5. Google API Services Limited Use
NgDinhNhaStudio’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Security
NgDinhNhaStudio applies least-privilege access, explicit authorization, local credential storage, secret redaction, and fail-closed publishing checks. The App does not use personal browser cookies or browser-session extraction as a substitute for official Google OAuth authorization.
No method of electronic storage or transmission is completely secure, but reasonable technical safeguards are used to reduce the risk of unauthorized access, disclosure, credential exposure, or accidental publication.
7. Retention and Deletion
Google OAuth authorization is retained locally only for as long as the authorized user chooses to keep the integration active. The user can stop future access by revoking NgDinhNhaStudio’s authorization through Google Account permissions and by deleting the locally stored authorization files.
Revoking the Google authorization grant prevents the App from continuing to use that revoked grant to obtain or use new access credentials. Locally retained non-secret operational records may be removed when they are no longer required for verification, auditing, or troubleshooting.
8. User Choice and Control
Each authorized user chooses which supported Google account to connect and which Blogger post or YouTube video is submitted through the App. Connecting an account alone does not authorize every prepared item to be uploaded or published.
Google account access can be reviewed or revoked through Google Account permissions settings.
For social platforms that are manual publication destinations under the current workflow, the user performs the platform-side posting action directly and retains control over the final content and publication state.
9. Children’s Privacy
NgDinhNhaStudio is not designed as a consumer service for children and does not knowingly collect personal information from children through its Google publishing integrations.
10. Changes to This Privacy Policy
This Privacy Policy may be updated when the App’s API usage, supported platforms, data handling, or security practices materially change. The “Last updated” date above will be revised when changes are made.
11. Contact
For privacy questions or requests related to NgDinhNhaStudio, please use the public Contact page.
Comments
Post a Comment