Skip to content
Veriaco
Get started

Services

YouTube monetizationChannel managementYouTube consultingChannel promotionContent ID protectionMusic copyright registrationInternational paymentsPayPal accountInternational SIM cards
AboutFAQContactSign in
فارسیEnglishTürkçeالعربية

Privacy Policy

Last Updated: August 22, 2026

Veriaco ("Veriaco", "we", "us", or "our") operates the Veriaco web application and related services (the "Service"). This Privacy Policy explains how we collect, use, store, protect, and disclose information when you use our Service, including information obtained through Google APIs and YouTube APIs.

By using Veriaco or connecting a Google/YouTube account to the Service, you acknowledge the practices described in this Privacy Policy.

1. Information We Collect

We collect information necessary to provide and operate the Service. Depending on how you use Veriaco, this may include:

We collect and retain only information that is reasonably necessary for the functionality requested by the user.

2. Google and YouTube User Data

When you connect a Google or YouTube account to Veriaco, we may access certain information associated with your authorized YouTube channels through the Google APIs. Depending on the permissions granted and the features you use, this may include:

YouTube Data. Through the youtube.readonly scope, Veriaco may access read-only information associated with the YouTube resources authorized by the user, including channel and account information necessary to identify and operate the connected channel.

YouTube Analytics Data. Through the yt-analytics.readonly scope, Veriaco may access read-only YouTube Analytics information associated with the authorized channel for analytics and reporting functionality.

YouTube Analytics Revenue Data. Through the yt-analytics-monetary.readonly scope, Veriaco may access read-only YouTube Analytics monetary information associated with the authorized channel for analytics and reporting functionality.

Veriaco does not request permission to upload, modify, delete, comment on, or otherwise make changes to YouTube content. All Google and YouTube API permissions used by Veriaco are read-only.

3. How We Use Google User Data

We use Google and YouTube user data only to provide and improve the user-facing functionality of Veriaco. This may include:

We do not sell Google user data.

We do not use Google user data for targeted advertising, personalized advertising, retargeting, or interest-based advertising.

We do not use Google user data to determine creditworthiness, provide lending services, or sell information to data brokers or information resellers.

We do not use Google user data to train generalized or non-personalized artificial intelligence or machine-learning models.

4. Google API Limited Use

Veriaco's use of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

We request only the Google API permissions necessary to provide the functionality described in this Privacy Policy and use Google user data only for providing or improving user-facing features of the Service.

We do not use Google user data for purposes unrelated to providing or improving the functionality of Veriaco.

5. Data Protection and Security of Google User Data

We implement technical and organizational safeguards designed to protect Google user data against unauthorized access, disclosure, alteration, or loss.

Encryption at Rest

Google OAuth refresh tokens stored by Veriaco are encrypted at rest using AES-256-GCM authenticated encryption.

Each encrypted refresh token uses a randomly generated initialization vector (IV) and an authentication tag to protect the confidentiality and integrity of the stored credential.

The encryption key is maintained separately from the database through a protected server-side environment variable and is not stored in the database.

Accordingly, access to a copy of the database alone does not provide the ability to decrypt the stored Google OAuth refresh tokens.

Encryption in Transit

Communications between users and Veriaco are protected using HTTPS/TLS.

HTTP requests to the Service are redirected to HTTPS to help protect information transmitted between users and the application.

OAuth Token Protection

Veriaco does not store Google OAuth access tokens.

Where persistent authorization is required, Veriaco stores only the encrypted OAuth refresh token necessary to maintain the authorized connection.

When a channel is added, the authorization granted at sign-in is retained as an encrypted refresh token and becomes that channel's connection, so that the analytics and reporting features described in this Privacy Policy can operate. It is stored under the same protections as any other retained refresh token. Where a verification does not result in a connected channel, the retained authorization is revoked and the stored credential is deleted.

When a user disconnects their Google/YouTube account from Veriaco, the associated stored authorization data is deleted and the applicable Google authorization is revoked where supported by the authorization flow.

Access Controls

Access to Google user data within the Veriaco application is controlled using role-based access controls (RBAC) and the principle of least privilege.

Users are restricted to information associated with their own authorized channels according to the permissions assigned to their account.

Employees do not have direct access to the production database, encryption keys, or the server infrastructure containing Google user data.

Direct administrative access to the production server, database, and encryption infrastructure is restricted to authorized senior management personnel and is limited to legitimate operational, security, and maintenance purposes.

Data Minimization

Veriaco follows a data-minimization approach and collects and retains only the Google user data reasonably necessary to provide the requested Service and its related functionality.

We do not intentionally collect Google user data that is unnecessary for the features provided by Veriaco.

6. Sharing and Disclosure of Google User Data

Veriaco does not sell, rent, or trade Google user data.

Google user data is not disclosed to third parties except where disclosure is necessary to provide the requested Service, comply with a legal obligation, protect the security of the Service, prevent fraud or abuse, or protect the rights and safety of Veriaco, our users, or others.

We do not transfer Google user data to third parties for advertising, data brokerage, information resale, or other unrelated purposes.

Access to Google user data within Veriaco is restricted according to the access-control measures described in this Privacy Policy.

7. Data Storage and Hosting

Veriaco's application and production data are hosted on infrastructure provided by Hetzner in Germany.

Google user data is stored within the Veriaco production environment as necessary to provide the Service.

Sensitive OAuth credentials are protected using the encryption mechanisms described in the "Data Protection and Security of Google User Data" section of this Privacy Policy.

8. Data Retention

We retain information only for as long as reasonably necessary to provide the Service, maintain an authorized connection, provide requested analytics and reporting functionality, maintain security, comply with legal obligations, resolve disputes, and enforce our agreements.

Google OAuth refresh tokens are retained only while the associated Google/YouTube connection remains necessary for the Service.

When a user disconnects their Google/YouTube account, the associated stored authorization data is deleted in accordance with our data deletion procedures.

9. Contact

Questions about this Privacy Policy, or requests to access or delete your data, can be sent to info@veriaco.com.