UGC247 · Website policies
Privacy policy
How the UGC247 marketing website handles enquiries and visitor information.
1. Who this policy covers
This policy is for the UGC247 marketing website and enquiries sent through it. “UGC247”, “we” and “us” refer to Zac William Goodall, ABN 91 446 902 759, an individual/sole trader based in Queensland, Australia, operating UGC247.
For privacy, access, correction or complaints, contact zac@ugc247.com. Business registration details can be checked on ABN Lookup.
Creator accounts, brand programs, uploaded content, messages, Shopify attribution and payouts are separate platform activities. See the platform privacy notice. A merchant's store also has its own privacy policy.
2. Information collected here
- Enquiries: your name, email address, phone number and message, plus any brand name, store URL and service interest you provide.
- Follow-up correspondence: information you provide when discussing an enquiry or proposed service.
- Connection information: hosting and external asset providers receive technical request information, such as an IP address, browser details and the requested resource, when delivering the site.
- Contact-form metadata: the form handler derives a hashed value from the forwarded IP address, when available, and includes it in the enquiry record. Hashing does not necessarily make this anonymous, and a hosting provider may separately process the original IP address.
You do not need to create an account to browse. The current enquiry form requires a name, email, phone number and message; without them it cannot submit. You can instead email an enquiry or privacy request. Please do not send passwords, card details, identity documents or sensitive information through the form.
3. Why information is used
Enquiry information is used to understand your request, reply by email or phone, prepare and discuss a proposal, and keep a record of the conversation. Technical information supports site delivery and investigation of technical or security issues.
The current form sends an enquiry, not a newsletter subscription. It does not contain a marketing opt-in or an automated newsletter enrolment. Any separate marketing use must have an appropriate basis and an available opt-out; sending an enquiry is not blanket permission for unrelated marketing.
4. Service providers and disclosures
The website's current implementation is configured to use the following services. Production account settings and access arrangements still need verification:
- Vercel — hosting and the enquiry endpoint
- Delivers the production website and runs the contact handler. Requests and operational logs may contain connection and error information.
- Supabase — enquiry records
- The contact handler attempts to store the submitted fields, a source label and the hashed IP value in the contacts database for the UGC247 team to review.
- Resend and the receiving mailbox provider — email delivery
- The handler also attempts to email the submitted enquiry to the configured team mailbox, including your email as the reply-to address. Copies may exist in both the database and email systems.
- Google Fonts, cdnjs and unpkg — website assets
- Supply fonts and animation libraries. Loading those resources makes a direct request from your browser to the relevant provider. See the cookies and website technologies notice.
People authorised to handle enquiries may receive the information needed to do so. Information may also need to be disclosed where required or authorised by law. The enquiry handler does not contain a sale-of-data or advertising-audience export; wider business practices must be confirmed before publication.
5. Storage and overseas processing
Information can be held in the contacts database, recipient mailboxes and provider logs or backups. Providers may process information outside your country. The country of the database, mailboxes, hosting functions and provider support access has not been verified for this draft.
Before publication: confirm the relevant recipient countries, account regions, contracts and any cross-border safeguards, then replace this review note with the actual arrangements. Do not assume all information stays in Australia.
6. Retention and security
Different copies of an enquiry can have different retention settings. A deletion from the contacts database does not by itself remove mailbox copies, logs or backups.
Before publication: approve and implement retention periods or clear retention criteria for unsuccessful enquiries, client records, mailboxes, IP metadata, logs and backups. Confirm access controls, staff access, deletion procedures and incident response. This draft does not promise a fixed deletion period or security controls that have not been verified.
No online service can guarantee absolute security. Do not include information in an enquiry that we do not need to respond.
7. Access, correction and privacy requests
Email zac@ugc247.com with a description of your request and enough information to locate the relevant enquiry. You may request access, correction or deletion, subject to applicable law and any legitimate recordkeeping requirements. A request may require proportionate identity checks; do not send identity documents unless a suitable method has been agreed.
The proposed process is to review the request, explain the outcome and any lawful limits, and provide a way to follow up. The owner must confirm who handles requests and the applicable response deadlines before this policy takes effect.
8. Complaints and changes
Send privacy concerns to zac@ugc247.com, including what happened and the outcome you are seeking. The proposed process is to acknowledge the complaint, investigate it and provide a written response within a reasonable time. Where Australian privacy law applies, the OAIC generally recommends allowing the organisation 30 days to respond before escalating.
If the issue is unresolved, you may be able to contact the Office of the Australian Information Commissioner or the relevant regulator in your jurisdiction. Available rights depend on the laws that apply.
The effective date will be added after approval. Future versions should reflect actual changes to information handling and be made available here; publishing new wording does not itself authorise a new use of information.
Drafting reference: OAIC — privacy policy contents.