1. Scope of this policy
This policy applies to MonocomSoft websites, Workspace accounts, cloud applications, desktop product purchases, support interactions, trials, fixed-term plans, and related services.
A product may provide additional notices where its workflow requires different data or permissions.
2. Information you provide
We receive information you knowingly provide when you create an account, organization, or tenant; request support; start a trial; purchase a plan or license; subscribe to updates; or submit a contact form.
- Name, email address, business name, and contact details
- Account, organization, tenant, role, and access information
- Plan, order, invoice, tax, and payment status information
- Support messages, diagnostics, and product feedback you choose to share
3. Information collected automatically
When you visit or use our services, systems may record technical information such as IP address, browser, device type, operating system, referring page, timestamps, session activity, errors, and feature usage.
Cookies and similar technologies may be used for sign-in, security, preferences, performance, analytics, and essential site operation. Browser controls can limit non-essential cookies where available.
4. How information is used
We use information to provide and secure accounts, create organizations or tenants, grant app access, operate trials and fixed-term plans, process purchases and renewals, deliver licenses, provide support, prevent abuse, improve performance, and meet legal obligations.
We may send service messages about account security, billing, product access, policy changes, or support. Marketing communication is sent according to applicable consent and opt-out requirements.
6. Product and local workflow data
Local Windows utilities are designed to process source files and records on the user computer unless a feature clearly requires an external connection. Customers remain responsible for their source data, backups, permissions, and outputs.
Cloud applications may store the business records needed to provide their functions. Access is controlled through the relevant account, organization, tenant, and application permissions.
6a. Google-connected features in SEO Auditor 360 for Windows
Optional connection and data access. When you choose to connect Google Search Console, SEO Auditor 360 requests the read-only https://www.googleapis.com/auth/webmasters.readonly permission. Google handles sign-in and consent. The app receives authorization tokens, the addresses and access levels of matching Search Console properties, and search-performance data for the property and reporting period you select. This data may include search queries, page addresses, countries, clicks, impressions, click-through rate and average position. The permission lets the app read Search Console data; it does not authorize changes to your properties.
How the data is used. The app uses this information to display search-performance reports, filter and compare retained results, relate findings to your website audit, and create reports you choose to export. Google connections are optional for local website auditing.
Storage and protection. Search Console results and page-performance records are saved in the app's local workspace on your Windows computer. OAuth tokens and API credentials are also stored locally and protected using Windows data protection for the signed-in Windows user. Tokens and credentials are excluded from exported reports. Saved project data and exported files should be protected through your device security and backup practices.
Transfers and sharing. In this Windows integration, Google API requests are sent directly to Google. Search Console results and authorization tokens are not automatically uploaded to MonocomSoft servers. You control any reports you export or share, and any data you choose to provide to support. MonocomSoft does not sell Google API data, share it with data brokers, or use it for advertising. The general marketing and service-provider descriptions elsewhere in this policy do not expand these permitted uses of Google API data.
PageSpeed and Chrome UX Report. When you request page-performance analysis, the app sends the selected page address or website origin, device setting and API credentials to the relevant Google service. Google returns Lighthouse lab measurements or available aggregated Chrome UX Report real-user measurements. These results are used for your performance analysis and locally saved reports. Google processes requests under its own privacy policy.
Retention, disconnection and deletion. Local results remain until you delete the relevant files. Choosing Disconnect removes the locally stored OAuth session and requests revocation at Google. You can also revoke the app's access through your Google Account's third-party connections settings. Disconnecting does not erase previously saved results, configured API credentials or exported reports. Removing a project from the workspace may retain a local recovery copy; permanently deleting its data requires removing the relevant local records, recovery copies, exports and any backups you control. Contact support@monocomsoft.com for assistance locating local app data or requesting deletion of information you have sent to MonocomSoft support.
Google API data commitments. SEO Auditor 360 follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs.
6.b. Google-connected features in Contact Extractor 360 for Windows
Optional connection and permissions. Google handles sign-in and consent when you choose to connect a Google account. The current Windows sign-in requests openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/gmail.readonly and https://www.googleapis.com/auth/contacts.readonly together. OpenID and account email identify the connected account. Gmail and Contacts permissions allow reading; they do not authorize sending or changing mail, or creating, editing or deleting contacts. Google access is optional for extraction from local files and pasted text.
Data accessed and how it is used. For Gmail collection, the app reads mailbox labels and the selected messages, including headers, message bodies and available attachment content such as contact cards. When you select Google Contacts collection, it reads contact names, email addresses, phone numbers, organizations and website addresses through the Google People API. Both read permissions are requested at sign-in; reading contacts is controlled by your collection selection. The app uses this data to collect source snapshots, extract selected contact details, show their source evidence, relate and review contacts, identify duplicates and create exports you choose to save.
Local storage and protection. Collected message and contact snapshots, extracted values, source evidence and collection checkpoints are retained in local project data on your Windows computer. OAuth access and refresh tokens are stored separately using Windows data protection for the signed-in Windows user and are not included in project data or exports. This token protection does not mean that project snapshots, exported files or backups are encrypted. Protect your device and any project files, exports and backups that you keep or share.
Transfers, sharing and restricted uses. In this Windows integration, Gmail, People API and account identity requests go directly to Google. Google mail, contacts and authorization tokens are not automatically uploaded to MonocomSoft servers. You control exports and any information you choose to send to support. MonocomSoft does not sell Google API data, share it with data brokers, use it for advertising, or use it to train generalized artificial intelligence or machine learning models. Human access is limited to your affirmative consent for specific support needs or the security and legal exceptions permitted by the Google API Services User Data Policy. General marketing or service-provider descriptions elsewhere in this policy do not expand these uses of Google API data.
Retention, disconnection and deletion. Choosing Disconnect removes the locally saved Google session; it does not revoke permission at Google. To revoke the app permission, remove its access in your Google Account third-party connections settings. Disconnecting or revoking access does not erase snapshots, extracted results, exports or backups already saved. Delete the relevant local projects and retained data, and separately remove exports, recovery copies and backups you control when you no longer need them. Original input files are separate from project data. Contact support@monocomsoft.com for help locating local app data or requesting deletion of information you have sent to MonocomSoft support.
Windows integration and your choices. This section describes the Google connection in Contact Extractor 360 for Windows. It does not describe browser uploads or cloud storage in the separate Workspace app. Collect only information you are authorized to access; extraction does not establish marketing consent.
Google API data commitments. Contact Extractor 360 follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs.
7. Security and retention
We use reasonable administrative, technical, and organizational safeguards appropriate to the service. No online system can guarantee absolute security, so customers must also protect passwords, devices, accounts, and exported data.
Information is retained for as long as needed to provide services, maintain records, resolve disputes, enforce agreements, prevent fraud, and meet legal or accounting requirements.
8. Access, correction, and choices
You may review or update available account information through the service. You may also contact support to request access, correction, deletion, or information about your personal data, subject to identity verification and legal retention requirements.
You can opt out of non-essential marketing messages using the unsubscribe method provided. Essential security, billing, and service notices may still be sent.
9. Changes and contact
We may update this policy as products, laws, or practices change. The latest version and effective date will remain available on this page.
Privacy questions and requests can be sent to support@monocomsoft.com. Please do not include passwords, payment credentials, or unnecessary sensitive source data.