Last Updated: November 4, 2026
ThinkMatch collects the information needed to create and operate your account, such as your name, email address, profile information, event activity, questionnaire responses, and messages you choose to send. We use an essential, secure authentication cookie to keep website users signed in. We do not use that cookie for advertising. We may associate limited IP address, browser, and device information with account sessions for security, abuse prevention, troubleshooting, and aggregate service analysis.
Public message-board posts, replies, author names, edits, reports, and moderation actions are processed to operate and protect public discussions. If you enable notifications, we store your board preference and the device or browser notification token needed to deliver them. Public-board notification choices are separate from private group-chat notifications.
Links in outreach emails may use a first-party redirect token so we can measure whether a campaign link was requested. When the linked ThinkMatch, Meet In Common, or Common Quandary page loads, we may record that the page loaded and whether the visitor interacted with it. This measurement does not use advertising cookies or store the visitor's raw IP address. Automated email-security systems may request links, so redirect requests are not treated as proof that a person viewed or engaged with a page.
Choosing phone contacts is optional. The system picker gives ThinkMatch access only to the contacts or email addresses you select. We do not import your whole address book or phone numbers. When you tap Add, selected names and email addresses are sent to ThinkMatch servers and saved as your private reusable contacts for guest management and invitations. Adding contacts does not send invitations. Removing a guest from an event does not delete the reusable contact; contact us using the privacy and deletion procedures below to request removal.
If you allow device location, ThinkMatch uses approximate or precise location to show your position with the green map marker and find nearby venues and events. Precise location places the marker more accurately as you move. You can choose a city or address manually instead of allowing device location.
In the Android app, the ongoing location watch runs while you use device-location mode in the nearby map or list. It pauses when the app becomes inactive or hidden, resumes when you return, and stops when you choose a manual location, switch to online events, or leave the nearby homepage.
Location is not processed only on your device. We send coordinates to ThinkMatch servers for nearby searches and location labels, and to mapping or geocoding providers when needed. We remember your latest current or chosen location on your device. Server search caches may retain rounded coordinates, and request logs may contain location parameters. See the retention section below for our data retention practices.
You can change or revoke location permission in your device or browser settings, choose approximate location where supported, or select a location manually. Clearing ThinkMatch app or site data removes locally saved locations and other local settings. Revoking permission does not by itself delete existing server records; contact us using the privacy or deletion procedures below.
We use information to provide accounts, events, introductions, matching, messages, notifications, customer support, and other features requested by users; to secure, troubleshoot, and improve the service; to prevent fraud and abuse; and to comply with legal obligations. Questionnaire responses and profile information are used to support the introductions, groups, and conversation suggestions a user requests. We do not sell personal information or use MCP connector data for advertising or behavioral profiling.
ThinkMatch offers public MCP tools for venue discovery, published discussion topics and editable event drafts. No ThinkMatch account is required to prepare a draft. Creating an event requires sign-in and explicit confirmation on ThinkMatch.
Event drafts and images: When requested, the assistant sends the agreed topic, title, invitation, venue identifier, date/time, question text, answer choices, required flags and event settings. It may send a public image URL or a selected conversation image with a temporary download URL and file identifier. ThinkMatch retrieves and normalizes that image, removes embedded metadata, and caches the image in server memory for up to 30 minutes or until a restart. The assistant provider and the selected image host process the transfer; ThinkMatch does not generate these images. Tool results include published topics/questions and a review link containing the draft data and, when applicable, a temporary image-access token. Anyone with that link may read its contents and access the image before expiry; avoid sensitive information and share carefully. Opening the link stores the draft and imported image in browser storage, including across sign-in, until cleared using the browser site-data controls. Temporary image access expires automatically. Only after the user signs in and confirms creation are event details and the image stored as account/event content under the retention and deletion rules below. Users can omit or replace images, edit the draft, abandon it without creating an event, clear local site data, or request deletion through support.
Planning-poll drafts receive a title, invitation, proposed local times, time zone, freely chosen place names or meeting descriptions, guest-suggestion preference and email-notification preference. The poll tool does not geocode these locations, collect an email address or store/publish a poll. Its review link contains these draft details; opening it saves them in your browser until you discard them, clear site data or the draft expires after 14 days. Anyone receiving the review link can read its contents. Publishing requires sign-in and confirmation; enabled notifications go to your verified host-account email. Anyone with the published poll link can view its options and named responses. Creating an event from a poll is optional.
Personal-feedback tools read public templates and receive your agreed survey title, template, question IDs, custom questions and choices, and content language. They return this wording in an editable review link to your AI assistant without storing or publishing a survey or accessing responses. Anyone receiving the review link can read its contents. Opening it stores a browser draft for up to 14 days; discard it or clear site data to remove it. Sign-in and explicit confirmation are required to publish. Published survey wording and your account name are visible to anyone with its response link. Respondents need no account; response tables store answers and a hashed browser retry key, not names, email addresses, account IDs or IP addresses. Infrastructure access logs still exist. Only the owner can access aggregate results; small groups or identifying questions may still reveal respondents. Owners can close collection or delete surveys and their responses through Your surveys. ThinkMatch hosting and security providers process these requests, and your AI provider handles its own conversation records.
Connector inputs: Venue discovery receives search terms, coarse coordinates, filters or OpenStreetMap identifiers. Event drafts may also receive a complete user-supplied street address, including a home or office, and the event details and chosen image described below. We send custom addresses to OpenStreetMap Nominatim to resolve coordinates and time zone without using our shared geocoding cache. Addresses and coordinates are included in review links and browser drafts. Anyone receiving a review or event link may see its address. Public map listing is optional for open events and unavailable for invite-only events. We also receive IP address, request time, user agent and language. The tools do not request credentials, contacts, attendee answers or full chat transcripts.
Purposes: We use inputs to find public venues and topics, show venue cards, prepare requested event drafts and transfer chosen images, enforce rate limits, diagnose failures and protect the service.
Connector outputs: Results may include whether a venue is in the ThinkMatch catalog; venue name, category, city, region, country, OpenStreetMap type and ID, public coordinates, approximate distance, a coarse status indicating either that people may be waiting or that an introduction can be started, and public ThinkMatch venue, image, and prefilled event-wizard links. Results never include participant names, profiles, contact information, questionnaire answers, private messages, party IDs, or exact participant counts. Opening an event-wizard link does not create an event; the user must sign in to ThinkMatch and confirm it there.
Recipients: We return tool results to the AI assistant provider that sent the request so it can display them to the user. Hosting, content-delivery, database, security, and image-storage providers process limited information for us as service providers. Loading a venue image sends the ordinary web request to the identified ThinkMatch image host. The AI assistant provider separately controls its conversation records under its own privacy policy and user controls.
Retention: ThinkMatch does not save MCP search terms, coarse location inputs, or tool results to a user profile or venue record. They are processed transiently to answer the request. An in-memory rate-limit key expires after one minute. Security and operational logs, which may include network metadata and the requested MCP path, are retained by ThinkMatch for no more than 14 days unless a longer period is required to investigate abuse, protect the service, or comply with law. Public venue catalog information remains available independently of any connector request.
Controls: Users can avoid connector processing by not enabling or invoking the ThinkMatch plugin, can disconnect it through their AI assistant settings, and can omit location or provide only a city or region. Because anonymous connector requests are not linked to a ThinkMatch account, ThinkMatch cannot use them to build an account history. Requests concerning access, correction, deletion, or privacy may be sent to [email protected]. Controls for the conversation itself are provided by the AI assistant provider.
If you ask an assistant to prepare an event draft, we also process its title, invitation, venue, date and time, grouping, visibility, question definitions (not participant answers), language, and optional public image URL. These inputs are processed transiently to build a review link returned to the assistant. The link contains the draft details; anyone you share it with can read them. Opening it saves an editable draft on your device, which you can resume for 14 days. It remains in browser storage until you discard it or clear that storage. For an optional image, ThinkMatch fetches the public host, processes the image in memory, and saves it in your browser; the image host receives the network request. No event or image is published until you sign in and confirm creation. The assistant provider separately controls conversation retention.
We disclose information only as needed to provide the service: to hosting, database, content-delivery, authentication, email, notification, communications, mapping, AI-processing, security, and customer-support providers acting for us; to other users when a user intentionally posts publicly, joins an event, or shares within a group; to identity providers when a user chooses their sign-in service; and to authorities or other parties when required by law, needed to protect rights and safety, or involved in a corporate transaction. Providers receive only information needed for their function and are subject to applicable contractual or legal duties. We do not sell or rent personal information.
Account information is kept while an account is active and is deleted or de-identified after a verified deletion request, normally within 30 days. Authentication sessions normally expire after 30 days. Event participation, questionnaire responses, messages, public posts, and notification preferences remain for the relevant account or feature lifecycle, unless the user deletes them or applicable safety, fraud-prevention, dispute, or legal obligations require limited retention. Operational logs are retained for no more than 14 days under normal operations. Protected backups may persist until the normal backup cycle completes and are not used for active product purposes.
Users may review or update profile information, delete questionnaire answers where that control is offered, change notification permissions in the browser or device, decline to share location, remove public content where the feature permits, disconnect Google or Meta sign-in, and permanently delete their ThinkMatch account from the Profile page. A user may also email [email protected] to request access, correction, or deletion or to ask a privacy question.
When a user chooses Meta login, we may receive the name, email address, and account identifier needed to authenticate and provide account functionality. We use this information only for those purposes. It may be processed by the service providers described above, but it is not sold or rented.
You may request permanent deletion of your ThinkMatch account and associated personal data at any time. This includes personal data received through Facebook Login.
Delete your account directly in ThinkMatch:
If you cannot log in, you may instead request deletion by email:
Information that must be retained for fraud prevention, security, legal compliance, or resolving disputes may be retained only as permitted by law. Residual protected backup copies may remain temporarily until the normal backup-retention cycle completes and are not used for active product purposes.
Public message boards are removed with their parent topic, article, or party. Reports, content snapshots, and moderation records may be retained where needed to document safety, publisher-removal, legal, or operational decisions.
You may also remove ThinkMatch from Facebook under Settings & Privacy > Apps and Websites. Removing Facebook access stops future Facebook access, but it does not by itself delete an existing ThinkMatch account; use the Profile-page option or the email procedure above to delete the ThinkMatch account and its data.
ThinkMatch has a zero-tolerance policy regarding Child Sexual Abuse and Exploitation (CSAE). To ensure a safe environment for all users, we adhere to the following standards:
If you have questions regarding this policy, contact [email protected].