As of August 24, 2026. This policy defines the access and operating baseline for Shopify work performed by HansonCore, LLC DBA Five Acre Code.
Approved access methods
Use the narrowest practical method for the deliverable:
- A Shopify collaborator account with only the required store permissions is preferred for ordinary Client-store access.
- An appropriately scoped named staff account can be used when a collaborator account cannot perform an agreed task.
- Shopify's Theme Access app can provide theme-only access for Shopify CLI work without granting broader Shopify admin permissions.
- A Client-owned GitHub repository and Shopify GitHub theme integration can be used when the release and bidirectional synchronization behavior is understood and included in the scope.
- App, API, provider, domain, or repository access requires separate authorization and only the permissions required for that work.
Five Acre Code will not ask for or use the Client's shared Shopify login credentials. Do not create or send a shared Shopify owner account. Do not send passwords, access tokens, payment credentials, customer passwords, session cookies, or recovery codes through the public contact form, ordinary email, issue titles, screenshots, or source repositories.
Permission and access lifecycle
The Client authorizes the requested permissions and remains responsible for store-owner and staff administration. Five Acre Code will use access only for the agreed work, limit it to assigned personnel, and notify the Client if broader access becomes necessary.
Five Acre Code will remove its collaborator access and delete or return locally held access material when it is no longer needed, subject to required security evidence and the written agreement. The Client must remove or reduce remaining staff access, Theme Access passwords, repository tokens, provider invitations, and other Client-controlled permissions after the work or support period ends.
Development themes and source control
Theme changes should normally be developed in a Shopify development theme, unpublished theme, or agreed preview branch. The Client must identify the authoritative theme and whether Shopify-admin edits, Git commits, vendor updates, or another system can change it.
Shopify's GitHub theme integration can commit admin changes to the connected branch and update Shopify when the branch changes. The Client and Five Acre Code must agree on connected repositories/branches, production publication, who can merge, and how admin edits are handled.
Five Acre Code can create a working copy or repository for the project. Ownership, handoff, archival, and deletion follow the written scope. The Client remains responsible for licensed theme/vendor source and any restrictions on copying or distribution.
Testing and publication
The Client will provide representative products, variants, collections, markets, languages, B2B/customer contexts, discounts, subscriptions, apps, payment/shipping settings, and content needed for acceptance.
Five Acre Code tests the agreed scenarios and environments. The Client remains responsible for business acceptance, content accuracy, prices, inventory, taxes, shipping, payments, legal notices, app charges, and publication approval.
Five Acre Code will not publish or make another consequential production change without authority in the written scope or an authorized Client approval. Emergency live changes require documented authorization and can carry greater risk than the standard preview/release workflow.
Backups and rollback
Before consequential theme work, confirm an available original/live theme version, repository state, duplicate, export, or other recovery path appropriate to the store. Shopify theme copies do not back up products, orders, customers, files, apps, markets, domains, or external systems.
The Client remains responsible for complete business continuity and data recovery. Five Acre Code's release notes or theme rollback path are not a substitute for a store-wide backup or incident plan.
Content, rights, and compliance
The Client represents that it has the rights to all themes, designs, fonts, media, copy, data, apps, code, trademarks, and instructions supplied for the work. The Client is responsible for accessibility and privacy requirements, consent, product claims, advertising, taxes, returns, subscriptions, regulated goods, customer communications, and other legal obligations.
Five Acre Code can flag technical or usability risks but does not certify legal compliance or replace qualified legal, accounting, tax, accessibility, payment, or security advice.
Third-party changes
Theme vendors, apps, Shopify, browsers, consent tools, analytics, and integrations can change the storefront independently. Notify Five Acre Code about planned theme updates, app installs/removals, code edits, checkout changes, domain changes, or major content releases that overlap active work.
Concurrent changes can invalidate tests, overwrite work, or require re-scoping. Preserve the affected state before attempting multiple repairs.
Questions
Contact support@fiveacrecode.com before granting access if the appropriate permission set or access method is unclear.