This policy describes the service built for House of Graveleaf and the information it uses. Updated 13 November 2026.
Your Graveleaf sign-in is shared across the House and Grove. Their profiles serve different purposes. In your House profile you may save a display name, biography, disciplines, optional country and time zone, rights-organisation notes and a profile photo. Photos are cropped and resized on your device, converted to JPEG and saved with your profile; the original file and its metadata are not uploaded. These details stay in your account and are not a public directory entry. Location is not detected. A separate, optional marketing preference records your choice and when it changed; sending is not configured. Profile data is included in account export and removed through account deletion, subject to the existing account conditions.
House of Graveleaf is a Sydney-based artisan business founded by Joel Wallbank-Hutton. Use the signed-in privacy enquiry form to request access, correction, deletion or a response about data use. Replies are available in the same account. Formal business contact and programme details will be confirmed before paid enrolment opens.
Sign-in supplies a site-specific account identifier and account email. Applications collect your name, confirmation that you are 18+, experience, practice, performance links, reflective answers and acknowledgement versions. We use these to assess readiness and retain an admission decision. We do not ask for identity documents, exact date of birth, health information, political views or religious beliefs.
Member records include verified subscription references and paid-through dates, a nominated companion email and account link, task evidence, feedback and service enquiries. AI projects store the brief you submit, generated drafts, provider name and token usage. Usage records support allowances, billing reconciliation and service-budget limits.
Application and enquiry forms explain collection at the point of submission. Providing the application information is necessary to assess admission; you may browse without applying. AI use is optional and requires a separate confirmation when sending a brief. Companion invitations are optional. We do not add you to marketing lists through these forms.
You can access your own account records. The verified guild owner can review applications, subscriptions, evidence and enquiries. Companion accounts cannot see a student’s private application, task submissions or conversations. AI project drafts are private to the account that created them and are not shown in the owner review console; a technical service operator may require limited access for support or incident response.
If you request application research, you supply your professional name and up to three public music portfolio URLs and explicitly permit retrieval and AI processing. The assistant fetches permitted public text from approved professional sites, respects automated-access rules and does not bypass logins or paywalls. It does not independently search personal accounts or infer sensitive traits. Text is used as source material for an editable, cited professional summary, not an admission decision.
The draft and source citations are saved privately for your review. Retrieved excerpts are processed transiently rather than retained as a separate scraped dossier. The owner receives a summary only if you check it, correct it and choose to include it in your application. Source claims are not independently verified credentials. You may instead provide your own written answers and performance evidence. Research drafts are included in account export and removed by account-data deletion.
When AI generation is enabled, only the project brief you explicitly submit and the tool’s instructions are sent to the configured provider. Applications, private conversations and complete account histories are not automatically sent. The separate optional application-research workflow sends only your requested professional name and permitted source excerpts after explicit consent. The workspace identifies the active provider before generation. The guild does not use submissions to train its own model.
The AI provider’s own processing, retention and training terms depend on the service configured. Provider details must be published before activation. Do not send sensitive or confidential information or unpublished third-party work without permission. The current architecture uses hosted API processing; local AI hosting is a future option.
Hosting, database and sign-in infrastructure are supplied through Sites and Cloudflare/OpenAI services. Fonts are loaded from Google Fonts. These services receive connection or account information under their own policies and may process information outside Australia. Exact AI processing locations depend on the selected provider and deployment. Skool separately handles subscriptions and community activity under its own policies; this site does not collect card details.
Submitting your material does not assign its copyright to the guild. You permit the processing reasonably needed to assess your application, provide the requested tools and administer membership. This does not clear third-party rights or guarantee ownership of an AI output. Do not submit material you cannot lawfully share. Public portfolio use of a student’s work requires a separate permission.
Admission eligibility is retained so approved members can return without repeating assessment while in good standing. Applications, evidence and projects remain associated with your account until removed through the data controls or an agreed privacy request; retention will be reviewed as the programme develops. Use your account to export records and delete saved drafts.
Account deletion removes your application, approval, evidence, drafts, enquiries and companion links. If your paid term is still active, first cancel on Skool and allow the term to end, or contact the guild for assistance. Deleting your approval record means reapplication will be necessary. Minimal usage and action records are anonymised for cost reconciliation. Provider, backup and Skool records have their own retention processes.
Account access is checked server-side. Secret provider keys are never included in browser code. The site uses essential sign-in storage; completed entry acknowledgements are remembered on this browser for one year, unless the policies change or cookies are cleared. No advertising pixels or optional visitor analytics are configured. Privacy concerns and corrections can be sent through the enquiry form. Material changes will be reflected in the dated policy and relevant collection notices.
This is the service’s operational data policy, not a claim of legal certification. Australian privacy guidance: OAIC collection guidance.
Task publication asks for a public artist name, public work link and optional note, with a separate publication acknowledgement. These fields, the task, publication date and member-declared grade appear on the work register to site visitors. Your private application, email and account records are not published. You can edit or withdraw a listing from your account; your grade recalculates from remaining published tasks. Existing private evidence is not made public automatically. The site currently retains its existing private launch audience; the work you link should already be publicly accessible.
Your project titles, target dates, music-session details, track stages, artistic-development notes, practice records, release plans, asset links and task board are stored privately against your account. They are included in your data export and removed when your guild account data is deleted. They are not sent to an AI provider by saving the workspace.
A necessary HttpOnly cookie identifies an anonymous entry record. We store its random-token hash, acknowledgement stage, policy version, reading-pause start and expiry. Unfinished records expire after 24 hours; completed acknowledgements and their cookie expire after one year. A policy-version change requires fresh acknowledgement. Clearing cookies or using another browser requires induction again. This records browsing acknowledgements; it does not create membership or make an admission decision. No identity or device fingerprint is collected for this entry check.
Coaching enquiries store your service focus, goal, current practice, format preference, availability and adult/collection acknowledgements with your signed-in identity. The owner replies privately in your account. An enquiry does not make a booking, take payment or subscribe you to marketing.
Assigned learning stores a lesson snapshot, learning outcome, your reflection, an optional authorised HTTPS work link, the latest instructor feedback, completion state, revision and timestamps. These records are private to you and the authorised owner instructor. A companion does not inherit access. Assignments are included in account export and removed when your learner account data is deleted; minimal audit records follow the existing anonymisation process. Lesson text is preserved as assigned even if the library changes.
Neither these records nor linked work are sent to AI automatically. No audio is uploaded or analysed by this lesson workflow. The current system retains the latest feedback response rather than a complete history of previous feedback text. Completion is an educational record, not guild recognition or a formal qualification. Request corrections through the private enquiry channel. Share no medical, account-security or other sensitive information.
The Rights pilot stores composition titles, proposed writer names and shares, permission or agreement reference links, user-entered identifiers and source notes, and separate recording metadata. Status events include your reason, source/reference, reported external date and the time you recorded it. Metadata amendments retain prior snapshots in your private change history.
Your full catalogue is accessible through your own authenticated account; another artist or the ordinary owner dashboard cannot browse it. A separately shared split snapshot has the limited scope described below. The optional split-review workflow shares only the composition title, alternative title and proposed writer names, roles and percentages with email accounts you explicitly nominate. Invitation links do not grant access without the invited signed-in email. No message or Site access grant is sent automatically. Pending invitations expire after seven days. Responses are account acknowledgements, not independently verified identity or legal ownership. Do not store information about someone else without permission, or include credentials, one-time codes, bank details or secret-bearing links. Saving a link does not fetch its contents or send data to AI or a rights society.
Catalogue export includes compositions, recordings and event history. Account deletion removes these records under the existing account-deletion conditions. Archiving a composition changes its local status and does not delete it. Submitted and confirmation statuses are user-attested, not official verification or proof of ownership. No copyright assignment, royalty collection or external submission occurs.
For split review, we store the invited email, named writer, proposal snapshot, version, expiry, response, optional note, signed-in responder identifier and response time. The catalogue owner sees the response and note. Reviewers do not see other invited emails, private notes, agreement links or recordings. A metadata amendment invalidates the proposal for the current record; prior responses remain attached to their old version. An approved writer may raise a dispute.
Account export includes your own review invitations and responses. If you delete your account, your invitation identity and response note are removed from other catalogues and the response is marked withdrawn, so it no longer contributes to approval. Shared writer names originally entered by another artist may remain in that artist’s own catalogue; use the correction/privacy enquiry process for concerns about that information. Deleting the catalogue owner’s account removes its proposal and response records. Keep your own preparation export if you need a copy; this service is not a permanent legal evidence archive.
A Rights document reference stores its title, type, source, document date, optional HTTPS link, private note, active/withdrawn status and amendment reason. Previous metadata is retained in your private change history. No linked file is fetched, uploaded, inspected, hashed or verified by this reference ledger.
A preparation snapshot preserves composition metadata, linked recording metadata, document references, a user-reviewed checklist and limited response receipts. It omits invited email addresses and private response notes from those receipts. It is a historical private administrative record, not a verified legal agreement, rights determination or society registration. The current-catalogue check identifies later metadata/reference/response changes; no external record is changed by preparing or downloading it.
Snapshots are included in your catalogue and account exports and removed with your catalogue account under the existing deletion conditions. If a reviewer withdraws or deletes their response, an earlier snapshot may retain the historical decision and writer name originally entered by the catalogue owner, but it no longer matches the current response state. Contact the guild about corrections or retention concerns. This pilot does not replace your own safe copies or any required retention arrangements.
The members-only Forum stores posts, replies, chosen artist names, movement manifestos, voluntary movement participation, artistic challenge invitations and responses. These can reveal views you choose to express. Political activity is optional, does not affect grades, and is not used to infer political affiliations or build political profiles. Do not publish someone else’s private information.
Active members and adult companions can read member-visible material. Movement participant lists are not displayed; the Forum shows a count and your own participation. Stewards manage their own manifestos and invitations, not other members’ accounts. Reports and moderation reasons are available to the owner for review; reporter identity is not shared with other members.
Public previews and weekly selections require the post author’s separate, explicit permission. Permission covers the chosen artist name, title and preview, and possible editorial publication of the full post. Member discussion replies are not automatically included. Editing invalidates an existing feature; withdrawing or removing public permission removes current public visibility. Copies already read, indexed or made by others cannot be recalled.
You may leave movements and withdraw your own contributions. Account export includes your own Forum records; account deletion removes participation and report records and withdraws and clears your authored Forum content. Other artists retain control of their own contributions. No Forum content is sent to an AI provider by these features. External artwork links are not fetched or scanned by the guild; opening them uses the external provider’s services.
Member Support stores your account identity, message text, sender role and timestamps to provide support. Joel, the founder, can read and respond; other members cannot access your conversation. Messages are not sent to an AI provider or used for advertising by this feature. Your full conversation is included in account export and removed with account deletion under the account controls. The panel shows the latest 100 messages. Live availability is temporary and expires when the owner stops attending the inbox. Replies are delivered in the app; no email or push notifications are connected.
Grove Android and the website use the same House account service and backend. Android sessions are stored privately on the device; browser sessions are separate. Email sign-in is verified by Supabase with House-branded email delivery. Linking an older sign-in requires proof of both identities; email matches alone never merge records.
Grove is free to join separately from paid House membership. Creating a Grove profile publishes your chosen handle, artist name, bio and practice. Posts, replies, communities, movements and published product listings are public. Private House records, email addresses, applications and billing details are not automatically copied into Grove. You may preview and select your House display name, biography and practice to copy into a Grove draft. Nothing is published by that import; you review and save the Grove profile separately. Linking the same authenticated House identity is optional; public membership and earned-grade display require a separate choice and reflect the current ledger.
Grove stores follows, likes, voluntary community participation, blocks, reports and purchase enquiries. Membership rosters are not public. Purchase enquiries are visible to the buyer and seller; they do not charge a payment, reserve stock or arrange fulfilment. Founder moderation can review reports and remove content. No movement affiliation is inferred, no ideology scoring is performed, and no commerce analytics or investment programme is enabled. Moderation reports may be retained without a linked reporter identity after profile removal. Your own Grove records are available through account export. You can remove Grove separately without cancelling House membership; community purpose statements you published may remain with the owner removed when your Grove account is deleted.
Grove stores uploaded images and videos in private object storage, with file descriptions, type, size and ownership records. An upload becomes publicly readable when attached to published work. Withdrawing or moderating that work removes public access through Grove; deleting the upload or Grove profile removes the stored file. Published files can retain embedded metadata. Unused uploads stay private until you remove them.
Connected Shopify shops use merchant-authorised storefront access. Grove encrypts its stored Storefront token and does not retain a Shopify Admin API token. Physical-goods checkout uses Shopify; Android presents Shopify’s Checkout Kit. Shopify and the artist’s store process checkout information, including delivery and payment information and technical connection data. Grove does not store your card details or claim an order is paid merely because checkout opened. Shopify and merchants have separate privacy, order retention and fulfilment responsibilities.
