Privacy Policy

Oakmont Planner is operated by Pierson Creative Group LLC. It provides AI-assisted hospitality and event planning tools for operators and their prospective customers.

This policy describes the data handling implemented in the product. Some capabilities are available only when configured and enabled; this policy does not announce their availability. Operators are responsible for the customer information they submit and for explaining their own handling of that information. This policy addresses Oakmont’s handling, not every operator’s independent practices.

Operator accounts: sign-in is handled through Clerk when authentication is configured. Oakmont uses the authentication provider’s user identifier and stores operator memberships, workspace names, actor identifiers, roles and account or membership status. Oakmont’s application does not implement its own password storage.

Customer and event information: the planner can process event descriptions, occasions, dates, locations, guest counts, budgets, menu preferences and service requirements. A proposal or contact request can include a name, email address, optional phone number, preferred contact method, event address and message.

Event planning may include dietary requirements and allergy information, which can be sensitive. Provide only information relevant to the event and avoid unnecessary guest-identifying or medical details. If you submit information about another person, make sure you have the authority and any permission required to do so.

Operator materials: import workflows process submitted PDFs, images and public website content. Saved records can include source references or filenames, extracted content, configuration and menu proposals, pricing inputs, review decisions, actor references and timestamps.

Planning and operational records: saved leads can include the event brief, plan revision, preliminary pricing, qualification results, review flags, operator summary and status history. Email records include delivery status, provider message identifiers, attempts and delivery-event timestamps. Not every unsaved draft is recorded as a saved lead or proposal.

The implemented workflows use information to authenticate operators, identify the appropriate workspace, interpret event requests, prepare and revise plans, support operator review, save submitted requests and proposals, and send transactional notifications when email delivery is enabled.

Operational diagnostics help identify extraction failures, rejected outputs, planning-pipeline issues and conversion errors. Operators remain responsible for reviewing AI-assisted results before using them to make menu, pricing, safety or commercial decisions.

Clerk supports authentication and sessions. Neon PostgreSQL supports stored application records. The project uses Vercel hosting configuration. Information processed by an enabled service is subject to the applicable service arrangements and provider practices.

OpenAI processes event descriptions and relevant planning context to assist interpretation, generation and revisions. Operator extraction workflows can send PDF or image content and extracted website text to OpenAI. The implemented API requests set store to false. That setting is not a promise of zero provider retention, and this policy does not make an account-level training or retention guarantee.

Resend supports transactional operator notifications and customer confirmations when enabled. Recipient addresses and message content are sent for delivery, and delivery events are recorded. Preview email delivery can be redirected to a configured test recipient; do not enter real customer information in a test environment.

Operator website-import workflows retrieve the public URL supplied by the operator. The site being retrieved may handle the resulting request under its own practices.

Stripe processes Oakmont subscription and Founding Partner Pilot payments. Payment details are collected through Stripe-hosted checkout rather than stored directly by Oakmont. Oakmont stores billing identifiers and billing state needed to provision and manage operator access.

Authentication uses Clerk session handling when configured. Operator configuration-review workflows also use application cookies to maintain a review reference or state. Those application cookies are configured for a 24-hour lifetime, are HTTP-only, and use the Secure flag in production.

The current application does not include an analytics SDK or advertising pixel. It does include operational logging for errors, extraction, safety checks and planning-pipeline counts. Hosting and authentication providers may also process technical request and session information; their deployment-specific settings and retention require final review.

Blocking necessary cookies may prevent sign-in or operator review workflows from functioning. This policy does not characterize all provider cookies as analytics or make an unverified claim that no cookies are used.

Operator access is resolved on the server using authenticated membership. Operator-scoped repository queries associate records with the appropriate workspace. These controls are designed to separate operator access; they are not an absolute security guarantee.

A customer’s submitted request is associated with the responsible operator and can be included in that operator’s transactional notification. Operators have their own responsibilities for information received and used outside Oakmont.

For questions about an event or information provided to a particular operator, contact that operator through your existing relationship. Platform privacy questions and requests to access, correct or delete information require the contact channel marked below. Request handling depends on the applicable law, the records involved and the requester’s authority; no automated self-service deletion or fixed response deadline is promised here.

Saved application records remain distinct from temporary planning input. The product includes an administrative lead-deletion capability, but no comprehensive automated retention schedule or self-service account-deletion workflow has been established in the audited implementation.

Oakmont does not currently use a single automated deletion schedule for every record type. Saved application records, billing records, delivery logs and backups may be retained for operational, security, accounting, dispute-resolution or legal purposes. A privacy request does not necessarily remove information immediately from backups or records that must be retained.

Oakmont uses authentication and operator-scoped access controls. This policy makes no claim of a security certification or a guarantee that every risk can be prevented.

For privacy, legal or support inquiries about Oakmont Planner, contact Pierson Creative Group LLC at support@oakmontplanner.com.

Privacy rights and request handling vary by location and the records involved. Material changes to this policy will be reflected in an updated notice and effective date, with additional notice where required by applicable law.