Skip to content
Signare home
  • How it works
  • Features
  • Security
  • Resources
  • Cut to the chase
Menu
  • How it works
  • Features
  • For medical practices
  • Security and privacy
  • Resources
  • Cut to the chase
  • About Signare
  • Sign in
Sign in Book a demo
Legal

Privacy policy

Contents

  1. 1. The short version
  2. 2. Personal information we collect
  3. 3. How we use personal information
  4. 4. Google user data: Limited Use
  5. 5. Who we share personal information with
  6. 6. Storage and security
  7. 7. How long we keep information
  8. 8. Cookies
  9. 9. Your choices and rights
  10. 10. Organisations that use Signare
  11. 11. Children
  12. 12. Changes to this Privacy Policy
  13. 13. Contact us and complaints

Terms of service

Effective: 21 November 2026

Signare (ABN 58 175 474 095) ("Signare", "we", "us" or "our") makes software that lets an organisation's staff print a form from their own computer system, have a person sign it on a tablet on the organisation's own network, and save the signed copy back to the organisation's computer. This Privacy Policy explains how we handle personal information through our website signare.com.au, our online portal app.signare.com.au (the "Portal"), the Signare software installed on our customers' computers and tablets (the "Software"), and when you contact us (together, the "Service").

We are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs), and we handle personal information in line with them.

1. The short version

  • Documents and signatures never come to us. Forms, the documents printed through Signare, signatures, consent answers and signed PDFs are kept on our customer's own computers and local network. The Software does not send them to Signare or to any cloud service, and the Portal cannot store, show or retrieve them.
  • The Portal holds account and status information only: who can sign in, the organisation's settings, and the technical status of its Signare computers.
  • If you sign in with Google, we receive only your Google account ID, email address, whether that email is verified, and your name. We use them only to sign you in. We do not sell them, use them for advertising, or share them.
  • Crash reports are sent only if the organisation agrees. They describe a fault in Signare's own software and are cleaned so that they contain no patient, client or document information (section 2.4).
  • We do not use advertising or analytics cookies, and we do not sell personal information.

2. Personal information we collect

2.1 Information you give us

  • Account information: your organisation's name, and for each person with a Portal login: name, email address and password. Passwords are stored only as a salted one-way hash (PBKDF2-SHA256); we cannot see them.
  • Invitations: if you are invited to the Portal, the invitation code (stored only as a hash) and the account it belongs to.
  • Communications: what you send us when you contact us for support, feedback or sales (for example your name, email address, phone number and the content of your message).
  • Billing information (paid plans only): payments are handled by our payment provider, Stripe, on Stripe’s own checkout pages. Stripe collects your payment details (card, Apple Pay, Google Pay or bank account), the billing email address, the organisation’s name and its ABN, which appear on invoices. We receive and keep a Stripe customer reference, your plan, subscription status and renewal dates. We can see invoices and the last digits of the payment method in Stripe’s dashboard, but we never receive or store full card or bank account numbers.

2.2 Information from Google (Sign in with Google)

If you choose to create an account or sign in with Google, Google sends us the following about your Google account, after you agree on Google's consent screen:

Google data Why we use it
Google account ID (the "subject" identifier) To recognise your Google account each time you sign in. We match accounts on this ID only, never on email address.
Email address and whether Google has verified it To show which Google account is linked to your login, and as your Portal login email when you sign up with Google. We refuse unverified email addresses.
Name To show your name in the Portal when you sign up with Google.

We request only the basic openid, email and profile scopes. We do not request access to your Gmail, Google Drive, contacts, calendar or any other Google service. We do not store your Google password (we never see it) and we do not keep Google access or refresh tokens: the sign-in is checked on our server and the tokens are then discarded. Your profile photo is not stored. See section 6 for how this information is protected and section 7 for how to remove it.

2.3 Information collected automatically

  • Sign-in and security data: the network (IP) address of sign-in attempts, kept briefly to limit password guessing and sign-up abuse; when sessions were created and last used.
  • A log of changes made in the Portal: for example "settings updated", "computer linked", "tablet removed", "Google sign-in linked", with the time and the user who made the change.
  • Status of Signare computers: each reception computer linked to the Portal checks in about every 30 seconds and sends its name, Signare version, local network address, the names given to its tablets and whether they are online, simple counts (for example how many documents were signed today) and the status of its secure connection. This contains no patient or document information.
  • Hosting logs: our hosting provider (Cloudflare) processes technical request information, such as IP address, browser type and the time of the request, to deliver and protect the Service.

2.4 Crash reports (only if the organisation agrees)

If part of the Software stops working (the Signare service, the signature stamper, the tray app or the printer listener), the reception computer writes a crash report on that computer first. It is sent to us only if the organisation agrees: the Signare dashboard and the tray icon ask "Signare had a problem. Send a crash report?", show exactly what would be sent, and offer Send and Don't send. In Settings > Crash reports the organisation can choose to always send reports without being asked; this is off unless it is turned on.

A crash report contains only: which part of Signare stopped and how; the Signare version, the Windows version and how long Signare had been running; the type of error, its message, and where in Signare's own program code it happened; how many times it happened; and the last (up to 50) lines of Signare's own log.

Before anything is saved, the message and log lines are cleaned with an allow-list: only words that Signare itself uses in its messages, and common technical error words, are kept. Names, file names and folder paths, web and email addresses, network addresses, dates, longer numbers, codes, keys and quoted text are replaced. So a crash report does not contain patient or client details, documents, signatures, the text of a form, or network addresses. Our server checks each report again when it arrives.

The same problem is reported at most once a day from a computer, and at most 10 reports a day. We keep one entry per problem, with counts and at most 5 example reports (no more than 2 from one computer), linked to the organisation that sent it so we can follow up. Crash reports are visible only to Signare staff (not in the Portal) and are deleted with the organisation's account.

2.5 Business contact records

To support our customers, Signare staff keep a contact record for each customer organisation: its legal name, ABN and address, the name, role, phone number and email address of its contact person and of its IT contact (if it has one), our notes about the account (for example setup and support history) and its customer status. We also keep a history of changes to that record (what changed, when and which Signare staff member changed it). These are business contact details, typed in by Signare staff from what the organisation tells us; they never contain patient or client information. They are visible only to Signare staff, not in the Portal.

2.6 Information we do not collect

  • The content of any document printed or signed with Signare, signatures, consent answers, or values read from forms. These stay on the customer's computers.
  • The layout of customers' forms (where the signing boxes go). These stay on each reception computer.
  • Sensitive information (such as health information) about anyone. Please do not send us documents or health information when asking for support; describe the problem instead.

3. How we use personal information

We use personal information to:

  • provide the Service: create and manage accounts, sign you in (with a password or with Google), link reception computers, show their status, and apply your settings;
  • keep the Service secure: prevent and investigate unauthorised access, fraud and abuse, and keep a record of changes;
  • take payment for paid plans, send invoices and keep billing and tax records;
  • issue and check software licences;
  • find and fix faults in the Software, using crash reports the organisation chose to send;
  • provide support and reply to your questions;
  • send you service messages (for example security notices or changes to these terms). We do not send marketing email without your consent, and you can opt out at any time;
  • meet our legal obligations and enforce our terms.

We may create de-identified, aggregated statistics (for example the number of active computers) to run and improve the Service. We do not use personal information for advertising, profiling, or to train artificial intelligence models.

4. Google user data: Limited Use

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

In particular, information we receive from Google is used only to sign you in to the Portal and to show you which Google account is linked. It is not sold, not used for advertising, not used to train AI models, not transferred to anyone else (except as required by law, or as part of a merger or sale of Signare's business with notice to you), and not read by people at Signare except with your permission, for security reasons, or where required by law.

5. Who we share personal information with

We do not sell or rent personal information. We share it only with:

  • Service providers that run the Service for us: Cloudflare, Inc. (hosting, database, DNS and network security; the Portal database is located in the Asia-Pacific region), Google LLC (Sign in with Google, if you use it, and our support email, which runs on Gmail), and Stripe (Stripe Payments Australia Pty Ltd and its related companies, for payments on paid plans). They may only use the information to provide their services to us.
  • Let's Encrypt (Internet Security Research Group): to issue security certificates for customers' reception computers. Certificate names are random (for example c-k3j9x2m4q8w1.lan.signare.com.au), contain no organisation or personal names, and are published in public certificate logs as all web certificates are.
  • Professional advisers (such as lawyers, accountants and insurers) where needed.
  • Authorities, where required or authorised by law.
  • A buyer or successor of all or part of Signare's business, who would be bound by this Privacy Policy.
  • Other users in your organisation: people with a Portal login for your organisation can see the organisation's settings, linked computers and change log, including which user made a change.

Overseas disclosure

Some of these providers are based in, or store information in, other countries, including the United States (Cloudflare, Google, Stripe) and other countries where Cloudflare operates its network. We take reasonable steps, including through their contractual terms, to make sure they handle personal information consistently with the APPs.

6. Storage and security

The Portal stores data in Cloudflare's database service (Asia-Pacific region) and is reached only over HTTPS. Protections include hashed passwords, hashed session and device tokens, single-use and time-limited sign-in codes, limits on repeated sign-in attempts, HttpOnly / Secure cookies and strict security headers. Google sign-in uses the server-side authorization code flow with PKCE, so your browser never holds a Google token.

No method of storage or transmission is completely secure, and we cannot guarantee security. If we suspect a data breach, we will assess it within 30 days. If it is likely to result in serious harm, we will notify affected people and the Office of the Australian Information Commissioner (OAIC) as soon as practicable, as the Notifiable Data Breaches scheme requires, telling them what happened, what information was involved, what we have done and what they can do to protect themselves. To report a suspected breach or a security problem, email help@signare.com.au.

7. How long we keep information

  • Account, login and Google sign-in information: while the account exists. If you unlink Google in Settings > Sign in with Google, we delete the stored Google account ID and email straight away. When an account is closed, we delete its logins, linked computers and settings within 30 days, except where we must keep something to meet legal, tax or accounting obligations.
  • Sessions: expire after a period of inactivity and at most 7 days after sign-in.
  • Sign-in attempts in progress: deleted after 10 minutes or once used.
  • Network addresses for rate limiting: kept only for the short limiting window (minutes to an hour).
  • Change log: for the life of the account, so your organisation can see who changed what.
  • Support emails: for up to 2 years after the conversation ends.
  • Billing and tax records (invoices, payments and the subscription history): for 5 years, as Australian tax law requires.
  • Crash reports: while the organisation’s account exists, and deleted when it is closed. We keep at most 5 example reports for each problem (no more than 2 from one computer), and may delete them sooner once the problem is fixed.
  • Business contact records and their change history: while the organisation is a customer, and for up to 2 years after its account is closed, unless the law requires us to keep them longer.

8. Cookies

The Portal uses only cookies that are strictly necessary to sign you in:

Cookie Purpose Lasts
__Host-signare Keeps you signed in to the Portal Up to 7 days, ends on sign-out
__Host-signare-oauth Protects a Google sign-in in progress against forgery 10 minutes

We do not use advertising, tracking or third-party analytics cookies. Cloudflare may set a strictly necessary security cookie to protect the site from attacks. Because these cookies are needed for the Service to work, they cannot be switched off in the Portal; you can block them in your browser, but you will not be able to sign in.

When you pay for a plan, you do so on Stripe’s checkout and billing pages, which set their own cookies under Stripe’s privacy policy. The Signare website (signare.com.au) sets no cookies.

9. Your choices and rights

  • Access and correction: you can see and update your name, email and sign-in methods in the Portal under Settings. You can also ask us for a copy of the personal information we hold about you, or ask us to correct it. We will respond within 30 days, and we do not charge for a request.
  • Google sign-in: you can unlink Google at any time in Settings > Sign in with Google (once a password is set), and you can remove Signare's access in your Google Account at https://myaccount.google.com/permissions.
  • Deleting your account: email us at the address below and we will close it (see section 7). If your login belongs to an organisation, we may confirm the request with the organisation's account owner.
  • Anonymity: it is not practical to provide a Portal account without identifying you, but you can make general enquiries without giving your name.

10. Organisations that use Signare

Our customers (for example medical practices) control the documents their patients and clients sign with Signare. Those documents are kept on the customer's own systems and are handled under the customer's own privacy policy. If you signed a document at an organisation that uses Signare and have a question about it, please contact that organisation: Signare does not hold a copy.

11. Children

The Portal is for businesses and is not intended for anyone under 18.

12. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. We will post the new version on this page with a new effective date, and tell account owners by email or in the Portal about material changes before they take effect.

13. Contact us and complaints

  • Email: help@signare.com.au

If you have a complaint about how we handled your personal information, please contact us first. We will acknowledge it within 7 business days and aim to resolve it within 30 days. If you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner: https://www.oaic.gov.au, phone 1300 363 992.

Signare keeps documents on your own computers and local network; its online portal holds account, settings and status information only. Signed PDFs are tamper-evident: changes made after signing can be detected, not prevented.

Signare

Paper forms, signed on a tablet and saved back to your computer.

Book a demo

Product

  • How it works
  • Features
  • For medical practices
  • Security and privacy
  • Resources
  • About Signare
  • Setup and requirements
  • Cut to the chase

Account

  • Sign in
  • Pricing
  • help@signare.com.au

Legal

  • Privacy policy
  • Terms of service
Copyright © 2026 Signare. ABN 58 175 474 095. Made in Australia.
About Privacy Terms Sign in