InlineScan Privacy Statement
Version: 2026-11-18
1. Who this covers
This statement explains how Inline Code Pty Ltd, ABN 16 639 203 259 ("we", "us") handles personal information in InlineScan, the app at app.inlinecode.com.au. It goes with the InlineScan Terms of Service of the same version. We are a small business, so the Privacy Act 1988 (Cth) may not apply to us by law. We choose to handle personal information as the Australian Privacy Principles set out, and we promise that to our customers in the terms. Our postal address is 1506/56 Scarborough Street, Southport QLD 4215 and our email is mathew@inlinecode.com.au.
Our website at inlinecode.com.au has its own privacy notice at /privacy, which covers the website, forms, newsletters and analytics. The app does not use the website's analytics or advertising tools. It sets only the cookies needed to sign you in and keep you signed in, including cookies set by our sign-in provider. If the two documents differ about the app, this statement applies to the app.
2. Who is responsible for what
Your organisation decides what it gives us: its staff's sign-in details, its cloud and system configuration, and any evidence it uploads in an incident. Evidence can contain information about third parties, and sometimes sensitive information such as health or financial details. Your organisation promises in the terms that it has the right to give us that information and has given any notice or obtained any consent the law requires. We are responsible for protecting what we hold, for the other matters in this statement, and for answering people who ask us about their own information.
3. What we collect, why, where and for how long
| What | Why | Where | How long |
|---|---|---|---|
| Sign-in profile: name, work email, the sign-in provider's identifier for you, your role, first and last seen | To sign you in and decide what you may do | AWS Sydney; Auth0 (Okta) Australian tenant | While your account is open and 90 days after |
| Audit record: what you did, when, and the network address it came from | Security and accountability | AWS Sydney | 7 years |
| Acceptance record: terms and statement versions, who accepted, when, network address and browser | To show what was agreed | AWS Sydney | 7 years |
| Results and uploads: scan files, observations, configuration findings from connected accounts, reports. These can name people, for example a user list. Names, email addresses and directory ids are replaced before storing, where the provider's rules say so | To provide the service you asked for | AWS Sydney | While your account is open and 90 days after |
| Connection and consent records: who connected an account, when, and its state | To show what access you granted | AWS Sydney | 7 years |
| AI endpoint test replies | To report on the test | AWS Sydney | With your results; an approver can delete a run's replies |
| Digital CISO conversations | To answer your questions from your register | AWS Sydney; AI model in Sydney or Melbourne | 30 days, then up to 7 more in backups |
| Incident evidence you upload: samples and attachments | To investigate the incident you asked us to | AWS Sydney | 30 days after the case closes |
| Other incident evidence and log snapshots | Same | AWS Sydney | 90 days after the case closes |
| Incident reports, findings and the custody log (hashes and actions, no evidence content) | To record our work and what we told you | AWS Sydney | While your account is open and 90 days after |
| Domain preview on the sign-in page: a one-way hash of the domain and result; a one-way hash of your network address | To show a preview and limit its use | AWS Sydney | 24 hours; 25 hours |
| Billing details: the work email of the person who subscribed, the organisation's legal name and ABN, the plan, and invoices we raise ourselves. Stripe alone holds the billing address and the card details, and issues a subscription's invoices; the card details never reach us | To bill you and keep tax records | AWS Sydney; Stripe | 5 years, because tax law requires records |
| Support emails to us | To answer you | Google Workspace | 2 years after the last message |
| Application logs | To run and secure the service | AWS Sydney | 30 days |
| Database backups | To recover from failure | AWS Sydney | 7 days |
A hold placed by a consultant on an incident case stops its evidence deletion clock until the hold is lifted, and we review each hold at least every 90 days. Where we delete by hand, we do it normally within 30 days after the period ends. Deleted data can remain in backups for up to 7 more days.
4. How we use and share it
We use personal information to run the service for your organisation, keep it secure, support you, bill you, meet our legal duties and improve the service. We do not sell it, rent it or use it for advertising. We share it only with: the providers in section 5 and the providers they use; contractors who work for us under a duty of confidence; our professional advisers and insurers where we need to, for example to notify a claim; people you tell us to share it with; a buyer of our business, under a duty of confidence; and anyone the law requires or allows us to give it to, such as a court, regulator or police. Reports you share by link can be revoked by you and expire.
5. Providers and where they process data
| Provider | What it does | Where |
|---|---|---|
| Amazon Web Services | Hosts the app, database, storage, evidence and logs | Sydney (ap-southeast-2) |
| Amazon Simple Email Service (SES) | Sends the app's emails to you, such as a welcome or a failed payment. Receives your email address and the message | Sydney (ap-southeast-2) |
| Amazon Bedrock, running Anthropic Claude models | AI narration, Digital CISO, incident drafting and checking | Sydney and Melbourne (ap-southeast-4). Your inputs are not used to train the models |
| Auth0, operated by Okta | Sign-in, using your Google or Microsoft identity | Australian tenant. Okta staff may reach it for support from the United States and other countries Okta lists |
| Google and Microsoft | Your own sign-in provider. We receive your name, email address and identifier | Under their terms and privacy policies |
| Stripe | Takes subscription payments by card on its own page, and issues invoices. Receives the subscriber's name and email, the organisation's name, ABN and billing address, and the card details, which we never see | Australia and overseas, including the United States |
| Google Workspace | Our email, which holds your messages to us | Australia, the United States and other countries where Google operates |
| crt.sh, run by Sectigo | Public certificate lookups. Receives a domain name, not a person | Overseas |
| Have I Been Pwned | Breach lookups by domain. Switched off today. Would receive a domain name only | Overseas |
Where we disclose personal information to a provider overseas, we take reasonable steps so that it handles the information consistently with the Australian Privacy Principles. The table above names those providers, and we update it when it changes.
6. AI and automated decisions
Models write narration, Digital CISO answers and drafts. No computer program alone makes a decision that could significantly affect a person's rights or interests. In incident work, a model reads evidence, which can include names, email addresses, account activity and message content, and drafts findings. A draft can concern what a person did, for example whether an account was misused. That drafting is directly related to a decision, but the decision is made by our named consultant, who checks the evidence and releases, changes or rejects each finding, and then by your organisation, which decides what to do. Some service controls run automatically, such as rate limits, a monthly allowance, and stopping a scan when proof of domain control lapses. They concern an organisation's use of the service, and you can ask us for a person to review one.
Digital CISO is built to remove email addresses, phone numbers, tax file numbers, ABNs, Medicare numbers and card numbers before a message goes to the model. The filter works on patterns and can miss some, and other names and free text go as written, so leave out personal details you do not need. Models can be wrong, so check what they tell you.
7. Security and incidents
We protect personal information with access controls scoped to each customer organisation, encryption, logging and the other safeguards the service is built around. If we suspect an eligible data breach on our side, we assess it quickly and, where the Notifiable Data Breaches scheme requires, tell the Office of the Australian Information Commissioner and affected people. We tell your organisation as the terms say. If the scheme does not apply to us, we still tell your organisation as the terms say. Your organisation tells its own people about incidents in its own systems.
8. Your rights and complaints
You can ask for access to, or correction of, personal information we hold about you. Email mathew@inlinecode.com.au and we aim to respond within 30 days. We do not charge you to make a request. We may need to confirm who you are. If your information is in a customer's data, we may involve that customer, and we still answer you. If we refuse, we tell you why and how to complain.
If you think we have breached the Australian Privacy Principles, tell us first at the same address. If the Privacy Act applies to your complaint, you can also complain to the Office of the Australian Information Commissioner at oaic.gov.au.
9. Children
InlineScan is for business use by adults. We do not knowingly collect information from children. If you think we have, tell us and we will delete it.
10. Changes
We update this statement when what we do changes, and it carries a version. Where a change matters, we ask each user to acknowledge the new version at sign-in, as the terms say.
11. Contact
Inline Code Pty Ltd, mathew@inlinecode.com.au.