01About this policy
This Privacy Policy explains how BialCorp handles information through CMS 2.0, our internal marketing content management application. The application supports website updates, social media publishing, business prospecting, and reporting on company-owned websites. It is available only to authorized personnel.
This policy covers information processed by CMS 2.0. Websites we publish and third-party services have their own privacy policies.
02Information we access
CMS 2.0 processes content and information supplied by authorized users, such as website articles, social posts, business names, professional contact details, prospecting notes, and account information needed for internal access. Operational records may include sign-in activity, actions taken, timestamps, IP addresses, and error details.
When an authorized user connects Google Search Console, the application can access only company-owned website properties that the user is authorized to access, and the Search Console information needed for reporting. This includes property URLs and permissions, search queries, page URLs, clicks, impressions, click-through rates, average search positions, and available breakdowns such as date, country, device, and search appearance.
03Google authorization and use
Google access is granted through Google's OAuth authorization process. CMS 2.0 receives access tokens and, when offline access is granted, a refresh token that allows scheduled retrieval without repeated sign-in. BialCorp does not receive your Google password.
The Search Console reporting connection uses read-only access (https://www.googleapis.com/auth/webmasters.readonly). This permission does not authorize changes to website content, Search Console settings, or social media accounts. Website and social publishing use separate connections.
We store and use Search Console data for internal reporting on websites owned by our company. Reports show search visibility, historical performance, and content performance for those websites. We do not retrieve Search Console data for websites owned by clients, prospects, or other third parties. We do not use it to identify individual searchers, build personal prospect profiles, or populate outreach contact lists.
04Storage and protection
Retrieved reports and associated property information are stored in the application's server-side database or reporting storage for internal reporting on company-owned websites, including historical performance comparisons. Connection tokens are retained server-side to maintain authorized access. Operational logs and backups may contain related records.
Our handling requirements are to restrict access to personnel and service providers who need it to operate the application, protect information during transmission and storage, and keep connection credentials out of public pages and downloadable reports. Users must protect their accounts and report suspected unauthorized access to the application administrator.
06Retention and deletion
We retain application records and Search Console reports only while needed for internal reporting on company-owned websites, historical comparisons, security, or applicable recordkeeping obligations. Access tokens and refresh tokens are needed only while the associated connection remains authorized and in use.
You may request deletion of stored Google data and connection credentials by contacting the BialCorp CMS 2.0 administrator through your established internal company contact channel. Identify the Google account and website properties involved; do not send passwords or tokens. We may verify your authority before acting on a request.
On an approved deletion request, we remove the relevant credentials and data from active application storage, subject to legal retention requirements. Backup copies expire through the normal backup rotation and are not used for ongoing reporting. Revoking Google access alone does not delete reports already stored by the application.
07Your choices and account access
You may decline to connect Google; related Search Console reporting will then be unavailable. You can withdraw access at any time in your Google Account's third-party connections settings. Revocation prevents further authorized retrieval with that connection. Contact the application administrator to remove the connection from CMS 2.0 and request deletion of previously retrieved data.
Internal access is managed by BialCorp. Contact the administrator to request account corrections, access changes, or removal. Necessary authentication cookies may be used by the application to maintain your session; these informational pages do not add advertising cookies or third-party analytics.
08Questions and policy changes
For privacy questions, deletion requests, or security concerns, contact the BialCorp CMS 2.0 application administrator through your established internal company contact channel.
We will update this page when our practices change. Material changes to Google data use will be communicated to connected users, and any required consent will be obtained before the new use begins. The application is intended for authorized business users and is not directed to children.