Privacy Policy

Who we are

SangraMate is operated by Worklair Pty Ltd (ACN 685 645 452, ABN 16 685 645 452) — "we" and "us" in this policy — an Australian company based in Sydney. We provide the SangraMate apps for iPhone and Android, their companion web portals for clinics and carers, and this website, and you can reach us about anything in this policy at info@sangramate.com.

Because SangraMate handles health information, we hold ourselves to the Privacy Act 1988 (Cth) and the Australian Privacy Principles as our baseline — wherever in the world you use the app.

Health information and consent

Glucose readings, insulin doses, meals and the other records you keep in SangraMate are health information — a category of sensitive information under Australian privacy law. We collect it only with your consent: you choose to connect your LibreLinkUp account, to log events and to use the AI features. You can withdraw that consent at any time by disconnecting your sensor or deleting your account.

What we collect

• Account details — your email address, a display name of your choosing, time zone, country and app settings. We deliberately collect no date of birth, no government identifiers and no proof of identity. Your password is stored only as a cryptographic hash, never in plain text. Clinic accounts may also carry an organisation name and address.
• Diabetes data — glucose readings (refreshed roughly every two minutes while your sensor is connected), your logs of meals, insulin, activity and notes, and the reports and insights the app builds from them.
• LibreLinkUp credentials — the email and password you provide are stored encrypted and used for one thing only: fetching your glucose data from Abbott's LibreLinkUp service.
• Meal photos — a photo you attach to a meal is used to estimate its nutrition and stored with the log.
• Voice recordings — your voice recordings are streamed to our speech-recognition provider to produce a transcript and are not retained by SangraMate. We have opted out of our provider's data-retention and model-training programs, so your audio is not stored after transcription or used to train speech models.
• AI conversations — your chat threads with the assistant, plus a technical log of AI requests that we keep for reliability and usage metering.
• Security data — two-factor authentication secrets and recovery codes, stored encrypted.
• Subscription records — your plan and entitlement status from the App Store or Google Play. Payment happens through Apple or Google; we never see your card details.
• Support messages — feedback and support tickets you send us.
• Diagnostics — crash and error reports from the app and our servers, so we can find and fix failures.

Where it comes from

Almost everything comes directly from you or your sensor: what you log, what you ask the assistant, and the readings SangraMate fetches from Abbott's LibreLinkUp service using the credentials you provide. The rest — forecasts, insights, briefings — is generated by the app itself from your data. Nothing comes from the health store on your phone: SangraMate does not read from Apple Health or Health Connect.

How we use it

• Running the service — syncing readings, storing logs, firing alarms and building reports.
• AI features you invoke — answering chats, estimating nutrition from meal photos and writing briefings, delivered around 07:00 in your time zone with a weekly edition on Mondays.
• Notifications you enable — alarms, briefings and Care Circle updates.
• Keeping the service reliable and fair — metering AI usage per plan, preventing abuse and fixing crashes.
• Support and legal — answering your messages and meeting obligations the law places on us.

We do not sell personal information, and we do not use it for advertising.

Sharing you control

Followers and clinic connections see your data only after you invite them, and you can remove their access at any time. Nobody is added by default.

Cookies and website analytics

This section is about this website, sangramate.com. The apps themselves use no advertising or tracking cookies.

Running the site needs no cookies at all, so there is nothing you have to accept in order to read it. The one optional thing we load is analytics.

In the EU, the EEA, the UK, Switzerland and the rest of Europe, we ask before we load it: on your first visit we ask whether you are willing to allow analytics, nothing analytics-related loads until you answer, and declining takes the same single click as allowing. Nothing is pre-selected, and dismissing the question is not consent — we ask again. We tell where you are from your device's time zone; when it does not say, or your browser sends a Global Privacy Control signal, we ask as well.

Everywhere else, analytics is on when you arrive, and you can turn it off at any time under "Cookie settings" in the footer of any page.

• When analytics is on — we use Google Analytics (Google Ireland Limited for visitors in the EU and UK) to count visits and see which pages people find useful. It sets cookies in your browser and receives your IP address, which Google uses to approximate your country and then discards. We have turned off Google Signals and ad personalisation on our property, so this data is not used to build advertising profiles and is not shared with Google for advertising.
• If you decline or turn it off — no analytics cookies are set and nothing is sent to Google. Any analytics cookies already in your browser are deleted.
• Changing your mind — the "Cookie settings" link in the footer of any page reopens the question. Analytics can be turned off there at any time, whether you allowed it or it was on when you arrived, which stops it immediately and deletes the cookies it set.
• Remembering your answer — we keep it in your browser's local storage, under a single key, so we do not ask again on every page. It is stored whichever way you answer, because that is what lets us honour a no. It never identifies you and it is never sent to us.
• Campaign tags — when you arrive from one of our tagged links (utm_source, utm_medium and utm_campaign in the address), we keep those three tags for your visit in your browser's session storage, which empties when you close the tab. We add them to the App Store and Google Play links, so the stores can tell us which campaign an install came from, and Google Analytics gets them with your visit when analytics is on. They name the campaign, never you.

The website sets no other cookies. We run no advertising network, no social widgets and no A/B testing tools.

Apple Health and Health Connect

SangraMate can copy your own records into the health store on your phone — Apple Health on iPhone, Health Connect on Android. It is off until you switch it on in Settings and grant the operating system permission.

• What gets written — on iPhone, blood glucose readings, insulin doses (each tagged basal or bolus) and the carbohydrates from your meals. On Android, blood glucose readings and carbohydrates only: Health Connect has no record type for insulin, so insulin doses are not written there.
• Write only — the app puts records in and never reads anything back out. Neither Apple Health nor Health Connect is a source of data for SangraMate.
• When you switch it on — SangraMate writes the recent glucose readings it already holds, then keeps pace as new ones arrive. Doses and meal carbohydrates are written for the current day onwards. Your earlier history is not backfilled.
• Your own records only — the write runs for the account that owns the data. If you follow someone else, their readings and logs are never written into the health store on your phone.
• Stays on your phone — writing to the health store sends nothing to us and nothing to any third party. Whether other apps can see those records is controlled by you inside Apple Health or Health Connect, not by us.
• Corrections and deletions — editing an entry makes SangraMate send the corrected value again under the same record id. Deleting an entry does not remove it from the health store: the app only ever writes records, it never deletes them, so clearing those out is up to you.
• Turning it off — switching the toggle off in Settings stops every future write. It does not remove anything already written; delete that yourself in Apple Health or Health Connect.

Service providers

We use a small set of specialised providers, each receiving only what its function needs:

• Amazon Web Services (United States) — hosts our servers, database and file storage.
• OpenAI (United States) — processes AI chats, meal-photo analysis and generated reports when you use those features. Our AI provider may retain inputs and outputs for up to 30 days for abuse monitoring, after which they are deleted.
• Deepgram (United States) — converts voice recordings to text when you log by voice.
• RevenueCat (United States) — matches your App Store or Google Play receipt to your subscription entitlements.
• OneSignal (United States) — delivers push notifications to your device.
• Sentry (United States) — receives crash and error diagnostics.
• Google Analytics (Ireland and the United States) — receives website usage data, and only if you have allowed analytics on this website. It is not used by the apps.
• Apple — handles App Store billing on iPhone under Apple's own terms.
• Google — handles Google Play billing on Android under Google's own terms.
• Abbott's LibreLinkUp — the source of your glucose data, accessed with your own credentials under Abbott's terms. SangraMate is an independent product and is not affiliated with, endorsed by or sponsored by Abbott.

Our service providers process your information only to provide their service to us — never for advertising, and never to sell to third parties. Some providers may use de-identified, aggregated information (which does not identify you) to operate and improve their services.

Overseas processing

We use service providers located overseas, principally in the United States (cloud hosting, AI processing, speech transcription, subscription management, notifications, error monitoring and website analytics). We take reasonable steps, including contractual data-processing terms, to ensure these providers handle your information consistently with Australian privacy law. By using SangraMate you consent to your information, including health information, being transferred to and processed in the United States for these purposes.

How long we keep it

Your health data has no time-based expiry — it stays available to you until you delete it or your account. In detail:

When your account is deleted, this data is deleted from our production systems, and residual copies in backups and storage cleanups expire within 90 days.

Security

Data moves over encrypted connections. LibreLinkUp credentials and two-factor secrets are encrypted at rest, passwords are stored only as hashes, and access to the clinic and admin portals is role-gated.

No system is perfectly secure. If a breach ever puts you at likely risk of serious harm, we will notify you and the Office of the Australian Information Commissioner under the Notifiable Data Breaches scheme.

Access and correction

Most of your data is visible and editable directly in the app. For anything else — a copy of your data, a correction, or a question about what we hold — email info@sangramate.com from your account address. We aim to answer within 30 days.

Deleting your account

You can delete your account and its data from inside the app. If you would rather we did it, email info@sangramate.com from your account address and we will delete the account and its data for you.

Complaints

If you think we've mishandled your information, tell us first — we take it seriously and will respond within 30 days. If you're not satisfied with our answer, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au or on 1300 363 992.

Changes to this policy

When this policy changes, we will update it here and adjust the date above. If a change meaningfully affects how we handle your data, we'll tell you in the app or by email first.