Ownership &
Support

Your code can move with you

After final payment, we provide the completed website source code and the rights stated in your signed agreement to use, host, deploy, maintain, and modify the project-specific custom website. You can manage it yourself or hire another provider; continued management by FreeLifter is never required.

Domain name and renewals

Our preferred approach is for you to purchase the domain through an account owned and controlled by your business. You are responsible for the registrar’s purchase price, recurring annual renewal charges, optional domain-privacy charges, taxes, and any other registrar fees.

If we purchase or configure a domain for the project, the proposal or agreement identifies the cost and who pays it. After final payment, we transfer the domain to your registrar account or place the account under your control, subject to the registrar’s transfer rules and any mandatory waiting period. You are responsible for keeping payment and contact information current after handoff so the domain does not expire.

Netlify project handoff

For a website hosted on Netlify, we can create or use a client-controlled Netlify team and make you a Team Owner. Where Netlify permits it, we transfer the project to that team and verify the production domain, deployment settings, environment variables, and billing responsibility with you. Netlify plan limits, transfer eligibility, and charges apply.

You decide our post-handoff access. We can be removed entirely, or—if you choose ongoing management—you can invite or retain us in an appropriate Netlify role with only the access needed for agreed updates. Because Netlify assigns ownership at the team level, “client ownership” means your business controls the team, its billing, its members, and the project within it.

Complete handoff

We provide or transfer the final source files, agreed source-code repository access, deployment information, domain control, and applicable service accounts. We verify that you can access the live project before handoff is considered complete. Credentials are not published in the source code; when a service uses private credentials, we coordinate a secure transfer or help you replace them with credentials from your own account.

Third-party software, open-source libraries, fonts, stock media, platforms, and services remain subject to their own licenses, terms, plan limits, and fees. Pre-existing or reusable tools, if any, are addressed separately in the signed agreement.

Ongoing support — custom quote

Support scope, update allowances, response expectations, hosting responsibilities, fees, and cancellation terms are agreed in writing. No fixed monthly price or delivery window is published.

Managed operations — custom quote

Any ongoing hosting, integration work, workflow maintenance, and third-party costs are scoped and quoted for your project. Access and responsibilities are agreed before service begins.

Small updates and exclusions

A small update means text, an image replacement, a link, or a change to existing-page content. It does not include new pages, new sections, layout or design revisions, copywriting, SEO work, new functionality, or third-party troubleshooting.

Neither care plan includes unlimited edits, unlimited support, or open-ended design and development. Plan details, billing, access, and cancellation terms are confirmed in writing. The client remains the owner of client-controlled accounts and can change or revoke our access.

Before work begins

We confirm the scope, code rights, payment milestones, launch, handoff, and support terms in writing. Both parties sign the project agreement and the deposit is paid through a secure electronic invoice before we present the creative direction or begin the build.

Recurring care-plan payments are authorized directly through Square or another selected payment processor. Payment credentials belong only on the processor's secure payment page and should never be sent through ordinary email or included in project documents.