How Amblet Handles Website, Buyer, and Customer-Request Information.

Information Amblet collects

The buyer application collects business and buyer-criteria information. The customer project request collects contact information, general commercial-property location, property and service categories, project stage, timing, scope, contact preferences, authorization, and consent records. Basic technical information may also be used for security, duplicate prevention, and rate limiting.

How the information is used

Amblet uses buyer information to review buyer fit and confirm criteria and to create a private buyer-application record. Amblet uses customer-request information to review completeness, service and territory fit, permission, and possible provider coverage; contact the requester; create a private customer-request record; and coordinate a permitted next step when a potential fit is identified. Neither form creates an automatic charge or automatic delivery.

Private service providers

When privately configured, the server may send records to customer-relationship management and email systems used by Amblet. Buyer applications may also use a private workspace and private Discord notification. Customer requests are not routed to the buyer-application workspace or Discord notification. Customer phone numbers and email addresses are excluded from public pages and analytics events.

Customer information

Protected customer contact details are not published in website examples. The initial buyer review uses a redacted summary. Release and permitted use are controlled by the signed Buyer Agreement.

Sharing a customer request

When the requester grants permission and Amblet identifies a potential match against an approved provider's documented service and territory criteria, Amblet may share the submitted contact and project information with that provider. Amblet does not promise that a provider is available or will respond.

Do not submit sensitive security information

Do not use the website forms to send passwords, credentials, alarm or door codes, precise camera blind spots, detailed floor plans, vulnerability reports, or emergency information. Use the forms only for general commercial-project needs.

Cookies, attribution, and analytics

The website preserves standard UTM campaign parameters in session storage so the application journey can retain its marketing source. No third-party analytics provider is installed by this rebuild. If an approved analytics data layer already exists, the site can emit first-party conversion event names to it.

Internal access, retention, and requests

Access should be limited to people and configured service providers who need the information for intake, security, matching, communications, dispute, and operational work. Amblet has not published a fixed retention period. Records may be retained for those needs while policy is finalized. To ask about access, correction, withdrawal, or deletion, call 1 (616) 466-0095. Legal or operational requirements may limit a request.

Security limits

Amblet uses same-origin submission, server validation, rate limiting, private storage, and restricted browser policies. No internet transmission or storage system can be guaranteed completely secure.

Changes

This notice may change as the operating process and service providers are confirmed. The effective date above identifies the current version.