Privacy Policy

What we collect

The private itinerary service stores each website-enabled crew member’s name, verified mobile number, authentication identifier, access status, and sign-in or session activity. For app activity, it records the signed-in crew identity, page path, timestamp, and a user-agent string that can describe the device and browser. It also records the label and destination when a member selects an outbound link, a private menu PDF, or a photo-download or API link.

Hosts may also add texts-only contacts. The service stores their name, mobile number, contact status, consent, and messaging records, but adding a texts-only contact does not create an authentication account or grant website access.

The service stores SMS consent choices and timestamps, disclosure version, the phone and time associated with the initial STOP/HELP disclosure, final outbound message and recipient audit records, Twilio delivery outcomes and error codes, STOP/START/HELP metadata, and trip photos and captions a member chooses to share. Unknown inbound text content is represented by a SHA-256 hash; the message body and media content are not stored.

How information is used

Information is used only to secure and administer the private itinerary, coordinate the September 10–13, 2026 Napa trip, troubleshoot access and delivery problems, measure aggregate app usage, deliver consented itinerary reminders or urgent schedule changes, operate shared photos, and maintain required consent and opt-out records. The program does not use mobile information for advertising, sales, lead generation, or unrelated American Intelligence Works LLC communications.

Administration and operational records

Host actions that add, edit, suspend, or restore a crew member or texts-only contact are recorded with the acting host and before-and-after state. Starting the saved text schedule records the authorizing host, roster, and provider acceptance of the invitation batch. Changes to the trip-status message or shared-photo availability are also audited. These records preserve accountability without deleting prior activity, photos, consent, message audiences, or delivery history when access is paused.

Authentication codes are separate

When a guest requests a one-time sign-in code, the mobile number is used to deliver that requested transactional authentication message. Requesting or receiving a sign-in code does not enroll the guest in Napa Proposal Weekend Trip Updates and does not authorize recurring trip updates.

Service providers

American Intelligence Works LLC is the registered Twilio account holder and administers SMS delivery for this private program. Supabase processes authentication and stores app data, Twilio processes SMS delivery and supplies delivery outcomes plus STOP/START/UNSTOP/HELP metadata, and Vercel hosts the website and supplies aggregated, anonymous Web Analytics. These providers process information only as needed to operate the service and do not use guest information for their own marketing. Neither the program nor American Intelligence Works LLC sells, rents, or shares guest mobile numbers for advertising or third-party marketing.

SMS opt-in data and consent

Consent may be recorded through the authenticated website checkbox or a signed Twilio START event from a host-listed phone. The app retains the phone, timestamp, disclosure version, and enrollment source. Mobile numbers, SMS opt-in data, and text messaging consent are not sold, rented, traded, transferred, or disclosed to third parties or affiliates for their own marketing or promotional purposes.

All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

Choices and retention

SMS participation is optional. Recipients may reply STOP to any Napa Proposal Weekend Trip Updates message; website members can also disable text updates in the app. Twilio handles reserved keywords; the app retains the signed command metadata for audit and sends no keyword reply. START or UNSTOP from a host-listed phone can enroll that phone or clear a text-originated STOP. An in-app opt-out can still be reversed in the app. Consent, delivery, access-administration, and opt-out records are retained as reasonably necessary to document messaging preferences and private-trip operations. No fixed deletion schedule is promised for other trip data.

Questions

Reply HELP to a Napa Proposal Weekend Trip Updates message or email hello@americanintelligenceworks.com. Requests to review or remove personal information will be handled directly with the verified guest.