Privacy Policy

01Data we collect

Account and contact information such as name, email, company, role, tenant/workspace, and content you submit through forms or support channels.

Operational data you provide to the platform, including documents, workflows, messages, integration settings, audit logs, and metadata needed to provide the service.

Technical information such as IP address, browser, device, session, usage events, system errors, and security data needed to operate the platform.

02How we use data

To provide, maintain, secure, and improve the website, product, workflows, Copilot, data connections, review gates, billing, and customer support.

To process demo requests, onboarding, operational notices, usage reports, and account or service-related communications.

To detect abuse, prevent unauthorized access, review quality, meet legal obligations, and enforce applicable terms.

03AI, customer data, and access

Customer data is processed within tenant/workspace boundaries, user permissions, and configured data-source controls in the product.

When AI features are used, the system may send the minimum necessary context to model providers or processing infrastructure to generate responses, extract data, or execute workflows.

In the planning app, the current third-party AI integrations are TypeSafe AI Jev (Early Access API, api.typesafe.ai/v1/systemone, model jev-latest) for typed decisions, and the pay-as-you-go OpenRouter Developer API for text generation, running google/gemma-4-26b-a4b-it on DeepInfra's Zero Data Retention endpoint. Every OpenRouter request requires data_collection=deny and zdr=true, allows only DeepInfra, and disables fallbacks; TypeSafe states that it does not train or fine-tune models on API Input.

We do not sell personal data. Sharing with subprocessors is limited to operating the service, security, hosting, analytics, payment, or support under contract.

04Google Calendar and Microsoft Outlook Calendar data

Connecting a calendar is optional, and each member connects their own account in the planning app (pm.aiglobalhub.app) under Settings → Calendars. For Google we request calendar.readonly, calendar.events, and your email address; for Microsoft we request Calendars.ReadWrite, User.Read, offline_access, openid, and email.

We use this access only to: list your calendars so you can choose which ones count as busy time; read events from the calendars you choose so the planner does not schedule work over meetings and today's meetings appear on your dashboard; if you turn on writing, create, update, and delete the events that represent your own scheduled task blocks in the one calendar you pick; and receive change notifications from the provider to keep this up to date. We never modify or delete meetings the app did not create.

Imported meetings are visible only to you; public booking pages show busy times only, never titles or details. OAuth tokens are stored server-side and never sent to your browser. Google Workspace Calendar data and data derived from it — including titles, times, links, calendar metadata, busy blocks, and scheduling results influenced by those records — are isolated from Jev, Copilot, OpenRouter, and every other AI model provider. AI receives only app-native content created directly in the planning app, such as task titles/descriptions, comments, help questions, and review evidence.

AI Global Hub's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We do not sell calendar data, use it for advertising, use it to train or improve AI or machine-learning models, or allow humans to read it except with your consent, for security or abuse investigations, or as required by law.

Disconnecting a calendar deletes its stored tokens, imported meetings, and the task events the app created, and asks the provider to revoke access where supported. You can also revoke access at any time at myaccount.google.com/permissions or myapplications.microsoft.com.

05Retention and security

We use access controls, tenant separation, operational logging, encryption in transit, and reasonable safeguards appropriate to the nature of the data.

Data is retained as needed to provide the service, meet legal obligations, handle disputes, preserve audit trails, or comply with valid deletion requests.

No system is perfectly secure; if a significant data incident occurs, we will follow our response process and provide appropriate notice.

06Your rights and contact

Depending on your jurisdiction, you may request access, correction, export, restriction, or deletion of your personal data.

Tenant administrators are responsible for managing users, permissions, and organization-provided data in the platform.

Privacy and data requests can be sent to aiglobalhubapp@gmail.com.