/ Privacy while Brooks AI HUB opens. /

Brooks AI HUB is opening in stages. During the waitlist period, Northern Americana Tech collects only the information needed to run the waitlist, send launch updates, plan staged access, and prevent abuse.

Website privacy controls

Optional analytics start off. Use Privacy settings in the footer to review or withdraw your choice at any time. Using essential site functions only does not block the public website.

Required site storage

Purpose
Consent choice, security, routing, PWA behavior, and core preferences.
Provider
Brooks AI HUB / Northern Americana Tech
Retention / choice
Always enabled; privacy choice retained up to 180 days.

Anonymous analytics

Purpose
Cookie-free, aggregated public page analytics.
Provider
Vercel
Retention / choice
No analytics cookie; Vercel controls aggregate report retention. Off until allowed and can be withdrawn.

Embedded media

Purpose
Embedded playlist playback; Spotify controls its own storage and retention.
Provider
Spotify
Retention / choice
Loads only after the separate Load Spotify player action.

Public waitlist data

Who operates this site

Brooks AI HUB is operated by Northern Americana Tech. This public site is a waitlist shell while the broader app, accounts, billing, memory, workspaces, and managed AI features remain closed to the public.

What we collect now

During the waitlist period, we collect the email address you submit, optional company information, and basic anti-abuse or technical logs needed to keep the public pages and waitlist form working.

Why we use it

Waitlist information is used for launch updates, staged access planning, early-access communication, support for removal requests, and abuse prevention. Waitlist signup data is not used to train or fine-tune AI models.

Providers during the waitlist

Mailchimp stores waitlist membership, Resend may send a Brooks AI HUB thank-you email, and Vercel or the hosting stack serves the public site. Public Vercel Analytics stays unloaded until you explicitly allow it. Spotify may receive technical data only if you separately choose to load the embedded radio player.

Retention and removal

We keep waitlist information only as long as it is useful for the waitlist, launch updates, staged access, abuse prevention, or basic operations. You can request removal at /waitlist/remove. The current MVP accepts removal requests generically and does not reveal whether an email is on the list.

Local storage and PWA behavior

Public waitlist pages use first-party browser storage for required site behavior and to remember privacy choices for up to 180 days. Service-worker files, routing state, security controls, and PWA metadata may still operate when optional analytics are rejected. Do not put secrets or sensitive personal information into public forms beyond the requested waitlist fields.

Services inquiry data

Client services inquiries

Services inquiries may collect contact details, business or project name, optional phone, website link, goals, package preference, timing, materials readiness, referral context, consent evidence, and basic technical or anti-abuse logs. A successfully saved inquiry is retained in the first-party Services datastore even if a downstream email delivery attempt fails. We use this information for fit review, communication, scopes, scheduling, delivery, approvals, payment coordination, records, and abuse prevention. Services information stays separate from waitlist and Platform data unless the person separately joins those systems. Do not submit passwords, card details, Social Security numbers, health records, government identification, or other unnecessary sensitive information.

Services retention targets

The working target is 12 months for ordinary unsuccessful or abandoned Services inquiries and seven years for signed agreements, Scopes of Work, invoices, approvals, and material client project records. These are operational targets pending professional review, legal holds, and applicable requirements.

Future Platform privacy

Before broader access opens

A fuller privacy policy is required before public accounts, billing, workspaces, memory controls, managed AI features, or broad product access open beyond the waitlist shell.