Privacy Policy — Meetings

Meetings (“the app”) is a business app for iPhone and Android that records meetings and delivers them to your organisation’s workspace on TechXcel’s business AI platform for transcription and summaries. This policy explains what the app collects, where that information goes, who can access it, how long it is kept, and the choices available to you and your organisation. It covers both the iPhone app and the Android app. Where the two behave differently, this policy says so.

In this policy, “TechXcel”, “we” and “us” mean Qorelink Pty Ltd, trading as TechXcel, of Australia. We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles.

In short

• The app records audio only after you start a recording, and uploads it with the meeting’s details to your organisation’s workspace.
• Your organisation controls its workspace. TechXcel operates the workspace on your organisation’s behalf, and TechXcel’s technical staff can access it to run and support it.
• Support requests you send, and automatic error reports about your recordings, reach TechXcel with your email address and are stored in GitHub in the United States.
• By default, uploaded audio stays on your phone for 30 days after your organisation’s workspace has processed it, and is then deleted automatically.
• The app contains no advertising, analytics or tracking SDKs and does not use your location.

1. Your organisation and TechXcel

The app is licensed to organisations for use by their staff under a separate agreement with TechXcel. You can only sign in with a Microsoft 365 work account in an organisation that TechXcel has set up, and only after your organisation’s administrator has given you access to Meetings. Personal Microsoft accounts are not accepted.

Each organisation has its own workspace: a separate deployment of TechXcel’s business AI platform, hosted in Microsoft Azure in Australia. TechXcel operates each workspace on the organisation’s behalf, as its service provider. Your organisation controls the recordings and other information in its workspace: it decides who can access them, how long they are kept, and which features and AI services are used. In privacy terms, your organisation is the controller of that information and TechXcel is its processor. TechXcel uses its own service providers, such as Microsoft Azure and AI model providers, to run the workspace (section 3.1).

TechXcel also receives some information directly: support requests you send, automatic error reports, and requests to its tenant-discovery service (sections 3.3 and 3.4).

2. What the app collects and why

2.1 Audio recordings

The app records audio only after you start a recording, using the microphone your phone is currently using (its built-in microphone or a connected headset). You can start a recording:

• in the app, for a meeting in your calendar or as an impromptu recording;
• on iPhone, with the Meetings “Toggle recording” shortcut, from Siri, the Shortcuts app or the Action Button;
• on Android, with the “Record meeting” tile in Quick Settings or the “Record” shortcut on the app icon.

These shortcuts open the app and start recording straight away, without asking you to confirm (on iPhone, this includes when the shortcut runs from an automation you have set up). Using a shortcut again while a recording is in progress stops it. You can pause or stop a recording at any time, and recording continues while the screen is off.

Audio is saved in the app’s private storage on your phone and uploaded automatically to your organisation’s workspace, over Wi-Fi only if you turn on “Upload on Wi-Fi only”. The app keeps its copy on your phone for the period you choose (section 6.1). The app does not transcribe audio itself; transcription happens in the workspace.

2.2 Account information

You sign in through Microsoft’s sign-in service (Microsoft Entra ID), using the Microsoft Authentication Library. The app receives from Microsoft:

• your name and email address (or, where Microsoft does not supply an email address, your Microsoft sign-in name);
• your Microsoft account ID, a unique identifier for your work account;
• your organisation’s Microsoft tenant ID, which identifies your organisation’s Microsoft 365, not you;
• sign-in tokens that let the app read your calendar from Microsoft and use your organisation’s workspace as you.

Every request the app makes to your organisation’s workspace carries your sign-in token, which identifies you by name, email address and Microsoft account ID. If you do not already have a user record in the workspace, the workspace creates one the first time you use it, holding your name, email address and Microsoft account ID, and it keeps your name and email address up to date when they change in Microsoft 365. The workspace uses your email address to check that your organisation has given you access to Meetings.

Permissions the app asks Microsoft 365 for. When you sign in, or when your IT administrator approves the app for your organisation, the app requests these permissions:

• Sign in and read your profile (User.Read): your own name and email address. On iPhone, the app also uses it to show your profile photo in Settings.
• Read your calendars (Calendars.Read): your upcoming meetings (section 2.3).
• Read all users’ basic profiles (User.ReadBasic.All): this would allow the app to read basic directory details, such as name, email address and photo, for other people in your organisation. The app does not use this permission. It makes no directory look-ups and reads no profile but your own. The permission is listed here because the app currently asks for it at sign-in.
• Access to your organisation’s Meetings service: lets the app use your organisation’s workspace as you, to check that Meetings is enabled for you; upload recordings with their meeting details and check their processing status; re-link a recording the workspace no longer recognises, using its calendar event ID; rename recordings; read your user settings in the workspace and save your time zone to them; read your organisation’s branding; and send support requests, including any screenshots you attach.

The Microsoft Authentication Library also requests the standard sign-in permissions that identify you to the app and keep you signed in between launches.

2.3 Calendar and meeting details

Using the calendar permission, the app reads up to 50 of your Microsoft 365 calendar events in the next 36 hours, including each event’s ID, title, start and end time, organiser, attendees (names and email addresses), your response to the invitation, whether it is an online meeting, whether it is an all-day event, and whether it is part of a recurring series. It uses them to show your upcoming meetings, let you record a meeting with its details attached, schedule any meeting reminders you turn on and, where your organisation allows it, offer to share a recording with the meeting’s attendees.

The app holds events you do not record in memory only; it does not save them to its own storage (on iPhone, the system’s standard web cache may keep a copy of the calendar response). If you turn on meeting reminders, each upcoming meeting’s title and calendar event ID are scheduled with your phone’s notification system. On Android, the app also saves each scheduled reminder’s meeting title, calendar event ID and time so it can restore reminders after the phone restarts, and clears them when you turn reminders off or sign out.

When you record a calendar meeting, the app saves the meeting’s title, start and end time, calendar event ID, organiser and attendee list (each attendee’s name and email address, and your own response to the invitation) on your phone with the recording, together with whether you chose to share it with attendees. The same details are sent to your organisation’s workspace with the recording. There they become the recording’s details (for example, the meeting title becomes the recording’s title, and the calendar event ID is used to detect duplicate uploads and to re-link recordings), and the attendee list is used to help identify speakers in the transcript.

Sharing with attendees. Where your organisation allows it, you can tick “Share meeting transcript with all internal attendees” before recording a calendar meeting. It is off unless you tick it. The workspace then gives each attendee who has an account in your organisation’s workspace access to the recording. Although the option mentions the transcript, those attendees can see the whole recording, including its audio while the workspace keeps it.

An impromptu recording sends no calendar information. On iPhone, attendee names you type for an impromptu recording are shown on the recording screen only; they are not saved or sent.

The app’s notifications (and, on iPhone, its Live Activity on the Lock Screen) can show meeting and recording titles. Depending on your phone’s notification settings, these may be visible while your phone is locked.

2.4 Recording titles you type

The name you type for an impromptu recording, and any new name you give a recording later, are saved on your phone and sent to your organisation’s workspace as the recording’s title.

2.5 Your time zone

When you sign in, and each time the app starts with a saved sign-in, the app reads your phone’s time zone setting (for example, “Australia/Perth”). If it differs from the time zone saved in your user settings in the workspace, the app saves it there, so that times in your summaries use your local time. The time zone is a setting, not your location; the app does not use location services.

2.6 Support requests

Sending a support request is optional. You can open the support form from Settings → About → Help & feedback, or from the Support button on the Logs screen. A request contains:

• the category you choose, and the subject (optional) and message you write;
• any screenshots you attach, up to five, chosen with your phone’s photo picker, which gives the app only the images you select. The app resizes them and converts them to JPEG before sending;
• details that are always included: the app version; your phone’s operating system version and model (on Android, the Android version and API level, and the device make and model); your organisation’s Microsoft tenant ID and its name (on Android, the name your organisation’s workspace is branded with); and the time you sent the request.

Include device logs is on by default. While it is on, the request also includes the 20 most recent entries from the app’s activity log (section 2.7) with meeting and recording titles removed, and a snapshot of your phone and the app: how many recordings are waiting to upload or failed to upload, the last upload error and the time of the last successful upload, the number of recordings and the amount of audio waiting to upload, your auto-delete setting, free storage, network type, microphone permission status, battery level and charging state, Low Power Mode (on Android, battery saver), language and region setting, time zone, and any recent calendar or branding error message. On iPhone it also includes whether Live Activities are allowed. On Android it also includes notification permission status, whether a recording is in progress, whether the network is reachable, and your “Upload on Wi-Fi only” setting. Turn the option off to send only your message, screenshots and the details that are always included.

The app itself does not add your email address, any recording or transcript, or meeting titles to a support request, unless you include them in your message or screenshots. However, your organisation’s workspace adds your email address, from your account, when it forwards the request to TechXcel.

Support requests go to your organisation’s workspace, not directly to TechXcel. The workspace stores the request, all the details above and any screenshots, and forwards the request to TechXcel’s support queue (section 3.4). We use support requests to respond to you and to diagnose and fix problems.

2.7 Activity log and diagnostic logs on your phone

The app keeps an activity log on your phone, which you can view at Settings → Diagnostics → Logs. Each entry records an upload, delivery or failure event, with the meeting or recording title, a status or error message, the recording’s local ID and the time. On Android, the log also records calendar refreshes and sign-in check-ins. Entries stay on your phone after you delete a recording and after you sign out. On iPhone, entries are kept until you uninstall the app. On Android, the app keeps the most recent 200 entries and removes older ones automatically. The log leaves your phone only as part of a support request, with titles removed (section 2.6).

On iPhone, the app also writes diagnostic messages to the iOS system log. These can include your first name and organisation name each time the app starts while you are signed in, your email address and tenant ID when you sign in or are refused access, and, if a response from your organisation’s workspace cannot be read or reports an error, the first part of that response, which can include a recording title or an email address. The app never reads, exports or sends these messages. On Android, the app writes only technical error messages to the system log, without your personal details.

2.8 Technical information sent with requests

• Like any internet connection, each request reveals your phone’s IP address to the service that receives it.
• Requests carry standard technical headers that identify the app, its version and your phone’s operating system. On Android, these include the Android version and the device model.
• The Microsoft Authentication Library sends Microsoft its standard technical details with sign-in requests, such as the library version, your phone’s operating system and version, the device model, and error codes from earlier sign-in attempts. Microsoft handles these under its own terms.

2.9 What the app does not collect

• The app contains no advertising, analytics or behavioural-tracking SDKs, does not use your phone’s advertising identifier, and does not track you across other companies’ apps or websites.
• The app does not request or use your location.
• The app does not access your contacts. Attendee details come only from your calendar events.
• The app does not access your photo library, other than the screenshots you choose to attach to a support request.

3. Where your information goes

The app connects only to the services described in this section.

3.1 Your organisation’s workspace

The app sends your organisation’s workspace the audio of each recording, its meeting details and title (sections 2.3 and 2.4), your sign-in token with each request (section 2.2), your time zone (section 2.5), recording renames, and support requests (section 2.6). Audio is uploaded directly to the workspace’s storage in Microsoft Azure, using a short-lived, upload-only address the workspace issues for each recording. The app also reads your organisation’s branding (name, colours and logos) from the workspace, and downloads the logos from the addresses the workspace supplies, without sending a sign-in token.

In the workspace, the audio is transcribed using Microsoft Azure’s speech service, speakers are identified (using the attendee list where there is one), and AI models produce outputs such as summaries, follow-ups and risks. The workspace stores the recording, its transcript, its meeting details and these outputs. If your organisation turns on voice matching, the workspace also creates voice profiles (numerical representations of speakers’ voices) from recordings, to recognise the same speakers in later meetings. Voice matching is off unless your organisation turns it on.

Who runs the AI models. The AI models are run by providers TechXcel engages as its service providers, and the transcript, or the part of it needed for the task, is sent to the provider your organisation’s workspace is set up to use. Depending on that set-up, these are Amazon Web Services (AWS Bedrock, in Sydney), Anthropic (United States), OpenAI or Microsoft Azure OpenAI (United States and other locations), and Google (Vertex AI, which asserts no single location). Your organisation can tell you which of them its workspace uses. Section 5 sets out what this means for information leaving Australia.

Your organisation decides who can see recordings in its workspace, how long they are kept and which AI services process them. For how your organisation uses recordings, contact your organisation’s IT administrator.

3.2 Microsoft

Sign-in goes through Microsoft Entra ID (and, if your organisation’s Microsoft 365 sign-in is federated, your organisation’s own sign-in service). The app reads your calendar from Microsoft Graph and, on iPhone, your profile photo. If Microsoft Authenticator is installed (or, on Android, Company Portal), sign-in may go through it. These are your organisation’s Microsoft 365 services, which Microsoft provides to your organisation; the app reaches them with your own sign-in. Microsoft also receives the technical details described in section 2.8.

3.3 TechXcel’s tenant-discovery service

When you sign in, and each time the app starts with a saved sign-in, the app sends your organisation’s Microsoft tenant ID to a tenant-discovery service that TechXcel operates in Microsoft Azure in Australia. The service returns the address of your organisation’s workspace, which the app saves. The request carries no sign-in token, and none of your name, email address, recordings or calendar. Like any web service, it sees your phone’s IP address. Requests are logged for operational purposes; the logs can include the tenant ID, the result of the request and the time.

3.4 TechXcel’s support queue

TechXcel tracks support requests and errors as issues in GitHub, a software development service. These issues are stored in the United States (section 5).

Support requests. When your organisation’s workspace forwards a support request, the issue TechXcel receives includes your email address (taken from your account in the workspace); the name of your organisation’s workspace and a label identifying your organisation; the category, subject and message; your app version, operating system version and device model (on Android, also the device make); and the number of screenshots attached. If device logs were included, it also includes your organisation’s name and tenant ID, the activity-log entries and the device and app details listed in section 2.6. Screenshots are not copied to GitHub; they stay in your organisation’s workspace, where TechXcel support can view them. If you reply to the request in the workspace, and when a reply from TechXcel support reaches you, a comment showing your name and email address is added to the issue.

Automatic error reports. If your organisation’s workspace fails to produce the summary, follow-ups, risks or transcript corrections for a recording you uploaded, it automatically files an error report in TechXcel’s support queue. The report includes your email address, a label identifying your organisation and technical details of the error. If the same error happens again, a further comment carrying your email address is added to the same issue. We use these reports to diagnose and fix problems with the service.

3.5 App update checks

• On iPhone, each time the app starts or you switch back to it while signed in, it asks Apple’s App Store lookup service whether a newer version is available. The request contains only the app’s identifier and the Australian App Store region.
• On Android, the app asks the Google Play Store app on your phone whether an update is available, using Google Play’s in-app update service, which Google provides under its own terms. The app sends Google no account, organisation or recording information.

3.6 Things you choose to send elsewhere

“Save audio” in the recordings list passes a recording to your phone’s share sheet, which sends it wherever you choose. Settings → About → Privacy opens this policy in your web browser. On iPhone, “Update now” on the new-version prompt opens the app’s App Store page.

4. What TechXcel can access

Because TechXcel operates your organisation’s workspace, TechXcel’s technical staff have administrative access to the systems that store it. This means TechXcel can access the recordings, transcripts, meeting details, account information and support requests held there. TechXcel uses this access to operate, maintain, secure and support the workspace on your organisation’s behalf (for example, to investigate a problem you or your organisation reports), and where the law requires it.

TechXcel also holds the information it receives directly: support requests and automatic error reports (section 3.4), and tenant-discovery logs (section 3.3).

We do not sell personal information, and we do not use it for advertising.

5. Information outside Australia

Your organisation’s workspace and TechXcel’s tenant-discovery service are hosted in Microsoft Azure in Australia. Some information is handled outside Australia:

• Support requests and automatic error reports are stored in GitHub in the United States (section 3.4). They include your email address and, for support requests, what you wrote.
• Transcripts are sent to the AI providers that produce summaries and other outputs (section 3.1). Which providers depends on how your organisation’s workspace is set up: Amazon Web Services (AWS Bedrock) processes in Sydney; Anthropic processes in the United States; OpenAI and Microsoft Azure OpenAI process in the United States and other locations; and Google (Vertex AI) asserts no single location, so a request sent there may be handled anywhere Google operates. Your organisation can tell you which of them its workspace uses.
• Microsoft handles sign-in and calendar information as part of your organisation’s Microsoft 365 service, under your organisation’s arrangements with Microsoft.
• Apple (on iPhone) and Google (on Android) handle app update checks under their own terms (section 3.5).

6. How long information is kept

6.1 On your phone

After a recording has been uploaded and your organisation’s workspace has finished processing it, the app keeps the audio on your phone for the period set under Settings → Storage & uploads → Auto-delete after sync: 1, 7, 14 or 30 days, or Never (keep the audio until you delete it yourself). The default is 30 days, on both iPhone and Android. The period is counted from when the workspace finished processing the recording (or, if the workspace does not report that time, from when the app learns of it). Audio that has not been uploaded, is still being processed, or failed to upload or process is never deleted automatically, whatever the setting.

The app checks for audio past its auto-delete period:

• on iPhone, each time the app starts while you are signed in, and straight after you sign in. It does not check in the background, so audio is removed at the next check, which can be some time after the period ends;
• on Android, each time the app starts, and about once a day in the background.

A change to the setting takes effect at the next check. Automatic deletion removes only the audio: the recording’s details, including its meeting and attendee details, stay in the recordings list until you delete the recording.

The other information the app stores on your phone (section 7.1) is kept until you delete it or uninstall the app, except that cached organisation details, branding and scheduled reminders are cleared when you sign out (on Android, so is the saved record of your workspace account), and the activity log is kept as described in section 2.7.

6.2 In your organisation’s workspace

Your organisation decides how long recordings, transcripts, meeting details, support requests and other information are kept in its workspace. The workspace does not delete them automatically; they are kept until they are deleted (section 9). Microsoft’s speech service holds a copy of the audio while it transcribes it, for about 24 hours.

What deleting in the workspace does. Deleting a recording in the workspace removes the recording, its transcript, its AI outputs, its speaker details and any sharing from the workspace’s database, deletes the audio and the files made from it from Microsoft Azure storage, and deletes the transcription job at Microsoft’s speech service. Some copies remain for a limited period afterwards:

• Azure keeps a retained copy of a deleted file so that a file deleted by mistake can be recovered. That copy is removed automatically, and no more than 90 days after the recording was uploaded to the workspace.
• Copies of the workspace’s database can remain in its backups for up to 35 days, until those backups expire.

Deleting a recording does not remove the meeting it belongs to: the meeting’s title, start and end time and organiser stay in the workspace. Support requests and any screenshots attached to them cannot be deleted in the workspace. To have either removed, email privacy@techxcel.au (section 9).

6.3 Held by TechXcel

Support requests and automatic error reports in GitHub are kept for as long as TechXcel needs them to support the service and track problems; they are not deleted automatically after a set period. Tenant-discovery logs are kept for 90 days and are then deleted automatically. You can ask us to delete any of these sooner (section 9).

7. Storage on your phone and security

7.1 What the app stores on your phone

On iPhone:

• Recorded audio files (section 6.1).
• A database with details of each recording: its title, duration, recording and meeting times, audio format, quality and file size, upload state and times, the workspace’s ID for the recording, any error message, whether you chose to share it with attendees and, for calendar meetings, the calendar event ID and attendee names and email addresses.
• The activity log (section 2.7), in the same database.
• A cache of your organisation’s details (tenant ID, name, initials, workspace address, region and status) and branding (workspace name, colours, logo addresses and which features are enabled), cleared when you sign out.
• Your preferences (auto-delete period, Wi-Fi-only uploads, meeting reminder options, theme and colour choices), and a small amount of working state, such as which in-app tips you have seen and a record linking recent uploads to their workspace recording IDs, kept for 7 days.
• Your Microsoft sign-in tokens and a record of your account (your name, sign-in name, Microsoft account ID and tenant ID), in the iOS keychain, encrypted at rest.

On Android:

• Recorded audio files, in the app’s private storage (section 6.1).
• The recordings list, with details of each recording: its title, capture time and duration, audio quality and file size, upload state, the workspace’s ID for the recording, any error message, whether you chose to share it with attendees and, for calendar meetings, the meeting’s start and end time, calendar event ID, organiser’s email address, and attendee names and email addresses.
• The activity log, up to 200 entries (section 2.7).
• A cache of your organisation’s details (tenant ID, name and initials, workspace address and region) and branding (colours, logo addresses and which features are enabled), cleared when you sign out.
• Your preferences (theme and colours, audio quality, Wi-Fi-only uploads, auto-delete period and meeting reminder options), your scheduled meeting reminders (section 2.3), and, briefly, a pending request from the Quick Settings tile or app shortcut.
• Your Microsoft sign-in tokens and account, in app-private storage managed by the Microsoft Authentication Library.
• A record of your account in your organisation’s workspace: your name, email address, the workspace’s ID for you, whether Meetings and workspace administration are enabled for you, and your organisation’s tenant ID. The app saves it each time the workspace confirms your account, so that it can let you back in if the workspace cannot be reached the next time the app starts. It is cleared when you sign out.

On both platforms, recording details stay after the audio is deleted automatically and after you sign out, until you delete the recording.

7.2 Backups and uninstalling

On iPhone, uninstalling the app removes its recordings, database and preferences. The app does not exclude its recordings or database from iPhone backups, so copies may remain in backups made before you uninstalled it. Sign-in tokens and the account record are held in the iOS keychain, which iOS manages separately from the app; signing out before uninstalling removes the tokens, but not the account record.

On Android, the app’s data is excluded from Android cloud backup and from device-to-device transfer, so it is not copied to a backup or to a new phone. Uninstalling the app removes all of its data from your phone.

7.3 Security

• The app connects only over HTTPS, so information is encrypted in transit.
• Audio is uploaded using a short-lived, upload-only address issued for that one recording.
• Each organisation’s workspace is a separate deployment in Microsoft Azure in Australia, and information stored there is encrypted at rest by Azure.
• Using the app requires your organisation’s Microsoft 365 sign-in, and your organisation’s administrator must have given you access to Meetings.

No system is completely secure, but we take reasonable steps to protect the information we handle.

8. Your choices and controls

In the app (the same on iPhone and Android unless noted):

• Settings → Storage & uploads: “Upload on Wi-Fi only”; “Auto-delete after sync” (section 6.1); and “View all recordings”, where you can play, rename, save, re-sync or delete a recording.
• Settings → Meeting reminders: reminders are off unless you turn them on. Choose how far ahead they fire, and whether to skip declined or recurring meetings.
• Settings → Permissions: see whether microphone and notification access are granted, and open your phone’s settings to change them.
• Settings → Diagnostics → Logs: view the activity log (section 2.7).
• Sharing with attendees: off for each calendar recording unless you tick it before recording (section 2.3).
• Sign out: the sign-out icon on the account card at the top of Settings.

Signing out removes your Microsoft sign-in tokens from the app, clears the cached organisation details and branding, cancels scheduled meeting reminders (reminders already shown are not removed), and stops the app reading your calendar. On Android, it also clears the saved record of your workspace account described in section 7.1. On iPhone, the record of your account described in section 7.1 stays in the iOS keychain. If sign-in went through Microsoft Authenticator (or, on Android, Company Portal), signing out of Meetings does not sign you out of that app.

Signing out does not delete your recordings, their saved meeting and attendee details, the activity log or your preferences, because these are not tied to your account. Anyone who signs in to the app next on the same phone can see, play and export your recordings and see the activity log. Any of your recordings that had not finished uploading, and any recording they choose to re-sync, may be uploaded to their account and their organisation’s workspace, not yours. Before someone else uses the app on your phone, delete your recordings in the recordings list. The activity log is removed only by uninstalling the app (on Android, entries beyond the most recent 200 are also removed automatically).

Calendar access is a Microsoft 365 permission granted at sign-in (section 2.2), not a phone permission, so there is no in-app switch for it. Signing out stops the app reading your calendar. To withdraw the permission for your account or your organisation, speak to your IT administrator.

On your phone (menu names can vary between phone makers):

• iPhone: Settings → Meetings to turn microphone or notification access off.
• Android: Settings → Apps → Meetings, then Permissions to turn microphone or notification access off. “Alarms & reminders” on the same screen controls whether meeting reminders can fire at the exact time.
• Uninstalling the app removes its data from your phone (section 7.2).

9. Deleting your information

For the steps to follow, set out on their own page, see how to delete your Meetings data.

On your phone. Delete any recording from the recordings list. This removes its audio and saved details from your phone. It does not remove anything from your organisation’s workspace: a copy already uploaded is not affected, and an upload already under way may still reach your organisation. Activity-log entries that mention the recording are not deleted. Audio is also deleted automatically on the schedule you choose once a recording has been processed (section 6.1). Uninstalling the app removes all of its data from your phone (on iPhone, see section 7.2 for backups and the keychain). Signing out clears your sign-in tokens, cached organisation details, scheduled reminders and, on Android, the saved record of your workspace account, but does not delete recordings or the activity log (section 8).

In your organisation’s workspace. Sign in to your organisation’s workspace in a web browser, open Meetings, and delete the recording: every user can delete the recordings they made. Section 6.2 sets out what that removes and what remains for a limited period afterwards. Only the person who made a recording, or whoever set up the meeting it belongs to, can delete it, and support requests and any screenshots attached to them cannot be deleted in the workspace, so for anything else email privacy@techxcel.au and we will act with your organisation to have it deleted. Your organisation’s IT administrator controls access to Meetings and can remove yours.

Held by TechXcel. To have support requests, automatic error reports or tenant-discovery logs deleted, email privacy@techxcel.au with your organisation’s name or Microsoft tenant ID and the email address used on the support request or error report.

10. Access, correction and complaints

You can ask for access to the personal information held about you, and ask for it to be corrected. Your organisation is responsible for the information in its workspace, so for recordings, transcripts and your workspace account, start with your organisation; TechXcel will assist your organisation to respond. For information TechXcel holds directly (section 4), or if you are not sure who to ask, email privacy@techxcel.au. We will respond within a reasonable period, usually within 30 days.

If you have a concern about how your information has been handled, contact us at privacy@techxcel.au first. We will acknowledge your complaint within 5 business days, investigate it, and respond to you in writing with the outcome and what we will do about it, usually within 30 days. If we need longer, we will tell you why and when to expect our response. If you are not satisfied with it, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

11. Children

The app is designed for use at work by adults. It is not directed at children, and it is licensed only to organisations for use by their staff.

12. Changes to this policy

We will publish any changes to this policy at https://journey.techxcel.au/meetings-privacy and update the effective date at the top of this page.

13. Contact

Privacy queries and requests: privacy@techxcel.au
Support: support@techxcel.au
Qorelink Pty Ltd, trading as TechXcel, Australia