Your information, in plain view.

01 · Status and scope

What this draft covers.

This page is intended to cover personal information handled through the NurseBuiltAI website, including newsletter sign-up, gated resources, business enquiries, scheduling, and future measurement of site use. It does not finalize the legal role of NurseBuiltAI or any service provider; those roles depend on the selected services, contracts, and applicable law.

The current site is a prototype. Its shared newsletter and other prototype forms are designed to stop locally and state that nothing was submitted until production endpoints are configured. The booking configuration is also unpopulated. This draft describes both that current state and the processing that is expected once those services are connected.

Last updated

No publication date has been assigned to this draft.

Jurisdiction

Not yet confirmed; rights and notices will be tailored after review.

Providers

Kit and Cal are planned; analytics, hosting, and contact-form providers are not yet confirmed here.

Privacy route

Use the Contact page and label the message “Privacy request.”

02 · Site analytics

Measurement will wait for a clear choice.

No analytics provider has been selected in the current production configuration. Analytics events are planned only after a provider and the related consent requirements have been reviewed. NurseBuiltAI does not plan to send form-message text or other sensitive free-text content in analytics events.

If analytics are enabled, the final policy will name the provider and explain the information it receives. Depending on the service, that may include pages visited, approximate location derived from an IP address, device and browser details, referral information, event timestamps, and interactions such as opening an article or choosing a resource filter.

A future hosting or security provider may also process request information such as an IP address, timestamp, requested page, and browser details to deliver and protect the site. Those provider details and any available controls will be added after hosting is confirmed.

03 · Newsletter and resources

Email is used for the thing you asked for.

Newsletter

Once the newsletter connection is active, NurseBuiltAI expects to use Kit to collect an email address and, only where the form asks for it, a first name. The provider may also record consent, sign-up source, delivery, and engagement information needed to operate the mailing list. The production notice will identify the exact Kit account setup and available unsubscribe controls.

Kit resource gates

A gated resource may collect a first name, email address, the requested resource ID, its source video ID or URL, an approved public tag, and delivery status. That information is intended to deliver the selected resource and keep an accurate delivery record. Requesting a resource should not silently enroll someone in unrelated email; any newsletter choice must be stated beside the form.

Kit is not connected in the current shared configuration, so the prototype must not transmit form entries or reveal a private delivery URL. When Kit is connected, its own processing terms and privacy notice will also apply and will be linked from the relevant form.

04 · Contact and business enquiries

An enquiry should contain only what the conversation needs.

When a contact-form service is connected, NurseBuiltAI expects to collect basic contact and professional details: name, work email, organization, role, optional website, country or time zone, enquiry type, message, and consent record. That information would be used to understand and respond to the enquiry and, where relevant, discuss a possible engagement.

Additional fields depend on what the visitor selects. They may include team size, workflow and timing, a non-binding budget band, event or campaign details, audience information, location, format, publication details, or a deadline. The final policy will name the contact-form provider, recipient, security arrangements, and confirmed retention approach.

05 · Cal scheduling

Booking data will pass through Cal.

The site plans to use Cal for scheduling, but the owner booking URL is not yet configured. If scheduling is enabled, the information entered into the Cal page or embed may include name, contact details, time zone, chosen time, answers to booking questions, and optional notes. Cal may also process device, browser, and service metadata as an independent third-party service.

The final version of this policy will link to the applicable Cal privacy information, identify whether the experience is embedded or external, and explain how booking records are shared with NurseBuiltAI and any connected calendar or meeting provider. Visitors will still have a contact alternative.

06 · Cookies and browser storage

Storage choices depend on connected services.

NurseBuiltAI’s current shared site script does not write cookies or local-storage values. The browser may still cache public files as part of normal page delivery. Once Kit, Cal, analytics, hosting, or other third-party features are connected, those services may use cookies, pixels, or similar browser storage for security, preferences, form delivery, measurement, or service operation.

No advertising technology has been selected in the current configuration. Before non-essential storage is enabled, NurseBuiltAI will review the provider behavior and the consent controls required in the applicable jurisdictions. The finalized notice will explain categories, providers, purposes, and how to change a choice.

07 · Retention and transfers

Time limits and locations still need review.

How long information is kept

Exact retention periods have not been approved. The intended approach is to keep information only for as long as needed to provide the requested communication or resource, manage an enquiry or scheduling record, meet security and record-keeping needs, resolve disputes, and comply with applicable obligations. Different records may need different schedules, and provider backups may follow their own documented cycles.

International processing

Some future providers may process information in countries other than the visitor’s own. Whether that is an international transfer, and which legal safeguards or contract terms are required, depends on the selected provider, the people served, and the applicable jurisdiction. The final policy will identify relevant provider locations and transfer mechanisms after that review.

08 · Your choices and rights

Ask, change, unsubscribe, or raise a concern.

Depending on where you live and which law applies, you may have rights to ask whether information is held, request access or correction, request deletion, object to or restrict some uses, receive a portable copy, withdraw consent, or complain to a regulator. These rights are not identical everywhere, and lawful exceptions may apply.

• Newsletter messages should include an unsubscribe route once the provider is live.
• Withdrawing consent does not undo processing that was lawful before withdrawal.
• NurseBuiltAI may need enough information to verify the requester and locate the relevant record.
• A request may be limited where information must be kept for a legal, security, or record-keeping reason.

To make a request now, use the Contact page, choose the general business enquiry route, and begin the message with “Privacy request.” Do not include patient information or copies of sensitive identity documents in the first message. The confirmed privacy contact and jurisdiction-specific escalation route will be added before this policy becomes effective.

09 · Changes and dates

Dates will appear after approval.

This draft deliberately has no effective date, last-updated date, or governing jurisdiction. Those details must not be inferred from the website copyright year. After providers, data flows, and applicable requirements are confirmed and the policy is reviewed, NurseBuiltAI will publish an effective date and an updated date here. Material changes will be described in the version then in force.