How Concourse uses AI
Concourse uses open-source AI models that run on our own server. No event data or personal data is sent to an outside AI provider. AI never makes a decision with legal or similarly significant effect on you.
- Anything AI filled in on an event is marked “AI” on that event.
- LinkedIn post drafts are labelled “Drafted with AI, edited by you” and are never posted without your action.
- Ranking is based only on preferences you set, and every event shows why it ranked.
AI register
| Use | Purpose | Model | Data | Human oversight |
|---|---|---|---|---|
| Category tagging | Assign industry and format categories | Same model plus keyword rules | Public | Tags marked as AI; admin can change |
| Duplicate matching | Merge the same event from several sources | Fuzzy matching; optional bge-m3 embeddings | Public | Merges are logged and reversible by admin |
| Employer watch | Highlight events that mention companies on the user's private watch list | String matching, no model | User's encrypted watch list (decrypted in memory only) and public event text | User sees which name matched; list is never shown to admins |
| Event extraction | Turn scrubbed page or email text into event fields | Open-weight model via Ollama (Qwen3.5 / Gemma 4, Apache 2.0); rule-based fallback | Public and internal only; personal data removed before the model sees it | Low-confidence results go to the review queue; admin approves |
| LinkedIn draft | Draft an attendance post for the user to edit | Template with optional model rewrite | User's chosen event (public) | Labelled "Drafted with AI, edited by you"; never posted without user action |
| Relevance scoring | Order the feed for each user | Rules over the user's own preferences (no model training) | Confidential (user preferences) and public | User sees why an event is ranked; can change preferences; no legal or similar effect |