Privacy Policy

Core32 is a business workspace operated by Ai32 (we, us or our). This policy explains how we handle personal information when you visit our website, use Core32, connect another service, participate in a meeting or contact us.

If your employer or another organisation provides your workspace, that organisation decides what information to put in Core32 and how its team uses it. We process workspace content to provide the service to that organisation. Its own policies also apply. We separately handle account, billing, support and service-operation information as described here.

Our Terms of Service explain the conditions for using Core32.

• Account and business details: your name, work email, profile, organisation, role, membership and authentication information.
• Workspace content: messages, documents, uploaded files, tasks, project and client records, calendar events and information you or your organisation add to Core32.
• Meetings and voice: participant details, audio and video needed to run a call, and recordings, transcripts or summaries when those features are used. Voice-assistant features process the audio and instructions you provide.
• Connected services: information made available by the permissions you grant, such as mailbox messages, attachments, contacts or calendar events, together with connection credentials and synchronisation details.
• AI interactions: prompts, relevant source content, responses, generated files, feedback and records of tool or workflow actions.
• Service records: billing contacts, subscriptions, invoices, usage and cost records, support correspondence, device and browser information, IP addresses, timestamps, error reports and security logs.

We collect information directly from you, from authorised users and administrators, from services you connect, and automatically as the service operates. If required information is not provided, we may be unable to create an account or deliver the affected feature.

Only provide personal or sensitive information you are authorised to share. Workspace content may include information about people who do not have a Core32 account.

We use information to operate the workspace; authenticate users and enforce access rules; store, search and retrieve content; run enabled AI, meeting and integration features; carry out instructions and configured workflows; provide support; administer subscriptions and usage; troubleshoot and improve service reliability; prevent misuse; and meet applicable legal obligations.

What Core32 processes depends on the features and connections used by your organisation. An AI feature may process relevant messages, documents or meeting notes to answer a question or perform a requested task.

• Your organisation and collaborators: content is available according to workspace membership, roles and sharing settings. Administrators manage business access and configuration; administrator status does not mean every private source is shared.
• Service providers: infrastructure, storage, email delivery, AI, transcription, video, support and other providers receive information needed to deliver the features they support.
• Services and recipients you choose: information may be sent to an external service, meeting participant, message recipient or shared-link recipient when you use a feature that makes that disclosure.
• Legal and business circumstances: we may disclose information where required or authorised by law, to protect legal rights or security, or to advisers and parties involved in a business transfer subject to appropriate confidentiality arrangements.

Core32 supports services such as Amazon Web Services for infrastructure and AI, OpenAI, Anthropic and xAI for AI features, Deepgram for transcription, Agora or Daily for meetings, and Microsoft or Google for connected accounts. The providers involved depend on your configuration and the features used; not every provider receives every workspace record.

AI processing can involve sending your prompt, selected business context, attachments or audio to the provider supporting that feature. Provider processing locations and retention depend on the service and applicable agreement. We do not promise that every AI feature has zero retention or operates entirely in your workspace’s storage region.

Connecting an external assistant through an API or connector can disclose the information retrieved to that assistant’s provider. Its terms and privacy policy apply to its handling of that information. Review the connection and its permissions before enabling it.

You can disconnect supported integrations in Core32 or revoke their permissions with the source provider. Disconnecting stops future access through that connection; it does not automatically erase information already imported, sent or retained as part of workspace records. Contact your administrator or us about deletion.

Meeting organisers are responsible for giving participants appropriate notice and obtaining any required consent before recording or transcribing a meeting. You can choose whether to grant device microphone and camera access.

When you connect Google Calendar, Core32 requests your Google account email, the list of calendars you can read, and read-only access to calendar events. You choose which calendars Core32 imports. Imported information includes event titles, descriptions, locations, dates, times and links to the original events. This connection does not request permission to change your Google events or read your Gmail.

We use this information to display your schedule and support the calendar features you use. When you ask a Core32 assistant about your schedule, relevant event information may be sent to the AI provider supporting that request. Google data is not used for advertising, sold, or used to train general-purpose AI or machine-learning models. Transfers to service providers are limited to providing or improving these user-facing features, security purposes, legal obligations, or other uses permitted by Google’s policies.

Core32 follows the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API user data policy. Human access to Google data is limited to the circumstances those policies permit, such as your consent for support, security investigations, or a legal requirement.

Connection tokens are encrypted in storage. Imported calendar events are associated with your Core32 account and business. Disconnecting Google Calendar removes its stored connection tokens and imported calendar events from the active service. Backup copies and information you separately saved in other workspace records follow the retention provisions below. You can also revoke Core32 access through your Google Account’s third-party connections page, or contact admin@ai32.com.au to request deletion.

Our standard infrastructure is hosted in Australia. Workspace deployment settings and external providers can involve processing or access overseas, including in the United States. A workspace’s storage location does not determine where all connected services, AI inference or provider support operate.

The locations involved depend on the provider, feature and deployment selected. Contact us before enabling a feature if your organisation has particular residency requirements. We can provide information about the providers and processing locations relevant to your deployment.

We use technical and organisational measures designed to protect information, including authenticated access, tenant and workspace permission controls, encrypted network connections and protected integration credentials. No service or transmission method can guarantee absolute security.

We retain information for as long as needed to provide the service, maintain relevant business records, meet legal obligations, resolve disputes and protect the service. Retention differs by record type, workspace configuration and customer agreement. Removing a user or disconnecting a service does not necessarily delete shared business records.

Deletion may be subject to recovery periods, backup cycles and legal retention requirements. External recipients may retain copies under their own policies. Contact us for information about retention or a deletion request for your workspace.

Core32 uses browser storage and similar technologies to keep sessions working, remember preferences and cache information for performance. Your browser may store workspace information locally while you use the application.

You can manage cookies and site storage in your browser. Clearing or blocking them may sign you out, remove saved preferences or prevent features from working. Connected third-party services may use their own cookies under their privacy policies.

You can ask about the personal information we hold about you, request access or correction, or request deletion where applicable. If the information belongs to an organisation’s workspace, contact its administrator first. We can help identify the appropriate request process.

For privacy requests or complaints, email admin@ai32.com.au. Describe your concern and the relevant account or organisation. Do not send passwords or other unnecessary sensitive information. We may need to verify your identity and authority before responding.

We aim to respond to privacy complaints within 30 days. If more time is needed, we will explain why. If you are dissatisfied, you may contact the Office of the Australian Information Commissioner or another regulator with jurisdiction. Your legal rights depend on the laws that apply to your circumstances.

We may update this policy as the service or our practices change. The current version and its update date will remain available on this page. Where required, we will provide additional notice of material changes.

Privacy contact: Ai32, admin@ai32.com.au.