CustomBuilds

Legal

Privacy Policy

This policy describes the information CustomBuilds actually collects through the current website and admin platform. It does not claim collection that the application does not perform.

Version 2026-08-14 · Last updated August 14, 2026

01Who we are

CustomBuilds is a software and web development studio. This policy covers the public website, project inquiries, and the staff-operated admin platform.

Contact: custombuilds.dev@gmail.com. Address: [BUSINESS ADDRESS].

02Information you submit

Project inquiries collect name, email, optional company, project type, optional budget, optional timeline, and your message. Submission also records that you accepted the Terms of Service and this Privacy Policy, including the version dates and a timestamp.

FiveM custom script requests collect name, email, optional Discord username, optional script or project name, description, optional features, budget, timeline, and additional notes. Those submissions are stored as inquiries and FiveM request records for staff review.

Staff may later create customer records, quotes, invoices, payments, support tickets, project notes, FiveM orders, licenses, and download records. Those records contain the business details staff enter or that a verified purchase creates, such as name, email, company, phone, and notes.

03Customer accounts

Customer portal accounts, when created by staff, store an email and a link to the related customer record. CustomBuilds does not collect passwords through the public inquiry form.

Staff accounts use Supabase Auth. Passwords are handled by that authentication service, not stored in CustomBuilds application tables.

04Quotes, invoices, and payments

Quotes and invoices store line items, amounts, status, and related customer or project identifiers.

If Stripe is configured, payment processing is handled by Stripe. CustomBuilds stores payment status and processor references needed to reconcile a payment. Card numbers are not stored in CustomBuilds tables.

FiveM marketplace checkouts store the email used at purchase, order status, and, after webhook confirmation, a license record. Download events store that a licensed file was retrieved, without publishing storage URLs.

05Support requests

Support tickets store the subject, message, status, and any customer or staff assignment entered in the admin panel.

06Website analytics

If you accept analytics, the site may record first-party page views: path, referrer, a session identifier cookie, and a coarse device/browser category derived from the user agent. This is used in the staff analytics view.

If a Google Analytics measurement ID is configured and you accept analytics, Google Analytics may also receive page views and standard engagement signals such as pages used, approximate traffic, referrals, and device information provided by that platform.

If you decline analytics, CustomBuilds does not load Google Analytics and does not send first-party page-view events. If no measurement ID is configured, Google Analytics is not loaded regardless of consent.

07Cookies and local storage

Authentication cookies are used so staff can stay signed in to the admin panel. Those are necessary for that function.

If you accept analytics, a first-party session cookie may be set so page views are not double-counted in a short window.

Your analytics choice is stored in local storage on your device so the banner does not reappear on every visit. You can change that choice from Cookie preferences in the footer.

08Security and server logs

The application may log errors and apply rate limits on public forms. Rate limiting can use a network address supplied by the hosting platform.

Supabase may retain authentication and database access logs as part of operating the backend. CustomBuilds does not operate a separate secret-capture or keystroke log on the public site.

09Third-party services

Depending on configuration, CustomBuilds may use Supabase for database and authentication, Stripe for payments, and Google Analytics for consented website measurement.

Those providers process data under their own policies. CustomBuilds does not sell inquiry or customer records.

10How we use information

Inquiry and customer information is used to respond to project requests, scope work, bill, support, and operate the studio, including the FiveM marketplace.

Analytics, when consented, is used to understand which public pages are visited. CustomBuilds does not fabricate analytics numbers.

11Retention

Inquiry, customer, billing, and support records are kept while they are needed to run the business and meet legal or accounting obligations.

Consent records keep the Terms version, Privacy version, timestamp, and related inquiry identifier so a later policy update does not erase what you accepted. Current Terms version: 2026-08-14. Current Privacy version: 2026-08-14.

12Your choices

You can decline analytics and still use the public site and contact form.

To ask about access, correction, or deletion of inquiry or customer records, contact custombuilds.dev@gmail.com. Some records may be retained where the studio is required to keep them.

13Children

The site is intended for business inquiries. CustomBuilds does not knowingly collect personal information from children through the public forms.

14Changes

This policy may be updated. The current version is 2026-08-14. Historical consent records keep the version that was accepted at the time.

15Contact

Privacy questions: custombuilds.dev@gmail.com.

Mailing address: [BUSINESS ADDRESS].