Privacy · administrator and legal review required
How OZ AI FINDER handles information.
This noindex draft describes data flows visible in the application code. The legal operator, retention rules, provider locations and request-handling process still need confirmation before publication.
Who operates the service
Business identity still needs confirmation
OZ AI FINDER is powered by Oz Retail Group and is based in Hervey Bay, Queensland, Australia. The supplied business structure is sole trader, but the legal operating name and ABN have not been provided. This draft does not identify a legal entity or claim a registered business name, company or registered office.
The public privacy contact supplied for this draft is matty@ozretail.group. The mailbox still needs to be verified as monitored for privacy enquiries.
Information collected
What you provide and what the audit reads
The free audit form collects a business name, website address, business category, town or suburb, Australian state, postcode and email address. A customer question is optional. Marketing consent is optional; the application records the consent wording, version, source and time.
The audit crawler requests a limited sample of publicly accessible pages on the submitted website. The application stores the audit status, score when enough evidence is available, checks, evidence and information about sampled pages. The audit is not a live query of AI-platform recommendations.
After a paid Website Improvement Plan purchase, onboarding collects a contact name, phone number, primary services, service areas and customer questions; website platform and additional context are optional. Business name, website and email are carried forward from the audit. The service does not ask for website passwords or login credentials.
Use and sharing
How information is used and which providers are involved
Information is used to run the requested audit, prepare and display its report, administer paid onboarding, fulfil the Website Improvement Plan and send service-related messages. Declining marketing consent does not stop an audit or its transactional result messages.
MailerLite receives marketing contact data and audit fields. A new contact is sent only after optional marketing consent and is left unconfirmed for MailerLite’s confirmation process. For an existing subscriber, audit fields may be updated without changing their group or subscription status. The application does not send MailerLite campaigns or automation emails.
Resend sends transactional service emails, including audit and paid-onboarding notifications. Stripe handles the paid checkout. The application stores order and payment status, amount, currency, customer email and payment references; its order records do not include a payment-card number.
Clerk provides administrator sign-in. Customer records are visible through protected administrator functions. Replit provides the application environment, and the application uses a PostgreSQL database for lead, audit and order records. The provider locations and any international data transfers have not been confirmed.
Browser storage and report access
Session data, cookies and private links
The browser stores an audit access credential in session storage so the customer can view the report. The database stores a hash of the initial credential rather than that raw credential. Some completed-report email links contain a signed, time-limited access token; the current implementation limits that token to 30 days after audit completion.
The app also stores a small cookie for the administrator sidebar preference. Clerk manages administrator sign-in and its browser session. The application source reviewed for this draft contains no analytics or advertising-pixel integration; confirm whether any platform-level measurement is enabled separately.
Do not forward a private audit or onboarding link to anyone who should not see the associated information. Administrator and customer report access controls are separate.
Storage and requests
Retention, access, correction and deletion
The application uses a PostgreSQL database for lead, audit and order records. Operational logs record technical request metadata. The code reviewed for this draft does not define public data or log-retention periods, or provide a self-service data export or deletion feature.
For access, correction, deletion or other privacy enquiries, email matty@ozretail.group. The mailbox, request-verification steps, handling process and response timeframe must be confirmed before publication. This draft does not promise a deletion outcome or a particular response time.