Privacy Policy

Version 1.0. Effective 26 September 2026.

B1. Who we are and how to contact us

Brenton Darvill trading as Blessed B Studios, ABN 24 334 813 190, operates Sage. Our privacy contact is the Privacy Officer at privacy@trysage.com.au. This policy explains how we collect, use, disclose, protect and retain personal information, and how you can make requests or complaints.

B2. Information we collect and its sources

We collect information you provide when creating an account, using features, making choices or contacting support. Depending on the features used, this includes account and contact details, age eligibility confirmation, selected emotions and mood, check-in responses, journal entries, activity history and preferences, AI inputs and outputs, and support correspondence.

The app and our service providers also supply technical information such as device and app version, security events, diagnostics, network information and subscription entitlements or transaction identifiers. The providers and categories actually received are specified in Schedule B1. Payment providers process payment details. Sage. does not receive or store your full payment-card details. Subscription purchases made through the Apple App Store are processed by Apple. Sage. uses RevenueCat to manage subscription status, entitlements and purchase history. RevenueCat does not collect users’ payment-card information.

AI features can generate summaries, suggested themes or other inferences about you. These may be wrong. We treat identifiable inferences as personal information, and sensitive inferences with the corresponding care. We do not present them as a diagnosis. You can ask us to correct information held about you.

B3. Sensitive information and your choices

Mood, journal and wellbeing information may reveal health, sexual orientation, religious beliefs or other sensitive matters. We collect sensitive information with your consent where required by law and only where reasonably necessary for the feature or purpose explained to you, unless a lawful exception applies.

A notice appears before sensitive-information collection. AI processing is essential to Sage. and there is currently no AI-off mode. All submitted check-ins are processed by OpenAI, including for weekly and monthly reflections. This is explained before submission. The “do not share my personal details” setting controls profile details such as your name, not check-in processing. Text you enter may still identify you or contain sensitive information. You may withdraw consent for future processing by contacting privacy@trysage.com.au. Because AI is essential, withdrawal may require stopping the affected service or closing your account. When you withdraw consent, we stop new AI requests and cancel queued or scheduled AI processing associated with your account as soon as reasonably practicable. Withdrawal does not reverse processing already completed. Existing information is deleted, de-identified or retained as described in B11 and Schedule B2.

You are not generally required by law to supply optional journal or wellbeing information. If you withhold information needed for a chosen feature, we may be unable to provide that feature. We will explain the consequence at collection.

B4. Account identification, pseudonyms and information about other people

Sage. does not offer guest or anonymous use of its app features. You must create and sign in to an account to use Sage. An account is necessary to authenticate access, protect private content, store and retrieve your entries, maintain subscription entitlements, synchronise information across sessions, and administer access, correction and deletion requests.

Sage. does not require you to provide your legal name unless it is reasonably necessary for a particular purpose. You may use a permitted display name or omit optional profile details where the app allows this. However, your account and activity may still be identifiable through information such as your email address, internal account identifier, subscription transaction, device or network information. Using a display name or enabling the “do not share my personal details with AI” setting does not make your account anonymous.

General information about Sage., including its Terms of Use and this Privacy Policy, may be viewed without creating an account. Where reasonably practicable, you may make a general enquiry without providing your legal name. The communication method you use may still disclose information such as your email address or network information.

For account-specific support, subscription issues, access, correction, deletion, security incidents or complaints concerning your personal information, we may require enough information to locate the relevant account and verify that you are authorised to make the request. We collect only the information reasonably necessary for that purpose.

Avoid entering identifying or sensitive information about another person unless you have a lawful reason and any required permission to do so. If we receive unsolicited personal information, we assess whether we may lawfully retain it and delete or de-identify it where required and lawful.

B5. Why we use information

We use information to provide accounts and requested features, save your entries and preferences, generate chosen AI reflections, provide activity suggestions and progress history, administer purchases, respond to support requests, protect accounts, investigate faults and safety reports, and comply with legal obligations. We use technical and appropriately minimised usage information to improve reliability and performance.

Sage. contains no advertising. We do not sell private wellbeing content or use it for advertising. We do not use that content to train our own general-purpose models or opt it into OpenAI model training. OpenAI states that API content is not used to train its models by default unless the customer opts in. A new purpose requiring consent will be explained and consent obtained before it begins. An updated policy alone is not treated as that consent.

B6. External AI processing

Sage. uses OpenAI API calls as an essential part of its operation. Every submitted check-in is shared with OpenAI for processing and used to create weekly and monthly reflections. The processing includes check-ins, check-in fields, history, identifiers and other context, honoring the personal-details setting, and produces reflections. There is no current setting to turn off AI while keeping full app functionality. Do not submit a check-in if you do not consent to this processing.

Processing locations, retention and any provider human access or abuse monitoring are described in Schedules B1 and B2. OpenAI does not use API content to train its models by default unless the customer opts in, and Sage. does not opt private wellbeing content into training. This does not mean OpenAI retains no data. OpenAI’s standard API controls may retain prompts, responses and related information for abuse monitoring, and some API products may retain application state. The applicable periods and controls are described in Schedules B1 and B2.

B7. Recipients and access

We disclose information to providers only for the functions described in Schedule B1 and other purposes permitted by law. Authorised personnel may access information where necessary for support, security, administration or incident investigation, under access restrictions.

We may disclose information where required or authorised by law, including a valid compulsory legal process. If a lawful serious-threat exception applies, a necessary disclosure may be made to help address the threat. This is not a promise that we monitor users, detect emergencies or contact emergency services. We assess the basis and scope of such disclosures.

If a business transfer is proposed, we will assess the lawful basis for any disclosure, minimise the information shared and require appropriate safeguards. We will notify users of a resulting material change to information handling as required. This policy does not give unrestricted permission to transfer private journals to a buyer.

B8. Overseas processing

Information may be processed in the countries identified in Schedule B1, including through provider support or subprocessors. We assess applicable safeguards and cross-border obligations before disclosure. Merely using Sage. is not treated as consent to waive protections under Australian Privacy Principle 8. We update the schedule and provide any additional notice or consent required before material changes.

B9. Analytics, marketing and security

Sage. does not currently use optional behavioural analytics, advertising analytics, cross-app tracking or session-replay technology, so there is no optional analytics control in the app.

Sage. processes limited technical logs, crash and performance information, authentication events and subscription events where reasonably necessary to operate, secure and troubleshoot the service, administer subscriptions and prevent fraud. Apple, Google, Supabase and RevenueCat may also provide operational, subscription and aggregated store statistics. These activities are described in Schedule B1.

These systems are configured to exclude journal entries, check-in free text and AI conversation content.

B10. Retention

Schedule B2 specifies retention periods or objective criteria for each data category, including provider copies and backups. We delete or de-identify information when it is no longer needed and there is no lawful retention requirement. We do not keep private wellbeing content indefinitely merely because it may be useful later. Removing your name alone does not necessarily de-identify a journal.

B11. Account and content deletion

Request account deletion through Settings, or contact privacy@trysage.com.au. We verify requests proportionately. Before confirmation, we explain loss of access and content, the deletion timetable and any action needed to stop subscription renewal. Deleting an account may not cancel a subscription billed by Apple or Google. Use the applicable store cancellation control.

On confirmation, active-system deletion and downstream deletion requests occur within the periods in Schedule B2. Limited information may be retained where required by law or reasonably necessary for a specified security or legal-claims purpose. We restrict retained information to that purpose and delete it when the basis ends. We explain applicable exceptions unless legally prohibited. Backups expire on the stated cycle. Deleted information is not restored to ordinary use following recovery.

Information already transmitted to a provider may remain there until the applicable provider retention period expires and may not be capable of immediate recall.

B12. Access and correction

Contact privacy@trysage.com.au to request access to or correction of personal information, including stored AI-derived information. We will reasonably verify identity and respond within the period required by applicable law. We aim to respond within 30 calendar days. We do not charge to make a request or to correct information. If a reasonable access charge is permitted and proposed, we will explain it in advance.

If we lawfully refuse a request, we will provide reasons where required and explain complaint options. Where required, we will associate a statement of requested correction with the information and take reasonable steps to notify relevant recipients of a correction.

Sage. does not currently provide a self-service data-download feature. The absence of a self-service export feature does not limit any access, correction or portability right that applies under law.

B13. Children and safety reports

Sage. is restricted to adults aged 18 and over. If we become aware of a child’s account, we will restrict access, assess the information and take appropriate deletion or retention steps under applicable law.

Safety, privacy, security and abuse concerns may be reported to support@trysage.com.au. This inbox is reviewed regularly during South Australian business days but is not continuously monitored. We assess reports, request further information where necessary and escalate urgent matters through our internal safety, privacy or security process.

This channel is not an emergency or crisis service. If you or another person may be in immediate danger, contact the emergency or crisis service available in your location. Do not wait for a Sage. support response.

B14. Data breaches

We investigate suspected breaches and take steps to contain and remedy them. Where notification is legally required, we notify the relevant regulator and affected individuals as required by law and provide practical protective information. Contact privacy@trysage.com.au to report a suspected privacy incident.

B15. Privacy complaints

Contact privacy@trysage.com.au with your concern. We aim to acknowledge complaints within five business days and respond within 30 calendar days, or explain the reason for delay and expected response date. You can also contact the Office of the Australian Information Commissioner at oaic.gov.au or on 1300 363 992 where it has jurisdiction, or an applicable state or territory regulator. You do not lose any other complaint or legal rights by contacting us.

B16. Policy changes

We publish the current policy with its effective date and communicate material changes through the app or account contact details as appropriate. We will obtain any consent required for new handling of information. We will not treat publication of a revised policy as retrospective consent.

Schedule B1. Providers and processing locations

We use the providers listed below to operate Sage. The information describes the services used, the information disclosed, relevant processing locations and the provider controls applying to Sage. Provider arrangements may change. We will update this schedule and provide any additional notice or consent required before making a material change to how sensitive information is handled.

Database and infrastructure: Supabase

Sage. uses Supabase, provided under our account agreement with SUPABASE PTE. LTD., for PostgreSQL database, authentication, Storage, Edge Functions, logging and any other services.

Supabase processes account information, authentication records, consent records, check-ins, journals, activity history, AI-generated reflections, movement and give-back tasks, to the extent those categories are stored or processed through the applicable Supabase services.

The primary Supabase project region is Singapore. Information may also be processed or accessed from other countries through Supabase support, security operations and subprocessors, as described in Supabase’s applicable data-processing terms and subprocessor information.

Sage. uses daily database backups. The maximum database recovery period is 7 days. Supabase database backups do not include the underlying objects stored through the Supabase Storage API, although associated database metadata may be included. Storage-object deletion and any separate replication or backup arrangements are described in Schedule B2.

Access to production information is restricted to authorised personnel and provider personnel who require access for permitted operational, security, support or legal purposes. Further information is available in the applicable Supabase privacy notice, data-processing agreement and subprocessor list:

Artificial intelligence: OpenAI

Sage. uses the OpenAI API under an account agreement with OpenAI OpCo, LLC. Sage. uses https://api.openai.com/v1/chat/completions and https://api.openai.com/v1/moderations to process submitted check-ins, movement suggestions and give-back suggestions, and to generate weekly and monthly reflections.

The information transmitted may include check-in text, mood and wellbeing information and relevant historical check-ins. When the “do not share my personal details with AI” setting is enabled, Sage. excludes name, age, gender and experience with somatics from being shared with AI. This setting does not remove any other identifying or sensitive information that a user enters in free text.

OpenAI does not use API content to train its models by default unless the customer opts in. Sage. does not opt private wellbeing content into model training.

Under OpenAI’s standard API controls, prompts, responses and related information may be retained in abuse-monitoring logs for up to 30 days, unless longer retention is required by law or reasonably necessary to protect OpenAI’s services or third parties. Depending on the API endpoint and configuration, OpenAI may also retain application state. The applicable retention periods are described in Schedule B2.

Access by OpenAI personnel may occur where permitted under the applicable agreement for abuse investigation, safety, support, security or legal purposes. Modified Abuse Monitoring and Zero Data Retention do not apply to Sage.'s OpenAI organisation unless OpenAI has approved and enabled the relevant control.

OpenAI processing and storage are global and are not limited to one country. Further information is in OpenAI’s privacy notice, services agreement, data-processing addendum, subprocessor list and API data-control documentation. OpenAI’s privacy notice is at https://openai.com/policies/privacy-policy.

Analytics and crash reporting

Sage. does not currently use a separate analytics or crash-reporting provider. Limited technical logs are described in B9 and Schedule B2. If a separate analytics provider is introduced, this schedule will be updated before that collection begins.

Billing and distribution: Apple and Google

Apple App Store

Sage. uses Apple’s App Store and In-App Purchase services to offer, bill and administer subscriptions on Apple devices. The applicable provider is Apple Inc. and the applicable regional Apple Media Services affiliates.

Apple processes the customer’s Apple Account and payment information. Sage. does not receive the customer’s full payment-card number, bank-account details or Apple Account password.

Sage. receives or may access transaction information made available through StoreKit, App Store Server Notifications, the App Store Server API and App Store Connect. Depending on the implemented services, this may include:

Sage. uses this information to verify purchases, provide and restore subscription access, administer trials and renewals, process cancellation or refund status, prevent fraud, provide billing support, reconcile revenue and comply with accounting and taxation obligations.

Apple may process information through Apple entities and service providers around the world, including in the United States. The Apple entity responsible for a customer may depend on the customer’s country or region.

Apple retains App Store transaction information according to its legal obligations and business requirements. Apple states that purchase records may be retained for at least as long as the customer maintains an Apple Account and that, for most customers, certain transaction records are retained for at least ten years. Sage. retains the transaction information it receives for the period stated in Schedule B2.

Apple privacy information:

Google Play

Sage. uses Google Play Billing to offer, bill and administer subscriptions on Android devices. The applicable providers include Google LLC and the Google or Google Payments entity responsible for the transaction under the customer’s regional Google Play and Google Payments terms.

Google processes the customer’s Google Account and payment information. When the standard Google Play billing system is used, Sage. does not receive the customer’s full payment-card number, bank-account details or Google Account password.

Sage. receives or may access transaction information made available through the Google Play Billing Library, Real-time Developer Notifications, Google Play Developer API, Play Console and payments reports. Depending on the implemented services, this may include:

Sage. uses this information to verify purchases, provide and restore subscription access, administer trials and renewals, process cancellation or refund status, prevent fraud, provide billing support, reconcile revenue and comply with accounting and taxation obligations.

Google maintains servers around the world, and transaction information may be processed outside the customer’s country, including in the United States and other countries where Google, its affiliates or service providers operate.

Google retains payment and transaction information for the duration necessary to provide Google Play and Google Payments and for additional periods required for taxation, accounting, dispute resolution, anti-money-laundering and other legal or regulatory purposes. Google does not specify one universal retention period for every transaction category and country. Sage. retains the transaction information it receives for the period stated in Schedule B2.

Google privacy information:

Direct billing providers

Sage. does not currently use a direct web-billing or payment-card provider. Subscriptions are purchased and managed through the applicable Apple App Store or Google Play account. If Sage. later introduces Stripe, PayPal, web checkout, alternative billing or another payment provider, that provider and its information handling will be added to this schedule before launch of that payment method.

Subscription management: RevenueCat

Sage. uses RevenueCat, Inc. to validate purchases made through Apple’s App Store and Google Play, maintain subscription and trial status, restore purchases, detect renewals, cancellations and refunds, and determine whether a user is entitled to paid Sage. features.

RevenueCat receives or generates information associated with subscription administration. Depending on Sage.'s configuration, this may include:

Sage. does not provide RevenueCat with journal entries, check-in text, AI prompts, AI-generated reflections or payment-card details.

Sage. shares an account identifier with RevenueCat to match subscription. Sage. does not use an email address, name or readily guessable identifier as the App User ID.

RevenueCat processes end-user information on Sage.'s behalf as a data processor. RevenueCat states that customer data is stored using Amazon Web Services data centres in the United States. Information may also be accessed by authorised RevenueCat personnel and subprocessors where necessary to provide, secure and support the service.

RevenueCat subscription and customer records are retained while the associated Sage. account remains active and for as long as reasonably necessary to verify, administer, restore or support the user’s subscription.

When a user deletes their Sage. account or makes a valid erasure request, Sage. submits a customer-deletion request to RevenueCat promptly and no later than 30 days after the request is verified. RevenueCat processes customer deletions asynchronously and states that deletion through its dashboard or API clears the customer’s RevenueCat data and purchase history.

Limited information may remain temporarily in RevenueCat’s standard backups or archives or where retention is required to comply with law, resolve disputes or enforce applicable agreements. Any such information is restricted to those purposes and removed in accordance with RevenueCat’s applicable retention practices.

Deleting a RevenueCat customer does not cancel an Apple App Store or Google Play subscription. Users must cancel the subscription through the applicable store to stop future renewal. If Sage. terminates its RevenueCat service, Sage. will request return or deletion of customer personal data within 30 days of termination in accordance with the applicable RevenueCat Data Processing Addendum.

Further information:

Schedule B2. Retention and deletion periods

This schedule describes how long Sage. ordinarily retains different categories of information. A longer period applies only where required by law, subject to a legal hold, or reasonably necessary for a documented security, fraud-prevention or legal-claims purpose.

Account profile, authentication and consent records

Account profile information is retained while the account remains active. Following confirmed account closure or deletion, Sage. deletes or de-identifies profile information, contact details, preferences and authentication-account information from active systems promptly and no later than 30 days after confirmation. Information remaining in protected backups expires according to the backup period stated below.

Limited information may be retained separately where required for billing, taxation, security, consent evidence, dispute resolution or legal compliance. Closing an account does not justify continued retention of journals, check-ins, AI conversations or other private wellbeing content for those purposes.

Authentication-event records, including sign-in, sign-out, password-reset, verification, failed-authentication and session-security events, are retained for 12 months after the relevant event for account security, fraud prevention and investigation of unauthorised access. They are then deleted or de-identified. Where an authentication record is relevant to a specific security incident, complaint, investigation or legal claim, the necessary record may be retained until that matter and any applicable review or claim period have ended. The continuing need for that retention is reviewed at least annually.

Evidence of acceptance, consent and withdrawal is retained while the account remains active and for six years after the later of account closure or the last relevant acceptance, consent or withdrawal event. This limited record is retained to demonstrate what the user was told and accepted, honour withdrawals, respond to complaints and establish, exercise or defend legal claims.

Consent and acceptance records are limited to a user or pseudonymous account identifier, the action taken, date and time, consent scope, method of acceptance, applicable Terms, Privacy Policy or consent-notice version, and the resulting processing status. They do not contain journal entries, check-in text, AI prompts, AI responses or generated reflections. Access is restricted to authorised personnel who require it for compliance, dispute resolution, security or legal purposes.

Check-ins, activity history, AI memory and AI outputs

Sage. retains submitted check-ins, check-in notes, activity and practice history, saved check-in reflections, weekly and monthly reflections, and the user’s derived AI memory profile while the Sage. account remains active and until the user deletes the relevant information or account. Cancelling a subscription does not automatically delete this information or close the Sage. account.

The AI memory profile is a plain-text derived record used to provide continuity and personalise subsequent Sage. outputs. Sage. does not use embeddings or vector indexes. The memory profile may contain summaries or inferences derived from check-ins, reflections and activity information and is treated as sensitive personal information.

When a user deletes an individual check-in, Sage. removes the check-in, its associated check-in reflection and bookmark from the user’s account view immediately. Sage. also deletes or regenerates affected weekly and monthly reflections using only the remaining source information and rebuilds or deletes the AI memory profile so that deleted information is no longer included. These changes are completed in active Sage. systems promptly and no later than 30 days after the deletion request.

When a user deletes their Sage. account, access ends when deletion is confirmed. Sage. deletes or de-identifies check-ins, check-in notes, activity and practice history, saved reflections, the AI memory profile, bookmarks, consent-state records, rate-limit records, entitlement-cache records and other associated private or derived information from active Sage. systems promptly and no later than 30 days after confirmation.

On-device personal information remains available while the user is signed in where necessary to operate the app. Relevant local information is cleared when its source content is deleted and all personal local-storage keys are cleared on sign-out or account deletion. Short-lived entitlement and application-cache records do not contain journal text, check-in free text, AI prompts, AI responses or AI memory content. Expired server entitlement-cache records are deleted no later than seven days after expiry.

Sage. does not write successful OpenAI prompts, responses or check-in text to its operational logs. Failed AI requests are logged using limited technical metadata, such as function name, timestamp, HTTP status, safe provider error code and request identifier. Sage. does not retain OpenAI error response bodies or private wellbeing content in routine operational logs.

Deletion from active Sage. systems does not immediately remove information from protected backups or copies already transmitted to OpenAI. Those copies expire under the backup and provider periods described separately below. Following restoration of a backup, Sage. reapplies recorded content deletions, account deletions and consent withdrawals before restored information returns to ordinary use or further AI processing.

Sage. may retain a restricted copy of particular information where required by law or reasonably necessary for a specific complaint, security incident or legal claim. This exception is limited to the information necessary for that matter, does not permit continued AI processing and is reviewed at least annually. Billing and accounting requirements do not justify retaining check-ins, reflections, practice notes or AI memory.

AI provider copies

For the OpenAI Chat Completions API, OpenAI may retain inputs, outputs and related information in abuse-monitoring logs for up to 30 days. OpenAI may retain information longer where required by law or reasonably necessary to protect its services or third parties from harm. Any human access is limited to authorised OpenAI personnel under OpenAI’s abuse-monitoring, safety, security, support and legal processes.

OpenAI currently states that the Moderations API has no abuse-monitoring or application-state retention. Prompt caching associated with Chat Completions may retain encrypted cache data for up to 24 hours.

Sage. cannot recall information already transmitted to OpenAI or individually delete it from OpenAI’s abuse-monitoring logs. When the related information is deleted from Sage. or AI processing is withdrawn, Sage. stops future submissions as applicable, but existing Chat Completions copies may remain until the 30-day period expires, subject to the limited exceptions above.

OpenAI’s no-training default does not mean that Chat Completions data has zero retention. Provider configuration is recorded in Schedule B1.

Technical logs, analytics and support

Security logs: authentication, access-control, rate-limit and security logs are retained for up to 90 days from the event. Records required to investigate a confirmed security incident may instead be retained with the relevant incident record.

Diagnostic and analytics events: operational and diagnostic logs are retained for up to 30 days. Sage. does not currently use third-party product analytics. If analytics are introduced, this schedule will be updated before collection begins.

Support correspondence: routine support correspondence is retained for two years after the support case is closed. Information connected with an unresolved complaint, payment dispute, legal claim or regulatory matter may be retained for the applicable dispute or legal-retention period.

Safety incident records: routine automated safety results that are not escalated are retained for no more than 90 days, or are not separately stored. Records concerning a credible or escalated safety incident may be retained for up to six years after the incident is closed where reasonably necessary to investigate the event, respond to a complaint, meet a legal or regulatory obligation, or establish, exercise or defend a legal claim. Continued retention is reviewed periodically.

Technical logs and incident records are limited to the information reasonably necessary for their purpose. Raw journal entries, check-in text, AI prompts, AI responses and practice-session notes are excluded unless a specific incident cannot reasonably be investigated without them. Any necessary extract is access-restricted and deleted or de-identified when it is no longer required. Legal holds override the ordinary deletion period only for information relevant to the particular matter.

Billing, legal retention and disputes

Transaction and accounting records: Sage. retains transaction and accounting records for seven years after the relevant transaction is completed, or longer where required by applicable tax, corporate or accounting law. These records may include the store or billing provider, pseudonymous customer or account reference, transaction identifier, subscription product, transaction date, amount and currency, tax information, invoice or receipt, refund or chargeback status, and payout or reconciliation records. Sage. does not retain full payment-card numbers received by Apple, Google or another payment processor.

Accounting retention applies only to information needed to document the transaction and Sage.'s financial position. It does not justify retaining journal entries, check-ins, AI prompts, AI-generated reflections, practice notes or other private wellbeing content.

Claims and legal holds: information may be retained beyond its ordinary deletion period where Sage. receives notice of litigation, a regulatory investigation, a binding legal demand, or a credible complaint, dispute or claim for which the information is reasonably necessary. Each legal hold must identify the matter, information covered, responsible decision-maker and reason for retention. Legal holds are reviewed at least every six months and when the matter materially changes or concludes. When the hold ends, information without another lawful retention basis is deleted or de-identified within 30 days.

Health-record retention: Sage. is intended as a general wellbeing service and does not diagnose illness, provide medical treatment or replace professional healthcare. However, whether Sage. is legally classified as a health service provider, and whether any mandatory health-record retention period applies, requires confirmation for the jurisdictions in which Sage. operates. In particular, certain Australian health-record laws may require a health service provider to retain an adult’s health information for seven years after the last health service.

If a mandatory health-record requirement applies, Sage. will retain only the information covered by that requirement for the legally required period. Billing or accounting obligations will not be used as a basis for retaining unrelated wellbeing content.

Backups and recovery

Backup rotation and final expiry: Supabase creates daily backups of Sage.'s production database and retains them for a maximum of seven days. When information is deleted from the active database, a copy may remain in a rotating backup until the last backup containing it expires. Backups are maintained for disaster recovery and are not used for ordinary product operation.

Downstream backup behaviour: Sage. does not ordinarily create manual database exports or off-site copies of production information. Any exceptional export required for migration, incident recovery or provider transition must be approved, encrypted, access-restricted and recorded. It must be securely deleted when its purpose is complete and no later than 30 days after creation, unless a documented legal obligation requires longer retention.

Access during retention: backup access is limited to authorised Supabase personnel operating under provider security controls and designated Sage. administrators who require access for disaster recovery or an approved migration. Backups must not be accessed for product analytics, staff browsing, AI training or routine customer-support purposes.

Restoration control: a restored backup is treated as potentially containing information deleted after the backup was created. Before ordinary user access, AI processing, scheduled jobs or other background processing resumes, Sage. places the restored system in restricted recovery mode and reapplies all account-deletion, individual-entry deletion and AI-withdrawal actions recorded after the backup timestamp.

Sage. maintains a restricted recovery ledger outside the restorable production database. The ledger contains only the pseudonymous account reference, action required, timestamp and completion status necessary to prevent deleted or withdrawn information from returning to use. After the required deletions and consent states have been reapplied, Sage. validates the restoration before returning the system to ordinary operation. Any temporary restoration or recovery environment is deleted within seven days after validation.

Deletion confirmation

Sage. acknowledges an authenticated account-deletion request immediately through the app or as soon as reasonably practicable through the reporting channel. Sage. provides a deletion-completion notice without undue delay and ordinarily within 30 calendar days after receiving and verifying the request.

The completion notice identifies:

Retained information may include, where applicable:

Only the minimum information required for the applicable purpose is retained. Accounting, audit or legal retention does not justify retaining unrelated journals, check-ins, reflections or other private wellbeing content.

The notice does not state that all information has been permanently erased while provider copies, backups or legally retained records remain. Once the stated backup and provider periods expire, no further confirmation is required unless the user requests one or Sage. becomes aware that deletion was not completed as described.

B17. Additional EEA and UK privacy information

Where the GDPR or UK GDPR applies, Brenton Darvill trading as Blessed B Studios is the controller for the processing it determines. Contact privacy@trysage.com.au.

Our bases are contract necessity for essential account and subscription administration, consent for specified wellbeing and AI processing and for optional marketing where required, legal obligation for specified mandatory records, and legitimate interests for proportionate security and fraud prevention after balancing rights. Special-category processing also requires an Article 9 condition. Explicit consent is the basis for check-ins and associated AI reflections.

Subject to the conditions in applicable law, you may request access, correction, erasure, restriction and portability, object to relevant processing and withdraw consent without affecting earlier lawful processing. You may object to direct marketing at any time. Contact privacy@trysage.com.au. We respond within the applicable statutory period. Where a lawful extension is needed, we notify you within the required period. You may complain to the supervisory authority in the relevant EEA country or the UK Information Commissioner.

Acceptance of this policy is not a substitute for a lawful international-transfer mechanism.

B18. United States consumer health data

Sage. does not sell private wellbeing information, share it for targeted advertising, or use geofencing to identify people seeking health services.

Contact

Privacy Officer

Brenton Darvill trading as Blessed B Studios

ABN 24 334 813 190

Email: privacy@trysage.com.au

A postal service address has not yet been published. Please use the email above.