Privacy Policy

Quies is not intended for, marketed to, or designed for anyone under 18.

• We collect date of birth at signup to verify users are at least 18 years old. Accounts that fail this check are blocked from creation.
• Why we keep a record of your age declaration: when you sign up you declare that you are 18 or over. We keep your date of birth and a minimal record that the declaration was made and when. We keep it for one reason only — so that if an account is later found to belong to someone under 18, we can show that the age gate worked and that the declaration given to us was false. We do not use it for marketing, advertising, profiling, scoring or any other purpose, and we do not disclose it for those purposes. This is collection that is reasonably necessary for our functions under APP 3, used only for that primary purpose under APP 6, and destroyed with the rest of your information when your account is deleted under APP 11.2.
• We do not knowingly collect personal information from children. If we become aware that an account belongs to a person under 18, we will close the account, delete all associated personal and health information within 30 days, and refund any unused subscription.
• If you are a parent or guardian and believe your child has created an account, please contact us at support@quies.dev and we will action removal promptly.
• We do not perform behavioural profiling, ad targeting, or social-feature exposure of minors. The 18+ rule is enforced uniformly regardless of jurisdiction.
• This policy is consistent with the Privacy Act 1988 (Cth), guidance from the Office of the Australian Information Commissioner (OAIC), and the Children's Online Privacy Code being developed by the OAIC.

• Personal information: name, email, date of birth, sex, height, weight, timezone, country.
• Sensitive health information: fasting sessions, food logs, sleep data, activity data, glucose/ketone levels, mood, body measurements, journal entries. Health information is "sensitive information" under s 6 of the Privacy Act and is collected only with your express consent during onboarding.
• Usage data: in-app interactions, feature usage, subscription status.
• Device & technical data: device type, operating system, browser, app version, language, screen size, and timezone — used for app compatibility, debugging, and abuse prevention.
• Network & location data (signup, waitlist & login): we collect your IP address, derived country and (where available) approximate city/region, user agent string, browser, OS, device type, referrer, and timezone. This is used to (a) verify Australian residency for our AU-only service, (b) detect fraud and bot signups, (c) notify our admin team of new accounts, (d) email you when your account signs in from a device or country we haven't seen in the last 90 days, so you can check it was you, and (e) maintain a security/audit log as required for an APP entity. Your IP address is sent to an IP-lookup provider (see Section 5) to work out your country.
• Payment data: processed entirely by Stripe — we never see or store your card numbers. Stripe also receives your billing address and card-issuer country, which we use to confirm AU residency.

• Directly from you when you create an account, complete onboarding, or use the app.
• Automatically as part of running the service — for example, anonymous records of technical faults (a screen failing to load, a save failing) so we can fix them. These contain no health data and nothing you have written.
• From Stripe for subscription and billing status.
• In plain English — personal invitations: when the owner invites someone, we use the supplied name and email to prepare their account, record gifted access and send a private welcome link. The recipient supplies their own date of birth and consent before using the diary. Invitation, gift and email records are used to provide and account for that access under APPs 3, 5 and 6 of the Privacy Act 1988 (Cth), not to enrol the recipient in marketing.
• When you use the Contact form: your name, email, the topic you pick, your message and — only if you choose to give it — a phone number. We use these only to reply to you. The message is emailed to our support inbox and a short alert is sent to the owner's private Telegram so it isn't missed. Messages are kept in our inbox only as long as needed to deal with your request.
• In plain English: the waitlist and Contact forms need a successful bot check. We keep an IP-address request counter to limit repeated submissions. We also keep a one-way code made from a waitlist email address so that address is not sent another confirmation, even if its waitlist entry is removed. This code can still be compared with an address and is not anonymous. These records are used for abuse prevention and avoiding repeated mail, under APPs 3, 5, 6 and 11 of the Privacy Act 1988 (Cth).

• To provide, maintain, and improve the Quies service.
• To show your own records back to you as summaries, charts and reflections.
• To process subscription payments via Stripe (in AUD, GST-inclusive where applicable).
• To send transactional emails (account confirmation, password reset, receipts) and, with your consent, product updates you can unsubscribe from at any time.

We do NOT sell your personal or health information to anyone. Ever.

Where your data is stored:

Your personal and health information is stored on managed cloud infrastructure provided by Supabase Inc. (a US company), with the underlying database, file storage, authentication and serverless functions physically hosted in Tokyo, Japan (AWS region ap-northeast-1). Your data is therefore stored OUTSIDE Australia.

Before disclosing personal information to an overseas recipient, we take reasonable steps to ensure the recipient does not breach the Australian Privacy Principles (APP 8.1), including binding data-processing terms.

We do not make any optional overseas disclosures. Quies uses no third-party analytics provider, so there is nothing extra to consent to at sign-up.

Overseas recipients of your information may include:

• Supabase Inc. — primary database, auth and storage (data resident in Tokyo, Japan; corporate entity in the United States). Bound by a Data Processing Agreement.
• Amazon Web Services (AWS) — underlying cloud infrastructure (Tokyo, Japan).
• Stripe, Inc. — payment processing (United States and Ireland). PCI-DSS Level 1 certified.
• Google LLC — Gemini AI models accessed via the Lovable AI Gateway, used to generate suggestions (United States). Health data sent to AI models is not used to train those models.
• Resend — sends our emails (sign-in, receipts, contact replies). Receives your email address, name and the email content (United States).
• Cloudflare — Turnstile bot check on sign-in, sign-up, the waitlist and the contact form. Receives your IP address and a check token (outside Australia).
• ipwho.is and ipapi.co — IP-address country lookup when you sign up, sign in or join the waitlist. ipapi.co is used only if ipwho.is does not answer. Receives your IP address only (outside Australia).
• Telegram — instant alerts to the owner when you use the contact form. Receives your name, email address and message (outside Australia).
• Oura — only if you connect an Oura Ring. We receive your ring data from Oura and send back only the sign-in tokens Oura needs (outside Australia).
• Registrum — our own accounting system. For each payment or refund it receives your name, email address, the amount, the Stripe fee and the Stripe payment reference. No health information is sent (outside Australia).

What this means for you:

Because your data leaves Australia, the Australian Privacy Principles do not directly apply to those overseas recipients. However, under section 16C of the Privacy Act, Quies remains accountable for any act or practice of those overseas recipients that, if done by us in Australia, would breach the APPs. In other words: we remain on the hook if they mishandle your information.

Health data is collected only with your express consent (given during onboarding) and only for the primary purpose of providing the Quies service to you. We do not share health data with insurers, employers, advertisers, or marketers.

Health data may be processed by AI features (Google Gemini via the Lovable AI Gateway) to generate reflections on what you have logged. This processing occurs over encrypted connections and the data is not used to train AI models. AI reflections are general information only — see our Terms of Service for full disclaimers.

Meal photos. If you use photo scanning to log a meal, the picture you choose is sent once, over an encrypted connection, to the same AI provider (Google LLC, United States) so it can be read and turned into a list of foods and estimated amounts. We do not keep the picture: it is not written to our database or file storage, and it is not used to train AI models. Only the food items you review and choose to save are stored, in your own diary. Photo scanning is optional — you can log every meal by search, barcode or by hand without ever sending a photo.

Your data is encrypted while it travels between your device and our servers (HTTPS/TLS), and encrypted while it is stored, using the encryption provided by our infrastructure providers. Every table uses row-level security so that only your own account can read your records, and we apply least-privilege access internally. We review security regularly and we disclose eligible data breaches to affected users and the OAIC as required by the Notifiable Data Breaches scheme (Part IIIC of the Privacy Act).

What we do not claim. Quies is not end-to-end encrypted — the service has to be able to read your entries in order to draw your charts, calculate your summaries and generate AI reflections. We do not hold ISO 27001, SOC 2 or any equivalent certification, and we do not claim that any system is free of vulnerabilities. We say this plainly so that you can make an informed choice about what you record here.

In plain English: if the sign-in bot check is unavailable, we keep a small outage record with no password, check token or diary entries. This record does not identify an account. The owner receives at most one outage alert per hour. We use it to investigate sign-in problems, consistent with APP 1, APP 6 and APP 11 of the Privacy Act 1988 (Cth).

As described in Section 5, the underlying storage location is the Tokyo, Japan AWS region.

• Supabase / AWS Tokyo — database, auth, storage, edge functions.
• Stripe — payment processing in AUD.
• Google (Gemini via Lovable AI Gateway) — AI suggestions.
• Cloudflare Turnstile — bot protection on sign-in, sign-up and the contact form. Receives your IP and a session token to verify you're human; no personal information or browsing history is sent. See Cloudflare's privacy policy.
• Resend — sends our emails; receives your email address, name and the email content.
• ipwho.is and ipapi.co — IP-address country lookup at sign-up, sign-in and waitlist; receives your IP address only.
• Telegram — owner alerts from the contact form; receives your name, email address and message.
• Oura — only if you connect a ring; see Section 8A.
• Registrum — our accounting system; receives your name, email address and payment or refund amounts with the Stripe reference. No health information.
• We do not disclose your data to anyone else without your explicit consent or unless required by Australian law.

Connecting a ring is entirely your choice and Quies works fully without one. If you do connect one, you are sent to Oura to sign in and approve it. We never see your Oura password.

What we receive: the daily sleep, readiness and activity figures Oura works out for you, and heart-rate figures if you leave that permission ticked at Oura's screen. Nothing is sent back to Oura and nothing is shared with other members.

How it is held: the keys that let us fetch your figures are encrypted on our servers, are never shown in the app, and are used only to read your own data. The figures themselves sit in your account with the same protections as everything else you record, and are health information under the Privacy Act.

Stopping it: tap Disconnect on the Health Sync page. We withdraw our access at Oura, delete the keys, and remove the ring days we copied across. Oura keeps its own copy under its own privacy policy — see ouraring.com/privacy-policy.

Oura is a third party we disclose to only in the sense that we ask it, with your approval, for your own data. We do not send it anything you record in Quies.

You have the right to:

• Access the personal information we hold about you (APP 12).
• Correct inaccurate, out-of-date, incomplete, or misleading information (APP 13).
• Request deletion of your account and all associated data — you can do this yourself, straight away, in the app: Profile → Danger Zone → Delete Account. It happens immediately; you do not need to email us or wait for approval.
• Take a copy with you before you go — Profile → Export my data downloads everything we hold about you as a file.
• Opt out of marketing communications.
• Lodge a complaint with the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au or 1300 363 992.

To exercise these rights, contact us at support@quies.dev. We respond within 30 days.

We keep your information while your account is open. When you delete your account, the deletion runs immediately — it is not a request that sits in a queue.

Removed straight away: your profile, your sign-in identity (so the account no longer exists and cannot be logged into), your photo, and everything you tracked — fasting sessions, food, water, weight, body measurements, glucose and ketones, sleep, mood, activity, habits, journal entries, gratitude notes, affirmations, badges, targets, notification settings, and any connected device data such as Oura.

Billing: if you have a paid subscription, it is cancelled at the same moment so your card is never charged again. Deleting your account does not by itself create a refund — see our Refunds page.

Backups: encrypted backups roll over on a schedule, so copies are fully gone within 90 days.

What we must keep: a small record that the deletion happened (date and time only), payment and tax records we are legally required to hold, and basic records of any support or partner activity tied to your email. These are kept to meet Australian tax, accounting, and legal obligations, and are not used to rebuild your account or profile.

Your date of birth is deleted too. The age declaration you made at sign-up is removed with everything else when you delete your account. It is not carried over into the deletion record, and it is never used for marketing or profiling while your account is open — see Section 1A.

De-identified, aggregated statistics that cannot be traced back to you may be kept for analytics and product improvement. Deletion cannot be undone, and we cannot restore an account after the fact.

Legal basis: we destroy or de-identify personal information that is no longer needed for a permitted purpose in accordance with APP 11.2 of the Privacy Act 1988 (Cth), except where we are required by or under an Australian law or a court/tribunal order to retain it — including records required under the Income Tax Assessment Act 1936 (Cth) s 262A and the Corporations Act 2001 (Cth) s 286 (financial records retained for 5 and 7 years respectively). Deletion requests are actioned as a correction/destruction request under APP 11 and APP 13, and you may access the information we hold under APP 12 using the in-app export before deleting.

Privacy Officer: Quies, [Your Company Name], Victoria, Australia.

Email: support@quies.dev · General support: support@quies.dev

If you are not satisfied with our response, contact the OAIC: oaic.gov.au or call 1300 363 992.