This notice describes the Borne Operations request, First Win and connected-work experience operated by J.C. Borne LLC. Agreed services may have additional terms covering their scope and information.
What this form collects
Your name, email, and the idea or process information you enter. Custom project requests include a project type, whether it is business or personal, an optional project name, any description of existing material, and preferred timing. Business service requests include a business name and optional website. First Win requests also include the chosen task, your supplied example and your permission to use that material. We store request history, replies, consent and submission times. Submission limits use hashed email and daily hashed network address values to reduce automated abuse.
Campaign links
A recognized Borne campaign link can save a campaign label in this browser tab for up to 24 hours. If you submit a request, that label stays with the request so Borne can compare requests, payments, delivery and service costs. We retain only predefined campaign labels, not the full referring address or advertising click identifiers. An unrecognized or unavailable label is recorded as unattributed. This does not subscribe you to marketing.
Optional website analytics
You can allow or decline optional analytics using the website analytics choice. If you allow it, PostHog helps Borne count public-page visits, browser sessions, which referring site brought a visitor here, guide form starts, saved signups and download-button clicks, and a fixed set of example/request steps: starting, changing and finishing the fictional demonstration, plus reaching the details, review and saved-request stages of First Win. These events contain no form answers or customer-work identifiers. A prior pageview-only opt-in does not enable these counts; we ask for the updated permission. A random browser identifier is stored in local storage to distinguish repeat visits. Your analytics choice is remembered for up to 180 days. Your browser’s Do Not Track or Global Privacy Control signal keeps optional analytics off.
Analytics does not collect form entries, customer work, account identifiers, private app pages, full referring addresses, URL query parameters or private-link fragments. Session recording, automatic click and form capture, personal profiles and IP-based location enrichment are disabled. Signed-in Borne team visits are excluded; explicitly marked verification visits are labeled as tests.
Choose “Privacy choices” in the footer to withdraw consent. This stops future analytics and clears the analytics identifiers stored by this site. Previously collected events are not automatically removed by changing this preference. Use the support form for questions about collected data. Analytics permission is separate from submitting a request, connecting an account or subscribing to marketing.
Why we use it
To assess whether Borne can help, clarify the requested task, and keep a record of the request and follow-up. The form does not enroll you in a marketing campaign or authorize access to another account.
Where the request goes
The request is stored by the hosting infrastructure used for this site. Authorized Borne operators can review it. Configured Borne server workers may process the workflow details to prepare a fit-review checklist. Submitting the intake does not itself send your details to an AI model. Later preparation of an agreed sample or workflow may use the supplied material with Borne’s configured AI service and server checks. Account access and external actions require their separate settings and authorization.
Optional landing-page signup
If you choose to sign up on Meet Borne, we save your email, the exact consent statement, signup time and recognized campaign label. Signup is optional and does not create an account, service request or purchase. The Borne team can review these records. New signups that agree to the three-part welcome series are sent to Resend with their email, consent and customer status so the sequence can be delivered. Earlier signups under the previous consent statement are not automatically enrolled. We retain the record until you request removal. You can opt out through the unsubscribe link in each email, withdraw this signup from its confirmation in the same browser tab, or use Support to request withdrawal or removal later. Withdrawal stops remaining welcome emails; an email already handed to the provider may still arrive. Repeated signups do not restart the series or reverse an unsubscribe. Network-address hashes limit automated submissions; raw addresses are not stored in this signup record.
Optional welcome emails
When email signup is available in My account, you can separately choose Borne’s three-part welcome series. We record your account email, the consent statement and version, signup time and delivery-connection status. Resend processes that email address, your subscription choice and customer status to deliver the series. Your business-task materials are not sent to the marketing service. We check confirmed purchase records to end First Win invitations. You can opt out through My account or the unsubscribe link in each email; this does not cancel your service request. Submitting an intake alone does not sign you up.
Optional Google connections
Connecting Google is a separate choice in Connections. Borne requests read access to the Gmail and Drive services you select, then limits imports to your chosen custom mail label and direct files in your selected folder. Google’s account permission is broader than those application filters. Borne stores the account identity, granted permissions, encrypted access credentials, selected sources, imported text, source references and version history for the signed-in workspace.
Imports support new plain-text email bodies and newly modified Google Docs or text files after source selection. Enabling automatic preparation authorizes Borne to send imported text to its configured OpenAI service for AI drafting and to Borne’s dedicated server for source checks. Work remains a proposal for human review. This connection does not send email or edit Google files.
Imported sources and their saved work are retained until removed through a data request; this version does not automatically expire them. Pausing stops new imports and new automatic delegation. Already queued jobs keep their instructions, stored records remain available, and the Google grant stays in place. You can revoke Borne’s grant in your Google Account connection settings. Revocation does not delete sources already saved in Borne; use the Support & information request form to request their removal.
Your creation workshop
We store the style, approved facts, files and project instructions you choose to save, along with allowance reservations, production references, revisions, delivered files and your review decisions. Sources and results are private to your account and authorized Borne production or review staff. Files use private object storage; they are not added to the public website. When you submit a creation, you choose its source files and whether to include your saved style. Each project keeps that exact snapshot, so later profile edits do not rewrite earlier work.
For an authorized production request, selected instructions and material may be processed on Borne’s production server and by its configured services, including OpenAI for planning or images and fal.ai for supported video generation. Uploading a file alone does not start generation or authorize marketing use. No permission to publish your material or showcase your project is inferred. Saved files and project records do not automatically expire; use Support to request correction, export or removal. Files needed for an active project and payment records may require review before removal. The workshop is excluded from optional website analytics.
Your Borne conversations
When you send a message to Borne, we store the message, replies, selected work references, action receipts and timestamps in your signed-in account. Your message, relevant conversation history and selected saved context are sent to the configured OpenAI service to prepare a response. Approved operating accounts can also request source-based drafts and first-cut films through the connected preparation and production services. Customer work keeps its existing scope and payment requirements.
Text files are added to the message for you to review before sending. Voice typing uses your browser’s speech service and places the recognized words in the composer; it sends no message until you choose to send. Unsent text and an interrupted save may remain in this browser tab until you clear or submit them. Saved conversations do not automatically expire in this version; use Support to request removal. Private conversation and film-workshop pages are excluded from optional website analytics.
Optional voice conversations
Approved team members can choose to start an AI voice conversation. Your microphone audio is sent to the configured voice provider. The application can supply a bounded brief from the selected saved work or workspace; it is not access to every company record. The browser displays conversation text while the session is open. This version stores session identifiers, status, timestamps, errors and provider-confirmed duration when available, rather than a recording of the conversation. A spoken update does not change saved work: it must be reviewed and saved through a separate action.
Work, payments and time-back records
Saved work can include source material and versions, business rules, AI proposals, decisions, responsible people, delivery evidence and customer feedback. Coverage plans record the selected period, reported lead and backup acceptance, interruptions, time used and cost evidence. Agreed paid services also retain agreement versions, acceptance and payment-provider references and status. Card details are entered with the payment provider, not into the Borne intake form. These records support the agreed service and its review; a recorded estimate is not a verified business result.
Your private link and client access
The receipt link is a bearer link: anyone who holds the complete link can view and reply to the request. Treat it like a private document link. The secret portion is not placed in normal query parameters, and only its hash is stored with the request. A matching signed-in email and possession of the link are required to associate a request with a client account.
Team access requests
If you request Borne team access, we save your platform-provided account identifier, name, email and request time so an administrator can review the account. Making the request does not grant team permissions or notify anyone outside Borne. Repeating it keeps the same request.
Drafts, retention, and requests about your data
An unfinished draft may be kept in this browser tab for up to 24 hours and is cleared after successful submission. Submitted requests and their history remain stored until removed through an operational data request; this version does not automatically expire submitted records. Use the Support & information request form to ask Borne to correct or remove your information, even if you no longer have your original link. We save the name, email, optional reference, request type and messages you provide, along with hashed submission-limit identifiers. The form gives you a new private link where you can return for updates; submitting it does not send an email. Keep that link private. A supplied email or reference is not proof of identity. Borne must verify authority before disclosing, changing or removing information from another record. A closed request can still receive ordinary discussion without reopening the original service.
What to leave out
Do not enter passwords, API keys, payment information, health information, government identification, or confidential client records in the intake. For a $197 First Win, use a redacted example containing only material you have permission to share.