Privacy Policy

Last updated 23 August 2026

This Privacy Policy explains how Sunwise ("we", "us") at sunwise.org.au collects, uses, stores and shares personal information when you use the site, optional accounts, sun-session features and MCP endpoints. Last updated 23 August 2026.

1. Who is responsible

Sunwise is operated from Australia. For privacy requests, access or deletion, email adrian@martini.studio. We aim to respond within a reasonable time.

2. Information we collect

Information you provide

  • Email address when you sign in or create a free account (passwordless one-time code).
  • Skin type if you save a Fitzpatrick estimate or choose a type manually for your profile.
  • Sun-session details you log or allow to be saved (for example place label, times, sunscreen applications, reconstructed UV dose summaries).
  • OAuth consent choices when you approve an AI assistant to use the signed-in MCP endpoint.
  • Messages you send us (for example support or privacy emails).

Information from your device and use of the service

  • Photo / camera sample: for the skin check, a small centre crop of pixels is processed on our servers in memory and discarded. We do not store the image file or pixel buffer.
  • Location: with permission, approximate coordinates or a chosen place, used to fetch UV/weather and (when relevant) analytics. Stored analytics coordinates are rounded to about 1 km.
  • On-device data: skin profile and active sun-session state may be kept in your browser (for example localStorage) so the app works when you return.
  • Usage analytics: event names and coarse context (path, local hour/day, timezone, device class, optional skin type, place, UV reading, rounded coordinates). See section 4.
  • Technical logs: standard server and security logs needed to run and protect the service.

Information we do not collect

  • We do not ask for passwords (sign-in is email OTP only).
  • We do not sell your personal information.
  • We do not use your inner-arm photo for advertising or facial recognition — the sample is for skin-tone estimation only and is not retained.

3. How we use information

  • Provide skin-type estimates, live UV conditions, burn-time guidance and sun-session tracking.
  • Create and secure your account, send sign-in codes, and sync profile data across devices.
  • Operate MCP tools and honour the scopes you approve for connected assistants.
  • Understand how the product is used (product improvement and, in aggregate form, research relevant to sun safety) via first-party analytics and Google Analytics 4.
  • Maintain security, prevent abuse, debug issues and meet legal obligations.
  • Respond to your requests and communicate about the service when needed.

4. Analytics

Google Analytics 4: we send coarse product events (for example flow steps). We do not send precise coordinates or place names to GA4.

First-party analytics: the same events may also be stored in our own database (DynamoDB) for anonymous and signed-in visitors. That store may include rounded coordinates (~1 km), place labels, UV readings, skin type, timezone and local time of day. An anonymous visitor ID cookie may link events on a device before sign-in; when you sign in, anonymous history on that device may be associated with your account.

Aggregated or de-identified insights may be used to improve Sunwise and, where appropriate, shared with public-health or skin-cancer research contexts. We will not sell identifiable personal profiles.

5. Cookies and similar technologies

We use first-party cookies and similar storage to run the service:

  • Authentication / session cookies so signed-in features work.
  • Permission memory cookies (for example camera or location allowed in our UI) and a short-lived cached location so we do not re-prompt every visit.
  • Anonymous analytics id so first-party event history can be stitched on one device before you create an account.
  • localStorage for on-device profile and active sun-session state.

You can clear cookies and site data in your browser settings. Doing so may sign you out and reset permission prompts and local session state. Google Analytics may set its own cookies subject to Google's policies; you can use browser controls or Google's tools to limit ad/measurement cookies where available.

6. Accounts, sun sessions and MCP

  • Account data (email, skin type, sessions) is stored in our cloud database so you can access it when signed in.
  • AI assistants you approve via OAuth may read and write only within the scopes shown on the consent screen (for example log sessions, read history). Disconnect access from your assistant's settings when you no longer want it connected.
  • Transactional emails (sign-in codes) are sent via Amazon SES from our sunwise.org.au identity.

7. Who we share information with

We share personal information only as needed to operate Sunwise:

  • Infrastructure providers such as hosting, database (AWS DynamoDB), email (Amazon SES) and related cloud services in regions we configure (typically including Australia / Asia-Pacific).
  • UV and geocoding providers (for example Open-Meteo for forecasts; reverse-geocoding services for place names) receive the location query needed to answer your request.
  • Google Analytics for coarse measurement, as described above.
  • Connected AI assistants you explicitly approve, limited to consented scopes.
  • Legal or safety disclosures if required by law, or to protect rights, security and users.

Service providers are engaged to process information on our behalf under appropriate arrangements. They are not permitted to use it for their own unrelated marketing.

8. International processing

Sunwise is aimed at people in Australia but works worldwide. Your information may be processed in Australia and in other countries where our providers operate. Where we transfer personal information overseas, we take reasonable steps appropriate to the circumstances so that it continues to be handled carefully.

9. Retention

  • Photo pixel buffers: not retained after analysis.
  • Account and sun-session records: kept while your account is active and for a reasonable period afterward if needed for security, backups or legal reasons.
  • Analytics events: retained for product and research analysis on a rolling basis consistent with that purpose.
  • Permission and cached-location cookies: up to about one year, or until you clear them (cached coordinates expire sooner for freshness).
  • On-device localStorage: until you clear site data or we change storage keys in a future version.

10. Security

We use reasonable technical and organisational measures appropriate to a small consumer web service (HTTPS, access controls, least-privilege cloud roles, passwordless OTP). No method of transmission or storage is completely secure; please protect access to your email account.

11. Children

Sunwise is a general audience sun-safety education tool. It is not directed at young children. If you believe we have collected personal information from a child inappropriately, contact us and we will take reasonable steps to delete it.

12. Your choices and rights

Depending on where you live, you may have rights to request access to, correction of, or deletion of personal information we hold about you, or to complain about our handling of it. Australian users may also contact the Office of the Australian Information Commissioner (oaic.gov.au) if they have a privacy complaint they cannot resolve with us.

  • Access / correction: email us from the address on your account where possible.
  • Deletion: email us to request account and associated personal data deletion. Some records may be retained where we must (for example security logs or legal obligations).
  • Cookies / local data: clear them in your browser; revoke camera/location in browser or OS settings.
  • MCP assistants: revoke access in the assistant's connected-apps settings.
  • Analytics: browser controls and, for Google Analytics, Google's published opt-out / controls where available.

13. Sensitive information and health framing

Skin-type estimates and UV exposure summaries relate to sun safety education. They are not health records in a clinical sense and must not be treated as medical data. Do not upload photos or information you are not comfortable processing under this Policy.

14. Changes to this Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top will change when we do. Continued use of Sunwise after an update means you accept the revised Policy.

15. Contact

Privacy requests: adrian@martini.studio. Related: Terms of Service.

Also see Terms of Service.