Loggit privacy policy

This policy explains what Loggit collects, why, where it is kept, who else handles it, and what you can ask us to do with it. It follows the Australian Privacy Principles (APPs) in the Privacy Act 1988 (Cth).

Loggit is run by Kevin Axelsen (ABN 18 842 815 279), trading as Loggit, in Queensland. In this policy “we” means that business.

Who this is for

  • Support workers and small NDIS providers who use Loggit to log shifts, write notes, send agreements and invoice.
  • NDIS participants, their families, nominees, representatives and plan managers, whose details a provider keeps in Loggit.

If you are a participant or family member, the provider you work with decides what to record about you in Loggit. They are responsible for their own privacy obligations to you; we hold the records for them and protect them as described here. You can ask either the provider or us about your information (see Access and correction).

In short

  • Client records are health-adjacent personal information. The database, uploaded files and backups are kept in Sydney.
  • Progress notes are never sent to any outside service other than our Sydney hosting (not to email, SMS, push, billing or accounting providers), unless the business turns on cloud AI. Then note text and recordings go to Google’s AI service in Sydney to be drafted, and stay in Australia (see Notes and AI).
  • Some services we use are overseas. Each gets only what it needs for its job, listed in the table.
  • Note drafting runs on your device by default. Cloud AI is off unless the business’s owner turns it on.

What we collect and why

Accounts (everyone who signs in)

What Why
Name, and an email address or mobile number To sign you in (we send a one-time code) and to contact you about your account
Apple or Google account identifier, and the verified email Apple or Google gives us Only if you choose Sign in with Apple or Google
Passkeys (Touch ID, Face ID, Windows Hello): the public key and the browser’s label, e.g. “Touch ID on Jess’s MacBook” To sign in on the website. The private part never leaves your device
One-time sign-in codes, stored only as a hash, and sign-in sessions, stored only as a hash To sign you in and keep you signed in
Each signed-in device: the kind of device and browser (e.g. “Chrome on Mac”, “iPhone app”), when it signed in and when it was last used. No IP addresses So you can see where you’re signed in and sign out a lost device, and (compliance mode) to sign the website out after an hour without use
Push notification tokens for your phones, which notification topics you turned off for push, and which you turned on by email To send the notifications you asked for

Workers’ details (businesses with a team)

What Why
Role in the business (owner, admin, worker) and home state To decide what each person can see, and which time zone and public holidays apply
Clearances: type (e.g. NDIS worker screening, first aid), number and expiry date So the business can roster only cleared workers and see expiry warnings
Training (businesses using compliance mode): course, provider, the date done and the expiry date So the business can show an auditor its training records, with expiry warnings
Unavailable times, with an optional note For rostering
Rostered shifts, swaps, invites To run the roster

Workers never see rates, invoices, agreements or plan managers.

Business details

Business name, ABN, NDIS registration number, whether registered and GST-registered, state, logo, rates, invoice numbering, agreement template wording, and (if connected) which accounting software and organisation is linked. Accounting connection keys are stored encrypted (AES-256-GCM) and are never sent to the app.

Clients’ details and shift notes

What Why
Client name, NDIS number, funding type (NDIA-managed, plan-managed, self-managed), plan dates To bill correctly and check NDIS price limits
Suburb, street address, other places their shifts often start (for example a day program, with the usual days), state, and remoteness area (MMM) For directions, public holidays and the travel rules. While a street address is typed, Google suggests matching addresses (see the table)
“Quick info” the business writes about the client So workers have what they need on a shift
Other contacts: plan manager, nominee, representative, family; name, role, email, mobile To send agreements and invoices to the right person
Goals and plan goals, and workers’ ratings of progress on them For progress reports and plan reviews
Shifts: date, times, support item, travel, sleepover wake-ups, cancellations and why, expenses To record what was delivered and bill for it
Progress notes: what the worker said or typed, the structured note, goals worked on, an incident flag The record of support. Kept for the business and its records duties
Approved days: a locked copy of each approved day, kept when a day is reopened and approved again So approved records can’t be changed silently
Every change to a shift’s times: old and new value, who and why An audit trail
Compliance registers (businesses using compliance mode): incidents (what happened, when, whether it’s reportable, when the NDIS Commission was told, who else was told, follow-up, closing reason); complaints (who made it, what about, actions, outcome); consent records (the date, who gave it, what they agreed to and the wording version, and any withdrawal); uses of a restrictive practice (what, when, for how long, whether authorised, what happened) Registered providers must keep these registers under the NDIS Practice Standards
Shift sign-off (if the business turns it on for a client): the name of the participant or nominee who signed, a drawn signature if they drew one, and when; or why they couldn’t sign Evidence the support happened as recorded

Clients that are archived or removed stay in the records with their shifts, notes and invoices (see Retention).

Notes on your device. Loggit keeps a copy of your data on your phone so it works offline, and syncs it with our server. Speech to text and note structuring run on the device by default. Where the device can’t do it (for example in some browsers), the business’s owner can turn on cloud AI. Then the note text, or the voice recording once you stop recording, is sent to Google Cloud’s Vertex AI in Sydney (the australia-southeast1 region) to be drafted. Names are not removed first. Loggit uses Google’s Sydney regional service only, never its global or multi-region services, so the processing happens in Australia. Google processes it under its Google Cloud terms, only to answer Loggit, and those terms don’t let Google use it to train its models. Loggit doesn’t keep the recordings. Turning cloud AI on is the owner’s choice, made in Settings after reading what it means, and Loggit records who turned it on, when, and which wording they agreed to. Each person has a monthly cloud AI allowance; Loggit counts the minutes of voice and the number of drafts each person uses, never what they said.

No decisions made by computer. Loggit doesn’t make decisions about anyone automatically. AI drafts notes and reads details from uploaded documents, and Loggit’s checks flag things such as a note that may describe an incident, a price over the NDIS limit or an expired clearance. A person reads, changes and saves every note, agreement and invoice, and decides what to do about any flag.

Agreements and signatures

What Why
The service agreement as sent: business, participant and provider details, rates, schedule, sections, start and end To agree services and prices
Uploaded agreement files (PDF or photo) Owners can upload an agreement already signed on paper. PDFs are read on our Sydney server, so their text doesn’t leave Australia
Signing record: who the link was sent to (name, email, and mobile for a texted link), how it went (email, in person, or SMS), when it was opened, for in person the name and email of the provider’s person who confirmed the signer, a one-time code for texted links (hash only), the signer’s name, role, drawn signature, consent and authority times, IP address, browser, and a SHA-256 fingerprint of the document seen Evidence of who signed what, and when
Change requests the signer types Sent to the business so they can change the agreement

The signing link is stored only as a hash and works for 7 days (2 hours when opened in person on the provider’s device). An emailed link is how the signer is identified, so it is meant for them only. A texted code (for businesses with texts on) is bound to the browser that entered it.

Invoices

Invoice number, period, who it is billed to (the NDIA, the plan manager or the participant) and the plan manager’s email, lines (date, description, support item number, quantity, rate, total) and status. Credit notes the same. Loggit also makes NDIA bulk claim files you download.

When a business emails an invoice from Loggit, we keep the address it went to, who sent it, when, and when the link was first opened. The email holds a link, not the invoice: the link is stored only as a hash, opens that one invoice and its PDF with no sign-in, and stops working if the invoice is voided. Anyone holding the link can open it, so it is meant for the person it was sent to and their organisation.

Receipts and expenses

Amount, category, description, whether billable, and a photo of the receipt. Receipt photos are stored in the private Sydney file store and opened only through short-lived signed links.

Billing for Loggit itself

Plan, seats, add-ons and subscription status. Payment card details are entered on Stripe’s own pages and kept by Stripe; Loggit never sees or stores card numbers. Loggit gives Stripe the business name and Loggit’s id for the business.

Records we keep for safety and support

  • Audit log: who did what and when (approvals, reopenings, price overrides, changes to shift times, rates and settings, team changes including who the owners are, two-step sign-in being turned on, off or reset, devices signed out, signatures with IP address, records exports, every change to the compliance registers, shift sign-offs, audit packs made, invoices made, addenda to notes with their reason, and compliance mode being turned on, paused or off with the reason). Once a business has turned on compliance mode, each entry carries a fingerprint of the one before, so a changed or deleted entry shows.
  • Notifications: the text of each notification we sent you, so you can see it in the app.
  • Terms of Service agreement: which version of the terms a business agreed to, when, and which owner agreed.
  • Text message count and limits: see SMS counting and limits.
  • Cloud AI use: per person per month, the minutes of voice notes and the number of cloud drafts, and Loggit’s estimated spend on cloud AI per month. Counts and dollars only, never note text, recordings or names.
  • Server logs: method, path and status of each request. Outside development they leave out query strings, mask signing-link tokens and drop error messages, so they hold no client names or notes.

We don’t use your information for advertising and we don’t sell it.

Where your information is kept

What Where
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 website Cloudflare Pages. The website holds no data; it is the app’s code, served from Cloudflare’s network
Your devices A 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 data

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.

Who What they receive Where Why Source (read)
Supabase The whole database and files (Sydney); its own account, support, telemetry and logs overseas (above) Sydney; logs in the EU; other processing outside the region Database and file hosting Data residency FAQ, v1 6 Oct 2026 (3 Nov 2026)
Fly.io Runs the Loggit server, so all data passes through it in memory; the nightly backups Sydney Server and backups apps/api/fly.toml, infra/fly/backup
Stripe The business name and Loggit’s id for it; card and billing contact details the owner enters on Stripe’s pages Mostly the USA; also India, Ireland, Australia and others; Stripe’s Irish entity is responsible outside the Americas Billing for Loggit’s subscription (website only) Sub-processors list, updated 27 Sep 2026 (3 Nov 2026)
Apple, Google (sign-in) You sign in on their page; they confirm to us an account identifier and verified email USA (their own services) Sign in with Apple / Google, only if you choose it Apple, Google
Resend Email 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 attachments Its sub-processors are all listed in the USA (including AWS for hosting and sending) Email Sub-processors, updated 27 Aug 2026 (3 Nov 2026)
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 only Message 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 Sub-processors, no date on page (3 Nov 2026)
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 notes Xero: 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 statement Accounting sync Xero sub-processors, no date on page (3 Nov 2026); Intuit privacy statement
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 reasons Expo: USA; Expo lists Apple and Google (USA) for push delivery Push notifications Expo sub-processors, updated 19 Oct 2026 (3 Nov 2026)
Cloudflare Serves the website’s code and runs the 8am/6pm scheduled jobs, which only call the Loggit server; holds no client data Cloudflare’s global network Website and scheduled jobs docs/HOSTING.md; Cloudflare privacy policy
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 Loggit Sydney (australia-southeast1): Loggit calls Google’s Sydney regional service only Cloud AI apps/api/src/ai/vertex.ts, ADR 0003
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 typing Google’s own services, not limited to Australia Address suggestions apps/api/src/places/google.ts; Google privacy policy

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.

SMS counting and limits

Loggit keeps a count of texts sent per business per month (for pricing decisions). It never keeps the message text. Sign-in codes are counted under “none”, not under a business. The count stays even if a business is deleted.

To stop text messages being misused (for example someone sending large numbers of texts to numbers they control), Loggit limits how many texts go to the same mobile and how many different mobiles a business texts. For that it keeps, for 48 hours only, a record of each text sent and each wrong signing code: the business, the time, and a keyed hash of the mobile number (a one-way code made with a secret key held only on Loggit’s server), never the number itself. The records are deleted after 48 hours.

With the server’s secret key a hash could be matched to a number by trying every mobile number, so it is treated as personal information and kept no longer than the limits need.

How long we keep it

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 deletion

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.

Access and correction

You can ask for a copy of the personal information we hold about you, and ask us to correct it (APPs 12 and 13). Owners and admins can correct most details in Loggit directly. If you are a participant or family member, you can also ask the provider.

We will reply within 30 days, and tell you why if we can’t do what you ask.

Security

  • 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.

Contact us

Email support@loggit.com.au. Loggit is run by Kevin Axelsen (ABN 18 842 815 279), Queensland.

Complaints

Contact us first and we will reply within 30 days. If you’re not satisfied, you can complain to the Office of the Australian Information Commissioner (OAIC): oaic.gov.au, phone 1300 363 992. For a complaint about the care or support a provider gives you, contact the provider, or the NDIS Quality and Safeguards Commission (ndiscommission.gov.au).

Changes to this policy

We will post changes on this page with a new date. For significant changes we will also tell business owners in Loggit and by email at least 30 days before they take effect.

Last updated: 15 November 2026.