Connector privacy and data handling

Effective October 5, 2026. This notice describes the I Do Crew connection for ChatGPT and Claude.

Information used by the connector

The connector uses your Firebase account identifier and active client or vendor membership to authorize access. After you approve a connection, it can read your own wedding or business profile, your matches, approved conversations you participate in, your notifications, and your available vendor recommendations. Wedding preferences may include the date, city, guest count, budget, styles, and cultural preferences you saved in I Do Crew. A vendor profile can include its business name, description, service area, budget range, website, and Instagram link.

Only information relevant to an authorized tool request is returned. Dedicated structured fields for counterpart account email addresses, payment links, contract tokens, moderation details, and another participant's private notes are excluded. Messages, your own notes, vendor descriptions, and notification text are returned as recorded; these free-text fields can contain personal information or links supplied by participants. Review conversation content before requesting it through an AI service. The connector cannot send messages, change bookings, make payments, or administer accounts.

Purpose and recipients

We use this information to authenticate your connection and answer the wedding-planning questions you request. Requested results are shared with the AI service you connect: OpenAI for ChatGPT, or Anthropic for Claude. Google Firebase and Google Cloud host authentication, the connector, and its authorization records. Your connected AI service handles information you send to it under its own privacy policy and account settings.

Your password is entered only in the Firebase sign-in flow. It is never included in the connector's tools, shared with an AI assistant, or stored by this connector. OAuth access and refresh tokens are issued to the connected assistant; I Do Crew persists their hashes rather than their raw values.

Retention

The connector does not persist copies of tool responses or your assistant's conversation. It reads existing I Do Crew records when needed. Existing wedding, vendor, and conversation records remain in I Do Crew independently of a connector connection.

Authorization requests expire after 10 minutes, authorization codes after 5 minutes, access tokens after 1 hour, and refresh tokens after 30 days. Refresh tokens rotate on use. Expiration prevents further use; it is not automatic deletion of the hashed authorization record. Authorization request records, token/code hashes, and consent history are retained until deleted. Contact support to request deletion of your connector authorization records. Public-client registration metadata identifies the assistant, not an I Do Crew user, and is retained while that registration is used.

Google Cloud operational HTTP logs are retained for 30 days. They may contain request timestamps, IP addresses, request URLs, HTTP status, and latency. They are used for service operation, security, and troubleshooting. The connector does not log request bodies, account credentials, access tokens, authorization codes, or tool results.

Your choices

Connecting requires Firebase sign-in and an explicit Allow read-only access choice. You can choose Cancel instead. Use Disconnect on the connection page to invalidate that assistant's grants immediately. Changing or deleting information in I Do Crew changes what future tool requests can read. Disconnecting does not remove information already shared with an AI service; manage that information through the AI service's privacy controls.

Do not request that the connector share passwords, government identifiers, payment-card details, protected health information, or other information unrelated to wedding planning. When asking about conversations, consider the information other participants have shared.

Contact

For privacy questions or a request to remove your connector authorization records, contact heath@kingofthecurve.org. Do not send passwords, tokens, or payment details in support messages.