Privacy Policy

(ABN ) publishes Section Manager. We are bound by the Australian Privacy Principles in the Privacy Act 1988 (Cth).

Section Manager's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The permissions it requests

• documents.currentonly — read and modify only the Google Docs document the add-on is currently open in. This does not grant access to any other file in your Google Drive, and the add-on cannot list, search or open your other documents.
• script.container.ui — display the add-on's own sidebar inside the document.
• script.scriptapp — create and remove the trigger that lets the sidebar open automatically when you open a document. You can turn this off in the add-on's settings.
• script.external_request — make outbound HTTPS requests. Used for a single endpoint: our own licence server, to check or activate a Pro licence key, to claim or release a seat, and to read or write organisation-wide settings on a Pro licence. It is never used to send document content, and on the free tier it is never used at all.

The add-on does not request the general Google Drive permission, and it deliberately avoids any function that would require it.

What we do not do

• We do not transmit your document content anywhere. Our licence server never receives any part of your documents, and there is no database of them.
• We do not read your documents. No person at can see them through the add-on.
• We do not use Google user data for advertising, and we do not sell it.
• We do not use Google user data to develop, improve or train machine learning models.
• We do not create accounts. The add-on never reads your Google account’s email address; the only way we hold an email is if you type one into the optional label field when activating a licence, or write to us.

With one exception — the licence record described below — everything the add-on saves is held by Google, inside your own account, using Apps Script's Properties Service:

• Document properties — the index of sections in that document; the History of sections you have deleted from it (including their text and formatting so they can be restored); any custom tag types you have defined for that document and which tag each section carries; and whether automatic numbering is on and how deep it goes. All of this is stored with the document itself, which is why a colleague who opens the same file sees the same tags.
• User properties — your own preferences and your own content: whether the sidebar opens automatically, dark mode, any custom heading and button colours, compact view, sort order, your chosen History depth, which sections you have collapsed, whether you have seen the latest update note and whether you have completed the guided tour; plus your saved section templates, which is why they are available to you in every document and are not visible to anyone else who opens the same file.

None of this reaches us. Deleting the document deletes its stored sections, tags and History along with it; uninstalling the add-on revokes its access.

Licence checks — the one thing that does leave your account

If you buy Pro, the add-on talks to our licence server so it knows whether your key is valid. This happens when you activate a key, and again each time the sidebar opens. Each request contains:

• The licence key you were issued.
• An installation identifier — a random value the add-on generates for itself the first time it needs one. It is not derived from your name, your email or your Google account, and it tells us only that two requests came from the same installation. It is what stops one key being shared across unlimited accounts.
• An optional label — whatever you type into the "your name or email" box when activating. It is never verified, never required, and exists only so you or whoever manages your team's seats can tell one seat from another later. If you type an email address here, we hold that email address.

On a Pro licence covering more than one seat, the same record is what lets whoever manages the licence see which seats are in use, under the labels their holders typed, and release a seat when someone leaves.

Organisation settings — the other thing we hold

Pro licences can define settings once and have every seat inherit them: the organisation's tag types and the defaults new documents start from. Because those have to reach seats that have never met each other, they are stored on our licence server against your licence rather than in any one document.

They contain what an administrator typed into the settings panel — tag names and preference values. They do not contain document content, document names, heading text, or any list of which documents your organisation has. If you never buy Pro, none of this exists for you.

No document content, document name, heading text or Google account identifier is included in these requests. If the licence server cannot be reached, the add-on carries on with whatever status it already had rather than locking you out.

If you use the contact form or email us, we receive your name, email address and whatever you write. We use it to answer you, and for nothing else. We do not add you to a mailing list.

This website has no user accounts and takes no payments. Pro subscriptions are bought through Stripe’s own hosted checkout — your card details go to Stripe, never to us, and never through this site or the add-on.

We do not sell personal information and we do not disclose it for anyone's marketing. The only third parties involved are:

• Google — the platform the add-on runs on and where its data is stored.
• Our email provider — for correspondence you send us.
• Stripe — payment processing for Pro subscriptions. Stripe receives your payment and billing details directly; we receive confirmation that a subscription exists, not your card details.

We may disclose information where required by law.

Your document content never reaches our infrastructure at all, so it is protected by Google's own security rather than ours. The licence records we do hold — keys, installation identifiers and any optional labels — sit in the Apps Script project that serves them, reachable only with a shared secret that is not present in the add-on’s published code. For the correspondence we do hold, we use access controls and the principle of least privilege. If a data breach were likely to cause serious harm, we would notify affected people and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme.

• Section index, tags, templates, History and preferences — held in your Google account for as long as you keep the document or the add-on. History is capped at 40 sections per document on the free tier, or at whatever you set between 5 and 200 on Pro; older entries are removed automatically.
• Licence records, including seat labels — for as long as the licence exists, and for up to 12 months after it ends so that a renewal or a billing query can be answered. Ask us and we will delete a lapsed record sooner.
• Organisation settings — until the licence ends or you clear them, then deleted with the licence record.
• Support correspondence — up to 24 months.

You can ask us to access, correct or delete the personal information we hold about you — in practice, your correspondence, since that is all we have. You can revoke the add-on's access at any time through your Google account's third-party access settings, or by uninstalling it.

To make a request, email . We respond within 30 days. If you are unhappy with how we handle a privacy matter, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

This site sets no cookies and runs no analytics or tracking. The add-on sets no cookies and does not track usage.

Section Manager is intended for adults working with documents. We do not knowingly collect personal information from children under 13.

We will post changes to this policy on this page and update the date above. Privacy enquiries: , or write to , .