What is collected, who holds it, and what never moves.

• VoyantIQ never sells your data and never uses it for advertising.
• Three different operators appear on this page and they hold different things. The next section says which is which.
• Selling an application to a buyer transfers no user data. The buyer receives source code, schema and migrations, and nobody's records.
• External AI models are reached only through VoyantIQ's own routing layer, and only the part of a request a feature needs is sent.
• Analytics identifies you by an internal account identifier only, and never records what you typed.
• Every demonstration on this site runs on synthetic data and stores nothing unless you ask to be contacted.
• There is no self-serve account deletion or full data export yet. Ask, and it is handled for you.

This Website

• Operated by VoyantIQ. It holds storefront accounts, acquisition inquiries, contact messages and the analytics described below.
• Browsing the applications, reading about Tools, exploring a demonstration and asking about an acquisition require no account.

The Hosted Tools Platform

• Operated by VoyantIQ, on its own address, with its own database and its own sign-in. A storefront account is not a Tools account and cannot reach one.
• No Tool is published for sale yet, so no customer document, prompt or run history exists there today. What a Tool will store is described in its own section below and on that Tool's page before you subscribe.
• This website reads only the Tools platform's public catalogue, which carries no personal information in either direction.

An Acquired Application, After Handover

• Operated by its buyer, not by VoyantIQ. Once an application is handed over, the buyer runs it, holds its database, sets its privacy terms and answers for it.
• VoyantIQ does not host an acquired deployment, does not hold credentials to it, and does not receive data from it. Your relationship about that deployment is with its operator.
• During the bounded handover window VoyantIQ may be shown information by the buyer in order to resolve a reported defect. That is the buyer's decision and the buyer's data, handled under the acquisition agreement.

Legacy VoyantIQ Products

• VoyantIQ previously ran a subscription product estate — travel planning, team stays, business travel, property evaluation, founder operations and a partner interface. Those subscriptions are retired and are not sold.
• Accounts and data created under them still exist and still work, and are still operated by VoyantIQ. What they hold is listed in its own section below rather than removed from this page, because removing it would hide data that is really there.

• An acquisition transfers that application's source code, database schema, migrations, deployment configuration, documentation, and the application-specific intellectual property VoyantIQ owns and has agreed to transfer.
• It transfers no user records, no account, no inquiry, no email address and no usage history. A buyer receives an empty database and the means to create one.
• Acquiring source code does not remove a buyer's own privacy responsibilities. Once they operate a deployment with real people in it, those obligations are theirs.
• Nothing in an acquisition makes a VoyantIQ account holder a customer of the buyer.

• Your name and email address, and a profile image if you sign in with Google or Microsoft.
• Your password, which is never stored in plain text.
• For each signed-in session: when it expires, and the network address and browser description it was created from.
• A record of account security events, such as signing in, signing out, resetting a password and verifying an email address.
• If you start planning in a legacy product before creating an account, a guest session. Only a hashed form of its identifier is stored, and work you started can be claimed into your account when you sign up.

• Every Contact category, including an acquisition inquiry and a custom-work request, is stored as one inquiry record: your name, email address, company, message, and any detail you choose to add such as company size, interest, timing or security requirements.
• Where you came from is attached when it can be checked against VoyantIQ's own catalogue, such as a demonstration or an application you were reading about.
• An email notification carrying your message is sent to VoyantIQ so a person can reply.
• No customer relationship management system is connected today. If one is added, inquiries are still stored by VoyantIQ first.

• A Tool holds what you give it to work on, in your workspace, separated from every other workspace.
• A Tool's own system instructions, thresholds and model configuration are VoyantIQ's and stay on the server. They are never in anything your browser receives.
• An activity record says what was read, what was done, what needed your approval and what the result was. It is written so it can be useful without carrying the implementation.
• The Tools platform has its own account. Creating one does not create a storefront account, and neither can read the other's data.

• Every demonstration runs on synthetic data and writes nothing to VoyantIQ's database.
• If you type a request into one, the text is sent through the model routing layer to interpret it. It is not stored, not logged and not recorded in analytics. A short-lived rate limit held in one server's memory uses your network address.
• If you ask to be sent next steps, your email address, and your name if you give it, are stored as an inquiry along with what you were looking at.

• When product analytics is enabled, VoyantIQ uses PostHog to understand how the product is used.
• You are identified only by an internal account identifier. Your name and email address are not sent.
• Events carry identifiers, categories, counts and yes or no values. They never carry prompts, messages, names, email addresses, street addresses or notes, and an automated test fails if an event property is named for that kind of content.
• Automatic click capture is turned off. Only named events are recorded, along with page views and errors.
• VoyantIQ also uses Google Analytics on its public pages to count visits and see which pages people arrive on. Google Analytics sets its own cookies.
• It receives the page you are on and nothing else. An address that identifies one customer's own record is reduced to the kind of page before it is sent, and an invitation link or a payment session reference is removed entirely rather than passed on.
• Session replay masks every form input, and masks saved conversations and preferences shown as text.
• VoyantIQ asks before it sets any analytics cookie and loads Google Analytics only if you accept. Declining is remembered and you are not asked again. You can change your answer at any time using the control below. VoyantIQ does not currently respond to a browser's Do Not Track setting.

• External AI models are reached only through VoyantIQ's model routing layer, never directly from product code. Today that means Google Gemini, with Anthropic Claude as the next provider when Gemini is unavailable.
• What is sent depends on the feature: a message or description you typed, a question about one record together with that record's facts, or a document you asked VoyantIQ to read.
• Operational logs about an AI request record which provider and model answered, how long it took, and whether the answer was valid. They never record the request or the response.
• When no provider is available, features fall back to VoyantIQ's own deterministic responses.
• VoyantIQ does not use your content to train AI models. How long a provider keeps a request it receives is governed by that provider's terms.

Payments

• Payments on this site happen in Stripe's hosted checkout and billing portal. Stripe receives your name, email address and workspace identifier.
• VoyantIQ stores Stripe's customer and subscription identifiers, your plan, status, billing interval, renewal and cancellation dates, and one-time purchases. It never stores card details.
• An application acquisition does not pass through checkout, so Stripe receives nothing about one.

Email

• Email is sent through Resend: account verification, password resets, invitations, notifications and inquiry notifications to VoyantIQ.
• VoyantIQ does not send marketing email.

File Storage

• Uploaded files and generated documents are kept in private Vercel Blob storage.

Analytics

• PostHog for product analytics, and Google Analytics on public pages, both as described above and both subject to your consent where a cookie is involved.

AI Providers

• Google and Anthropic, reached only through the routing layer described above.

Location and Data Providers, in Legacy Products

• To estimate a starting point, a legacy travel product uses the location information its hosting platform provides, and where that is unavailable sends your network address to freeipapi.com to make the same estimate. The estimate is not stored.
• To find real options, search details such as places, dates and the number of adults and children are sent to travel data providers. Addresses you enter are sent to OpenStreetMap services, and property addresses to a property data provider.

Travel Planning

• Trips: where from and where to, dates, budget, notes, and the planning conversation you typed, which is kept as part of the trip.
• Travelers: names, birth dates, relationships, preferences, accessibility needs, and medical or safety notes you chose to add.
• Travel documents by type, status, expiry and issuing country, without a document number or image. Known traveler numbers and loyalty membership numbers are stored if you added them.
• Preferences VoyantIQ learned, recommendations it produced, the decisions you made about them, and documents you uploaded.

Team Stays

• Organizations, events, venues, rosters and who is in each party.
• Household details a participant or organizer provided, such as accompanying adults and children, room and bed needs, and accessibility needs.
• For participants who are minors, guardian contact email addresses and a recorded consent state: pending, granted or revoked.
• Hotel quotes, the contacts they came from, and quote documents an organizer uploaded.

Business Travel

• The purpose of a work trip, its cost centre and project reference, and the commitments it was planned around.
• Travel policies, how each trip was evaluated against them, and approval requests and decisions.
• Receipts: amount, currency, category, merchant, date, and the uploaded file.

Property Evaluation

• The properties you evaluated, including details from a property data provider.
• Your objectives and maximum budget, and how each property was evaluated.
• Visit findings, notes and photos you uploaded.

Founder Operations

• Companies, applications, repository and deployment references, and domains you added.
• Services with their plans, costs, renewal dates and notes, and the decisions you recorded about them.
• When it read repository or deployment details it used VoyantIQ's own read-only access. It did not ask for, or store, credentials to your accounts.

The Retired Partner Interface

• Partner applications and their environments. Partner credentials are stored only as a hash, and webhook signing secrets encrypted.
• The external user identifiers a partner linked, usage and activity records, and branding settings.
• This interface is not offered for sale and is not open to new partners.

• A session cookie keeps you signed in.
• A guest cookie, lasting 30 days, holds your place if you start work in a legacy product before creating an account.
• An active workspace cookie, lasting one year, remembers which workspace you were using.
• A departure location cookie, lasting 180 days, remembers a starting location you confirmed in a legacy travel product.
• Your appearance setting is kept in your browser's local storage, and a few interface choices in session storage.
• When analytics is enabled, PostHog keeps its own identifiers in your browser.
• None of these are used for advertising.

• Invitation, guest, claim and guardian tokens and partner credentials are stored only as hashes. Webhook signing secrets are encrypted.
• Sensitive fields, such as medical or safety notes, are kept out of list views and out of the default context AI reasoning reads. They are not separately encrypted field by field today.
• Sign-in is rate limited, by counters held in one server process's memory rather than shared across instances. The Security page describes what that does and does not cover.

• A preference VoyantIQ learns is proposed to you first. You can confirm, correct, reject or delete it, and edit saved preferences directly.
• You can remove accessibility needs, travel documents, loyalty memberships and uploaded documents. A traveler can be archived and then permanently deleted. A trip can be archived.
• You can change your name and password in account settings.
• There is no self-serve account deletion or full personal data export yet. Write to the address below and either request is handled for you.

• There is no automatic retention schedule today. Data is kept until you remove it or ask for it to be deleted.
• Guest sessions stop working after 30 days and guest claim links after 24 hours, but their records are not yet removed automatically.
• Cancelling a subscription does not delete anything in your workspace.