Security

Your clients’ records, kept in Australia.

What Loggit does to keep NDIS records safe, where they live and who else handles them. The detail below is our privacy policy’s own wording.

  • Kept in Sydney

    Client records, notes, files and backups stay in Sydney.

  • Drafted on your phone

    Notes are drafted on your phone. Cloud drafting, if you turn it on, stays in Australia.

  • Each role sees its own

    Workers only see their own clients. Never rates or invoices.

  • On the record

    Every price override, change to shift times and approval is on the record, in the audit trail.

  • Kept for 7 years

    Built around NDIS record-keeping: 7-year retention, export any time.

  • Two-step sign-in

    Anyone can add a passkey, phone unlock or authenticator app after the email code. Owners can require it of their workers.

Where data is kept

WhatWhere
Database (everything above)Supabase, Sydney (AWS ap-southeast-2). Encrypted at rest; connections use TLS checked against Supabase's certificate
Files (receipts, uploaded and signed agreements, logos)Supabase Storage, Sydney, a private bucket. Signed links only
Backups (production)A nightly database copy on a Fly.io volume in Sydney, kept 14 days
The Loggit server (API)Fly.io, Sydney
The websiteCloudflare Pages. The website holds no data; it is the app's code, served from Cloudflare's network
Your devicesA local copy on your phone or browser, for offline use

Supabase also processes some data overseas. Supabase's Data Residency and Transfers FAQ (Version 1, 6 Oct 2026, read 3 Nov 2026) says the database, Storage objects and backups stay in the chosen region, but four kinds of data are processed outside it: customer account information (setup, configuration and billing), customer support requests, usage information ("telemetry, logs, and service metadata", excluding application data), and content delivery (Storage content may be cached on a global network, depending on configuration). It says logs are stored in EU-based data centres. Loggit's files are opened only through short-lived signed links.

Fly.io handles the server's logs and machine metrics under its own terms, and may process them outside Australia. The logs hold no client names or notes (see "Server logs" above).

Who else handles it

These services process data for Loggit. Each gets only what it needs. None of them receives progress notes, except Google's Sydney AI service when a business turns cloud AI on. Locations are from each provider's own page, read on the date shown; a provider's entity location is not always where data is stored.

WhoWhat they receiveWhereWhy
SupabaseThe whole database and files (Sydney); its own account, support, telemetry and logs overseas (above)Sydney; logs in the EU; other processing outside the regionDatabase and file hosting
Fly.ioRuns the Loggit server, so all data passes through it in memory; the nightly backupsSydneyServer and backups
StripeThe business name and Loggit's id for it; card and billing contact details the owner enters on Stripe's pagesMostly the USA; also India, Ireland, Australia and others; Stripe's Irish entity is responsible outside the AmericasBilling for Loggit's subscription (website only)
Apple, Google (sign-in)You sign in on their page; they confirm to us an account identifier and verified emailUSA (their own services)Sign in with Apple / Google, only if you choose it
ResendEmail address, subject and text of: sign-in codes, invites (business name), signing links (business, client and signer names), "signed" and change-request emails (client name, and the signer's message for a change request), billing emails (business name), compliance mode changes to owners and admins (staff names and times, never the reason), overdue incident deadlines to owners and admins (the incident's number only, never the client), invoices emailed from Loggit (business name, invoice number, amount, due date and the link; not the participant's name), and notifications a person chose to get by email (the same text as the push: worker first names, dates and times, never client names). No attachmentsIts sub-processors are all listed in the USA (including AWS for hosting and sending)Email
ClickSend (only for businesses that have text messages turned on)Mobile number and text of: signers' codes and signing links (which name the business and the client). Codes and links only, never notes. Sign-in and invites are by email onlyMessage content on AWS in Australia, deleted after 120 days; Datadog in North America (debugging and monitoring); Sinch group entities in the EU, USA, Philippines and Australia (provisioning, support, development)SMS
Xero or Intuit (QuickBooks)Only if the business connects one: invoices and credit notes: bill-to name (the participant, the plan manager or "NDIA"), the plan manager's email, line descriptions with dates and support item numbers, amounts, and a tag of either the funding type or the worker's name if the business chooses that. If the business chooses to send an invoice through Xero or QuickBooks, that service emails it to the bill-to email under its own terms (Xero approves a draft first). Not notesXero: its hosting providers (AWS, Google Cloud, Azure, Snowflake and others) are US entities, with Xero affiliates in NZ, Australia and elsewhere; the page doesn't say where data is stored. Intuit: overseas, under Intuit's own privacy statementAccounting sync
Expo, then Apple (APNs) and Google (FCM)Push tokens and notification text: worker first names, dates and times, shift counts, invoice numbers, agreement version numbers, incident numbers. Never client names or notes. See the note below about reasonsExpo: USA; Expo lists Apple and Google (USA) for push deliveryPush notifications
CloudflareServes the website's code and runs the 8am/6pm scheduled jobs, which only call the Loggit server; holds no client dataCloudflare's global networkWebsite and scheduled jobs
Google Cloud (Vertex AI) (only if a business turns cloud AI on)Note text, voice recordings and agreement text sent to be drafted or read, with names left in. Not kept by LoggitSydney (australia-southeast1): Loggit calls Google's Sydney regional service onlyCloud AI
Google Maps Platform (Places)Only the street address an owner or admin types into a client's address box, as they type it, and which suggestion they pick, sent from Loggit's server. Never the client's name or anything else about them, and not who is typingGoogle's own services, not limited to AustraliaAddress suggestions

About days sent back or reopened. The reason an owner or admin types is shown only inside Loggit. The push itself says only the date and to open Loggit, so a typed reason never goes through Apple or Google.

Overseas disclosure (APP 8)

Because of the services above, some personal information is disclosed to recipients in the USA, the EU (including Ireland and Sweden), the Philippines, India, New Zealand and other countries where these providers operate. We choose services that receive only what they need, and we keep client notes, agreements, receipts and voice recordings in Australia, including when a business turns on cloud AI (Google's Sydney region). By using these features you agree to these disclosures; the overseas recipients aren't bound by the Australian Privacy Principles.

Encryption, sign-in and the breach plan

  • Data is encrypted in transit (TLS) and at rest.
  • Sign-in uses one-time codes (rate-limited), Apple or Google, or passkeys, and the app can lock with Face ID, Touch ID or a fingerprint.
  • Anyone can turn on two-step sign-in, and owners can require it of their workers: after the code (or Apple or Google), Loggit also asks for a passkey, phone unlock (Face ID or a fingerprint on their phone), a code from an authenticator app, or a one-time recovery code. Recovery codes and phone unlock keys are stored only as hashes, and an authenticator app’s secret is stored encrypted. An owner can reset a team member’s two-step sign-in (an admin can reset a worker’s): they are signed out of every device and emailed. Someone who has lost their phone and their recovery codes can ask Loggit to clear it: we email them and Loggit support at once, they can cancel by signing in with a second step, and it clears after 72 hours. In compliance mode it’s required of owners and admins, the website signs out after an hour without use or 24 hours after signing in, and the phone app asks for Face ID, a fingerprint or the passcode after an hour in the background.
  • Anyone can see where they're signed in and sign out a lost device (Settings › Signed-in devices); owners and admins can sign a team member out of every device.
  • Every records export is written to the business's audit trail.
  • Every action is checked on the server by role; workers never see rates, invoices or plan managers.
  • Files are in a private bucket and opened only through short-lived signed links.
  • Codes, links and sessions are stored only as hashes.

If we have a data breach likely to cause serious harm, we will notify the people affected and the OAIC as the Notifiable Data Breaches scheme requires. Our plan: within 72 hours of learning of a possible breach we assess it, contain it, and tell the businesses affected; if serious harm is likely, we notify the OAIC and the people affected as soon as we can.

Roles and the audit trail

  • Three roles: owner, admin and support worker. The server checks the role on every change, whatever the app shows.
  • Workers see only the clients they’re assigned to, and never rates, invoices or plan managers.
  • The audit trail records approvals and reopened days, price overrides, changes to shift times, rates and settings, signatures and every records export. Owners download it with their records.

Keeping records

What the code does today:

  • Nothing is deleted on a timer. Removing a client, shift or note marks it removed; archiving a client keeps their records. Approved days, signed agreements and invoices are never edited, and each approved version is kept.
  • Signing links last 7 days; signing codes expire after 10 minutes; passkey challenges after 5 minutes.
  • Hashed mobile numbers kept for the SMS limits are deleted after 48 hours.
  • Production backups are kept 14 days, then overwritten.
  • ClickSend deletes message content after 120 days (its own page). Other providers keep data under their own terms.

How long we keep it from here on:

  • Client records, notes, agreements and invoices: while the business has a Loggit account, then 7 years after the account closes (NDIS providers have their own record-keeping duties), then deleted.
  • Sign-in codes and sessions: removed once they expire or you sign out.
  • Audit logs: 7 years.
  • Backups: overwritten after 14 days, so deleted data leaves the backups within 14 days.

Export and closed businesses

A business's owners (it can have several) can each export all its records at any time in one file (Settings › Export records): clients, shifts, progress notes and incident reports, service agreements (with their signing record and the signed or uploaded copy), invoices and credit notes, and the audit trail, as CSV and PDF. With compliance mode, owners can also make an audit pack for an auditor: every register, agreements, the notes they choose, the screening and training list and the audit log. Invoices, plan review reports and NDIA bulk claim files can also be downloaded one by one. This works when the subscription is read-only too.

Delete your account in Loggit: Settings › Delete account, on the phone app or the website. We send a code to your email to confirm it is you. Then:

  • Your sign-in details go: email address, mobile number, Apple and Google links, passkeys, notification choices, push tokens, the notifications Loggit sent you and your availability. You are signed out everywhere. We keep only a one-way code made from your email (or mobile), which can't be turned back into the address, so we can check that a later request for records comes from the same address.
  • If you work for a business, you leave it. Your name stays on the shifts and notes you wrote, because the business must keep those records.
  • If you own a business that has another owner, you simply leave it and the other owners carry on; they are emailed that you left. If you are its only owner, you first choose someone in your team to take it over, or close it. Closing it removes everyone's access and cancels the subscription. Download invoices and exports first: as the provider, keeping your records is your duty.
  • Records the business must keep (clients, notes, agreements, invoices and the audit log) are kept for 7 years, then deleted (see Retention). The owner who closed a business can download its records for as long as we keep them, at app.loggit.com.au/records: we send a code to the email address the account had, which proves it's them. If the account used a mobile number, email support@loggit.com.au.

You can also ask for deletion by emailing support@loggit.com.au. We delete what we can within 30 days, and keep only what the law requires us or the business to keep (for example invoices for tax, and records the NDIS requires a provider to keep). If you are a participant or family member, we may refer you to the provider, who decides what they must keep.

Closed your business?

Download its records with a code sent to the email address your account had.

What we don’t claim

There is no NDIS certification for software, so Loggit is not “NDIS approved” or “NDIS compliant”. It warns, keeps a record and keeps data in Australia; your prices, claims, notes and your own privacy duties to participants stay yours as the provider.

Found a security problem? Email support@loggit.com.au. Full detail is in the privacy policy.