MinhVuTechBUILD WHAT'S NEXT

MINHVUTECH / POLICIES

Clear information.
Agree before work starts.

The website stores project requests and account data on its hosting database to process requests and provide project tracking. Commercial terms marked as drafts must be agreed in a quote or contract.

01

Current privacy practices

When you submit a request, the website stores your name, email, organization (if provided), service, tasks, budget, timeline and project description in SQLite on the hosting account to handle the inquiry and provide progress updates. Authorized admins can access requests; signed-in customers can only view requests linked to their account.

The sign-in session uses a secure authentication cookie. Theme preference is stored in your browser. This site does not use analytics or advertising cookies.

Be Vietnam Pro and DM Mono are loaded from Google Fonts, so your browser requests font files from Google. If you send an email, its contents are processed by your email provider and the recipient’s mailbox.

Customer registration, sign-in, project requests and progress updates are available in the portal. Passwords are stored as hashes. New email/password accounts require a one-time email verification code. Google sign-in receives your verified email, name and profile photo with your consent; the site stores your email and name for account access, but does not store your photo. Automatic password reset is not available; contact [email protected] for account help.

02

Data and support requests

Do not send passwords, payment data, identity documents or sensitive information through a project inquiry email. For questions about information you emailed, contact [email protected].

Data is kept while a request is being handled or until a deletion request; the MVP does not yet automatically delete records. To request access, correction or deletion, contact [email protected] with your account email/request ID for verification. The hosting provider processes data to deliver the website. Do not include passwords, payment details, identity documents or access secrets in project descriptions.

03

DRAFT · TO BE AGREED

Scope, acceptance and warranty

Each quote should define deliverables, page or feature count, client-provided content, handover milestones, acceptance criteria, revision rounds and support scope.

The warranty period has not been confirmed. A specific warranty commitment should appear in a quote or contract only after both parties agree.

04

DRAFT · TO BE AGREED

Pricing, payment, cancellation and refunds

Prices on the services page are starting prices, not fixed prices for every scope. API, hosting, domain, AI model and third-party costs should be itemized before work starts.

Payment schedule, deposit, scope changes, cancellation and refund terms must be stated in the quote or contract. This website does not promise a general refund policy.

05

Concepts, content and updates

Images marked “Concept” are AI-generated illustrations. They do not prove a system has been built or accepted by a client. The client portal is deployed on the live website; concept images are illustrations and do not represent screenshots of the operating interface.

Last updated: October 12, 2026. Contact: [email protected].

Ready to define the real scope?

Send a request to discuss your project and receive a quote before work begins.

Create a request ↗