AZLO App Privacy Policy

Effective date: 2 November 2026.

AZLO is operated by Alexandra Lang, a sole trader trading as AZLO in South Australia, Australia. This policy covers the AZLO mobile and web planner. Contact support@azlo.com.au or visit https://azlo.com.au. Website cookies and physical planner orders require their own applicable disclosures.

Information you provide

AZLO handles your account email and identifier, sign-in information, planner settings, rosters and shift overrides, leave, plans, recurring patterns, notes, priorities, commute preferences and exercise entries, including quantities and feelings you choose to record. Your entries can contain sensitive information. Shared-calendar records include display names, invitations, membership and shared plans. Reminder preferences are stored for each account on each phone. Support messages and attachments contain information you choose to send us.

Avoid entering confidential workplace, patient or client information, or other people's sensitive information unless you have authority to do so.

How information is used

Information supports sign-in, local planning, cloud backup and synchronisation, shared calendars, planning-request interpretation, reminders, subscriptions where enabled, support and misuse prevention. Online voice usage is counted against account-related limits.

Device storage and cloud backup

Planner information is stored locally. Signed-in backup and synchronisation send planner information to Supabase, including saved notes, exercise entries and planner settings. Local features can work offline; online interpretation, account services, shared updates and cloud synchronisation need a connection. Changes on another device must reach this phone before its local reminders can be updated. Shared-calendar refreshes operate while the app is open; this is not a promise of continuous background synchronisation.

Sign-out retains a separate local account planner cache. Uninstalling is not an account-deletion request. Reminder preferences are not included in planner cloud backups.

Voice and AI planning

When you choose voice input, AZLO uses the speech-recognition service available on your device. AZLO does not require recognition to occur entirely on-device: the selected speech service may process audio remotely under its own practices. AZLO's planning integration does not separately upload or archive microphone recordings. Typed and manual input are alternatives.

Some requests are interpreted locally. Others send request text and clarification answers to AZLO's Expo-hosted interpretation service, which uses OpenAI. Context can include the local date and timezone, current shift, workflow and roster pattern, commute time, up to 15 days of shift details and up to 80 selected plans with titles, dates, times and repeat patterns. The context builder does not send the complete notes or exercise-log collections. Information you speak, type or place in a plan title can nevertheless be included. Microphone audio is not sent to OpenAI by this interpretation route.

AZLO's API request uses OpenAI's store:false option. OpenAI data-sharing options were disabled in the account settings inspected. API content is therefore not opted into model training through those controls. This does not mean zero retention: OpenAI's standard abuse-monitoring logs may contain content and metadata and are generally retained for up to 30 days, with legal and safety exceptions under its published rules. AZLO has not verified an approved Zero Data Retention arrangement.

Transcripts appear during planning interactions. Saving a request as a note, or saving a plan containing its wording, stores that content as planner information and can include it in cloud backup.

Shared calendars

Joining does not automatically share your private roster or all personal plans. Joint plans added to the shared calendar are visible and editable by its members. Individually shared personal plans are viewable by the partner while their owner keeps editing control.

Leaving stops individual personal-plan sharing; the original personal plan remains with its owner. Deleting a joining partner’s account leaves the owner’s calendar and joint plans with the remaining owner, with the deleted author’s account reference cleared. Deleting the calendar owner’s account removes that shared calendar and its joint plans. Personal-plan sharing records are cleared when membership changes. These joint plans differ from private plans that are only made visible to a partner.

Copies another person independently saves, exports or screenshots cannot be withdrawn by deleting your account.

Providers

The app uses Supabase for authentication and database services; Expo for app delivery, updates and the hosted interpretation endpoint; OpenAI for online text interpretation; Resend for sign-in email delivery; and device speech and notification services. RevenueCat and Apple or Google process subscriptions when billing is enabled. RevenueCat's integration uses the AZLO account identifier and purchase/entitlement information. Payment-card entry is handled by the store checkout, not AZLO's planner form. Google Workspace is used for business/support email.

Provider infrastructure and SDKs can generate operational records, including records used for security, service delivery and troubleshooting.

Technical records

AZLO’s hosting service records technical information about requests, including route, timestamp, response status, deployment, operating system, approximate request location, duration and request identifier. AZLO’s deployed interpretation and account-deletion code does not explicitly write planning-request text or request bodies to application logs. Hosting providers may separately retain operational and security records.

Account-linked voice-usage records contain an account identifier, date, request count and last-request timestamp. AZLO also maintains global usage totals. Authentication, email and subscription providers may retain records needed to operate and secure their services. Provider retention is explained under “Retention and account deletion”.

Processing locations

The primary Supabase database project inspected is in Sydney, Australia (ap-southeast-2). That does not establish Australian-only processing for authentication, hosting, backups, support, speech or purchases. Resend's published information states stored data is in the United States. Other providers may process information outside Australia, including in the United States. Expo hosting uses Cloudflare’s global network. Processing locations can depend on the service and the device speech provider.

Security

AZLO uses account authentication and access controls. Native authentication sessions use Expo SecureStore. Planner caches use ordinary app storage without an additional AZLO encryption layer. The interpretation service uses HTTPS. Keep your device and account secure. No device or online service can be guaranteed completely secure.

Retention and account deletion

Account and planner records support the service while your account is active. In-app deletion is at You → Account → Delete account. Complete the fresh email verification and confirmation shown. A successful request deletes the authentication account and its private cloud-backup record. Matching account-linked voice-usage records are also removed by the account-deletion database process.

After a successful response, AZLO attempts to clear the current account's main planner cache, named recovery copies, reminder preferences and widget on that device, and cancel its scheduled reminders. If local cleanup reports a failure, follow the app's retry instructions. This does not remotely erase local copies on other devices. Shared-calendar consequences are explained above.

When you delete your account through the app, AZLO automatically requests deletion of the associated RevenueCat customer record before deleting your sign-in account. RevenueCat processes accepted deletion requests asynchronously. If the cleanup request fails, AZLO does not complete account deletion and asks you to retry or contact support@azlo.com.au. Email-assisted deletion includes this cleanup as a support step. Store transactions, support correspondence and provider logs are not all erased by deleting the authentication account. Deleting an AZLO account does not cancel an Apple or Google subscription.

OpenAI's applicable monitoring retention is described above. Resend publishes 30-day email/log retention for its Free, Pro and Scale plans and seven-day backup persistence. Its separate 90-day period following termination of a Resend customer account is not the deletion period for an AZLO user. The Supabase Free-plan dashboard inspected does not include project backups, which is not proof that the provider retains no operational copies. Provider operational records may remain after account deletion under the provider’s retention practices or applicable legal requirements. Support correspondence is handled separately from planner-account deletion. Contact us about deletion of support correspondence; we may need to retain records to resolve a complaint or meet legal obligations.

Requests, correction and complaints

Contact support@azlo.com.au to ask about access, correction, privacy or deletion, using your AZLO account email. Do not send a password or sign-in code. Identity checks protect your account. You can request account deletion by email without opening the app. We will verify your identity and ask you to confirm permanent deletion before acting. If you cannot access your registered email, contact us to discuss other verification. Contact us first about privacy concerns; information about Australia's privacy regulator is at https://www.oaic.gov.au.

Updates

We will publish revisions on our website with an updated date and provide additional notice where appropriate.